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

Lookup for Profile_R5_Requirements_R4

Lookup for FHIR R5 Requirements for use in FHIR R4

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

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

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

Source Element (FHIR R5) Target(s) Comments
Requirements    
Requirements.meta Basic.meta Element matches Basic element path Basic.meta (Resource.meta), use that element instead.
Element Requirements.meta is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.meta has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.implicitRules Basic.implicitRules Element matches Basic element path Basic.implicitRules (Resource.implicitRules), use that element instead.
Element Requirements.implicitRules is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.implicitRules has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.language Basic.language Element matches Basic element path Basic.language (Resource.language), use that element instead.
Element Requirements.language is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.text Basic.text Element matches Basic element path Basic.text (DomainResource.text), use that element instead.
Element Requirements.text is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.text has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.contained Basic.contained Element matches Basic element path Basic.contained (DomainResource.contained), use that element instead.
Element Requirements.contained is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.contained has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.url Extension: ExtensionRequirements_Url Element Requirements.url is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.url has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.identifier Basic.identifier Element matches Basic element path Basic.identifier (Basic.identifier), use that element instead.
Element Requirements.identifier is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.identifier has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.version Extension: ExtensionRequirements_Version Element Requirements.version is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.version has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.versionAlgorithm[x] Extension: ExtensionRequirements_VersionAlgorithm Element Requirements.versionAlgorithm[x] is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.versionAlgorithm[x] has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.name Extension: ExtensionRequirements_Name Element Requirements.name is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.name has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.title Extension: ExtensionRequirements_Title Element Requirements.title is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.title has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.status Modifier Extension: ExtensionRequirements_Status Element Requirements.status is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.status has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.experimental Extension: ExtensionRequirements_Experimental Element Requirements.experimental is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.experimental has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.date Extension: ExtensionRequirements_Date Element Requirements.date is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.date has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.publisher Extension: ExtensionRequirements_Publisher Element Requirements.publisher is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.publisher has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.contact Extension: ExtensionRequirements_Contact Element Requirements.contact is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.contact has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.description Extension: ExtensionRequirements_Description Element Requirements.description is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.description has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.useContext Extension: ExtensionRequirements_UseContext Element Requirements.useContext is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.useContext has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.jurisdiction Extension: ExtensionRequirements_Jurisdiction Element Requirements.jurisdiction is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.jurisdiction has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element Requirements.jurisdiction has been flagged as deprecated.
Requirements.purpose Extension: ExtensionRequirements_Purpose Element Requirements.purpose is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.purpose has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.copyright Extension: ExtensionRequirements_Copyright Element Requirements.copyright is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.copyright has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.copyrightLabel Extension: ExtensionRequirements_CopyrightLabel Element Requirements.copyrightLabel is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.copyrightLabel has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.derivedFrom Extension: ExtensionRequirements_DerivedFrom Element Requirements.derivedFrom is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.derivedFrom has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.reference Extension: ExtensionRequirements_Reference Element Requirements.reference is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.reference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.actor Extension: ExtensionRequirements_Actor Element Requirements.actor is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.actor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement Extension: ExtensionRequirements_Statement Element Requirements.statement is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.key Extension: ExtensionRequirements_Statement Slice:key Element Requirements.statement.key is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.key is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.key has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.label Extension: ExtensionRequirements_Statement Slice:label Element Requirements.statement.label is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.label is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.label has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.conformance Extension: ExtensionRequirements_Statement Slice:conformance Element Requirements.statement.conformance is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.conformance is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.conformance has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.conditionality Extension: ExtensionRequirements_Statement Slice:conditionality Element Requirements.statement.conditionality is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.conditionality is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.conditionality has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.requirement Extension: ExtensionRequirements_Statement Slice:requirement Element Requirements.statement.requirement is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.requirement is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.requirement has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.derivedFrom Extension: ExtensionRequirements_Statement Slice:derivedFrom Element Requirements.statement.derivedFrom is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.derivedFrom is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.derivedFrom has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.parent Extension: ExtensionRequirements_Statement Slice:parent Element Requirements.statement.parent is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.parent is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.parent has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.satisfiedBy Extension: ExtensionRequirements_Statement Slice:satisfiedBy Element Requirements.statement.satisfiedBy is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.satisfiedBy is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.satisfiedBy has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.reference Extension: ExtensionRequirements_Statement Slice:reference Element Requirements.statement.reference is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.reference is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.reference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Requirements.statement.source Extension: ExtensionRequirements_Statement Slice:source Element Requirements.statement.source is part of an existing definition because parent element Requirements.statement requires a cross-version extension.
Element Requirements.statement.source is not mapped to FHIR R4, since FHIR R5 Requirements is not mapped.
Element Requirements.statement.source has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).