Reference·PD1 Segment·PD1-4
HL7 v2 Reference

PD1-4 in HL7 v2: A Field Guide to Patient Primary Care Provider Name & ID No.

Jul 28, 2026 · 4 min read
← PD1-3 PD1-11 →

PD1-4 is the field a care-coordination system reaches for when it needs to know who to notify about a patient's encounter — not the attending physician on this visit, but the provider who owns the relationship long-term.

Quick answer

PD1-4 is the Patient Primary Care Provider Name & ID No. field, a composite value carrying the provider's identifier, family name, given name, and credential. It identifies the clinician the patient is assigned to for ongoing care, and it's frequently used to trigger notifications or copy the primary care provider on encounter documentation.

What this field contains

Component 1
Provider ID — an internal identifier for the provider, e.g. 4521
Component 2
Family name — the provider's last name, e.g. WELLS
Component 3
Given name — the provider's first name, e.g. SARAH
Component 6
Prefix — credential or title, e.g. DR
Repeatability
Can repeat — some implementations allow more than one PD1-4 repetition when a patient has co-managing primary providers

Example

Synthetic example Generated by Synthibase
PD1|||SYNTHIB COMMUNITY CLINIC^^12345|4521^WELLS^SARAH^^^DR|||||||01^ONE PER PATIENT^SYNTHIBLOCAL|Y|20260101|||A|20260115

PD1-4 (4521^WELLS^SARAH^^^DR) identifies the patient's assigned primary care provider by ID and name components.

Where this trips people up

Test data often leaves PD1-4 either permanently populated with the same provider or permanently blank, which hides two real failure modes: notification logic that can't handle a missing primary care provider gracefully, and logic that assumes exactly one repetition when the implementation actually allows more. Provider reassignment is also rarely modeled — a patient switching primary care providers between messages is a routine production event that most test suites never generate.

Testing HL7 v2 PD1: The Fields Your System Actually Needs to Handle
How to Build a Synthetic Patient Registry for Healthcare Testing
HL7 ADT Messages: A01 through A08 Explained
Test provider assignment and reassignment logic
Synthibase varies primary care provider assignments across generated patients — including missing values and mid-history reassignments — so your care-coordination notifications get tested against realistic variation.
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.