Engineering for the front desk: How PolyAI books appointments in ModMed
Inside PolyAI's ModMed integration and how appointments get booked end-to-end.
TL;DR
- How real-time Patient SEARCH, Appointment CREATE, and multi-tenant endpoint routing actually work inside a ModMed environment.
- Built for the enterprise, tested in sandbox, verified before day one.
- For the operational picture, what this means for staffing, patient experience, and revenue, start with PolyAI for ModMed: Voice AI built for specialty practice workflows .
A ringing phone and an empty time slot are a constant challenge for medical clinics. To be useful, voice AI must do more than just understand a patient. It must navigate a clinical database and take action while the patient is on the line. We built our ModMed integration to solve the technical hurdles of enterprise scheduling. We chose to move away from batch processing and instead built a system that interacts with the MMI Proprietary API in real time. This ensures that every booking is accurate and every patient record remains secure.
A common way to talk to health records
Building for the enterprise requires a shared set of rules. We use the FHIR R4 standard to communicate with ModMed. This protocol provides a common way for our AI to share data using rules both systems understand.
We use JSON to exchange information. This makes our requests light and fast. By following these industry rules, PolyAI can verify patient identities and check schedules without the errors that come with custom data formats. The information arrives at the clinic exactly how the ModMed system expects to see it.
The logic of real-time scheduling
One of our most asked about use cases is appointment creation. This is a multi-step process that happens while the patient is still talking. Our AI performs a live search to find the right patient and the right time.
The workflow begins with a Patient SEARCH request. The AI uses the patient name and date of birth to find a matching Patient ID. Once verified, the AI performs a Slot SEARCH to see live availability for specific doctors and locations.
When the patient chooses a time, the AI sends an Appointment CREATE request. This links the patient to the open slot instantly. The visit appears on the clinic calendar immediately. This real-time action prevents double bookings and saves the front desk from manual data entry.
How we handle a thousand unique front doors
ModMed uses a unique architecture where every practice has its own firm-specific URL. This means there is no single entrance for all data. Instead, there are thousands of individual endpoints.
We built our infrastructure to handle this multi-tenant setup. When a call starts, our system identifies which clinic the patient is calling. We then route every API request to that specific practice address. This keeps patient records separated. It ensures that the AI is always talking to the right database for the right clinic.
Hardening the handshake
Security is the foundation of our work in the medical field. We use OAuth 2.0 to verify every connection we make to a ModMed tenant. This is the global standard for secure authorization.
Our system manages unique security tokens for every practice. We use the password grant flow to gain access to the clinical and scheduling data we need. We log every request to create a clear audit trail for HIPAA compliance. This architecture ensures that we only access the data we are authorized to use. It keeps patient privacy protected at every step of the call.
Getting it right before day one
Reliability is built through careful testing. We develop and verify every feature in a ModMed sandbox before it ever handles a real patient call. This test area allows us to run our scheduling logic against fake data to ensure the RESTful calls are perfect.
Before a new integration goes live, we perform a full technical review with the customer team. We demonstrate that our AI can handle the necessary tasks without errors. We only ask for the specific FHIR resources required for the job, such as Schedule and Slot. This process ensures that our voice AI is a stable and trusted part of the clinic workflow from the very first day.
Built to be trusted
Patients don't think about API architecture when they call to book an appointment. They just want it to be easy. The engineering underneath is what makes that possible, and it's why specialty practices can trust PolyAI with scheduling from day one.
If you want to simplify patient access and meet them on the channel of their choice, speak to our team today.
