Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4B
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4B - 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-Permission-element-map-to-R4B"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-Permission-element-map-to-R4B</b></p><a name="R5-Permission-element-map-to-R4B"> </a><a name="hcR5-Permission-element-map-to-R4B"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.3</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Permission|5.0.0</code> to <a href="http://hl7.org/fhir/R4B/basic.html">Basicversion: 4.3.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>Permission.meta (meta)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.meta</td><td>Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.
Element `Permission.meta` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.meta` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.implicitRules (implicitRules)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.implicitRules</td><td>Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.
Element `Permission.implicitRules` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.implicitRules` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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>Permission.language (language)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.language</td><td>Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.
Element `Permission.language` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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>Permission.text (text)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.text</td><td>Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.
Element `Permission.text` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.text` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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>Permission.contained (contained)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.contained</td><td>Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.
Element `Permission.contained` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.contained` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.status.html">R5: active | entered-in-error | draft | rejected (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>Permission.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: active | entered-in-error | draft | rejected (new))</td><td>Element `Permission.status` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.status` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.asserter.html">R5: The person or entity that asserts the permission (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>Permission.asserter (asserter)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The person or entity that asserts the permission (new))</td><td>Element `Permission.asserter` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.asserter` has no mapping targets in FHIR R4B. 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/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.date.html">R5: The date that permission was asserted (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>Permission.date (date)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The date that permission was asserted (new))</td><td>Element `Permission.date` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.date` has no mapping targets in FHIR R4B. 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/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.validity.html">R5: The period in which the permission is active (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>Permission.validity (validity)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The period in which the permission is active (new))</td><td>Element `Permission.validity` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.validity` has no mapping targets in FHIR R4B. 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/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.justification.html">R5: The asserted justification for using the data (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>Permission.justification (justification)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The asserted justification for using the data (new))</td><td>Element `Permission.justification` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.justification` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.justification.basis (basis)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:basis (R5: The regulatory grounds upon which this Permission builds (new))</td><td>Element `Permission.justification.basis` is part of an existing definition because parent element `Permission.justification` requires a cross-version extension.
Element `Permission.justification.basis` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.justification.basis` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.justification.evidence (evidence)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:evidence (R5: Justifing rational (new))</td><td>Element `Permission.justification.evidence` is part of an existing definition because parent element `Permission.justification` requires a cross-version extension.
Element `Permission.justification.evidence` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.justification.evidence` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.combining.html">R5: deny-overrides | permit-overrides | ordered-deny-overrides | ordered-permit-overrides | deny-unless-permit | permit-unless-deny (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>Permission.combining (combining)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: deny-overrides | permit-overrides | ordered-deny-overrides | ordered-permit-overrides | deny-unless-permit | permit-unless-deny (new))</td><td>Element `Permission.combining` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.combining` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
see [XACML Combining Rules](http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-cos01-en.html#_Toc325047267)</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/Permission|5.0.0</code> to <a href="StructureDefinition-ext-R5-Permission.rule.html">R5: Constraints to the Permission (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>Permission.rule (rule)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Constraints to the Permission (new))</td><td>Element `Permission.rule` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.type (type)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:type (R5: deny | permit (new))</td><td>Element `Permission.rule.type` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.type` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.data (data)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data (R5: The selection criteria to identify data that is within scope of this provision (new))</td><td>Element `Permission.rule.data` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.data` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.data.resource (resource)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data.extension:resource (R5: Explicit FHIR Resource references (new))</td><td>Element `Permission.rule.data.resource` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.resource` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.resource` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.data.resource.meaning (meaning)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data.extension:resource.extension:meaning (R5: instance | related | dependents | authoredby (new))</td><td>Element `Permission.rule.data.resource.meaning` is part of an existing definition because parent element `Permission.rule.data.resource` requires a cross-version extension.
Element `Permission.rule.data.resource.meaning` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.resource.meaning` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.data.resource.reference (reference)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data.extension:resource.extension:reference (R5: The actual data reference (new))</td><td>Element `Permission.rule.data.resource.reference` is part of an existing definition because parent element `Permission.rule.data.resource` requires a cross-version extension.
Element `Permission.rule.data.resource.reference` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.resource.reference` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.data.security (security)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data.extension:security (R5: Security tag code on .meta.security (new))</td><td>Element `Permission.rule.data.security` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.security` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.security` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Note the ConfidentialityCode vocabulary indicates the highest value, thus 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>Permission.rule.data.period (period)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data.extension:period (R5: Timeframe encompasing data create/update (new))</td><td>Element `Permission.rule.data.period` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.period` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.period` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This has a different sense to the .validity.</td></tr><tr><td>Permission.rule.data.expression (expression)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:data.extension:expression (R5: Expression identifying the data (new))</td><td>Element `Permission.rule.data.expression` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.expression` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.expression` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.activity (activity)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:activity (R5: A description or definition of which activities are allowed to be done on the data (new))</td><td>Element `Permission.rule.activity` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.activity` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.activity.actor (actor)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:activity.extension:actor (R5: Authorized actor(s) (new))</td><td>Element `Permission.rule.activity.actor` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension.
Element `Permission.rule.activity.actor` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity.actor` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.activity.action (action)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:activity.extension:action (R5: Actions controlled by this rule (new))</td><td>Element `Permission.rule.activity.action` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension.
Element `Permission.rule.activity.action` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity.action` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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>Permission.rule.activity.purpose (purpose)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:activity.extension:purpose (R5: The purpose for which the permission is given (new))</td><td>Element `Permission.rule.activity.purpose` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension.
Element `Permission.rule.activity.purpose` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity.purpose` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>Permission.rule.limit (limit)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:limit (R5: What limits apply to the use of the data (new))</td><td>Element `Permission.rule.limit` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.limit` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.limit` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</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.r4b"/>
</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.r4b"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-Permission-element-map-to-R4B"/>
<version value="0.1.0"/>
<name value="R5PermissionElementMapToR4B"/>
<title
value="Cross-version mapping for FHIR R5 Permission to FHIR R4B Basic"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:03:58.0261436-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 Permission to FHIR R4B."/>
<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.3"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Basic"/>
<targetVersion value="4.3.0"/>
<element>
<code value="Permission.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.meta"/>
<display value="Basic.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.
Element `Permission.meta` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.meta` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.implicitRules"/>
<display value="implicitRules"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.implicitRules"/>
<display value="Basic.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.
Element `Permission.implicitRules` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.implicitRules` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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="Permission.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.language"/>
<display value="Basic.language"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.
Element `Permission.language` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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="Permission.text"/>
<display value="text"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.text"/>
<display value="Basic.text"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.
Element `Permission.text` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.text` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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="Permission.contained"/>
<display value="contained"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.contained"/>
<display value="Basic.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.
Element `Permission.contained` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.contained` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.status"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.status"/>
<display value="status"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.status` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.status` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.asserter"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.asserter"/>
<display value="asserter"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.asserter` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.asserter` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.date"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.date"/>
<display value="date"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.date` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.date` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.validity"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.validity"/>
<display value="validity"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.validity` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.validity` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.justification"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.justification"/>
<display value="justification"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.justification` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.justification` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.justification.basis"/>
<display value="basis"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:basis"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.justification.basis` is part of an existing definition because parent element `Permission.justification` requires a cross-version extension.
Element `Permission.justification.basis` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.justification.basis` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.justification.evidence"/>
<display value="evidence"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:evidence"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.justification.evidence` is part of an existing definition because parent element `Permission.justification` requires a cross-version extension.
Element `Permission.justification.evidence` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.justification.evidence` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
While any resource may be used, DocumentReference, Consent, PlanDefinition, and Contract would be most frequent"/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.combining"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.combining"/>
<display value="combining"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.combining` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.combining` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
see [XACML Combining Rules](http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-cos01-en.html#_Toc325047267)"/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/Permission"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Permission.rule"/>
<targetVersion value="0.1.0"/>
<element>
<code value="Permission.rule"/>
<display value="rule"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.type"/>
<display value="type"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:type"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.type` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.type` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.data"/>
<display value="data"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:data"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.data` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.data.resource"/>
<display value="resource"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:data.extension:resource"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data.resource` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.resource` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.resource` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.data.resource.meaning"/>
<display value="meaning"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code
value="Extension.extension:data.extension:resource.extension:meaning"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data.resource.meaning` is part of an existing definition because parent element `Permission.rule.data.resource` requires a cross-version extension.
Element `Permission.rule.data.resource.meaning` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.resource.meaning` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.data.resource.reference"/>
<display value="reference"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code
value="Extension.extension:data.extension:resource.extension:reference"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data.resource.reference` is part of an existing definition because parent element `Permission.rule.data.resource` requires a cross-version extension.
Element `Permission.rule.data.resource.reference` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.resource.reference` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.data.security"/>
<display value="security"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:data.extension:security"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data.security` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.security` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.security` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Note the ConfidentialityCode vocabulary indicates the highest value, thus 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="Permission.rule.data.period"/>
<display value="period"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:data.extension:period"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data.period` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.period` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.period` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This has a different sense to the .validity."/>
</target>
</element>
<element>
<code value="Permission.rule.data.expression"/>
<display value="expression"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:data.extension:expression"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.data.expression` is part of an existing definition because parent element `Permission.rule.data` requires a cross-version extension.
Element `Permission.rule.data.expression` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.data.expression` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.activity"/>
<display value="activity"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:activity"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.activity` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.activity` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.activity.actor"/>
<display value="actor"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:activity.extension:actor"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.activity.actor` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension.
Element `Permission.rule.activity.actor` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity.actor` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.activity.action"/>
<display value="action"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:activity.extension:action"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.activity.action` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension.
Element `Permission.rule.activity.action` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity.action` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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="Permission.rule.activity.purpose"/>
<display value="purpose"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:activity.extension:purpose"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.activity.purpose` is part of an existing definition because parent element `Permission.rule.activity` requires a cross-version extension.
Element `Permission.rule.activity.purpose` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.activity.purpose` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="Permission.rule.limit"/>
<display value="limit"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:limit"/>
<equivalence value="wider"/>
<comment
value="Element `Permission.rule.limit` is part of an existing definition because parent element `Permission.rule` requires a cross-version extension.
Element `Permission.rule.limit` is not mapped to FHIR R4B, since FHIR R5 `Permission` is not mapped.
Element `Permission.rule.limit` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4b#0.1.0 based on FHIR 4.3.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change