AI Voice Agent + DrChrono / Athenahealth: Patient Scheduling Without Front Desk

The two cloud EHRs with the friendliest APIs for AI integration in 2026 are DrChrono and Athenahealth. Both expose patient demographics, schedule, and appointment write endpoints. CallSphere's healthcare deployment ships pre-built tools for both.

What the integration unlocks

flowchart TD
  Client[MCP client · Claude Desktop] --> MCP[MCP server]
  MCP --> Tool1[Tool: Calendar]
  MCP --> Tool2[Tool: CRM]
  MCP --> Tool3[Tool: KB search]
  Tool1 --> SaaS1[(Calendly)]
  Tool2 --> SaaS2[(Salesforce)]
  Tool3 --> SaaS3[(Notion)]

A patient calls Monday morning. CallSphere voice agent identifies them by phone in DrChrono, confirms DOB for HIPAA, fetches the next available slot with their preferred provider, books the appointment, sends an intake form via SMS, and confirms insurance is on file. Total time 90 seconds. The medical assistant who used to do this can now triage clinical messages instead.

How the EHR APIs expose it

DrChrono at https://app.drchrono.com/api: GET /patients/?phone_number=... for lookup, POST /patients/ for create, GET /appointments/?date=...&doctor=... for schedule, POST /appointments/ for booking, PATCH /appointments/{id}/ for reschedule. OAuth 2.0 with scopes patients, patients:summary, calendar. Webhooks fire on APPOINTMENT_CREATED, APPOINTMENT_MODIFIED.

Athenahealth at https://api.athenahealth.com/v1/{practiceid}: GET /patients with firstname, lastname, dob for demographic match, POST /patients for create, GET /appointments/open for slot search by department and provider, PUT /appointments/{appointmentid} for booking (Athenahealth uses PUT to claim a pre-existing open slot rather than POST a new one), and PUT /appointments/{appointmentid}/cancel to cancel.

Auth: OAuth 2.0 with Athenahealth-specific token endpoint. Required Practice ID in path.

Both are HIPAA-eligible with BAA. CallSphere maintains BAAs with our subprocessors and runs healthcare workloads in segregated VPC tenancy.

How CallSphere implements it

CallSphere's Healthcare vertical ships 14 tools (lookup_patient, create_new_patient, get_available_slots, schedule_appointment, reschedule_appointment, cancel_appointment, verify_insurance, send_intake_link, add_clinical_note, request_callback, escalate_to_clinician, triage_symptom, book_lab, request_refill). The same 14 wrap DrChrono, Athena, eClinicalWorks, and Practice Fusion via a thin adapter. The voice agent never sees the EHR brand.

Explore a live demo and compare current plans to find the right fit for your business.

Build steps

1. Sign a BAA with the EHR vendor and confirm your CallSphere tenant is provisioned in HIPAA-segregated capacity.
2. Register your OAuth app. For DrChrono, request scopes patients and calendar. For Athena, request department-scoped access.
3. Implement lookup_patient with two-factor verification: phone match + DOB confirmation. Never confirm match by phone alone.
4. Implement get_available_slots. Filter by provider, location, visit type, and patient insurance acceptance.
5. Implement booking. For DrChrono use POST /appointments/. For Athena use PUT /appointments/{id} against an open slot ID returned by appointments/open.
6. Capture the call recording in HIPAA-eligible storage; do not include PHI in non-eligible LLM logs. CallSphere redacts before logging.
7. Send post-booking SMS via a HIPAA-eligible SMS vendor with a generic confirmation ("Your appointment is booked. View details: ...").
8. Subscribe to webhook APPOINTMENT_MODIFIED so out-of-band schedule changes propagate.

Code snippet

// Book an Athenahealth appointment by claiming an open slot
const booking = await fetch(
  `https://api.athenahealth.com/v1/${practiceId}/appointments/${appointmentId}`,
  {
    method: "PUT",
    headers: {
      Authorization: `Bearer ${athenaToken}`,
      "Content-Type": "application/x-www-form-urlencoded",
    },
    body: new URLSearchParams({
      patientid: matchedPatient.patientid,
      appointmenttypeid: visitTypeId,
      bookingnote: "Booked by CallSphere voice agent",
    }),
  }
);

FAQ

Is this HIPAA-compliant? Yes when both vendors have BAAs and the LLM provider is HIPAA-eligible. CallSphere uses HIPAA-BAA models and redacts PHI from non-eligible logs.

How do you handle DOB confirmation? Voice agent asks; speech-to-text outputs are matched against EHR DOB; mismatch routes to a human. We never confirm a patient by phone alone.

Does this work on FHIR? Yes. Both DrChrono and Athena expose FHIR endpoints; CallSphere supports them as an alternate adapter behind the same 14-tool interface.

What about Epic and Cerner? They expose FHIR endpoints with patient context and SMART-on-FHIR auth. Different scope review process; CallSphere supports both for enterprise deployments.

Explore a live demo and compare current plans to find the right fit for your business.

Sources

• DrChrono Developer Documentation
• Athenahealth Developer Portal
• DrChrono AI-Powered EHR Platform
• Athenahealth AI-Powered Healthcare