Epic BPA (Best Practice Advisory) & EHR Clinical Decision Support: Architecture, CDS Hooks, and Vendor Comparison

An Epic BPA (Best Practice Advisory—increasingly termed an OurPractice Advisory [OPA] in newer Epic Systems releases) is the primary rule-based clinical decision support (CDS) mechanism in the Epic electronic health record (EHR). Evaluated in real time against patient data in the Chronicles database, a BPA alerts clinicians to care gaps, drug-disease contraindications, sepsis deterioration scores, or clinical trial eligibility—either as an interruptive modal pop-up or a non-interruptive banner—and provides one-click actionable orders, SmartSets, or acknowledgement reasons.

What Is a BPA in Epic and How Does Its Architecture Work?

In Epic’s Chronicles hierarchy, a Best Practice Advisory separates its clinical logic from its user-interface display so that informatics builders can reuse criteria across multiple alerts and quality registries:

• Criteria Records (LGL) and Rule Records (CER): The underlying logical conditions of an Epic BPA are built using LGL (criteria) and CER (rule) master file records. These records evaluate discrete patient properties—such as active ICD-10-CM problem list diagnoses, LOINC lab values, medication orders, age, or predictive model scores—using Boolean operators (AND, OR, NOT) and lookback time windows.
• Base Records (LGL): The BPA Base record defines what the clinician sees and what actions they can take when all linked criteria evaluate to true—including the advisory display text, clinical reference links, pre-selected single orders or SmartSets/Order Sets, and required override/acknowledgement buttons (e.g., “Contraindicated,” “Patient Refused,” “Will Reassess in 2 Hours”).
• Trigger Actions vs. Passive Display: Builders configure precisely when the EHR evaluates and displays the advisory. Interruptive BPAs fire on specific workflow triggers—such as Open Patient Chart, Enter Order, Sign Orders, or Medication Reconciliation—halting workflow until addressed. Non-interruptive BPAs appear passively in the patient Storyboard, Visit Navigator (Plan/Wrap-Up sections), or Health Maintenance activity without blocking charting.
• Lockout Times and Role Restrictions: To mitigate alert fatigue, BPA records support user-level and department-level filters (so a nursing screening BPA does not fire for an attending surgeon) as well as snooze/lockout timers after an acknowledgement reason is recorded.

Comparing EHR Clinical Decision Support Systems: Epic vs. Cerner Discern vs. MEDITECH vs. Allscripts

While health systems use the term “BPA” specifically for Epic, other major enterprise EHRs implement equivalent native rules engines alongside standardized HL7 interoperability hooks:

EHR Platform	Native CDS Engine & Rule Format	Execution Modes	External Interoperability Standards
Epic Systems	Best Practice Advisories (BPAs) / OurPractice Advisories (OPAs) built on Chronicles LGL criteria and CER rules	Interruptive modal pop-ups, passive Storyboard hover banners, Navigator sections, and In Basket messages	HL7 CDS Hooks (patient-view, order-select, order-sign), SMART on FHIR launch (e.g., MDCalc), and MCG Care Guidelines
Oracle Health (Cerner)	Cerner Discern Expert (Event Knowledge Server [EKS] using Evoke-Logic-Action modules and Cerner Command Language [CCL])	Synchronous Discern alerts, asynchronous chart surveillance, Dynamic Worklists, and PowerPlan suggestions	HL7 CDS Hooks, FHIR R4 operations, and Arden Syntax Medical Logic Modules (MLMs)
MEDITECH Expanse	Expanse Clinical Decision Support & Surveillance rules integrated with Quality & Surveillance registries	Real-time order-entry conflict checks, sepsis/deterioration surveillance boards, and care protocol prompts	SMART on FHIR app launch, HL7 CDS Hooks, and USCDI FHIR R4 APIs
Veradigm / Allscripts (Altera Sunrise)	Medical Logic Modules (MLMs) (Arden Syntax in Sunrise) and CareGuides / clinical quality prompts	Order-entry clinical checking, CareGuide problem-driven order templates, and ambulatory care gap reminders	Arden Syntax standard, HL7 CDS Hooks, and FHIR R4 API integration

Standards and Regulatory Requirements Governing EHR Clinical Decision Support

• ONC / ASTP 45 CFR § 170.315(b)(11) Decision Support Interventions (DSI): Under the HTI-1 Final Rule, certified EHR modules (including Epic and Oracle Health) must support both evidence-based DSIs and predictive AI/ML DSIs, exposing standardized “source attribute” transparency metadata (how the rule or model was developed, validated, and tested for fairness) and enabling institutional governance over intervention risks.
• HL7 CDS Hooks Specification: Rather than hard-coding every rule natively inside Chronicles or Cerner Discern, HL7 CDS Hooks allows the EHR to send a lightweight JSON POST request (containing the hook context and prefetched FHIR resources) to an external CDS service at workflow moments like patient-view or order-select, rendering the returned CDS Cards directly inside the native BPA or Discern alert UI.
• eCQM and Clinical Trial Recruitment Alignment: Hospitals frequently align BPA logic with hospital eCQM reporting denominators (such as VTE prophylaxis or stroke antithrombotic therapy) and use silent or research-coordinator-routed BPAs to flag patients who meet inclusion/exclusion criteria for active clinical trials.

Preventing Alert Fatigue: The Five Rights of CDS Governance

Unchecked proliferation of interruptive BPAs leads to clinician alert fatigue, where override rates regularly exceed 80–90%. Clinical informatics committees apply the AHRQ Five Rights of Clinical Decision Support before activating any new advisory:

1. The Right Information: Evidence-based, concise clinical guidance with a direct link to the primary guideline or source attribute.
2. The Right Person: Targeted strictly to the clinical role (physician, pharmacist, bedside RN, or research coordinator) authorized to execute the recommended action.
3. The Right Intervention Format: Reserving interruptive pop-ups for high-severity, time-critical safety hazards while shifting routine preventive care and quality gaps to non-interruptive Storyboard indicators or order sets.
4. The Right Channel: Delivering the prompt inside the native EHR workflow (or mobile Haiku/Canto push only when clinically urgent).
5. The Right Point in Workflow: Firing at the exact decision moment (such as order-select or order-sign) rather than on initial chart open before the clinician has examined the patient.

Frequently Asked Questions

What is a bpa in epic?

A BPA (Best Practice Advisory—also called an OurPractice Advisory in recent Epic versions) is an automated clinical decision support alert in the Epic EHR that evaluates patient chart data against Chronicles criteria (LGL) and rule (CER) records. When triggered, it presents clinicians with clinical guidance, one-click orders or SmartSets, or clinical trial eligibility notifications either as an interruptive pop-up or a passive Storyboard/Navigator banner.