Reference·PR1 Segment·PR1-10
HL7 v2 Reference

Understanding HL7 v2 PR1-10: Surgeon in Practice

Jul 27, 2026 · 4 min read
← PR1-6

PR1-10 is the only field in the PR1 segment dedicated to who actually performed the procedure, as opposed to who ordered it or who's attending the patient. Systems that fall back to the attending provider when PR1-10 is missing end up crediting procedures to physicians who never picked up an instrument.

Quick answer

PR1-10 is the tenth field of the HL7 v2 PR1 segment — the Surgeon, an extended composite ID identifying the provider who performed the procedure, separate from the ordering provider or attending physician carried elsewhere in the message.

What this field contains

component 1
ID number — the provider's identifier, such as an internal or national provider ID
components 2-4
Name — last name, first name, and middle initial of the surgeon
component 7
Degree — a credential suffix like MD or DO, when included

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-10 carries 8842^REYES^MONICA^L^^^MD, identifying the surgeon by ID, name, and credential. Synthetic provider — not a real person.

Where this trips people up

In teaching or co-surgery cases, more than one provider may be involved in a single procedure, but PR1-10 only carries one surgeon per PR1 segment. Some source systems handle this by repeating the field, others by adding a second PR1 with the same procedure code and a different surgeon, and others simply drop the second provider entirely. If your test suite only ever exercises the single-surgeon case, you won't catch which behavior your interface actually implements until a co-surgery case hits production and a provider's productivity report comes up short. Test multi-surgeon scenarios explicitly and confirm how your system reconciles them.

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
Test provider attribution edge cases
Synthibase generates synthetic PR1 segments covering single- and multi-surgeon scenarios, so you can validate provider attribution logic before it affects real productivity or billing reports.
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.