Communicates a problem-oriented clinical pathway for a patient. The PTH segment carries pathway details with nested problem, goal, and order groups. Care pathway management systems consume this.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'PPP^PCB^PPP_PCB|MSG001|P|2.9\r' \
'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
'PV1|1|I|MED^201^A'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_locationHow to construct, send, receive, and extract fields from real-world PPP^PCB messages.
Demonstrates receiving and extracting key fields from a pathway (problem-oriented) transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'PPP^PCB^PPP_PCB|MSG001|P|2.9\r' \
'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
'PV1|1|I|MED^201^A'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_locationStep-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||PPP^PCB^PPP_PCB|MSG00001|P|2.9\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201'
msg = HL7Message.parse(raw)
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birthBeyond the mandatory MSH header, the required segments are: PID, PRD, PV1, PTH, ROL, PRT, PRB, ROL. 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 PPP^PCB message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | ARV | Optional | Yes | Access restriction | - |
| 3 | SFT | Optional | Yes | Software segment | - |
| 4 | UAC | Optional | No | User authentication credential | - |
| 5 | PID | Required | No | Patient identification | - |
| 6 | PRD | Required | No | Provider data | PROVIDER |
| 7 | CTD | Optional | Yes | Contact data | PROVIDER |
| 8 | PV1 | Required | No | Patient visit | PATIENT_VISIT |
| 9 | PV2 | Optional | No | Patient visit - additional info | PATIENT_VISIT |
| 10 | PTH | Required | No | Pathway | PATHWAY |
| 11 | NTE | Optional | Yes | Notes and comments | PATHWAY |
| 12 | VAR | Optional | Yes | Variance | PATHWAY |
| 13 | ROL | Required | No | Role | PATHWAY |
| 14 | PRT | Required | No | Participation information | PATHWAY |
| 15 | VAR | Optional | Yes | Variance | PATHWAY |
| 16 | PRB | Required | No | Problem detail | PATHWAY |
| 17 | NTE | Optional | Yes | Notes and comments | PATHWAY |
| 18 | VAR | Optional | Yes | Variance | PATHWAY |
| 19 | ROL | Required | No | Role | PROBLEM_PARTICIPATION |
| 20 | PRT | Required | No | Participation information | PROBLEM_PARTICIPATION |
| 21 | VAR | Optional | Yes | Variance | PROBLEM_PARTICIPATION |
| 22 | OBX | Required | No | Observation result | PROBLEM_OBSERVATION |
| 23 | PRT | Optional | Yes | Participation information | PROBLEM_OBSERVATION |
| 24 | NTE | Optional | Yes | Notes and comments | PROBLEM_OBSERVATION |
| 25 | GOL | Required | No | Goal detail | GOAL |
| 26 | NTE | Optional | Yes | Notes and comments | GOAL |
| 27 | VAR | Optional | Yes | Variance | GOAL |
| 28 | ROL | Required | No | Role | GOAL |
| 29 | PRT | Required | No | Participation information | GOAL |
| 30 | VAR | Optional | Yes | Variance | GOAL |
| 31 | OBX | Required | No | Observation result | GOAL |
| 32 | PRT | Optional | Yes | Participation information | GOAL |
| 33 | NTE | Optional | Yes | Notes and comments | GOAL |
| 34 | ORC | Required | No | Common order | ORDER |
| 35 | NTE | Optional | Yes | Notes and comments | ORDER |
| 36 | VAR | Optional | Yes | Variance | ORDER |
| 37 | OBX | Required | No | Observation result | ORDER_OBSERVATION |
| 38 | PRT | Optional | Yes | Participation information | ORDER_OBSERVATION |
| 39 | NTE | Optional | Yes | Notes and comments | ORDER_OBSERVATION |
| 40 | VAR | Optional | Yes | Variance | ORDER_OBSERVATION |
Get started with Zato and connect your systems in minutes.