SGHI FHIR Profile Implementation Guide
0.1.0 - ci-build

SGHI FHIR Profile Implementation Guide, published by Kathurima Kimathi. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/savannahghi/sil_fhir_profile_ig/ and changes regularly. See the Directory of published versions

Resource Profile: SGHIConsent - Mappings

Draft as of 2025-09-17

Mappings for the sghi-consent resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameWorkflow PatternFiveWs Pattern MappingHL7 V2 MappingRIM Mappingdoco
.. Consent
Event
infrastructure.information
CON
  • Entity
  • Role
  • or Act
... id
... meta
... implicitRules
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... identifier
Event.identifier
FiveWs.identifier
An implementation-specific requirement will be needed
.... id
n/a
.... extension
n/a
.... use
N/A
Role.code or implied by context
.... type
CX.5
Role.code or implied by context
.... system
CX.4 / EI-2-4
II.root or Role.id.root
.... value
CX.1 / EI.1
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
.... period
CX.7 + CX.8
Role.effectiveTime or implied by context
.... assigner
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
... status
Event.status
FiveWs.status
CON-11 (Consent Status – CNE using table HL70498)
... category
Event.code
FiveWs.class
CON-2 (Consent Type - CWE using table HL70496)
... subject
Event.subject
FiveWs.subject[x]
... date
Event.occurrence[x]
FiveWs.recorded
CON-13 (Consent Decision Date/Time – DTM)
... period
... grantor
... grantee
... manager
FiveWs.witness
... controller
... sourceAttachment
  • Potential mappings to CON-5
  • 6
  • 7
  • 8
  • 16
  • 19
  • 20-23
... sourceReference
  • Potential mappings to CON-5
  • 6
  • 7
  • 8
  • 16
  • 19
  • 20-23
... regulatoryBasis
An implementation-specific requirement will be needed
... policyBasis
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... reference
.... url
... policyText
... verification
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... verified
.... verificationType
.... verifiedBy
.... verifiedWith
.... verificationDate
... decision
... provision
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... period
  • CON-14&15 (Consent Effective Date Time
  • Consent End DateTime)
.... actor
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... role
..... reference
.... action
.... securityLabel
.... purpose
.... documentType
.... resourceType
.... code
.... dataPeriod
.... data
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... meaning
..... reference
.... expression
.... provision

doco Documentation for this format