Skip to content
Contact Us

HL7 v2 Sample Messages

Every HL7 sample message below is a complete, annotated example you can use as a starting point for development and testing. Each sample HL7 message uses realistic clinical data with segment-by-segment explanations. Click any segment to explore its fields. Copy these into HL7 Workbench to parse and validate interactively.

An inpatient admission to the ICU:

ADT^A01 — Admit/Visit Notification
Header Patient Clinical Order/Result Financial

Key segments: MSH (header) → EVN (event) → PID (patient) → PV1 (visit) → NK1 (next of kin) → IN1 (insurance) → AL1 (allergy). See our ADT message reference for event type details.

A Comprehensive Metabolic Panel result:

ORU^R01 — Observation Result
Header Patient Clinical Order/Result Financial

Key segments: ORC (order common) → OBR (observation request) → OBX (individual results, repeating). All results are final (F) and normal (N). See our ORU message reference for result status codes.

A STAT Complete Blood Count order:

ORM^O01 — Lab Order
Header Patient Clinical Order/Result Financial

Key segments: ORC (new order NW) → OBR (CBC, STAT priority) → DG1 (diagnosis) → NTE (clinical note). See our ORM message reference for order lifecycle details.

A routine office visit appointment:

SIU^S12 — New Appointment
Header Patient Clinical Order/Result Financial

Key segments: SCH (scheduling activity) → RGS/AIS/AIP/AIL (resource group with service, personnel, and location). See our SIU message reference for event types.

MDM^T02 — Original Document Notification

Section titled “MDM^T02 — Original Document Notification”

A transcribed operative note:

MDM^T02 — Original Document Notification
Header Patient Clinical Order/Result Financial

Key segments: TXA (transcription information — document type, author, authentication status) → OBX (document content as formatted text). MDM^T02 signals an original document; T04 signals an addendum, T08 an update, and T11 a cancellation. See our MDM message reference for complete event type details.

The MSH-2 field (^~\&) defines the delimiter characters used throughout the message:

CharacterNamePurpose
^Component separatorSeparates components within a field
~Repetition separatorSeparates repeated values in a field
\Escape characterEscapes special characters in text
&Sub-component separatorSeparates sub-components
SequenceMeaning
\.br\Line break
\F\Field separator (literal |)
\S\Component separator (literal ^)
\T\Sub-component separator (literal &)
\R\Repetition separator (literal ~)
\E\Escape character (literal \)