Shared Health Specification and Guide Version 2.0 Revision F

 

Mappings for the Profile.

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

Shared Health Patient
PatientClinicalDocument.recordTarget.patientRole
   identifier.id
   activen/a
   gender.patient.administrativeGenderCode
   birthDate.patient.birthTime
   deceased[x]n/a
   maritalStatus.patient.maritalStatusCode
   multipleBirth[x]n/a
   photon/a
   contactn/a
      relationshipn/a
      namen/a
      telecomn/a
      addressn/a
      gendern/a
      organizationn/a
      periodn/a
   animaln/a
      speciesn/a
      breedn/a
      genderStatusn/a
   communicationpatient.languageCommunication
      language.languageCode
      preferred.preferenceInd
   careProvidern/a
   managingOrganization.providerOrganization
   linkn/a
      othern/a
      typen/a

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

Shared Health Patient
PatientPatient[classCode=PAT]
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifierid
   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]
      idn/a
      extensionn/a
      useRole.code or implied by context
      typeCD
         idn/a
         extensionn/a
         codingunion(., ./translation)
            idn/a
            extensionn/a
            system./codeSystem
            version./codeSystemVersion
            code./code
            displayCV.displayName
            userSelectedCD.codingRationale
         text./originalText[mediaType/code="text/plain"]/data
      systemII.root or Role.id.root
      valueII.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
      periodRole.effectiveTime or implied by context
      assignerII.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
   identifier (JurisidictionalHealthNumber)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]
      idn/a
      useRole.code or implied by context
      typeCD
         idn/a
         extensionn/a
         codingunion(., ./translation)
            idn/a
            extensionn/a
            system./codeSystem
            version./codeSystemVersion
            code./code
            displayCV.displayName
            userSelectedCD.codingRationale
         text./originalText[mediaType/code="text/plain"]/data
      systemII.root or Role.id.root
      valueII.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
      periodRole.effectiveTime or implied by context
      assignerII.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
   activestatusCode
   nameEN (actually, PN)
   name (LegalName)EN (actually, PN)
      idn/a
      extensionn/a
      useunique(./use)
      text./formatted
      family./part[partType = FAM]
      given./part[partType = GIV]
      prefix./part[partType = PFX]
      suffix./part[partType = SFX]
      period./usablePeriod[type="IVL<TS>"]
   telecomTEL
   genderplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
   birthDateplayer[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
   addressAD
   maritalStatusplayer[classCode=PSN]/maritalStatusCode
   multipleBirth[x]player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthOrderNumber
   photoplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/desc
   contactplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON]
      idn/a
      extensionn/a
      modifierExtensionN/A
      relationshipcode
      namename
      telecomtelecom
      addressaddr
      genderplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
      organizationscoper
      periodeffectiveTime
   animalplayer[classCode=ANM]
      idn/a
      extensionn/a
      modifierExtensionN/A
      speciescode
      breedplayedRole[classCode=GEN]/scoper[classCode=ANM, determinerCode=KIND]/code
      genderStatusgenderStatusCode
   communicationLanguageCommunication
      idn/a
      extensionn/a
      modifierExtensionN/A
      languageplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
      preferredpreferenceInd
   careProvidersubjectOf.CareEvent.performer.AssignedEntity
   managingOrganizationscoper
   linkoutboundLink
      idn/a
      extensionn/a
      modifierExtensionN/A
      otherid
      typetypeCode

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

Shared Health Patient
Patientadministrative.individual
   identifierid
   activestatus

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

Shared Health Patient
Patient
   identifierPID-3
   identifier (SenderPatientIdentifier)CX / EI (occasionally, more often EI maps to a resource id or a URL)
      useN/A
      typeCE/CNE/CWE
         codingC*E.1-8, C*E.10-22
            systemC*E.3
            versionC*E.7
            codeC*E.1
            displayC*E.2 - but note this is not well followed
            userSelectedSometimes implied by being first
         textC*E.9. But note many systems use C*E.2 for this
      systemCX.4 / EI-2-4
      valueCX.1 / EI.1
      periodCX.7 + CX.8
      assignerCX.4 / (CX.4,CX.9,CX.10)
   identifier (JurisidictionalHealthNumber)CX / EI (occasionally, more often EI maps to a resource id or a URL)
      useN/A
      typeCE/CNE/CWE
         codingC*E.1-8, C*E.10-22
            systemC*E.3
            versionC*E.7
            codeC*E.1
            displayC*E.2 - but note this is not well followed
            userSelectedSometimes implied by being first
         textC*E.9. But note many systems use C*E.2 for this
      systemCX.4 / EI-2-4
      valueCX.1 / EI.1
      periodCX.7 + CX.8
      assignerCX.4 / (CX.4,CX.9,CX.10)
   nameXPN
   name (LegalName)XPN
      useXPN.7, but often indicated by which field contains the name
      textimplied by XPN.11
      familyXPN.1
      givenXPN.2 + XPN.3
      prefixXPN.5
      suffixXPN/4
      periodXPN.13 + XPN.14
   telecomXTN
   genderPID-8
   birthDatePID-7
   deceased[x]PID-30 (bool) and PID-29 (datetime)
   addressXAD
   maritalStatusPID-16
   multipleBirth[x]PID-24 (bool), PID-25 (integer)
   photoOBX-5 - needs a profile
   contact
      relationshipNK1-7, NK1-3
      nameNK1-2
      telecomNK1-5, NK1-6, NK1-40
      addressNK1-4
      genderNK1-15
      organizationNK1-13, NK1-30, NK1-31, NK1-32, NK1-41
   animal
      speciesPID-35
      breedPID-37
      genderStatusN/A
   communication
      languagePID-15, LAN-2
      preferredPID-15
   careProviderPD1-4
   link
      otherPID-3, MRG-1

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

Shared Health Patient
Patient
   birthDate21112-8