^A14
ADT^A14 — Pending Admit
Sent to notify downstream systems that a patient admission is expected in the near future. This is an advisory notification only — it does not create an encounter record. It alerts bed management, nursing, and ancillary systems to prepare for the incoming patient.
When Is This Sent?
When a care manager or bed coordinator identifies that a patient will be admitted and wants to notify bed management and downstream systems in advance. The actual admission (A01) follows separately.
Real-World Usage
A14 is used in facilities with active bed prediction and capacity management workflows. It allows bed management teams to proactively assign beds and prepare rooms before the patient physically arrives or the formal admission is entered. Not all ADT systems generate A14 — it is more common in facilities using dedicated capacity management tools.
Message Structure
Segment names link to their field-level reference pages.
| # | Segment | Purpose in this message | Req | Repeat |
|---|---|---|---|---|
| 1 | MSH | Message header with ADT^A14 in MSH.9 | R | — |
| 2 | EVN | Event type with A14 trigger | R | — |
| 3 | PID | Patient demographics | R | — |
| 4 | PV1 | Visit information with expected admission details and PV1.2=P (preadmit) or I | R | — |
| 5 | PD1 | Additional patient demographics | O | — |
| 6 | NK1 | Next of kin information | O | Yes |
| 7 | PV2 | Expected admission date/time in PV2.8 | O | — |
| 8 | AL1 | Known allergies | O | Yes |
| 9 | DG1 | Anticipated admitting diagnosis | O | Yes |
| 10 | IN1 | Insurance information | O | Yes |
Example Message
Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.
1MSH||^~\&|EPIC|HOSPITAL_A|MIRTH_PROD|BED_MGT|20260312070000||ADT^A14^ADT_A14|MSG00065|P|2.5.1 2EVN||A14|20260312070000 3PID||1||456789^^^HOSP_A^MR||Williams^Carol^A||19550714|F 4PV1||1|P|5A^510^2^^^HOSP_A||||6789^Carter^Dr.^David|||MED||||ADM||||||PA||||||||||||||||||||||||||20260312090000
Troubleshooting Scenarios
A14 followed by A01 creates a duplicate encounter
Cause
Downstream systems are treating A14 as an actual admit (A01) and creating encounter records. When A01 arrives, a second encounter is created.
Fix
Ensure downstream systems are configured to treat A14 as a notification only — no encounter should be created. Only A01 or A05 should trigger encounter creation. If the downstream system cannot distinguish, filter A14 events out of that system's subscription.
Common Confusions
ADT^A14 (Pending Admit) vs ADT^A05 (Pre-Admit). A14 is advisory — it creates no encounter record. A05 creates an actual pre-admission record in downstream systems. Use A14 for capacity planning notifications; use A05 when a full pre-registration workflow is required.
Related Message Types
Segment Reference
Paste this message into our viewer
Interactive HL7 parser. Decodes every field, validates structure, highlights errors. Free, no signup.
Open HL7 Message Viewer →Need mapping templates?
The HL7 Integration Toolkit includes field mapping worksheets and interface spec templates for every major HL7 message type including ADT^A14.
View HL7 Integration Toolkit →