HL7 MFA Master File Acknowledgment
HL7 field reference MFA 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 |
|---|---|---|---|---|---|
| MFA.1 | Record-Level Event Code | Yes | No | ID | 0180 |
| MFA.2 | MFN Control ID | No | No | ST | |
| MFA.3 | Event Completion Date/Time | No | No | TS | |
| MFA.4 | MFN Record Level Error Return | Yes | No | CE | 0181 |
| MFA.5 | Primary Key Value - MFA | Yes | Yes | var | 9999 |
| MFA.6 | Primary Key Value Type - MFA | Yes | Yes | ID | 0355 |
MFA acknowledges the result of applying a master-file entry update.
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 MFA in MFK_M01 - Master file not otherwise specified. 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.
MFA-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.
MFA-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.
MFA-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.
MFA-4 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 0181. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
MFA-5 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.
MFA-6 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.