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

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

ConceptMap: R4DeviceUseStatementElementMapToR5

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4 DeviceUseStatement to FHIR R5.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|4.0.1 to DeviceUsageversion: 5.0.0)

Source CodeRelationshipTarget CodeComment
DeviceUseStatement.meta (meta)is equivalent toDeviceUsage.metaElement `DeviceUseStatement.meta` is mapped to FHIR R5 element `DeviceUsage.meta` as `Equivalent`.
DeviceUseStatement.implicitRules (implicitRules)is equivalent toDeviceUsage.implicitRulesElement `DeviceUseStatement.implicitRules` is mapped to FHIR R5 element `DeviceUsage.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 it's narrative along with other profiles, value sets, etc.
DeviceUseStatement.language (language)is equivalent toDeviceUsage.languageElement `DeviceUseStatement.language` is mapped to FHIR R5 element `DeviceUsage.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).
DeviceUseStatement.text (text)is equivalent toDeviceUsage.textElement `DeviceUseStatement.text` is mapped to FHIR R5 element `DeviceUsage.text` as `Equivalent`. Contained resources do not have 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.
DeviceUseStatement.contained (contained)is equivalent toDeviceUsage.containedElement `DeviceUseStatement.contained` is mapped to FHIR R5 element `DeviceUsage.contained` as `Equivalent`. 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.
DeviceUseStatement.identifier (identifier)is equivalent toDeviceUsage.identifierElement `DeviceUseStatement.identifier` is mapped to FHIR R5 element `DeviceUsage.identifier` as `Equivalent`.
DeviceUseStatement.basedOn (basedOn)is equivalent toDeviceUsage.basedOnElement `DeviceUseStatement.basedOn` is mapped to FHIR R5 element `DeviceUsage.basedOn` as `Equivalent`.
DeviceUseStatement.status (status)is narrower thanDeviceUsage.statusElement `DeviceUseStatement.status` is mapped to FHIR R5 element `DeviceUsage.status` as `SourceIsNarrowerThanTarget`. The mappings for `DeviceUseStatement.status` do not allow expression of the necessary codes, per the bindings on the source and target. 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.
DeviceUseStatement.subject (subject)is broader thanDeviceUsage.patientElement `DeviceUseStatement.subject` is mapped to FHIR R5 element `DeviceUsage.patient` as `SourceIsBroaderThanTarget`. The mappings for `DeviceUseStatement.subject` 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 R4 element `DeviceUseStatement.subject` with unmapped reference targets: Group.
DeviceUseStatement.derivedFrom (derivedFrom)is narrower thanDeviceUsage.derivedFromElement `DeviceUseStatement.derivedFrom` is mapped to FHIR R5 element `DeviceUsage.derivedFrom` as `SourceIsNarrowerThanTarget`. The most common use cases for deriving a DeviceUseStatement 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 DeviceUseStatement from.
DeviceUseStatement.timing[x] (timing[x])is equivalent toDeviceUsage.timing[x]Element `DeviceUseStatement.timing[x]` is mapped to FHIR R5 element `DeviceUsage.timing[x]` as `Equivalent`. The target context `DeviceUsage.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceUsage`.
DeviceUseStatement.recordedOn (recordedOn)is equivalent toDeviceUsage.dateAssertedElement `DeviceUseStatement.recordedOn` is mapped to FHIR R5 element `DeviceUsage.dateAsserted` as `Equivalent`.
DeviceUseStatement.source (source)is equivalent toDeviceUsage.informationSourceElement `DeviceUseStatement.source` is mapped to FHIR R5 element `DeviceUsage.informationSource` as `Equivalent`.
DeviceUseStatement.device (device)is narrower thanDeviceUsage.deviceElement `DeviceUseStatement.device` is mapped to FHIR R5 element `DeviceUsage.device` as `SourceIsNarrowerThanTarget`.
DeviceUseStatement.reasonCode (reasonCode)is narrower thanDeviceUsage.reasonElement `DeviceUseStatement.reasonCode` is mapped to FHIR R5 element `DeviceUsage.reason` as `SourceIsNarrowerThanTarget`.
DeviceUseStatement.reasonReference (reasonReference)is related toDeviceUsage.reasonElement `DeviceUseStatement.reasonReference` is mapped to FHIR R5 element `DeviceUsage.reason` as `RelatedTo`. The mappings for `DeviceUseStatement.reasonReference` do not cover the following types: Reference.
DeviceUseStatement.bodySite (bodySite)is narrower thanDeviceUsage.bodySiteElement `DeviceUseStatement.bodySite` is mapped to FHIR R5 element `DeviceUsage.bodySite` as `SourceIsNarrowerThanTarget`.
DeviceUseStatement.note (note)is equivalent toDeviceUsage.noteElement `DeviceUseStatement.note` is mapped to FHIR R5 element `DeviceUsage.note` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|4.0.1 to R4: Why was DeviceUseStatement performed? additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceUseStatement.reasonReference (reasonReference)is broader thanExtension (R4: Why was DeviceUseStatement performed? additional types)Element `DeviceUseStatement.reasonReference` is mapped to FHIR R5 element `DeviceUsage.reason` as `RelatedTo`. The mappings for `DeviceUseStatement.reasonReference` do not cover the following types: Reference.