Epic ASAP Emergency Department: ED Tracking Board, Triage Workflows, and Build Guide

Epic ASAP implementations fail most often not in build configuration but in requirements – teams collect ED workflow requirements from nurses and physicians without understanding how ASAP’s tracking board, triage acuity model, and disposition workflow translate into build objects. This article gives analysts, build specialists, and IT project leads the depth needed to configure Epic ASAP correctly across ED tracking board design, triage workflow build, order management, disposition, and go-live validation.

What Is Epic ASAP?

Epic ASAP (A System for the After-hours Practices) is Epic Systems’ emergency department module. It manages the complete ED patient encounter from arrival registration through triage, provider evaluation, orders, nursing documentation, and disposition. ASAP is purpose-built for the emergency department workflow – high volume, high acuity, time-critical, and operationally distinct from inpatient or ambulatory care.

The central feature of ASAP is the ED Tracking Board – a real-time view of every patient in the department showing location, acuity, care team assignment, outstanding orders, time in department, and disposition status. The tracking board is not just a dashboard. It is the primary workflow tool that nurses, physicians, charge nurses, and bed managers use to run the department. Getting the tracking board configuration wrong is the most visible failure in an ASAP implementation.

ASAP shares Epic’s clinical infrastructure. Orders placed in ASAP flow through the same CPOE framework used in inpatient settings. Nursing documentation uses Epic’s flowsheet engine. Results from the laboratory and radiology post directly to the patient record. Medications are verified through Willow. When a patient is admitted from the ED, the handoff to inpatient moves through a defined Epic workflow that transfers care team assignments, active orders, and documentation. The broader Epic module context is covered in the Epic EHR Learning Hub.

ED Tracking Board: Design and Configuration in Epic ASAP

The ED tracking board is a configurable grid where each row represents a patient and each column represents a data element – room location, acuity, provider, nurse, chief complaint, time in department, outstanding lab results, outstanding radiology reads, medication status, and disposition. The tracking board is configured in ASAP’s Tracking Board (TBD) master file. Build analysts define which columns appear, in what order, with what visual indicators, and which patient populations display on each board view.

Tracking Board Views and Patient Population Filters

Most EDs run multiple tracking board views simultaneously. The main ED board shows all patients currently in the department. A triage board shows patients waiting to be triaged. A results-pending board shows patients awaiting lab or imaging results. A ready-for-discharge board shows patients whose disposition has been ordered but who have not yet left. Each view filters the patient population by status, location zone, or care stage.

Build analysts configure patient population filters using ASAP’s Patient List Criteria rules. These filters use encounter status, department location, triage level, disposition status, and time-based criteria. A tracking board that shows too many patients overwhelms staff. A board with overly restrictive filters hides patients who need attention. The filter logic must be reviewed with charge nurses and nursing leadership – not just IT – before the build is locked.

Column Configuration and Visual Indicators

Each column on the tracking board is a configurable data element. Common columns include patient name (or alias for HIPAA compliance), room/bed number, ESI acuity level (color-coded 1-5), assigned provider, assigned nurse, chief complaint, arrival time, time in department (auto-calculated), lab result status (pending/resulted), radiology status (ordered/read), and current patient status (waiting/in room/admitted/discharged).

Visual indicators on the tracking board are configured as flags and alert icons that fire when conditions are met. A red clock icon when a patient has been in the department more than 4 hours. A lab results pending icon when critical lab values are outstanding. A bed request pending icon when an admit order has been placed but no inpatient bed has been assigned. These alerts are configured in ASAP’s tracking board column settings and must be validated against the actual clinical thresholds used by the department.

Zone Configuration and Bed Management Integration

Most EDs are divided into zones – acute care, fast track, pediatric, trauma bay, triage. Each zone has its own bed locations configured in Epic’s department and bed master files. The tracking board uses zone assignments to filter which patients appear on zone-specific board views. Zone configuration must match the physical ED layout exactly – a bed assigned to the wrong zone on the tracking board creates a patient tracking failure when the actual patient is in a different physical location.

Bed management integration connects ASAP to the hospital’s bed management system (Epic’s own bed management module or third-party tools like TeleTracking or Cerner). When an admit order is placed in ASAP, a bed request fires to bed management. The tracking board reflects bed assignment status in real time. Build analysts configure the bed request workflow and the interface between ASAP and the bed management system – if this interface is not tested end-to-end, ED boarding time data will be missing from the tracking board at go-live.

