HL7 v2 NK1-2 (Name): Format, Values, and Testing Notes
A next-of-kin record with only a family name and no given name is valid HL7 — and it's exactly the kind of input that crashes a display screen built assuming a first and last name always show up.
NK1-2 holds the associated party's name using the same extended person name (XPN) component structure as the patient name field, PID-5: family name, given name, middle name, suffix, prefix, and so on, separated by carets. Unlike PID-5, it's common for NK1-2 to arrive with several components blank.
What this field contains
Example
Here the contact's name is DOE^JANE^M — a fully populated synthetic name used consistently across this NK1 example.
Where this trips people up
Teams reuse their PID-5 name-parsing logic for NK1-2 and assume the same completeness guarantees, but next-of-kin names are frequently entered by front-desk staff under time pressure and show up with only a last name, or with a nickname jammed into the family-name component. Test data that always supplies a tidy full name never exposes the display and matching bugs that a bare "MOTHER" or single-word entry causes downstream.