ADT and the Patient Lifecycle (A01 to A08 and Merges)

Why ADT is the heartbeat of an interface

Of all v2 message types, ADT — Admit, Discharge, Transfer — is the one nearly every system subscribes to. It announces the events that define a patient’s presence in a facility, and dozens of downstream systems (lab, pharmacy, radiology, billing) depend on those announcements to know who a patient is and where they are. A single ADT^A01 message recurs throughout this course because it is the canonical example, but ADT is a large family: one shared message structure selected by many different trigger events ¹.

The core lifecycle events

The trigger event in MSH-9 (for example ADT^A01) names what happened in the real world. The events that carry the most operational weight are:

Event	Meaning	Typical effect downstream
A01	Admit / visit notification	Create the encounter; open the patient for orders.
A02	Transfer	Update patient location (bed, unit).
A03	Discharge	Close the encounter; trigger billing.
A04	Register (outpatient)	Create a non-inpatient encounter.
A05	Pre-admit	Establish the patient/encounter ahead of arrival.
A08	Update patient information	Correct or enrich demographics on an existing patient.

A patient typically flows A05 → A01 → A02 → … → A03, with A08 updates layered in whenever demographics change. Because every system listens, an A08 that corrects a misspelled name or a wrong date of birth propagates the fix everywhere at once ².

Corrections, cancellations, and merges

Real admitting is messy, so ADT includes events for undoing and reconciling:

• Cancellations reverse a mistaken event — A11 cancels an admit, A13 cancels a discharge. They exist because you cannot simply “unsend” a message; the correction must itself be an explicit event other systems can act on.
• Merges (for example A40, merge patient identifier list) reconcile the common situation where one real patient was registered as two. A merge tells every downstream system to combine the records — one of the highest-risk operations in healthcare integration, because a bad merge mixes two people’s data ².

The mental model to carry forward

ADT is event-driven state synchronization: one facility’s admitting system is the source of truth for who is here and where, and ADT messages keep every other system’s copy of that truth current. The next lesson opens up the segments — PID, PV1, NK1 — that actually carry the identity and visit detail these events deliver.