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_Permission_R4

Lookup for FHIR R5 Permission 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: Permission

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

Source Element (FHIR R5) Target(s) Comments
Permission    
Permission.meta Basic.meta Element matches Basic element path Basic.meta (Resource.meta), use that element instead.
Element Permission.meta is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.meta has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.implicitRules Basic.implicitRules Element matches Basic element path Basic.implicitRules (Resource.implicitRules), use that element instead.
Element Permission.implicitRules is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.implicitRules has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.language Basic.language Element matches Basic element path Basic.language (Resource.language), use that element instead.
Element Permission.language is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.language has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.text Basic.text Element matches Basic element path Basic.text (DomainResource.text), use that element instead.
Element Permission.text is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.text has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.contained Basic.contained Element matches Basic element path Basic.contained (DomainResource.contained), use that element instead.
Element Permission.contained is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.contained has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.status Extension: ExtensionPermission_Status Element Permission.status is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.status has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.asserter Extension: ExtensionPermission_Asserter Element Permission.asserter is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.asserter has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.date Extension: ExtensionPermission_Date Element Permission.date is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.date has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.validity Extension: ExtensionPermission_Validity Element Permission.validity is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.validity has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.justification Extension: ExtensionPermission_Justification Element Permission.justification is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.justification has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.justification.basis Extension: ExtensionPermission_Justification Slice:basis Element Permission.justification.basis is part of an existing definition because parent element Permission.justification requires a cross-version extension.
Element Permission.justification.basis is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.justification.basis has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.justification.evidence Extension: ExtensionPermission_Justification Slice:evidence Element Permission.justification.evidence is part of an existing definition because parent element Permission.justification requires a cross-version extension.
Element Permission.justification.evidence is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.justification.evidence has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.combining Modifier Extension: ExtensionPermission_Combining Element Permission.combining is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.combining has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule Modifier Extension: ExtensionPermission_Rule Element Permission.rule is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Child element type is a modifier, so this extension must be a modifier.
Permission.rule.type Extension: ExtensionPermission_Rule Slice:type Element Permission.rule.type is part of an existing definition because parent element Permission.rule requires a cross-version extension.
Element Permission.rule.type is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.type has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data Extension: ExtensionPermission_Rule Slice:data Element Permission.rule.data is part of an existing definition because parent element Permission.rule requires a cross-version extension.
Element Permission.rule.data is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data.resource Extension: ExtensionPermission_Rule_Data Slice:resource Element Permission.rule.data.resource is part of an existing definition because parent element Permission.rule.data requires a cross-version extension.
Element Permission.rule.data.resource is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data.resource has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data.resource.meaning Extension: ExtensionPermission_Rule_Data_Resource Slice:meaning Element Permission.rule.data.resource.meaning is part of an existing definition because parent element Permission.rule.data.resource requires a cross-version extension.
Element Permission.rule.data.resource.meaning is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data.resource.meaning has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data.resource.reference Extension: ExtensionPermission_Rule_Data_Resource Slice:reference Element Permission.rule.data.resource.reference is part of an existing definition because parent element Permission.rule.data.resource requires a cross-version extension.
Element Permission.rule.data.resource.reference is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data.resource.reference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data.security Extension: ExtensionPermission_Rule_Data Slice:security Element Permission.rule.data.security is part of an existing definition because parent element Permission.rule.data requires a cross-version extension.
Element Permission.rule.data.security is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data.security has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data.period Extension: ExtensionPermission_Rule_Data Slice:period Element Permission.rule.data.period is part of an existing definition because parent element Permission.rule.data requires a cross-version extension.
Element Permission.rule.data.period is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data.period has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.data.expression Extension: ExtensionPermission_Rule_Data Slice:expression Element Permission.rule.data.expression is part of an existing definition because parent element Permission.rule.data requires a cross-version extension.
Element Permission.rule.data.expression is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.data.expression has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.activity Extension: ExtensionPermission_Rule Slice:activity Element Permission.rule.activity is part of an existing definition because parent element Permission.rule requires a cross-version extension.
Element Permission.rule.activity is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.activity has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.activity.actor Extension: ExtensionPermission_Rule_Activity Slice:actor Element Permission.rule.activity.actor is part of an existing definition because parent element Permission.rule.activity requires a cross-version extension.
Element Permission.rule.activity.actor is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.activity.actor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.activity.action Extension: ExtensionPermission_Rule_Activity Slice:action Element Permission.rule.activity.action is part of an existing definition because parent element Permission.rule.activity requires a cross-version extension.
Element Permission.rule.activity.action is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.activity.action has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.activity.purpose Extension: ExtensionPermission_Rule_Activity Slice:purpose Element Permission.rule.activity.purpose is part of an existing definition because parent element Permission.rule.activity requires a cross-version extension.
Element Permission.rule.activity.purpose is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.activity.purpose has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Permission.rule.limit Extension: ExtensionPermission_Rule Slice:limit Element Permission.rule.limit is part of an existing definition because parent element Permission.rule requires a cross-version extension.
Element Permission.rule.limit is not mapped to FHIR R4, since FHIR R5 Permission is not mapped.
Element Permission.rule.limit has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).