HL7 OM3 Segment: Categorical Service/Test/Observation

The OM3 (Categorical Service/Test/Observation) segment extends an observation/test master catalog entry with the attributes specific to a categorical result, that is, a result expressed as a code or text rather than a number. Where OM1 carries the general definition shared by all observation types, OM3 supplies the categorical detail: the preferred coding system (OM3-2), the set of valid coded answers (OM3-3), and the codes that count as normal, abnormal, or critical (OM3-4, OM3-5, OM3-6). OM3 is used when the observation produces a categorical value.

Purpose

OM3 lets a producing system publish the controlled vocabulary and result semantics for a categorical observation. It names the coding system that answers are drawn from, enumerates the permitted answers, and classifies which of those answers are normal, abnormal, or critical so that result systems can flag findings consistently. The value type (OM3-7) records how the categorical result is carried. These definitions let order-entry and result systems validate incoming categorical results against an agreed-upon answer set.

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

Used in

OM3 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; OM3 then follows OM1 to extend a categorical observation with its coded-answer 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 (OM3 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
OM3-1	Sequence Number - Test/Observation Master File	nm	—	R	—	—	Sequence number shared with the OM1 entry
OM3-2	Preferred Coding System	ce	—	O	—	—	Coding system from which answers are drawn
OM3-3	Valid Coded "Answers"	ce	—	O	—	—	Permitted coded answers for the observation
OM3-4	Normal Text/Codes for Categorical Observations	ce	—	O	Y	—	Codes considered normal for the observation
OM3-5	Abnormal Text/Codes for Categorical Observations	ce	—	O	Y	—	Codes considered abnormal for the observation
OM3-6	Critical Text/Codes for Categorical Observations	ce	—	O	Y	—	Codes considered critical for the observation
OM3-7	Value Type	id	—	O	—	HL70125	Data type used to carry the categorical value

Most-used fields

OM3-1 Sequence Number - Test/Observation Master File: the key that ties the categorical extension to its OM1 general definition.
OM3-2 Preferred Coding System: the vocabulary that valid answers belong to.
OM3-3 Valid Coded "Answers": the enumerated set of permitted result codes.
OM3-4 / OM3-5 / OM3-6 Normal / Abnormal / Critical codes: classify answers so results can be flagged.
OM3-7 Value Type: indicates how the categorical result value is carried.

Version differences (2.3 to 2.8.2)

OM3 has been one of the most stable observation-catalog segments, keeping its compact seven-field structure across versions. Its evolution has been in the referenced data types and supporting tables rather than in field count: the coded fields use the CE type, and the value type field references the standard value-type table that itself gained members over time. Through v2.8.2 the field positions are unchanged, so OM3 segments built against v2.5.1 generally load cleanly on neighboring versions. Confirm only that the coding systems named in OM3-2 and the value-type codes in OM3-7 are recognized by the receiver for the negotiated version.

Common mistakes

Omitting OM3-1 or mismatching it with OM1-1. The sequence number must equal the sequence number of the OM1 general definition it extends.
Sending OM3 for a numeric observation. Categorical attributes belong only with observations whose result is coded or text; numeric entries use OM2.
Failing to enumerate valid answers in OM3-3, which leaves receivers unable to validate incoming results.
Listing a code as both normal and abnormal across OM3-4 and OM3-5, creating ambiguous flagging.
Ignoring repetition. OM3-4, OM3-5, and OM3-6 may repeat to list multiple codes; collapsing them loses members of the answer set.

Examples

Minimal valid segment (only the required field):

OM3|1

Fully-populated segment:

OM3|1|SCT^SNOMED CT^L|260385009^Negative^SCT~10828004^Positive^SCT|260385009^Negative^SCT|10828004^Positive^SCT|10828004^Positive^SCT|CE

Annotated breakdown:

OM3|1|SCT^SNOMED CT^L|...Negative~...Positive|...Negative|...Positive|...Positive|CE
    |  |               |                       |           |           |           |
    |  |               |                       |           |           |           └─> OM3-7 Value Type (CE)
    |  |               |                       |           |           └─────────────> OM3-6 Critical Text/Codes
    |  |               |                       |           └─────────────────────────> OM3-5 Abnormal Text/Codes
    |  |               |                       └─────────────────────────────────────> OM3-4 Normal Text/Codes
    |  |               └─────────────────────────────────────────────────────────────> OM3-3 Valid Coded "Answers"
    |  └─────────────────────────────────────────────────────────────────────────────> OM3-2 Preferred Coding System
    └────────────────────────────────────────────────────────────────────────────────> OM3-1 Sequence Number (required, matches OM1-1)

In-context excerpt, OM3 extending an OM1 ABO group definition inside an MFN^M08:

MSH|^~&|LIS|VORRO|EMR|HOSP|20260610082000||MFN^M08^MFN_M08|MSG00061|P|2.5.1
MFI|OMA^Observation Master^L|VORRO|UPD|20260610082000||AL
MFE|MAD|MFE0002|20260610082000|BLDABO^ABO Group^L|CE
OM1|2|BLDABO^ABO Group^L|CE|Y|LAB001^Vorro Reference Lab^L|ABO blood group|||ABO Group||||||BLDBNK^Blood Bank^L||A
OM3|2|HL70112^ABO^L|A^A^L~B^B^L~O^O^L~AB^AB^L|A^A^L~B^B^L~O^O^L~AB^AB^L|||CE

In-context excerpt, OM3 for a microbiology culture result inside an MFN^M08:

MSH|^~&|LIS|VORRO|EMR|HOSP|20260610084500||MFN^M08^MFN_M08|MSG00062|P|2.5.1
MFI|OMA^Observation Master^L|VORRO|UPD|20260610084500||AL
MFE|MAD|MFE0020|20260610084500|CULT^Culture Result^L|CE
OM1|20|CULT^Culture Result^L|CE|Y|LAB001^Vorro Reference Lab^L|Bacterial culture interpretation|||Culture Result||||||MICRO^Microbiology^L||A
OM3|20|SCT^SNOMED CT^L|260385009^Negative^SCT~10828004^Positive^SCT|260385009^Negative^SCT|10828004^Positive^SCT|10828004^Positive^SCT|CE

FHIR mapping

There is no segment-level ConceptMap published in the v2-to-FHIR Implementation Guide for OM3. The categorical attributes of OM3 map conceptually to ObservationDefinition in FHIR, where the valid coded answers align with ObservationDefinition.qualifiedInterval (categorical type) and ObservationDefinition.validCodedValueSet, and the normal/abnormal/critical classifications align with qualified interval categories. Because OM3 always extends an OM1 entry, FHIR mapping is performed against the combined catalog record rather than the OM3 segment in isolation. Treat any field-level alignment as conceptual rather than a published transform.

Engine considerations

OM3 is meaningful only in the context of a preceding OM1; engines should attach it to the OM1 sharing the same OM3-1 / OM1-1 sequence number.
The coded fields use the CE data type; parse the full identifier, text, and coding-system components so answers resolve correctly.
OM3-4, OM3-5, and OM3-6 may repeat; retain each repetition so the complete normal, abnormal, and critical answer sets survive round-trips.
Validate that coding systems named in OM3-2 are recognized before applying the valid-answer set to incoming results.

How Vorro parses and produces OM3

When Vorro parses OM3, it links the segment to its OM1 general definition by matching OM3-1 to OM1-1, then loads the preferred coding system and the valid coded answers into the categorical portion of the catalog model. Normal, abnormal, and critical code sets are preserved as ordered lists so result flagging stays faithful to the producer's definition.

When Vorro produces OM3, it emits the segment only for observations that are categorical per the OM1 definition, always sets the required OM3-1 to match OM1-1, and writes the valid answer set and classifications as coded CE values. The value type in OM3-7 is set so receivers know how the categorical result is carried.

Sources

← Back to HL7 v2 Guide