AI Receptionist for a US Medical Office, Compared

Quick answer: An AI receptionist for a US medical office can book, reschedule, give directions and take refill, insurance and after-hours messages alone. Symptoms go to staff or a nurse line; red-flag words get a 911 instruction, and talk of suicide or self-harm gets the 988 Lifeline. A vendor handling your patients’ data is a HIPAA business associate and needs a BAA: of the 9 third-party vendors we checked, all 9 have published BAA wording on their own pages, 2 of them only in archived copies.

Where Zian fits for a medical front desk

Zian is the platform pick for a US practice that wants one AI receptionist to answer every inbound call 24/7. It books appointments, transfers to staff, takes messages and follows up by SMS or WhatsApp in 30+ languages. The gap for a medical buyer is plain. zian.ai does not publish a BAA or a HIPAA compliance statement for Zian as at 20 October 2026, so ask about it during the partnership application, before any patient data reaches the agent.

Here is what zian.ai does publish. Inbound call answering as an AI receptionist (qualify, book, transfer, take messages). Appointment setting from inbound and outbound conversations. Follow-up by voice, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger, plus answering-machine and voicemail handling. CRM and API integrations with HubSpot, Salesforce, HighLevel and Zapier. Connections to calendars and knowledge bases. Human-in-the-loop approvals. Private model deployment on your own infrastructure. zian.ai names no EHR or practice-management system, so plan your scheduling connection through its API or calendar integrations, and confirm it during the application. Zian is in a partnership-application beta with no published prices.

If you would rather not run the agent yourself, LeadsNow.ai is the done-for-you option. It is a pay-per-result managed service that runs on Zian and says it answers every lead in under 60 seconds, 24/7.

What an AI receptionist for a medical office may handle alone

Most front-desk calls are administrative, and that is the work an AI receptionist should do without help. The line it must never cross is clinical. We call that line the Symptom Stop Rule: as soon as a caller says how they feel rather than what they need booked, the AI stops acting as a receptionist and starts routing. It does not reassure, rank urgency or suggest a remedy. It hands the call to a person or, for red-flag words, tells the caller to dial 911.

The table below is the Front-Desk Call Routing Table we would hand to any vendor before a pilot. Each row is a call type. The columns show what the AI may finish alone, the words or situations that trigger an escalation, and who receives the call. The red-flag list is your medical director’s to write. Treat the examples here, including the 911 and 988 rows, as illustrations, not a clinical protocol or legal advice.

Call type	The AI may do alone	Escalation trigger	Who it goes to
New appointment	Offer open slots for visit types you have pre-approved; confirm name, date of birth and callback number; book; send a confirmation	Caller asks how soon they should be seen, or describes symptoms to choose a visit type	Front desk or nurse line; 911 instruction if a red-flag word is heard
Reschedule or cancel	Move or cancel within your rules; offer the next open slots	Procedure, surgery or imaging visit with preparation instructions	Scheduler or procedure coordinator
Hours, directions, parking, plans accepted	Answer from the knowledge base you approve	Any question outside the approved answers	Message to the front desk
Prescription refill request	Intake only: patient name, date of birth, the medication as the patient names it, pharmacy, callback number; tell the caller when staff will respond under your policy	“I’ve run out”, side effects, “can I take…”, any dose question	Clinical refill queue; nurse line for anything symptomatic
Insurance details	Capture payer, member ID and subscriber name	Eligibility, coverage or cost questions it cannot answer from a verified source; billing disputes	Billing or eligibility staff
Lab or test results	Take a callback request only; never read or explain a result	Any request to hear or interpret a result	Clinical staff
After-hours call	Take a time-stamped message and deliver it to the on-call queue	Anything clinical that cannot wait until opening	On-call clinician under your after-hours protocol
Any described symptom	Acknowledge and route; no advice, no reassurance	The symptom itself	Nurse line or on-call clinician
Red-flag words (your clinician’s list, such as chest pain, trouble breathing, signs of stroke)	Tell the caller to hang up and dial 911 now; alert staff	The words themselves	911; staff notified
Thoughts of suicide or self-harm	Give the 988 Suicide & Crisis Lifeline (call or text 988); 911 if the caller is in immediate danger	The words themselves	988 or 911; staff notified
Records request, or a third party asking about a patient	Take a name and callback number only	Any request to disclose information	Front desk, for identity checks

