HL7 OM2 Segment: Numeric Observation

The OM2 (Numeric Observation) segment extends an observation/test master catalog entry with the attributes specific to a quantitative result. Where OM1 carries the general definition shared by all observation types, OM2 supplies the numeric detail: the units of measure (OM2-2), decimal precision (OM2-3), reference and critical ranges (OM2-6 and OM2-7), and delta-check criteria (OM2-9). OM2 is used when the observation produces a numeric value, signalled by the data types and nature recorded in OM1.

Purpose

OM2 lets a producing system publish how a numeric observation should be interpreted and bounded. Reference (normal) ranges tell a result system what is expected, critical ranges identify values requiring urgent attention, and absolute ranges bound what the instrument can report at all. Units of measure and SI conversion information let receivers display and normalize values consistently. Delta-check criteria and minimum meaningful increments support quality checks and rounding behavior. Together these define the numeric semantics that order-entry and result systems apply when handling values for the test.

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

Used in

OM2 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; OM2 then follows OM1 to extend a numeric observation with its quantitative 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 (OM2 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
OM2-1	Sequence Number - Test/Observation Master File	nm	—	R	—	—	Sequence number shared with the OM1 entry
OM2-2	Units of Measure	ce	—	O	—	—	Units in which the value is reported
OM2-3	Range of Decimal Precision	nm	—	O	Y	—	Decimal precision used for the value
OM2-4	Corresponding SI Units of Measure	ce	—	O	—	—	SI units corresponding to the reported units
OM2-5	SI Conversion Factor	tx	—	O	—	—	Factor to convert to SI units
OM2-6	Reference (Normal) Range - Ordinal and Continuous Observations	rfr	—	O	Y	—	Expected normal range for the value
OM2-7	Critical Range for Ordinal and Continuous Observations	rfr	—	O	Y	—	Values requiring urgent attention
OM2-8	Absolute Range for Ordinal and Continuous Observations	rfr	—	O	—	—	Reportable limits of the measurement
OM2-9	Delta Check Criteria	dlt	—	O	Y	—	Criteria for flagging change between results
OM2-10	Minimum Meaningful Increments	nm	—	O	—	—	Smallest meaningful change in the value

Most-used fields

OM2-1 Sequence Number - Test/Observation Master File: the key that ties the numeric extension to its OM1 general definition.
OM2-2 Units of Measure: the units used for the reported value, often UCUM-coded.
OM2-6 Reference (Normal) Range: the expected range, used to flag results as normal or abnormal.
OM2-7 Critical Range: the bounds beyond which a result is critical and triggers urgent notification.
OM2-3 Range of Decimal Precision: governs how many decimal places the value carries.

Version differences (2.3 to 2.8.2)

OM2 has been stable in shape across versions, retaining its compact ten-field structure focused on numeric semantics. The principal evolution has been in the data types it references rather than in field count: range fields use the RFR (reference range) type and delta checks use the DLT type, both of which were refined as the value-range and delta-check components matured. Units fields increasingly carry UCUM-coded values in modern deployments even though the underlying CE/CWE structure is unchanged. Because the field positions have not shifted materially between v2.3 and v2.8.2, OM2 segments built against v2.5.1 generally load cleanly on neighboring versions; confirm only the exact component structure of RFR and DLT against the negotiated version.

Common mistakes

Omitting OM2-1 or mismatching it with OM1-1. The sequence number must equal the sequence number of the OM1 general definition it extends.
Sending OM2 for a non-numeric observation. Numeric attributes belong only with observations whose result is quantitative; categorical entries use OM3.
Confusing the range fields. Reference (normal), critical, and absolute ranges (OM2-6, OM2-7, OM2-8) have distinct meanings and must not be interchanged.
Encoding units as free text instead of a coded CE value in OM2-2, which breaks downstream normalization.
Ignoring repetition. OM2-3, OM2-6, OM2-7, and OM2-9 may repeat to cover population-specific ranges; collapsing them loses information.

Examples

Minimal valid segment (only the required field):

OM2|1

Fully-populated segment:

OM2|1|mg/dL^milligram per deciliter^UCUM|2~1|mmol/L^millimole per liter^UCUM|0.0555|70-99^^^F~60-100^^^M|<40^^^L~>400^^^H|10-600|1.0&20&%^^^^^^|1

Annotated breakdown:

OM2|1|mg/dL^...^UCUM|2~1|mmol/L^...^UCUM|0.0555|70-99^^^F|<40^^^L|10-600|...
    |  |             |   |               |      |          |        |
    |  |             |   |               |      |          |        └─> OM2-8 Absolute Range (reportable limits)
    |  |             |   |               |      |          └──────────> OM2-7 Critical Range (urgent values)
    |  |             |   |               |      └─────────────────────> OM2-6 Reference (Normal) Range
    |  |             |   |               └────────────────────────────> OM2-5 SI Conversion Factor
    |  |             |   └────────────────────────────────────────────> OM2-4 Corresponding SI Units
    |  |             └────────────────────────────────────────────────> OM2-3 Range of Decimal Precision (repeating)
    |  └──────────────────────────────────────────────────────────────> OM2-2 Units of Measure
    └─────────────────────────────────────────────────────────────────> OM2-1 Sequence Number (required, matches OM1-1)

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

MSH|^~&|LIS|VORRO|EMR|HOSP|20260610081500||MFN^M08^MFN_M08|MSG00051|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
OM2|1|mg/dL^milligram per deciliter^UCUM|2|mmol/L^millimole per liter^UCUM|0.0555|70-99^^^F|<40^^^L~>400^^^H|10-600|

In-context excerpt, two numeric definitions in one MFN^M08:

MSH|^~&|LIS|VORRO|EMR|HOSP|20260610083000||MFN^M08^MFN_M08|MSG00052|P|2.5.1
MFI|OMA^Observation Master^L|VORRO|UPD|20260610083000||AL
MFE|MAD|MFE0010|20260610083000|K^Potassium^L|CE
OM1|10|K^Potassium^L|NM|Y|LAB001^Vorro Reference Lab^L|Serum potassium|||Potassium||||||CHEM^Chemistry^L||A
OM2|10|mmol/L^millimole per liter^UCUM|1|mmol/L^millimole per liter^UCUM|1.0|3.5-5.1^^^|<2.5^^^L~>6.5^^^H|1.0-9.0|
MFE|MAD|MFE0011|20260610083000|NA^Sodium^L|CE
OM1|11|NA^Sodium^L|NM|Y|LAB001^Vorro Reference Lab^L|Serum sodium|||Sodium||||||CHEM^Chemistry^L||A
OM2|11|mmol/L^millimole per liter^UCUM|0|mmol/L^millimole per liter^UCUM|1.0|136-145^^^|<120^^^L~>160^^^H|100-200|

FHIR mapping

There is no segment-level ConceptMap published in the v2-to-FHIR Implementation Guide for OM2. The numeric attributes of OM2 map conceptually to ObservationDefinition in FHIR, where units align with ObservationDefinition.quantitativeDetails (unit and conversion factor) and ranges align with ObservationDefinition.qualifiedInterval (normal, critical, and absolute categories). Because OM2 always extends an OM1 entry, FHIR mapping is performed against the combined catalog record rather than the OM2 segment in isolation. Treat any field-level alignment as conceptual rather than a published transform.

Engine considerations

OM2 is meaningful only in the context of a preceding OM1; engines should attach it to the OM1 sharing the same OM2-1 / OM1-1 sequence number.
Range fields use the RFR data type and carry low/high values plus an optional condition or age/sex qualifier. Parse all components, not just the numeric bounds.
OM2-3, OM2-6, OM2-7, and OM2-9 may repeat; retain each repetition so population-specific ranges and delta checks survive round-trips.
Normalize units (OM2-2 and OM2-4) and apply the SI conversion factor (OM2-5) consistently when reconciling values from different sources.

How Vorro parses and produces OM2

When Vorro parses OM2, it links the segment to its OM1 general definition by matching OM2-1 to OM1-1, then loads units, precision, and ranges into the numeric portion of the catalog model. Repeating reference and critical ranges are preserved as ordered lists with their qualifiers intact, and the SI conversion factor is retained for value normalization.

When Vorro produces OM2, it emits the segment only for observations that are numeric per the OM1 definition, always sets the required OM2-1 to match OM1-1, and encodes units as coded values so receivers can normalize cleanly. Reference and critical ranges are written with their full RFR component structure, and precision is set so downstream systems render values consistently.

Sources

← Back to HL7 v2 Guide