HL7 MFN_M08 (Test/Observation Numeric Master File) | Integration Soup HL7 Reference Guide

HL7 MFN_M08 Test/Observation Numeric Master File

Catalog updates for numeric observations: units, precision, ranges, specimens, and result behavior.

HL7 message structure MFN_M08 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
MFI	Master File Identification	Yes	No
MFN_M08.MF_TEST_NUMERIC	Mf Test Numeric group	Yes	Yes
MFE	Master File Entry	Yes	No
OM1	General Segment	Yes	No
OM2	Numeric Observation	No	No
OM3	Categorical Service/Test/Observation	No	No
OM4	Observations that Require Specimens	No	No

MFN_M08 publishes master-file updates for numeric tests and observations. Think glucose, potassium, weight, blood pressure components, calculated numeric scores, and other observations where receivers care about units, decimal precision, reference ranges, critical ranges, and specimen handling.

This is reference data for the order/result world. It supports later ORM_O01, OML_O21, and ORU_R01 workflows by keeping test definitions aligned before orders and results start flowing.

A small MFN M08 example

MSH|^~\&|LIS|CITYHOSP|EHR|CITYHOSP|20260722104000||MFN^M08^MFN_M08|MFN080001|P|2.5.1 MFI|OMA^Numeric observation master^HL70175|LIS^CITYHOSP|UPD|20260722104000|20260722110000|AL MFE|MAD|MFN080001|20260722110000|GLU^Glucose^L|CE OM1|1|GLU^Glucose^L|NM|Y|LAB^City Hospital Laboratory^L|Serum glucose measurement||||Glucose|Glucose Serum|Y OM2|1|mmol/L^millimole per liter^UCUM|1|||3.9-5.5|2.5-25.0|0-60 OM4|1|N|Serum separator tube|5|mL^milliliter^ISO+|SER^Serum^HL70070|SST^Serum separator tube^L|Centrifuge before analysis

What workflow it represents

The sender is often a laboratory information system, enterprise test catalog, device middleware layer, or integration engine that publishes test definitions. Receivers may use the feed for ordering catalogs, result validation, reference-range display, abnormal flag logic, mapping, and downstream analytics.

If the numeric catalog is wrong, later results can look valid while being clinically confusing. A value of 5.6 is not meaningful until the receiver knows the units, expected precision, and reference interval that apply to that observation.

How to read the structure

MSH, MFI, and MFE carry the message, file, and record identity. The primary key in MFE should line up with the test or observation code carried in the observation master segments.

OM1 is required and carries the general observation definition: identifier, permitted data types, whether a specimen is required, producer, names, orderability, and other broad catalog behavior.

OM2 is the numeric detail segment. This is where units, decimal precision, reference ranges, critical ranges, absolute ranges, delta checks, and meaningful increments belong. OM3 is available when categorical details are still needed, and OM4 carries specimen and container requirements.

Implementation traps

The biggest trap is treating units as display-only text. Units drive interpretation, decision support, trending, conversions, and sometimes billing/reporting. A naked "mg/dL" or "mmol/L" with no coding system is easy to misread across systems.

Reference ranges are another rich source of pain. Decide whether ranges are general defaults, age/sex-specific ranges, method-specific ranges, or local-lab-only ranges. If the real logic is more specific than the feed, say so in the interface agreement.

Also keep orderability and resultability separate. Some observations can be resulted but not directly ordered, while some orderable tests produce multiple result observations. MFN_M08 can define numeric observation behavior, but it should not be forced to carry every catalog relationship if a richer profile is needed.

Reference notes

HL7 v2+ identifies M08 as the numeric test/observation master-file event. The MFN_M08 structure requires OM1 after MFE and allows OM2, OM3, and OM4 for numeric attributes, categorical support, and specimen requirements.