athenahealth
athenahealth owns the appointment and the patient record. DialSplice checks for an existing record, books with identity resolved first, and reads appointment outcomes back for show rate.
athenahealth owns the appointment. The agent stays on one screen.
Existing patient record lookup
Before booking, the agent sees whether the contact already exists in athenahealth, and at which locations.
Booking into athenahealth
Bookings write with identity resolved; an ambiguous match is held for a person. The CRM is updated from the same event.
Payments and card on file
Take a payment or update the card on file from the workspace, through athenahealth; the action is journaled like every other.
Appointment outcomes
Kept, cancelled, and no-show outcomes are read back and tied to the calls that produced them.
Built during onboarding when the vendor exposes an API. We confirm feasibility in the demo before you commit.
Reads, writes, and never returns.
- Whether a patient record already exists, and a match score
- Whether the patient exists at more than one clinic or location
- Demographics and contact preferences under scope
- Provider and room availability for booking
- Appointment schedule and outcomes: kept, cancelled, no-show
- Sales and revenue, including invoice status
- Bookings: create, reschedule, cancel
- Payments and card-on-file actions
- New patient profiles when no match exists
- Notes on the patient record: outcome, not transcript
- Appointment confirmations
- Clinical notes or treatment history
- Records outside the requesting location scope
- Provider credentials to the browser
Credentials never reach the browser
Provider tokens live server-side; the agent's browser only ever sees a work item.
Scope on every request
Organization and location travel with each call to the connector; an unknown scope fails closed.
Idempotent, journaled, reconciled
Every effect is journaled once; an ambiguous outcome enters reconciliation instead of a retry.
What athenahealth is usually spliced with.
One connector per category. These are the systems we most often see beside athenahealth; any of them can be swapped for the one you run.
Other EHR / system of record connectors.
athenahealth and DialSplice.
Who it is for, and what to ask before the demo.
Does DialSplice replace athenahealth?
No. athenahealth stays your system of record for appointments and patient records. DialSplice adds the queue, the contactability preflight, and the audit ledger on top, and hands work back to athenahealth where it belongs.
What does DialSplice store from athenahealth?
Work items, scope, timestamps, dispositions, event hashes, and operational telemetry. Identity is read from athenahealth under your scopes and is not copied into the ledger.
Is the athenahealth connector available today?
It is built on request during onboarding, when athenahealth exposes the API surface we need. We confirm feasibility in the demo before you commit, and quote it in writing.
Where do the athenahealth credentials live?
Server-side, always. The agent's browser only receives a work item; provider tokens never reach it, and every request carries organization and location scope.
See athenahealth spliced in.
Bring the rest of your stack; we will show you the workspace with every system named.