Integrations · Epic
AI receptionist for Epic practices
For practices and groups on Epic. The receptionist answers every call and books through Epic's FHIR R4 interfaces once your organization's Epic team enables the scheduling operations you need.
What connects to Epic.
Through the receptionist's FHIR R4 adapter, once access is approved and tested for your practice.
- Reads open slots for each provider and visit type, so the receptionist only offers times your system has free
- Books the visit in your system with an identifier on every request, so a repeated request finds the first booking instead of making a second
- Cancels and reschedules visits the caller asks to change
- Finds the caller's chart by phone number only when exactly one chart matches; anything else is left to your staff
- Reads a patient's upcoming visits, for confirmations and “when is my appointment?” calls
How the connection behaves.
Built so a phone call can never leave your schedule in a state nobody knows about.
Your system is the authority
The receptionist asks your system for openings and to book, and records only what your system confirmed.
A lost reply is never a booking
If your system times out, the outcome is marked unknown, not booked and not failed, and left for your staff to check.
Safe to repeat
Every booking carries its operation's identifier. Trying again looks for the first attempt before it asks again, so there are no doubles.
A sick system is left alone
If your system keeps failing, a breaker stops calls to it for a while instead of retrying into it, and what could not be confirmed waits for your staff.
Before the first live booking in Epic.
Epic publishes its FHIR R4 interfaces on open.epic. Which scheduling operations are available to a vendor is decided by each organization's Epic team, so we confirm them with yours before anything goes live.
- Your Epic team's approval and the client registration for the receptionist
- Which scheduling operations are enabled: reading open slots, booking, cancelling
- The departments, providers and visit types the receptionist may book
- A complete test in your non-production Epic environment
Until the connection is validated, the receptionist books on the schedule kept in the Callinzo dashboard, which your staff can run from day one, and after-hours coverage needs no connection at all: every call answered, urgent calls screened and paged, the rest waiting as tasks.
Other systems.
Epic is a trademark of its owner. Callinzo is not affiliated with or endorsed by Epic.
Asked about Epic.
Does Callinzo book directly into Epic?
Once your organization's Epic team enables the scheduling interfaces and the workflow passes testing in your non-production environment, yes. Until then, visits are booked on the dashboard schedule and your staff enter them.
Who has to approve the connection?
Your organization's Epic team. They decide which interfaces a vendor may use. We give them the operations we need and test against their environment first.
What works before the connection is live?
Until the connection is validated, the receptionist books on the schedule kept in the Callinzo dashboard, which your staff can run from day one, and after-hours coverage needs no connection at all: every call answered, urgent calls screened and paged, the rest waiting as tasks.
What if the EHR does not answer during a booking?
The booking is marked unknown, never booked and never failed, and is left for your staff to check. Retrying looks for the first attempt before asking again, so nobody is double-booked.
Tell us how you run Epic.
We will tell you honestly what we can commit to, and what works on day one without a connection.