HL7 v2 NK1 Segment Guide: Fields, Format, and Testing Gotchas

Jul 27, 2026 · 6 min read

NK1 looks like a simple contact-info segment until a repeating instance for the guarantor collides with one for the emergency contact, and your parser has to figure out which is which without a hint from the segment name itself.

Quick answer

NK1 (Next of Kin / Associated Parties) carries one person or organization tied to the patient beyond the patient themselves — a spouse, an emergency contact, a guarantor, an employer. A single ADT or registration message can carry multiple NK1 segments, one per associated party, and NK1-1 is what tells a receiving system which repetition it is looking at.

The fields that actually matter in practice

NK1-1 →

Set ID — sequence number distinguishing repeating NK1 instances; systems that ignore it often overwrite one contact with another

NK1-2 →

Name — the associated party's name, in the same component structure as PID-5; frequently arrives with only a last name populated

NK1-3 →

Relationship — coded relationship to the patient (spouse, parent, guardian, employer); the code table in use varies more between vendors than teams expect

NK1-4 →

Address — mailing address for the contact, structurally identical to PID-11 but almost never validated as strictly

NK1-5 →

Phone Number — home or primary contact number; a common source of malformed area codes and missing country codes in test data

NK1-7 →

Contact Role — distinguishes what the person does — emergency contact, next of kin, guarantor — separately from their family relationship

Example

Synthetic example Generated by Synthibase

NK1|1|DOE^JANE^M|SPO|482 OAK ST^^DENVER^CO^80202|3035550142|||EC

A synthetic NK1 segment for a spouse listed as an emergency contact — invented for this example, not from any real patient or facility.

Where this trips people up

The most common failure mode isn't a malformed field, it's an assumption about cardinality. Teams build test fixtures with exactly one NK1 segment and never exercise the path where three repeat, or where two NK1 segments describe the same person in two different roles (next of kin and guarantor). When a real feed sends four NK1 repetitions and your test suite has only ever seen one, the bugs show up in production registration screens instead of in CI.

→

HL7 ADT Messages: A01 through A08 Explained

→

How to Build a Synthetic Patient Registry for Healthcare Testing

Test NK1 repetitions without touching real patient data

Synthibase generates ADT and registration messages with realistic, varied NK1 repetitions — multiple contacts, roles, and relationship codes — so your parser gets exercised before go-live, not after.

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.