Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - 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-DeviceDispense-element-map-to-R3"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-DeviceDispense-element-map-to-R3</b></p><a name="R5-DeviceDispense-element-map-to-R3"> </a><a name="hcR5-DeviceDispense-element-map-to-R3"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <code>http://hl7.org/fhir/StructureDefinition/Basic|3.0.2</code></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>DeviceDispense.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 `DeviceDispense.meta` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>DeviceDispense.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 `DeviceDispense.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.implicitRules` has no mapping targets in FHIR STU3. 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>DeviceDispense.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 `DeviceDispense.language` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.language` has no mapping targets in FHIR STU3. 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>DeviceDispense.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 `DeviceDispense.text` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.text` has no mapping targets in FHIR STU3. 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>DeviceDispense.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 `DeviceDispense.contained` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.contained` has no mapping targets in FHIR STU3. 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><tr><td>DeviceDispense.identifier (identifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.identifier</td><td>Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.
Element `DeviceDispense.identifier` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This is a business identifier, not a resource identifier.</td></tr><tr><td>DeviceDispense.subject (subject)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.subject</td><td>Element matches Basic element path `Basic.subject` (`Basic.subject`), use that element instead.
Element `DeviceDispense.subject` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.subject` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
What about 'this measuring Device is now asigned to Dr X who needs it now'?</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.basedOn.html">R5: The order or request that this dispense is fulfilling (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>DeviceDispense.basedOn (basedOn)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The order or request that this dispense is fulfilling (new))</td><td>Element `DeviceDispense.basedOn` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.basedOn` has no mapping targets in FHIR STU3. 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/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.partOf.html">R5: The bigger event that this dispense is a part of (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>DeviceDispense.partOf (partOf)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: The bigger event that this dispense is a part of (new))</td><td>Element `DeviceDispense.partOf` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.partOf` has no mapping targets in FHIR STU3. 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/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.status.html">R5: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown (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>DeviceDispense.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown (new))</td><td>Element `DeviceDispense.status` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.statusReason.html">R5: Why a dispense was or was not performed (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>DeviceDispense.statusReason (statusReason)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Why a dispense was or was not performed (new))</td><td>Element `DeviceDispense.statusReason` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.statusReason` has no mapping targets in FHIR STU3. 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/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.category.html">R5: Type of device dispense (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>DeviceDispense.category (category)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Type of device dispense (new))</td><td>Element `DeviceDispense.category` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The category can be used to include where the device is expected to be consumed or other types of dispenses. Invariants can be used to bind to different value sets when profiling to bind.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.device.html">R5: What device was supplied (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>DeviceDispense.device (device)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: What device was supplied (new))</td><td>Element `DeviceDispense.device` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.device` has no mapping targets in FHIR STU3. 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/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.receiver.html">R5: Who collected the device or where the medication was delivered (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>DeviceDispense.receiver (receiver)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Who collected the device or where the medication was delivered (new))</td><td>Element `DeviceDispense.receiver` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.receiver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.encounter.html">R5: Encounter associated with event (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>DeviceDispense.encounter (encounter)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Encounter associated with event (new))</td><td>Element `DeviceDispense.encounter` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.encounter` has no mapping targets in FHIR STU3. 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/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.supportingInformation.html">R5: Information that supports the dispensing of the device (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>DeviceDispense.supportingInformation (supportingInformation)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Information that supports the dispensing of the device (new))</td><td>Element `DeviceDispense.supportingInformation` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.supportingInformation` has no mapping targets in FHIR STU3. 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/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.performer.html">R5: Who performed event (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>DeviceDispense.performer (performer)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Who performed event (new))</td><td>Element `DeviceDispense.performer` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>DeviceDispense.performer.function (function)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:function (R5: Who performed the dispense and what they did (new))</td><td>Element `DeviceDispense.performer.function` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension.
Element `DeviceDispense.performer.function` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.performer.function` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>DeviceDispense.performer.actor (actor)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:actor (R5: Individual who was performing (new))</td><td>Element `DeviceDispense.performer.actor` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension.
Element `DeviceDispense.performer.actor` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.performer.actor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.location.html">R5: Where the dispense occurred (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>DeviceDispense.location (location)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Where the dispense occurred (new))</td><td>Element `DeviceDispense.location` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.type.html">R5: Trial fill, partial fill, emergency fill, etc (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>DeviceDispense.type (type)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Trial fill, partial fill, emergency fill, etc (new))</td><td>Element `DeviceDispense.type` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.quantity.html">R5: Amount dispensed (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>DeviceDispense.quantity (quantity)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Amount dispensed (new))</td><td>Element `DeviceDispense.quantity` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.quantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 15 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.preparedDate.html">R5: When product was packaged and reviewed (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>DeviceDispense.preparedDate (preparedDate)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: When product was packaged and reviewed (new))</td><td>Element `DeviceDispense.preparedDate` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.preparedDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 16 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.whenHandedOver.html">R5: When product was given out (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>DeviceDispense.whenHandedOver (whenHandedOver)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: When product was given out (new))</td><td>Element `DeviceDispense.whenHandedOver` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.whenHandedOver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 17 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.destination.html">R5: Where the device was sent or should be sent (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>DeviceDispense.destination (destination)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Where the device was sent or should be sent (new))</td><td>Element `DeviceDispense.destination` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.destination` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 18 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.note.html">R5: Information about the dispense (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>DeviceDispense.note (note)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Information about the dispense (new))</td><td>Element `DeviceDispense.note` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 19 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.usageInstruction.html">R5: Full representation of the usage instructions (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>DeviceDispense.usageInstruction (usageInstruction)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Full representation of the usage instructions (new))</td><td>Element `DeviceDispense.usageInstruction` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.usageInstruction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content.</td></tr></table><hr/><p><b>Group 20 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0</code> to <a href="StructureDefinition-ext-R5-DeviceDispense.eventHistory.html">R5: A list of relevant lifecycle events (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>DeviceDispense.eventHistory (eventHistory)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: A list of relevant lifecycle events (new))</td><td>Element `DeviceDispense.eventHistory` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.eventHistory` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.).</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">
<valueUri
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"/>
</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">
<valueUri
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceDispense-element-map-to-R3"/>
<version value="0.1.0"/>
<name value="R5DeviceDispenseElementMapToR3"/>
<title
value="Cross-version mapping for FHIR R5 DeviceDispense to FHIR STU3 Basic"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:05:15.4379931-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 DeviceDispense to FHIR STU3."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceUri value="http://hl7.org/fhir/5.0"/>
<targetUri value="http://hl7.org/fhir/3.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Basic"/>
<targetVersion value="3.0.2"/>
<element>
<code value="DeviceDispense.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 `DeviceDispense.meta` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="DeviceDispense.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 `DeviceDispense.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.implicitRules` has no mapping targets in FHIR STU3. 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="DeviceDispense.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 `DeviceDispense.language` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.language` has no mapping targets in FHIR STU3. 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="DeviceDispense.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 `DeviceDispense.text` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.text` has no mapping targets in FHIR STU3. 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="DeviceDispense.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 `DeviceDispense.contained` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.contained` has no mapping targets in FHIR STU3. 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>
<element>
<code value="DeviceDispense.identifier"/>
<display value="identifier"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.identifier"/>
<display value="Basic.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.
Element `DeviceDispense.identifier` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This is a business identifier, not a resource identifier."/>
</target>
</element>
<element>
<code value="DeviceDispense.subject"/>
<display value="subject"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.subject"/>
<display value="Basic.subject"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.subject` (`Basic.subject`), use that element instead.
Element `DeviceDispense.subject` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.subject` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
What about 'this measuring Device is now asigned to Dr X who needs it now'?"/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.basedOn"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.basedOn"/>
<display value="basedOn"/>
<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 `DeviceDispense.basedOn` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.basedOn` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.partOf"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.partOf"/>
<display value="partOf"/>
<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 `DeviceDispense.partOf` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.partOf` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.status"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.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 `DeviceDispense.status` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.statusReason"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.statusReason"/>
<display value="statusReason"/>
<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 `DeviceDispense.statusReason` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.statusReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.category"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.category"/>
<display value="category"/>
<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 `DeviceDispense.category` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The category can be used to include where the device is expected to be consumed or other types of dispenses. Invariants can be used to bind to different value sets when profiling to bind."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.device"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.device"/>
<display value="device"/>
<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 `DeviceDispense.device` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.device` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.receiver"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.receiver"/>
<display value="receiver"/>
<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 `DeviceDispense.receiver` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.receiver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.encounter"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.encounter"/>
<display value="encounter"/>
<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 `DeviceDispense.encounter` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.encounter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.supportingInformation"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.supportingInformation"/>
<display value="supportingInformation"/>
<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 `DeviceDispense.supportingInformation` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.supportingInformation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.performer"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.performer"/>
<display value="performer"/>
<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 `DeviceDispense.performer` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="DeviceDispense.performer.function"/>
<display value="function"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:function"/>
<equivalence value="wider"/>
<comment
value="Element `DeviceDispense.performer.function` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension.
Element `DeviceDispense.performer.function` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.performer.function` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="DeviceDispense.performer.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:actor"/>
<equivalence value="wider"/>
<comment
value="Element `DeviceDispense.performer.actor` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension.
Element `DeviceDispense.performer.actor` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.performer.actor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.location"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.location"/>
<display value="location"/>
<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 `DeviceDispense.location` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.location` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.type"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.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"/>
<equivalence value="wider"/>
<comment
value="Element `DeviceDispense.type` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.quantity"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.quantity"/>
<display value="quantity"/>
<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 `DeviceDispense.quantity` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.quantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.preparedDate"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.preparedDate"/>
<display value="preparedDate"/>
<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 `DeviceDispense.preparedDate` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.preparedDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.whenHandedOver"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.whenHandedOver"/>
<display value="whenHandedOver"/>
<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 `DeviceDispense.whenHandedOver` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.whenHandedOver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.destination"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.destination"/>
<display value="destination"/>
<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 `DeviceDispense.destination` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.destination` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.note"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.note"/>
<display value="note"/>
<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 `DeviceDispense.note` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.usageInstruction"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.usageInstruction"/>
<display value="usageInstruction"/>
<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 `DeviceDispense.usageInstruction` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.usageInstruction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/DeviceDispense"/>
<sourceVersion value="5.0.0"/>
<target
value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.eventHistory"/>
<targetVersion value="0.1.0"/>
<element>
<code value="DeviceDispense.eventHistory"/>
<display value="eventHistory"/>
<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 `DeviceDispense.eventHistory` is not mapped to FHIR STU3, since FHIR R5 `DeviceDispense` is not mapped.
Element `DeviceDispense.eventHistory` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change