MajwareMAJWARE
ADT
^A14
ADT4 required / 6 optional segments

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.

#SegmentPurpose in this messageReqRepeat
1MSHMessage header with ADT^A14 in MSH.9R—
2EVNEvent type with A14 triggerR—
3PIDPatient demographicsR—
4PV1Visit information with expected admission details and PV1.2=P (preadmit) or IR—
5PD1Additional patient demographicsO—
6NK1Next of kin informationOYes
7PV2Expected admission date/time in PV2.8O—
8AL1Known allergiesOYes
9DG1Anticipated admitting diagnosisOYes
10IN1Insurance informationOYes

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 →

Moving to FHIR?

Convert HL7 v2 ADT, ORU and ORM messages to FHIR R4 resources in your browser, with per-field conversion notes. Free, no upload.

Open HL7 to FHIR Converter →
← Back to HL7 Message Types Reference