0.1.0 - ci-build Switzerland flag

KISIMConsent - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: KisimCoreConsent - Mappings

Draft as of 2025-05-23

Mappings for the KisimCoreConsent resource profile.

Mappings for Workflow Pattern (http://hl7.org/fhir/workflow)

KisimCoreConsent
ConsentEvent
   identifierEvent.identifier
   statusEvent.status
   categoryEvent.code
   subjectEvent.subject
   dateEvent.occurrence[x]

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

KisimCoreConsent
Consentinfrastructure.information
   identifierFiveWs.identifier
   statusFiveWs.status
   categoryFiveWs.class
   subjectFiveWs.subject[x]
   dateFiveWs.recorded
   managerFiveWs.witness

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

KisimCoreConsent
ConsentCON
   identifierCON-4 (Consent Form Number – EI) Note: An implementation-specific requirement will be needed
   statusCON-11 (Consent Status – CNE using table HL70498)
   categoryCON-2 (Consent Type - CWE using table HL70496)
   dateCON-13 (Consent Decision Date/Time – DTM)
   period
      startDR.1
      endDR.2
   grantor
      identifier
         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)
   grantee
      identifier
         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)
   manager
      identifier
         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)
   controller
      identifier
         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)
   sourceAttachmentPotential mappings to CON-5,6,7,8,16,19, 20-23
   sourceReferencePotential mappings to CON-5,6,7,8,16,19, 20-23
   regulatoryBasisCON-3 (Consent Form ID and Version – ST) Note: An implementation-specific requirement will be needed
   provision
      periodCON-14&15 (Consent Effective Date Time, Consent End DateTime)

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

KisimCoreConsent
ConsentEntity, Role, or Act
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   period
      idn/a
      extensionn/a
      start./low
      end./high
   grantor
      idn/a
      extensionn/a
      referenceN/A
      typeN/A
      identifier.identifier
         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
      displayN/A
   grantee
      idn/a
      extensionn/a
      referenceN/A
      typeN/A
      identifier.identifier
         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
      displayN/A
   manager
      idn/a
      extensionn/a
      referenceN/A
      typeN/A
      identifier.identifier
         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
      displayN/A
   controller
      idn/a
      extensionn/a
      referenceN/A
      typeN/A
      identifier.identifier
         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
      displayN/A
   policyBasis
      idn/a
      extensionn/a
      modifierExtensionN/A
   verification
      idn/a
      extensionn/a
      modifierExtensionN/A
   provision
      idn/a
      extensionn/a
      modifierExtensionN/A
      actor
         idn/a
         extensionn/a
         modifierExtensionN/A
      data
         idn/a
         extensionn/a
         modifierExtensionN/A