Triage Workflow Build and ESI Acuity in Epic ASAP

Triage in ASAP is a structured clinical workflow that starts when a patient arrives and ends when an acuity level is assigned and the patient is placed in the department. The triage workflow in ASAP is built as a sequence of documentation steps – arrival registration, chief complaint capture, vital signs, ESI level assignment, and room placement. Each step must be completed in the correct sequence and by the correct role (triage nurse, charge nurse, or provider depending on the department’s fast-track triage model).

ESI Triage Level Configuration

The Emergency Severity Index (ESI) is the five-level triage acuity scale used by the majority of US emergency departments. ESI 1 is immediate life threat requiring immediate resuscitative intervention. ESI 5 is a non-urgent complaint requiring minimal resources. ASAP builds the ESI scale directly into the triage flowsheet – the nurse selects the ESI level based on clinical assessment, and that selection drives the color coding on the tracking board, the room assignment priority, and the response time metric calculation.

Build analysts configure the ESI level choices in the triage flowsheet row. The ESI level assignment must match the organization’s adopted ESI version (ESI v4 is current as of 2026) and the clinical decision support rules that guide triage nurses in level assignment. ASAP does not automatically assign ESI levels based on vital signs – clinical algorithms can be configured as CDS alerts that prompt the nurse, but the level assignment itself is always a human clinical decision.

Chief Complaint Dictionary and Symptom Protocols

The chief complaint in ASAP is selected from a configured chief complaint dictionary. Each chief complaint can be linked to a symptom-based triage protocol that auto-launches additional documentation requirements – a chest pain chief complaint triggers a chest pain protocol that requires a 12-lead ECG timestamp, troponin order set availability, and a pain scale assessment. A stroke chief complaint triggers the stroke protocol and NIHSS (NIH Stroke Scale) documentation requirement.

Build analysts configure the chief complaint dictionary in ASAP’s Chief Complaint (CHF) master file. Each entry includes the display name, the protocol linkage, and whether the complaint triggers mandatory additional documentation. The chief complaint list must be reviewed by ED medical leadership – it should be comprehensive enough to cover the department’s actual case mix but not so long that nurses cannot find the right complaint efficiently.

Fast-Track and Provider-in-Triage Models

Many high-volume EDs use a provider-in-triage (PIT) or split-flow model where a provider evaluates low-acuity patients directly at triage, initiating orders before the patient is assigned a room. ASAP supports PIT workflows through a triage-based order entry configuration that allows orders to be placed from the triage encounter before room assignment. Build analysts must configure whether triage encounters can accept orders, and which order types are available at triage versus after room placement.

Fast-track workflow in ASAP routes low-acuity patients (ESI 4-5) to a separate fast-track zone with its own tracking board, bed pool, and nursing assignments. Fast-track configuration requires a separate department location in Epic’s department master, separate provider and nurse assignment workflows, and separate order set configurations tailored to common fast-track diagnoses (minor injuries, URI, UTI, skin complaints).

Order Management and CPOE in Epic ASAP

The ED is the highest-order-volume environment in most hospitals. Providers place labs, imaging, medications, procedures, and disposition orders in rapid succession, often for multiple patients simultaneously. ASAP’s CPOE implementation must balance safety validation (allergy checks, drug interactions, clinical decision support) with the speed demands of emergency care. Order sets are the primary mechanism for managing this balance.

ED Order Sets: Build Strategy

ED order sets are condition-specific bundles of orders that a provider can place with a single action – a chest pain order set that includes troponin, BNP, ECG, aspirin, and IV access orders. Order sets in ASAP are built in Epic’s Order Set (OST) master file, the same framework used across all Epic clinical modules. However, ED order sets have specific requirements: they must be fast to place, relevant to emergency presentations, and pre-populated with default values appropriate for the ED context.

Build analysts work with ED medical leadership to develop order sets for the department’s top 20-30 presenting conditions. Sepsis, chest pain, stroke, abdominal pain, pediatric fever, trauma, overdose, COPD exacerbation – each requires its own evidence-based order set reviewed against current clinical guidelines. Order set content changes as clinical evidence updates. Build analysts must establish a governance process for order set review and update before go-live, not after. Analysts with experience in Epic EHR Orders and CPOE workflows will recognize that ED order sets require the same governance rigor as inpatient order sets, with the additional constraint of speed.

Clinical Decision Support in the ED Context

