Healthcare IT
HL7 ADT Message Guide (2026): Segments, Events & Mapping Basics
A practical HL7 ADT guide for 2026 — message structure, common admit/update events, segments that matter, and mapping habits for real interfaces.
ADT is the heartbeat of hospital interoperability. If you can read an ADT message, explain the event type, and map PID/PV1 safely, you are already ahead of slide-only learners. This guide focuses on the structure and habits used in real HL7 work.
New to HL7 overall? Start with /blog/what-is-hl7. Planning a course? See /blog/hl7-training-india-2026.
What ADT messages do in hospitals
ADT events tell downstream systems that a patient was admitted, transferred, discharged, or that demographics changed. LIS, RIS, billing, and ancillary apps rely on these feeds to keep the patient record consistent.
Common ADT trigger events
- A01 — Admit / visit notification
- A02 — Transfer a patient
- A03 — Discharge a patient
- A04 — Register a patient
- A08 — Update patient information
- A11 — Cancel admit (know that cancels exist)
Segments beginners must know
- MSH — sending/receiving apps, message type, control ID, timestamp
- EVN — event type and recorded time
- PID — patient identifiers and demographics
- PV1 — visit/encounter class, location, attending doctor patterns
- Optional: NK1 (next of kin), OBX (observations), insurance segments
ACK behavior that trips people up
Interfaces fail quietly when ACKs are ignored. Learn what success vs application error looks like for your engine, and never assume “sent” means “accepted.” Document retry and quarantine rules before go-live.
Mapping tips that keep data safe
- Map identifiers carefully — MRN vs visit number confusion causes duplicates
- Preserve clinical meaning; do not invent fields to “make it work”
- Test updates (A08) separately from admits (A01)
- Keep a sample library of good and bad messages for regression tests
Practice path with Shaivee Tech
Live online HL7 training at Shaivee Tech includes ADT message labs and interface troubleshooting habits. Start at /learn/hl7-training or register at /go/hl7-training. Pair with /blog/mirth-connect-for-beginners if you will use an interface engine.
Frequently Asked Questions
What is an HL7 ADT message?
ADT (Admit, Discharge, Transfer) messages communicate patient demographic and visit events between hospital systems — for example admit (A01) or patient information update (A08).
Which ADT segments matter most for beginners?
Start with MSH (message header), EVN (event), PID (patient), and PV1 (visit). Many interfaces also use NK1, OBX, or insurance segments depending on the vendor.
How do ADT messages relate to FHIR?
ADT events often map conceptually to FHIR resources like Patient and Encounter. Hybrid estates use both. See /blog/hl7-vs-fhir-which-to-learn-first.
Where can I practice ADT mapping?
Use sample messages in a lab or interface engine. Shaivee Tech training covers ADT labs — /learn/hl7-training and /go/hl7-training.
Get practical IT insights
Occasional guides on HL7, FHIR, cloud, DevOps, and digital growth — no spam.