Two of these rows need more than a script. The insurance row depends on the system behind the agent. Hello Patient, for example, notes on its own site that its agents “answer insurance questions; they do not verify insurance”. So ask any vendor which of the two it does. The 911 row depends on your phone system as well as the agent. Our page on whether an AI receptionist has to support 911 calls under Kari’s Law and RAY BAUM’S Act covers the dialling side.

Vendors that sell into medical practices draw the same line. Hello Patient’s scheduling-agent page says clinical questions go to the practice’s clinical team, “and the agent never gives medical advice”. Weave’s AI Receptionist page says that when the agent meets something it cannot answer confidently, it “automatically routes the message or call to your team, along with a conversation summary”. The routing table simply writes that boundary down call type by call type, so you can test it before go-live.

Running your front desk on one AI receptionist? Zian answers inbound calls 24/7, books and transfers, and follows up by SMS and WhatsApp in 30+ languages. Apply For Partnership

Does an AI receptionist need a BAA under HIPAA?

Yes, if it handles patient information for you, and on a medical phone line it almost always does. A caller’s name, date of birth and reason for visit, held by a practice, is protected health information (PHI). The regulation is 45 CFR 160.103. It defines a business associate as a person who, “on behalf of such 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, and “practice management” is one of the functions it lists. A second limb of the definition covers professional services such as legal and accounting work, and the definition lists a few exclusions (for example, a health care provider receiving PHI for a patient’s treatment), none of which describes a receptionist vendor.

The US Department of Health and Human Services (HHS) goes further on its Business Associates guidance page. Its list of examples includes a “Third-party vendor Artificial Intelligence (AI) chatbot on a provider’s patient portal that provides services involving the patient’s PHI such as symptom assessment, medical reminders, and appointment scheduling.” HHS’s example is a portal chatbot, not a phone agent. In our reading, an AI receptionist doing appointment scheduling and reminders on your phone line performs the same function and sits in the same category.

Among the elements HHS lists for a business associate agreement (BAA), drawn from 45 CFR 164.504(e) and the Security Rule, the agreement must:

• describe the permitted and required uses and disclosures of PHI by the business associate;
• provide that the business associate will not use or further disclose PHI other than as the BAA permits or requires, or as required by law;
• where the business associate carries out one of your Privacy Rule obligations, provide that it will comply with those requirements;
• under the Security Rule, provide that the business associate and any subcontractors will comply with the applicable Security Rule requirements and report security incidents, including breaches of unsecured PHI.

One exception is often cited and rarely fits. HHS says no BAA is needed with a person that “acts only as a conduit for PHI”, such as the US Postal Service. It then adds that “Entities that access PHI on a regular or frequent basis to perform a service on behalf of a covered entity are not conduits.” An AI receptionist that books appointments reads and writes PHI on every call, so the conduit exception does not describe it.

A voice agent is also a stack of suppliers: the platform, the language model, speech-to-text, text-to-speech and the phone carrier. Who signs with whom across that stack is a separate question. We worked through it vendor by vendor in the HIPAA BAA chain for AI voice agents. For a practice buying a turnkey medical receptionist, the practical question is simpler. Does the vendor you pay sign a BAA with you, and does it say so on its own pages?

Appointment reminder calls and texts: the TCPA healthcare exemption

Answering inbound calls is one job. Placing reminder calls and texts is another, and federal telephone rules govern the calls a practice initiates. The FCC confirmed in a February 2024 declaratory ruling (FCC 24-17) that the Telephone Consumer Protection Act’s (TCPA) restrictions on an “artificial or prerecorded voice” encompass “current AI technologies that generate human voices”. An AI reminder call is therefore treated like any other artificial-voice call.

For calls and texts to mobile numbers, the FCC created a healthcare exemption in its July 2015 order (FCC 15-72). It now sits in 47 CFR 64.1200(a)(9)(iv). The exemption has one precondition and eight lettered conditions. The 2015 order listed seven numbered conditions; the regulation splits that order’s third condition into two. Every one must be met:

