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

HL7 MFN_M03 Test/Observation Master File

Catalog updates for tests and observations that orders and results depend on.

HL7 message structure MFN_M03 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_M03.MF_TEST	Mf Test group	Yes	Yes
MFE	Master File Entry	Yes	No
OM1	General Segment	Yes	No
anyHL7Segment	Anyhl7segment group	Yes	No

MFN_M03 publishes master-file updates for tests or observations. In practice this means lab tests, radiology exams, panels, observations, or local service codes that other systems use in orders and results.

This event is marked as withdrawn/deprecated in later HL7 terminology, with newer and more specific test/observation master-file events available. Still, v2.5.1 interfaces may use MFN_M03, and those catalog feeds often sit right under critical order/result workflows.

A small MFN M03 example

MSH|^~\&|CATALOG|CITYHOSP|EHR|CITYHOSP|20260718123000||MFN^M03^MFN_M03|MFN030001|P|2.5.1 MFI|OM1^Test observation master^HL70175|LABCAT^CITYHOSP|UPD|20260718123000|20260718130000|AL MFE|MUP|MFN030001|20260718130000|CBC^Complete blood count^L|CE OM1|1|CBC^Complete blood count^L|NM~ST|Y|LAB^City Hospital Laboratory^L|Complete blood count panel|||CBC|Complete Blood Count OM4|1|BLD^Blood^HL70070|K2EDTA^EDTA tube^L|2|mL^milliliter^ISO+ NTE|1||Updated specimen and display metadata for order/result catalog.

What workflow it represents

The sender is usually a laboratory information system, enterprise catalog, radiology system, or integration layer that manages observation definitions. The receiver may use the feed to maintain ordering catalogs, result mapping, picklists, validation, or downstream code translations.

These messages are deceptively important. If the catalog says the wrong specimen, display name, orderability, data type, or code system, the later ORM_O01, OML_O21, or ORU_R01 traffic can be technically valid and operationally wrong.

How to read the structure

MSH identifies the notification. MFI identifies the test/observation master file. Each group starts with MFE, whose primary key should match the catalog code being updated.

OM1 carries the general observation definition. The required any-segment group can carry the additional observation-master details agreed by the profile, such as OM4 for specimen information or one of the other OM segments for numeric, categorical, battery, or calculated observation detail.

Implementation traps

The common trap is treating display names as identifiers. The stable key is the catalog code and coding system. Display names are allowed to change; mappings should survive that.

Another trap is updating the order catalog but not result mapping, or the other way around. A test definition usually has ordering behavior, specimen behavior, result behavior, and billing/reporting behavior. Decide which parts this feed owns.

Reference notes

HL7 terminology marks M03 as a test/observation master-file event that is deprecated in later versions. HL7 master-file material also lists newer test/observation-specific master-file events for numeric, categorical, batteries, calculated observations, and additional basic observation definitions.