Integrations · ModMed
AI receptionist for ModMed practices
For specialty practices on ModMed. The receptionist answers every call, screens with your specialty's forms, and books in ModMed once API access is arranged and tested for your practice.
What connects to ModMed.
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 ModMed.
ModMed offers API access to partners. Access for the receptionist is arranged with ModMed and your practice, and we confirm the scheduling operations available before anything goes live.
- API access for the receptionist, arranged with ModMed for your practice
- Your appointment types, durations and the providers who take each
- How the specialty pack's visit types map to your ModMed templates
- A complete test: book, move and cancel a test visit
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.
ModMed is a trademark of its owner. Callinzo is not affiliated with or endorsed by ModMed.
Asked about ModMed.
Does Callinzo book directly into ModMed?
Once API access is arranged and the test visit passes, yes. Until then, visits are booked on the dashboard schedule and your staff enter them in ModMed.
Does it know my specialty's visit types?
The specialty pack brings its own visit types and screening forms, and we map them to your ModMed appointment types during onboarding.
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 ModMed.
We will tell you honestly what we can commit to, and what works on day one without a connection.