HL7 v2 PR1 Segment Guide: Fields, Format, and Testing Gotchas
PR1 carries the procedure that actually happened, not what was scheduled or ordered. Confuse those two and a billing feed can walk out the door claiming a patient had a laparoscopic procedure when the surgeon converted to open partway through the case.
PR1 (Procedures) is the repeating HL7 v2 segment that records a procedure performed on a patient, including its code, description, timing, and type. It typically shows up in ADT and DFT messages tied to inpatient or surgical encounters, with one PR1 segment per procedure performed during the visit.
The fields that actually matter in practice
Example
A synthetic PR1 segment for a laparoscopic gallbladder removal, showing the CPT-coded procedure, its performed date/time, a primary-procedure type flag, and the operating surgeon.
Where this trips people up
Teams frequently test PR1 using only the scheduled or planned procedure, then assume the field mapping is solid. In production, PR1-3 and PR1-4 have to reflect what actually happened, which can diverge from the pre-op plan — a laparoscopic case that converts to open, or a diagnostic procedure that becomes therapeutic mid-encounter. If the interface engine populates PR1 from an order-entry system snapshot instead of the post-procedure documentation, downstream billing systems end up coding for a procedure that never occurred. Test suites should include at least one case where the performed procedure differs from what was originally ordered, and verify PR1-6's type code correctly distinguishes primary from secondary procedures when a visit has more than one PR1 segment.