Current Build
Patient Administration Work GroupMaturity Level: 3 Trial UseCompartments: 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.

Control1..1
Alternate NamesAvailability
Schedule.identifier
Definition

External Ids for this item.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Summarytrue
Schedule.active
Definition

Whether this schedule record is in active use, or should not be used (such as was entered in error).

Control0..1
Typeboolean
Is Modifiertrue
Default Valuetrue
Summarytrue
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.

Control0..1
Terminology BindingServiceCategory (Example)
TypeCodeableConcept
Summarytrue
Schedule.serviceType
Definition

The specific service that is to be performed during this appointment.

Control0..*
Terminology BindingServiceType (Example)
TypeCodeableConcept
Summarytrue
Schedule.specialty
Definition

The specialty of a practitioner that would be required to perform the service requested in this appointment.

Control0..*
Terminology BindingPractice Setting Code Value Set (Preferred)
TypeCodeableConcept
Summarytrue
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.

Control1..*
TypeReference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location)
Summarytrue
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.

Control0..1
TypePeriod
Summarytrue
Schedule.comment
Definition

Comments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated.

Control0..1
Typestring