Reference·PID Segment·PID-3
HL7 v2 Reference

PID-3 in HL7 v2: A Field Guide to Patient Identifier List

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

PID-3 is the field almost every downstream system keys off of, yet it is also one of the most misparsed — because it is a repeating field that can carry an MRN, an account number, and identifiers from other facilities all in the same message.

Quick answer

PID-3 is the third field of the HL7 v2 PID segment — a repeating list of patient identifiers, each with its own ID number, assigning authority, and identifier type code, most commonly the medical record number.

What this field contains

Component 1
ID Number (the actual identifier value)
Component 4
Assigning Authority (which system issued it)
Component 5
Identifier Type Code (e.g. MR, AN, SS)
~
Separator between repeated identifiers in the same field

Example

Synthetic example Generated by Synthibase
PID|1||847213609^^^HOSP^MR~55219847^^^HOSP^AN~19204837^^^REGIONALCLINIC^MR||GARCIA^ELENA^M||19870314|F|||482 OAK ST^^DENVER^CO^80202||3035550142|

Three identifiers are packed into PID-3, separated by ~: an MRN, an account number, and an MRN from a second facility. Synthetic patient — not a real person.

Where this trips people up

Interfaces built and tested against a single identifier per patient often hardcode "take the first repetition" logic. That works until a merged or referred patient arrives with identifiers from two facilities, and the system silently keeps the wrong one — or drops the identifier the receiving application actually needed to match on.

HL7 v2 PID Segment Guide: Fields, Format, and Testing Gotchas
How to Build a Synthetic Patient Registry for Healthcare Testing
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Generate realistic multi-identifier PID-3 values
Synthibase generates synthetic patients with multiple identifiers across facilities, so your matching logic gets tested against real-world identifier repetition, not just the happy path.
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.