Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4B - Downloaded Version null See the Directory of published versions

ConceptMap: R2DeviceUseRequestElementMapToR4B

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-DeviceUseRequest-element-map-to-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R2DeviceUseRequestElementMapToR4B

This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 DeviceUseRequest to FHIR R4B.

Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/4.3


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DeviceRequestversion: 4.3.0)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2Codes from DeviceRequest
DeviceUseRequest.metametamaps to wider conceptDeviceRequest.metaDeviceRequest.metaElement `DeviceUseRequest.meta` is mapped to FHIR R4B element `DeviceRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.meta` do not cover the following types: Meta. The mappings for `DeviceUseRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
DeviceUseRequest.implicitRulesimplicitRulesis equivalent toDeviceRequest.implicitRulesDeviceRequest.implicitRulesElement `DeviceUseRequest.implicitRules` is mapped to FHIR R4B element `DeviceRequest.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.
DeviceUseRequest.languagelanguageis equivalent toDeviceRequest.languageDeviceRequest.languageElement `DeviceUseRequest.language` is mapped to FHIR R4B element `DeviceRequest.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
DeviceUseRequest.texttextmaps to wider conceptDeviceRequest.textDeviceRequest.textElement `DeviceUseRequest.text` is mapped to FHIR R4B element `DeviceRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.text` do not cover the following types: Narrative. The mappings for `DeviceUseRequest.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.
DeviceUseRequest.containedcontainedis equivalent toDeviceRequest.containedDeviceRequest.containedElement `DeviceUseRequest.contained` is mapped to FHIR R4B element `DeviceRequest.contained` as `SourceIsBroaderThanTarget`. 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.
DeviceUseRequest.statusstatusis related toDeviceRequest.statusDeviceRequest.statusElement `DeviceUseRequest.status` is mapped to FHIR R4B element `DeviceRequest.status` as `RelatedTo`. The mappings for `DeviceUseRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `DeviceRequest.status` is a modifier element, so this extension does not need to be defined as a modifier.
DeviceUseRequest.devicedeviceis related toDeviceRequest.code[x]DeviceRequest.code[x]Element `DeviceUseRequest.device` is mapped to FHIR R4B element `DeviceRequest.code[x]` as `RelatedTo`. The mappings for `DeviceUseRequest.device` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DeviceUseRequest.device` with unmapped reference targets: Device. Source element `DeviceUseRequest.device` has unmapped reference types. While the target element `DeviceRequest.code[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it.
DeviceUseRequest.encounterencountermaps to wider conceptDeviceRequest.encounterDeviceRequest.encounterElement `DeviceUseRequest.encounter` is mapped to FHIR R4B element `DeviceRequest.encounter` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.encounter` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DeviceUseRequest.encounter` with unmapped reference targets: Encounter.
DeviceUseRequest.identifieridentifiermaps to wider conceptDeviceRequest.identifierDeviceRequest.identifierElement `DeviceUseRequest.identifier` is mapped to FHIR R4B element `DeviceRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.identifier` do not cover the following types: Identifier. The mappings for `DeviceUseRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
DeviceUseRequest.indicationindicationis equivalent toDeviceRequest.reasonCodeDeviceRequest.reasonCodeElement `DeviceUseRequest.indication` is mapped to FHIR R4B element `DeviceRequest.reasonCode` as `Equivalent`.
DeviceUseRequest.notesnotesmaps to wider conceptDeviceRequest.noteDeviceRequest.noteElement `DeviceUseRequest.notes` is mapped to FHIR R4B element `DeviceRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.notes` do not cover the following types: string. The mappings for `DeviceUseRequest.notes` do not cover the following types based on type expansion: value.
DeviceUseRequest.orderedOnorderedOnis equivalent toDeviceRequest.authoredOnDeviceRequest.authoredOnElement `DeviceUseRequest.orderedOn` is mapped to FHIR R4B element `DeviceRequest.occurrence[x]` as `SourceIsNarrowerThanTarget`. Element `DeviceUseRequest.orderedOn` is mapped to FHIR R4B element `DeviceRequest.authoredOn` as `Equivalent`.
is equivalent toDeviceRequest.occurrence[x]DeviceRequest.occurrence[x]Element `DeviceUseRequest.orderedOn` is mapped to FHIR R4B element `DeviceRequest.occurrence[x]` as `SourceIsNarrowerThanTarget`. Element `DeviceUseRequest.orderedOn` is mapped to FHIR R4B element `DeviceRequest.authoredOn` as `Equivalent`.
DeviceUseRequest.recordedOnrecordedOnis equivalent toDeviceRequest.authoredOnDeviceRequest.authoredOnElement `DeviceUseRequest.recordedOn` is mapped to FHIR R4B element `DeviceRequest.authoredOn` as `Equivalent`.
DeviceUseRequest.subjectsubjectmaps to wider conceptDeviceRequest.subjectDeviceRequest.subjectElement `DeviceUseRequest.subject` is mapped to FHIR R4B element `DeviceRequest.subject` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.subject` do not cover the following types based on type expansion: display, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DeviceUseRequest.subject` with unmapped reference targets: Patient.
DeviceUseRequest.timing[x]timing[x]is related toDeviceRequest.occurrence[x]DeviceRequest.occurrence[x]Element `DeviceUseRequest.timing[x]` is mapped to FHIR R4B element `DeviceRequest.occurrence[x]` as `RelatedTo`. The mappings for `DeviceUseRequest.timing[x]` do not cover the following types: Period, Timing. The target context `DeviceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`.
DeviceUseRequest.prioritypriorityis equivalent toDeviceRequest.priorityDeviceRequest.priorityElement `DeviceUseRequest.priority` is mapped to FHIR R4B element `DeviceRequest.priority` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.meta (meta)maps to wider conceptExtension (DSTU2: meta additional types)Element `DeviceUseRequest.meta` is mapped to FHIR R4B element `DeviceRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.meta` do not cover the following types: Meta. The mappings for `DeviceUseRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.text (text)maps to wider conceptExtension (DSTU2: text additional types)Element `DeviceUseRequest.text` is mapped to FHIR R4B element `DeviceRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.text` do not cover the following types: Narrative. The mappings for `DeviceUseRequest.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: Target body site (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.bodySite[x] (bodySite[x])is equivalent toExtension (DSTU2: Target body site (new))Element `DeviceUseRequest.bodySite[x]` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceUseRequest.bodySite[x]` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.status (status)maps to wider conceptExtension (DSTU2: proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted additional codes)Element `DeviceUseRequest.status` is mapped to FHIR R4B element `DeviceRequest.status` as `RelatedTo`. The mappings for `DeviceUseRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `DeviceRequest.status` is a modifier element, so this extension does not need to be defined as a modifier.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: Request identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.identifier (identifier)maps to wider conceptExtension (DSTU2: Request identifier additional types)Element `DeviceUseRequest.identifier` is mapped to FHIR R4B element `DeviceRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.identifier` do not cover the following types: Identifier. The mappings for `DeviceUseRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: notes additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.notes (notes)maps to wider conceptExtension (DSTU2: notes additional types)Element `DeviceUseRequest.notes` is mapped to FHIR R4B element `DeviceRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseRequest.notes` do not cover the following types: string. The mappings for `DeviceUseRequest.notes` do not cover the following types based on type expansion: value.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: PRN (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.prnReason (prnReason)is equivalent toExtension (DSTU2: PRN (new))Element `DeviceUseRequest.prnReason` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceUseRequest.prnReason` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseRequest|1.0.2 to DSTU2: Schedule for use additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseRequest.timing[x] (timing[x])maps to wider conceptExtension (DSTU2: Schedule for use additional types)Element `DeviceUseRequest.timing[x]` is mapped to FHIR R4B element `DeviceRequest.occurrence[x]` as `RelatedTo`. The mappings for `DeviceUseRequest.timing[x]` do not cover the following types: Period, Timing. The target context `DeviceRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`.