EHR and calendar integrations
OpenEMR integration, plus athenahealth, eCW and Open Dental: status
Clinic Answering Service is designed to read your real schedule and write appointments, intake answers, call summaries and eligibility results back into the system you already run. This page states, for each system, what works in production today and what is still a sandbox or on the roadmap. A logo or a name on this page is not a claim of production readiness.
What is live today (October 2026)
| System | Status today | Production target | What that means |
|---|---|---|---|
| OpenEMR | Sandbox (demo) | Planned: write-enabled, first in line | Bookings, patient matches, notes and the sync log run against a sandbox adapter that returns test references. No production OpenEMR write-back is live yet; the first pilot is planned with Radiatus-hosted OpenEMR clients. |
| athenahealth | Sandbox (demo) | Planned: write-enabled after Marketplace approval | Sandbox only. Clinic Answering Service is not yet listed on the athenahealth Marketplace, so no live athenahealth practice can be connected today. |
| eClinicalWorks | Sandbox (demo) | Planned: read via FHIR, write via HL7 SIU | Sandbox only. A live connection needs eClinicalWorks to enable the FHIR API and an HL7 interface for your account; none is in production yet. |
| Open Dental | Sandbox (demo) | Planned: write-enabled | Sandbox only. The Open Dental API adapter is planned; until then dental bookings stay in the Clinic Answering Service schedule and reach staff by export or the REST API. |
| Dentrix | Planned | Planned: scoped per Dentrix version | Not available today, not even as a dedicated sandbox. We scope G7 or Ascend per practice and will tell you in writing whether write-back is possible before you sign. |
| REST API and CSV export | Live | Live: read and write | Live in every workspace today. Use it to pull bookings, calls and eligibility results into any system while the EHR adapters are in development. |
| Google Calendar | Sandbox (demo) | Planned: write-enabled | Sandbox only. Google Calendar OAuth sync is planned; trial workspaces book into the built-in Clinic Answering Service schedule instead. |
- OpenEMRNative API (FHIR R4 + REST)Sandbox (demo)
- athenahealthFHIR R4 + HL7 (planned)Sandbox (demo)
- eClinicalWorksFHIR R4 + HL7 (planned)Sandbox (demo)
- Open DentalOpen Dental API (planned)Sandbox (demo)
- DentrixScoped per practicePlanned
- REST API and CSV exportAPI keyLive
- Google CalendarCalendar (planned)Sandbox (demo)
- Something elseAsk us: scoped in writing
What the status labels mean
Live: works in production for paying customers today.
Sandbox (demo): the full booking flow runs in your trial against a simulated adapter that returns test references (for example OPE-APT-12345). Nothing is written to a real EHR.
Write-enabled / Read-only: once an adapter is live, whether it can create appointments and notes or only read schedules and patients.
Planned: on the roadmap, not available yet, no date promised.
Every connection runs over TLS 1.2+ with scoped credentials and is covered by the BAA.
Native API (FHIR R4 + REST) · Sandbox (demo)
Clinic Answering Service + OpenEMR
The first integration on the roadmap, designed by the Radiatus team that hosts OpenEMR for US clinics. Existing Radiatus OpenEMR clients will get $0 setup when the production adapter is released.
What it will write once live
- Appointments in the calendar with provider, facility, category and duration
- New patient demographics and insurance, matched by phone, name and DOB
- Intake answers as a patient note and, with forms enabled, as a structured form
- Call summary with recording link as a patient note on the encounter-free timeline
- Eligibility 271 result stored against the appointment
- Refill, results and clinical questions as messages in the provider or nurse inbox
Status today: Sandbox (demo). Bookings, patient matches, notes and the sync log run against a sandbox adapter that returns test references. No production OpenEMR write-back is live yet; the first pilot is planned with Radiatus-hosted OpenEMR clients.
Self-hosted and Radiatus-hosted OpenEMR will both be supported. For self-hosted installs behind a firewall, Clinic Answering Service connects through an outbound TLS tunnel so no inbound ports are opened.
Planned setup steps
- Create a Clinic Answering Service API client in OpenEMR. In Administration > System > API Clients, register Clinic Answering Service with the FHIR and standard API scopes for patient, appointment and message resources. OpenEMR 6.1 or later is supported; 7.x is recommended.
- Authorize and map. Clinic Answering Service connects with OAuth2, lists your facilities, providers and appointment categories, and you map each to the appointment types Clinic Answering Service may book.
- Choose write rules. Decide whether new patients are created automatically or flagged for review, and which notes go to which inbox.
- Test on your own number. Call the demo line, book a visit and watch it appear in the OpenEMR calendar with the summary attached before you forward any patient calls.
Why OpenEMR first
Thousands of US clinics run OpenEMR, yet few answering services or AI receptionists write to it. Radiatus hosts and integrates OpenEMR for US clinics, so OpenEMR is the first production adapter on the roadmap. Today the OpenEMR connection is a sandbox (demo); the first live pilot is planned with Radiatus-hosted OpenEMR clients.
How a booking will land
When the adapter is live, Clinic Answering Service reads the provider's calendar and facility hours, offers two open slots, and on confirmation creates the appointment with the category you mapped (for example "Office Visit", 15 minutes). The patient note carries the summary and recording link; the 271 result is stored against the appointment.
Messages, not clinical writes
Refill requests, results questions and symptoms become messages in the OpenEMR provider or nurse inbox with the details captured. Clinic Answering Service never writes to the clinical chart, orders or prescriptions.
FHIR R4 + HL7 (planned) · Sandbox (demo)
Clinic Answering Service + athenahealth
Connects through athenahealth's API marketplace with FHIR R4 for scheduling and patient resources and HL7 SIU for appointment events.
What it will write once live
- Appointments on the provider schedule by department and appointment type
- Patient registration and demographics updates
- Call summary and intake as a patient case or document
- Eligibility result attached to the appointment note
Status today: Sandbox (demo). Sandbox only. Clinic Answering Service is not yet listed on the athenahealth Marketplace, so no live athenahealth practice can be connected today.
Marketplace approval is controlled by athenahealth and has not been obtained yet. We will update this page when it is.
Planned setup steps
- Request Clinic Answering Service in the athenahealth marketplace. Approve the Clinic Answering Service app for your practice ID; this takes athenahealth one to five business days.
- Map departments and appointment types. Clinic Answering Service lists your departments, providers and appointment types; choose which Clinic Answering Service may book and the default duration for each.
- Go live. Book a test visit from the demo line and confirm it appears on the schedule with the case attached.
FHIR R4 + HL7 (planned) · Sandbox (demo)
Clinic Answering Service + eClinicalWorks
Uses the eCW FHIR R4 API for patient and schedule reads and HL7 SIU messages for appointment write-back.
What it will write once live
- Appointments on provider and resource schedules
- Patient demographics for new callers
- Call summary and intake as a patient document
- Refill and clinical questions as a telephone encounter
Status today: Sandbox (demo). Sandbox only. A live connection needs eClinicalWorks to enable the FHIR API and an HL7 interface for your account; none is in production yet.
The HL7 interface fee, if any, is set by eClinicalWorks, not Clinic Answering Service.
Planned setup steps
- Enable the eCW FHIR and interface license. Your eCW account manager enables the FHIR API and an HL7 SIU interface; Clinic Answering Service provides the interface specification.
- Connect and map. Clinic Answering Service reads providers, facilities and visit types; you choose which visit types are bookable.
- Test and forward. Book from the demo line, verify the appointment and telephone encounter, then forward your number.
Open Dental API (planned) · Sandbox (demo)
Clinic Answering Service + Open Dental
Connects to the Open Dental API for operatory and provider schedules, patient lookup and appointment write-back with procedure-based durations.
What it will write once live
- Appointments in operatory slots with the right length for the procedure
- Patient records and insurance for new callers
- Call summary as a commlog entry with the recording link
- Eligibility result stored on the patient insurance plan
Status today: Sandbox (demo). Sandbox only. The Open Dental API adapter is planned; until then dental bookings stay in the Clinic Answering Service schedule and reach staff by export or the REST API.
Open Dental is the first dental system on the roadmap. Same-day go-live will only be promised once the production adapter is released.
Planned setup steps
- Create a Clinic Answering Service API key in Open Dental. In Setup > Advanced Setup > API, add Clinic Answering Service with permissions for patients, appointments and commlog.
- Map operatories and providers. Choose which operatories, providers and appointment types Clinic Answering Service may book and the default lengths.
- Test from the demo line. Book a hygiene visit and watch it appear in the Open Dental schedule before forwarding.
Scoped per practice · Planned
Clinic Answering Service + Dentrix
Dentrix G7 and Dentrix Ascend expose different interfaces, so each connection is scoped and confirmed before you sign.
What it will write once live
- Appointments on the Dentrix schedule (Ascend API; G7 via the Dentrix Developer Program connector)
- Patient records for new callers
- Call summary and intake delivered to the front desk inbox
Status today: Planned. Not available today, not even as a dedicated sandbox. We scope G7 or Ascend per practice and will tell you in writing whether write-back is possible before you sign.
Until a Dentrix write-back is confirmed for your version, Clinic Answering Service delivers bookings by secure inbox and Google Calendar.
Planned setup steps
- Tell us your Dentrix version. G7 on-premise or Ascend cloud; we confirm the write-back path and any Henry Schein connector requirement.
- Connect. Ascend connects through its API; G7 connects through the developer connector installed on your server.
- Test and go live. Book from the demo line and confirm the appointment before forwarding calls.
API key · Live
Clinic Answering Service + REST API and CSV export
The integration path that works in production today: a REST API (version 1, API-key authenticated) and CSV exports that any EHR team, interface engine or practice IT person can use.
What it does today
- Read and create calls, appointments, patients and waitlist entries (GET and POST /api/v1/...)
- Cancel appointments and request an eligibility check for a patient
- Read the revenue ledger
- CSV export of the call log, patients, ledger and the PHI access log from the app
Status today: Live. Live in every workspace today. Use it to pull bookings, calls and eligibility results into any system while the EHR adapters are in development.
Eligibility checks requested through the API use the same sandbox clearinghouse as the app until a clearinghouse is contracted for your account.
Setup steps
- Create an API key. In the app, open the API keys screen and create a key with the narrowest scope you need. Keys are stored only as hashes.
- Call the API. Send requests to /api/v1 with the key in the Authorization header over TLS.
- Schedule exports. Or download CSV exports from the call log, patients and ledger screens and import them into your EHR.
Calendar (planned) · Sandbox (demo)
Clinic Answering Service + Google Calendar
For practices without an EHR schedule, or as a mirror for providers who live in their calendar.
What it will write once live
- Appointments on a calendar per provider or location
- Patient name, phone and reason in the event (no diagnosis or insurance details)
- Call summary link in the event description
Status today: Sandbox (demo). Sandbox only. Google Calendar OAuth sync is planned; trial workspaces book into the built-in Clinic Answering Service schedule instead.
PHI in calendar events is minimized by design; full intake and eligibility stay in Clinic Answering Service under the BAA.
Planned setup steps
- Connect Google Workspace. Authorize Clinic Answering Service with calendar scope for the calendars you choose.
- Set bookable hours and types. Define working hours, buffer times and appointment lengths.
- Go live. Forward your number; bookings appear in the calendar within seconds.
How the connection is secured
This describes how production adapters are built; the sandbox adapters used today do not connect to any external system. Each integration uses a dedicated service identity with the narrowest scope the EHR allows: read schedule and patients, write appointments, notes and messages. Credentials are stored encrypted, rotated on request and never shared across workspaces. Clinic Answering Service connects outbound over TLS 1.2 or higher; for self-hosted systems behind a firewall, an outbound tunnel means no inbound port is opened. Every write Clinic Answering Service makes is attributed to the Clinic Answering Service user in your EHR's own audit log, and mirrored in Clinic Answering Service's access log under the BAA.
Not sure your system is on the list? Today, every practice starts with the built-in Clinic Answering Service schedule plus the REST API or CSV export, while we scope a direct connection, and switches over later without changing its phone setup. Tell us what you run and we will confirm the path before you sign anything.
EHR write-back and eligibility checks are included on the Practice ($349 a month) and Group ($699 a month) plans; see clinic answering service pricing. For the technical detail behind the OpenEMR connection, read the OpenEMR phone and appointment automation guide.
Frequently asked questions
Which EHR integrations are live today?
None of the EHR write-back adapters is in production yet. OpenEMR, athenahealth, eClinicalWorks, Open Dental and Google Calendar run as a sandbox (demo) that returns test references, and Dentrix is planned. What is live today is the REST API and CSV export, which any EHR team can use. Each section below shows its status.
What will Clinic Answering Service write into my EHR?
Once a production adapter is released for your EHR: appointments in real slots, new-patient demographics, intake answers, a three-line call summary with a link to the recording and the eligibility result for the visit. Nothing clinical is written; a refill or symptom message becomes a task for the provider.
What if my EHR is not listed?
Today, bookings stay in the Clinic Answering Service schedule and reach your system through the REST API or CSV export. If your system exposes a FHIR R4 or HL7 v2 SIU interface, tell us; we scope it and state in writing whether and when a connection is planned before you sign.
How does Clinic Answering Service match a caller to the right patient record?
By phone number first, then name and date of birth confirmed on the call. If two records match, Clinic Answering Service asks one more question (last visit or address) rather than guessing. New callers get a new record flagged for front-desk review.
Is the EHR connection covered by the BAA?
Yes. The BAA covers every connection, including the API. EHR credentials you enter are stored encrypted with AES-256-GCM. Production adapters are designed to use scoped credentials, TLS 1.2+ and, where the EHR supports it, OAuth2 with a dedicated service user so every write is attributed to Clinic Answering Service in your EHR audit log.
How will I know when my EHR goes live?
This page is the public status list and is updated when an adapter moves from Sandbox to Live. Customers on a waiting list for an adapter are emailed, and no plan is ever sold on the promise of a live EHR connection that is not yet released.
Ask where your EHR stands
Tell us which system you run. Within one US business day we reply with its honest status (live, sandbox or planned), what you can use today and a demo of the booking flow.