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: R5FormularyItemElementMapToR4

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

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

Source CodeRelationshipTarget CodeComment
FormularyItem.meta (meta)​is equivalent toBasic.metaElement matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `FormularyItem.meta` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
FormularyItem.implicitRules (implicitRules)​is equivalent toBasic.implicitRulesElement matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `FormularyItem.implicitRules` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.implicitRules` has no mapping targets in FHIR R4. 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.
FormularyItem.language (language)​is equivalent toBasic.languageElement matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `FormularyItem.language` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.language` has no mapping targets in FHIR R4. 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).
FormularyItem.text (text)​is equivalent toBasic.textElement matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `FormularyItem.text` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.text` has no mapping targets in FHIR R4. 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.
FormularyItem.contained (contained)​is equivalent toBasic.containedElement matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `FormularyItem.contained` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.contained` has no mapping targets in FHIR R4. 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.
FormularyItem.identifier (identifier)​is equivalent toBasic.identifierElement matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `FormularyItem.identifier` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/FormularyItem|5.0.0 to R5: Codes that identify this formulary item (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
FormularyItem.code (code)​maps to wider conceptExtension (R5: Codes that identify this formulary item (new))Element `FormularyItem.code` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/FormularyItem|5.0.0 to R5: active | entered-in-error | inactive (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
FormularyItem.status (status)​maps to wider conceptExtension (R5: active | entered-in-error | inactive (new))Element `FormularyItem.status` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped. Element `FormularyItem.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This status is intended to identify if the formulary item in a local system is in active use within the formulary. For example, a formulary might include a medicinal product and the status relates to its inclusion. At some point in the future, if the status of the formulary item is changed to "inactive" that means that it is no longer valid in the formulary. But the product itself might still be in active use and might be included in other formularies.