How do I integrate an AI agent with Epic or athenahealth?
For Epic, register on open.epic and use its FHIR R4 APIs, then have each health system activate your app in its own instance; many writes, such as scheduling, go through HL7v2 interfaces or need the health system’s Epic team to build them. For athenahealth, build on the athenaOne APIs through its Developer Portal, pass athenahealth’s partner approval, then have each practice enable your app.
How long it takes
Epic: published estimates run from 2 to 14 months, sometimes 18, and the health system’s own review often takes longer than the build (Nirmitee (blog, confirm)). athenahealth: production access needs partner approval, a security review and authorization by each practice, which one guide puts at 1 to 3 months (Arkenea (blog, confirm)). Treat both as ranges to confirm with the vendor and the customer, not promises.
A two-week launch is still possible inside those ranges when it starts read-only or staff-confirmed: the agent takes the request and staff confirm the booking in the EHR until the write path is approved.
Epic
- Access
- FHIR R4 APIs registered on open.epic; each health system activates the client in its own instance. Many writes go through HL7v2 interfaces instead.
- Approval
- The health system’s Epic team activates and approves the app, usually after a security review. Write scopes are approved per organization.
- Sandbox
- A public open.epic sandbox with synthetic patients. Testing in the customer’s environment needs their Epic team.
- Writes
- Depend on each organization’s build. Scheduling needs their visit types and departments, and FHIR writes such as Observation.Create fail without a mapped flowsheet row (Epic FHIR specs).
- HL7v2 feeds
- A single ADT or SIU feed can take weeks to 8–10 weeks once the hospital assigns an interface analyst (Vital (blog, confirm)). Request the interface slot at signature.
- Cost
- Epic’s Vendor Services program is listed at $1,900 a year; confirm on open.epic before budgeting.
- Ask for on day 1
- App activation in their Epic instance, the FHIR scopes or HL7 interfaces in scope, and a named contact on their Epic team.
athenahealth
- Access
- athenaOne REST and FHIR APIs through the athenahealth Developer Portal. The practice enables access.
- Approval
- athenahealth’s partner approval first, then each practice enables your app.
- Sandbox
- A preview environment with test data. Per-app rate limits apply; reports say the preview limits are low, so confirm them with athenahealth. Load tests there may not reflect production.
- Configuration
- Appointment types, departments and providers are set per practice, and staff often override slot types by hand. Replay against the practice’s own past bookings and write the override rules down with staff.
- Ask for on day 1
- Practice enablement of your app, the departments and appointment types in scope, and a practice contact.
What applies to both
- A BAA with every vendor that touches PHI: the voice provider, model, speech-to-text, text-to-speech, telephony carrier, recording store, and eval and logging tools. One missing BAA blocks go-live (45 CFR 164.502(e)). Redact PHI from logs before shadow mode.
- Wrong-patient matches. Caller ID, name and date of birth collide: duplicate charts, family members on one phone. Require two or more identifiers and send ambiguous matches to staff. A wrong match is a privacy incident.
- California AB 3030. A generative-AI message to a patient about clinical information needs an AI disclaimer at the start and end of an audio interaction and instructions for reaching a human, unless a licensed provider reviews it (ArentFox Schiff). Scheduling-only calls are administrative, but agents drift into clinical questions mid-call. See consent and disclosure.
- Oracle Health (Cerner) is similar. Provider and system apps are activated per client after a sandbox demo, a FHIR Appointment create needs a Slot reference, and booking against order-role slots isn’t supported (Oracle docs).
Short answers
Can an AI agent book appointments directly in Epic?
It depends on each health system’s build. Scheduling writes need their visit types and departments and are approved per organization, so many launches start read-only or with staff confirming bookings.
Do I need a BAA for an AI voice agent that talks to patients?
Yes, with every vendor in the data path that handles PHI, including the model, speech, telephony, recording and logging providers. One missing BAA blocks go-live.
How long does athenahealth integration take for an AI agent?
Production access goes through athenahealth’s partner approval and a security review, then each practice enables the app. One published estimate is 1 to 3 months; confirm with athenahealth.