Reference·PR1 Segment·PR1-4
HL7 v2 Reference

Testing HL7 v2 PR1-4: What Procedure Description Actually Needs to Handle

Jul 27, 2026 · 4 min read
← PR1-3 PR1-5 →

PR1-4 is meant to be a human-readable companion to the coded value in PR1-3, but nothing enforces that the two actually describe the same procedure. When they drift apart, whichever one a downstream screen displays becomes the version of the truth clinicians and coders see.

Quick answer

PR1-4 is the fourth field of the HL7 v2 PR1 segment — the Procedure Description, a free-text field giving a readable description of the procedure performed, intended to accompany the coded value carried in PR1-3.

What this field contains

free text
Description — a plain-language description of the procedure, entered or generated separately from the code lookup
length
Truncation risk — longer descriptions can get cut off by systems with fixed field-length limits
blank
Omitted description — valid when a system relies solely on the code in PR1-3 and its own lookup table for display text

Example

Synthetic example Generated by Synthibase
PR1|1||47562^LAPAROSCOPIC CHOLECYSTECTOMY^CPT|LAPAROSCOPIC REMOVAL OF GALLBLADDER VIA FOUR SMALL ABDOMINAL INCISIONS|20260726103000|P||8842^REYES^MONICA^L^^^MD

PR1-4 carries a free-text description of the procedure, distinct from and longer than the short label embedded in PR1-3. Synthetic record — not a real patient.

Where this trips people up

When a coder or surgeon amends the procedure description after the fact — say, adding detail about an unplanned finding — some systems update PR1-4 without touching PR1-3, or vice versa. A test suite that only checks each field in isolation will pass even though the two fields now describe subtly different procedures. Include test cases that verify both fields together after a documentation amendment, and confirm which field wins when a downstream display has to pick one.

HL7 v2 PR1 Segment Guide: Fields, Format, and Testing Gotchas
Regression Testing for EHR Upgrades: A Complete Guide
HL7 ADT Messages: A01 through A08 Explained
Keep procedure text and codes in sync across test data
Synthibase generates synthetic PR1 segments with descriptions that stay consistent with their coded values, so your tests catch real drift bugs instead of chasing synthetic ones.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.