HL7 OM4 Segment: Observations that Require Specimens

The OM4 (Observations that Require Specimens) segment extends an observation/test master catalog entry with the attributes specific to a test that needs a physical specimen. Where OM1 carries the general definition shared by all observation types, OM4 supplies the specimen detail: the specimen type (OM4-6), the additive (OM4-7), the container description and volume (OM4-3, OM4-4), and the collection volumes and handling requirements. OM4 is used when OM1-4 Specimen Required indicates that a specimen must be collected.

Purpose

OM4 lets a producing system publish how a specimen for a given observation must be collected, contained, and handled. It records the specimen type, the container and any additive, the normal and minimum collection volumes, special handling requirements, and how long the specimen is retained. When a single test can be performed on more than one specimen type, OM4 may repeat within the catalog entry to describe each option. These definitions let order-entry and collection systems guide phlebotomists and specimen-processing staff to collect the correct specimen the first time.

OM4 never stands alone. It always follows an OM1 general definition for the same catalog entry, sharing the OM4-1 sequence number with OM1-1. For numeric observations use OM2; for categorical observations use OM3.

Used in

OM4 appears in MFN master-file notification messages that define the test/observation catalog, most commonly the MFN^M08 (test/observation master file) message. Within that message the master file identification (MFI) segment names the file, each master file entry (MFE) segment marks a record, and OM1 provides the general definition; OM4 then follows OM1 to extend an observation that requires a specimen with its collection and container attributes.

See MFN messages for the surrounding structure. OM1 is the general definition shared by all observation types; OM2 (numeric), OM3 (categorical), and OM4 (specimen) extend it.

Field-by-field reference

Source: HAPI HL7v2 v2.5.1 javadocs (OM4 javadoc) for sequence, name, data type, and repetition. Length is not published in the javadocs (—); Required and Table # are filled from the HL7 v2.5.1 standard where well-established.

Seq	Name	Data Type	Length	Req	Repeat	Table #	Description
OM4-1	Sequence Number - Test/Observation Master File	nm	—	R	—	—	Sequence number shared with the OM1 entry
OM4-2	Derived Specimen	id	—	O	—	HL70170	Whether the specimen is derived from another
OM4-3	Container Description	tx	—	O	—	—	Description of the collection container
OM4-4	Container Volume	nm	—	O	—	—	Volume the container holds
OM4-5	Container Units	ce	—	O	—	—	Units for the container volume
OM4-6	Specimen	ce	—	O	—	HL70070	Type of specimen required for the test
OM4-7	Additive	cwe	—	O	—	HL70371	Additive present in the container
OM4-8	Preparation	tx	—	O	—	—	Preparation needed before collection
OM4-9	Special Handling Requirements	tx	—	O	—	—	Special handling for the specimen
OM4-10	Normal Collection Volume	cq	—	O	—	—	Usual volume collected for the test
OM4-11	Minimum Collection Volume	cq	—	O	—	—	Smallest acceptable collection volume
OM4-12	Specimen Requirements	tx	—	O	—	—	Free-text specimen requirements
OM4-13	Specimen Priorities	id	—	O	Y	HL70027	Priorities at which the specimen is handled
OM4-14	Specimen Retention Time	cq	—	O	—	—	How long the specimen is retained

Most-used fields

OM4-1 Sequence Number - Test/Observation Master File: the key that ties the specimen extension to its OM1 general definition.
OM4-6 Specimen: the type of specimen the test requires.
OM4-7 Additive: the additive in the collection container, such as an anticoagulant.
OM4-3 / OM4-4 / OM4-5 Container description, volume, and units: identify the correct collection container.
OM4-10 / OM4-11 Normal and minimum collection volumes: guide how much specimen to collect.

Version differences (2.3 to 2.8.2)

OM4 has been stable in shape across versions, retaining its fourteen-field structure focused on specimen and container attributes. Its evolution has been largely in the referenced data types and supporting tables: the additive field (OM4-7) moved toward the CWE coded-with-exceptions type, and collection-volume fields use the CQ (composite quantity with units) type whose unit component matured over time. The specimen-type table referenced by OM4-6 gained members as specimen vocabularies expanded. Through v2.8.2 the field positions are unchanged, so OM4 segments built against v2.5.1 generally load cleanly on neighboring versions; confirm only that specimen and additive codes are recognized by the receiver for the negotiated version.

Common mistakes

Omitting OM4-1 or mismatching it with OM1-1. The sequence number must equal the sequence number of the OM1 general definition it extends.
Sending OM4 when OM1-4 Specimen Required does not call for a specimen, or omitting OM4 when it does. Keep the two consistent.
Confusing container volume (OM4-4) with collection volume (OM4-10 and OM4-11); they describe different quantities.
Encoding the specimen type as free text instead of a coded CE value in OM4-6, which breaks downstream matching to collection rules.
Ignoring repetition. OM4-13 Specimen Priorities may repeat, and OM4 itself may repeat to describe alternative specimen options; collapsing these loses information.

Examples

Minimal valid segment (only the required field):