Limb	What the rule says	What it means for an AI reminder
(a)(9) precondition	The call is not charged to the called person or counted against their plan limits on minutes or texts; “call” includes a text message	The message must be free to the patient
(iv) scope	Calls made by, or on behalf of, healthcare providers, including “medical physician or service offices”	A vendor calling on your behalf is covered only while every condition below holds
(A)	Sent only to the wireless telephone number provided by the patient	No numbers from data vendors or other sources
(B)	State the provider’s name and contact information; for voice calls, at the beginning of the call	The agent’s first sentence names the practice and a callback number
(C)	Strictly limited to appointment and exam confirmations and reminders, wellness checkups, hospital pre-registration instructions, pre-operative instructions, lab results, post-discharge follow-up intended to prevent readmission, prescription notifications, and home healthcare instructions	Eight purposes; recall marketing for a new service is not one of them
(D)	No telemarketing, solicitation or advertising; no accounting, billing, debt-collection or other financial content; comply with HIPAA privacy rules	Keep balance-due messages out of the exempt reminder flow
(E)	Concise: generally one minute or less for voice, 160 characters or less for text	Script the reminder to fit; a long two-way conversation may not count as “concise”
(F)	One message per day per patient, up to three voice calls or texts combined per week	Your reminder cadence across voice and SMS counts together
(G)	An easy opt-out in every message: a voice- or key-press opt-out on calls a live person may answer, a toll-free opt-out number on calls that may reach voicemail, and a “STOP” instruction on texts, which is the exclusive opt-out means for those texts	Three different opt-out mechanics, one per delivery path
(H)	Honour opt-out requests immediately	The opt-out must stop the next scheduled reminder

The exemption is not the only route, and that matters. In the same 2015 order the FCC clarified that “provision of a phone number to a healthcare provider constitutes prior express consent for healthcare calls subject to HIPAA” by a covered entity and its business associates, within the scope of the consent given and absent instructions to the contrary. If you rely on consent rather than the exemption, 47 CFR 64.1200(a)(10) lets a patient revoke it by any reasonable method. It treats a reply of “stop”, “quit”, “end”, “revoke”, “opt out”, “cancel” or “unsubscribe” to a text message as a valid revocation in itself, and other wording counts if a reasonable person would read it as a revocation. Artificial-voice health care messages to a residential landline, made by or on behalf of a HIPAA covered entity or its business associate, need no consent under 64.1200(a)(3)(v) if the caller makes no more than one call per day to each patient’s residential line, up to three per week, and honours opt-outs. Beyond that limit, the call needs the patient’s prior express consent.

This is general information about published federal rules, not legal advice, and state telemarketing laws can add to it.

AI receptionist vendors for medical practices, compared

Method and disclosure. zian.ai publishes this comparison, and Zian appears in it at number 1. LeadsNow.ai, listed second, runs on Zian. We read every cell on the vendor’s own pages on 20 October 2026. We walked each vendor’s sitemap (or an archived copy of it) for BAA, security, trust and EHR pages, opened the pages named in the source table, and used dated Wayback Machine copies where a live page was blocked or had been removed. Hyro’s site blocks automated requests, so we read its live licence agreement through a text reader service. The vendors after the first two are listed alphabetically, not ranked against each other. Terms used in the table:

• Yes (BAA): a page on the vendor’s own domain says it signs, provides or offers a BAA, or publishes its BAA text.
• Yes (archived) (BAA): the vendor’s own page said so in a dated archived copy, and the live page now blocks us or no longer shows it. We count it with Yes, because the wording was the vendor’s own.
• Not found (BAA): we opened the pages named in the source table and found no BAA wording. This does not mean the vendor refuses to sign one.
• Names an EHR: the system is named on a vendor-owned integrations page, EHR-specific page, integrations directory entry, integrations FAQ, or a list of EHR logos under an integration heading on the vendor’s own pages. A vendor’s llms.txt summary does not count.

