HL7 PMU_B04 (Active Practicing Person) | Integration Soup HL7 Reference Guide

HL7 PMU_B04 Active Practicing Person

Tell receivers this practitioner is available for work again.

HL7 message structure PMU_B04 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

PMU_B04 signals that a staff member or practitioner is active and available for work while maintaining a relationship with the institution. This is the message that turns a known person into someone the receiver may allow on schedules, provider lists, task routing, or order workflows.

It is different from adding a brand-new personnel record with PMU_B01. B04 is about practice availability and active status. A receiver may already know the staff member and only need to change whether that person can be selected for new operational work.

A small PMU B04 example

MSH|^~\&|CREDENTIAL|CITYHOSP|SCHED|CITYHOSP|20260721110000||PMU^B04^PMU_B04|PMU040001|P|2.5.1 EVN|B04|20260721110000|||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

What workflow it represents

The sender is usually credentialing, HR, provider-directory, or user-management logic. The receiver might be scheduling, order entry, an EHR provider file, a lab system, or a billing workflow that needs to know whether the provider can currently be used.

Receivers often use B04 to reopen operational paths: allow appointments to be booked, allow orders to name the provider, allow results to route to that person, or show the person on a picklist. Those downstream behaviors should be explicit in the interface agreement.

How to read the structure

EVN carries the event timing. STF identifies the staff member and carries the active/inactive flag. PRA and ORG can provide practitioner and organization unit context when activation depends on specialty, department, or role.

The receiver usually sends an ACK. If activation fails because a required department, specialty, provider type, or identifier is unknown, returning ERR detail is much kinder than quietly leaving the provider inactive.

Implementation traps

Do not treat "active" as one universal switch unless the receiver really works that way. A practitioner may be active in cardiology but not in orthopedics, active for scheduling but not ordering, or active in one facility but not another.

Also be careful when B04 follows a prior delete-like correction. If the target identifier no longer exists in the receiver, the right answer may be an error or a separate add workflow, not a silent create.

Reference notes

HL7 v2+ describes B04 as signaling that a staff member is available for work and has a relationship with the institution. The refactored page also shows STF as required, with optional PRA and ORG detail.