HL7 OUL_R22 (Specimen-Oriented Observation) | Integration Soup HL7 Reference Guide

HL7 OUL_R22 Specimen-Oriented Observation

A lab result message that puts the specimen before the order.

HL7 message structure OUL_R22 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
NTE	Notes and Comments	No	No
OUL_R22.PATIENT	Patient group	No	No
PID	Patient Identification	Yes	No
PD1	Patient Additional Demographic	No	No
NTE	Notes and Comments	No	Yes
OUL_R22.VISIT	Visit group	No	No
PV1	Patient Visit	Yes	No
PV2	Patient Visit - Additional Information	No	No
OUL_R22.SPECIMEN	Specimen group	Yes	Yes
SPM	Specimen	Yes	No
OBX	Observation/Result	No	Yes
OUL_R22.CONTAINER	Container group	No	Yes
SAC	Specimen Container detail	Yes	No
INV	Inventory Detail	No	No
OUL_R22.ORDER	Order group	Yes	Yes
OBR	Observation Request	Yes	No
ORC	Common Order	No	No
NTE	Notes and Comments	No	Yes
OUL_R22.TIMING_QTY	Timing Quantity group	No	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
OUL_R22.OBXTCDSIDNTE_SUPPGRP	Obxtcdsidnte Suppgrp group	No	Yes
OBX	Observation/Result	Yes	No
TCD	Test Code Detail	No	No
SID	Substance Identifier	No	Yes
NTE	Notes and Comments	No	Yes
CTI	Clinical Trial Identification	No	Yes
DSC	Continuation Pointer	No	No

OUL_R22 is an unsolicited laboratory observation message organized around specimens. Where ORU_R01 tends to read patient, order, observation, OUL_R22 makes the specimen the central repeating group and then places orders, observations, containers, and instrument-oriented detail beneath it.

This shape is useful in lab automation, microbiology, specimen processing, and instrument workflows where the specimen and container identity are as important as the order number. If you need to know which tube, aliquot, isolate, or container produced a result, OUL_R22 gives that detail a cleaner structure.

A small OUL specimen result example

MSH|^~\&|LABAUTO|CITYLAB|LIS|CITYLAB|20260715150000||OUL^R22^OUL_R22|OUL00001|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F SPM|1|SPEC20260715001^CITYLAB||BLD^Blood^HL70487|||||||||||||20260715114000 SAC|||TUBE778899^CITYLAB||||SER^Serum tube^L OBR|1|ORD448812^EHR|LAB998878^CITYLAB|24323-8^Comprehensive metabolic panel^LN|||20260715114500 OBX|1|NM|2951-2^Sodium^LN||139|mmol/L|135-145|N|||F OBX|2|NM|2823-3^Potassium^LN||4.2|mmol/L|3.5-5.2|N|||F

What systems do with it

The sender is often a LIS, automation middleware, analyzer manager, or lab integration engine. The receiver may be another LIS, EHR, repository, public health system, or downstream analytics system. The receiver files results while preserving specimen and container identity.

That preservation is the point. If the receiving system only files "sodium 139" and discards the specimen/container trail, it may be losing the exact information that made OUL the right message in the first place.

How to read the structure

The message has optional patient and visit groups, then a required repeating specimen group. SPM identifies the specimen. Container groups under it use SAC and sometimes inventory detail. The order group contains OBR, optional ORC, timing, notes, observation groups, and clinical trial identifiers.

Observation groups under the order carry OBX, with optional TCD, SID, and NTE. Those extra segments are not decorative in automation-heavy labs; they can explain test code detail, substance identity, and comments tied to the observation.

Implementation traps

Do not convert OUL_R22 to ORU_R01 by throwing away SPM and SAC unless the receiver truly cannot store them. A lossy conversion may pass validation while losing traceability. If you must map to ORU, document where specimen ID, type, collection time, container ID, and instrument notes land.

Also watch grouping. In OUL, the order sits under the specimen. That is different from ORU, where specimen is often subordinate to the order. Mapping between the two requires care when one specimen supports multiple orders or one order has multiple specimens.

Reference notes

HL7 and local generated structures describe OUL_R22 as the unsolicited specimen-oriented observation message. Public lab-ordering discussions describe OUL variants as common responses for laboratory order workflows when specimen, order, and observation orientation matters.