^M02
MFN^M02 — Master File - Staff Practitioner
MFN^M02 synchronizes provider and staff master file data across systems. It carries practitioner demographics, credentials, specialties, and organizational relationships that downstream systems need for ordering provider lookups, result routing, and access control.
When Is This Sent?
When the provider/staff master file is updated — new physician onboarded, credentials change, provider leaves the organization, NPI number added. Sent from the provider master (HR/credentialing system) to all dependent systems.
Real-World Usage
Provider master file synchronization is critical for interfaces that use provider identifiers for result routing, ordering authority validation, and access control. PACS, LIS, and pharmacy systems need accurate provider records to route results to the correct physician. When providers join or leave, MFN^M02 ensures all systems are updated consistently. Without it, result routing failures and access control gaps accumulate over time.
Message Structure
Segment names link to their field-level reference pages.
| # | Segment | Purpose in this message | Req | Repeat |
|---|---|---|---|---|
| 1 | MSH | Message header with MFN^M02 in MSH.9 | R | — |
| 2 | MFI | Master file identification — identifies the staff practitioner file | R | — |
| 3 | MFE | Master file entry — action code (MAD/MDL/MUP) and provider ID key | R | Yes |
| 4 | STF | Staff identification and demographic data: provider ID, name, specialty, contact info | R | Yes |
| 5 | PRA | Practitioner detail: specialty, provider type, institution | O | Yes |
| 6 | ORG | Practitioner organization unit membership | O | Yes |
Example Message
Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.
1MSH||^~\&|PROVIDER_MASTER|HOSPITAL_A|EPIC|HOSPITAL_A|20260310070000||MFN^M02^MFN_M02|MFN00010|P|2.5.1 2MFI||PRA^Practitioner Master File^HL70175||UPD|||AL 3MFE||MAD|20260310070000|PROV-9876 4STF||PROV-9876^HOSPITAL_A|NPI12345678^^^NPI^NPI|Patel^Ravi^S^Dr.^MD|P|19720415|M||MD|20260301||9876^Radiology^RAD^HOSPITAL_A 5PRA||PROV-9876|||||RAD^Radiology^HL70487|ST
Troubleshooting Scenarios
New provider not found in PACS or LIS after onboarding
Cause
MFN^M02 was not sent to the PACS or LIS, or the STF.2 (staff identifier list) NPI format doesn't match the identifier the PACS uses for provider lookup.
Fix
Verify the MFN^M02 is being distributed to all dependent systems. Check STF.2 — ensure the NPI and local provider ID are both populated with the correct assigning authority codes. Confirm the PACS uses the same identifier type for provider matching.
Provider termination (MDL) causes historical results to lose provider attribution
Cause
MFE.1=MDL deletes the provider record entirely. Downstream systems that store the provider by reference now have a broken link for historical records.
Fix
Use MFE.1=MUP (update) with STF.9 (active/inactive indicator) set to inactive rather than deleting the record. This preserves provider identity for historical records while preventing the provider from being used in new orders or assignments.
Common Confusions
MFN^M02 (Staff/Practitioner) vs MFN^M01 (Generic). M02 is specifically for the practitioner master file and uses the STF/PRA/ORG segments. M01 is for any master file that doesn't have a specific event type. Use M02 when synchronizing provider demographics, credentials, and specialties. Also: MFN^M02 vs ADT^A08 — A08 updates patient demographics; M02 updates provider/staff data. They are fundamentally different master files.
Related Message Types
Segment Reference
Paste this message into our viewer
Interactive HL7 parser. Decodes every field, validates structure, highlights errors. Free, no signup.
Open HL7 Message Viewer →Need mapping templates?
The HL7 Integration Toolkit includes field mapping worksheets and interface spec templates for every major HL7 message type including MFN^M02.
View HL7 Integration Toolkit →