Scheduling matches clinical demand to constrained capacity
A referral is not truly booked until the receiving organization can align the patient, service, staff, location, duration, and any prerequisites into one executable commitment.
That is why scheduling systems keep separate views of demand, resource calendars, and booking rules. An urgent MRI with contrast may require a scanner, a nurse, recent labs, and enough time for prep and post-checks. A plain x-ray may need far fewer dependencies.
Capacity-aware booking flow
Loading diagram...
Appointment - FHIR v4.0.1
Official FHIR scheduling resource for representing planned healthcare bookings among people, places, and equipment.
Read the Appointment resourceSchedule - FHIR v4.0.1
Official scheduling resource that represents the calendars and allocatable capacity behind appointment discovery and booking.
Read the Schedule resourceCross-enterprise scheduling separates search, hold, and booking
Shared scheduling networks should not treat every available slot as already committed capacity. Search shows candidate availability, a temporary hold protects one option while details are confirmed, and only the final booking creates an appointment that downstream systems can trust.
That separation is explicit in the IHE Scheduling profile: consumers first find potential appointments, may place a temporary hold, and then either book or release the slot. In FHIR terms, Schedule and Slot describe availability, while Appointment is the actual reserved event.
Search-hold-book lifecycle
Loading diagram...
A held slot is not a booked appointment
If shared systems collapse hold and book into one state, they create race conditions, false confirmations, and weak auditability when prerequisites fail.
IHE Scheduling profile
IHE profile defining the cross-enterprise appointment search, hold, book, and release workflow.
Read the IHE Scheduling profileSlot - FHIR v4.0.1
Official FHIR resource for describing individual units of availability that can later be held or booked.
Read the Slot resourcePreparation work should be modeled as trackable tasks
Readiness work often happens between booking and arrival: reminders, consent, lab verification, fasting instructions, implant checks, or transport coordination. If those steps stay in free text, the service team learns too late that the patient is not ready.
Booking plus preparation task pattern
A modern scheduling API can separate the appointment from the related readiness work that must happen before the service date.
Request
POSTANNOTATIONS
Response
Task - FHIR v4.0.1
FHIR workflow resource for tracking the state of operational work such as reminders, verification, or readiness checks.
Read the Task resourceACR Manual on Contrast Media
Reference for the patient-selection, readiness, and risk-mitigation steps that often drive preparation tasks.
Review preparation considerationsKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.