HL7 MFE (Master File Entry) | Integration Soup HL7 Reference Guide

HL7 MFE Master File Entry

Master-file and catalog fields from experience.

HL7 field reference MFE 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

Field	Name	Required	Repeatable	Type	Table
MFE.1	Record-Level Event Code	Yes	No	ID	0180
MFE.2	MFN Control ID	No	No	ST
MFE.3	Effective Date/Time	No	No	TS
MFE.4	Primary Key Value - MFE	Yes	Yes	var	9999
MFE.5	Primary Key Value Type	Yes	Yes	ID	0355

MFE describes one master-file entry action, including the key value and effective timing.

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 MFE in MFN_M01 - Master file not otherwise specified, MFN_M02 - Master file - staff practitioner, MFN_M03 - Master file - test/observation, and MFN_M04 - Master files charge description, 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.

MFE-1 Record-Level Event Code RequiredR SingleS TypeID Table0180

MFE-1 identifies the Record-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 0180; many real interfaces narrow that list further, so follow the receiver's implementation guide.

MFE-2 MFN Control ID OptionalO SingleS TypeST

MFE-2 is part of the control identity for this master-file record. Make it stable enough for duplicate detection, retries, audit trails, and support conversations.

MFE-3 Effective Date/Time OptionalO SingleS TypeTS

MFE-3 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.

MFE-4 Primary Key Value - MFE RequiredR RepeatableR Typevar Table9999

MFE-4 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.

The generated panel links this to HL7 table 9999; many real interfaces narrow that list further, so follow the receiver's implementation guide.

MFE-5 Primary Key Value Type RequiredR RepeatableR TypeID Table0355

MFE-5 qualifies the master-file record rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.

Use the agreed value set, starting from HL7 table 0355. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.

HL7^® Reference Guide