The Technical Flow: From First Click to Confirmed Appointment
Patient Initiates Contact
A patient visits your website, sends an SMS, calls your AI phone line, or opens your Telegram channel. The Motiv widget loads instantly — one line of embed code, no heavy integration required.
Intelligent Information Collection
The AI begins a natural conversation — not a form. It collects patient demographics, visit reason (mapped to your appointment types), provider preference, insurance information (including real-time card OCR), and scheduling preferences. Every piece maps to structured data behind the conversation.
Insurance Eligibility Verification
Before searching for slots, the AI runs a real-time insurance eligibility check. If coverage is active and in-network, the flow continues. If there is a coverage issue, the patient is informed immediately — not after they have already booked and driven to the office.
Real-Time FHIR R4 Slot Search
Motiv connects to Epic's FHIR R4 API and executes a real-time slot search based on provider/specialty, appointment type, preferred date range, and practice location. These are live, real-time openings — not cached on a 15-minute interval.
Direct Appointment Creation
When the patient confirms a slot, Motiv sends a FHIR Appointment resource directly to Epic. The slot is consumed immediately. No other patient can book it. No double booking is possible because the system writes directly to the source of truth.
Confirmation
The patient receives an immediate confirmation with appointment details, provider name, office address, and pre-visit instructions — through whatever channel they are already using. The front desk sees the appointment in their Epic schedule, identical to any appointment created manually.
Why Direct Integration Matters
There are platforms that claim EHR integration but actually sit on top of a middleware layer. Patient data goes into the AI, gets reformatted, passes through an intermediary, and eventually lands in the EHR. Sometimes.
Problems with middleware-based booking:
- • Latency — Slot availability is stale. Double bookings happen.
- • Data loss — Information gets dropped between systems.
- • Failure points — Every additional layer is another place the process can break.
- • Compliance risk — PHI passes through additional systems, expanding the attack surface.
Motiv eliminates all of these. The AI reads from Epic. The AI writes to Epic. No middle layer.
Zero PHI Retention
Every data point collected during the booking conversation is transmitted to Epic and then purged. Motiv retains zero protected health information after the transaction completes. The booking data lives where it belongs — in the EHR — and nowhere else. Read our full HIPAA compliance breakdown.
Beyond Epic: 11 EHR Integrations
Epic is the largest EHR in the United States, but it is not the only one. Motiv runs the same direct-booking architecture across 10 additional systems:
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
What It Looks Like in Practice
A patient visits your website at 9:47 PM on a Tuesday. Your office closed four hours ago.
They click the chat widget: “I need a follow-up with Dr. Chen for my knee.”
The AI confirms their identity, checks insurance, pulls Dr. Chen's availability from Epic, and books a Thursday morning appointment. The patient gets a confirmation. Dr. Chen's schedule updates.
Your front desk arrives Wednesday morning to a fully booked Thursday with zero voicemails to return.