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

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

Lookup for Profile_R3_Schedule_R4B

Lookup for FHIR STU3 Schedule for use in FHIR R4B

The FHIR STU3 resource is represented in FHIR R4B via the Schedule resource.

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

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

Source Element (FHIR STU3) Target(s) Comments
Schedule    
Schedule.meta Schedule.meta
Extension: ExtensionSchedule_Meta
Element Schedule.meta is mapped to FHIR R4B element Schedule.meta as SourceIsBroaderThanTarget.
The mappings for Schedule.meta do not cover the following types: Meta.
The mappings for Schedule.meta do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Schedule.implicitRules Schedule.implicitRules Element Schedule.implicitRules is mapped to FHIR R4B element Schedule.implicitRules as Equivalent.
Schedule.language Schedule.language Element Schedule.language is mapped to FHIR R4B element Schedule.language as Equivalent.
Schedule.text Schedule.text
Extension: ExtensionSchedule_Text
Element Schedule.text is mapped to FHIR R4B element Schedule.text as SourceIsBroaderThanTarget.
The mappings for Schedule.text do not cover the following types: Narrative.
The mappings for Schedule.text do not cover the following types based on type expansion: div, status.
Schedule.contained Schedule.contained Element Schedule.contained is mapped to FHIR R4B element Schedule.contained as SourceIsBroaderThanTarget.
Schedule.identifier Schedule.identifier
Extension: ExtensionSchedule_Identifier
Element Schedule.identifier is mapped to FHIR R4B element Schedule.identifier as SourceIsBroaderThanTarget.
The mappings for Schedule.identifier do not cover the following types: Identifier.
The mappings for Schedule.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Schedule.active Schedule.active Element Schedule.active is mapped to FHIR R4B element Schedule.active as Equivalent.
Schedule.serviceCategory Schedule.serviceCategory Element Schedule.serviceCategory is mapped to FHIR R4B element Schedule.serviceCategory as SourceIsNarrowerThanTarget.
Schedule.serviceType Schedule.serviceType Element Schedule.serviceType is mapped to FHIR R4B element Schedule.serviceType as Equivalent.
Schedule.specialty Schedule.specialty Element Schedule.specialty is mapped to FHIR R4B element Schedule.specialty as Equivalent.
Schedule.actor Schedule.actor
Standard Extension: alternate-reference
Element Schedule.actor is mapped to FHIR R4B element Schedule.actor as SourceIsBroaderThanTarget.
The standard extension alternate-reference has been mapped as the representation of FHIR STU3 element Schedule.actor with unmapped reference targets: Device, HealthcareService, Location, Patient, Practitioner, PractitionerRole, RelatedPerson.
Schedule.planningHorizon Schedule.planningHorizon
Extension: ExtensionSchedule_PlanningHorizon
Element Schedule.planningHorizon is mapped to FHIR R4B element Schedule.planningHorizon as SourceIsBroaderThanTarget.
The mappings for Schedule.planningHorizon do not cover the following types: Period.
The mappings for Schedule.planningHorizon do not cover the following types based on type expansion: end, start.
Schedule.comment Schedule.comment Element Schedule.comment is mapped to FHIR R4B element Schedule.comment as Equivalent.