HL7 ORU, ORM, SIU & MDM Message Guide

Q: What is HL7 ORU?

HL7 ORU (Observation Result — Unsolicited, most commonly trigger event ORU^R01 ) is the standard HL7 Version 2 message type used by Laboratory Information Systems (LIS), radiology PACS/RIS, and bedside medical devices to transmit structured clinical observations, laboratory panels, and diagnostic reports to an Electronic Health Record (EHR) or public health registry.

Q: How do HL7 ORU, ORM, SIU, and MDM messages differ in hospital workflows?

While ADT messages manage patient movement, four clinical message families drive order-to-result and scheduling workflows: ORM^O01 (or OML / OMG ) transmits clinical orders from the EHR to ancillaries; ORU^R01 returns structured diagnostic and lab results in OBX segments; SIU ( S12–S15 ) synchronizes appointment bookings and cancellations; and MDM ( T02 / T04 ) transmits clinical narrative documents and transcription status updates.

Q: How are OBR and OBX segments structured inside an HL7 ORU^R01 message?

In an HL7 ORU^R01 message, each ordered battery or panel is represented by an OBR (Observation Request) header segment containing the placer/filler order numbers and LOINC panel code ( OBR-4 ), followed by one or more repeating OBX (Observation/Result) child segments carrying the value data type ( OBX-2 ), LOINC test identifier ( OBX-3 ), result value ( OBX-5 ), UCUM units ( OBX-6 ), reference range ( OBX-7 ), abnormal flag ( OBX-8 ), and result status ( OBX-11 ).

HL7 ORU (Observation Result — Unsolicited) is the primary message family in the HL7 Version 2 (v2) messaging standard used to transmit clinical laboratory results, vital signs, diagnostic imaging impressions, pathology reports, and physiological waveform measurements from ancillary diagnostic systems into an electronic health record (EHR) or clinical research repository. Alongside HL7 ORM (orders), HL7 SIU (scheduling), and HL7 MDM (clinical documents), ORU messages form the operational core of HL7 v2 clinical interfaces managed through integration engines such as Epic Bridges, Mirth Connect (NextGen Connect), and Rhapsody, and parsed using HL7 v2 parsers.

What Is HL7 ORU?

Defined in Chapter 7 of the HL7 v2.5.1 and v2.8 specifications, an ORU message—almost universally implemented via trigger event ORU^R01 (Unsolicited Transmission of an Observation Message)—is generated whenever a producing system (such as a reference laboratory, in-hospital Laboratory Information System [LIS], cardiology ECG cart, or automated vital-sign monitor) records or updates a clinical observation. The word “unsolicited” in ORU^R01 means the producing system pushes the result message to the receiving EHR integration endpoint as soon as the test reaches a reportable status (preliminary, final, or corrected) rather than waiting for a synchronous query.

In public health informatics, the HL7 v2.5.1 ORU^R01 profile is also codified by the Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT (ASTP/ONC) under 45 CFR § 170.315(f)(3) as the mandatory federal transport format for Electronic Laboratory Reporting (ELR) of reportable infectious diseases to state health departments.

HL7 ORU vs ORM vs SIU vs MDM: Clinical Message Families Compared

While Admission, Discharge, and Transfer (ADT) messages maintain patient demographics and bed census, clinical care delivery across hospital and ambulatory interfaces relies on four specialized message families:

HL7 v2 Message Family	Primary Trigger Events	Core Segments	Clinical & Research Workflow Role
HL7 ORU (Observation Result)	`ORU^R01` (Unsolicited observation), `ORU^R30` (Point-of-care)	`MSH, PID, PV1, ORC, OBR, OBX, NTE, SPM`	Delivers discrete LOINC-coded lab panels, microbiology cultures, radiology reports, and bedside device vitals into the EHR or EDC
HL7 ORM (General Order Message)	`ORM^O01` (replaced in v2.4+ by domain-specific `OML^O21` lab, `OMG^O19` general clinical, `OMP^O09` pharmacy)	`MSH, PID, PV1, ORC, OBR, DG1, OBX`	Transmits new (`NW`), canceled (`CA`), or modified (`XO`) diagnostic and procedure orders from the EHR to LIS/RIS/PACS
HL7 SIU (Scheduling Information Unsolicited)	`SIU^S12` (New appointment), `S13` (Rescheduled), `S14` (Modified), `S15` (Canceled), `S26` (No-show)	`MSH, SCH, PID, PV1, RGS, AIS, AIG, AIL, AIP`	Synchronizes outpatient clinic calendars, surgical block schedules, clinical trial visit windows, and digital patient intake platforms
HL7 MDM (Medical Document Management)	`MDM^T01` (Status notification), `MDM^T02` (Original document with content), `MDM^T08` (Edit document)	`MSH, EVN, PID, PV1, TXA, OBX`	Pushes dictated progress notes, operative reports, ambient AI scribe outputs, and Base64-encoded PDFs (using the `TXA` Transcription Document Header segment)

