HL7 Version 2 to FHIR
1.0.0 - STU 1 International flag

HL7 Version 2 to FHIR, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/v2-to-fhir/ and changes regularly. See the Directory of published versions

ConceptMap: Segment NK1 to RelatedPerson Map (Experimental)

Official URL: http://hl7.org/fhir/uv/v2mappings/ConceptMap/segment-nk1-to-relatedperson Version: 1.0.0
Standards status: Informative Computable Name: SegmentNK1ToRelatedPerson

Copyright/Legal: Copyright (c) 2025, HL7 International, Inc., All Rights Reserved.

This ConceptMap represents a mapping from the HL7 V2 Segment NK1 to the FHIR RelatedPerson Resource.

This ConceptMap represents the mapping from the HL7 V2 NK1 Segment to the FHIR RelatedPerson Resource. See also the FHIR Shorthand or the CSV Source.

HL7 v2Condition (IF True, args)HL7 FHIRComments
Sort OrderIdentifierNameData TypeCardinality - MinCardinality - MaxComputable ANTLRComputable FHIRPathNarrativeFHIR AttributeExtensionData TypeCardinality - MinCardinality - MaxData Type MappingVocabulary Mapping
(IS, ID, CE, CEN, CWE)
Assignment
1NK1-1Set ID - NK1SI11
2NK1-2NameXPN0-1RelatedPerson.nameHumanName0-1XPN[HumanName]
3NK1-3RelationshipCWE01RelatedPerson.relationshipCodeableConcept0-1CWE[CodeableConcept]RelationshipNote that the value sets between Patient.contact.relationship and RelatedPerson.relationship are quite different. See https://chat.fhir.org/#narrow/stream/179166-implementers/topic/relationship.20in.20Patient.2Econtact.20and.20RelatedPersonfor further discussion
4NK1-4AddressXAD0-1AddressAddress0-1XAD[Address]
5NK1-5Phone NumberXTN0-1RelatedPerson.telecomContactPoint0-1XTN[ContactPoint]ContactPoint.use would likely be "home" or "mobile", but picked up from XTN.2
6NK1-6Business Phone NumberXTN0-1RelatedPerson.telecomContactPoint0-1XTN[ContactPoint]
6NK1-6Business Phone NumberXTN0-1RelatedPerson.telecom.use"work"
7NK1-7Contact RoleCWE01RelatedPerson.relationshipCodeableConcept0-1CWE[CodeableConcept]ContactRoleNote that the value sets between Patient.contact.relationship and RelatedPerson.relationship are quite different. RelatedPerson.relationship is allowed to repeat and so can accept values from both NK1-3 and NK1-7 See https://chat.fhir.org/#narrow/stream/179166-implementers/topic/relationship.20in.20Patient.2Econtact.20and.20RelatedPerson for further discussion
8NK1-8Start DateDT01RelatedPerson.period.startdateTime01
9NK1-9End DateDT01RelatedPerson.period.enddateTime01
10NK1-10Next of Kin / Associated Parties Job TitleST01
11NK1-11Next of Kin / Associated Parties Job Code/ClassJCC01
12NK1-12Next of Kin / Associated Parties Employee NumberCX01IdentifierIdentifier0-1CX[Identifier]
13NK1-13Organization Name - NK1XON0-1Do we need to enhance the Organization resource to be able to serve as a next of kin or associated party?
14NK1-14Marital StatusCWE01
15NK1-15Administrative SexCWE01RelatedPerson.gendercode01CWE[Code]AdministrativeSex
16NK1-16Date/Time of BirthDTM01RelatedPerson.birthDatedate01
17NK1-17Living DependencyCWE0-1
18NK1-18Ambulatory StatusCWE0-1
19NK1-19CitizenshipCWE0-1
20NK1-20Primary LanguageCWE01RelatedPerson.communication.languageCodeableConcept0-1CWE[CodeableConcept]PrimaryLanguage
21NK1-21Living ArrangementCWE01
22NK1-22Publicity CodeCWE01
23NK1-23Protection IndicatorID01
24NK1-24Student IndicatorCWE01
25NK1-25ReligionCWE01
26NK1-26Mother's Maiden NameXPN0-1We could dupicate the patient-mothersmaidenname extension and add it to RelatedPerson if we need to
27NK1-27NationalityCWE01
28NK1-28Ethnic GroupCWE0-1
29NK1-29Contact ReasonCWE0-1
30NK1-30Contact Person's NameXPN0-1RelatedPerson.nameHumanName0-1XPN[HumanName]Do we need a way in RelatedPerson to distinguish between a "next of kin" and a "contact Person"?
31NK1-31Contact Person's Telephone NumberXTN0-1RelatedPerson.telecomContactPoint0-1XTN[ContactPoint]
32NK1-32Contact Person's AddressXAD0-1AddressAddress0-1XAD[Address]
33NK1-33Next of Kin/Associated Party's IdentifiersCX0-1IdentifierIdentifier0-1CX[Identifier]
34NK1-34Job StatusCWE01
35NK1-35RaceCWE0-1Use your local extension, e.g., US = US Core Race Extension, AUS = indiginous extension.
36NK1-36HandicapCWE01
37NK1-37Contact Person Social Security NumberST01RelatedPerson.identifier.valueIdentifier0-1
37NK1-37Contact Person Social Security NumberST01RelatedPerson.identifier.systemuri0-1"http://hl7.org/fhir/sid/us-ssn"
37NK1-37Contact Person Social Security NumberST01If in the US and various other jurisdictionsRelatedPerson.identifier.type.coding.codecode01"SS"
37NK1-37Contact Person Social Security NumberST01If outside the US for certain jurisdictionsRelatedPerson.identifier.type.coding.codecode01"SB"
38NK1-38Next of Kin Birth PlaceST01
39NK1-39VIP IndicatorCWE01
40NK1-40Next of Kin Telecommunication InformationXTN01RelatedPerson.telecomContactPoint0-1XTN[ContactPoint]
41NK1-41Contact Person's Telecommunication InformationXTN01RelatedPerson.telecomContactPoint0-1XTN[ContactPoint]

