Schedule a demo
Message type

Unsolicited initial individual product experience report

Reports an initial individual product experience (adverse event) to a safety monitoring system. The PES segment identifies the sender and PEO segments carry the product experience observations.

42segments
17required
7groups
v2.9HL7 version
pex-p07.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'PEX^P07^PEX_P07|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 PEX^P07 messages in Python

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

1

Parse an incoming PEX^P07 message

Demonstrates receiving and extracting key fields from a unsolicited initial individual product experience report transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'PEX^P07^PEX_P07|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||PEX^P07^PEX_P07|MSG00001|P|2.9\rEVN|P07|20260401120000\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPD1|||Family Health Clinic^^12345\rPRT|1||AT^Attending||1234^CHEN^DAVID^L^^^MD'
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: EVN, PID, PV1, PES, PEO, PCR, RXE, TQ1. 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.

PEX^P07 segment composition

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

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5EVNRequiredNoEvent type-
6PIDRequiredNoPatient identification-
7PD1OptionalNoPatient additional demographic-
8PRTOptionalYesParticipation information-
9ARVOptionalYesAccess restriction-
10NTEOptionalYesNotes and comments-
11PV1RequiredNoPatient visitVISIT
12PV2OptionalNoPatient visit - additional infoVISIT
13PRTOptionalYesParticipation informationVISIT
14PESRequiredNoProduct experience senderEXPERIENCE
15PEORequiredNoProduct experience observationEXPERIENCE
16PCRRequiredNoPossible causal relationshipPEX_CAUSE
17RXERequiredNoPharmacy / treatment encoded orderPEX_CAUSE
18PRTOptionalYesParticipation informationPEX_CAUSE
19TQ1RequiredNoTiming / quantityTIMING_QTY
20TQ2OptionalYesTiming / quantity relationshipTIMING_QTY
21RXROptionalYesPharmacy / treatment routePEX_CAUSE
22RXARequiredNoPharmacy / treatment administrationPEX_CAUSE
23RXROptionalNoPharmacy / treatment routePEX_CAUSE
24PRTOptionalYesParticipation informationPEX_CAUSE
25PRBOptionalYesProblem detailPEX_CAUSE
26OBXRequiredNoObservation resultPEX_CAUSE
27PRTOptionalYesParticipation informationPEX_CAUSE
28NTEOptionalYesNotes and commentsPEX_CAUSE
29NK1RequiredNoNext of kin / associated partiesPEX_CAUSE
30RXERequiredNoPharmacy / treatment encoded orderASSOCIATED_RX_ORDER
31PRTOptionalYesParticipation informationASSOCIATED_RX_ORDER
32TQ1RequiredNoTiming / quantityASSOCIATED_RX_ORDER
33TQ2OptionalYesTiming / quantity relationshipASSOCIATED_RX_ORDER
34RXROptionalYesPharmacy / treatment routeASSOCIATED_RX_ORDER
35RXARequiredNoPharmacy / treatment administrationASSOCIATED_RX_ADMIN
36RXROptionalNoPharmacy / treatment routeASSOCIATED_RX_ADMIN
37PRTOptionalYesParticipation informationASSOCIATED_RX_ADMIN
38PRBOptionalYesProblem detailPEX_CAUSE
39OBXRequiredNoObservation resultASSOCIATED_OBSERVATION
40PRTOptionalYesParticipation informationASSOCIATED_OBSERVATION
41CSRRequiredNoClinical study registrationPEX_CAUSE
42CSPOptionalYesClinical study phasePEX_CAUSE

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python