1. Procedure and Procedure Category Configuration: EAP/EDP hierarchy and
precedence rules; Procedure record types (Order, Charge, Referral, Activity);
Building Block concepts; Result Components; Procedure Category linkage for
shared settings; Record purpose and orderable configuration.
2. Order Composer Configuration (OCC): Display context versus Summary
context; Controlled versus Editable field status; OCC hierarchy fallback to
System Definitions (LSD); Priority buttons and quantity quick-select
configuration; Summary sentence generation.
3. SmartTools (SmartSets, SmartGroups, SmartTexts, SmartPhrases): SmartSet
Base criteria and restriction logic; BPA Criteria record linkage for conditional
section display; SmartGroup panel type restrictions (medication versus order);
SmartList (ELG) for documentation dropdowns; SmartPhrase versus SmartText
scope.
4. Preference Lists and User Personalization: Ordering Mode requirements for
Preference List Editor; Section creation prerequisites; Department-level
availability via Profile linkage; Override detail visibility scope; Preference List
Composer versus Editor distinctions.
5. Patient Registration, Scheduling, and Intake Workflows: Recurring Unavailable
blocks versus template swaps; Deceased patient scheduling hard stops;
Scheduling Security record scope; Slot release after cancellation (Remove
, Hold); Master Benefit Order (MBO) billing hierarchy; Department Master File
required fields.
6. Documentation, Flowsheets, and Navigator Configuration: Navigator
Template/Topic/Section hierarchy; Extension (LPP) records for interactive
workflows; Workflow Engine Rule (LOR) for conditional navigator display;
Flowsheet row configuration; Synopsis and Report configuration.
7. In Basket Management and Results Routing: Pool versus Workqueue
configuration; Message routing rules; Results routing to providers; In Basket
security and delegation; Workqueue escalation and filtering.
8. Immunizations, Referrals, and Therapy Plans: Historical immunization
documentation (Single Historical Immunization versus Immunization Activity);
LIM record linkage for ordering-administering workflow; Referral workflow
configuration; Therapy Plan build and episodic versus longitudinal tracking.
9. MyChart, Patient Engagement, and Population Health: MyChart activation and
proxy access; Patient portal configuration; Registry and population health tools;
Care Everywhere and interoperability basics.
10. Security, Billing, and Regulatory Compliance: User security templates and
access scope; Billing and charge capture configuration; Regulatory compliance
(meaningful use, HIPAA); Reporting tools (SliceDice) for ad-hoc queries.
,AMB400 (EpicCare Ambulatory Administration)
certification Exam
250 Detailed Multiple-Choice Questions with Answers
and Rationales
1. Which record type serves as the foundational building block for all procedure
configuration within the EpicCare Ambulatory module and defines core clinical
and administrative attributes?
A. EDP (Epic Department Procedure)
B. EAP (Epic Ambulatory Procedure)
C. EDO (Epic Department Order)
D. ECG (Epic Code Group)
Answer: B
Rationale: The EAP (Epic Ambulatory Procedure) master file record establishes
the core clinical and administrative attributes of a procedure. EDP records inherit
from the foundational EAP and provide department-specific overrides, making the
EAP the primary configuration record . 8 12
2. In the EAP and EDP procedure hierarchy, which configuration level takes
precedence when settings conflict for a procedure ordered within a specific
, department?
A. EAP settings always override EDP settings in all circumstances.
B. EDP settings override EAP settings for that specific department.
C. The most recently modified record always wins regardless of level.
D. Settings are determined solely by the user's security class assignment.
Answer: B
Rationale: The Epic procedure hierarchy follows a "most specific overrides most
general" model. The EAP establishes system-wide defaults, while the EDP allows
department-specific customization. When a conflict exists, the department-level
EDP setting takes precedence for encounters in that department . 1 8
3. A builder needs the exact same screening question to appear automatically for
every diagnostic imaging procedure within a service line. What is the most
efficient configuration approach?
A. Link the question to each EAP procedure record individually.
B. Link the question at the Procedure Category (EDP) level for those imaging
tests.
C. Create a separate SmartPhrase containing the question for each procedure.
D. Add the question to every single Order Composer Configuration record.
Answer: B
Rationale: Linking a question at the procedure category (EDP) level ensures every
precedence rules; Procedure record types (Order, Charge, Referral, Activity);
Building Block concepts; Result Components; Procedure Category linkage for
shared settings; Record purpose and orderable configuration.
2. Order Composer Configuration (OCC): Display context versus Summary
context; Controlled versus Editable field status; OCC hierarchy fallback to
System Definitions (LSD); Priority buttons and quantity quick-select
configuration; Summary sentence generation.
3. SmartTools (SmartSets, SmartGroups, SmartTexts, SmartPhrases): SmartSet
Base criteria and restriction logic; BPA Criteria record linkage for conditional
section display; SmartGroup panel type restrictions (medication versus order);
SmartList (ELG) for documentation dropdowns; SmartPhrase versus SmartText
scope.
4. Preference Lists and User Personalization: Ordering Mode requirements for
Preference List Editor; Section creation prerequisites; Department-level
availability via Profile linkage; Override detail visibility scope; Preference List
Composer versus Editor distinctions.
5. Patient Registration, Scheduling, and Intake Workflows: Recurring Unavailable
blocks versus template swaps; Deceased patient scheduling hard stops;
Scheduling Security record scope; Slot release after cancellation (Remove
, Hold); Master Benefit Order (MBO) billing hierarchy; Department Master File
required fields.
6. Documentation, Flowsheets, and Navigator Configuration: Navigator
Template/Topic/Section hierarchy; Extension (LPP) records for interactive
workflows; Workflow Engine Rule (LOR) for conditional navigator display;
Flowsheet row configuration; Synopsis and Report configuration.
7. In Basket Management and Results Routing: Pool versus Workqueue
configuration; Message routing rules; Results routing to providers; In Basket
security and delegation; Workqueue escalation and filtering.
8. Immunizations, Referrals, and Therapy Plans: Historical immunization
documentation (Single Historical Immunization versus Immunization Activity);
LIM record linkage for ordering-administering workflow; Referral workflow
configuration; Therapy Plan build and episodic versus longitudinal tracking.
9. MyChart, Patient Engagement, and Population Health: MyChart activation and
proxy access; Patient portal configuration; Registry and population health tools;
Care Everywhere and interoperability basics.
10. Security, Billing, and Regulatory Compliance: User security templates and
access scope; Billing and charge capture configuration; Regulatory compliance
(meaningful use, HIPAA); Reporting tools (SliceDice) for ad-hoc queries.
,AMB400 (EpicCare Ambulatory Administration)
certification Exam
250 Detailed Multiple-Choice Questions with Answers
and Rationales
1. Which record type serves as the foundational building block for all procedure
configuration within the EpicCare Ambulatory module and defines core clinical
and administrative attributes?
A. EDP (Epic Department Procedure)
B. EAP (Epic Ambulatory Procedure)
C. EDO (Epic Department Order)
D. ECG (Epic Code Group)
Answer: B
Rationale: The EAP (Epic Ambulatory Procedure) master file record establishes
the core clinical and administrative attributes of a procedure. EDP records inherit
from the foundational EAP and provide department-specific overrides, making the
EAP the primary configuration record . 8 12
2. In the EAP and EDP procedure hierarchy, which configuration level takes
precedence when settings conflict for a procedure ordered within a specific
, department?
A. EAP settings always override EDP settings in all circumstances.
B. EDP settings override EAP settings for that specific department.
C. The most recently modified record always wins regardless of level.
D. Settings are determined solely by the user's security class assignment.
Answer: B
Rationale: The Epic procedure hierarchy follows a "most specific overrides most
general" model. The EAP establishes system-wide defaults, while the EDP allows
department-specific customization. When a conflict exists, the department-level
EDP setting takes precedence for encounters in that department . 1 8
3. A builder needs the exact same screening question to appear automatically for
every diagnostic imaging procedure within a service line. What is the most
efficient configuration approach?
A. Link the question to each EAP procedure record individually.
B. Link the question at the Procedure Category (EDP) level for those imaging
tests.
C. Create a separate SmartPhrase containing the question for each procedure.
D. Add the question to every single Order Composer Configuration record.
Answer: B
Rationale: Linking a question at the procedure category (EDP) level ensures every
