12.12 12.15 Resource Schedule - Content

12.12.1 12.15.1 Scope and Usage

Schedule resources provide a container for time-slots that can be booked using an appointment. It provides the window of time (period) that slots are defined for and what type of appointments can be booked.
The schedule does not provide any information about actual appointments. This separation also greatly assists where access to the appointments would not be permitted for security or privacy reasons, while still being able to determine if an appointment might be available.

Note: A schedule is not used for the delivery of medication, the Timing data type should be used for that purpose.

12.12.1.1 12.15.1.1 Context

A schedule controls the dates and times available for the performance of a service and/or the use of a resource. One schedule applies to one service or resource, since each service or resource can be reserved independently of the others.
If two or more services, people, locations, or things cannot be reserved independently of one another, they are considered to be one activity or resource.

A schedule consists of slots of time during which the controlled service or resource is potentially available for provision or use. Slots are categorized as open, booked, or blocked. An open slot on a schedule indicates that the service or resource is available for provision or use during that period of time. A booked slot indicates that the service or resource is not available during the time period, because an appointment has been scheduled. A blocked slot indicates that a service or resource is unavailable for reasons other than a scheduled appointment.

The real-world, non-automated analogue of the schedule described above is a standard appointment book. These books are generally organized with rows of time slots, during which a service or resource is available.

A slot is one unit on a schedule. A slot represents the smallest unit of time or quantity that a service or resource may be booked. Depending on the nature of the service or resource, there may be more than one defined slot at a given instant of time. For example, if a service is an open group therapy session with twelve available seats, then there are twelve slots for the given block of time.

12.12.1.2 12.15.1.2 Actor - What the schedule applies to

The schedule belongs to a single instance of a service or resource. This is normally a HealthcareService, Practitioner, Location or Device. In the case where a single resource can provide different services, potentially at different location, then the schedulable resource is considered the composite of the actors.
For example, if a practitioner can provide services at multiple locations, they might have one schedule per location, where each schedule includes both the practitioner and location actors. When booking an appointment with multiple schedulable resources, multiple schedules may need to be checked depending on the configuration of the system.

If an appointment has two practitioners, a specific medical device and a room then there could be a schedule for each of these resources that may need to be consulted to ensure that no collisions occur.
If the schedule needed to be consulted, then there would be one created covering the planning horizon for the time of the appointment.

12.12.1.3 12.15.1.3 Checking availability - Searching

When checking availability for an appointment, the creator of the appointment should determine which schedules are applicable, then check for available slots within each schedule.

Determining which schedules should be consulted often will involve searching via the properties of the referenced actors, such as the ServiceCategory on the HealthcareService, or the Address on a Location.

The type parameter can be used to filter the type of services that can be booked within the associated slots.

If all slots are busy, the caller may attempt to book an appointment into a already booked an already-booked slot, but the server business rules will dictate whether overbooking is allowed, or whether the appointment may be given a higher precedence and allocated the overbooked slot.

12.15.2 Boundaries and Relationships

This resource is referenced by slot Slot : Provides the granular, bookable units within the Schedule.

Schedule : Defines the broader availability and context for an individual or service.

Appointment : Is the outcome of a scheduling process. That scheduling process may involve consulting Slot and Schedule resources, or it may be the result of other processes.

• Structure
• UML
• XML
• JSON
• Turtle
• R2 R4 Diff
• All

Structure

0..1 A broad categorisation of the service that is to be performed during this appointment The specific The specialty The resource this Schedule resource is providing The period of time that the slots that are attached to this Schedule resource cover (even if none exist). These cover the amount

Name	Flags	Card.	Type	Description & Constraints      Filter: Bindings Constraints Obligations
Schedule	TU		DomainResource	A container for slots of time that may be available for booking appointments Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
identifier	Σ	0..*	Identifier	External Ids for this item
active	?! Σ	0..1	boolean	Whether this schedule is in active use
serviceCategory	Σ	0..*	CodeableConcept	High-level category Binding: ServiceCategory Service Category ( Example )
serviceType	Σ	0..*	CodeableConcept CodeableReference ( HealthcareService )	Specific service that is to be performed during this appointment Binding: ServiceType Service Type ( Example )
specialty	Σ	0..*	CodeableConcept	Type of a practitioner that would be required to perform the service requested in this appointment specialty needed Binding: Practice Setting Code Value Set ( Preferred Example )
actor name	Σ	0..1	string 1..*	Human-readable label
actor	Σ	1..*	Reference ( Patient | Practitioner | PractitionerRole | CareTeam | RelatedPerson | Device | HealthcareService | Location )	Resource(s) that availability information for. These are expected to usually be one of HealthcareService, Location, Practitioner, PractitionerRole, Device, Patient or RelatedPerson is being provided for
planningHorizon	Σ	0..1	Period	Period 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 covered by schedule
comment		0..1	string markdown	Comments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated
Documentation for this format