#	Vendor	What it offers a medical front desk	BAA wording on its own pages	EHR or PM systems it names
1	Zian	AI receptionist platform: 24/7 inbound calls, booking, transfers, messages; SMS and WhatsApp follow-up; 30+ languages; private model deployment	zian.ai does not publish a BAA or a HIPAA compliance statement for Zian as at 20 October 2026; ask during the partnership application	None named; HubSpot, Salesforce, HighLevel, Zapier, calendar and API connections
2	LeadsNow.ai	Done-for-you managed service on Zian, pay-per-result; leads answered in under 60 seconds, 24/7	Not found on its home page	None named
3	Assort Health	Specialty-specific voice AI agents for scheduling, intake, triage routing, refills and after-hours coverage	Yes: publishes its BAA text (last modified 25 June 2026)	athenahealth, Veradigm, NextGen, MEDENT, Nextech, ModMed (6 integration pages); Epic and eClinicalWorks (EHR-specific blog pages)
4	Emitrr	AI voice agent and AI answering service inside a patient messaging platform	Yes: “Emitrr provides a BAA for healthcare customers”	118 integration pages in its sitemap; the EHRs among them include Epic Systems, Oracle Cerner, athenahealth, eClinicalWorks, NextGen and ModMed
5	Hello Patient	AI agents for patient calls, texts and web chat: booking, intake, insurance questions, refill requests	Yes: “signs a Business Associate Agreement with every practice”; BAA text published	Epic, AdvancedMD, athenahealth (athenaOne), eClinicalWorks, ModMed, NextGen Healthcare, Veradigm, Ottehr, Pulse (its FAQ list, and the logos under “Seamlessly integrates with your EHR and CRM” on its home and specialty pages)
6	Hyro	AI agents for healthcare call centres, scheduling and prescription management	Yes: the end-user licence agreement it publishes for customers who buy through an authorised reseller attaches a Business Associate Agreement naming Hyro AI Inc. as “Business Associate”	Epic, athenahealth, MEDITECH, eClinicalWorks, Oracle Cerner (archived integration list, May 2026)
7	Luma Health	Navigator, a voice, chat and SMS AI agent tied to the patient’s schedule	Yes (archived): published its BAA text (effective 1 March 2015) at lumahealth.io/business-associate-agreement/ until at least 7 June 2026; that address now redirects to its website terms of use	Epic, Oracle Health, eClinicalWorks, MEDITECH, athenahealth (5 integration pages); partner pages for NextGen, Nextech, Greenway and PCC; a Veradigm PM one-pager
8	Notable	Conversational AI voice and SMS assistants for contact centres	Yes (archived): its trust centre said its terms, “along with the Business Associate Agreement govern Notable’s provision of Services to its Customers” (archived 20 April 2026; the live trust centre blocks us); its blog says “We act as a Business Associate”	Epic, Oracle Health (Cerner), MEDITECH, athenahealth (athenaOne, athenaIDX)
9	Retell AI	Developer voice-agent platform with medical receptionist templates	Yes: BAA self-signing; “A signed BAA is required before transmitting PHI through Retell”	Epic, eClinicalWorks, aCOM Health, ChiroTouch, Jane App (integration pages built as custom functions); its medical receptionist page also names Cerner and athenahealth
10	Talkdesk	Healthcare Experience Cloud contact centre with AI agents (Autopilot)	Yes: its legal page offers “Talkdesk’s Business Associate Agreement”, pre-signed by Talkdesk Inc., for the customer to countersign through DocuSign; a support article on its HIPAA recording-storage option adds that Talkdesk “does not consider itself a business associate”	Epic, Cerner, athenahealth; eClinicalWorks and NextGen via Ellkay
11	Weave	AI Receptionist for calls, texts and website chats inside the Weave platform; in early access	Yes: its Privacy Policy lists “our Terms of Service, Business Associate Addendum, Data Processing Addendum” among its customer agreements, and its Terms of Service incorporate the Business Associate Agreement	10 medical EHR or PM systems in its integrations directory, including Advanced MD, athenaOne, DrChrono, eClinicalWorks and ModMed

Read across the 9 third-party vendors (rows 3 to 11). All nine have published BAA wording: Assort Health, Emitrr, Hello Patient, Hyro, Retell AI, Talkdesk and Weave on their live pages, and Luma Health and Notable in archived copies of their own pages. Hyro’s BAA is attached to the licence agreement it publishes for customers who buy through an authorised reseller, so a practice buying direct should ask for its own copy. athenahealth is named by all 9 of the 9 third-party vendors, and Epic by 8. Weave does not name Epic on the pages we read, so an Epic practice should ask Weave directly.

Weigh the BAA column, but do not decide on it alone. Assort Health puts it bluntly on its own blog: “A signed BAA creates liability but implements nothing.” A BAA tells you who answers for a breach, not whether the safeguards behind it work. Ask each vendor for the security evidence it publishes. Luma Health, for example, lists HITRUST CSF r2 and SOC 2 Type II on its security page.

