CH Core (R4)
5.0.0-ballot - ballot Switzerland flag

This page is part of the CH Core (R4) (v5.0.0-ballot: STU 5 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Resource Profile: CHCorePatient - Mappings

Active as of 2024-05-16

Mappings for the ch-core-patient resource profile.

Mappings for eCH-Standards (http://www.ech.ch/)

CHCorePatient
Patient
   extension (placeOfBirth)eCH-0011: placeOfBirth BFS-322, BFS-323, BFS 324
   extension (placeOfOrigin)eCH-0011: placeOfOrigin, BFS-42
   extension (citizenship)eCH-0011: nationalityData
   extension (religion)eCH-0011: religion, BFS-711
   nameeCH-0011: nameData
   telecomeCH-0046: Contact
   telecom (email)eCH-0046: email
   telecom (phone)eCH-0046: phone
   telecom (internet)eCH-0046: internet
   gendereCH-0011: sex. sexType, BFS-33, see ConceptMap http://fhir.ch/ig/ch-core/ConceptMap/sex-ech11-to-fhir
   birthDateeCH-0011: birthData, BFS-31
   deceased[x]eCH-0011: deathData, deathPeriod, dateFrom, BFS-361
   addresseCH-0010: addressInformation
   maritalStatuseCH-0011: maritalData, BFS-341, see ConceptMap http://fhir.ch/ig/ch-core/ConceptMap/maritalstatus-ech11-to-fhir
      extension (maritalDataSeparation)eCH-0011: separation - Trennung BFS-343
   contact
   contact (contact)eCH-0011: contactData, BFS-61
      addresseCH-0010: addressInformation
   contact (nameOfParent)eCH-0021: nameOfParent
   communication (languageOfCorrespondence)eCH-0011: languageOfCorrespondance: de, fr, it, rm = Rhaeto-Romance, en, other languages ISO 639-1

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

CHCorePatient
PatientEntity. Role, or Act, Patient[classCode=PAT]
   textAct.text?
   containedN/A
   modifierExtensionN/A
   identifierid
   identifier (EPR-SPID)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]
   identifier (AHVN13)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]
   identifier (LocalPid)id
      idn/a
      extensionn/a
      useRole.code or implied by context
      typeRole.code or implied by context
      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 (insuranceCardNumber)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]
   activestatusCode
   namen/a, EN (actually, PN)
   telecomtelecom
      idn/a
      extensionn/a
      system./scheme
      value./url
      useunique(./use)
      rankn/a
      period./usablePeriod[type="IVL<TS>"]
   telecom (email)n/a, TEL
   telecom (phone)n/a, TEL
   telecom (internet)n/a, TEL
   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
   addressn/a, AD
   maritalStatusplayer[classCode=PSN]/maritalStatusCode
      idn/a
      extensionn/a
      codingunion(., ./translation)
      text./originalText[mediaType/code="text/plain"]/data
   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
   contact (contact)player[classCode=PSN|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON]
      idn/a
      extensionn/a
      modifierExtensionN/A
      relationshipcode
      namename
      addressn/a, AD
      genderplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
      organizationscoper
      periodeffectiveTime
   contact (nameOfParent)player[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
   communicationLanguageCommunication
      idn/a
      extensionn/a
      modifierExtensionN/A
      languageplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
      preferredpreferenceInd
   communication (languageOfCorrespondence)LanguageCommunication
      idn/a
      extensionn/a
      modifierExtensionN/A
      languageplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
      preferredpreferenceInd
   generalPractitionersubjectOf.CareEvent.performer.AssignedEntity
   managingOrganizationscoper
   linkoutboundLink
      idn/a
      extensionn/a
      modifierExtensionN/A
      otherid
      typetypeCode

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

CHCorePatient
PatientClinicalDocument.recordTarget.patientRole
   identifier.id
   identifier (LocalPid).id
   activen/a
   telecom.telecom
   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
   contact (contact)n/a
      relationshipn/a
      namen/a
      gendern/a
      organizationn/a
      periodn/a
   contact (nameOfParent)n/a
      relationshipn/a
      namen/a
      telecomn/a
      addressn/a
      gendern/a
      organizationn/a
      periodn/a
   communicationpatient.languageCommunication
      language.languageCode
      preferred.preferenceInd
   communication (languageOfCorrespondence)patient.languageCommunication
      language.languageCode
      preferred.preferenceInd
   generalPractitionern/a
   managingOrganization.providerOrganization
   linkn/a
      othern/a
      typen/a

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

CHCorePatient
Patient
   identifierFiveWs.identifier
   identifier (LocalPid)FiveWs.identifier
   activeFiveWs.status

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

CHCorePatient
Patient
   identifierPID-3
   identifier (EPR-SPID)CX / EI (occasionally, more often EI maps to a resource id or a URL)
   identifier (AHVN13)CX / EI (occasionally, more often EI maps to a resource id or a URL)
   identifier (LocalPid)PID-3
      useN/A
      typeCX.5
      systemCX.4 / EI-2-4
      valueCX.1 / EI.1
      periodCX.7 + CX.8
      assignerCX.4 / (CX.4,CX.9,CX.10)
   identifier (insuranceCardNumber)CX / EI (occasionally, more often EI maps to a resource id or a URL)
   nameXPN
   telecomPID-13, PID-14, PID-40, -> as of HL7 v2.7 PID-40 (leave PID-13 and PID-14 empty)
      systemXTN.3
      valueXTN.1 (or XTN.12)
      useXTN.2 - but often indicated by field
      rankn/a
      periodN/A
   telecom (email)XTN
   telecom (phone)XTN
   telecom (internet)XTN
   genderPID-8
   birthDatePID-7
   deceased[x]PID-30 (bool) and PID-29 (datetime)
   addressXAD
   maritalStatusPID-16
      codingC*E.1-8, C*E.10-22
      textC*E.9. But note many systems use C*E.2 for this
   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
   contact (contact)
      relationshipNK1-7, NK1-3
      nameNK1-2
      addressXAD
      genderNK1-15
      organizationNK1-13, NK1-30, NK1-31, NK1-32, NK1-41
   contact (nameOfParent)
      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
   communication
      languagePID-15, LAN-2
      preferredPID-15
   communication (languageOfCorrespondence)
      languagePID-15, LAN-2
      preferredPID-15
   generalPractitionerPD1-4
   link
      otherPID-3, MRG-1

Mappings for LOINC code for the element (http://loinc.org)

CHCorePatient
Patient
   birthDate21112-8