See the Extensions for this resource

<

<Schedule xmlns="http://hl7.org/fhir"> 

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this item --></identifier>
 <
 <</serviceCategory>
 <</serviceType>
 <</specialty>
 <|
   </actor>
 <</planningHorizon>
 <

 <active value="[boolean]"/><!-- 0..1 Whether this schedule is in active use -->
 <serviceCategory><!-- 0..* CodeableConcept High-level category --></serviceCategory>
 <serviceType><!-- 0..* CodeableReference(HealthcareService) Specific service --></serviceType>
 <specialty><!-- 0..* CodeableConcept Type of specialty needed --></specialty>
 <name value="[string]"/><!-- 0..1 Human-readable label -->
 <actor><!-- 1..* Reference(CareTeam|Device|HealthcareService|Location|Patient|
   Practitioner|PractitionerRole|RelatedPerson) Resource(s) that availability information is being provided for --></actor>

 <planningHorizon><!-- 0..1 Period Period of time covered by schedule --></planningHorizon>
 <comment value="[markdown]"/><!-- 0..1 Comments on availability -->

</Schedule>

{
  "resourceType" : "",

  "resourceType" : "Schedule",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "
  "
  "
  "
  "
  "|
   
  "
  "

  "identifier" : [{ Identifier }], // External Ids for this item
  "active" : <boolean>, // Whether this schedule is in active use
  "serviceCategory" : [{ CodeableConcept }], // High-level category
  "serviceType" : [{ CodeableReference(HealthcareService) }], // Specific service
  "specialty" : [{ CodeableConcept }], // Type of specialty needed
  "name" : "<string>", // Human-readable label
  "actor" : [{ Reference(CareTeam|Device|HealthcareService|Location|Patient|
   Practitioner|PractitionerRole|RelatedPerson) }], // R!  Resource(s) that availability information is being provided for

  "planningHorizon" : { Period }, // Period of time covered by schedule
  "comment" : "<markdown>" // Comments on availability

}

@prefix fhir: <http://hl7.org/fhir/> .


[ a fhir:Schedule;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from 
  # from 
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:|
  
  fhir:
  fhir:

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* External Ids for this item
  fhir:active [ boolean ] ; # 0..1 Whether this schedule is in active use
  fhir:serviceCategory  ( [ CodeableConcept ] ... ) ; # 0..* High-level category
  fhir:serviceType  ( [ CodeableReference(HealthcareService) ] ... ) ; # 0..* Specific service
  fhir:specialty  ( [ CodeableConcept ] ... ) ; # 0..* Type of specialty needed
  fhir:name [ string ] ; # 0..1 Human-readable label
  fhir:actor  ( [ Reference(CareTeam|Device|HealthcareService|Location|Patient|Practitioner|PractitionerRole|
  RelatedPerson) ] ... ) ; # 1..* Resource(s) that availability information is being provided for

  fhir:planningHorizon [ Period ] ; # 0..1 Period of time covered by schedule
  fhir:comment [ markdown ] ; # 0..1 Comments on availability

]

Structure

0..1 A broad categorisation of the service that is to be performed during this appointment The specific The specialty The resource this Schedule resource is providing The period of time that the slots that are attached to this Schedule resource cover (even if none exist). These cover the amount