Mapping from (not specified) to (not specified)


Group 1 Mapping from unspecified code system to unspecified code system

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from NarrativeConditionCodes from
NK1-2Nameis equivalent toname[1]name[1]
NK1-3Relationshipis equivalent torelationship[1]relationship[1]Note that the value sets between Patient.contact.relationship and RelatedPerson.relationship are quite different. See https://chat.fhir.org/#narrow/stream/179166-implementers/topic/relationship.20in.20Patient.2Econtact.20and.20RelatedPersonfor further discussion\
NK1-4Addressis equivalent toaddress[1]address[1]
NK1-5Phone Numberis equivalent totelecom[1]telecom[1]ContactPoint.use would likely be "home" or "mobile", but picked up from XTN.2
NK1-6Business Phone Numberis equivalent totelecom[2]telecom[2]
NK1-6Business Phone Numberis equivalent totelecom[2].usetelecom[2].use
NK1-7Contact Roleis equivalent torelationship[2]relationship[2]Note that the value sets between Patient.contact.relationship and RelatedPerson.relationship are quite different. RelatedPerson.relationship is allowed to repeat and so can accept values from both NK1-3 and NK1-7 See https://chat.fhir.org/#narrow/stream/179166-implementers/topic/relationship.20in.20Patient.2Econtact.20and.20RelatedPerson for further discussion\
NK1-8Start Dateis equivalent toperiod.startperiod.start
NK1-9End Dateis equivalent toperiod.endperiod.end
NK1-12Next of Kin / Associated Parties Employee Numberis equivalent toidentifier[1]identifier[1]
NK1-15Administrative Sexis equivalent togendergender
NK1-16Date/Time of Birthis equivalent tobirthDatebirthDate
NK1-20Primary Languageis equivalent tocommunication.languagecommunication.language
NK1-30Contact Person's Nameis equivalent toname[2]name[2]Do we need a way in RelatedPerson to distinguish between a "next of kin" and a "contact Person"?
NK1-31Contact Person's Telephone Numberis equivalent totelecom[3]telecom[3]
NK1-32Contact Person's Addressis equivalent toaddress[2]address[2]
NK1-33Next of Kin/Associated Party's Identifiersis equivalent toidentifier[2]identifier[2]
NK1-37Contact Person Social Security Numberis equivalent toidentifier[3].valueidentifier[3].value
NK1-37Contact Person Social Security Numberis equivalent toidentifier[3].systemidentifier[3].system
NK1-37Contact Person Social Security NumberIf in the US and various other jurisdictionsis equivalent toidentifier[3].type.coding.codeidentifier[3].type.coding.code
NK1-37Contact Person Social Security NumberIf outside the US for certain jurisdictionsis equivalent toidentifier[3].type.coding.codeidentifier[3].type.coding.code
NK1-40Next of Kin Telecommunication Informationis equivalent totelecom[4]telecom[4]
NK1-41Contact Person's Telecommunication Informationis equivalent totelecom[5]telecom[5]

Notes: