Call capture
The AI collects caller identity, reason for visit, preferred timing, contact details, and any practice-approved intake fields.
Live EHR integration
MedReceptionist books patient calls into ClaimPower
For clinics using ClaimPower scheduling and claims workflows, MedReceptionist answers the call, identifies the patient and visit reason, checks the configured scheduling workflow, creates an appointment in ClaimPower when write-back is enabled, and hands off safely when it cannot confirm the booking.
How booking works
From phone call to confirmed ClaimPower appointment.
EHR mapping
The configured provider, facility, reason code, service duration, and patient lookup rules determine whether the appointment can be created.
Fail-safe handoff
If ClaimPower cannot confirm the write, the receptionist captures the call and routes it to staff instead of silently changing the schedule.
Supported vs not claimed
Honest ClaimPower capability boundaries.
What this integration does
- Books appointments through ClaimPower PatientScheduler when patient, provider, facility, subtype, and slot details are resolved.
- Checks available slots through the ClaimPower scheduler endpoint when configured.
- Uses staff handoff for cancellation or reschedule because the adapter does not expose confirmed cancel/reschedule APIs.
What this page does not claim
- Does not claim ClaimPower cancel or reschedule write-back from the AI receptionist.
- Does not treat claim status questions as scheduling decisions; those should route to staff unless a separate verified workflow exists.
Operational setup
What Justin or onboarding still confirms per clinic.
| Setup item | Why it matters |
|---|---|
| Provider/resource mapping | Prevents calls from being booked into the wrong person, room, or schedule. |
| Appointment type and duration mapping | Keeps new patient, consult, follow-up, and emergency slots distinct. |
| Escalation rules | Routes urgent, clinical, billing, or unsupported calls to the right staff path. |
| Write-access validation | Confirms the adapter can create appointments in the specific practice account before going live. |
FAQ
ClaimPower integration FAQ.
Can MedReceptionist book directly into ClaimPower?
Yes, when the ClaimPower account, credentials, mapped providers, appointment types, facilities, and write permissions are configured. If the integration cannot confirm the write, the call is captured for staff instead.
What ClaimPower capabilities are public claims on this page?
This page is limited to the registered MedSiteAI adapter boundary: search or create patients, search by phone, create appointments, check available slots, and read resources/reason codes from configured ClaimPower fields. It does not claim capabilities outside that implementation boundary.
Does the AI receptionist give clinical advice?
No. It follows the practice-approved phone script, books or routes the call, and escalates clinical questions to staff.
What happens during onboarding?
The practice maps providers, locations, services, appointment durations, call scripts, escalation rules, and any EHR-specific access required for safe booking.
Related integrations