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

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

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

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

Source CodeRelationshipTarget CodeComment
InventoryReport.status (status)​maps to wider conceptExtension (R5: draft | requested | active | entered-in-error (new))Element `InventoryReport.status` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.status` 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/InventoryReport|5.0.0 to R5: snapshot | difference (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.countType (countType)​maps to wider conceptExtension (R5: snapshot | difference (new))Element `InventoryReport.countType` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.countType` 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/InventoryReport|5.0.0 to R5: addition | subtraction (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.operationType (operationType)​maps to wider conceptExtension (R5: addition | subtraction (new))Element `InventoryReport.operationType` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.operationType` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/InventoryReport|5.0.0 to R5: The reason for this count - regular count, ad-hoc count, new arrivals, etc (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.operationTypeReason (operationTypeReason)​maps to wider conceptExtension (R5: The reason for this count - regular count, ad-hoc count, new arrivals, etc (new))Element `InventoryReport.operationTypeReason` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.operationTypeReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/InventoryReport|5.0.0 to R5: When the report has been submitted (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.reportedDateTime (reportedDateTime)​maps to wider conceptExtension (R5: When the report has been submitted (new))Element `InventoryReport.reportedDateTime` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.reportedDateTime` 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/InventoryReport|5.0.0 to R5: Who submits the report (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.reporter (reporter)​maps to wider conceptExtension (R5: Who submits the report (new))Element `InventoryReport.reporter` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.reporter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/InventoryReport|5.0.0 to R5: The period the report refers to (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.reportingPeriod (reportingPeriod)​maps to wider conceptExtension (R5: The period the report refers to (new))Element `InventoryReport.reportingPeriod` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.reportingPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/InventoryReport|5.0.0 to R5: An inventory listing section (grouped by any of the attributes) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.inventoryListing (inventoryListing)​maps to wider conceptExtension (R5: An inventory listing section (grouped by any of the attributes) (new))Element `InventoryReport.inventoryListing` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.location (location)​maps to wider conceptExtension.extension:location (R5: Location of the inventory items (new))Element `InventoryReport.inventoryListing.location` is part of an existing definition because parent element `InventoryReport.inventoryListing` requires a cross-version extension. Element `InventoryReport.inventoryListing.location` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.location` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.itemStatus (itemStatus)​maps to wider conceptExtension.extension:itemStatus (R5: The status of the items that are being reported (new))Element `InventoryReport.inventoryListing.itemStatus` is part of an existing definition because parent element `InventoryReport.inventoryListing` requires a cross-version extension. Element `InventoryReport.inventoryListing.itemStatus` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.itemStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.countingDateTime (countingDateTime)​maps to wider conceptExtension.extension:countingDateTime (R5: The date and time when the items were counted (new))Element `InventoryReport.inventoryListing.countingDateTime` is part of an existing definition because parent element `InventoryReport.inventoryListing` requires a cross-version extension. Element `InventoryReport.inventoryListing.countingDateTime` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.countingDateTime` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.item (item)​maps to wider conceptExtension.extension:item (R5: The item or items in this listing (new))Element `InventoryReport.inventoryListing.item` is part of an existing definition because parent element `InventoryReport.inventoryListing` requires a cross-version extension. Element `InventoryReport.inventoryListing.item` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.item` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.item.category (category)​maps to wider conceptExtension.extension:item.extension:category (R5: The inventory category or classification of the items being reported (new))Element `InventoryReport.inventoryListing.item.category` is part of an existing definition because parent element `InventoryReport.inventoryListing.item` requires a cross-version extension. Element `InventoryReport.inventoryListing.item.category` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.item.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.item.quantity (quantity)​maps to wider conceptExtension.extension:item.extension:quantity (R5: The quantity of the item or items being reported (new))Element `InventoryReport.inventoryListing.item.quantity` is part of an existing definition because parent element `InventoryReport.inventoryListing.item` requires a cross-version extension. Element `InventoryReport.inventoryListing.item.quantity` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.item.quantity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
InventoryReport.inventoryListing.item.item (item)​maps to wider conceptExtension.extension:item.extension:item (R5: The code or reference to the item type (new))Element `InventoryReport.inventoryListing.item.item` is part of an existing definition because parent element `InventoryReport.inventoryListing.item` requires a cross-version extension. Element `InventoryReport.inventoryListing.item.item` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.inventoryListing.item.item` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/InventoryReport|5.0.0 to R5: A note associated with the InventoryReport (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
InventoryReport.note (note)​maps to wider conceptExtension (R5: A note associated with the InventoryReport (new))Element `InventoryReport.note` is not mapped to FHIR R4, since FHIR R5 `InventoryReport` is not mapped. Element `InventoryReport.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).