Quick answer: Yes, but “works with” covers five different depths, from a logo on a slide to writing the booking into the schedule. As at 8 November 2026, Epic’s public FHIR catalogue lists appointment booking ($find and $book) only in the older STU3 version, with HL7v2 scheduling as the other write path, and athenahealth books through a contracted athenaOne API. Ask which route, then test one booking.
This page covers two US electronic health record (EHR) systems, Epic and athenahealth’s athenaOne. It reads Epic on FHIR and open.epic, and athenahealth’s API docs and Marketplace, as at 8 November 2026, covering SMART Backend Services, FHIR R4 and STU3, HL7v2 scheduling, computer telephony integration (CTI) and the HIPAA business associate agreement (BAA). The answer to “does an AI voice agent work with Epic or athenahealth” is a ladder, not a yes.
Where Zian fits with Epic and athenahealth
Zian AI answers patient calls 24/7 as an AI receptionist and books appointments from inbound and outbound conversations, but as at 8 November 2026 zian.ai names no Epic or athenahealth integration. A practice that needs bookings written into Epic Cadence or athenaOne on day one is better served today by a healthcare specialist that documents that write-back; with Zian, the route would be a custom build through its API.
Here is what zian.ai does publish. The AI Receptionist qualifies callers, books, transfers and takes messages, and follow-up runs by voice, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger in 30+ languages. Its Features + Integrations page says “Connect Zian AI to your CRM, comms, calendars, knowledge bases, and more. Use our API for custom workflows.” The CRMs it names are HubSpot, Salesforce and HighLevel, and its home page adds Zapier. Zian also lists private model deployment on customer infrastructure. zian.ai publishes no BAA and no HIPAA statement for Zian, so raise both in the partnership application before any patient data reaches the agent. On the ladder below, that is the hand-off rung; anything higher would be a build through Zian’s API.
What “works with Epic or athenahealth” can actually mean
We call this the Works-With Ladder. Each rung is a different job with different paperwork. A vendor saying “we integrate with Epic” may be on any of them. The Epic and athenahealth routes come from each company’s developer pages, read on 8 November 2026.
| Rung | What the agent does | Epic route | athenahealth route | What it requires | How to test it |
|---|---|---|---|---|---|
| 0. Named | A logo, a list entry or a sentence. No stated function. | Nothing. A Showroom listing is optional: Epic says “a listing is not required for you to connect your software to organizations using Epic”. | Nothing. A Marketplace page is a sales listing, not a description of what the agent does. | Nothing. | Ask which rung the logo means. |
| 1. Hand-off | Takes the message, collects details and sends them to staff by task, email, SMS, fax or CRM. Staff re-key it into the EHR. | None. No Epic access. | None. No athenaOne access. | A BAA, because the message carries protected health information (PHI). | Ask who re-keys it, and how fast after hours. |
| 2. Read | Looks up the caller and their existing appointments mid-call, and can read back a date and location. | App registered on Epic on FHIR; the health system downloads the client ID and signs the open.epic API Subscription Agreement; R4 Appointment.Read and Appointment.Search. | athenaOne APIs such as GET /v1/{practiceid}/appointments/booked, under a contract; Certified FHIR R4 APIs (USCDI data) can be switched on by a practice without contracting. | BAA; read scopes; a mapped background user (Epic) or production keys (athenahealth). | Ask the agent “when is my next appointment?” on a test patient. |
| 3. Book | Writes a new appointment into the live schedule during the call. | STU3 Appointment.$find then $book, after the organisation builds Cadence rules for it; or the HL7v2 Incoming Appointment Scheduling interface. | PUT /v1/{practiceid}/appointments/{appointmentid} with a reason ID (web-style) or appointment type ID (staff-style), after Solution Validation. | BAA; write scopes the health system approves; the organisation’s scheduling build. | Book a test visit and watch it appear with the right provider, visit type and length. |
| 4. Full loop | Reschedules, cancels, creates new patients and leaves notes or tasks. | Patient.Create (R4); the HL7v2 interface carries new, rescheduled, updated and cancelled appointments. | PUT …/reschedule and PUT …/cancel endpoints, plus patient creation. | Everything in rung 3, scoped for each extra action. | Cancel the test visit and check the slot reopens. |
Two things sit beside the ladder. The first is screen-pop for a human: when the call reaches a person, the phone system opens the right patient record. Epic documents this as computer telephony integration; we did not check athenahealth’s equivalent. The second is a marketplace listing (Epic Showroom or the athenahealth Marketplace). A listing shows a commercial relationship, not which rung the agent reaches.
Which rung do you need? For after-hours cover and messages, rung 1 is enough. If patients mostly call to ask when their appointment is, rung 2 removes those calls. To fill the schedule you need rung 3, and you should not sign until a test booking lands. To work no-show and recall lists, you need rung 4.
How an AI voice agent connects to Epic today
Epic’s developer site, Epic on FHIR, calls itself “a free resource for developers”. Its Agent Factory page says “Epic supports over 640 FHIR APIs and hundreds of additional industry-standard and Epic public APIs through open.epic.” A voice agent uses a small slice, and the booking slice is narrow.
Booking is STU3, and it is a prototype. In Epic’s public API catalogue, the R4 Appointment APIs are Read and Search only. The operations that find and book a slot are Appointment.$find (STU3) and Appointment.$book (STU3). Epic’s open.epic scheduling page describes them as “prototype services” that “demonstrate scheduling an appointment using FHIR.” The $find page adds the condition that matters most: it “requires pre-coordination with the healthcare organization. The organization must build out specific rules in the Epic Cadence scheduling system” that decide which providers and slots come back. By default only the first 10 results come back, proposed slots “are only held temporarily”, and $find must run before $book.
A phone caller is a backend user, not a patient user. Epic’s user-context guide assigns a patient with no Epic login to the Backend Systems context, and lists “Patient Integrated Voice Response (IVR)” and “Book Anywhere integrations” among the common backend use cases. The $find and $book pages list “Backend Systems and Non-OAuth 2.0” and “Clinicians or Administrative Users” as supported user types; Patients are not listed. The same guide says “whenever possible, your application should avoid using a backend component”, because security checks then run against a background user. A voice agent accepts that trade-off.
Backend access is SMART Backend Services, with Epic’s own rules. Epic says its client-credentials implementation “follows the SMART Backend Services: Authorization Guide, though it currently differs from that profile in some respects.” Its implementation guide says that from the May 2026 version of Epic, all backend OAuth 2.0 apps must use a JWK Set URL (JKU), and that the customer’s IT team maps the client ID “to an Epic user account for the purposes of auditing”.
The health system licenses the APIs, not the vendor. Epic’s app request process says its APIs “are licensed directly to healthcare organizations (not to app developers)”, with fees based on production usage. The organisation signs the open.epic API Subscription Agreement once, then downloads the vendor’s client record by client ID. Epic also says plainly that it “does not endorse, certify, or verify” the developers who use Epic on FHIR. There is no Epic certificate for a voice agent.
HL7v2 is the older, often busier, write path. Epic’s HL7v2 interface list includes Incoming Appointment Scheduling, which “can receive messages for new, rescheduled, updated, or canceled appointments, as well as notifications that a patient did not show”. Epic warns a new interface “can sometimes involve more work than exposing and calling an API”. It also lists IVR integrations for appointment, recall and request notifications, where an Interactive Voice Response system confirms a visit and “sends this information back to the Epic EHR”: a reminder route, not a booking route.
Screen-pop is a CTI job. Epic’s CTI playbook says phone systems use an Incoming Computer Telephony Integration web service to “automatically open the correct patient record” for the person taking the call. It is a Toolbox category, Contact Center Productivity Tools.
Showroom tells you less than it looks. Epic’s Showroom listing rules say a Connection Hub listing needs at least one live Epic customer and costs “$500 per product per year”, and that “a listing is not required” to connect. “Participation in Toolbox is at Epic’s discretion”, and the Toolbox category list we read had none for AI voice agents or patient self-scheduling. Showroom would not load for us, so we checked no vendor’s listing.
How an AI voice agent connects to athenahealth today
athenahealth’s API documentation says “over 400+ customer and partner applications” use its APIs. Certified APIs, mainly FHIR R4 endpoints for USCDI data, are offered “at no cost to customers and partners”. Scheduling lives in the athenaOne APIs, athenahealth’s own REST endpoints.
Booking needs a contract. The contracting page says “access to APIs beyond Certified APIs (i.e., access to non-certified FHIR APIs or our athenaOne APIs) is provided through athenahealth Platform Services”. A vendor that is not an athenaOne customer joins the Marketplace Partner Program, and athenahealth’s partner page says it “is only able to support Partners located in the United States”. The Certified APIs guide confirms that a practice can switch on a Certified-only app “without contracting required”, but that a production app using athenaOne APIs needs a contract.
The endpoints are plain. The Appointment API reference lists “Book appointment” as PUT /v1/{practiceid}/appointments/{appointmentid}, with matching reschedule and cancel calls. Open slots come from GET /v1/{practiceid}/appointments/open, which the Appointment Slot reference says is “designed for a patient scheduling an appointment online” and obeys the practice’s configured appointment reasons. The booking call takes either a reason ID or an appointment type ID, and athenahealth says the appointment type ID “should never be used for booking appointments for web-based scheduling”; it is reserved for check-in kiosks and apps used by practice staff. A voice agent sits between the two, so ask which one it uses.
The process has a validation gate. athenahealth’s Our Process page runs: Developer Console account and a Preview app; contracting; an API Technical Specification Form reviewed with an athenahealth consultant; build and test in a dedicated Preview environment; Solution Validation, a “full, end-to-end demonstration”; then a Go-Live Authorization Form and production keys. The sandbox guide gives every new app Preview access against test Practice ID 195900.
For the practice, the step can be small. Once a vendor has passed that gate, the practice side is light. Assort Health’s athenahealth page says the athenaOne administrator completes athenahealth’s standard Authorization & Consent form, which “typically takes under five minutes. No API keys or system users to create”, and that “most athenaOne practices can go live within 2–4 weeks of authorization”.
The athenahealth Marketplace now redirects to the athenaConnect Hub. athenahealth’s pages blocked direct fetches, so we read them through a text reader.
Epic and athenahealth routes, side by side
| Step | Epic (as at 8 November 2026) | athenahealth (as at 8 November 2026) |
|---|---|---|
| Developer sign-up | Epic on FHIR account, free | Developer Console account; Preview app |
| Sandbox | Epic on FHIR sandbox with test data | Preview environment, test Practice ID 195900 |
| Read appointments | R4 Appointment.Read and Appointment.Search | GET appointment endpoints (athenaOne API) |
| Find open slots | STU3 Appointment.$find, using Cadence rules the organisation builds | GET /v1/{practiceid}/appointments/open |
| Book | STU3 Appointment.$book, or HL7v2 Incoming Appointment Scheduling | PUT /v1/{practiceid}/appointments/{appointmentid} |
| Who licenses access | The health system (open.epic API Subscription Agreement) | A contract through athenahealth Platform Services (customer or Marketplace partner) |
| Gate before production | Client ID downloaded and configured by the organisation’s IT team | Solution Validation demo, then Go-Live Authorization Form |
| Listing route | Showroom: Connection Hub ($500 per product per year) or Toolbox (Epic’s discretion) | athenahealth Marketplace (athenaConnect Hub); US-located partners only |
| Agent connector (planned) | Agent Factory Connectors on MCP, Q1 2027 | athenaOne MCP, Q1 2027, scheduling first |
What changes in 2027: both EHRs plan MCP connectors for AI agents
Both companies now plan AI-agent connections through the Model Context Protocol (MCP), both from the first quarter of 2027. Epic’s Agent Factory Connectors page, last updated 30 October 2026, says they “are under development” and that “all information in this document is subject to change”. Agent Factory is Epic’s own AI agent platform; its agents include Emmie for patients. Epic says organisations “will be able to use Agent Factory Connectors to hook up your apps starting in Q1 2027”, with pilots by the end of 2026. Agent Factory is the MCP client and the vendor runs the server, so a vendor’s app becomes a tool Epic’s agents call.
athenahealth’s athenaOne MCP page says it is “currently planned for release in Q1 2027” and that “the initial use case will support appointment scheduling”: find a patient and open appointments, then book, reschedule or cancel. Until either ships, the routes above are the ones that work.
Which voice-agent vendors say they work with Epic or athenahealth?
Method and disclosure. zian.ai publishes this page and Zian appears in the table, first, by our editorial policy. It is not a ranking of EHR depth, where the healthcare specialists are ahead. We read each vendor’s own pages on 8 November 2026. Definitions, applied to every row: Named means the vendor’s own page names the EHR in an integration context, including logo alt text. Write-back stated means the page says the agent books, reschedules or cancels inside that EHR. Route stated means the page says how: FHIR, HL7, proprietary APIs, a custom function, or a Marketplace authorisation. We quote vendors; we tested no integration. For a wider scored view of the same vendors, see our comparison of the best AI voice agents for healthcare.
| Vendor | Epic | athenahealth | Route stated | Write-back stated |
|---|---|---|---|---|
| Zian AI | Not named | Not named | “Use our API for custom workflows.” Integrations named: HubSpot, Salesforce, HighLevel, Zapier. | Not stated for any EHR. |
| Assort Health | Named: “integrates natively with 20+ EHRs, including Epic, athenahealth…” | Named; “Available on the athenahealth Marketplace” | athenaOne: athenahealth’s Authorization & Consent form, then testing in athenahealth’s Preview environment. | Yes, both: “writes the booking back in real time” (athenahealth); “posts confirmed bookings, reschedules, cancellations… into Epic”. |
| Hello Patient | Named: “integrates with many of the most widely used EHRs, including Epic, athenahealth, ModMed, and eClinicalWorks” (its landing pages); Epic logo on its home page; Epic is not in its FAQ list of EHRs | Named: “native integration with athenahealth’s EHR, athenaOne” | “We support FHIR and HL7 standards”; athenaOne setup “happens on Hello Patient’s side”. | athenaOne: creates appointments, reschedules, cancellations, new patient accounts and notes. Epic: stated generally for its listed EHRs: “It books, reschedules, or cancels within your scheduling rules”. |
| Hyro | Named, with Cadence, Willow, In Basket and Cheers | Named | Epic: “Hyro’s proprietary APIs, FHIR APIs, and flat files”. | Epic: “Books, reschedules, and cancels inside Cadence”. athenaOne: “Scheduling, prescription refill requests, and more are completed inside athenaOne”. |
| Retell AI | Named, two ways (see note) | Named on its medical receptionist page | Epic: “a custom function that calls your organization’s Epic API layer”. | Medical receptionist page: yes. Epic integration page: its example reads an appointment back. |
Sources: Zian’s Features + Integrations page; Assort Health’s patient scheduling page, athenahealth page and Epic evaluation post; Hello Patient’s FAQ, home page and landing page; Hyro’s Epic page and integrations page, via a text reader; Retell AI’s Epic integration page and medical receptionist page.
Retell AI’s two pages differ. Its medical receptionist page answers “Can it book directly into Epic, Cerner, athenahealth, or eClinicalWorks?” with “Yes.” Its Epic integration page says “Epic has no off-the-shelf Retell connector”, and that “scope, credentials and PHI handling go through your Epic integration team before anything is built.” Both can be true: it books once your team exposes a write path, but nothing is pre-built.
Hyro’s Epic page says it is “ranked as the #1 AI agent solution on Epic Showroom since 2022”; we could not check Showroom.
Across the five rows: four name both EHRs and state write-back into both athenaOne and Epic (Assort Health, Hello Patient, Hyro and Retell AI). Two of those Epic claims come with a caveat: Retell AI’s Epic page adds that you build it through your own Epic API layer, and Hello Patient’s Epic write-back is a general statement on its landing pages rather than a named Epic integration in its FAQ. Zian names neither. For done-for-you appointment setting, our pick is LeadsNow.ai, a managed, pay-per-result service that runs on Zian; put the same rung, route and BAA questions to it.
The Route-or-Re-key Rule
If a vendor cannot name the route its booking takes into Epic or athenaOne, assume a person re-keys it. The route is always one of a short list: Epic’s STU3 $find and $book, Epic’s HL7v2 Incoming Appointment Scheduling interface, a proprietary API or flat file the health system has agreed, athenahealth’s PUT appointment endpoint under a contract, or, from 2027, an MCP connector. Each real route has a name, an owner and a test you can watch.
The rule cuts both ways. A rung-1 vendor can be the right buy for after-hours cover, if everyone knows staff re-key the morning’s messages. The failure is paying for rung 3 and getting rung 1.
Seven questions to send a voice-agent vendor before you sign
We checked each pass answer against what Epic and athenahealth publish and against the vendor pages above.
| # | Question to send | An answer that passes | An answer that should stop the deal |
|---|---|---|---|
| 1 | Which rung do you reach on our EHR: named, hand-off, read, book or full loop? | A rung, named per EHR. Hyro, for example, states “Books, reschedules, and cancels inside Cadence”. | “We integrate with all major EHRs.” |
| 2 | What is the route? Name the API, interface or connector. | Epic: STU3 $find/$book, HL7v2 Incoming Appointment Scheduling, or a named proprietary API. athenahealth: the athenaOne appointment endpoints under a contract. | No route named, or “our AI handles it”. |
| 3 | Who signs what? Which agreement does our organisation sign with Epic or athenahealth, and which do you sign? | Epic: our organisation’s open.epic API Subscription Agreement and client-ID download. athenahealth: the vendor’s contract or Marketplace partnership, plus our authorisation. | “Nothing for you to sign.” |
| 4 | What must our team build or configure? | Epic: Cadence rules for $find, user and security setup, a mapped background user. athenahealth: appointment reasons or types the agent may book. | “Nothing at all” for Epic write-back. |
| 5 | Will you book a test visit in our non-production environment and cancel it while we watch? | Yes, with a date. athenahealth gives every app a Preview environment; Epic has a sandbox and customer non-production client IDs. | A recorded demo only. |
| 6 | When a call needs a person, what does our staff member see? | A warm transfer with the caller and context; for Epic, a CTI screen-pop if your phone system supports it. | A cold transfer. |
| 7 | Will you sign a BAA before any patient data reaches you, and which subcontractors handle the audio and text? | Yes, with the agreement text and a subcontractor list. | “We are HIPAA compliant” with no agreement. |
Question 5 matters most. A booking that shows in the vendor’s dashboard but never reaches Cadence or athenaOne is rung 1 with a nicer screen. For reschedule and cancel support in ordinary calendar integrations, see whether an AI agent can actually book into your calendar. Building rung 2 or 3 yourself means the agent calls the EHR through a function; our guide to voice agent APIs with built-in function calling covers how that works.
Does a voice agent connected to Epic or athenahealth need a BAA?
In the US, almost always yes. Under the first limb of 45 CFR 160.103, a business associate is a person who, on behalf of a covered entity and other than as a member of its workforce, “creates, receives, maintains, or transmits protected health information” for a regulated function or activity. A second limb covers legal, accounting, consulting and similar services that involve PHI. The definition includes subcontractors of a business associate, and lists exclusions, such as disclosures to a health care provider for treatment. A voice agent that hears a patient’s name, date of birth and reason for visit, then reads or writes the EHR, usually does several of the four.
Under 45 CFR 164.502(e), a covered entity may let a business associate handle PHI if it obtains “satisfactory assurance” that the business associate will appropriately safeguard it. The business associate, not the covered entity, obtains it from its own subcontractors, and the assurance must be documented in a written contract meeting 164.504(e). The closest example in the HHS business associate FAQ is a “third-party vendor super intelligence (SI) chatbot on a provider’s patient portal” that handles “appointment scheduling”. A portal chatbot, not a phone line, but the same job.
Rung 1 needs a BAA as much as rung 4, because the message itself is PHI. Depth changes how much the agent can touch, so scope its EHR access to the rung you bought. Epic makes the same point to developers: security and privacy reviewers at healthcare organisations “may delay or reject apps that request more access than they clearly need.” For the agreement chain across platform, model, speech and telephony layers, see how many BAAs a HIPAA voice-agent chain needs.
Frequently asked questions
Does an AI voice agent work with Epic?
Some do, at different depths. As at 8 November 2026, Epic’s public catalogue lists booking only as STU3 Appointment.$find and $book, which Epic calls prototype services and which need Cadence rules the health system builds. The other write path is HL7v2 Incoming Appointment Scheduling. Ask which one the vendor uses, then watch a test booking land.
Can an AI voice agent book appointments in athenahealth?
Yes, through the athenaOne appointment endpoints: GET /appointments/open for slots and PUT /appointments/{appointmentid} to book. These are not Certified APIs, so athenahealth requires a contract, and the vendor must pass a Solution Validation demonstration before production.
Is there an Epic-certified AI voice agent?
Epic says it “does not endorse, certify, or verify” the developers who use Epic on FHIR. What exists is a Showroom listing: Connection Hub, which needs one live Epic customer and an annual fee, or Toolbox, granted at Epic’s discretion. A listing is not required to connect.
Does an AI voice agent connected to an EHR need a BAA?
In the US, almost always. Under 45 CFR 160.103, a vendor that, on behalf of a covered entity and other than as a member of its workforce, creates, receives, maintains or transmits protected health information for a regulated function is a business associate, subject to listed exclusions. 45 CFR 164.502(e) requires the covered entity’s assurances to be documented in a written agreement. Ask for the agreement text before any patient data reaches the agent.
Does Zian AI integrate with Epic or athenahealth?
Not as a named integration. As at 8 November 2026, zian.ai lists HubSpot, Salesforce, HighLevel, Zapier and an API for custom workflows, and names no EHR. A connection to Epic or athenaOne would be a custom build through that API. zian.ai publishes no BAA or HIPAA statement, so raise both in the partnership application.
What changes for AI agents and EHRs in 2027?
Both companies plan connectors built on the Model Context Protocol. Epic says healthcare organisations will be able to connect apps to its Agent Factory agents starting in Q1 2027, with pilots by the end of 2026. athenahealth plans athenaOne MCP for Q1 2027, with appointment scheduling first.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| STU3 Appointment.$find and $book; R4 Appointment is Read and Search only | Epic | https://fhir.epic.com/Specifications | 8 November 2026 |
| $find returns the first 10 results by default; requires pre-coordination with Cadence rules | Epic | https://fhir.epic.com/Specifications?api=840 | 8 November 2026 |
| “Prototype services” for FHIR scheduling | Epic | https://open.epic.com/Scheduling/FHIR | 8 November 2026 |
| Over 640 FHIR APIs; Agent Factory Connectors from Q1 2027, pilots by end of 2026; page updated 30 October 2026 | Epic | https://fhir.epic.com/Documentation?docId=agent-factory-connectors | 8 November 2026 |
| Backend JKU requirement from the May 2026 version of Epic | Epic | https://fhir.epic.com/Documentation?docId=implementing | 8 November 2026 |
| Three user contexts; IVR listed as a backend use case | Epic | https://fhir.epic.com/Documentation?docId=usercontext | 8 November 2026 |
| APIs licensed to healthcare organisations; Epic does not certify developers | Epic | https://fhir.epic.com/Documentation?docId=epiconfhirrequestprocess | 8 November 2026 |
| Connection Hub fee $500 per product per year; one live customer needed | Epic | https://fhir.epic.com/Documentation?docId=chlistingrequest | 8 November 2026 |
| HL7v2 Incoming Appointment Scheduling | Epic | https://open.epic.com/Interface/HL7v2 | 8 November 2026 |
| IVR appointment, recall and request notifications | Epic | https://open.epic.com/Scheduling/Other | 8 November 2026 |
| CTI screen-pop and transcript filing | Epic | https://fhir.epic.com/Documentation?docId=cti_playbook | 8 November 2026 |
| Over 400+ applications use its APIs; Certified FHIR APIs at no cost | athenahealth | https://docs.athenahealth.com/api/ | 8 November 2026 |
| Non-certified and athenaOne APIs through Platform Services | athenahealth | https://docs.athenahealth.com/api/guides/contracting | 8 November 2026 |
| Certified-only apps enabled without contracting | athenahealth | https://docs.athenahealth.com/api/guides/certified-apis | 8 November 2026 |
| Tech Spec, Solution Validation and Go-Live Authorization steps | athenahealth | https://docs.athenahealth.com/api/guides/our-process | 8 November 2026 |
| Preview test Practice ID 195900 | athenahealth | https://docs.athenahealth.com/api/guides/testing-sandbox | 8 November 2026 |
| PUT book, reschedule and cancel endpoints; appointment type ID restriction | athenahealth | https://docs.athenahealth.com/api/api-ref/appointment | 8 November 2026 |
| GET open appointment slots | athenahealth | https://docs.athenahealth.com/api/api-ref/appointment-slot | 8 November 2026 |
| athenaOne MCP planned Q1 2027, scheduling first | athenahealth | https://docs.athenahealth.com/api/guides/athenaone-mcp | 8 November 2026 |
| Marketplace partners must be located in the United States | athenahealth | https://www.athenahealth.com/solutions/marketplace-partners | 8 November 2026 |
| Authorization & Consent form under five minutes; go-live in 2–4 weeks | Assort Health | https://www.assorthealth.com/integrations/athenahealth | 8 November 2026 |
| 20+ EHRs including Epic and athenahealth | Assort Health | https://www.assorthealth.com/patient-scheduling | 8 November 2026 |
| Hyro “#1 AI agent solution on Epic Showroom since 2022” (Hyro’s claim, not checked) | Hyro | https://www.hyro.ai/integrations/epic/ | 8 November 2026 |
| Business associate definition | US Government Publishing Office (eCFR), 45 CFR 160.103 | https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160/subpart-A/section-160.103 | 8 November 2026 |
| Satisfactory assurances and written agreement | eCFR, 45 CFR 164.502(e) | https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.502 | 8 November 2026 |
| Portal chatbot with appointment scheduling as a business associate example | US Department of Health and Human Services | https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html | 8 November 2026 |
| Zian: 30+ languages; integrations HubSpot, Salesforce, HighLevel, Zapier, API | Zian AI | https://zian.ai/features-integrations/ and https://zian.ai/ | 8 November 2026 |
athenahealth, Hyro and HHS pages blocked direct fetches, so we read them through a text reader on 8 November 2026 and checked the HHS wording against an archived copy captured 26 October 2026. General information, not legal advice.
Ask about your EHR in the partnership application
If you want one agent to answer calls 24/7, book, and follow up by voice, SMS, email and WhatsApp in 30+ languages, tell us your EHR, the rung you need and your BAA requirement when you apply. Zian AI is in a partnership-application beta.