TL;DR
- Grand Central is Epic’s patient flow and capacity application: a capacity command center, bed planning, a transfer center, and transport and environmental services work handled on Epic’s Rover app.
- Hospitals often staff it together with Prelude, Epic’s registration application; job titles such as “Grand Central/Prelude analyst” are common.
- Outside systems get admission, discharge and transfer events as HL7 v2 ADT messages through the hospital’s interface engine, or read encounters and locations through Epic’s FHIR APIs.
- The CMS e-notification rule (42 CFR 482.24(d)) requires hospitals to notify post-acute providers and primary care practitioners at registration, admission, discharge and transfer.
If you’re building a transport, capacity, transfer or care-transition tool for hospitals that run Epic, someone on the hospital side will eventually say “that comes from Grand Central.” This guide explains what Grand Central is, where its data actually leaves Epic, and what your team needs to settle before connecting to it.
What Is Grand Central in Epic?
Grand Central is Epic’s application for tracking and managing patient flow and capacity. Epic describes it as a way to “make better use of beds and clinical staff,” and lists these pieces (Epic, Hospital Patient Flow, checked October 2026):
- Capacity Command Center: real-time capacity, performance goals and open beds across hospitals.
- Predictive analytics: forecasts such as length of stay, expected ED admissions and the next day’s projected census.
- Transfer Center: coordinates moves between facilities; providers at other organizations can start transfer requests through Epic’s community portal.
- Bed planning: bed planners work open requests and spot bottlenecks.
- Transport: requests are assigned by proximity and priority, and transporters work from Epic’s Rover mobile app.
- Environmental services: cleaning is flagged from isolation information in the chart and assigned by skills and priority, also on Rover.
Epic’s page also reports a customer result: Parkview Health cut bed turnaround by 7 minutes per bed after connecting housekeeping and clinicians through Rover. Grand Central is one of many Epic modules; this is where staff manage where a patient goes next and how fast the bed behind them is ready.
Grand Central and Prelude: Who Owns Which Step
Grand Central and Prelude sit next to each other in a patient’s stay, which is why hospitals often hire for them together; postings such as Montefiore’s “Application Analyst, Epic Grand Central/Prelude” are common (Montefiore).
- Prelude registers the patient: demographics, insurance and the encounter itself.
- Grand Central takes it from there: placement, bed assignment, transfers, transport and cleaning.
- Cadence handles scheduled visits, which is where many outpatient encounters start.
For an outside tool, each step can be the trigger you care about. A transport tool cares about a transfer; a post-acute referral tool cares about a discharge; a capacity dashboard cares about all of them.
How ADT Events Reach Outside Systems
ADT stands for admission, discharge and transfer. When a patient is admitted, moved or discharged, the hospital’s systems send HL7 v2 ADT messages, each with a trigger event that says what happened:
| Trigger event | What happened | Tools that commonly care |
|---|---|---|
| A01 | Inpatient admission | Care management, capacity |
| A02 | Transfer to another unit or bed | Transport, capacity |
| A03 | Discharge | Post-acute referral, care transitions |
| A04 | Patient registered (outpatient or ED) | ED tools, notifications |
| A08 | Patient information updated | Any system keeping a patient record in sync |
| A11, A12, A13 | Cancel admission, cancel transfer, cancel discharge | Any tool that acted on the original event (transport tools especially) |
| A14, A15, A16 | Pending admission, pending transfer, pending discharge | Capacity and transport planning |
Our guide to HL7 trigger events covers the full list. Handle the cancels: a tool that dispatched transport on a transfer has to undo it when an A12 arrives. Outside systems usually receive these as a feed set up by the hospital’s interface team. Epic-side interfaces are built in Epic Bridges, and many hospitals route outside connections through their own enterprise interface engine, so your connection usually lands there. The hospital decides which events, which units and which facilities you receive, and how acknowledgments and retries work.
Apps can also read the current state rather than wait for messages. Epic’s FHIR R4 capability statement lists Encounter and Location with read and search support (Epic sandbox metadata, August 2026 release, checked October 2026). The patient’s current place sits on the Encounter (its location entries); the Location resource describes the place itself, such as a unit or bed. So an app with the right scopes can look up where a patient is on demand, within the hospital’s rate limits for polling. Many tools use both: the ADT feed signals a change, and the FHIR API fills in detail.
For the wider picture of HL7 v2 feeds, see our HL7 integration guide.
Need Better Epic Patient Flow Integration?
What ADT and FHIR Don’t Give You
Patient events are only part of what a transport or capacity tool wants. The rest of Grand Central’s working data, such as bed cleaning status, transport requests and environmental services tasks, isn’t something you can assume you’ll receive:
- Bed status: HL7 v2 does define a bed status update (trigger event A20, with an NPU segment) (HL7 v2 event table), but whether a hospital sends bed status outside Epic depends on the interfaces it builds. Ask for it by name.
- Transport and cleaning tasks: Epic’s FHIR capability statement lists a Task resource with read, search and update, but it doesn’t say which kinds of tasks are exposed. Confirm in Epic’s API documentation and with the hospital whether transport or cleaning work is among them before you design around it.
- Writing back: Encounter and Location are read and search only in Epic’s capability statement, so an outside app can’t record a patient’s move through them. If your tool needs to send something back, such as “transport complete”, agree the route with the hospital’s Epic team up front.
Scope all three with the hospital before you design the tool.
What the CMS Rule Requires (42 CFR 482.24(d))
The CMS Conditions of Participation add a reason hospitals send these events outward. Under 42 CFR 482.24(d), a hospital whose electronic records system conforms to the content exchange standard at 45 CFR 170.205(d)(2) (HL7 version 2.5.1) must show that its notification capacity is fully operational and that it sends patient event notifications:
- at registration in the emergency department,
- at admission to inpatient services, and
- immediately before, or at, discharge or transfer from the ED or inpatient services.
The notifications go, directly or through an intermediary, to all applicable post-acute care providers and suppliers and to the patient’s established primary care practitioner or group, or another practitioner the patient names, as a reasonable effort. They carry at least the patient’s name, the treating practitioner and the sending institution, and they’re sent only as far as federal and state law and the patient’s privacy preferences allow.
For a digital-health team, this rule is often why a hospital already has an ADT feed going to outside parties. The recipients are providers, so a vendor’s tool receives these notifications on a provider’s behalf, as its intermediary under a business associate agreement.
Building a Tool Around Grand Central
Transport, capacity, transfer and care-transition tools consume Grand Central’s events and Epic’s encounter data. They don’t change Grand Central itself; that configuration belongs to the hospital’s Epic team.
We built the Epic integration for a patient-logistics platform that coordinates hospital transport and care transitions, using Epic’s FHIR APIs, HL7 and OAuth2. Service-request time dropped from 15-20 minutes to under 5, a 70% cut. Alongside the Epic connection, we rebuilt how service requests are created and dispatched in the platform.
There are two ways to work with us:
- Mindbowser builds it: We build integrations and apps around Epic for digital-health products, using FHIR and HL7. See our Epic integration work.
- You run ConnectHealth: ConnectHealth is our EHR integration product. It can send and receive HL7 messages directly, with no middleware, and every message is acknowledged (ACK/NACK) and tracked end to end. ConnectHealth doesn’t remove vendor registration or the hospital’s approval chain.
If your tool also needs records from other organizations, Epic’s Care Everywhere is the exchange route to understand, and for care coordination across settings, see our guide to Epic Compass Rose.
What to Settle Before You Connect to Patient-Flow Data
Settle these with the hospital before any build starts:
- The event list: Which ADT events (including cancels and pending events), for which units and facilities, and whether you also need FHIR reads or bed status.
- Location and bed codes: Get the hospital’s department, room and bed identifiers and map them to your tool’s own locations; this mapping is easy to underestimate.
- Identifiers: Which patient and encounter identifiers arrive in each message, and which one your tool keys on.
- Connectivity and access: How the feed reaches you (for example HL7 over a VPN), and for FHIR, your app’s registration with Epic and its activation at each hospital.
- Agreements: The business associate agreement, and the purpose you receive the data for (treatment, care coordination), including how the hospital applies patients’ privacy preferences.
- Testing and delivery: A nonproduction feed to test admissions, transfers, discharges and cancels, plus how acknowledgments, retries and duplicates are handled on both sides.
Write those six down with the hospital’s interface team before any build starts.
Where to go next
- Have us build it: Epic integration
- Run it yourself: ConnectHealth
- Learn the messages: HL7 trigger events
- Talk to us: Start a Conversation








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 


















