HL7 MFN_M10 (Test/Observation Batteries Master File) | Integration Soup HL7 Reference Guide

HL7 MFN_M10 Test/Observation Batteries Master File

Catalog updates for panels and batteries made from multiple observations.

HL7 message structure MFN_M10 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_M10.MF_TEST_BATTERIES	Mf Test Batteries group	Yes	Yes
MFE	Master File Entry	Yes	No
OM1	General Segment	Yes	No
MFN_M10.MF_TEST_BATT_DETAIL	Mf Test Batt Detail group	No	No
OM5	Observation Batteries (Sets)	Yes	No
OM4	Observations that Require Specimens	No	Yes

MFN_M10 publishes master-file updates for observation batteries: panels, sets, and ordered tests that contain multiple result observations. A complete blood count, metabolic panel, urinalysis panel, or local respiratory panel is the kind of thing this message is trying to keep synchronized.

This message helps systems agree that one orderable battery expands into specific child observations. Without that catalog agreement, later OML_O21 orders and ORU_R01 results can disagree about what "CBC" actually contains.

A small MFN M10 example

MSH|^~\&|LIS|CITYHOSP|EHR|CITYHOSP|20260722112000||MFN^M10^MFN_M10|MFN100001|P|2.5.1 MFI|OMC^Observation batteries master^HL70175|LIS^CITYHOSP|UPD|20260722112000|20260722114000|AL MFE|MAD|MFN100001|20260722114000|CBC^Complete blood count^L|CE OM1|1|CBC^Complete blood count^L|NM~CWE|Y|LAB^City Hospital Laboratory^L|Complete blood count panel||||CBC|Complete Blood Count|Y OM5|1|WBC^White blood cell count^L~RBC^Red blood cell count^L~HGB^Hemoglobin^L~PLT^Platelet count^L|WBC~RBC~HGB~PLT OM4|1|N|EDTA lavender top tube|4|mL^milliliter^ISO+|BLD^Blood^HL70070|K2EDTA^EDTA anticoagulant^L

What workflow it represents

The sender is normally the LIS, an enterprise test catalog, or an integration service that owns panel definitions. Receivers use MFN_M10 to build orderable catalogs, expand batteries, validate result sets, and map local panel definitions into downstream reporting or analytics tools.

When a panel changes, the effect is wider than the one catalog row. Order entry, collection instructions, result display, interface mapping, billing, and clinical decision support may all depend on the same battery membership.

How to read the structure

The standard MSH, MFI, and MFE segments identify the message, the observation battery master file, and the battery record.

OM1 is required for the general test or service definition. The optional MF_TEST_BATT_DETAIL group contains required OM5, which lists observations included in the battery, and optional repeating OM4 for specimen requirements.

For record-level feedback, use MFK_M01. If a receiver rejects one child observation in a battery, the sender needs to know which catalog record failed.

Implementation traps

The easy mistake is assuming a panel code is self-explanatory. "BMP" or "CBC" is local shorthand until the battery membership is explicit. Two sites can use the same display name and include different observations.

Another trap is forgetting effective dates. A battery may change from tomorrow forward, but historical orders and results still need to reflect the old membership. Do not let a catalog update rewrite history unless both sides deliberately agreed to that behavior.

Also decide how the receiver handles extra result observations that are not listed in OM5. Some systems accept them as reflexes or add-ons; others treat them as unknown children of the panel.

Reference notes

HL7 v2+ identifies M10 as the test/observation batteries master-file event. Its structure requires OM1 and can include OM5 for battery membership, with OM4 for specimen-related requirements.