OM4|1

Fully-populated segment:

OM4|1|N|Lavender-top EDTA tube|4|mL^milliliter^UCUM|BLD^Whole blood^HL70070|EDTA^EDTA^HL70371|Fasting 8 hours|Keep on ice, deliver within 30 minutes|3&mL&UCUM|1&mL&UCUM|Avoid hemolysis|S~R|7&d&UCUM

Annotated breakdown:

OM4|1|N|Lavender-top EDTA tube|4|mL^...^UCUM|BLD^Whole blood^HL70070|EDTA^EDTA^HL70371|...
    |  |  |                    | |           |                       |
    |  |  |                    | |           |                       └─> OM4-7  Additive (EDTA)
    |  |  |                    | |           └─────────────────────────> OM4-6  Specimen (whole blood)
    |  |  |                    | └─────────────────────────────────────> OM4-5  Container Units
    |  |  |                    └───────────────────────────────────────> OM4-4  Container Volume
    |  |  └────────────────────────────────────────────────────────────> OM4-3  Container Description
    |  └───────────────────────────────────────────────────────────────> OM4-2  Derived Specimen (N = not derived)
    └──────────────────────────────────────────────────────────────────> OM4-1  Sequence Number (required, matches OM1-1)

In-context excerpt, OM4 extending an OM1 glucose definition inside an MFN^M08:

MSH|^~&|LIS|VORRO|EMR|HOSP|20260610081500||MFN^M08^MFN_M08|MSG00071|P|2.5.1
MFI|OMA^Observation Master^L|VORRO|UPD|20260610081500||AL
MFE|MAD|MFE0001|20260610081500|GLU^Glucose^L|CE
OM1|1|GLU^Glucose^L|NM|Y|LAB001^Vorro Reference Lab^L|Fasting plasma glucose|||Glucose, Plasma||||||CHEM^Chemistry^L||A
OM4|1|N|Gray-top sodium fluoride tube|3|mL^milliliter^UCUM|PLAS^Plasma^HL70070|FL^Sodium fluoride^HL70371|Fasting 8 hours|Deliver within 1 hour|2&mL&UCUM|1&mL&UCUM|Avoid hemolysis|R|7&d&UCUM

In-context excerpt, one entry with two specimen options inside an MFN^M08:

MSH|^~&|LIS|VORRO|EMR|HOSP|20260610090000||MFN^M08^MFN_M08|MSG00072|P|2.5.1
MFI|OMA^Observation Master^L|VORRO|UPD|20260610090000||AL
MFE|MAD|MFE0030|20260610090000|CULT^Culture^L|CE
OM1|30|CULT^Culture^L|CE|Y|LAB001^Vorro Reference Lab^L|Bacterial culture|||Culture||||||MICRO^Microbiology^L||A
OM4|30|N|Sterile urine cup|60|mL^milliliter^UCUM|UR^Urine^HL70070||Clean catch|Refrigerate if delayed|10&mL&UCUM|5&mL&UCUM|Midstream specimen|S~R|2&d&UCUM
OM4|30|N|Swab transport tube|1|mL^milliliter^UCUM|WND^Wound^HL70070||None|Transport at room temperature|1&mL&UCUM|1&mL&UCUM|Avoid contamination|S~R|2&d&UCUM

FHIR mapping

There is no segment-level ConceptMap published in the v2-to-FHIR Implementation Guide for OM4. The specimen attributes of OM4 map conceptually to ObservationDefinition in FHIR, where specimen and container detail align with SpecimenDefinition (referenced from ObservationDefinition), and additive, container, and volume detail align with SpecimenDefinition.typeTested and container components. Because OM4 always extends an OM1 entry, FHIR mapping is performed against the combined catalog record rather than the OM4 segment in isolation. Treat any field-level alignment as conceptual rather than a published transform.

Engine considerations

OM4 is meaningful only in the context of a preceding OM1; engines should attach it to the OM1 sharing the same OM4-1 / OM1-1 sequence number.
A single catalog entry may carry more than one OM4 to describe alternative specimen options; treat repeated OM4 segments as a set rather than overwriting.
Collection-volume fields use the CQ data type carrying a quantity and a unit component; parse both so volumes are unambiguous.
Reconcile OM4 against OM1-4 Specimen Required and warn when the two disagree about whether a specimen is needed.

How Vorro parses and produces OM4

When Vorro parses OM4, it links the segment to its OM1 general definition by matching OM4-1 to OM1-1, then loads specimen type, container, additive, and collection volumes into the specimen portion of the catalog model. Repeated OM4 segments for one entry are retained as a set of specimen options, and CQ volume fields are parsed into quantity-plus-unit pairs for downstream collection rules.

When Vorro produces OM4, it emits the segment only for observations whose OM1-4 indicates a specimen is required, always sets the required OM4-1 to match OM1-1, and encodes specimen and additive as coded values so collection systems can match them to container rules. Collection volumes are written with explicit units, and alternative specimen options are emitted as repeated OM4 segments.

Sources

← Back to HL7 v2 Guide