Alert fatigue is a documented patient safety problem in emergency departments. A 2023 JAMA study documented that ED providers override more than 90% of CDS alerts in high-volume settings – not because the alerts are always wrong, but because the volume of low-value alerts conditions providers to click through without reading. ASAP’s CDS configuration for the ED must be more restrictive than inpatient settings. Every alert must have a clear clinical rationale for its presence.

Build analysts configure CDS alerts in collaboration with the ED medical director and pharmacy. High-value alerts – critical drug-allergy interactions, high-alert medication dosing thresholds, sepsis screening alerts – should be configured as hard stops or require a mandatory override reason. Low-value alerts that fire for routine clinical practice should be suppressed or converted to passive best practice advisories. The P&T committee must review and approve the ED CDS alert configuration before go-live.

Disposition Workflows: Admit, Transfer, and Discharge

Disposition is the decision point where the provider determines the patient’s next care destination – admission to inpatient, transfer to another facility, or discharge home. Each disposition path in ASAP has its own workflow with distinct documentation requirements, order transitions, and downstream system notifications. Getting disposition workflow configuration wrong creates patient flow bottlenecks and data gaps that affect both operations and CMS quality reporting.

Inpatient Admission from the ED

When a provider places an admit order in ASAP, the workflow triggers: a bed request to bed management, a notification to the accepting inpatient team, a review of active ED orders for transition to inpatient, and documentation handoff. Build analysts configure the admit order type, the bed request trigger, and the care team notification workflow. The admit order workflow must account for different admission types – observation, inpatient, direct ICU – each of which may route to different inpatient departments with different nursing workflows.

ED boarding is the period when an admitted patient remains in the ED while waiting for an inpatient bed. The ASAP tracking board should reflect boarding status clearly – a patient who is admitted-pending-bed has a different workflow state than a patient still being evaluated. Build analysts configure the boarding status indicator and the LOS calculations that distinguish active ED time from boarding time. This distinction matters for CMS quality metrics and Joint Commission boarding time reporting.

Transfer Workflow

Transfers from the ED to another facility require documentation of the accepting facility, the mode of transport, the clinical reason for transfer, and the transfer summary. EMTALA (Emergency Medical Treatment and Labor Act) mandates specific documentation requirements for any patient who is transferred from an emergency department. ASAP’s transfer workflow must include all EMTALA-required documentation fields, and build analysts must review the transfer workflow configuration with the hospital’s compliance and legal teams before go-live.

Discharge Workflow and Patient Instructions

Discharge from the ED includes clinical documentation (final diagnosis, disposition note), patient education materials, discharge instructions, prescription generation, and after-care follow-up scheduling. ASAP’s discharge workflow is configured as a discharge navigator – a structured checklist that ensures all required steps are completed before the patient leaves. Build analysts configure the discharge navigator checklist items, the required versus optional documentation elements, and the patient education material assignments by chief complaint or diagnosis.

ASAP Integrations: ADT, Lab, Radiology, and Pharmacy

ASAP generates patient movement events that drive ADT (Admit-Discharge-Transfer) messages to every downstream system connected to the hospital. When a patient is registered in the ED, an ADT A04 (register) message fires. When they are assigned a room, an ADT A02 (transfer) fires. When they are admitted to inpatient, an ADT A01 fires. When they are discharged, an ADT A03 fires. Each of these messages must trigger correctly and deliver to the receiving systems within defined latency thresholds.

Laboratory integration in the ED is time-critical in ways it is not in other settings. A sepsis workup in the ED needs lactate results within 30 minutes of order placement. An ECG interpretation needs to be available within minutes of the procedure. Build analysts must validate that the lab order-to-result interface between ASAP and the LIS is configured for the ED’s turnaround time expectations, and that critical value notifications fire to the correct provider immediately.

Radiology integration connects ASAP orders to the RIS and displays imaging results and radiologist reads directly on the tracking board. The read status column on the tracking board must update in real time when a radiologist finalizes a report. If the SIU or ORU interface that carries radiology results is not configured with the correct trigger events, tracking board result status lags behind actual read status – and providers are looking at the EMR for results rather than the tracking board.

Pharmacy integration in the ED requires that medication orders placed in ASAP route to the correct pharmacy dispensing queue – typically the ED satellite pharmacy or an automated dispensing cabinet (ADC). Build analysts configure the medication routing rules for the ED department, the ADC cabinet assignments for ED beds, and the controlled substance workflow requirements for the ED. The medication administration workflow in ASAP connects to nursing eMAR documentation – the EpicCare Inpatient ClinDoc guide covers the nursing documentation workflow that applies across both ASAP and inpatient settings.

