Admin: Automated edit (via update-page on MediaWiki MCP Server)

2026-07-06T04:18:43Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 09:48, 6 July 2026
Line 74:		Line 74:

	Roles are granted through a user's facility and organization memberships, and permissions cascade down the organization tree — a role held on a parent organization applies to the facilities and resources beneath it.		Roles are granted through a user's facility and organization memberships, and permissions cascade down the organization tree — a role held on a parent organization applies to the facilities and resources beneath it.

			{{Navbox scheduling}}

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:43:39Z

OHC identity seed

New page

{{Doc header
|type=concept
|domain=scheduling
|title=Schedule & Availability
|order=1
|introduced=3.0
|concept=Concepts/Healthcare Service
|reference=References/Schedule & Availability
}}

A '''schedule''' is a named, date-bounded block of time during which a bookable resource — a practitioner, a location, or a healthcare service — accepts appointments. It is the supply side of scheduling: a schedule declares when care can be booked, so the rest of the platform knows which slots to offer patients.

== What it represents ==

In Care's FHIR-aligned model, a schedule maps to the '''Schedule''' resource, and the way it produces bookable times mirrors how FHIR derives '''Slot'''s from a schedule's planning horizon. A schedule captures:

* '''The resource''' — who or what is being booked: a practitioner, a physical location, or a named healthcare service
* '''The effective window''' — the dates between which this schedule applies, for example a doctor's roster for one quarter
* '''Availabilities''' — one or more recurring time blocks (a morning OPD, an afternoon clinic) that say which days and hours are open and how that time divides into slots
* '''Exceptions''' — specific dates and times when the resource is unavailable, such as leave or a public holiday

A schedule is not a list of appointments. It is the rule that ''generates'' bookable slots; the actual reservations live in [[Concepts/Appointment Booking|bookings]] and, where queues are used, in [[Concepts/Token|tokens]]. Slots are never stored as rows — they are computed on demand from a schedule's availabilities with exceptions subtracted, so the schedule is always the single source of truth for what is bookable. Editing a schedule changes what ''can'' be booked going forward; it does not touch appointments that already exist.

== How a schedule is built up ==

Three pieces work together. The schedule is the container; availabilities and exceptions shape the slots it offers.

* '''Schedule''' — the named, dated block attached to one resource. Holds the effective window and any billing charge that applies to bookings made against it.
* '''Availability''' — a recurring time block inside a schedule. It sets the slot type, how long each slot is, how many people each slot can hold, and which weekdays and hours it repeats on. A schedule can carry several, for example a morning and an afternoon block.
* '''Availability exception''' — a one-off date range that blocks the resource regardless of its schedules. Used for leave, holidays, and unplanned closures.

== Availability types ==

Each availability block has a '''slot type''' that decides how its time behaves:

<syntaxhighlight lang="text">appointment → open → closed</syntaxhighlight>
* '''appointment''' — time-precise booking. The block is divided into fixed-length slots (for example, 15-minute slots), each holding a set number of people. Use this when patients book a specific time.
* '''open''' — a block with no fixed slot size, suited to walk-in or queue-style flows where order matters more than an exact minute. Often paired with token generation.
* '''closed''' — a block that is explicitly not bookable, used to carve a gap out of an otherwise open period.

An appointment or open block can also issue a '''token''' for each booking, feeding the queue and token-display workflows that high-volume, walk-in clinics depend on.

== How it connects ==

A schedule sits at the center of the booking flow and links outward to several other primitives:

* '''Resource''' — every schedule attaches to exactly one practitioner ([[Concepts/User|user]]), [[Concepts/Location|location]], or [[Concepts/Healthcare Service|healthcare service]] within a [[Concepts/Facility|facility]].
* '''Bookings''' — patients reserve generated slots, creating [[Concepts/Appointment Booking|bookings]] against the schedule.
* '''Tokens''' — in queue-based clinics, a booking can also issue a [[Concepts/Token|token]] for the waiting line.
* '''Billing''' — a schedule can carry a charge that applies to its bookings, with an optional reduced charge for follow-up visits within a configured window, drawn from a [[Concepts/Charge Item Definition|charge item definition]].

== Permissions ==

Access to schedules and the bookings made against them is governed by the facility-level permissions below.

{| class="wikitable"
|-
! Permission
! Description
! System Roles
|-
| <code>can_write_schedule</code>
| Create, update, and delete schedules and their availabilities for a resource
| Admin, Staff, Facility Admin, Doctor, Nurse
|-
| <code>can_list_schedule</code>
| View the schedules and availabilities defined for a resource
| Admin, Staff, Facility Admin, Doctor, Nurse, Administrator
|-
| <code>can_set_charge_item_definition</code>
| Attach a billing charge item definition (and revisit settings) to a schedule
| Facility Admin, Admin
|}

Roles are granted through a user's facility and organization memberships, and permissions cascade down the organization tree — a role held on a parent organization applies to the facilities and resources beneath it.

{{Related}}

Concepts/Schedule & Availability - Revision history

Admin: Automated edit (via update-page on MediaWiki MCP Server)

Admin: OHC identity seed