HL7 PMU_B03 (Delete Personnel Record) | Integration Soup HL7 Reference Guide

HL7 PMU_B03 Delete Personnel Record

Remove an erroneous personnel record, not just an unavailable practitioner.

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

PMU_B03 deletes a personnel record. In practice, this should be treated as a correction workflow for a record that should not exist or was created incorrectly. It is not the everyday way to say a provider is on leave, inactive, retired, or no longer accepting work.

That distinction matters because staff and provider identifiers often appear in historical orders, results, appointments, notes, claims, audit logs, and security records. Deleting a record can break lookup and audit trails if the receiver treats it as a hard purge.

A small PMU B03 example

MSH|^~\&|CREDENTIAL|CITYHOSP|EHR|CITYHOSP|20260721103000||PMU^B03^PMU_B03|PMU030001|P|2.5.1 EVN|B03|20260721103000|||ADM001^Admin^Avery STF|PRV999^CITYHOSP|PRV999^^^CITYHOSP^PRN|Testonly^Theo^^^^^L|P|||I

What workflow it represents

The sender is the personnel source that discovered the wrong record. The receiver is the system that previously accepted or created that personnel record. If the receiver cannot safely delete it because other records already reference it, it should return an application error in the acknowledgment instead of silently doing something else.

Many real sites prefer inactivation or termination workflows for former staff because they preserve history. PMU_B03 is best reserved for clerical mistakes, test records that leaked, duplicate shell records, or records created against the wrong person.

How to read the structure

The structure is intentionally small. MSH identifies the message, EVN identifies the delete event and timing, and STF identifies the staff record to delete.

There is no PRA, ORG, certificate, or language detail in the local PMU_B03 structure. The receiver should already know which record is being targeted from the identifier in STF. The response is normally an ACK with MSA and optional ERR.

Implementation traps

The first trap is using delete as a lazy inactive flag. If the staff member existed and did real work, hard deletion is usually wrong. Preserve the record and stop it from being selectable for new work instead.

The second trap is deleting by an identifier that is not qualified. If PRV999 is only meaningful inside one credentialing system, include the assigning authority. Otherwise two systems can honestly disagree about which record was meant.

Reference notes

HL7 v2+ describes B03 as deleting the healthcare-administration record for an individual practitioner to correct erroneous entries. That wording is a useful guardrail: deletion is for correction, not ordinary lifecycle management.