Understanding HL7 v2 NK1-7: Contact Role in Practice
A guarantor and an emergency contact can be the same person, coded in two different NK1-7 values on two different NK1 segments, and systems that treat contact role as redundant with relationship end up merging records that were never supposed to be merged.
NK1-7 is a coded field describing what role the associated party plays with respect to the patient's care or account — emergency contact, next of kin, guarantor — as distinct from NK1-3, which describes the family or personal relationship. The same person can appear in multiple NK1 segments with different NK1-7 values if they serve more than one role.
Valid code values
Example
EC in the eighth pipe-delimited position marks this synthetic contact's role as emergency contact, separate from the SPO relationship code earlier in the segment.
Where this trips people up
Teams frequently build UI and logic that display only one of NK1-3 or NK1-7, assuming they carry the same information, which breaks the moment a patient has a next-of-kin contact who is not also the emergency contact, or a guarantor who isn't related to the patient at all. Test scenarios should deliberately include NK1 sets where relationship and contact role diverge — a guarantor coded OTH for relationship but GT for role, for instance — to confirm both fields are actually being read independently.