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

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

Lookup for Profile_R5_RegulatedAuthorization_R3

Lookup for FHIR R5 RegulatedAuthorization for use in FHIR STU3

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

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

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

Source Element (FHIR R5) Target(s) Comments
RegulatedAuthorization    
RegulatedAuthorization.meta Basic.meta Element matches Basic element path Basic.meta (Resource.meta), use that element instead.
Element RegulatedAuthorization.meta is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.meta has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.implicitRules Basic.implicitRules Element matches Basic element path Basic.implicitRules (Resource.implicitRules), use that element instead.
Element RegulatedAuthorization.implicitRules is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.implicitRules has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.language Basic.language Element matches Basic element path Basic.language (Resource.language), use that element instead.
Element RegulatedAuthorization.language is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.language has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.text Basic.text Element matches Basic element path Basic.text (DomainResource.text), use that element instead.
Element RegulatedAuthorization.text is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.text has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.contained Basic.contained Element matches Basic element path Basic.contained (DomainResource.contained), use that element instead.
Element RegulatedAuthorization.contained is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.contained has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.identifier Basic.identifier Element matches Basic element path Basic.identifier (Basic.identifier), use that element instead.
Element RegulatedAuthorization.identifier is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.identifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.subject Basic.subject Element matches Basic element path Basic.subject (Basic.subject), use that element instead.
Element RegulatedAuthorization.subject is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.subject has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.type Extension: ExtensionRegulatedAuthorization_Type Element RegulatedAuthorization.type is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.description Extension: ExtensionRegulatedAuthorization_Description Element RegulatedAuthorization.description is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.description has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.region Extension: ExtensionRegulatedAuthorization_Region Element RegulatedAuthorization.region is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.region has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.status Extension: ExtensionRegulatedAuthorization_Status Element RegulatedAuthorization.status is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.status has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.statusDate Extension: ExtensionRegulatedAuthorization_StatusDate Element RegulatedAuthorization.statusDate is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.statusDate has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.validityPeriod Extension: ExtensionRegulatedAuthorization_ValidityPeriod Element RegulatedAuthorization.validityPeriod is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.validityPeriod has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.indication Extension: ExtensionRegulatedAuthorization_Indication Element RegulatedAuthorization.indication is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.indication has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.intendedUse Extension: ExtensionRegulatedAuthorization_IntendedUse Element RegulatedAuthorization.intendedUse is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.intendedUse has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.basis Extension: ExtensionRegulatedAuthorization_Basis Element RegulatedAuthorization.basis is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.basis has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.holder Extension: ExtensionRegulatedAuthorization_Holder Element RegulatedAuthorization.holder is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.holder has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.regulator Extension: ExtensionRegulatedAuthorization_Regulator Element RegulatedAuthorization.regulator is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.regulator has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.attachedDocument Extension: ExtensionRegulatedAuthorization_AttachedDocument Element RegulatedAuthorization.attachedDocument is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.attachedDocument has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.case Extension: ExtensionRegulatedAuthorization_Case Element RegulatedAuthorization.case is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.case has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.case.identifier Extension: ExtensionRegulatedAuthorization_Case Slice:identifier Element RegulatedAuthorization.case.identifier is part of an existing definition because parent element RegulatedAuthorization.case requires a cross-version extension.
Element RegulatedAuthorization.case.identifier is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.case.identifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.case.type Extension: ExtensionRegulatedAuthorization_Case Slice:type Element RegulatedAuthorization.case.type is part of an existing definition because parent element RegulatedAuthorization.case requires a cross-version extension.
Element RegulatedAuthorization.case.type is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.case.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.case.status Extension: ExtensionRegulatedAuthorization_Case Slice:status Element RegulatedAuthorization.case.status is part of an existing definition because parent element RegulatedAuthorization.case requires a cross-version extension.
Element RegulatedAuthorization.case.status is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.case.status has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.case.date[x] Extension: ExtensionRegulatedAuthorization_Case Slice:date Element RegulatedAuthorization.case.date[x] is part of an existing definition because parent element RegulatedAuthorization.case requires a cross-version extension.
Element RegulatedAuthorization.case.date[x] is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.case.date[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
RegulatedAuthorization.case.application Extension: ExtensionRegulatedAuthorization_Case Slice:application Element RegulatedAuthorization.case.application is part of an existing definition because parent element RegulatedAuthorization.case requires a cross-version extension.
Element RegulatedAuthorization.case.application is not mapped to FHIR STU3, since FHIR R5 RegulatedAuthorization is not mapped.
Element RegulatedAuthorization.case.application has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).