HL7 PMU_B01 (Add Personnel Record) | Integration Soup HL7 Reference Guide

HL7 PMU_B01 Add Personnel Record

Create the healthcare practitioner relationship before other systems depend on it.

HL7 message structure PMU_B01 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
EVN	Event Type	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

PMU_B01 adds a personnel record for a healthcare practitioner or staff member. It is not a patient registration message, and it is not an order. It is personnel management: telling another system that this person now has an administrative relationship with the organization and can be identified by a stable staff or provider identifier.

You see this kind of message around credentialing, provider-directory synchronization, user-management feeds, scheduling, ordering-provider lists, and downstream applications that need to know which people can be selected, routed to, credited, or audited.

A small PMU B01 example

MSH|^~\&|CREDENTIAL|CITYHOSP|EHR|CITYHOSP|20260721100000||PMU^B01^PMU_B01|PMU010001|P|2.5.1 EVN|B01|20260721100000|||ADM001^Admin^Avery 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|D^Department^HL70474|Y|PRV123^^^CITYHOSP^PRN AFF|1|NZORTHO^NZ Orthopaedic Association^L|||Member LAN|1|eng^English^ISO639|P EDU|1|MD CER|1|CERT-ORTHO-2026|1|MEDCOUNCIL^Medical Council^L||||NZ|||LIC^Medical license^L|CLINICAL^Clinical privileges^L|PRV123|Nguyen Mara

What workflow it represents

The sender is usually a credentialing system, HR-style personnel source, provider directory, identity-management system, or integration engine. The receiver might be an EHR, scheduling application, order entry system, lab system, billing platform, or security/user directory that needs a staff record shell.

The practical boundary is important. A PMU_B01 can create the person and carry useful role, specialty, department, language, education, affiliation, and certificate data. It usually cannot configure every local preference, security template, ordering rule, inbox pool, or application-specific setting. Those often remain local build or separate workflow.

How to read the structure

MSH identifies the message. EVN gives the event and effective or planned timing. STF is the required staff identity segment, and it is where the stable identifier, name, active flag, department, and contact details usually begin.

PRA adds practitioner-specific detail. ORG carries organization unit detail, AFF professional affiliation, LAN language detail, EDU education, and CER certificates or permissions. Receivers usually acknowledge with ACK.

Implementation traps

The main trap is matching by name. Staff names, prefixes, credentials, and departments change. Use a stable staff identifier with assigning authority, then treat names and contact data as attributes of that identity.

Another trap is confusing PMU_B01 with MFN_M02. Both can carry staff/practitioner information, but PMU is event-driven personnel management while MFN is master-file synchronization. Pick the pattern that matches the business owner and the receiver's expectation.

Reference notes

HL7 v2+ describes PMU_B01 as adding a new healthcare-administration record for an individual practitioner and establishing the practitioner's relationship with the institution. The same source says EVN carries the effective or planned date.