HIPAA Privacy and ED Tracking Board Configuration

The ED tracking board is a visible display that multiple staff members view simultaneously. In many EDs, the tracking board is displayed on large monitors visible to anyone in the nursing station area. HIPAA’s Privacy Rule requires that patient information displayed in common areas be limited to the minimum necessary for treatment purposes. The HHS Office for Civil Rights has issued specific guidance that hospital patient tracking systems must be configured to limit disclosure of protected health information (PHI) to what is operationally necessary.

In ASAP, build analysts configure patient name display settings per tracking board. Options include full name display (appropriate for secure workstations with role-based access controls), initials only, room number only, or a system-assigned alias. The correct display configuration depends on the physical security of the tracking board location and the organization’s HIPAA privacy officer’s assessment. Build analysts should not make this determination unilaterally – the privacy officer must sign off on tracking board display configuration before go-live.

Sensitive patient types – behavioral health patients, VIP patients, patients under law enforcement custody – require additional tracking board configuration. Behavioral health patients may need their chief complaint masked on the tracking board even from ED staff not directly involved in their care. VIP patients may require a flagging system that alerts the charge nurse without displaying PHI to all board viewers. Build analysts configure these sensitivity settings with input from the privacy officer and the behavioral health and security departments.

ED Metrics, Throughput Reporting, and CMS Quality Measures

ASAP captures timestamps at every key ED workflow step. These timestamps drive the ED throughput metrics that hospital leadership and CMS use to evaluate ED performance. Build analysts must ensure that every timestamp is populated through the correct clinical workflow action – not through manual entry that can be inaccurate or retroactively modified.

Key ED Timestamps and CMS Reporting Requirements

CMS IQR (Inpatient Quality Reporting) and OQR (Outpatient Quality Reporting) programs require that timestamp data be submitted accurately and on time. ASAP’s reporting workbench reports must be validated before go-live to confirm that each timestamp populates through the correct clinical workflow action. If the door time is populated by registration rather than the patient’s physical arrival at the ED entrance, the door-to-provider metric will be artificially inflated for patients who walk in but have a registration delay. Build analysts must map each CMS metric to its source timestamp and validate the data flow end-to-end.

Testing and Validation Strategy for Epic ASAP

ASAP testing requires simulation of real ED operational conditions – high volume, time pressure, and concurrent multi-patient scenarios. Unit testing of individual build components (triage flowsheet, order sets, tracking board columns) is necessary but not sufficient. Integrated testing must simulate the complete ED patient journey from arrival through disposition across multiple simultaneous patients.

The tracking board must be tested with 20+ simultaneous test patients in different workflow stages – some in triage, some in rooms awaiting labs, some with critical results pending, some with admit orders placed. Only at that volume do tracking board configuration problems become visible. A column that works correctly for 5 patients may display incorrectly when 40 patients are on the board and sorting logic conflicts.

ASAP BAT (Business Acceptance Testing) must include ED nurses, charge nurses, and physicians – not just IT and build analysts. The tracking board review, triage flowsheet completion, and disposition workflow must be validated by the staff who will use them. Teams familiar with BAT vs UAT methodology understand that clinical staff sign-off on workflow function is the acceptance gate – not build team confirmation of configuration.

EMTALA documentation validation is a required testing step for the transfer workflow. Every EMTALA-required documentation field must be tested for completion enforcement. A test scenario where a transfer is attempted without completing all required EMTALA documentation must produce the correct system response – a block or mandatory warning, not a silent gap.

Go-Live Planning and Common ED Implementation Failures

ASAP go-live carries patient safety risk that other Epic module go-lives may not. The ED is a high-acuity, time-critical environment where workflow disruptions directly affect patient outcomes. Go-live timing, super-user deployment, and downtime procedure readiness are not optional risk mitigations. The Epic EHR Go-Live Support framework applies here with ED-specific additions: a physician champion in the command center, super-users on every shift for the first 30 days (not just 72 hours), and a paper downtime procedure for every ED workflow that has been practiced before go-live.

Roles, Certifications, and Career Path for ASAP Specialists

Authoritative References

• CMS – Hospital Compare and Outpatient Quality Reporting (OQR) Program Measure Specifications
• HL7 FHIR R4 – Encounter Resource: ED Visit and Emergency Encounter Data Model

Downloads: Epic ASAP Templates and Checklists