Testing HL7 v2 NK1-4: What Address Actually Needs to Handle
NK1-4 uses the exact same address structure as the patient's own address field, but almost none of the validation the patient address gets, because it's treated as a "nice to have."
NK1-4 carries the associated party's mailing address using the extended address (XAD) data type — street, second line, city, state, postal code, and country, separated by carets. It's structurally the same field type as PID-11, but it's populated far less consistently and validated far less often.
What this field contains
Example
The synthetic address 482 OAK ST^^DENVER^CO^80202 shows street, city, state, and zip populated with the second address line left blank.
Where this trips people up
Because NK1-4 is rarely required by workflow, it's often left entirely blank, or filled with a single free-text component instead of properly split values — the whole address jammed into the street-line component with the rest empty. Code that assumes city and state are always separately available breaks on this input, and it's easy to miss in testing if fixtures only ever use cleanly structured addresses.