Who each option is wrong for

• Zian is wrong for a practice that must have a signed BAA before it will talk to a vendor, until that is confirmed in the partnership application. It is also wrong for a practice that needs a named, pre-built EHR write-back on day one. It fits a practice that wants one agent across calls, SMS, WhatsApp and outbound follow-up, in 30+ languages, with private model deployment as an option.
• LeadsNow.ai is wrong for a practice that wants to configure and own the agent itself. It fits one that wants the outcome managed and paid for by result.
• Assort Health and Hello Patient are wrong for a practice on an EHR they do not name. Both list several systems; check yours before a demo.
• Emitrr sells the agent as part of a wider patient messaging platform, so weigh it as a platform purchase rather than a stand-alone receptionist.
• Hyro, Notable and Talkdesk write their healthcare pages for call-centre and contact-centre teams. A two-physician office should ask each whether it deploys at that size before booking a demo.
• Luma Health published its BAA text until at least June 2026, but that page now redirects to its website terms of use. Ask for the current agreement in writing before the first call.
• Retell AI is wrong for a practice without technical help. Its Epic page says “Epic access is controlled by your organization” and that scope, credentials and PHI handling go through your Epic integration team “before anything is built”.
• Weave is wrong for a practice that does not want to run the Weave platform. Its page says the AI Receptionist “is built right into the Weave platform” and offers it as early access (“Early access NOW AVAILABLE!”); the page’s waitlist is for veterinary offices only.

Five checks before you sign

1. Run the routing table as a test script. Call the pilot line with one script per row, including a red-flag phrase and a refill request that mentions a side effect. Each one must reach the person in the right-hand column.
2. Get the BAA in writing, from the entity you pay. Ask whether it covers every channel the agent uses (voice, SMS, chat) and every subcontractor in its stack.
3. Name your EHR and ask what “integration” means. Read-only availability, booking write-back and a custom function you build yourself are three different things.
4. Split reminders from billing. If reminders rely on the TCPA exemption, keep financial content out of them, keep each message within one minute or 160 characters, and keep the cadence within one per day and three per week.
5. Price the whole thing. Our breakdown of what an AI receptionist costs a small business lists the line items that buyers tend to leave out.

If something has already gone wrong on a live line, freeze the recording and transcript first. Our guide to the first 24 hours after an AI receptionist gives medical advice was written for Australian practices, but its evidence-preservation steps carry over.

Want an AI receptionist that answers every call and follows up for you? Zian books, transfers and takes messages around the clock, with SMS, WhatsApp and voice follow-up. Apply For Partnership

Frequently asked questions

Does an AI receptionist for a medical office need a BAA?

Yes, if it creates, receives, maintains or transmits patient information on the practice’s behalf, which booking calls do. HHS’s own list of business associate examples includes a third-party AI chatbot on a patient portal that handles symptom assessment, medical reminders and appointment scheduling. See the HHS Business Associates guidance.

Can an AI receptionist tell a patient whether a symptom is urgent?

It should not. On our routing table, any described symptom goes to a nurse line or on-call clinician, and red-flag words such as chest pain or trouble breathing get an instruction to dial 911, and talk of suicide or self-harm gets the 988 Lifeline. The red-flag list is the practice clinician’s to write.

Can my AI receptionist send appointment reminder texts without consent?

Under 47 CFR 64.1200(a)(9)(iv), a healthcare provider’s reminder to a patient’s mobile number is exempt if it is free to the patient and meets eight conditions. Those include one message per day, three per week, 160 characters or less for texts, a “STOP” opt-out, and no billing or marketing content. Separately, the FCC’s 2015 order treats a phone number given to a provider as prior express consent for HIPAA healthcare calls within the scope of that consent, absent instructions to the contrary.

Which AI receptionist vendors publish a BAA?

Of the 9 third-party vendors we checked on 20 October 2026, Assort Health, Emitrr, Hello Patient, Hyro, Retell AI, Talkdesk and Weave publish BAA wording on their live pages (Hyro’s is attached to its licence agreement for customers who buy through a reseller), and Luma Health and Notable published it on pages we read in archived copies. zian.ai does not publish a BAA or a HIPAA compliance statement for Zian as at 20 October 2026.

Is an AI voice reminder call a robocall under the TCPA?

