PMU: Add personnel record
This page lists the structures and trigger events PMU defines, taken from the standard. The written commentary that theADT page carries has not been written for PMU.
Recognising PMU messages
PMU announces itself in MSH-9 like this:
PMU^B01^PMU_B01- MSH-9.1
PMUmessage code: what kind of message this is - MSH-9.2
B01trigger event: what happened in the real world: add personnel record - MSH-9.3
PMU_B01message structure: which segments to expect, and in what order
How to use these specifications explains MSH-9 in full, with a worked example.
Message structures
PMU takes 5 structures. The first 4 are shown in full; the rest are listed below.
PMU_B01: Add Personnel Record
2 different trigger events send this structure:
The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate PMU_B02 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.
You must always send: MSH, EVN, STF. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | Message Header | R | 1..1 |
| SFT | Software | O | 0..* |
| EVN | Event Type | R | 1..1 |
| STF | Staff | R | 1..1 |
| PRA | Practitioner | O | 0..* |
| ORG | Organization | O | 0..* |
| AFF | Affiliation | O | 0..* |
| LAN | Language | O | 0..* |
| EDU | Education | O | 0..* |
| CER | Certificate | O | 0..* |
PMU_B03: Delete Personnel Record
Sent when one thing happens: B03: Delete Personnel Record.
PMU_B04: Activate Practicing Person
3 different trigger events send this structure:
The segments below are the same for all 3. HL7 varies the meaning, not the shape: there is no separate PMU_B05 layout. What changes is MSH-9, which tells the receiver which of the 3 happened and therefore what to do with the message.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | Message Header | R | 1..1 |
| SFT | Software | O | 0..* |
| EVN | Event Type | R | 1..1 |
| STF | Staff | R | 1..1 |
| PRA | Practitioner | O | 0..* |
| ORG | Organization | O | 0..* |
PMU_B07: Grant Certificate/Permission
Sent when one thing happens: B07: Grant Certificate/Permission.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | Message Header | R | 1..1 |
| SFT | Software | O | 0..* |
| EVN | Event Type | R | 1..1 |
| STF | Staff | R | 1..1 |
| PRA | Practitioner | O | 0..1 |
| CERTIFICATE | a group of 2 segments, repeated together | O | 0..* |
| CERin CERTIFICATE | Certificate | R | 1..1 |
| ROLin CERTIFICATE | Role | O | 0..* |
R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 1 such group: CERTIFICATE.
Other PMU structures
| Structure | Name | Events |
|---|---|---|
| PMU_B08 | Revoke Certificate/Permission | B08 |
Trigger events
The trigger event is the real-world thing that made the message get sent. PMU defines 8.
| Event | Name | Structure |
|---|---|---|
| B01 | Add Personnel Record | PMU_B01 |
| B02 | Update Personnel Record | PMU_B01 |
| B03 | Delete Personnel Record | PMU_B03 |
| B04 | Activate Practicing Person | PMU_B04 |
| B05 | Deactivate Practicing Person | PMU_B04 |
| B06 | Terminate Practicing Person | PMU_B04 |
| B07 | Grant Certificate/Permission | PMU_B07 |
| B08 | Revoke Certificate/Permission | PMU_B08 |