HL7 MFI Master File Identification
HL7 field reference MFI fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
MFI identifies the master file being maintained and sets the file-level update context.
Master-file segments update reference data rather than describing a single patient event. They define locations, staff, providers, test catalogs, charge items, inventory items, languages, certificates, and other shared records.
Because many downstream messages depend on this data, small changes here can have large effects. Use stable identifiers, effective dates, action codes, and clear ownership rules instead of treating a master-file feed like a loose spreadsheet export.
The v2.5.1 structures show MFI in MFK_M01 - Master file not otherwise specified, MFN_M01 - Master file not otherwise specified, MFN_M02 - Master file - staff practitioner, and MFN_M03 - Master file - test/observation, and 17 other message structures. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
MFI-1 identifies the Master File Identifier for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0175; many real interfaces narrow that list further, so follow the receiver's implementation guide.
MFI-2 identifies the Master File Application Identifier for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0361; many real interfaces narrow that list further, so follow the receiver's implementation guide.
MFI-3 identifies the File-Level Event Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0178; many real interfaces narrow that list further, so follow the receiver's implementation guide.
MFI-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
MFI-5 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
MFI-6 identifies the Response Level Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0179; many real interfaces narrow that list further, so follow the receiver's implementation guide.
Related links
- MFE - Master File Entry
- MFA - Master File Acknowledgment
- LOC - Location Identification
- STF - Staff Identification
- PRA - Practitioner Detail
- OM1 - General Segment
- CDM - Charge Description Master
- MFK_M01 - Master file not otherwise specified
- MFN_M01 - Master file not otherwise specified
- MFN_M02 - Master file - staff practitioner