Manages personnel records in the staff master file. The STF segment carries staff identification and demographic details. Human resources and credentialing systems consume this.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'PMU^B07^PMU_B07|MSG001|P|2.9\r' \
'STF|STF001||CHEN^DAVID^L|MD'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
staff_id = msg.stf.primary_key_value_stf
staff_name = msg.stf.staff_nameHow to construct, send, receive, and extract fields from real-world PMU^B07 messages.
Demonstrates receiving and extracting key fields from a add personnel record certificate transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'PMU^B07^PMU_B07|MSG001|P|2.9\r' \
'STF|STF001||CHEN^DAVID^L|MD'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
staff_id = msg.stf.primary_key_value_stf
staff_name = msg.stf.staff_nameStep-by-step guides for working with HL7 v2 in Zato.
Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.
from zato.hl7v2 import HL7Message
raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||PMU^B07^PMU_B07|MSG00001|P|2.9\rEVN|B07|20260401120000\rSTF|STF-001||CHEN^DAVID^L^^^MD|||M\rPRA|1234'
msg = HL7Message.parse(raw)
staff_id = msg.stf.primary_key_value_stf
staff_name = msg.stf.staff_nameBeyond the mandatory MSH header, the required segments are: EVN, STF, CER. Optional segments provide additional detail when available.
Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.
Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.
Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.
Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.
Segments that make up the PMU^B07 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | SFT | Optional | Yes | Software segment | - |
| 3 | UAC | Optional | No | User authentication credential | - |
| 4 | EVN | Required | No | Event type | - |
| 5 | STF | Required | No | Staff identification | - |
| 6 | PRA | Optional | No | Practitioner detail | - |
| 7 | CER | Required | No | Certificate detail | CERTIFICATE |
| 8 | PRT | Optional | Yes | Participation information | CERTIFICATE |
| 9 | ROL | Optional | Yes | Role | CERTIFICATE |
Get started with Zato and connect your systems in minutes.