Schedule a demo
Message type

Problem

Communicates patient problem information for clinical tracking. The PRB segment carries the problem details and associated goal, order, and observation groups provide context. Problem list management systems consume this.

36segments
15required
6groups
v2.9HL7 version
ppr-pc1.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'PPR^PC1^PPR_PC1|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_location

Build and parse PPR^PC1 messages in Python

How to construct, send, receive, and extract fields from real-world PPR^PC1 messages.

1

Parse an incoming PPR^PC1 message

Demonstrates receiving and extracting key fields from a problem transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'PPR^PC1^PPR_PC1|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_location

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

Frequently asked questions

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||PPR^PC1^PPR_PC1|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_birth

Beyond the mandatory MSH header, the required segments are: PID, PRD, PV1, PRB, ROL, PRT, PTH, OBX. 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.

PPR^PC1 segment composition

Segments that make up the PPR^PC1 message, in order. Groups are shown with their child segments.

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5PIDRequiredNoPatient identification-
6PRDRequiredNoProvider dataPROVIDER
7CTDOptionalYesContact dataPROVIDER
8PV1RequiredNoPatient visitPATIENT_VISIT
9PV2OptionalNoPatient visit - additional infoPATIENT_VISIT
10PRBRequiredNoProblem detailPROBLEM
11NTEOptionalYesNotes and commentsPROBLEM
12VAROptionalYesVariancePROBLEM
13ROLRequiredNoRolePROBLEM
14PRTRequiredNoParticipation informationPROBLEM
15VAROptionalYesVariancePROBLEM
16PTHRequiredNoPathwayPROBLEM
17VAROptionalYesVariancePROBLEM
18OBXRequiredNoObservation resultPROBLEM
19PRTOptionalYesParticipation informationPROBLEM
20NTEOptionalYesNotes and commentsPROBLEM
21GOLRequiredNoGoal detailPROBLEM
22NTEOptionalYesNotes and commentsPROBLEM
23VAROptionalYesVariancePROBLEM
24ROLRequiredNoRoleGOAL_PARTICIPATION
25PRTRequiredNoParticipation informationGOAL_PARTICIPATION
26VAROptionalYesVarianceGOAL_PARTICIPATION
27OBXRequiredNoObservation resultGOAL_OBSERVATION
28PRTOptionalYesParticipation informationGOAL_OBSERVATION
29NTEOptionalYesNotes and commentsGOAL_OBSERVATION
30ORCRequiredNoCommon orderPROBLEM
31NTEOptionalYesNotes and commentsORDER_DETAIL
32VAROptionalYesVarianceORDER_DETAIL
33OBXRequiredNoObservation resultORDER_DETAIL
34PRTOptionalYesParticipation informationORDER_DETAIL
35NTEOptionalYesNotes and commentsORDER_DETAIL
36VAROptionalYesVarianceORDER_DETAIL

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python