Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R5-Consent-element-map-to-R4"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-Consent-element-map-to-R4</b></p><a name="R5-Consent-element-map-to-R4"> </a><a name="hcR5-Consent-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="http://hl7.org/fhir/R4/consent.html">Consentversion: 4.0.1)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.meta (meta)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.meta</td><td>Element `Consent.meta` is mapped to FHIR R4 element `Consent.meta` as `Equivalent`.</td></tr><tr><td>Consent.implicitRules (implicitRules)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.implicitRules</td><td>Element `Consent.implicitRules` is mapped to FHIR R4 element `Consent.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.</td></tr><tr><td>Consent.language (language)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.language</td><td>Element `Consent.language` is mapped to FHIR R4 element `Consent.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).</td></tr><tr><td>Consent.text (text)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.text</td><td>Element `Consent.text` is mapped to FHIR R4 element `Consent.text` as `Equivalent`.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.</td></tr><tr><td>Consent.contained (contained)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.contained</td><td>Element `Consent.contained` is mapped to FHIR R4 element `Consent.contained` as `Equivalent`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>Consent.identifier (identifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.identifier</td><td>Element `Consent.identifier` is mapped to FHIR R4 element `Consent.identifier` as `Equivalent`.
This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.</td></tr><tr><td>Consent.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.status</td><td>Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`.
The target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier.
This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.</td></tr><tr><td>Consent.category (category)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.category</td><td>Element `Consent.category` is mapped to FHIR R4 element `Consent.category` as `Equivalent`.</td></tr><tr><td>Consent.subject (subject)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.patient</td><td>Element `Consent.subject` is mapped to FHIR R4 element `Consent.patient` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.subject` with unmapped reference targets: Group, Practitioner.</td></tr><tr><td>Consent.date (date)</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td>Consent.dateTime</td><td>Element `Consent.date` is mapped to FHIR R4 element `Consent.dateTime` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td>Consent.grantee (grantee)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.performer</td><td>Element `Consent.grantee` is mapped to FHIR R4 element `Consent.performer` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.grantee` with unmapped reference targets: CareTeam, HealthcareService.
In a fully computable consent, both grantee and grantor will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only.</td></tr><tr><td>Consent.sourceAttachment (sourceAttachment)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.source[x]</td><td>Element `Consent.sourceAttachment` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`.
The target context `Consent.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Consent`.
The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.</td></tr><tr><td>Consent.sourceReference (sourceReference)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.source[x]</td><td>Element `Consent.sourceReference` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.sourceReference` with unmapped reference targets: DocumentReference.
Source element `Consent.sourceReference` has unmapped reference types. While the target element `Consent.source[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.</td></tr><tr><td>Consent.regulatoryBasis (regulatoryBasis)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.policyRule</td><td>Element `Consent.regulatoryBasis` is mapped to FHIR R4 element `Consent.policyRule` as `SourceIsBroaderThanTarget`.</td></tr><tr><td>Consent.policyBasis (policyBasis)</td><td><a href="CodeSystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>Consent.policy</td><td>Element `Consent.policyBasis` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td>Consent.policyBasis.reference (reference)</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td>Consent.policy</td><td>Element `Consent.policyBasis.reference` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.
While any resource may be used, Consent, PlanDefinition and Contract would be most frequent</td></tr><tr><td>Consent.policyBasis.url (url)</td><td><a href="CodeSystem-concept-map-relationship.html#narrower" title="narrower">narrower</a></td><td>Consent.policy</td><td>Element `Consent.policyBasis.url` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.</td></tr><tr><td>Consent.verification (verification)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.verification</td><td>Element `Consent.verification` is mapped to FHIR R4 element `Consent.verification` as `Equivalent`.</td></tr><tr><td>Consent.verification.verified (verified)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.verification.verified</td><td>Element `Consent.verification.verified` is mapped to FHIR R4 element `Consent.verification.verified` as `Equivalent`.</td></tr><tr><td>Consent.verification.verifiedWith (verifiedWith)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.verification.verifiedWith</td><td>Element `Consent.verification.verifiedWith` is mapped to FHIR R4 element `Consent.verification.verifiedWith` as `Equivalent`.</td></tr><tr><td>Consent.verification.verificationDate (verificationDate)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.verification.verificationDate</td><td>Element `Consent.verification.verificationDate` is mapped to FHIR R4 element `Consent.verification.verificationDate` as `SourceIsBroaderThanTarget`.
Allows for history of verification/validation.</td></tr><tr><td>Consent.provision (provision)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.provision</td><td>Element `Consent.provision` is mapped to FHIR R4 element `Consent.provision` as `SourceIsBroaderThanTarget`.</td></tr><tr><td>Consent.provision.period (period)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.period</td><td>Element `Consent.provision.period` is mapped to FHIR R4 element `Consent.provision.period` as `Equivalent`.
This is the bound effective time of the consent and should be in the base provision in the Consent resource.</td></tr><tr><td>Consent.provision.actor (actor)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.provision.actor</td><td>Element `Consent.provision.actor` is mapped to FHIR R4 element `Consent.provision.actor` as `Equivalent`.</td></tr><tr><td>Consent.provision.actor.role (role)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.actor.role</td><td>Element `Consent.provision.actor.role` is mapped to FHIR R4 element `Consent.provision.actor.role` as `Equivalent`.</td></tr><tr><td>Consent.provision.actor.reference (reference)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.actor.reference</td><td>Element `Consent.provision.actor.reference` is mapped to FHIR R4 element `Consent.provision.actor.reference` as `Equivalent`.</td></tr><tr><td>Consent.provision.action (action)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.action</td><td>Element `Consent.provision.action` is mapped to FHIR R4 element `Consent.provision.action` as `Equivalent`.
Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.</td></tr><tr><td>Consent.provision.securityLabel (securityLabel)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.securityLabel</td><td>Element `Consent.provision.securityLabel` is mapped to FHIR R4 element `Consent.provision.securityLabel` as `Equivalent`.
If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.</td></tr><tr><td>Consent.provision.purpose (purpose)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.purpose</td><td>Element `Consent.provision.purpose` is mapped to FHIR R4 element `Consent.provision.purpose` as `Equivalent`.
When the purpose of use tag is on the data, access request purpose of use shall not conflict.</td></tr><tr><td>Consent.provision.documentType (documentType)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.class</td><td>Element `Consent.provision.documentType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`.
Multiple types are or'ed together. The intention of the documentType element is that the codes refer to document types defined in a standard somewhere.</td></tr><tr><td>Consent.provision.resourceType (resourceType)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.class</td><td>Element `Consent.provision.resourceType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`.
Multiple types are or'ed together. The intention of the resourceType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.</td></tr><tr><td>Consent.provision.code (code)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.code</td><td>Element `Consent.provision.code` is mapped to FHIR R4 element `Consent.provision.code` as `Equivalent`.</td></tr><tr><td>Consent.provision.dataPeriod (dataPeriod)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.dataPeriod</td><td>Element `Consent.provision.dataPeriod` is mapped to FHIR R4 element `Consent.provision.dataPeriod` as `Equivalent`.
This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.</td></tr><tr><td>Consent.provision.data (data)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Consent.provision.data</td><td>Element `Consent.provision.data` is mapped to FHIR R4 element `Consent.provision.data` as `Equivalent`.</td></tr><tr><td>Consent.provision.data.meaning (meaning)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.data.meaning</td><td>Element `Consent.provision.data.meaning` is mapped to FHIR R4 element `Consent.provision.data.meaning` as `Equivalent`.</td></tr><tr><td>Consent.provision.data.reference (reference)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.data.reference</td><td>Element `Consent.provision.data.reference` is mapped to FHIR R4 element `Consent.provision.data.reference` as `Equivalent`.</td></tr><tr><td>Consent.provision.provision (provision)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Consent.provision.provision</td><td>Element `Consent.provision.provision` is mapped to FHIR R4 element `Consent.provision.provision` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.status.html">R5: draft | active | inactive | not-done | entered-in-error | unknownversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R5: draft | active | inactive | not-done | entered-in-error | unknown)</td><td>Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`.
The target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier.
This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.period.html">R5: Effective period for this Consent (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.period (period)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Effective period for this Consent (new))</td><td>Element `Consent.period` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.grantor.html">R5: Who is granting rights according to the policy and rules (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.grantor (grantor)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Who is granting rights according to the policy and rules (new))</td><td>Element `Consent.grantor` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.grantor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.manager.html">R5: Consent workflow management (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.manager (manager)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Consent workflow management (new))</td><td>Element `Consent.manager` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.manager` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.controller.html">R5: Consent Enforcer (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.controller (controller)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Consent Enforcer (new))</td><td>Element `Consent.controller` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.controller` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.policyText.html">R5: Human Readable Policy (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.policyText (policyText)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Human Readable Policy (new))</td><td>Element `Consent.policyText` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.policyText` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.ver.verificationType.html">R5: Business case of verification (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.verification.verificationType (verificationType)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Business case of verification (new))</td><td>Element `Consent.verification.verificationType` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.verification.verificationType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
This allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent.</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.ver.verifiedBy.html">R5: Person conducting verification (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.verification.verifiedBy (verifiedBy)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Person conducting verification (new))</td><td>Element `Consent.verification.verifiedBy` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.verification.verifiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.decision.html">R5: deny | permit (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.decision (decision)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R5: deny | permit (new))</td><td>Element `Consent.decision` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.decision` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Consent|5.0.0</code> to <a href="StructureDefinition-ext-R5-Consent.pro.expression.html">R5: A computable expression of the consent (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>Consent.provision.expression (expression)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: A computable expression of the consent (new))</td><td>Element `Consent.provision.expression` has a context of Consent.provision based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.provision.expression` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Constraining the expression type for a specific implementation via profile is recommended</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-Consent-element-map-to-R4"/>
<version value="0.1.0"/>
<name value="R5ConsentElementMapToR4"/>
<title
value="Cross-version mapping for FHIR R5 Consent to FHIR R4 Consent"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:44.917818-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR R5 Consent to FHIR R4."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/5.0"/>
<targetUri value="http://hl7.org/fhir/4.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<targetVersion value="4.0.1"/>
<element>
<code value="Consent.meta"/>
<display value="meta"/>
<target>
<code value="Consent.meta"/>
<display value="Consent.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.meta` is mapped to FHIR R4 element `Consent.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="Consent.implicitRules"/>
<display value="Consent.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.implicitRules` is mapped to FHIR R4 element `Consent.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="Consent.language"/>
<display value="language"/>
<target>
<code value="Consent.language"/>
<display value="Consent.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.language` is mapped to FHIR R4 element `Consent.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/>
</target>
</element>
<element>
<code value="Consent.text"/>
<display value="text"/>
<target>
<code value="Consent.text"/>
<display value="Consent.text"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.text` is mapped to FHIR R4 element `Consent.text` as `Equivalent`.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later."/>
</target>
</element>
<element>
<code value="Consent.contained"/>
<display value="contained"/>
<target>
<code value="Consent.contained"/>
<display value="Consent.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.contained` is mapped to FHIR R4 element `Consent.contained` as `Equivalent`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
<element>
<code value="Consent.identifier"/>
<display value="identifier"/>
<target>
<code value="Consent.identifier"/>
<display value="Consent.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.identifier` is mapped to FHIR R4 element `Consent.identifier` as `Equivalent`.
This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same."/>
</target>
</element>
<element>
<code value="Consent.status"/>
<display value="status"/>
<target>
<code value="Consent.status"/>
<display value="Consent.status"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`.
The target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier.
This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid."/>
</target>
</element>
<element>
<code value="Consent.category"/>
<display value="category"/>
<target>
<code value="Consent.category"/>
<display value="Consent.category"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.category` is mapped to FHIR R4 element `Consent.category` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.subject"/>
<display value="subject"/>
<target>
<code value="Consent.patient"/>
<display value="Consent.patient"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.subject` is mapped to FHIR R4 element `Consent.patient` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.subject` with unmapped reference targets: Group, Practitioner."/>
</target>
</element>
<element>
<code value="Consent.date"/>
<display value="date"/>
<target>
<code value="Consent.dateTime"/>
<display value="Consent.dateTime"/>
<equivalence value="narrower"/>
<comment
value="Element `Consent.date` is mapped to FHIR R4 element `Consent.dateTime` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Consent.grantee"/>
<display value="grantee"/>
<target>
<code value="Consent.performer"/>
<display value="Consent.performer"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.grantee` is mapped to FHIR R4 element `Consent.performer` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.grantee` with unmapped reference targets: CareTeam, HealthcareService.
In a fully computable consent, both grantee and grantor will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only."/>
</target>
</element>
<element>
<code value="Consent.sourceAttachment"/>
<display value="sourceAttachment"/>
<target>
<code value="Consent.source[x]"/>
<display value="Consent.source[x]"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.sourceAttachment` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`.
The target context `Consent.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Consent`.
The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id."/>
</target>
</element>
<element>
<code value="Consent.sourceReference"/>
<display value="sourceReference"/>
<target>
<code value="Consent.source[x]"/>
<display value="Consent.source[x]"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.sourceReference` is mapped to FHIR R4 element `Consent.source[x]` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Consent.sourceReference` with unmapped reference targets: DocumentReference.
Source element `Consent.sourceReference` has unmapped reference types. While the target element `Consent.source[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id."/>
</target>
</element>
<element>
<code value="Consent.regulatoryBasis"/>
<display value="regulatoryBasis"/>
<target>
<code value="Consent.policyRule"/>
<display value="Consent.policyRule"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.regulatoryBasis` is mapped to FHIR R4 element `Consent.policyRule` as `SourceIsBroaderThanTarget`."/>
</target>
</element>
<element>
<code value="Consent.policyBasis"/>
<display value="policyBasis"/>
<target>
<code value="Consent.policy"/>
<display value="Consent.policy"/>
<equivalence value="relatedto"/>
<comment
value="Element `Consent.policyBasis` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Consent.policyBasis.reference"/>
<display value="reference"/>
<target>
<code value="Consent.policy"/>
<display value="Consent.policy"/>
<equivalence value="narrower"/>
<comment
value="Element `Consent.policyBasis.reference` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`.
While any resource may be used, Consent, PlanDefinition and Contract would be most frequent"/>
</target>
</element>
<element>
<code value="Consent.policyBasis.url"/>
<display value="url"/>
<target>
<code value="Consent.policy"/>
<display value="Consent.policy"/>
<equivalence value="narrower"/>
<comment
value="Element `Consent.policyBasis.url` is mapped to FHIR R4 element `Consent.policy` as `SourceIsNarrowerThanTarget`."/>
</target>
</element>
<element>
<code value="Consent.verification"/>
<display value="verification"/>
<target>
<code value="Consent.verification"/>
<display value="Consent.verification"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.verification` is mapped to FHIR R4 element `Consent.verification` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.verification.verified"/>
<display value="verified"/>
<target>
<code value="Consent.verification.verified"/>
<display value="Consent.verification.verified"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.verification.verified` is mapped to FHIR R4 element `Consent.verification.verified` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.verification.verifiedWith"/>
<display value="verifiedWith"/>
<target>
<code value="Consent.verification.verifiedWith"/>
<display value="Consent.verification.verifiedWith"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.verification.verifiedWith` is mapped to FHIR R4 element `Consent.verification.verifiedWith` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.verification.verificationDate"/>
<display value="verificationDate"/>
<target>
<code value="Consent.verification.verificationDate"/>
<display value="Consent.verification.verificationDate"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.verification.verificationDate` is mapped to FHIR R4 element `Consent.verification.verificationDate` as `SourceIsBroaderThanTarget`.
Allows for history of verification/validation."/>
</target>
</element>
<element>
<code value="Consent.provision"/>
<display value="provision"/>
<target>
<code value="Consent.provision"/>
<display value="Consent.provision"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.provision` is mapped to FHIR R4 element `Consent.provision` as `SourceIsBroaderThanTarget`."/>
</target>
</element>
<element>
<code value="Consent.provision.period"/>
<display value="period"/>
<target>
<code value="Consent.provision.period"/>
<display value="Consent.provision.period"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.period` is mapped to FHIR R4 element `Consent.provision.period` as `Equivalent`.
This is the bound effective time of the consent and should be in the base provision in the Consent resource."/>
</target>
</element>
<element>
<code value="Consent.provision.actor"/>
<display value="actor"/>
<target>
<code value="Consent.provision.actor"/>
<display value="Consent.provision.actor"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.provision.actor` is mapped to FHIR R4 element `Consent.provision.actor` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.actor.role"/>
<display value="role"/>
<target>
<code value="Consent.provision.actor.role"/>
<display value="Consent.provision.actor.role"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.actor.role` is mapped to FHIR R4 element `Consent.provision.actor.role` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.actor.reference"/>
<display value="reference"/>
<target>
<code value="Consent.provision.actor.reference"/>
<display value="Consent.provision.actor.reference"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.actor.reference` is mapped to FHIR R4 element `Consent.provision.actor.reference` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.action"/>
<display value="action"/>
<target>
<code value="Consent.provision.action"/>
<display value="Consent.provision.action"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.action` is mapped to FHIR R4 element `Consent.provision.action` as `Equivalent`.
Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'."/>
</target>
</element>
<element>
<code value="Consent.provision.securityLabel"/>
<display value="securityLabel"/>
<target>
<code value="Consent.provision.securityLabel"/>
<display value="Consent.provision.securityLabel"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.securityLabel` is mapped to FHIR R4 element `Consent.provision.securityLabel` as `Equivalent`.
If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict."/>
</target>
</element>
<element>
<code value="Consent.provision.purpose"/>
<display value="purpose"/>
<target>
<code value="Consent.provision.purpose"/>
<display value="Consent.provision.purpose"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.purpose` is mapped to FHIR R4 element `Consent.provision.purpose` as `Equivalent`.
When the purpose of use tag is on the data, access request purpose of use shall not conflict."/>
</target>
</element>
<element>
<code value="Consent.provision.documentType"/>
<display value="documentType"/>
<target>
<code value="Consent.provision.class"/>
<display value="Consent.provision.class"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.documentType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`.
Multiple types are or'ed together. The intention of the documentType element is that the codes refer to document types defined in a standard somewhere."/>
</target>
</element>
<element>
<code value="Consent.provision.resourceType"/>
<display value="resourceType"/>
<target>
<code value="Consent.provision.class"/>
<display value="Consent.provision.class"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.resourceType` is mapped to FHIR R4 element `Consent.provision.class` as `Equivalent`.
Multiple types are or'ed together. The intention of the resourceType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere."/>
</target>
</element>
<element>
<code value="Consent.provision.code"/>
<display value="code"/>
<target>
<code value="Consent.provision.code"/>
<display value="Consent.provision.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.code` is mapped to FHIR R4 element `Consent.provision.code` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.dataPeriod"/>
<display value="dataPeriod"/>
<target>
<code value="Consent.provision.dataPeriod"/>
<display value="Consent.provision.dataPeriod"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.dataPeriod` is mapped to FHIR R4 element `Consent.provision.dataPeriod` as `Equivalent`.
This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement."/>
</target>
</element>
<element>
<code value="Consent.provision.data"/>
<display value="data"/>
<target>
<code value="Consent.provision.data"/>
<display value="Consent.provision.data"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.provision.data` is mapped to FHIR R4 element `Consent.provision.data` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.data.meaning"/>
<display value="meaning"/>
<target>
<code value="Consent.provision.data.meaning"/>
<display value="Consent.provision.data.meaning"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.data.meaning` is mapped to FHIR R4 element `Consent.provision.data.meaning` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.data.reference"/>
<display value="reference"/>
<target>
<code value="Consent.provision.data.reference"/>
<display value="Consent.provision.data.reference"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.data.reference` is mapped to FHIR R4 element `Consent.provision.data.reference` as `Equivalent`."/>
</target>
</element>
<element>
<code value="Consent.provision.provision"/>
<display value="provision"/>
<target>
<code value="Consent.provision.provision"/>
<display value="Consent.provision.provision"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.provision.provision` is mapped to FHIR R4 element `Consent.provision.provision` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.status"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.status"/>
<display value="status"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.status` is mapped to FHIR R4 element `Consent.status` as `SourceIsBroaderThanTarget`.
The target context `Consent.status` is a modifier element, so this extension does not need to be defined as a modifier.
This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.period"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.period"/>
<display value="period"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.period` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.grantor"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.grantor"/>
<display value="grantor"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.grantor` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.grantor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.manager"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.manager"/>
<display value="manager"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.manager` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.manager` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.controller"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.controller"/>
<display value="controller"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.controller` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.controller` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.policyText"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.policyText"/>
<display value="policyText"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.policyText` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.policyText` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.verification.verificationType"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.verification.verificationType"/>
<display value="verificationType"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.verification.verificationType` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.verification.verificationType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
This allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.verification.verifiedBy"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.verification.verifiedBy"/>
<display value="verifiedBy"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.verification.verifiedBy` has a context of Consent.verification based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.verification.verifiedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.decision"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.decision"/>
<display value="decision"/>
<target>
<code value="Extension"/>
<equivalence value="equivalent"/>
<comment
value="Element `Consent.decision` has a context of Consent based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.decision` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Consent"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Consent.provision.expression"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Consent.provision.expression"/>
<display value="expression"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Consent.provision.expression` has a context of Consent.provision based on following the parent source element upwards and mapping to `Consent`.
Element `Consent.provision.expression` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Constraining the expression type for a specific implementation via profile is recommended"/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change