HL7 MFN_M02 (Staff Practitioner Master File) | Integration Soup HL7 Reference Guide

HL7 MFN_M02 Staff Practitioner Master File

Provider and staff reference data for systems that need the same people list.

HL7 message structure MFN_M02 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
MFI	Master File Identification	Yes	No
MFN_M02.MF_STAFF	Mf Staff group	Yes	Yes
MFE	Master File Entry	Yes	No
STF	Staff Identification	Yes	No
PRA	Practitioner Detail	No	Yes
ORG	Practitioner Organization Unit	No	Yes
AFF	Professional Affiliation	No	Yes
LAN	Language Detail	No	Yes
EDU	Educational Detail	No	Yes
CER	Certificate Detail	No	Yes
NTE	Notes and Comments	No	Yes

MFN_M02 publishes staff or practitioner master-file entries. This is the sort of feed that keeps provider directories, ordering provider lists, scheduling systems, billing systems, and downstream clinical applications using the same identifiers and names.

The message can carry general staff identity in STF and practitioner-specific detail in PRA, with optional organization, affiliation, language, education, certificate, and note segments.

A small MFN M02 example

MSH|^~\&|PROVIDERDIR|CITYHOSP|EHR|CITYHOSP|20260718122000||MFN^M02^MFN_M02|MFN020001|P|2.5.1 MFI|PRACT^Practitioner master^HL70175|PROVIDERDIR^CITYHOSP|UPD|20260718122000|20260718130000|AL MFE|MAD|MFN020001|20260718130000|PRV123^CITYHOSP|CE STF|PRV123^CITYHOSP|PRV123^^^CITYHOSP^PRN|Nguyen^Mara^^^Dr^MD|P|F|19780512|A|ORTHO^Orthopedics^L||^WPN^PH^^64^9^5551212 PRA|PRV123^CITYHOSP|MD^Doctor of Medicine^L|ORTHO^Orthopedics^L ORG|1|ORTHO^Orthopedics^L|CITYHOSP^City Hospital^L LAN|1|eng^English^ISO639|P NTE|1||Updated practitioner directory entry.

What workflow it represents

The sender is usually a provider directory, HR/credentialing system, identity-management system, or integration engine that owns staff reference data. The receiver might be an EHR, LIS, RIS, billing platform, scheduling application, or interface engine that needs provider codes to be current.

The feed is often operationally important because other messages reference providers by identifier. If the provider master is stale, an otherwise valid order, result, appointment, or claim can fail lookup or land on the wrong user list.

How to read the structure

MSH identifies the notification. MFI identifies the practitioner master file. Each staff group starts with MFE, then carries STF as the main identity record.

PRA, ORG, AFF, LAN, EDU, CER, and NTE provide additional detail. In v2.5 and later, PRA and ORG can repeat, so do not assume the first one has a special meaning unless the profile says so.

Implementation traps

The classic trap is mapping provider by name. Names change, credentials change, and two people can look very similar. Use stable identifiers with assigning authorities, and map display names separately.

Another trap is not distinguishing inactive from deleted. A retired provider may need to remain valid for historical orders and results but disappear from new-order picklists.

Reference notes

The HL7 v2+ MFN_M02 page describes STF as the general personnel segment and PRA, ORG, AFF, LAN, EDU, CER, and NTE as detail segments for a staff member. It also notes that PRA and ORG repeats have no inherent first-instance meaning.