HL7 MFN_M15 (Inventory Item Master File) | Integration Soup HL7 Reference Guide

HL7 MFN_M15 Inventory Item Master File

Limited inventory synchronization for orderable service items, lots, locations, and quantities.

HL7 message structure MFN_M15 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_M15.MF_INV_ITEM	Mf Inv Item group	Yes	Yes
MFE	Master File Entry	Yes	No
IIM	Inventory Item Master	Yes	No

MFN_M15 publishes inventory item master-file updates. In practice, this is the master-file message for item-specific inventory attributes: lot number, expiration date, manufacturer, location, received quantity, on-hand quantity, and related item cost.

It sits beside service-item catalog work such as MFN_M12. The service item says what can be ordered or used; the inventory item says which physical lots or quantities of that service item are currently known at a location.

A small MFN M15 example

MSH|^~\&|PHARMACY|CITYHOSP|DISPENSE|CITYHOSP|20260722121000||MFN^M15^MFN_M15|MFN150001|P|2.5.1 MFI|INV^Inventory master file^HL70175|PHARMACY^CITYHOSP|UPD|20260722121000|20260722123000|AL MFE|MAD|MFN150001|20260722123000|VACFLU2026A^Influenza vaccine lot 2026A^L|CWE IIM|VACFLU2026A^Influenza vaccine lot 2026A^L|VACFLU^Influenza vaccine dose^L|LOT2026A|20261231|ACMEVAC^Acme Vaccines^L|MAINPHARM^Main pharmacy^L|20260720|120|dose^dose^UCUM|18.50^USD|20260722|94|dose^dose^UCUM|90686^Influenza vaccine^CPT

What workflow it represents

The sender is usually a pharmacy system, supply system, dispensing cabinet, nurse-based dispensing system, or integration layer that owns inventory visibility. The receiver uses the feed to keep limited inventory facts synchronized for ordering, dispensing, administration, or operational checks.

MFN_M15 is not a full inventory-management transaction. It does not replace purchase orders, invoices, reorder points, PAR levels, or cycle counts. Its job is narrower: keep systems aligned on the inventory item attributes they need to safely use an orderable service item.

How to read the structure

MSH identifies the inventory notification. MFI identifies the inventory master file and file-level action. Each MF_INV_ITEM group starts with MFE, which carries the record-level action and primary key.

IIM is the required inventory item record. It carries the service item code, lot and expiration details, manufacturer, inventory location, received quantity, on-hand quantity, units, cost, and optional procedure coding.

If the receiver can reject one inventory record while accepting others, use MFK_M01 and log the record-level status.

Implementation traps

The first trap is treating MFN_M15 as an authoritative stock ledger. It is better understood as synchronization of limited inventory attributes between systems. If financial inventory, purchasing, or replenishment logic matters, another system usually owns that detail.

The second trap is forgetting the service-item relationship. A lot number without the service item code is not enough. The receiver needs to know which orderable or administrable item the lot belongs to.

Also be precise about units. "94" is only useful if both sides agree whether that means vials, doses, boxes, milliliters, or another unit.

Reference notes

HL7 v2+ describes M15 as an inventory item master-file message for item attributes such as lot number, expiration date, location, and quantity on hand. Its structure is MSH, optional SFT, MFI, and repeating MFE/IIM item records.