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

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

Lookup for Profile_R5_FormularyItem_R4B

Lookup for FHIR R5 FormularyItem for use in FHIR R4B

The FHIR R5 resource is represented in FHIR R4B via the Basic resource.

Note that there is a profile defined to simplify use of this cross-version resource representation:Profile: FormularyItem

A computable version of the following element information is available in: R5FormularyItemElementMapToR4B

Source Element (FHIR R5) Target(s) Comments
FormularyItem    
FormularyItem.meta Basic.meta Element matches Basic element path Basic.meta (Resource.meta), use that element instead.
Element FormularyItem.meta is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.meta has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.implicitRules Basic.implicitRules Element matches Basic element path Basic.implicitRules (Resource.implicitRules), use that element instead.
Element FormularyItem.implicitRules is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.implicitRules has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.language Basic.language Element matches Basic element path Basic.language (Resource.language), use that element instead.
Element FormularyItem.language is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.language has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.text Basic.text Element matches Basic element path Basic.text (DomainResource.text), use that element instead.
Element FormularyItem.text is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.text has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.contained Basic.contained Element matches Basic element path Basic.contained (DomainResource.contained), use that element instead.
Element FormularyItem.contained is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.contained has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.identifier Basic.identifier Element matches Basic element path Basic.identifier (Basic.identifier), use that element instead.
Element FormularyItem.identifier is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.identifier has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.code Extension: ExtensionFormularyItem_Code Element FormularyItem.code is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.code has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
FormularyItem.status Modifier Extension: ExtensionFormularyItem_Status Element FormularyItem.status is not mapped to FHIR R4B, since FHIR R5 FormularyItem is not mapped.
Element FormularyItem.status has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).