After several months of preview as an [Alpha](/content/docs/compliance/alpha-beta/index.html) product, we are pleased to announce that [Medplum's Scheduling API](/content/docs/scheduling/index.html) has graduated to [Beta](/content/docs/compliance/alpha-beta/index.html).

Medplum's Scheduling API provides an interface for applications to atomically interact with [Schedule](/content/docs/api/fhir/resources/schedule/index.html), [Slot](/content/docs/api/fhir/resources/slot/index.html), and [Appointment](/content/docs/api/fhir/resources/appointment/index.html) resources to safely create and manage bookings without creating scheduling conflicts. Developing a feature like this required the ability to iterate as we learned, and our Alpha period provided exactly that.

There's a piece of conventional wisdom in health tech that won't die: FHIR is fine for interoperability, but too slow and bloated for real-time clinical apps.

The skepticism isn't unreasonable. FHIR resources can be verbose, real charts are messy, and clinical workflows don't forgive much. A physician who opens a chart and watches a spinner for five seconds has already been let down by the architecture.