Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU International flag

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

ConceptMap: R5DeviceUsageElementMapToR3

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceUsage-element-map-to-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5DeviceUsageElementMapToR3

This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceUsage to FHIR STU3.

Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|3.0.2

Source CodeRelationshipTarget CodeComment
DeviceUsage.meta (meta)​is equivalent toDeviceUseStatement.metaElement `DeviceUsage.meta` is mapped to FHIR STU3 element `DeviceUseStatement.meta` as `Equivalent`.
DeviceUsage.implicitRules (implicitRules)​is equivalent toDeviceUseStatement.implicitRulesElement `DeviceUsage.implicitRules` is mapped to FHIR STU3 element `DeviceUseStatement.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
DeviceUsage.language (language)​is equivalent toDeviceUseStatement.languageElement `DeviceUsage.language` is mapped to FHIR STU3 element `DeviceUseStatement.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).
DeviceUsage.text (text)​is equivalent toDeviceUseStatement.textElement `DeviceUsage.text` is mapped to FHIR STU3 element `DeviceUseStatement.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
DeviceUsage.contained (contained)​is equivalent toDeviceUseStatement.containedElement `DeviceUsage.contained` is mapped to FHIR STU3 element `DeviceUseStatement.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
DeviceUsage.identifier (identifier)​is equivalent toDeviceUseStatement.identifierElement `DeviceUsage.identifier` is mapped to FHIR STU3 element `DeviceUseStatement.identifier` as `Equivalent`.
DeviceUsage.status (status)​maps to wider conceptDeviceUseStatement.statusElement `DeviceUsage.status` is mapped to FHIR STU3 element `DeviceUseStatement.status` as `SourceIsBroaderThanTarget`. The target context `DeviceUseStatement.status` is a modifier element, so this extension does not need to be defined as a modifier. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error). This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.
DeviceUsage.patient (patient)​maps to wider conceptDeviceUseStatement.subjectElement `DeviceUsage.patient` is mapped to FHIR STU3 element `DeviceUseStatement.subject` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.patient` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DeviceUsage.patient` with unmapped reference targets: Patient.
DeviceUsage.timing[x] (timing[x])​is equivalent toDeviceUseStatement.timing[x]Element `DeviceUsage.timing[x]` is mapped to FHIR STU3 element `DeviceUseStatement.timing[x]` as `Equivalent`. The target context `DeviceUseStatement.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceUseStatement`.
DeviceUsage.dateAsserted (dateAsserted)​is equivalent toDeviceUseStatement.recordedOnElement `DeviceUsage.dateAsserted` is mapped to FHIR STU3 element `DeviceUseStatement.recordedOn` as `Equivalent`.
DeviceUsage.informationSource (informationSource)​maps to wider conceptDeviceUseStatement.sourceElement `DeviceUsage.informationSource` is mapped to FHIR STU3 element `DeviceUseStatement.source` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DeviceUsage.informationSource` with unmapped reference targets: Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.
DeviceUsage.device (device)​maps to wider conceptDeviceUseStatement.deviceElement `DeviceUsage.device` is mapped to FHIR STU3 element `DeviceUseStatement.device` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.device` do not cover the following types: CodeableReference. The mappings for `DeviceUsage.device` do not cover the following types based on type expansion: concept.
DeviceUsage.reason (reason)​is related toDeviceUseStatement.indicationElement `DeviceUsage.reason` is mapped to FHIR STU3 element `DeviceUseStatement.indication` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.reason` do not cover the following types: CodeableReference. When the status is not done, the reason code indicates why it was not done.
DeviceUsage.bodySite (bodySite)​maps to wider conceptDeviceUseStatement.bodySiteElement `DeviceUsage.bodySite` is mapped to FHIR STU3 element `DeviceUseStatement.bodySite` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.bodySite` do not cover the following types: CodeableReference. The mappings for `DeviceUsage.bodySite` do not cover the following types based on type expansion: reference.
DeviceUsage.note (note)​is equivalent toDeviceUseStatement.noteElement `DeviceUsage.note` is mapped to FHIR STU3 element `DeviceUseStatement.note` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: Fulfills plan, proposal or order (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.basedOn (basedOn)​is equivalent toExtension (R5: Fulfills plan, proposal or order (new))Element `DeviceUsage.basedOn` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.basedOn` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: active | completed | not-done | entered-in-error +version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.status (status)​maps to wider conceptExtension (R5: active | completed | not-done | entered-in-error +)Element `DeviceUsage.status` is mapped to FHIR STU3 element `DeviceUseStatement.status` as `SourceIsBroaderThanTarget`. The target context `DeviceUseStatement.status` is a modifier element, so this extension does not need to be defined as a modifier. DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error). This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: The category of the statement - classifying how the statement is made (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.category (category)​maps to wider conceptExtension (R5: The category of the statement - classifying how the statement is made (new))Element `DeviceUsage.category` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: Supporting information (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.derivedFrom (derivedFrom)​maps to wider conceptExtension (R5: Supporting information (new))Element `DeviceUsage.derivedFrom` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.derivedFrom` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The most common use cases for deriving a DeviceUsage comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUsage from.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: The encounter or episode of care that establishes the context for this device use statement (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.context (context)​maps to wider conceptExtension (R5: The encounter or episode of care that establishes the context for this device use statement (new))Element `DeviceUsage.context` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.context` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: The status of the device usage, for example always, sometimes, never. This is not the same as the status of the statement (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.usageStatus (usageStatus)​maps to wider conceptExtension (R5: The status of the device usage, for example always, sometimes, never. This is not the same as the status of the statement (new))Element `DeviceUsage.usageStatus` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.usageStatus` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: The reason for asserting the usage status - for example forgot, lost, stolen, broken (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.usageReason (usageReason)​maps to wider conceptExtension (R5: The reason for asserting the usage status - for example forgot, lost, stolen, broken (new))Element `DeviceUsage.usageReason` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.usageReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: How device is being used (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.adherence (adherence)​maps to wider conceptExtension (R5: How device is being used (new))Element `DeviceUsage.adherence` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.adherence` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceUsage.adherence.code (code)​maps to wider conceptExtension.extension:code (R5: always | never | sometimes (new))Element `DeviceUsage.adherence.code` is part of an existing definition because parent element `DeviceUsage.adherence` requires a cross-version extension. Element `DeviceUsage.adherence.code` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.adherence.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceUsage.adherence.reason (reason)​maps to wider conceptExtension.extension:reason (R5: lost | stolen | prescribed | broken | burned | forgot (new))Element `DeviceUsage.adherence.reason` is part of an existing definition because parent element `DeviceUsage.adherence` requires a cross-version extension. Element `DeviceUsage.adherence.reason` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`. Element `DeviceUsage.adherence.reason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: Code or Reference to device used additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.device (device)​maps to wider conceptExtension (R5: Code or Reference to device used additional types)Element `DeviceUsage.device` is mapped to FHIR STU3 element `DeviceUseStatement.device` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.device` do not cover the following types: CodeableReference. The mappings for `DeviceUsage.device` do not cover the following types based on type expansion: concept.

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: reason additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.reason (reason)​maps to wider conceptExtension (R5: reason additional types)Element `DeviceUsage.reason` is mapped to FHIR STU3 element `DeviceUseStatement.indication` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.reason` do not cover the following types: CodeableReference. When the status is not done, the reason code indicates why it was not done.

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUsage|5.0.0 to R5: bodySite additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUsage.bodySite (bodySite)​maps to wider conceptExtension (R5: bodySite additional types)Element `DeviceUsage.bodySite` is mapped to FHIR STU3 element `DeviceUseStatement.bodySite` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUsage.bodySite` do not cover the following types: CodeableReference. The mappings for `DeviceUsage.bodySite` do not cover the following types based on type expansion: reference.