Epic cLN 251/252 coNfiguriNg thE Epic ENd usEr
fiNaL Exam QuEstioNs aNd corrEct VErifiEd
aNswEr with dEtaiLEd ratioNaLEs aLrEady gradEd
a+ | updatEd
1. An analyst is configuring SmartForms for a specialty clinic that requires a dynamic list of recent
lab results. Which Epic data model approach best ensures that the SmartForm displays the most
current results without manual intervention, while minimizing database queries?
A. Use a SmartForm with a Record Browser that queries the CLARITY_LABS table on form load
B. Implement a SmartForm with a linked SmartData element using the 'Get Latest Result' function with a
cached result set
C. Create a SmartForm with a direct SQL query to the CHRONICLES database using a stored procedure
D. Configure a SmartForm with a custom button that triggers a real-time HL7 message to pull lab data
Answer: B
Rationale: The 'Get Latest Result' function with caching balances performance and accuracy by
retrieving the most recent result from the operational data store while caching to reduce repeated
queries. Option A queries CLARITY which is a reporting database and may be stale; option C directly
queries CHRONICLES which is discouraged for performance; option D adds latency and complexity.
2. During a system upgrade, a configuration manager notices that certain user role templates are
causing excessive alert overrides. Which approach best aligns with Epic's current best practices to
reduce alert fatigue while maintaining safety?
A. Increase the severity level of all alerts to 'hard stop' to force compliance
B. Disable alerts for all non-critical drug-drug interactions and rely on pharmacist review
C. Implement a tiered alert strategy using the Alert Fatigue Reduction Toolkit, including suppression of
redundant alerts and grouping similar alerts
D. Customize each user's role template individually to remove alerts based on personal preference
Answer: C
Rationale: Epic's Alert Fatigue Reduction Toolkit (available since 2021) provides evidence-based
methods such as alert suppression, grouping, and tiered severity. Option A increases alert fatigue;
option B removes safety checks; option D is inefficient and inconsistent.
3. A health system wants to share patient summaries with a clinic using a different EHR that
supports only C-CDA 2.1. Which Epic interoperability configuration ensures compliant exchange
while maximizing data granularity?
A. Enable Care Everywhere with standard C-CDAs and map all local vocabularies to SNOMED CT and LOINC
B. Use Epic's FHIR R4 API to send a JSON-based summary, then convert to C-CDA at the edge
Page 1
,C. Configure a direct HL7 v2.5.1 ADT feed to the clinic's system
D. Export a PDF of the After Visit Summary and send via secure email
Answer: A
Rationale: Care Everywhere with C-CDA is the ONC-recommended standard for interoperability with
non-Epic systems. FHIR (option B) is not directly supported for C-CDA exchange; HL7 v2 (option C)
lacks structured data; PDF (option D) is not machine-readable.
4. An analyst is tasked with designing a report that identifies patients with uncontrolled
hypertension (BP >140/90 on two separate visits) who are due for a follow-up within 30 days.
Which combination of Epic reporting tools is most efficient for this task?
A. Use Reporting Workbench with a custom SQL query joining PAT_ENC and VITAL_SIGNS tables
B. Create a Hyperspace SlicerDicer dashboard with filters for BP and visit dates, then export to Excel
C. Build a Chronicles report using the 'Find Patients' function with recurrence criteria
D. Use Radar to create a population health rule that flags patients based on BP and last visit date
Answer: D
Rationale: Radar is designed for population health management and can run rules against operational
data to identify patients meeting multiple criteria. Option A is complex and may impact performance;
option B lacks automated recurrence; option C is for ad hoc queries.
5. A hospital is implementing a new opioid stewardship program. Which Epic configuration best
supports real-time monitoring of cumulative morphine milligram equivalents (MME) across
inpatient and outpatient encounters?
A. Activate the Opioid Management Best Practice Advisory with a daily MME calculation based on active
orders
B. Configure a custom SmartForm that manually calculates MME from medication administration records
C. Enable the MME column in the MAR and require nurses to document cumulative dose
D. Use the Reporting Workbench to generate weekly MME reports for review
Answer: A
Rationale: Epic's Opioid BPA automatically calculates MME from all active opioid orders across
encounters and alerts providers when thresholds are exceeded. Option B is manual and error-prone;
option C relies on nursing documentation; option D is retrospective.
6. During a security audit, it is discovered that a nurse has accessed patient records of a family
member without clinical reason. Which Epic security feature should be configured to detect and
prevent such violations proactively?
A. Enable the 'Break-the-Glass' feature with post-access auditing
B. Implement a 'Same Name' alert that flags access to patients with identical names
C. Configure a 'Patient Relationship' audit rule that triggers when a user accesses a record of a patient with a
matching address or phone number
D. Set up a 'Missed Opportunity' alert that notifies when a user views a record without a scheduled appointment
Answer: C
Rationale: Epic's Patient Relationship audit rules allow detection of inappropriate access based on
shared demographics. Option A is for emergency access; option B is too broad; option D does not
Page 2
,address family access.
7. A clinic wants to automate the process of sending patient reminders for overdue preventive
screenings. Which Epic tool and configuration best achieves this with minimal manual effort?
A. Use the 'MyChart' messaging system to manually send bulk messages
B. Configure a 'Population Health' registry in Radar with automated outreach via phone and MyChart
C. Create a 'SmartForm' that prints reminders at checkout
D. Set up a 'Reporting Workbench' report that is emailed to staff weekly
Answer: B
Rationale: Radar registries can define patient cohorts and trigger automated outreach (e.g., MyChart
messages, IVR calls) based on care gaps. Option A is manual; option C is point-of-care only; option D
requires staff action.
8. An analyst is optimizing the 'Schedule Appointment' workflow for a multi-specialty clinic.
Which Epic configuration reduces the number of clicks for front-desk staff while ensuring accurate
scheduling?
A. Use a single 'Quick Schedule' template for all visit types and specialties
B. Configure 'SmartLinks' that auto-populate patient demographics and insurance from the MPI
C. Enable 'Appointment Assistant' with specialty-specific search filters and auto-suggested slots
D. Create a custom 'Visit Type' dropdown with 50 options to cover all scenarios
Answer: C
Rationale: Appointment Assistant provides intelligent slot suggestions based on provider schedules and
patient preferences, reducing clicks. Option A is too generic; option B is already standard; option D
increases complexity.
9. A hospital is implementing a new sepsis protocol that requires a specific order set to be activated
when the qSOFA score is 2. Which Epic clinical decision support configuration best enforces this
protocol without over-alerting?
A. Create a Best Practice Advisory that fires on all patients with any abnormal vital sign
B. Use a 'SmartSet' that automatically appears when a nurse documents a qSOFA score of 2 in the flowsheet
C. Configure a 'Hard Stop' alert that prevents the user from continuing without opening the order set
D. Set up a 'Reference Text' link in the sepsis flowsheet that suggests the order set
Answer: B
Rationale: A SmartSet can be configured to launch automatically based on flowsheet documentation,
providing immediate access to the order set without alert fatigue. Option A is too broad; option C is
disruptive; option D is passive.
10. An organization is migrating from a legacy scheduling system to Epic. They need to ensure that
historical appointment data (including cancellations, no-shows, and reschedules) is accurately
imported. Which Epic migration tool and data mapping strategy is most appropriate?
A. Use the 'Patient Merge' tool to link legacy appointments to new patients
B. Perform a one-time CSV import into the 'PAT_ENC' table using the Data Import Manager
Page 3
, C. Utilize the 'Legacy Appointment Loader' with mapping of legacy status codes to Epic's internal codes
D. Manually re-enter all historical appointments to ensure accuracy
Answer: C
Rationale: Epic's Legacy Appointment Loader is specifically designed for importing historical scheduling
data and includes code mapping functionality. Option A is for duplicate patients; option B may bypass
integrity checks; option D is impractical.
11. In the context of Epic's end-user configuration for clinical workflows, which of the following
best describes the relationship between SmartForms and SmartLinks, and how they interact to
enforce data integrity across a multi-phase clinical pathway?
A. SmartForms are static templates that capture discrete data, while SmartLinks dynamically link form fields to
external databases to auto-populate values without user intervention.
B. SmartForms use SmartLinks to pull data from the patient chart and clinical decision support rules, but
SmartLinks cannot be used to write data back to the chart; they only display read-only values.
C. SmartForms rely on SmartLinks to inject computed values or chart data into form fields, and SmartLinks can
be configured to both read from and write to the patient chart, enabling bidirectional data flow within a single
form.
D. SmartForms and SmartLinks are independent tools: SmartForms control form layout, while SmartLinks
manage report generation; they do not directly integrate.
Answer: C
Rationale: SmartForms are designed to capture structured data, and SmartLinks are the mechanism that
allows those forms to interface with the chart. SmartLinks can be set to read data into the form and,
when properly configured, to write form data back to discrete chart fields, thus ensuring data integrity
across a clinical pathway. Option A is incorrect because SmartLinks are not limited to external
databases; they work within the Epic chart. Option B is incorrect because SmartLinks can write data.
Option D is incorrect because they are integrated tools.
12. When configuring Epic's reporting workbench for a population health dashboard, a builder
needs to filter a report to include only patients with a specific combination of diagnoses and
medication orders that occurred within overlapping time windows. Which type of filter logic and
record linkage would be most appropriate to ensure accurate patient counts without
double-counting?
A. Use a single 'Encounter Diagnosis' filter with a date range and a separate 'Medication Order' filter; accept the
default logical AND between record types.
B. Use a 'Patient Record' filter with sub-filters for diagnosis and medication, and set the linkage to 'Patient' level
to combine criteria across any encounter.
C. Use a 'Cross-Encounter' filter that links diagnoses from one encounter to medications from a different
encounter using a common provider ID.
D. Use a 'Record Type' filter for 'Diagnosis' and 'Medication' separately, then manually export and merge in a
spreadsheet to avoid system limitations.
Answer: B
Rationale: For population health dashboards, filtering at the patient level (rather than encounter level)
ensures that patients meeting any combination of criteria across encounters are counted once. Option B
correctly uses patient-level linkage with sub-filters, avoiding double-counting. Option A may
double-count if a patient has multiple encounters. Option C is incorrect because cross-encounter linkage
Page 4
fiNaL Exam QuEstioNs aNd corrEct VErifiEd
aNswEr with dEtaiLEd ratioNaLEs aLrEady gradEd
a+ | updatEd
1. An analyst is configuring SmartForms for a specialty clinic that requires a dynamic list of recent
lab results. Which Epic data model approach best ensures that the SmartForm displays the most
current results without manual intervention, while minimizing database queries?
A. Use a SmartForm with a Record Browser that queries the CLARITY_LABS table on form load
B. Implement a SmartForm with a linked SmartData element using the 'Get Latest Result' function with a
cached result set
C. Create a SmartForm with a direct SQL query to the CHRONICLES database using a stored procedure
D. Configure a SmartForm with a custom button that triggers a real-time HL7 message to pull lab data
Answer: B
Rationale: The 'Get Latest Result' function with caching balances performance and accuracy by
retrieving the most recent result from the operational data store while caching to reduce repeated
queries. Option A queries CLARITY which is a reporting database and may be stale; option C directly
queries CHRONICLES which is discouraged for performance; option D adds latency and complexity.
2. During a system upgrade, a configuration manager notices that certain user role templates are
causing excessive alert overrides. Which approach best aligns with Epic's current best practices to
reduce alert fatigue while maintaining safety?
A. Increase the severity level of all alerts to 'hard stop' to force compliance
B. Disable alerts for all non-critical drug-drug interactions and rely on pharmacist review
C. Implement a tiered alert strategy using the Alert Fatigue Reduction Toolkit, including suppression of
redundant alerts and grouping similar alerts
D. Customize each user's role template individually to remove alerts based on personal preference
Answer: C
Rationale: Epic's Alert Fatigue Reduction Toolkit (available since 2021) provides evidence-based
methods such as alert suppression, grouping, and tiered severity. Option A increases alert fatigue;
option B removes safety checks; option D is inefficient and inconsistent.
3. A health system wants to share patient summaries with a clinic using a different EHR that
supports only C-CDA 2.1. Which Epic interoperability configuration ensures compliant exchange
while maximizing data granularity?
A. Enable Care Everywhere with standard C-CDAs and map all local vocabularies to SNOMED CT and LOINC
B. Use Epic's FHIR R4 API to send a JSON-based summary, then convert to C-CDA at the edge
Page 1
,C. Configure a direct HL7 v2.5.1 ADT feed to the clinic's system
D. Export a PDF of the After Visit Summary and send via secure email
Answer: A
Rationale: Care Everywhere with C-CDA is the ONC-recommended standard for interoperability with
non-Epic systems. FHIR (option B) is not directly supported for C-CDA exchange; HL7 v2 (option C)
lacks structured data; PDF (option D) is not machine-readable.
4. An analyst is tasked with designing a report that identifies patients with uncontrolled
hypertension (BP >140/90 on two separate visits) who are due for a follow-up within 30 days.
Which combination of Epic reporting tools is most efficient for this task?
A. Use Reporting Workbench with a custom SQL query joining PAT_ENC and VITAL_SIGNS tables
B. Create a Hyperspace SlicerDicer dashboard with filters for BP and visit dates, then export to Excel
C. Build a Chronicles report using the 'Find Patients' function with recurrence criteria
D. Use Radar to create a population health rule that flags patients based on BP and last visit date
Answer: D
Rationale: Radar is designed for population health management and can run rules against operational
data to identify patients meeting multiple criteria. Option A is complex and may impact performance;
option B lacks automated recurrence; option C is for ad hoc queries.
5. A hospital is implementing a new opioid stewardship program. Which Epic configuration best
supports real-time monitoring of cumulative morphine milligram equivalents (MME) across
inpatient and outpatient encounters?
A. Activate the Opioid Management Best Practice Advisory with a daily MME calculation based on active
orders
B. Configure a custom SmartForm that manually calculates MME from medication administration records
C. Enable the MME column in the MAR and require nurses to document cumulative dose
D. Use the Reporting Workbench to generate weekly MME reports for review
Answer: A
Rationale: Epic's Opioid BPA automatically calculates MME from all active opioid orders across
encounters and alerts providers when thresholds are exceeded. Option B is manual and error-prone;
option C relies on nursing documentation; option D is retrospective.
6. During a security audit, it is discovered that a nurse has accessed patient records of a family
member without clinical reason. Which Epic security feature should be configured to detect and
prevent such violations proactively?
A. Enable the 'Break-the-Glass' feature with post-access auditing
B. Implement a 'Same Name' alert that flags access to patients with identical names
C. Configure a 'Patient Relationship' audit rule that triggers when a user accesses a record of a patient with a
matching address or phone number
D. Set up a 'Missed Opportunity' alert that notifies when a user views a record without a scheduled appointment
Answer: C
Rationale: Epic's Patient Relationship audit rules allow detection of inappropriate access based on
shared demographics. Option A is for emergency access; option B is too broad; option D does not
Page 2
,address family access.
7. A clinic wants to automate the process of sending patient reminders for overdue preventive
screenings. Which Epic tool and configuration best achieves this with minimal manual effort?
A. Use the 'MyChart' messaging system to manually send bulk messages
B. Configure a 'Population Health' registry in Radar with automated outreach via phone and MyChart
C. Create a 'SmartForm' that prints reminders at checkout
D. Set up a 'Reporting Workbench' report that is emailed to staff weekly
Answer: B
Rationale: Radar registries can define patient cohorts and trigger automated outreach (e.g., MyChart
messages, IVR calls) based on care gaps. Option A is manual; option C is point-of-care only; option D
requires staff action.
8. An analyst is optimizing the 'Schedule Appointment' workflow for a multi-specialty clinic.
Which Epic configuration reduces the number of clicks for front-desk staff while ensuring accurate
scheduling?
A. Use a single 'Quick Schedule' template for all visit types and specialties
B. Configure 'SmartLinks' that auto-populate patient demographics and insurance from the MPI
C. Enable 'Appointment Assistant' with specialty-specific search filters and auto-suggested slots
D. Create a custom 'Visit Type' dropdown with 50 options to cover all scenarios
Answer: C
Rationale: Appointment Assistant provides intelligent slot suggestions based on provider schedules and
patient preferences, reducing clicks. Option A is too generic; option B is already standard; option D
increases complexity.
9. A hospital is implementing a new sepsis protocol that requires a specific order set to be activated
when the qSOFA score is 2. Which Epic clinical decision support configuration best enforces this
protocol without over-alerting?
A. Create a Best Practice Advisory that fires on all patients with any abnormal vital sign
B. Use a 'SmartSet' that automatically appears when a nurse documents a qSOFA score of 2 in the flowsheet
C. Configure a 'Hard Stop' alert that prevents the user from continuing without opening the order set
D. Set up a 'Reference Text' link in the sepsis flowsheet that suggests the order set
Answer: B
Rationale: A SmartSet can be configured to launch automatically based on flowsheet documentation,
providing immediate access to the order set without alert fatigue. Option A is too broad; option C is
disruptive; option D is passive.
10. An organization is migrating from a legacy scheduling system to Epic. They need to ensure that
historical appointment data (including cancellations, no-shows, and reschedules) is accurately
imported. Which Epic migration tool and data mapping strategy is most appropriate?
A. Use the 'Patient Merge' tool to link legacy appointments to new patients
B. Perform a one-time CSV import into the 'PAT_ENC' table using the Data Import Manager
Page 3
, C. Utilize the 'Legacy Appointment Loader' with mapping of legacy status codes to Epic's internal codes
D. Manually re-enter all historical appointments to ensure accuracy
Answer: C
Rationale: Epic's Legacy Appointment Loader is specifically designed for importing historical scheduling
data and includes code mapping functionality. Option A is for duplicate patients; option B may bypass
integrity checks; option D is impractical.
11. In the context of Epic's end-user configuration for clinical workflows, which of the following
best describes the relationship between SmartForms and SmartLinks, and how they interact to
enforce data integrity across a multi-phase clinical pathway?
A. SmartForms are static templates that capture discrete data, while SmartLinks dynamically link form fields to
external databases to auto-populate values without user intervention.
B. SmartForms use SmartLinks to pull data from the patient chart and clinical decision support rules, but
SmartLinks cannot be used to write data back to the chart; they only display read-only values.
C. SmartForms rely on SmartLinks to inject computed values or chart data into form fields, and SmartLinks can
be configured to both read from and write to the patient chart, enabling bidirectional data flow within a single
form.
D. SmartForms and SmartLinks are independent tools: SmartForms control form layout, while SmartLinks
manage report generation; they do not directly integrate.
Answer: C
Rationale: SmartForms are designed to capture structured data, and SmartLinks are the mechanism that
allows those forms to interface with the chart. SmartLinks can be set to read data into the form and,
when properly configured, to write form data back to discrete chart fields, thus ensuring data integrity
across a clinical pathway. Option A is incorrect because SmartLinks are not limited to external
databases; they work within the Epic chart. Option B is incorrect because SmartLinks can write data.
Option D is incorrect because they are integrated tools.
12. When configuring Epic's reporting workbench for a population health dashboard, a builder
needs to filter a report to include only patients with a specific combination of diagnoses and
medication orders that occurred within overlapping time windows. Which type of filter logic and
record linkage would be most appropriate to ensure accurate patient counts without
double-counting?
A. Use a single 'Encounter Diagnosis' filter with a date range and a separate 'Medication Order' filter; accept the
default logical AND between record types.
B. Use a 'Patient Record' filter with sub-filters for diagnosis and medication, and set the linkage to 'Patient' level
to combine criteria across any encounter.
C. Use a 'Cross-Encounter' filter that links diagnoses from one encounter to medications from a different
encounter using a common provider ID.
D. Use a 'Record Type' filter for 'Diagnosis' and 'Medication' separately, then manually export and merge in a
spreadsheet to avoid system limitations.
Answer: B
Rationale: For population health dashboards, filtering at the patient level (rather than encounter level)
ensures that patients meeting any combination of criteria across encounters are counted once. Option B
correctly uses patient-level linkage with sub-filters, avoiding double-counting. Option A may
double-count if a patient has multiple encounters. Option C is incorrect because cross-encounter linkage
Page 4
