HL7 MFN_M09 Test/Observation Categorical Master File

Catalog updates for observations whose answers come from a controlled list.
HL7 message structure MFN_M09 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

SegmentNameRequiredRepeatable
MSH
 Message Header Yes No
SFT
 Software Segment No Yes
MFI
 Master File Identification Yes No
MFN_M09.MF_TEST_CATEGORICAL
 Mf Test Categorical group Yes Yes
MFE
 Master File Entry Yes No
OM1
 General Segment Yes No
MFN_M09.MF_TEST_CAT_DETAIL
 Mf Test Cat Detail group No No
OM3
 Categorical Service/Test/Observation Yes No
OM4
 Observations that Require Specimens No Yes

MFN_M09 publishes master-file updates for categorical tests and observations. These are the tests where the result is not primarily a free number, but a coded answer such as positive/negative, present/absent, detected/not detected, grade, color, organism category, or another local answer set.

This lives in the same order/result neighborhood as MFN_M08, but it answers a different catalog question. MFN_M08 says how to interpret numeric values. MFN_M09 says which coded answers are valid and how the receiver should treat normal, abnormal, or critical categorical answers before ORU_R01 results start arriving.

A small MFN M09 example

MSH|^~\&|LIS|CITYHOSP|EHR|CITYHOSP|20260722111000||MFN^M09^MFN_M09|MFN090001|P|2.5.1 MFI|OMB^Categorical observation master^HL70175|LIS^CITYHOSP|UPD|20260722111000|20260722113000|AL MFE|MAD|MFN090001|20260722113000|STREPA^Strep A screen^L|CE OM1|1|STREPA^Strep A screen^L|CWE|Y|LAB^City Hospital Laboratory^L|Group A streptococcus rapid screen||||Strep A Screen|Strep A Screen|Y OM3|1|L^Local answer set^L|NEG^Negative^L~POS^Positive^L~IND^Indeterminate^L|NEG^Negative^L|POS^Positive^L||CWE OM4|1|N|Throat swab transport tube|1|swab^swab^L|THRT^Throat swab^HL70070

What workflow it represents

The sender is usually a LIS, enterprise test catalog, microbiology system, device middleware layer, or integration engine that owns answer-set publishing. Receivers use the message to keep ordering catalogs, result validation, abnormal flagging, display logic, and analytics mappings aligned.

The value is in avoiding quiet drift. A result interface can send OBX-5 perfectly, but if the receiver has an old answer list, a new result code may land as unknown, plain text, or a local exception.

How to read the structure

MSH, MFI, and MFE provide the master-file envelope and record key. MFI-1 commonly identifies the categorical observation master file, and MFE-4 should identify the observation being updated.

Each MF_TEST_CATEGORICAL group has required OM1 for the general observation definition. The optional MF_TEST_CAT_DETAIL group adds required OM3 for categorical answer behavior and optional repeating OM4 for specimen requirements.

Use MFK_M01 when the sender needs record-level confirmation that the categorical observation was accepted by the receiver.

Implementation traps

The common trap is treating answer text as the answer code. "Positive" may display nicely, but the stable contract is the coded value and coding system. Text can change; mappings should not collapse when wording changes from "Positive" to "Detected."

Another trap is not deciding where abnormal and critical meaning comes from. Some interfaces rely on OBX abnormal flags at result time. Others want the catalog to define which categorical answers are normal, abnormal, or critical. Either can work, but mixed ownership gets messy fast.

Also decide whether OM3 is allowed to replace the whole answer set or only update listed answers. That rule matters when a site retires an old code but historical results still use it.

Reference notes

HL7 v2+ identifies M09 as the categorical test/observation master-file event. Its structure requires OM1 and can add OM3 for categorical answer definitions plus OM4 for specimen details.