Reference·PV1 Segment·PV1-17
HL7 v2 Reference

HL7 v2 PV1-17 (Admitting Doctor): Format, Values, and Testing Notes

Jul 27, 2026 · 4 min read
← PV1-14 PV1-18 →

PV1-17 and PV1-7 both hold physician composites and sit close together in the segment, and it is a surprisingly common integration bug to map one into the field meant for the other — a mistake that looks fine in testing and then confuses clinicians reviewing the wrong "physician of record" on a chart.

Quick answer

PV1-17 is the seventeenth field of the PV1 segment — a composite (XCN data type) identifying the physician who admitted the patient, which may or may not be the same person as the attending doctor in PV1-7.

What this field contains

Component 1
ID Number of the admitting physician
Component 2
Family Name
Component 3
Given Name
Component 4
Middle Name or Initial
Component 6
Prefix, e.g. Dr.

Example

Synthetic example Generated by Synthibase
PV1|1|I|3W^301^B^HOSP|U|||445566^PATEL^RAJ^S^^MD|667788^JONES^MARY^E^^MD|889900^LEE^DAVID^R^^MD|CAR||||7|||998877^CHEN^LISA^K^^MD|I|8827364501|MCR||||||||||||||||01||||||||202607261430

The 17th field (998877^CHEN^LISA^K^^MD) names Dr. Lisa K. Chen as the admitting physician, distinct from the attending physician in field 7. Synthetic patient — not a real person.

Where this trips people up

Because the admitting and attending doctor are the same person for a large share of visits, it is easy for a mapping mistake between PV1-7 and PV1-17 to go unnoticed through months of testing and production use. It surfaces the first time a patient is admitted by an ED physician but has a different physician assigned as attending — and downstream systems start displaying or billing under the wrong name.

Testing HL7 v2 PV1: The Fields Your System Actually Needs to Handle
Healthcare Data Interoperability: A Practical Explainer for IT Leaders
Regression Testing for EHR Upgrades: A Complete Guide
Test admitting vs. attending doctor mapping
Synthibase generates synthetic PV1 segments where admitting and attending doctors intentionally differ — the exact case most test suites never exercise.
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.