visit the hl7 website The Demo site for our new HL7 Version 2+ (plus) Standard

18.4.89 MFN/MFK - Inventory Item Master File Message - Enhanced (Event M16) (8.12.2)

This section describes a master file message designed to communicate information that relates to the sharing of material item master catalog and material item-inventory information between materials management systems and other systems such as surgical and immunization systems. The synchronization of the "item master" between systems and across the enterprise enables the success of the subsequent interfacing of transactions such as: material item requisitions (pre and post case), accounts payable invoices for the payment of material items, journal entries generated from the issue of items to departments or other inventory locations, and patient charges that allow a customer to improve patient care through the better management of materials. To face budget challenges, healthcare organizations need materials management systems that integrate with finance to automate logistics, eliminate paperwork and analyze data to improve efficiency and reduce overall costs. This process is a major contributor to improving the customers' bottom line by helping to eliminate materials waste, streamline ordering, ensure accurate payment of materials purchased, ensure accurate billing for materials used, and an accurate presentation of the financial statements of a healthcare facility.

Material items defined in this message include consumable supplies, devices, surgical sets, and implants.

Each MFE/ITM structure describes a set of attributes, specific to a material item existing in an item master catalog. The PCE and NTE segments are optional and repeating, associated with the item referred to in the ITM segment. An item may be linked to many patient charge exception combinations.

Each VND/PKG segment grouping includes the available vendors and packaging information valid for the item referred to in the ITM segment. An item may be associated with many vendors. A vendor may be linked to many packaging configurations. Therefore the vendor segment can repeat and can include a repeating PKG segment within each repetition of the vendor segment.

Each MFE/ITM/IVT structure describes a set of attributes specific to the inventory locations associated with the item referred to in the associated ITM segment. An inventory item can exist in more than one inventory location with different values for the same attributes, therefore, this segment repeats.

The ILT segment describes lot and quantity information for a material product. In the message structure, this segment is directly associated with the IVT segment, thus the lot/quantity information is always related to a location. Repetition of the ILT segment supports the case where more than one lot of a material product may exist in an inventory location.

Note that the quantities in the ILT segment are not necessarily intended to refer to continuously updated inventory quantities. The expectation is that periodic inventory quantities would be updated with subsequent master file messages. This segment can be used for interfacing, for example, Immunization information.

Additional specialized information segments may be defined as additional use cases are defined, such as medication/drug segments.

Segment Cardinality Implement Status
MFN^M16^MFN_M16
MSH

Message Header

[1..1] SHALL
SFT

Software Segment

 
MFI

Master File Identification

[1..1] SHALL
MATERIAL_ITEM_RECORD [1..*] SHALL
MFE

Master File Entry

[1..1] SHALL
ITM

Material Item

[1..1] SHALL
NTE

Notes and Comments

 
STERILIZATION  
STZ

Sterilization Parameter

[1..1] SHALL
NTE

Notes and Comments

 
PURCHASING_VENDOR  
VND

Purchasing Vendor

[1..1] SHALL
PACKAGING  
PKG

Item Packaging

[1..1] SHALL
PCE

Patient Charge Cost Center Exceptions

 
MATERIAL_LOCATION  
IVT

Material Location

[1..1] SHALL
ILT

Material Lot

 
NTE

Notes and Comments

 

 

MFN_M16

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank - MFK^M16^MFK_M01
NE NE - -
AL, SU, ER NE ACK^M16^ACK -
NE AL, SU, ER - MFK^M16^MFK_M01
AL, SU, ER AL, SU, ER ACK^M16^ACK MFK^M16^MFK_M01
We need some ER7 examples...
We need some XML examples...
Segment Cardinality Implement Status
MFK^M16^MFK_M01
MSH

Message Header

[1..1] SHALL
SFT

Software Segment

 
MSA

Message Acknowledgment

[1..1] SHALL
ERR

Error

 
MFI

Master File Identification

[1..1] SHALL
MFA

Master File Acknowledgment

 

 

MFK_M01

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank ACK^M15^ACK -
Blank Blank - -
Blank Blank - -
Blank Blank ACK^M04^ACK -
Blank Blank - -
Blank Blank ACK^M06^ACK -
Blank Blank - -
Blank Blank ACK^M07^ACK -
Blank Blank - -
Blank Blank ACK^M05^ACK -
Blank Blank - -
Blank Blank ACK^M16^ACK -
Blank Blank - -
Blank Blank ACK^M17^ACK -
Blank Blank - -
Blank Blank - -
Blank Blank - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
NE NE - -
AL, SU, ER NE ACK^M13^ACK -
AL, SU, ER NE ACK^M19^ACK -
AL, SU, ER NE ACK^M14^ACK -
AL, SU, ER NE ACK^M17^ACK -
AL, SU, ER NE ACK^M02^ACK -
AL, SU, ER NE ACK^M16^ACK -
AL, SU, ER NE ACK^M08^ACK -
AL, SU, ER NE ACK^M18^ACK -
AL, SU, ER NE ACK^M09^ACK -
AL, SU, ER NE ACK^M07^ACK -
AL, SU, ER NE ACK^M10^ACK -
AL, SU, ER NE ACK^M06^ACK -
AL, SU, ER NE ACK^M11^ACK -
AL, SU, ER NE ACK^M04^ACK -
AL, SU, ER NE ACK^M12^ACK -
AL, SU, ER NE ACK^M05^ACK -
AL, SU, ER NE ACK^M15^ACK -
NE AL, SU, ER - -
AL, SU, ER AL, SU, ER ACK^M19^ACK -
We need some ER7 examples...
We need some XML examples...

Master Files Query Response: Refer to Section 8.4.4.