HL7 PMU_B08 (Revoke Certificate Permission) | Integration Soup HL7 Reference Guide

HL7 PMU_B08 Revoke Certificate or Permission

Remove a specific credential without erasing the practitioner.

HL7 message structure PMU_B08 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	No
CER	Certificate Detail	No	Yes

PMU_B08 revokes a certificate or permission for a health professional. It does not necessarily remove the person, and it does not necessarily make the person inactive everywhere. It says a particular credential, privilege, license, or permission is no longer valid.

That makes it operationally sensitive. A revoked permission might change whether a provider can be scheduled for a procedure, sign a result, prescribe in a category, order a service, or appear in a role-specific list. It should be handled deliberately and audibly.

A small PMU B08 example

MSH|^~\&|CREDENTIAL|CITYHOSP|EHR|CITYHOSP|20260721114500||PMU^B08^PMU_B08|PMU080001|P|2.5.1 EVN|B08|20260721114500|||CRED001^Credentialing^Casey STF|PRV123^CITYHOSP|PRV123^^^CITYHOSP^PRN|Nguyen^Mara^^^Dr^MD|P|F|19780512|A|ORTHO^Orthopedics^L PRA|PRV123^CITYHOSP|MD^Doctor of Medicine^L|ORTHO^Orthopedics^L CER|1|CERT-ORTHO-2026|1|MEDCOUNCIL^Medical Council^L||||NZ|||PRIV^Clinical privilege^L|ORTHO^Orthopedics^L|PRV123|Nguyen Mara||||||||||||||20260721|EXP^Expired^L|R^Revoked^L

What workflow it represents

The sender is usually the credentialing or provider-governance source. The receiver is the application that needs to stop using the permission. That may be a clinical system, a scheduling system, ordering workflow, role directory, or integration engine that routes staff-specific work.

Revocation should trigger review of downstream operational effects. If the permission controlled a picklist, access role, scheduling slot, or signing ability, the receiving system needs a clear rule for when the change takes effect and whether existing scheduled or pending work is affected.

How to read the structure

MSH and EVN identify the revocation event. STF identifies the staff member. PRA can add practitioner context.

The repeated CER segment identifies the certificate or permission being revoked. In a good implementation, CER should include enough certificate identity, issuer, subject, status, and revocation timing to match the receiver's stored credential rather than relying on a display label.

Implementation traps

Do not make revocation a person-level delete. A provider can lose one privilege and keep many others. Disable exactly the credential, role, or local capability that the message identifies.

Also avoid leaving already scheduled work in a mystery state. The interface agreement should say whether existing appointments, unsigned results, pending orders, or queued tasks remain valid, require reassignment, or need manual review.

Reference notes

HL7 v2+ describes B08 as revoking a certificate or permission for a health professional, with EVN used for the effective or planned date. The local v2.5.1 structure carries MSH, SFT, EVN, STF, optional PRA, and repeating CER details.