Name	Flags	Card.	Type	Description & Constraints      Filter: Bindings Constraints Obligations
Schedule	TU		DomainResource	A container for slots of time that may be available for booking appointments Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
identifier	Σ	0..*	Identifier	External Ids for this item
active	?! Σ	0..1	boolean	Whether this schedule is in active use
serviceCategory	Σ	0..*	CodeableConcept	High-level category Binding: ServiceCategory Service Category ( Example )
serviceType	Σ	0..*	CodeableConcept CodeableReference ( HealthcareService )	Specific service that is to be performed during this appointment Binding: ServiceType Service Type ( Example )
specialty	Σ	0..*	CodeableConcept	Type of a practitioner that would be required to perform the service requested in this appointment specialty needed Binding: Practice Setting Code Value Set ( Preferred Example )
actor name	Σ	0..1	string	Human-readable label 1..*
actor	Σ	1..*	Reference ( Patient | Practitioner | PractitionerRole | CareTeam | RelatedPerson | Device | HealthcareService | Location )	Resource(s) that availability information for. These are expected to usually be one of HealthcareService, Location, Practitioner, PractitionerRole, Device, Patient or RelatedPerson is being provided for
planningHorizon	Σ	0..1	Period	Period 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 covered by schedule
comment		0..1	string markdown	Comments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated
Documentation for this format

See the Extensions for this resource

UML Diagram ( Legend )

XML Template

<

<Schedule xmlns="http://hl7.org/fhir"> 

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this item --></identifier>
 <
 <</serviceCategory>
 <</serviceType>
 <</specialty>
 <|
   </actor>
 <</planningHorizon>
 <

 <active value="[boolean]"/><!-- 0..1 Whether this schedule is in active use -->
 <serviceCategory><!-- 0..* CodeableConcept High-level category --></serviceCategory>
 <serviceType><!-- 0..* CodeableReference(HealthcareService) Specific service --></serviceType>
 <specialty><!-- 0..* CodeableConcept Type of specialty needed --></specialty>
 <name value="[string]"/><!-- 0..1 Human-readable label -->
 <actor><!-- 1..* Reference(CareTeam|Device|HealthcareService|Location|Patient|
   Practitioner|PractitionerRole|RelatedPerson) Resource(s) that availability information is being provided for --></actor>

 <planningHorizon><!-- 0..1 Period Period of time covered by schedule --></planningHorizon>
 <comment value="[markdown]"/><!-- 0..1 Comments on availability -->

</Schedule>

JSON Template

{
  "resourceType" : "",

  "resourceType" : "Schedule",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "
  "
  "
  "
  "
  "|
   
  "
  "

  "identifier" : [{ Identifier }], // External Ids for this item
  "active" : <boolean>, // Whether this schedule is in active use
  "serviceCategory" : [{ CodeableConcept }], // High-level category
  "serviceType" : [{ CodeableReference(HealthcareService) }], // Specific service
  "specialty" : [{ CodeableConcept }], // Type of specialty needed
  "name" : "<string>", // Human-readable label
  "actor" : [{ Reference(CareTeam|Device|HealthcareService|Location|Patient|
   Practitioner|PractitionerRole|RelatedPerson) }], // R!  Resource(s) that availability information is being provided for

  "planningHorizon" : { Period }, // Period of time covered by schedule
  "comment" : "<markdown>" // Comments on availability

}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .


[ a fhir:Schedule;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from 
  # from 
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:|
  
  fhir:
  fhir:

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* External Ids for this item
  fhir:active [ boolean ] ; # 0..1 Whether this schedule is in active use
  fhir:serviceCategory  ( [ CodeableConcept ] ... ) ; # 0..* High-level category
  fhir:serviceType  ( [ CodeableReference(HealthcareService) ] ... ) ; # 0..* Specific service
  fhir:specialty  ( [ CodeableConcept ] ... ) ; # 0..* Type of specialty needed
  fhir:name [ string ] ; # 0..1 Human-readable label
  fhir:actor  ( [ Reference(CareTeam|Device|HealthcareService|Location|Patient|Practitioner|PractitionerRole|
  RelatedPerson) ] ... ) ; # 1..* Resource(s) that availability information is being provided for

  fhir:planningHorizon [ Period ] ; # 0..1 Period of time covered by schedule
  fhir:comment [ markdown ] ; # 0..1 Comments on availability

]

Changes since DSTU2 from both R4 and R4B

Schedule
Schedule.active Schedule.serviceType	Added Element Type changed from CodeableConcept to CodeableReference
Schedule.serviceCategory Schedule.name	Added Element
Schedule.serviceType Renamed from type to serviceType Schedule.specialty Schedule.actor	Type Reference: Added Element Target Type CareTeam
Schedule.actor Schedule.comment	Max Cardinality Type changed from 1 string to * Add Reference(PractitionerRole) markdown

See the Full Difference for further information

This analysis is available for R4 as XML or JSON . See R2 <--> R3 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and all r3 resources are valid.). for R4B as XML or JSON .