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

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

ConceptMap: R5DeviceRequestElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceRequest to FHIR 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/DeviceRequest|5.0.0 to DeviceRequestversion: 4.0.1)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/DeviceRequest|5.0.0Codes from DeviceRequest
DeviceRequest.metameta​is equivalent toDeviceRequest.metaDeviceRequest.metaElement `DeviceRequest.meta` is mapped to FHIR R4 element `DeviceRequest.meta` as `Equivalent`.
DeviceRequest.implicitRulesimplicitRules​is equivalent toDeviceRequest.implicitRulesDeviceRequest.implicitRulesElement `DeviceRequest.implicitRules` is mapped to FHIR R4 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. 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.
DeviceRequest.languagelanguage​is equivalent toDeviceRequest.languageDeviceRequest.languageElement `DeviceRequest.language` is mapped to FHIR R4 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).
DeviceRequest.texttext​is equivalent toDeviceRequest.textDeviceRequest.textElement `DeviceRequest.text` is mapped to FHIR R4 element `DeviceRequest.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.
DeviceRequest.containedcontained​is equivalent toDeviceRequest.containedDeviceRequest.containedElement `DeviceRequest.contained` is mapped to FHIR R4 element `DeviceRequest.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.
DeviceRequest.identifieridentifier​is equivalent toDeviceRequest.identifierDeviceRequest.identifierElement `DeviceRequest.identifier` is mapped to FHIR R4 element `DeviceRequest.identifier` as `Equivalent`.
DeviceRequest.instantiatesCanonicalinstantiatesCanonical​is equivalent toDeviceRequest.instantiatesCanonicalDeviceRequest.instantiatesCanonicalElement `DeviceRequest.instantiatesCanonical` is mapped to FHIR R4 element `DeviceRequest.instantiatesCanonical` as `Equivalent`. Note: This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
DeviceRequest.instantiatesUriinstantiatesUri​is equivalent toDeviceRequest.instantiatesUriDeviceRequest.instantiatesUriElement `DeviceRequest.instantiatesUri` is mapped to FHIR R4 element `DeviceRequest.instantiatesUri` as `Equivalent`. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
DeviceRequest.basedOnbasedOn​is equivalent toDeviceRequest.basedOnDeviceRequest.basedOnElement `DeviceRequest.basedOn` is mapped to FHIR R4 element `DeviceRequest.basedOn` as `Equivalent`.
DeviceRequest.replacesreplaces​maps to wider conceptDeviceRequest.priorRequestDeviceRequest.priorRequestElement `DeviceRequest.replaces` is mapped to FHIR R4 element `DeviceRequest.priorRequest` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.replaces` 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 `DeviceRequest.replaces` with unmapped reference targets: DeviceRequest.
DeviceRequest.groupIdentifiergroupIdentifier​is equivalent toDeviceRequest.groupIdentifierDeviceRequest.groupIdentifierElement `DeviceRequest.groupIdentifier` is mapped to FHIR R4 element `DeviceRequest.groupIdentifier` as `Equivalent`.
DeviceRequest.statusstatus​is equivalent toDeviceRequest.statusDeviceRequest.statusElement `DeviceRequest.status` is mapped to FHIR R4 element `DeviceRequest.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes revoked and entered-in-error that mark the request as not currently valid.
DeviceRequest.intentintent​is equivalent toDeviceRequest.intentDeviceRequest.intentElement `DeviceRequest.intent` is mapped to FHIR R4 element `DeviceRequest.intent` as `Equivalent`.
DeviceRequest.prioritypriority​is equivalent toDeviceRequest.priorityDeviceRequest.priorityElement `DeviceRequest.priority` is mapped to FHIR R4 element `DeviceRequest.priority` as `Equivalent`.
DeviceRequest.codecode​is equivalent toDeviceRequest.code[x]DeviceRequest.code[x]Element `DeviceRequest.code` is mapped to FHIR R4 element `DeviceRequest.code[x]` as `SourceIsBroaderThanTarget`. The target context `DeviceRequest.code[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest`.
DeviceRequest.parameterparameter​maps to wider conceptDeviceRequest.parameterDeviceRequest.parameterElement `DeviceRequest.parameter` is mapped to FHIR R4 element `DeviceRequest.parameter` as `Equivalent`.
DeviceRequest.parameter.codecode​is equivalent toDeviceRequest.parameter.codeDeviceRequest.parameter.codeElement `DeviceRequest.parameter.code` is mapped to FHIR R4 element `DeviceRequest.parameter.code` as `Equivalent`.
DeviceRequest.parameter.value[x]value[x]​is equivalent toDeviceRequest.parameter.value[x]DeviceRequest.parameter.value[x]Element `DeviceRequest.parameter.value[x]` is mapped to FHIR R4 element `DeviceRequest.parameter.value[x]` as `Equivalent`. The target context `DeviceRequest.parameter.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceRequest.parameter`. Range means device should have a value that falls somewhere within the specified range.
DeviceRequest.subjectsubject​is equivalent toDeviceRequest.subjectDeviceRequest.subjectElement `DeviceRequest.subject` is mapped to FHIR R4 element `DeviceRequest.subject` as `Equivalent`.
DeviceRequest.encounterencounter​is equivalent toDeviceRequest.encounterDeviceRequest.encounterElement `DeviceRequest.encounter` is mapped to FHIR R4 element `DeviceRequest.encounter` as `Equivalent`.
DeviceRequest.occurrence[x]occurrence[x]​is equivalent toDeviceRequest.occurrence[x]DeviceRequest.occurrence[x]Element `DeviceRequest.occurrence[x]` is mapped to FHIR R4 element `DeviceRequest.occurrence[x]` as `Equivalent`. 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`.
DeviceRequest.authoredOnauthoredOn​is equivalent toDeviceRequest.authoredOnDeviceRequest.authoredOnElement `DeviceRequest.authoredOn` is mapped to FHIR R4 element `DeviceRequest.authoredOn` as `Equivalent`.
DeviceRequest.requesterrequester​is equivalent toDeviceRequest.requesterDeviceRequest.requesterElement `DeviceRequest.requester` is mapped to FHIR R4 element `DeviceRequest.requester` as `Equivalent`.
DeviceRequest.performerperformer​is related toDeviceRequest.performerDeviceRequest.performerElement `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performerType` as `SourceIsBroaderThanTarget`. Element `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performer` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.performer` do not cover the following types: CodeableReference.
​is related toDeviceRequest.performerTypeDeviceRequest.performerTypeElement `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performerType` as `SourceIsBroaderThanTarget`. Element `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performer` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.performer` do not cover the following types: CodeableReference.
DeviceRequest.reasonreason​is related toDeviceRequest.reasonCodeDeviceRequest.reasonCodeElement `DeviceRequest.reason` is mapped to FHIR R4 element `DeviceRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `DeviceRequest.reason` is mapped to FHIR R4 element `DeviceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.reason` do not cover the following types: CodeableReference.
​is related toDeviceRequest.reasonReferenceDeviceRequest.reasonReferenceElement `DeviceRequest.reason` is mapped to FHIR R4 element `DeviceRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `DeviceRequest.reason` is mapped to FHIR R4 element `DeviceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.reason` do not cover the following types: CodeableReference.
DeviceRequest.insuranceinsurance​is equivalent toDeviceRequest.insuranceDeviceRequest.insuranceElement `DeviceRequest.insurance` is mapped to FHIR R4 element `DeviceRequest.insurance` as `Equivalent`.
DeviceRequest.supportingInfosupportingInfo​is equivalent toDeviceRequest.supportingInfoDeviceRequest.supportingInfoElement `DeviceRequest.supportingInfo` is mapped to FHIR R4 element `DeviceRequest.supportingInfo` as `Equivalent`.
DeviceRequest.notenote​is equivalent toDeviceRequest.noteDeviceRequest.noteElement `DeviceRequest.note` is mapped to FHIR R4 element `DeviceRequest.note` as `Equivalent`.
DeviceRequest.relevantHistoryrelevantHistory​is equivalent toDeviceRequest.relevantHistoryDeviceRequest.relevantHistoryElement `DeviceRequest.relevantHistory` is mapped to FHIR R4 element `DeviceRequest.relevantHistory` as `Equivalent`. 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.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|5.0.0 to R5: True if the request is to stop or not to start using the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.doNotPerform (doNotPerform)​maps to wider conceptExtension (R5: True if the request is to stop or not to start using the device (new))Element `DeviceRequest.doNotPerform` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceRequest.doNotPerform` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If do not perform is not specified, the request is a positive request e.g. "do perform". DeviceRequest.reasonCode includes the reason for marking the DeviceRequest as 'do not perform'.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|5.0.0 to R5: Quantity of devices to supply (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.quantity (quantity)​maps to wider conceptExtension (R5: Quantity of devices to supply (new))Element `DeviceRequest.quantity` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceRequest.quantity` 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/DeviceRequest|5.0.0 to R5: Requested Filler additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.performer (performer)​maps to wider conceptExtension (R5: Requested Filler additional types)Element `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performerType` as `SourceIsBroaderThanTarget`. Element `DeviceRequest.performer` is mapped to FHIR R4 element `DeviceRequest.performer` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.performer` do not cover the following types: CodeableReference.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|5.0.0 to R5: Coded/Linked Reason for request additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.reason (reason)​maps to wider conceptExtension (R5: Coded/Linked Reason for request additional types)Element `DeviceRequest.reason` is mapped to FHIR R4 element `DeviceRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `DeviceRequest.reason` is mapped to FHIR R4 element `DeviceRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `DeviceRequest.reason` do not cover the following types: CodeableReference.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|5.0.0 to R5: PRN status of request (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.asNeeded (asNeeded)​maps to wider conceptExtension (R5: PRN status of request (new))Element `DeviceRequest.asNeeded` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceRequest.asNeeded` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceRequest|5.0.0 to R5: Device usage reason (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceRequest.asNeededFor (asNeededFor)​maps to wider conceptExtension (R5: Device usage reason (new))Element `DeviceRequest.asNeededFor` has a context of DeviceRequest based on following the parent source element upwards and mapping to `DeviceRequest`. Element `DeviceRequest.asNeededFor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).