Schedule - FHIR v3.0.2

FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

12.12.6 Resource Schedule - Detailed Descriptions

Patient Administration

Work Group

Maturity Level: 3

Trial Use

Compartments: Device, Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the Schedule resource.

Schedule
Definition	A container for slots of time that may be available for booking appointments.
Control	1..1
Alternate Names	Availability
Schedule.identifier
Definition	External Ids for this item.
Note	This is a business identifer, not a resource identifier (see discussion)
Control	0..*
Type	Identifier
Summary	true
Schedule.active
Definition	Whether this schedule record is in active use, or should not be used (such as was entered in error).
Control	0..1
Type	boolean
Is Modifier	true
Default Value	true
Summary	true
Comments	This element is labeled as a modifier because it may be used to mark that the resource was created in error.
Schedule.serviceCategory
Definition	A broad categorisation of the service that is to be performed during this appointment.
Control	0..1
Terminology Binding	ServiceCategory (Example)
Type	CodeableConcept
Summary	true
Schedule.serviceType
Definition	The specific service that is to be performed during this appointment.
Control	0..*
Terminology Binding	ServiceType (Example)
Type	CodeableConcept
Summary	true
Schedule.specialty
Definition	The specialty of a practitioner that would be required to perform the service requested in this appointment.
Control	0..*
Terminology Binding	Practice Setting Code Value Set (Preferred)
Type	CodeableConcept
Summary	true
Schedule.actor
Definition	The resource this Schedule resource is providing availability information for. These are expected to usually be one of HealthcareService, Location, Practitioner, PractitionerRole, Device, Patient or RelatedPerson.
Control	1..*
Type	Reference(Patient \| Practitioner \| PractitionerRole \| RelatedPerson \| Device \| HealthcareService \| Location)
Summary	true
Comments	The capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a pracitioner and a room(location) are always required by a system.
Schedule.planningHorizon
Definition	The period of time that the slots that are attached to this Schedule resource cover (even if none exist). These cover the amount of time that an organization's planning horizon; the interval for which they are currently accepting appointments. This does not define a "template" for planning outside these dates.
Control	0..1
Type	Period
Summary	true
Schedule.comment
Definition	Comments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated.
Control	0..1
Type	string