Reference·PR1 Segment·PR1-3
HL7 v2 Reference

HL7 v2 PR1-3 (Procedure Code): Format, Values, and Testing Notes

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

PR1-3 is the field billing, reporting, and quality-measure systems all key off of. Get the coding system component wrong and a perfectly valid procedure code can resolve to the wrong description — or nothing at all — on the receiving end.

Quick answer

PR1-3 is the third field of the HL7 v2 PR1 segment — the Procedure Code, a coded element (typically CPT or ICD-PCS) identifying the specific procedure performed, structured as code, text, and coding-system components.

What this field contains

component 1
Identifier — the actual procedure code value, such as a CPT or ICD-PCS code
component 2
Text — a short label associated with the code, often redundant with PR1-4 but not guaranteed to match
component 3
Coding system — names which code set the identifier belongs to, such as CPT or ICD-PCS — required to correctly interpret the code

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-3 carries 47562^LAPAROSCOPIC CHOLECYSTECTOMY^CPT — a CPT code for laparoscopic gallbladder removal. Synthetic record — not a real patient.

Where this trips people up

A common failure mode is an interface that populates the identifier and text components but leaves the coding-system component blank or defaults it incorrectly, assuming everything sent is CPT. When a facility later starts sending ICD-PCS codes for inpatient procedures alongside CPT codes for outpatient ones, a receiving system that ignores component 3 can look up a valid ICD-PCS identifier in a CPT table and either fail the lookup or, worse, silently map it to an unrelated CPT procedure that happens to share the numeric value. Always test with both coding systems represented, not just the one used in development.

HL7 v2 PR1 Segment Guide: Fields, Format, and Testing Gotchas
How to Reduce Claim Denials Through Better Pre-Submission Testing
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Generate realistic procedure codes across coding systems
Synthibase generates synthetic PR1 segments with correctly structured CPT and ICD-PCS codes, so your team can test coding-system handling before go-live.
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.