HL7 PEX_P07 (Initial Product Experience Report) | Integration Soup HL7 Reference Guide

HL7 PEX_P07 Initial Individual Product Experience Report

A product-safety report for a patient-level event, usually sent before the whole investigation is finished.

HL7 message structure PEX_P07 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
EVN	Event Type	Yes	No
PID	Patient Identification	Yes	No
PD1	Patient Additional Demographic	No	No
NTE	Notes and Comments	No	Yes
PEX_P07.VISIT	Visit group	No	No
PV1	Patient Visit	Yes	No
PV2	Patient Visit - Additional Information	No	No
PEX_P07.EXPERIENCE	Experience group	Yes	Yes
PES	Product Experience Sender	Yes	No
PEX_P07.PEX_OBSERVATION	Pex Observation group	Yes	Yes
PEO	Product Experience Observation	Yes	No
PEX_P07.PEX_CAUSE	Pex Cause group	Yes	Yes
PCR	Possible Causal Relationship	Yes	No
PEX_P07.RX_ORDER	Rx Order group	No	No
RXE	Pharmacy/Treatment Encoded Order	Yes	No
PEX_P07.TIMING_QTY	Timing Quantity group	Yes	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
RXR	Pharmacy/Treatment Route	No	Yes
PEX_P07.RX_ADMINISTRATION	Rx Administration group	No	Yes
RXA	Pharmacy/Treatment Administration	Yes	No
RXR	Pharmacy/Treatment Route	No	No
PRB	Problem Details	No	Yes
OBX	Observation/Result	No	Yes
NTE	Notes and Comments	No	Yes
PEX_P07.ASSOCIATED_PERSON	Associated Person group	No	No
NK1	Next of Kin / Associated Parties	Yes	No
PEX_P07.ASSOCIATED_RX_ORDER	Associated Rx Order group	No	No
RXE	Pharmacy/Treatment Encoded Order	Yes	No
PEX_P07.NK1_TIMING_QTY	Nk1 Timing Quantity group	Yes	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
RXR	Pharmacy/Treatment Route	No	Yes
PEX_P07.ASSOCIATED_RX_ADMIN	Associated Rx Admin group	No	Yes
RXA	Pharmacy/Treatment Administration	Yes	No
RXR	Pharmacy/Treatment Route	No	No
PRB	Problem Details	No	Yes
OBX	Observation/Result	No	Yes
PEX_P07.STUDY	Study group	No	Yes
CSR	Clinical Study Registration	Yes	No
CSP	Clinical Study Phase	No	Yes

PEX_P07 is an unsolicited initial individual product experience report. It is part of HL7 v2's product experience reporting family and is used for safety, complaint, and adverse-event style workflows rather than routine clinical care exchange.

The sender may be a hospital safety office, pharmacy system, device tracking system, or product surveillance gateway. The receiver may be a manufacturer, regulator-facing system, sponsor, or internal safety database.

A small PEX P07 example

MSH|^~\&|SAFETY|CITYHOSP|MFR|REMOTE|20260718130000||PEX^P07^PEX_P07|PEXP070001|P|2.5.1 EVN|P07|20260718130000 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F PES|CITYHOSP^City Hospital|7788^Safety^Sam|||EVT-7788^CITYHOSP|1|Suspected medication reaction||20260718110000|20260718130000|I|H PEO|REACT1^Reaction^L|RASH^Rash^L|20260718103000|||||Y|N|U|R PCR|AMOX500^Amoxicillin 500 mg capsule^L|||||||||INF^Infection treatment^L|REACTION^Suspected reaction^L|LOT12345 RXE|^^^20260718100000|AMOX500^Amoxicillin 500 mg capsule^L|1|CAP^capsule^UCUM TQ1|1|||TID^Three times daily^HL70335 RXR|PO^Oral^HL70162 OBX|1|ST|NARRATIVE^Narrative^L||Rash observed after first dose; clinician notified.||||||F

What systems do with it

The receiver usually creates or updates a product experience case. The message gives the sender, patient, event observation, suspected causal product, medication or administration details, and supporting observations. A later follow-up message may add investigation results or corrected details.

Unlike an ORU_R01, this is not mainly a result delivery message. It is a safety-event envelope. The product, causal relationship, report timing, and case identifiers are the parts that usually drive downstream workflow.

How to read the structure

MSH and EVN identify the unsolicited P07 event. PID, optional PD1, optional PV1, and optional PV2 identify the person and encounter.

PES identifies the sender and report. PEO describes the product experience observation. PCR describes the possible causal relationship. Medication-related details may appear in RXE, RXA, RXR, TQ1, and TQ2. Supporting findings can appear in OBX and NTE.

Implementation traps

Do not use PEX_P07 as a free-form incident note. The receiver needs structured identifiers for the product, reporter, event, suspected relationship, and lot or device details where known. Narrative is useful, but it should not be the only place the case can be understood.

Also be careful with certainty. Early product experience reports often contain suspected relationships, not proven causality. Keep local status, follow-up, and replacement rules explicit.

Reference notes

The HL7 product experience reporting family includes PEX_P07 for an unsolicited initial individual product experience report. This guide treats it as a specialized safety-reporting message and links the main segments so you can inspect their field-level structure.