Healthy Route Implementation Guide
0.1.0 - ci-build

Healthy Route Implementation Guide, published by Savannah Informatics. 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/healthy-route-ig/ and changes regularly. See the Directory of published versions

Resource Profile: HRConsent - Mappings

Draft as of 2026-09-04

Mappings for the hr-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
... Slices for extension
.... extension:tenant
... modifierExtension
N/A
... identifier
Event.identifier
FiveWs.identifier
An implementation-specific requirement will be needed
... status
Event.status
FiveWs.status
CON-11 (Consent Status – CNE using table HL70498)
... Slices for category
Event.code
FiveWs.class
CON-2 (Consent Type - CWE using table HL70496)
.... category:permission
Event.code
FiveWs.class
CON-2 (Consent Type - CWE using table HL70496)
..... id
n/a
..... extension
n/a
..... coding
  • C*E.1-8
  • C*E.10-22
  • union(.
  • ./translation)
...... id
n/a
...... extension
n/a
...... system
C*E.3
./codeSystem
...... version
C*E.7
./codeSystemVersion
...... code
C*E.1
./code
...... display
C*E.2 - but note this is not well followed
CV.displayName
...... userSelected
Sometimes implied by being first
CD.codingRationale
..... text
C*E.9. But note many systems use C*E.2 for this
./originalText[mediaType/code="text/plain"]/data
... 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