Shared Health Specification and Guide Version 5.0

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML

3.50.7 StructureDefinition: Shared Health Patient - Mappings

Mappings for the Profile.

Mappings for CDA (R2) (http://hl7.org/v3/cda)

Shared Health Patient
Patient	ClinicalDocument.recordTarget.patientRole
identifier	.id
active	n/a
gender	.patient.administrativeGenderCode
birthDate	.patient.birthTime
deceased[x]	n/a
maritalStatus	.patient.maritalStatusCode
multipleBirth[x]	n/a
photo	n/a
contact	n/a
relationship	n/a
name	n/a
telecom	n/a
address	n/a
gender	n/a
organization	n/a
period	n/a
animal	n/a
species	n/a
breed	n/a
genderStatus	n/a
communication	patient.languageCommunication
language	.languageCode
preferred	.preferenceInd
careProvider	n/a
managingOrganization	.providerOrganization
link	n/a
other	n/a
type	n/a

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

Shared Health Patient
Patient	Patient[classCode=PAT]
text	Act.text?
contained	N/A
extension	N/A
modifierExtension	N/A
identifier	id
identifier (senderPatientIdentifier)	II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. 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]
id	n/a
extension	n/a
use	Role.code or implied by context
type	CD
id	n/a
extension	n/a
coding	union(., ./translation)
id	n/a
extension	n/a
system	./codeSystem
version	./codeSystemVersion
code	./code
display	CV.displayName
userSelected	CD.codingRationale
text	./originalText[mediaType/code="text/plain"]/data
system	II.root or Role.id.root
value	II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period	Role.effectiveTime or implied by context
assigner	II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
identifier (jurisdictionalHealthNumber)	II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. 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]
id	n/a
use	Role.code or implied by context
type	CD
id	n/a
extension	n/a
coding	union(., ./translation)
id	n/a
extension	n/a
system	./codeSystem
version	./codeSystemVersion
code	./code
display	CV.displayName
userSelected	CD.codingRationale
text	./originalText[mediaType/code="text/plain"]/data
system	II.root or Role.id.root
value	II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period	Role.effectiveTime or implied by context
assigner	II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
active	statusCode
name	EN (actually, PN)
name (legalName)	EN (actually, PN)
id	n/a
extension	n/a
use	unique(./use)
text	./formatted
family	./part[partType = FAM]
given	./part[partType = GIV]
prefix	./part[partType = PFX]
suffix	./part[partType = SFX]
period	./usablePeriod[type="IVL<TS>"]
telecom	TEL
gender	player[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
birthDate	player[classCode=PSN|ANM and determinerCode=INSTANCE]/birthTime
deceased[x]	player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedTime
address	AD
maritalStatus	player[classCode=PSN]/maritalStatusCode
multipleBirth[x]	player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthOrderNumber
photo	player[classCode=PSN|ANM and determinerCode=INSTANCE]/desc
contact	player[classCode=PSN|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON]
id	n/a
extension	n/a
modifierExtension	N/A
relationship	code
name	name
telecom	telecom
address	addr
gender	player[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
organization	scoper
period	effectiveTime
animal	player[classCode=ANM]
id	n/a
extension	n/a
modifierExtension	N/A
species	code
breed	playedRole[classCode=GEN]/scoper[classCode=ANM, determinerCode=KIND]/code
genderStatus	genderStatusCode
communication	LanguageCommunication
id	n/a
extension	n/a
modifierExtension	N/A
language	player[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
preferred	preferenceInd
careProvider	subjectOf.CareEvent.performer.AssignedEntity
managingOrganization	scoper
link	outboundLink
id	n/a
extension	n/a
modifierExtension	N/A
other	id
type	typeCode

Mappings for W5 Mapping (http://hl7.org/fhir/w5)

Shared Health Patient
Patient	administrative.individual
identifier	id
active	status

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

Shared Health Patient
Patient
identifier	PID-3
identifier (senderPatientIdentifier)	CX / EI (occasionally, more often EI maps to a resource id or a URL)
use	N/A
type	CE/CNE/CWE
coding	C*E.1-8, C*E.10-22
system	C*E.3
version	C*E.7
code	C*E.1
display	C*E.2 - but note this is not well followed
userSelected	Sometimes implied by being first
text	C*E.9. But note many systems use C*E.2 for this
system	CX.4 / EI-2-4
value	CX.1 / EI.1
period	CX.7 + CX.8
assigner	CX.4 / (CX.4,CX.9,CX.10)
identifier (jurisdictionalHealthNumber)	CX / EI (occasionally, more often EI maps to a resource id or a URL)
use	N/A
type	CE/CNE/CWE
coding	C*E.1-8, C*E.10-22
system	C*E.3
version	C*E.7
code	C*E.1
display	C*E.2 - but note this is not well followed
userSelected	Sometimes implied by being first
text	C*E.9. But note many systems use C*E.2 for this
system	CX.4 / EI-2-4
value	CX.1 / EI.1
period	CX.7 + CX.8
assigner	CX.4 / (CX.4,CX.9,CX.10)
name	XPN
name (legalName)	XPN
use	XPN.7, but often indicated by which field contains the name
text	implied by XPN.11
family	XPN.1
given	XPN.2 + XPN.3
prefix	XPN.5
suffix	XPN/4
period	XPN.13 + XPN.14
telecom	XTN
gender	PID-8
birthDate	PID-7
deceased[x]	PID-30 (bool) and PID-29 (datetime)
address	XAD
maritalStatus	PID-16
multipleBirth[x]	PID-24 (bool), PID-25 (integer)
photo	OBX-5 - needs a profile
contact
relationship	NK1-7, NK1-3
name	NK1-2
telecom	NK1-5, NK1-6, NK1-40
address	NK1-4
gender	NK1-15
organization	NK1-13, NK1-30, NK1-31, NK1-32, NK1-41
animal
species	PID-35
breed	PID-37
genderStatus	N/A
communication
language	PID-15, LAN-2
preferred	PID-15
careProvider	PD1-4
link
other	PID-3, MRG-1

Mappings for LOINC (http://loinc.org)

Shared Health Patient
Patient
birthDate	21112-8