FHIR Appointment Booking in Epic, Oracle & athena

Summary

Pixel’s announcement explains how FHIR R4 scheduling uses Schedule, Slot, Appointment, and AppointmentResponse resources to book healthcare visits. It compares Epic’s $find and $book operations, Oracle Health’s Slot-and-Appointment flow, and athenahealth’s proprietary booking APIs, highlighting the need to verify patient matches and confirm saved appointments.

DEV Community

FHIR Scheduling: Booking in Epic, Oracle Health and athena

Originally published on Nirmitee.io: FHIR Scheduling API: How to Book Appointments with Slot and Appointment in Epic, Oracle Health and athenahealth (2026) Letting patients, front-desk tools or voice agents book a visit straight onto the EHR calendar is one of the most requested integrations in healthcare. FHIR has standard resources for it. The catch is that Epic, Oracle Health and athenahealth each expose a different slice of that model. The four resources, in plain terms FHIR R4 splits scheduling into four pieces: Schedule: the calendar for a practitioner, location or service. Slot: one bookable interval on that calendar, marked free or busy. Appointment: the booking that fills one or more Slots. AppointmentResponse: whether each participant accepted. Booking follows six steps Identify the patient, search availability, optionally hold the time, book, confirm what the EHR stored, and handle the response. Two rules matter most. Never book against a fuzzy or multiple patient match. And always read the created appointment back and check status, start, end, practitioner and location against what the patient agreed to. Per the source, skipping that confirmation read is the most common source of silent failures. Three EHRs, three booking paths Epic books through older STU3 operations called $find and $book. These only work after the health system builds scheduling rules in Cadence, Epic's scheduling system. Its R4 Appointment search requires a patient. Oracle Health is the closest to plain REST: search free Slots, then create an Appointment with status "booked" and exactly one slot reference. athenahealth's public FHIR R4 capability statement lists Appointment read and search only, with no Slot and no create. Booking runs through its proprietary athenaOne APIs. So a single "FHIR booking" feature is really three integrations. The original post has the full capability matrix, including cancel and reschedule for each EHR. Availability is set by each health system Availability is not a property of the API. It comes from scheduling rules each health system configures. Two sites on the same EHR version can return different answers for the same request. Visit types. New-patient, follow-up and telehealth visits have different lengths. Sending the wrong one returns nothing, or the wrong slots. Provider templates. A slot can be free on the calendar and still not bookable for your visit type. Departments and locations. The same provider may book differently at two clinics. Self-scheduling permissions. Sites decide which visit types patients or third parties may book. Many keep complex visits staff-only. Budget time with each site's scheduling team, not just your developers. Keeping appointments in sync There are three options: poll the FHIR Appointment search, take an HL7 v2 SIU feed from the EHR, or subscribe to change notifications where offered. For these three EHRs, polling is limited to date windows, and subscriptions are not in their public R4 capability statements. The SIU feed suits provider or department-wide calendars and reminders, but needs an interface build with each health system. Preventing double-booking Double-booking happens in the gap between "this slot is free" and "the booking succeeded." The source's rules: Treat every availability answer as stale. On a failed booking, search again and offer new options. Make retries safe. If a booking request times out, check the patient's appointments for that date before trying again, or the patient may get two. Never mark a slot taken in your own database before the EHR confirms it. Watch for expired holds. A voice call that takes four minutes to collect insurance details can outlast a hold. If you are building a voice or AI scheduling agent The agent uses the same booking calls, but works from spoken, error-prone input, and the EHR cannot tell whether the caller is the patient. So the agent must: Verify identity before any lookup that reveals data. Limit requests to visit type...
FHIR Appointment Booking in Epic, Oracle & athena
Powered by Readybot.io

The latest from Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …