The Health Service resource is used to describe a single healthcare service or category of services that are provided by an organization at a location. The location of the services could be virtual, as with telemedicine services. This profile provides a scheduling-optimized view of healthcare service offerings, enabling discovery and booking of appointments when no specific practitioner is required or specified.

Each line of the Location File is a minified JSON object that conveys a physical location where appointments are available.

This profile sets minimum expections for a Practitioner resource

Each line of the PractitionerRole File is a minified JSON object that represents a set of roles/locations/specialties/services that a practitioner may perform at an organization for a period of time. The PractitionerRole resource represents the specific roles that practitioners perform at organizations where appointments are available. According to the FHIR R4 PractitionerRole definition, practitioner roles define the specific context in which practitioners provide services, including:

• Primary care physician roles at specific locations
• Specialist roles (cardiologist, dermatologist, etc.) with specific availability
• Nursing roles for various services and locations
• Pharmacy roles for medication management and immunizations
• Therapy roles (physical therapy, occupational therapy, etc.)
• Diagnostic service roles (radiology, laboratory, etc.)
• Administrative roles that support patient care scheduling

Each line of the Schedule File is a minified JSON object that conveys information about a Schedule to which slots are attached. The Schedule represents a particular healthcare service (e.g., primary care appointments, specialist consultations, or procedures) offered at a specific location or by a specific practitioner role.

Each line of the Slot File is a minified JSON object that conveys information about an appointment slot. Publishers are encouraged to represent slots with fine-grained timing details (e.g. representing appointments at specific times of the day), but MAY represent slots with coarse grained timing (e.g., "between 9 a.m. and 5 p.m." or "between noon and five p.m.").

A deep link into the Provider Booking Portal where the user can begin booking this slot.

A phone number the user can call to book this slot.

The specialty associated with this schedule.

A value set that combines the preferred and required codes from slot.appointmentType and NDH new patient extension, respectively

Example Location instance conforming to the SMARTLocation profile.

Example Location instance conforming to the SMARTLocation profile.

Example PractitionerRole instance conforming to the SmartSchedulingPractitionerRole.

This example demonstrates a Schedule with multiple actors, indicating that general practice appointments are available for practitioner role "doc-smith-role" at location "123". This pattern is commonly used when a specific practitioner role provides services at a specific location.

Example slot that has the booking extensions

Example HealthcareService instance conforming to the SmartSchedulingHealthcareService profile.

Example of the Organization resource

A slot that is accepting new and existing patients

A slot that is accepting only existing patients