Back to FHIR Mappings

Segment NK1 to Patient Map

This ConceptMap represents a mapping from the HL7 V2 Segment NK1 to the FHIR Patient Resource.
View in v2-to-FHIR IG
#V2 FieldNameV2 TypeCard.FHIR AttributeFHIR TypeEquiv.
1NK1-2NameXPN-1..*
contact.name
HumanName
equivalent
2NK1-3RelationshipCWE1..1
contact.relationship[1]
CodeableConcept
equivalent
3NK1-4AddressXAD-1..*
contact.address

Note the decreased cardinality for the FHIR map

Address
equivalent
4NK1-5Phone NumberXTN-1..*
contact.telecom[1]
ContactPoint
equivalent
5NK1-6Business Phone NumberXTN-1..*
contact.telecom[2]
contact.telecom[2].use

= "work"

ContactPointcode
equivalentequivalent
6NK1-7Contact RoleCWE1..1
contact.relationship[2]

Should we update the names in the base FHIR standard as the names and value sets are confusing? It's normative, so has to have a very strong case.

CodeableConcept
equivalent
7NK1-8Start DateDT1..1
contact.period.start
dateTime
equivalent
8NK1-9End DateDT1..1
contact.period.end
dateTime
equivalent
9NK1-13Organization Name - NK1XON-1..*
contact.organization[1](Organization)
Reference(Organization)
equivalent
10NK1-15Administrative SexCWE1..1
contact.gender
code
equivalent
11NK1-30Contact Person's NameXPN-1..*
contact.organization[1](Organization.contact.name)
HumanName
equivalent
12NK1-31Contact Person's Telephone NumberXTN-1..*
contact.organization[1](Organization.contact.telecom)
ContactPoint
equivalent
13NK1-32Contact Person's AddressXAD-1..*
contact.organization[1](Organization.contact.address)
Address
equivalent
14NK1-40Next of Kin Telecommunication InformationXTN1..1
contact.telecom[3]
ContactPoint
equivalent
15NK1-41Contact Person's Telecommunication InformationXTN1..1
contact.telecom[4]
ContactPoint
equivalent

Equivalence Legend

equivalentExact match
wider/narrowerBroader/more specific meaning
relatedtoRelated but not exact
unmatchedNo equivalent in target