,1. Which data model best supports real-time clinical decision support across
disparate EHRs using FHIR?
A. HL7 v2 ADT messages with custom Z-segments
B. FHIR R4 resources with CDS Hooks and SMART on FHIR
C. C-CDA document templates for continuity of care
D. OpenEHR archetypes with proprietary APIs
Answer: B. FHIR R4 resources with CDS Hooks and SMART on FHIR
FHIR R4 combined with CDS Hooks and SMART on FHIR enables real-time,
standardized clinical decision support across heterogeneous EHRs by exposing discrete
resources and triggering logic at the point of care. HL7 v2 and C-CDA are
message/document-centric and lack native real-time CDS triggers, while OpenEHR
archetypes are not inherently interoperable without standardized APIs.
2. A hospital reports a 30-day readmission rate of 18% versus a national benchmark
of 12%. Which analytics approach best identifies modifiable drivers?
A. Descriptive dashboards showing monthly trends
B. Predictive modeling with logistic regression on structured EHR data
C. Prescriptive analytics using reinforcement learning on claims data
D. Comparative effectiveness analysis of readmission penalties
Answer: B. Predictive modeling with logistic regression on structured EHR data
Predictive modeling with logistic regression on structured EHR data can identify
patient-level risk factors and modifiable drivers of readmission, enabling targeted
interventions. Descriptive dashboards only show trends, prescriptive analytics require
mature action-outcome data, and comparative effectiveness focuses on treatment effects
rather than operational drivers.
Page 2
,3. Which EHR usability heuristic most directly addresses alert fatigue from excessive
clinical decision support notifications?
A. Visibility of system status
B. Match between system and real world
C. Signal-to-noise ratio optimization
D. User control and freedom
Answer: C. Signal-to-noise ratio optimization
Signal-to-noise ratio optimization directly targets alert fatigue by prioritizing
high-value alerts and suppressing low-value ones, improving the ratio of actionable to
non-actionable notifications. Visibility, real-world match, and user control are
important usability principles but do not specifically address alert burden.
4. Under HIPAA, which scenario requires a business associate agreement (BAA) for
a cloud-based FHIR API?
A. The API only stores encrypted data with no access
B. The API processes PHI on behalf of a covered entity
C. The API is used solely for research with de-identified data
D. The API is open-source and publicly available
Answer: B. The API processes PHI on behalf of a covered entity
A BAA is required when a vendor processes protected health information (PHI) on
behalf of a covered entity, including cloud-based FHIR APIs that handle PHI. Storing
encrypted data without access, using de-identified data, or open-source availability does
not eliminate BAA obligations if PHI is involved.
5. Which governance metric best evaluates the completeness of problem list
documentation across an enterprise EHR?
A. Percentage of encounters with at least one coded diagnosis
B. Number of active problems per patient
C. Time to resolution of problem list entries
D. Rate of problem list reconciliation at discharge
Answer: D. Rate of problem list reconciliation at discharge
Problem list reconciliation at discharge directly measures whether the problem list is
reviewed and updated for completeness and accuracy at a critical transition. Encounter
diagnosis coding, problem counts, and resolution times do not specifically assess
completeness of the problem list.
Page 3
, 6. In project management for EHR implementation, which critical path activity most
likely delays go-live if underestimated?
A. User training scheduling
B. Interface validation and testing
C. Hardware procurement
D. Policy revision
Answer: B. Interface validation and testing
Interface validation and testing often lie on the critical path because they require
coordination across systems, vendors, and clinical workflows; underestimation can
cascade into go-live delays. Training, hardware, and policy tasks are important but
typically more predictable and parallelizable.
7. Which telehealth modality raises the greatest concern for HIPAA-compliant
consent documentation?
A. Store-and-forward teledermatology
B. Real-time video visits via non-BAA platforms
C. Remote patient monitoring with connected devices
D. Asynchronous secure messaging
Answer: B. Real-time video visits via non-BAA platforms
Real-time video visits conducted on non-BAA platforms pose the highest risk because
PHI is transmitted in real time without a compliant agreement, violating HIPAA.
Store-and-forward, RPM, and secure messaging can be configured with BAAs and
encryption to meet requirements.
8. Which leadership strategy best aligns health IT governance with organizational
strategy in a merger?
A. Centralize all IT decisions under the CIO
B. Establish a joint clinical informatics council with shared metrics
C. Outsource EHR management to a single vendor
D. Delay integration until post-merger stabilization
Answer: B. Establish a joint clinical informatics council with shared metrics
A joint clinical informatics council with shared metrics ensures cross-organizational
alignment, clinician engagement, and strategic coherence during a merger. Centralizing
decisions, outsourcing, or delaying integration can create misalignment and resistance.
Page 4
disparate EHRs using FHIR?
A. HL7 v2 ADT messages with custom Z-segments
B. FHIR R4 resources with CDS Hooks and SMART on FHIR
C. C-CDA document templates for continuity of care
D. OpenEHR archetypes with proprietary APIs
Answer: B. FHIR R4 resources with CDS Hooks and SMART on FHIR
FHIR R4 combined with CDS Hooks and SMART on FHIR enables real-time,
standardized clinical decision support across heterogeneous EHRs by exposing discrete
resources and triggering logic at the point of care. HL7 v2 and C-CDA are
message/document-centric and lack native real-time CDS triggers, while OpenEHR
archetypes are not inherently interoperable without standardized APIs.
2. A hospital reports a 30-day readmission rate of 18% versus a national benchmark
of 12%. Which analytics approach best identifies modifiable drivers?
A. Descriptive dashboards showing monthly trends
B. Predictive modeling with logistic regression on structured EHR data
C. Prescriptive analytics using reinforcement learning on claims data
D. Comparative effectiveness analysis of readmission penalties
Answer: B. Predictive modeling with logistic regression on structured EHR data
Predictive modeling with logistic regression on structured EHR data can identify
patient-level risk factors and modifiable drivers of readmission, enabling targeted
interventions. Descriptive dashboards only show trends, prescriptive analytics require
mature action-outcome data, and comparative effectiveness focuses on treatment effects
rather than operational drivers.
Page 2
,3. Which EHR usability heuristic most directly addresses alert fatigue from excessive
clinical decision support notifications?
A. Visibility of system status
B. Match between system and real world
C. Signal-to-noise ratio optimization
D. User control and freedom
Answer: C. Signal-to-noise ratio optimization
Signal-to-noise ratio optimization directly targets alert fatigue by prioritizing
high-value alerts and suppressing low-value ones, improving the ratio of actionable to
non-actionable notifications. Visibility, real-world match, and user control are
important usability principles but do not specifically address alert burden.
4. Under HIPAA, which scenario requires a business associate agreement (BAA) for
a cloud-based FHIR API?
A. The API only stores encrypted data with no access
B. The API processes PHI on behalf of a covered entity
C. The API is used solely for research with de-identified data
D. The API is open-source and publicly available
Answer: B. The API processes PHI on behalf of a covered entity
A BAA is required when a vendor processes protected health information (PHI) on
behalf of a covered entity, including cloud-based FHIR APIs that handle PHI. Storing
encrypted data without access, using de-identified data, or open-source availability does
not eliminate BAA obligations if PHI is involved.
5. Which governance metric best evaluates the completeness of problem list
documentation across an enterprise EHR?
A. Percentage of encounters with at least one coded diagnosis
B. Number of active problems per patient
C. Time to resolution of problem list entries
D. Rate of problem list reconciliation at discharge
Answer: D. Rate of problem list reconciliation at discharge
Problem list reconciliation at discharge directly measures whether the problem list is
reviewed and updated for completeness and accuracy at a critical transition. Encounter
diagnosis coding, problem counts, and resolution times do not specifically assess
completeness of the problem list.
Page 3
, 6. In project management for EHR implementation, which critical path activity most
likely delays go-live if underestimated?
A. User training scheduling
B. Interface validation and testing
C. Hardware procurement
D. Policy revision
Answer: B. Interface validation and testing
Interface validation and testing often lie on the critical path because they require
coordination across systems, vendors, and clinical workflows; underestimation can
cascade into go-live delays. Training, hardware, and policy tasks are important but
typically more predictable and parallelizable.
7. Which telehealth modality raises the greatest concern for HIPAA-compliant
consent documentation?
A. Store-and-forward teledermatology
B. Real-time video visits via non-BAA platforms
C. Remote patient monitoring with connected devices
D. Asynchronous secure messaging
Answer: B. Real-time video visits via non-BAA platforms
Real-time video visits conducted on non-BAA platforms pose the highest risk because
PHI is transmitted in real time without a compliant agreement, violating HIPAA.
Store-and-forward, RPM, and secure messaging can be configured with BAAs and
encryption to meet requirements.
8. Which leadership strategy best aligns health IT governance with organizational
strategy in a merger?
A. Centralize all IT decisions under the CIO
B. Establish a joint clinical informatics council with shared metrics
C. Outsource EHR management to a single vendor
D. Delay integration until post-merger stabilization
Answer: B. Establish a joint clinical informatics council with shared metrics
A joint clinical informatics council with shared metrics ensures cross-organizational
alignment, clinician engagement, and strategic coherence during a merger. Centralizing
decisions, outsourcing, or delaying integration can create misalignment and resistance.
Page 4
