
The Technical Flow: From First Click to Confirmed Appointment
Patient Initiates Contact
A patient visits your website, sends a text, calls your phone line, or opens your Telegram channel. The Motiv widget is added to the practice's site with an embed snippet.
Conversation, Not a Form
Motiv holds a natural conversation instead of presenting a form. It collects the patient's details, the reason for the visit (matched to your appointment types), provider preference, insurance information (including reading a photo of the insurance card), and scheduling preferences. Each answer is kept as structured data behind the conversation.
Insurance Check
Where the practice has it set up, the insurance details are checked before slots are offered, so a coverage problem surfaces before the patient has booked.
Slot Search Through the EHR's API
For an EHR that supports it, Motiv searches open slots through the EHR's FHIR R4 API by provider or specialty, appointment type, preferred date range, and practice location. Availability comes from the EHR itself.
Writing the Appointment to the EHR
When the patient confirms a slot, Motiv sends the appointment to the EHR, so the EHR stays the source of truth for the schedule.
Confirmation
The patient receives a confirmation with the appointment details, through the channel they are already using. The front desk sees the appointment in the practice's own schedule.
Why Direct Integration Matters
Some integrations work through a middleware layer. Patient data goes into the AI, gets reformatted, passes through an intermediary, and then reaches the EHR.
Problems with middleware-based booking:
- • Stale availability — A copy of the schedule can show a slot that is already taken.
- • Dropped information — Details can be lost between systems.
- • More failure points — Every extra layer is another place the process can break.
- • More exposure — PHI passes through more systems.
Motiv is built to read open times from the EHR through its API and write the booking back to it, so the EHR stays the source of truth for the schedule. Motiv also keeps its own record of the booking for a limited time, to run reminders and confirmations.
What Motiv Keeps
Clinical details from the booking conversation, such as symptoms and notes, are meant to go to the practice's EHR rather than be stored as fields in Motiv's own database. Motiv does keep basic contact details (name, date of birth, phone and email) for a limited time to run the service. A booking in progress is kept for 24 hours with the clinical answers left out. Ask any vendor, Motiv included, for the full list in writing. The booking itself lives in the EHR. Read the questions to ask any vendor about patient data.
Where This Stands Today
The booking flow has been built and tested against Epic's developer sandbox. The same approach is built for the systems below, and each is at its own stage of testing. A connection for a specific practice is set up with that practice's own credentials and the EHR vendor's approval, and Google Calendar is available for practices without a mainstream EHR. Ask which stage your EHR is at before you plan around it.
athenahealth
FHIR R4
Cerner (Oracle Health)
FHIR R4
eClinicalWorks
FHIR DSTU2
ModMed
Proprietary API
Elation
REST API
eMedPractice
REST API
Veradigm
FHIR R4
NextGen
FHIR R4
DrChrono
REST API
Greenway
REST API
An Illustration
An invented example of the flow, not a real patient or practice.
A patient visits a practice's website at 9:47 PM on a Tuesday, after the office has closed.
They open the chat widget and write: “I need a follow-up for my knee.”
Motiv asks for the details it needs, looks up open times through the EHR, and offers a Thursday morning slot. The patient accepts and gets a confirmation. The appointment is written to the practice's schedule.
In the morning, the front desk sees the booking in its own schedule instead of a voicemail to return.
© 2026 Motiv Technologies, Inc. The text and images in this article belong to Motiv Technologies. To reuse them, please ask first.