FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r4 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-DeviceDispense-element-map-to-R4.json |
| FHIR Version | R4 |
| Source | http://hl7.org/fhir/uv/xver-r5.r4/0.1.0/ConceptMap-R5-DeviceDispense-element-map-to-R4.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceDispense-element-map-to-R4 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:04:44.9747943-05:00 |
| Name | R5DeviceDispenseElementMapToR4 |
| Title | Cross-version mapping for FHIR R5 DeviceDispense to FHIR R4 Basic |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceDispense to FHIR R4. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.basedOn | R5: The order or request that this dispense is fulfilling (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.category | R5: Type of device dispense (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.destination | R5: Where the device was sent or should be sent (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.device | R5: What device was supplied (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.encounter | R5: Encounter associated with event (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.eventHistory | R5: A list of relevant lifecycle events (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.location | R5: Where the dispense occurred (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.note | R5: Information about the dispense (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.partOf | R5: The bigger event that this dispense is a part of (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.performer | R5: Who performed event (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.preparedDate | R5: When product was packaged and reviewed (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.quantity | R5: Amount dispensed (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.receiver | R5: Who collected the device or where the medication was delivered (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.status | R5: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.statusReason | R5: Why a dispense was or was not performed (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.supportingInformation | R5: Information that supports the dispensing of the device (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.type | R5: Trial fill, partial fill, emergency fill, etc (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.usageInstruction | R5: Full representation of the usage instructions (new) |
| hl7.fhir.uv.xver-r5.r4#0.1.0 | extension-DeviceDispense.whenHandedOver | R5: When product was given out (new) |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-DeviceDispense-element-map-to-R4
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to Basicversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.meta (meta) | is equivalent to | Basic.meta | Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `DeviceDispense.meta` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| DeviceDispense.implicitRules (implicitRules) | is equivalent to | Basic.implicitRules | Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `DeviceDispense.implicitRules` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.implicitRules` has no mapping targets in FHIR R4. 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. |
| DeviceDispense.language (language) | is equivalent to | Basic.language | Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `DeviceDispense.language` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.language` has no mapping targets in FHIR R4. 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). |
| DeviceDispense.text (text) | is equivalent to | Basic.text | Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `DeviceDispense.text` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.text` has no mapping targets in FHIR R4. 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. |
| DeviceDispense.contained (contained) | is equivalent to | Basic.contained | Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `DeviceDispense.contained` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.contained` has no mapping targets in FHIR R4. 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. |
| DeviceDispense.identifier (identifier) | is equivalent to | Basic.identifier | Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `DeviceDispense.identifier` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This is a business identifier, not a resource identifier. |
| DeviceDispense.subject (subject) | is equivalent to | Basic.subject | Element matches Basic element path `Basic.subject` (`Basic.subject`), use that element instead. Element `DeviceDispense.subject` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.subject` has no mapping targets in FHIR R4. 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'? |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: The order or request that this dispense is fulfilling (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.basedOn (basedOn) | maps to wider concept | Extension (R5: The order or request that this dispense is fulfilling (new)) | Element `DeviceDispense.basedOn` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.basedOn` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: The bigger event that this dispense is a part of (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.partOf (partOf) | maps to wider concept | Extension (R5: The bigger event that this dispense is a part of (new)) | Element `DeviceDispense.partOf` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.partOf` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.status (status) | maps to wider concept | Extension (R5: preparation | in-progress | cancelled | on-hold | completed | entered-in-error | stopped | declined | unknown (new)) | Element `DeviceDispense.status` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.status` has no mapping targets in FHIR R4. 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. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Why a dispense was or was not performed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.statusReason (statusReason) | maps to wider concept | Extension (R5: Why a dispense was or was not performed (new)) | Element `DeviceDispense.statusReason` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.statusReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Type of device dispense (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.category (category) | maps to wider concept | Extension (R5: Type of device dispense (new)) | Element `DeviceDispense.category` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.category` has no mapping targets in FHIR R4. 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. |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: What device was supplied (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.device (device) | maps to wider concept | Extension (R5: What device was supplied (new)) | Element `DeviceDispense.device` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.device` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Who collected the device or where the medication was delivered (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.receiver (receiver) | maps to wider concept | Extension (R5: Who collected the device or where the medication was delivered (new)) | Element `DeviceDispense.receiver` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.receiver` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Encounter associated with event (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.encounter (encounter) | maps to wider concept | Extension (R5: Encounter associated with event (new)) | Element `DeviceDispense.encounter` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.encounter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Information that supports the dispensing of the device (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.supportingInformation (supportingInformation) | maps to wider concept | Extension (R5: Information that supports the dispensing of the device (new)) | Element `DeviceDispense.supportingInformation` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.supportingInformation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Who performed event (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.performer (performer) | maps to wider concept | Extension (R5: Who performed event (new)) | Element `DeviceDispense.performer` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| DeviceDispense.performer.function (function) | maps to wider concept | Extension.extension:function (R5: Who performed the dispense and what they did (new)) | 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 R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer.function` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| DeviceDispense.performer.actor (actor) | maps to wider concept | Extension.extension:actor (R5: Individual who was performing (new)) | 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 R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.performer.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Where the dispense occurred (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.location (location) | maps to wider concept | Extension (R5: Where the dispense occurred (new)) | Element `DeviceDispense.location` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.location` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Trial fill, partial fill, emergency fill, etc (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.type (type) | maps to wider concept | Extension (R5: Trial fill, partial fill, emergency fill, etc (new)) | Element `DeviceDispense.type` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Amount dispensed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.quantity (quantity) | maps to wider concept | Extension (R5: Amount dispensed (new)) | Element `DeviceDispense.quantity` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.quantity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: When product was packaged and reviewed (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.preparedDate (preparedDate) | maps to wider concept | Extension (R5: When product was packaged and reviewed (new)) | Element `DeviceDispense.preparedDate` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.preparedDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: When product was given out (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.whenHandedOver (whenHandedOver) | maps to wider concept | Extension (R5: When product was given out (new)) | Element `DeviceDispense.whenHandedOver` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.whenHandedOver` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Where the device was sent or should be sent (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.destination (destination) | maps to wider concept | Extension (R5: Where the device was sent or should be sent (new)) | Element `DeviceDispense.destination` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.destination` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Information about the dispense (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.note (note) | maps to wider concept | Extension (R5: Information about the dispense (new)) | Element `DeviceDispense.note` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: Full representation of the usage instructions (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.usageInstruction (usageInstruction) | maps to wider concept | Extension (R5: Full representation of the usage instructions (new)) | Element `DeviceDispense.usageInstruction` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.usageInstruction` has no mapping targets in FHIR R4. 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. |
Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDispense|5.0.0 to R5: A list of relevant lifecycle events (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceDispense.eventHistory (eventHistory) | maps to wider concept | Extension (R5: A list of relevant lifecycle events (new)) | Element `DeviceDispense.eventHistory` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.eventHistory` has no mapping targets in FHIR R4. 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.). |
{
"resourceType": "ConceptMap",
"id": "R5-DeviceDispense-element-map-to-R4",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceDispense-element-map-to-R4",
"version": "0.1.0",
"name": "R5DeviceDispenseElementMapToR4",
"title": "Cross-version mapping for FHIR R5 DeviceDispense to FHIR R4 Basic",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:04:44.9747943-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceDispense to FHIR R4.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceCanonical": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/4.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/Basic",
"targetVersion": "4.0.1",
"element": [
{
"code": "DeviceDispense.meta",
"display": "meta",
"target": [
{
"code": "Basic.meta",
"display": "Basic.meta",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.\nElement `DeviceDispense.meta` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "DeviceDispense.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "Basic.implicitRules",
"display": "Basic.implicitRules",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.\nElement `DeviceDispense.implicitRules` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nAsserting 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."
}
]
},
{
"code": "DeviceDispense.language",
"display": "language",
"target": [
{
"code": "Basic.language",
"display": "Basic.language",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.\nElement `DeviceDispense.language` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nLanguage 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)."
}
]
},
{
"code": "DeviceDispense.text",
"display": "text",
"target": [
{
"code": "Basic.text",
"display": "Basic.text",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.\nElement `DeviceDispense.text` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nContained 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."
}
]
},
{
"code": "DeviceDispense.contained",
"display": "contained",
"target": [
{
"code": "Basic.contained",
"display": "Basic.contained",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.\nElement `DeviceDispense.contained` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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."
}
]
},
{
"code": "DeviceDispense.identifier",
"display": "identifier",
"target": [
{
"code": "Basic.identifier",
"display": "Basic.identifier",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.\nElement `DeviceDispense.identifier` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis is a business identifier, not a resource identifier."
}
]
},
{
"code": "DeviceDispense.subject",
"display": "subject",
"target": [
{
"code": "Basic.subject",
"display": "Basic.subject",
"equivalence": "equivalent",
"comment": "Element matches Basic element path `Basic.subject` (`Basic.subject`), use that element instead.\nElement `DeviceDispense.subject` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.subject` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nWhat about 'this measuring Device is now asigned to Dr X who needs it now'?"
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.basedOn",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.basedOn",
"display": "basedOn",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.basedOn` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.basedOn` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.partOf",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.partOf",
"display": "partOf",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.partOf` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.partOf` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.status",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.status",
"display": "status",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.status` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.statusReason",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.statusReason",
"display": "statusReason",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.statusReason` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.statusReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.category",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.category",
"display": "category",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.category` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.device",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.device",
"display": "device",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.device` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.device` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.receiver",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.receiver",
"display": "receiver",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.receiver` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.receiver` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.encounter",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.encounter",
"display": "encounter",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.encounter` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.encounter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.supportingInformation",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.supportingInformation",
"display": "supportingInformation",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.supportingInformation` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.supportingInformation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.performer",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.performer",
"display": "performer",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.performer` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.performer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "DeviceDispense.performer.function",
"display": "function",
"target": [
{
"code": "Extension.extension:function",
"equivalence": "wider",
"comment": "Element `DeviceDispense.performer.function` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension.\nElement `DeviceDispense.performer.function` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.performer.function` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "DeviceDispense.performer.actor",
"display": "actor",
"target": [
{
"code": "Extension.extension:actor",
"equivalence": "wider",
"comment": "Element `DeviceDispense.performer.actor` is part of an existing definition because parent element `DeviceDispense.performer` requires a cross-version extension.\nElement `DeviceDispense.performer.actor` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.performer.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.location",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.location",
"display": "location",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.location` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.location` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.type",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.type",
"display": "type",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.type` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.quantity",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.quantity",
"display": "quantity",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.quantity` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.quantity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.preparedDate",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.preparedDate",
"display": "preparedDate",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.preparedDate` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.preparedDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.whenHandedOver",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.whenHandedOver",
"display": "whenHandedOver",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.whenHandedOver` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.whenHandedOver` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.destination",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.destination",
"display": "destination",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.destination` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.destination` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.note",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.note",
"display": "note",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.note` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.usageInstruction",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.usageInstruction",
"display": "usageInstruction",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.usageInstruction` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.usageInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThe content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DeviceDispense",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDispense.eventHistory",
"targetVersion": "0.1.0",
"element": [
{
"code": "DeviceDispense.eventHistory",
"display": "eventHistory",
"target": [
{
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DeviceDispense.eventHistory` is not mapped to FHIR R4, since FHIR R5 `DeviceDispense` is not mapped.\nElement `DeviceDispense.eventHistory` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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.)."
}
]
}
]
}
]
}