eHealth Infrastructure - Local Development build (v2.5.0). See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML
• JSON
• TTL

Resource Profile: ehealth-relatedperson - Mappings

Active as of 2023-02-09

Mappings for the ehealth-relatedperson resource profile.

Mappings for RIM Mapping (http://hl7.org/v3)

ehealth-relatedperson
RelatedPerson	Entity. Role, or Act, role
text	Act.text?
contained	N/A
modifierExtension	N/A
identifier	.id
identifier (ehealth-dk-crn-identifier)	n/a, II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
active	.statusCode
patient	scoper[classCode=PSN|ANM and determinerCode='INSTANCE']/playedRole[classCode='PAT']/id
relationship	code
id	n/a
extension	n/a
coding	union(., ./translation)
text	./originalText[mediaType/code="text/plain"]/data
name	name
telecom	telecom
gender	administrativeGender
birthDate	player.birthTime
address	addr
photo	player[classCode='PSN' and determinerCode='INSTANCE']/desc
period	.effectiveTime
communication	LanguageCommunication
id	n/a
extension	n/a
modifierExtension	N/A
language	player[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
preferred	preferenceInd

Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

ehealth-relatedperson
RelatedPerson
identifier	FiveWs.identifier
active	FiveWs.status
relationship	FiveWs.class
period	FiveWs.done[x]

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

ehealth-relatedperson
RelatedPerson
identifier	NK1-33
identifier (ehealth-dk-crn-identifier)	CX / EI (occasionally, more often EI maps to a resource id or a URL)
patient	PID-3
relationship	NK1-3
coding	C*E.1-8, C*E.10-22
text	C*E.9. But note many systems use C*E.2 for this
name	NK1-2
telecom	NK1-5 / NK1-6 / NK1-40
gender	NK1-15
address	NK1-4
photo	OBX-5 - needs a profile