Anatomy of an HL7 ORU^R01 Message: PID, OBR, and OBX Hierarchy

An ORU^R01 message organizes clinical results into a three-tier repeating hierarchy—Patient (PID/PV1) → Order/Battery Header (ORC/OBR) → Individual Observation Result (OBX/NTE):

MSH|^~&|QUEST_LIS|QUEST|EPIC_BRIDGES|UNIV_HOSP|20261109143022||ORU^R01^ORU_R01|MSG99201|P|2.5.1
PID|1||9004412^^^UNIV_HOSP^MR||DOE^JANE^M||19740819|F
PV1|1|O|CARD_CLIN^^^UNIV_HOSP||||1234567890^PATEL^RAJESH^^^MD^^^^NPI
ORC|RE|ORD88210^EPIC|ACC55109^QUEST||CM
OBR|1|ORD88210^EPIC|ACC55109^QUEST|24323-8^Comprehensive Metabolic 2000 Panel^LN|||20261109101500|||||||||1234567890^PATEL^RAJESH^^^MD||||||20261109142900|||F
OBX|1|NM|2345-7^Glucose [Mass/volume] in Serum or Plasma^LN||118|mg/dL|70-99|H|||F|||20261109101500
OBX|2|NM|2823-3^Potassium [Moles/volume] in Serum or Plasma^LN||4.2|mmol/L|3.5-5.1|N|||F|||20261109101500
NTE|1|L|Fasting specimen verified prior to venipuncture.

Critical OBX Fields for Clinical Informatics & FHIR Mapping

OBX-2 (Value Type): Defines how the parser interprets OBX-5: NM (Numeric, e.g., 4.2), SN (Structured Numeric for inequalities/titers, e.g., <^0.5 or 1^:^64), CE/CWE (Coded With Exceptions, e.g., SNOMED CT organism codes), ST/TX/FT (String or Formatted Text narratives), or ED (Encapsulated Data, such as a Base64-encoded PDF or waveform).
OBX-3 (Observation Identifier): The specific analyte or clinical measurement, standardized with LOINC (e.g., 2345-7^Glucose^LN).
OBX-4 (Observation Sub-ID): Distinguishes multiple OBX segments sharing the same OBX-3 LOINC code under a single OBR (critical for multi-line microbiology susceptibility profiles or multi-paragraph pathology reports).
OBX-8 (Abnormal Flags) & OBX-11 (Observation Result Status): OBX-8 flags out-of-range values (L Low, H High, LL Panic Low, HH Panic High, A Abnormal). OBX-11 governs clinical lifecycle state: P (Preliminary), F (Final), C (Record coming over is a correction and thus replaces a final result), or X (Canceled/Cannot obtain). In HL7 v2-to-FHIR R4 pipelines, each OBR maps to a FHIR DiagnosticReport (and ServiceRequest) while each child OBX maps to a FHIR Observation resource.

Frequently Asked Questions

What is HL7 ORU?

HL7 ORU (Observation Result — Unsolicited, most commonly trigger event ORU^R01) is the standard HL7 Version 2 message type used by Laboratory Information Systems (LIS), radiology PACS/RIS, and bedside medical devices to transmit structured clinical observations, laboratory panels, and diagnostic reports to an Electronic Health Record (EHR) or public health registry.

How do HL7 ORU, ORM, SIU, and MDM messages differ in hospital workflows?

While ADT messages manage patient movement, four clinical message families drive order-to-result and scheduling workflows: ORM^O01 (or OML/OMG) transmits clinical orders from the EHR to ancillaries; ORU^R01 returns structured diagnostic and lab results in OBX segments; SIU (S12–S15) synchronizes appointment bookings and cancellations; and MDM (T02/T04) transmits clinical narrative documents and transcription status updates.

How are OBR and OBX segments structured inside an HL7 ORU^R01 message?

In an HL7 ORU^R01 message, each ordered battery or panel is represented by an OBR (Observation Request) header segment containing the placer/filler order numbers and LOINC panel code (OBR-4), followed by one or more repeating OBX (Observation/Result) child segments carrying the value data type (OBX-2), LOINC test identifier (OBX-3), result value (OBX-5), UCUM units (OBX-6), reference range (OBX-7), abnormal flag (OBX-8), and result status (OBX-11).

Sources

Health Level Seven International (HL7). HL7 Messaging Standard Version 2.5.1 & Version 2.8 (Chapters 4, 7, 9, and 10). https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185
Electronic Code of Federal Regulations (eCFR). 45 CFR § 170.315(f)(3) — Transmission to Public Health Agencies: Electronic Laboratory Reporting. https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-D/part-170/subpart-C/section-170.315

Ask about HL7 ORU, ORM, SIU & MDM Messages: OBX/OBR Segment Structure & EHR Integration

Ask your first 2 questions free below. Subscribers get 150 a day for $29 a month.

An AI assistant specialized in research administration. It cites the sources behind every answer, labels web answers and says when it can't answer.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.