The PES (Product Experience Sender) segment identifies who is filing a product-experience report and when. It carries the sender organisation, the individual making the report, the sender-assigned event identifier, and metadata about the report's timing and source — everything a regulator needs to acknowledge receipt and chase follow-up.
Purpose
PES is the cover sheet for an adverse-event report. While PEO describes the observation and PCR names the product, PES answers who is telling us this, and when did they file? It supplies the chain of custody for the report, the sender's own tracking identifier, and a sequence number that allows initial, follow-up, and final reports to be linked by the receiving agency.
Used in
PES appears in product-experience / post-market surveillance PEX messages reporting adverse drug or device events to regulators such as the FDA, EMA, or MHRA. A PEX transaction contains exactly one PES per report instance, paired with one or more PEO/PCR groups.
Field-by-field
Each row below reflects the HAPI HL7 v2.5.1 javadoc for PES. Required fields are marked R; everything else is optional. Repeating fields are flagged Y. Data type names link to their reference page; lengths are not standardised at the segment level for v2.5.1 and are shown as "—".
| Seq | Name | Data Type | Length | Req | Repeat | Table # | Description |
|---|---|---|---|---|---|---|---|
| PES-1 | Sender Organization Name | xon | — | R | Y | — | Organisation submitting the report |
| PES-2 | Sender Individual Name | xcn | — | O | Y | — | Person within the sender organisation |
| PES-3 | Sender Address | xad | — | O | Y | — | Postal address of the sender |
| PES-4 | Sender Telephone | xtn | — | O | Y | — | Contact telephone for the sender |
| PES-5 | Sender Event Identifier | ei | — | O | — | — | Sender-assigned tracking identifier |
| PES-6 | Sender Sequence Number | nm | — | O | — | — | Ordinal for initial vs follow-up reports |
| PES-7 | Sender Event Description | ft | — | O | Y | — | Free-text summary supplied by sender |
| PES-8 | Sender Comment | ft | — | O | — | — | Additional sender comment or context |
| PES-9 | Sender Aware Date/Time | ts | — | O | — | — | When the sender first became aware |
| PES-10 | Event Report Date | ts | — | O | — | — | Date the report was generated |
| PES-11 | Event Report Timing/Type | id | — | O | Y | HL70234 | Initial, follow-up, or final report |
| PES-12 | Event Report Source | id | — | O | — | HL70235 | Source category of the report |
| PES-13 | Event Reported To | id | — | O | Y | HL70236 | Which agencies received the report |
Examples
Minimal
A PES with only the required sender organisation name.
PES|Riverford Cardiology^^L
Fully populated
PES|Riverford Cardiology^^L|Adekoya^Tomi^J^^Dr.|140 Clinic Way^^Riverford^OH^45402^USA|^WPN^PH^^^937^5550199|SE-2026-7741|1|Severe hypotension within 10 minutes of dose|Patient stable on discharge; awaiting cardiology follow-up|20260601090500|20260601120000|I|P|R
Annotated breakdown
PES
|Riverford Cardiology^^L PES-1 Sender organisation (required)
|Adekoya^Tomi^J^^Dr. PES-2 Sender individual
|140 Clinic Way^^Riverford^OH^45402 PES-3 Sender address
|^WPN^PH^^^937^5550199 PES-4 Sender telephone
|SE-2026-7741 PES-5 Sender event identifier
|1 PES-6 Sequence number (initial)
|Severe hypotension within 10 min... PES-7 Sender event description
|Patient stable on discharge... PES-8 Sender comment
|20260601090500 PES-9 Sender aware date/time
|20260601120000 PES-10 Event report date
|I PES-11 Report timing (Initial)
|P PES-12 Report source (Physician)
|R PES-13 Reported to (Regulator)
In context — PEX message excerpt 1
An initial report from a physician's office documenting an adverse cardiac event.
MSH|^~&|MEDWATCH|CLINIC-OH|FDA-AERS|FDA|20260601120000||PEX^P07^PEX_P07|MSG00012741|P|2.5.1
EVN|P07|20260601120000
PID|1||PT-44871^^^CLINIC-OH^MR||Okafor^Adaeze^M||19620318|F
PES|Riverford Cardiology^^L|Adekoya^Tomi^J^^Dr.|140 Clinic Way^^Riverford^OH^45402^USA|^WPN^PH^^^937^5550199|SE-2026-7741|1|Severe hypotension after first dose||20260601090500|20260601120000|I|P|R
PEO|AE-2026-7741^Severe Hypotension^L|R55^Syncope^I10|20260601084500||20260601094500|20260601110000||A|Y|N|R|R||Patient collapsed shortly after dose|||||||Adekoya^Tomi^J^^Dr.
In context — PEX message excerpt 2
A follow-up report from a manufacturer aggregating reporter narratives received after the initial filing.
MSH|^~&|SAFETY|VENDOR-MFR|FDA-AERS|FDA|20260612090000||PEX^P07^PEX_P07|MSG00013002|P|2.5.1
EVN|P07|20260612090000
PID|1||PT-44871^^^CLINIC-OH^MR||Okafor^Adaeze^M||19620318|F
PES|Helios Pharmaceuticals^^L|Petrov^Ivan^^^Mr.|1 Helios Plaza^^Cambridge^MA^02142^USA|^WPN^PH^^^617^5550172|SE-2026-7741-F1|2|Follow-up narrative from treating cardiologist|Causality assessment ongoing|20260610150000|20260612090000|F|M|R
PEO|AE-2026-7741^Severe Hypotension^L|R55^Syncope^I10|20260601084500||20260601094500|20260601110000||A|Y|N|R|R
Implementation notes
- PES-1 (Sender Organization Name) is the only strictly required field. In practice regulators expect PES-5 (Sender Event Identifier), PES-6 (Sender Sequence Number), and PES-11 (Event Report Timing/Type) to be present so that follow-ups can be linked.
- Use PES-5 consistently across initial and follow-up reports for the same case; increment PES-6 with each filing.
- PES-9 (Sender Aware Date/Time) is the clock from which most regulatory reporting deadlines run — keep it accurate even when the report is filed late.
- PES-2, PES-3, and PES-4 repeat so that a sender may include multiple contact persons; in regulatory practice list the primary case contact first.
Related segments
- PEO — describes the clinical observation that prompted the report.
- PCR — describes the product implicated in the experience.
- PEX message — the trigger event that carries PES end-to-end.
