Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
{
"resourceType" : "ConceptMap",
"id" : "R5-FormularyItem-element-map-to-R4",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ConceptMap R5-FormularyItem-element-map-to-R4</b></p><a name=\"R5-FormularyItem-element-map-to-R4\"> </a><a name=\"hcR5-FormularyItem-element-map-to-R4\"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/FormularyItem|5.0.0</code> to <a href=\"http://hl7.org/fhir/R4/basic.html\">Basicversion: 4.0.1)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>FormularyItem.meta (meta)</td><td><a href=\"CodeSystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Basic.meta</td><td>Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.\nElement `FormularyItem.meta` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>FormularyItem.implicitRules (implicitRules)</td><td><a href=\"CodeSystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Basic.implicitRules</td><td>Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.\nElement `FormularyItem.implicitRules` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nAsserting 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.</td></tr><tr><td>FormularyItem.language (language)</td><td><a href=\"CodeSystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Basic.language</td><td>Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.\nElement `FormularyItem.language` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nLanguage 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).</td></tr><tr><td>FormularyItem.text (text)</td><td><a href=\"CodeSystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Basic.text</td><td>Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.\nElement `FormularyItem.text` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nContained 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.</td></tr><tr><td>FormularyItem.contained (contained)</td><td><a href=\"CodeSystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Basic.contained</td><td>Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.\nElement `FormularyItem.contained` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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.</td></tr><tr><td>FormularyItem.identifier (identifier)</td><td><a href=\"CodeSystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Basic.identifier</td><td>Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.\nElement `FormularyItem.identifier` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/FormularyItem|5.0.0</code> to <a href=\"StructureDefinition-ext-R5-FormularyItem.code.html\">R5: Codes that identify this formulary item (new)version: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>FormularyItem.code (code)</td><td><a href=\"CodeSystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Extension (R5: Codes that identify this formulary item (new))</td><td>Element `FormularyItem.code` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/FormularyItem|5.0.0</code> to <a href=\"StructureDefinition-ext-R5-FormularyItem.status.html\">R5: active | entered-in-error | inactive (new)version: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>FormularyItem.status (status)</td><td><a href=\"CodeSystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Extension (R5: active | entered-in-error | inactive (new))</td><td>Element `FormularyItem.status` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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.</td></tr></table></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "fhir"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 0,
"_valueInteger" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
]
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/xver/ConceptMap/R5-FormularyItem-element-map-to-R4",
"version" : "0.1.0",
"name" : "R5FormularyItemElementMapToR4",
"title" : "Cross-version mapping for FHIR R5 FormularyItem to FHIR R4 Basic",
"status" : "active",
"experimental" : false,
"date" : "2026-03-17T16:04:45.47395-05:00",
"contact" : [
{
"name" : "FHIR Infrastructure",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description" : "This ConceptMap represents cross-version mappings for elements from a FHIR R5 FormularyItem to FHIR R4.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"sourceCanonical" : "http://hl7.org/fhir/5.0",
"targetUri" : "http://hl7.org/fhir/4.0",
"group" : [
{
"source" : "http://hl7.org/fhir/StructureDefinition/FormularyItem",
"sourceVersion" : "5.0.0",
"target" : "http://hl7.org/fhir/StructureDefinition/Basic",
"targetVersion" : "4.0.1",
"element" : [
{
"code" : "FormularyItem.meta",
"display" : "meta",
"target" : [
{
"code" : "Basic.meta",
"display" : "Basic.meta",
"equivalence" : "equivalent",
"comment" : "Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.\nElement `FormularyItem.meta` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code" : "FormularyItem.implicitRules",
"display" : "implicitRules",
"target" : [
{
"code" : "Basic.implicitRules",
"display" : "Basic.implicitRules",
"equivalence" : "equivalent",
"comment" : "Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.\nElement `FormularyItem.implicitRules` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nAsserting 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."
}
]
},
{
"code" : "FormularyItem.language",
"display" : "language",
"target" : [
{
"code" : "Basic.language",
"display" : "Basic.language",
"equivalence" : "equivalent",
"comment" : "Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.\nElement `FormularyItem.language` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nLanguage 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)."
}
]
},
{
"code" : "FormularyItem.text",
"display" : "text",
"target" : [
{
"code" : "Basic.text",
"display" : "Basic.text",
"equivalence" : "equivalent",
"comment" : "Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.\nElement `FormularyItem.text` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nContained 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."
}
]
},
{
"code" : "FormularyItem.contained",
"display" : "contained",
"target" : [
{
"code" : "Basic.contained",
"display" : "Basic.contained",
"equivalence" : "equivalent",
"comment" : "Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.\nElement `FormularyItem.contained` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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."
}
]
},
{
"code" : "FormularyItem.identifier",
"display" : "identifier",
"target" : [
{
"code" : "Basic.identifier",
"display" : "Basic.identifier",
"equivalence" : "equivalent",
"comment" : "Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.\nElement `FormularyItem.identifier` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source" : "http://hl7.org/fhir/StructureDefinition/FormularyItem",
"sourceVersion" : "5.0.0",
"target" : "http://hl7.org/fhir/5.0/StructureDefinition/extension-FormularyItem.code",
"targetVersion" : "0.1.0",
"element" : [
{
"code" : "FormularyItem.code",
"display" : "code",
"target" : [
{
"code" : "Extension",
"equivalence" : "wider",
"comment" : "Element `FormularyItem.code` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source" : "http://hl7.org/fhir/StructureDefinition/FormularyItem",
"sourceVersion" : "5.0.0",
"target" : "http://hl7.org/fhir/5.0/StructureDefinition/extension-FormularyItem.status",
"targetVersion" : "0.1.0",
"element" : [
{
"code" : "FormularyItem.status",
"display" : "status",
"target" : [
{
"code" : "Extension",
"equivalence" : "wider",
"comment" : "Element `FormularyItem.status` is not mapped to FHIR R4, since FHIR R5 `FormularyItem` is not mapped.\nElement `FormularyItem.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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."
}
]
}
]
}
]
}
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change