HL7 PMU_B07 (Grant Certificate Permission) | Integration Soup HL7 Reference Guide

HL7 PMU_B07 Grant Certificate or Permission

Credentialing detail for a specific practitioner permission.

HL7 message structure PMU_B07 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
PMU_B07.CERTIFICATE	Certificate group	No	Yes
CER	Certificate Detail	Yes	No
ROL	Role	No	Yes

PMU_B07 grants a certificate or permission to a health professional. In practical terms, it says this person now has a documented authorization for a special purpose: a license, privilege, certificate, approval, or other credential that a receiving system may need before allowing work.

This message is narrower than a full personnel add. The staff member is identified in STF, practitioner context can appear in PRA, and the authorization itself lives in CER. ROL can then describe roles that are pertinent to that certificate.

A small PMU B07 example

MSH|^~\&|CREDENTIAL|CITYHOSP|EHR|CITYHOSP|20260721113000||PMU^B07^PMU_B07|PMU070001|P|2.5.1 EVN|B07|20260721113000|||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 ROL|ROLE-ORTHO-1|AD|SURG^Orthopedic surgical privilege^L|PRV123^Nguyen^Mara^^^Dr^MD|20260721

What workflow it represents

The sender is usually credentialing, provider enrollment, medical staff office, or a provider-directory workflow. The receiver might be an EHR, scheduling system, operating-room system, ordering system, or another application that gates actions based on certificate, privilege, or role.

For example, a provider may exist in the directory but should not be scheduled for a procedure, shown as a signing clinician, or allowed in an ordering role until a specific permission is granted. PMU_B07 is the event that can move that credentialing fact into the receiver.

How to read the structure

EVN supplies the grant timing. STF identifies the staff member, and PRA optionally adds practitioner context.

The certificate group repeats. Each group has required CER certificate detail and optional ROL role detail. In the v2+ refactored pages, ROL is marked deprecated in later versions in favor of newer participation patterns, but it is still present in the v2.5.1 local structure.

Implementation traps

The first trap is granting a vague permission without a scope. The receiver needs to know whether the credential applies to a facility, department, service line, procedure family, role, or date range.

The second trap is updating an old permission in place without sending enough identity to match it. Certificate serial number, granting authority, practitioner identifier, and local role code should be preserved through mapping. Losing any one of those can turn one credential into several ambiguous rows.

Reference notes

HL7 v2+ describes B07 as granting a certificate or permission for a special purpose and notes that permission is documented as a certificate. The local v2.5.1 structure carries this as MSH, SFT, EVN, STF, optional PRA, then repeating certificate groups with CER and optional ROL.