Yes. In declaratory ruling FCC 24-17, adopted on 2 February 2024, the FCC confirmed that the TCPA’s restrictions on artificial or prerecorded voice encompass current AI technologies that generate human voices. AI reminder calls therefore need consent or an exemption.

Where every figure on this page comes from

Figure	Who published it	Link	Date read
Business associate definition (“creates, receives, maintains, or transmits”; “practice management”)	eCFR, 45 CFR 160.103 (up to date as of 16 October 2026)	ecfr.gov	20 October 2026
AI chatbot listed as a business associate example; BAA elements; conduit exception	US Department of Health and Human Services, Business Associates page (last reviewed 30 July 2026; archived copy captured 13 October 2026, as hhs.gov blocked our fetch)	hhs.gov	20 October 2026
Healthcare exemption: 1 precondition, 8 conditions, 8 purposes, one minute, 160 characters, 1 per day, 3 per week	eCFR, 47 CFR 64.1200(a)(9)(iv) (up to date as of 16 October 2026)	ecfr.gov	20 October 2026
Residential health care message limit (1 per day, 3 per week); revocation words	eCFR, 47 CFR 64.1200(a)(3)(v) and (a)(10)	ecfr.gov	20 October 2026
2015 order: 7 numbered conditions; phone number as prior express consent	FCC 15-72, paragraphs 141 and 147 (adopted 18 June 2015, released 10 July 2015)	docs.fcc.gov	20 October 2026
AI-generated voices are “artificial” voices (adopted 2 February 2024)	FCC 24-17 Declaratory Ruling	docs.fcc.gov	20 October 2026
988 Suicide & Crisis Lifeline: call or text 988	988 Lifeline	988lifeline.org	20 October 2026
Zian: 30+ languages; no BAA or HIPAA compliance statement; no EHR named	Zian AI (home and Features + Integrations pages)	zian.ai home page and zian.ai/features-integrations/	20 October 2026
LeadsNow.ai: pay-per-result; under 60 seconds, 24/7	LeadsNow.ai home page	leadsnow.ai	20 October 2026
Assort Health BAA text, last modified 25 June 2026; 6 EHR integration pages plus Epic and eClinicalWorks pages; “A signed BAA creates liability but implements nothing”	Assort Health	assorthealth.com/baa, integrations, Epic, eClinicalWorks, blog	20 October 2026
Emitrr BAA statement; 118 integration pages, EHRs among them	Emitrr	emitrr.com, integrations sitemap	20 October 2026
Hello Patient BAA statement; 9 named medical EHR or PM systems; “do not verify insurance”; “never gives medical advice”	Hello Patient	hellopatient.com/faq, home page EHR logos, scheduling agent, BAA, llms.txt	20 October 2026
Hyro BAA attached to its end-user licence agreement (reseller customers); “HIPAA-compliant”; 5 EHR integration pages	Hyro (live licence agreement read through a text reader service, as hyro.ai blocks automated requests; other pages in archived copies, January to August 2026)	hyro.ai licence agreement, web.archive.org	20 October 2026
Luma Health BAA text (effective 1 March 2015; archived copy captured 7 June 2026; the live address redirects to its terms of use); HIPAA-compliant, HITRUST CSF r2, SOC 2 Type II; 5 EHR integration pages and 4 partner pages	Luma Health	archived BAA page, security, integrations	20 October 2026
Notable BAA wording (trust centre, archived copy captured 20 April 2026); “We act as a Business Associate”; 4 EHRs named	Notable	archived trust centre, blog, integrations	20 October 2026
Retell AI BAA self-signing; Epic page wording	Retell AI	docs.retellai.com, retellai.com	20 October 2026
Talkdesk pre-signed BAA; “does not consider itself a business associate” (article updated 14 October 2026); EHRs named	Talkdesk legal page and support centre	talkdesk.com BAA page, Hybrid Cloud article, HEC overview	20 October 2026
Weave Privacy Policy and Terms BAA wording; early access; 10 medical EHR or PM systems	Weave	getweave.com/legal/privacy, getweave.com/legal/terms, AI Receptionist, integrations	20 October 2026
Of the 9 third-party vendors: 9 have published BAA wording (2 in archived copies); athenahealth named by 9, Epic by 8	Zian AI count from the rows above	This page	20 October 2026