R5DeviceDispenseElementMapToR3 - Extensions for Using Data Elements from FHIR R5 in FHIR STU3 v0.1.0

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

ConceptMap: R5DeviceDispenseElementMapToR3

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceDispense 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/DeviceDispense|5.0.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2

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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.meta` has no mapping targets in FHIR STU3. 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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.implicitRules` has no mapping targets in FHIR STU3. 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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.language` has no mapping targets in FHIR STU3. 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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.text` has no mapping targets in FHIR STU3. 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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.contained` has no mapping targets in FHIR STU3. 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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.identifier` has no mapping targets in FHIR STU3. 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 STU3, since FHIR R5 `DeviceDispense` is not mapped. Element `DeviceDispense.subject` has no mapping targets in FHIR STU3. 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)