Product experience sender

PES identifies the sender of a product experience report and carries the event identifier, sequence number, sender comments, awareness date, report date, timing type, and source. It is used in P07/P08 messages to establish the origin and submission timeline for regulatory adverse event reports.

The sender_event_identifier field uses the EI (entity identifier) datatype:

from zato.hl7v2.v2_9 import PES, EI

pes = PES()
pes.sender_event_identifier = EI(
    entity_identifier='EVT-2024-001',
    namespace_id='SENDER01'
)

The event_report_timing_type field uses HL7 table 0234 for report timing classification:

from zato.hl7v2.v2_9 import PES

pes = PES()

# 15D = 15 day report
pes.event_report_timing_type = '15D'

# 30D = 30 day report
pes.event_report_timing_type = '30D'

The event_report_source field uses HL7 table 0235 to identify who submitted the report:

from zato.hl7v2.v2_9 import PES

pes = PES()

# M = Manufacturer
pes.event_report_source = 'M'

# D = Distributor
pes.event_report_source = 'D'

Use the sender_aware_date_time DTM field to record when the sender first learned of the event:

from zato.hl7v2.v2_9 import PES

pes = PES()
pes.sender_aware_date_time = (
    '20240510'
)
pes.event_report_date = '20240601'

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.