HL7 MFN_M11 Test/Calculated Observations Master File

Catalog updates for observations derived from other observations.
HL7 message structure MFN_M11 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_M11.MF_TEST_CALCULATED
 Mf Test Calculated group Yes Yes
MFE
 Master File Entry Yes No
OM1
 General Segment Yes No
MFN_M11.MF_TEST_CALC_DETAIL
 Mf Test Calc Detail group No No
OM6
 Observations that are Calculated from Other Observations Yes No
OM2
 Numeric Observation Yes No

MFN_M11 publishes master-file updates for calculated observations. These are observations such as anion gap, estimated GFR, calculated ratios, risk scores, or derived indexes where the result is produced from other observations or patient context rather than measured directly as a standalone test.

Calculated observations are easy to underestimate because they often look like ordinary numeric results in OBX. The catalog needs to say what the observation is, how it is derived, and how its numeric attributes should be interpreted.

A small MFN M11 example

MSH|^~\&|LIS|CITYHOSP|EHR|CITYHOSP|20260722113000||MFN^M11^MFN_M11|MFN110001|P|2.5.1 MFI|OMD^Calculated observations master^HL70175|LIS^CITYHOSP|UPD|20260722113000|20260722115000|AL MFE|MAD|MFN110001|20260722115000|AGAP^Anion gap^L|CE OM1|1|AGAP^Anion gap^L|NM|N|LAB^City Hospital Laboratory^L|Calculated anion gap||||Anion Gap|Anion Gap|N OM6|1|Calculated from sodium, chloride, and bicarbonate: Na - (Cl + HCO3). OM2|1|mmol/L^millimole per liter^UCUM|1|||8-16|20-40|0-60

What workflow it represents

The sender is usually the LIS, device middleware, analytics service, or enterprise catalog that owns the calculated observation definition. Receivers use MFN_M11 to validate result mappings, display the calculation correctly, understand units and ranges, and avoid treating a calculated value like a directly measured analyte.

This matters when different systems can calculate the same value. If both the LIS and the EHR calculate eGFR or anion gap independently, the interface agreement should say which value is authoritative and what formula/version was used.

How to read the structure

MSH, MFI, and MFE identify the master-file notification and calculated observation record.

OM1 is required for the general observation definition. The optional MF_TEST_CALC_DETAIL group contains required OM6 for the derivation rule and required OM2 for numeric attributes such as units, precision, and ranges.

MFK_M01 is the practical companion when the publisher needs confirmation that the receiver accepted the calculated observation record.

Implementation traps

The big trap is hiding formula ownership. A calculated result without a clear derivation rule may be technically valid, but it is hard to support when clinicians compare values across systems.

Another trap is treating calculated observations as specimen-based tests. Some calculated observations depend on specimen results, but the calculated observation itself may not require collection. Be explicit about what should be ordered, what should be calculated, and what should only appear as a result.

Finally, keep numeric metadata in step with the rule. Changing the formula without reviewing units, reference ranges, critical ranges, and decimal precision is a tidy way to create untidy clinical confusion.

Reference notes

HL7 v2+ identifies M11 as the calculated observation master-file event. Its structure requires OM1 and can add OM6 for the derivation rule plus OM2 for numeric observation details.