The PID, PV1, and NK1 Segments in Clinical Context

When an ADT event arrives, the segments that follow the message header carry the actual clinical and administrative story: who the patient is, where they are, and who should be contacted on their behalf. Three segments do most of that work in patient administration messages — PID, PV1, and NK1. Each answers a distinct question, and each has a few fields that downstream systems lean on heavily.

PID — Who Is This Patient?

The Patient Identification (PID) segment establishes identity. Its most important field is PID-3, the patient identifier list. PID-3 is repeating and uses the CX data type, so each identifier carries not just a value but the assigning authority that issued it and an identifier type code that says what kind of number it is (for example, a medical record number, MRN). A bare number is meaningless without knowing who assigned it: the same digits can be an MRN at one hospital and a billing account elsewhere. Because PID-3 ties a person to the identifiers that every other system keys on, it is the linchpin of patient identity across the enterprise ¹.

The remaining demographics support and confirm that identity. PID-5 holds the patient name as an XPN, allowing family name, given name, and components like prefix or suffix. PID-7 carries the date of birth and PID-8 the administrative sex — both are classic tie-breakers when an identifier alone is ambiguous. PID-11 records the patient address as an XAD, used for correspondence, demographics matching, and regional reporting. Together these fields let a receiving system either find an existing record or, where supported, create a new one with confidence ².

PV1 — Where, and Under Whose Care?

The Patient Visit (PV1) segment describes the encounter rather than the person. PV1-2, patient class, classifies the visit — commonly Inpatient (I), Outpatient (O), or Emergency (E). This single coded value steers routing, billing, and clinical workflow, so an incorrect patient class can misdirect an entire encounter. PV1-3, the assigned location, gives the point of care: typically a nursing unit or ward, plus room and bed. PV1-7, PV1-8, and PV1-9 name the attending, referring, and consulting providers respectively, each as an XCN so the provider’s identifier and name travel together. PV1-19, the visit number, is the encounter-level identifier that links orders, results, and charges to this specific stay. In short, PV1 answers “where is the patient, and who is responsible for their care?” ²

NK1 — Who Should We Contact?

The Next of Kin / Associated Parties (NK1) segment records the people connected to the patient: their name, contact details, and — critically — their relationship to the patient. NK1 is repeating, so a message can list several associated parties. Its everyday use is the emergency contact, but the same segment can also convey guarantor or responsible-party context in some workflows, making it relevant to both clinical and financial follow-up ¹.

Reading a Real Example

Consider a short inpatient admission. The PID and PV1 might look like this:

PID|1||M00428671^^^STJOHNS^MR||DOE^JANE^Q||19840312|F|||742 EVERGREEN TER^^SPRINGFIELD^IL^62704
PV1|1|I|3W^312^A||||1742^SMITH^ROBERT^A^^^MD|0991^PATEL^ANIL^^^^MD|||||||||V20260418-0007

Walking the load-bearing fields: PID-3 is M00428671^^^STJOHNS^MR — the value M00428671, assigning authority STJOHNS, and identifier type MR (medical record number). PID-5 is the XPN DOE^JANE^Q; PID-7 is the DOB 19840312; PID-8 is F; PID-11 is the address. In PV1, PV1-2 is I (inpatient), PV1-3 is 3W^312^A (unit 3W, room 312, bed A), PV1-7 is the attending provider 1742^SMITH^ROBERT^A^^^MD, PV1-8 is the referring provider, and PV1-19 is the visit number V20260418-0007.

Why the Details Matter Operationally

These segments are only as useful as their identifying fields are complete. If PID-3 omits the assigning authority, a receiving system cannot safely tell whose MRN it is holding, and automated patient matching either fails or, worse, merges the wrong records ¹. If PV1-2 carries the wrong patient class, an outpatient visit can be processed as an inpatient stay — distorting clinical routing and producing incorrect charges. And a missing or inconsistent PV1-19 breaks the thread that links orders and results back to the right encounter. The fields described here are small, but they are exactly the ones that downstream matching, billing, and care coordination depend on ².