HL7 PCR Possible Causal Relationship
HL7 field reference PCR fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| PCR.1 | Implicated Product | Yes | No | CE | |
| PCR.2 | Generic Product | No | No | IS | 0249 |
| PCR.3 | Product Class | No | No | CE | |
| PCR.4 | Total Duration Of Therapy | No | No | CQ | |
| PCR.5 | Product Manufacture Date | No | No | TS | |
| PCR.6 | Product Expiration Date | No | No | TS | |
| PCR.7 | Product Implantation Date | No | No | TS | |
| PCR.8 | Product Explantation Date | No | No | TS | |
| PCR.9 | Single Use Device | No | No | IS | 0244 |
| PCR.10 | Indication For Product Use | No | No | CE | |
| PCR.11 | Product Problem | No | No | IS | 0245 |
| PCR.12 | Product Serial/Lot Number | No | Yes | ST | |
| PCR.13 | Product Available For Inspection | No | No | IS | 0246 |
| PCR.14 | Product Evaluation Performed | No | No | CE | |
| PCR.15 | Product Evaluation Status | No | No | CE | 0247 |
| PCR.16 | Product Evaluation Results | No | No | CE | |
| PCR.17 | Evaluated Product Source | No | No | ID | 0248 |
| PCR.18 | Date Product Returned To Manufacturer | No | No | TS | |
| PCR.19 | Device Operator Qualifications | No | No | ID | 0242 |
| PCR.20 | Relatedness Assessment | No | No | ID | 0250 |
| PCR.21 | Action Taken In Response To The Event | No | Yes | ID | 0251 |
| PCR.22 | Event Causality Observations | No | Yes | ID | 0252 |
| PCR.23 | Indirect Exposure Mechanism | No | Yes | ID | 0253 |
PCR records a possible causal relationship between a product and an event.
The standard describes PCR this way: The PCR segment is used to communicate a potential or suspected relationship between a product (drug or device) or test and an event with detrimental effect on a patient. This segment identifies a potential causal relationship between the product identified in this segment and the event identified in the PEO segment. More than one PCR segment can be included in the message if more than one product is possibly causally related to the event.
Product experience segments support adverse-event, product-quality, exposure, and regulatory-style reporting. They connect the product, sender, observation, possible causal relationship, and summary details.
The goal is traceability. Dates, product identifiers, manufacturer details, event descriptions, seriousness, and relationship assessments need to remain tied together so reviewers can understand the chain.
The v2.5.1 structures show PCR in PEX_P07 - PEX - Unsolicited initial individual product experience report. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
PCR-1 carries Implicated Product for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
PCR-2 carries Generic Product for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0249; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-3 qualifies the product-safety report rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
PCR-4 is used for reconciliation. The receiver may compare it with the segments, batches, messages, rows, or items actually received, so do not populate it from a stale estimate.
PCR-5 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PCR-6 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
PCR-7 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PCR-8 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PCR-9 helps identify the product, software, device, or equipment involved. It is particularly useful when support needs to trace behaviour back to a specific build, lot, instrument, or manufacturer.
The generated panel links this to HL7 table 0244; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-10 carries Indication For Product Use for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
PCR-11 is clinical or administrative context for the product-safety report. Use the coded value, lifecycle status, and timing fields together so a receiver can decide whether it is new, changed, resolved, cancelled, or historical.
The generated panel links this to HL7 table 0245; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-12 identifies the Product Serial/Lot Number for this product-safety report. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
PCR-13 carries Product Available For Inspection for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0246; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-14 carries Product Evaluation Performed for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
PCR-15 tells the receiver the state of this product-safety report. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0247 or the narrower table in the local profile.
PCR-16 carries Product Evaluation Results for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
PCR-17 carries Evaluated Product Source for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0248; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-18 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
PCR-19 helps identify the product, software, device, or equipment involved. It is particularly useful when support needs to trace behaviour back to a specific build, lot, instrument, or manufacturer.
The generated panel links this to HL7 table 0242; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-20 carries Relatedness Assessment for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0250; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-21 says what action is being taken for this segment or record: add, update, delete, cancel, clear, or another profile-defined operation. It needs to agree with the message trigger and the previous state.
The generated panel links this to HL7 table 0251; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-22 carries Event Causality Observations for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0252; many real interfaces narrow that list further, so follow the receiver's implementation guide.
PCR-23 carries Indirect Exposure Mechanism for this product-safety report. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0253; many real interfaces narrow that list further, so follow the receiver's implementation guide.