Assort Health Voice Agents on Epic: What Is Documented and What Is Not

Not published. For a voice agent on Epic, the standard paths are Epic on FHIR for reading the schedule, provider and patient demographics and for writing appointment bookings where the site exposes that capability; HL7 v2 SIU messages for schedule feeds and appointment updates at sites that prefer interfaces; and, in some deployments, a scheduling write that goes through a work queue for staff to confirm rather than directly into the book. Epic's own Cadence and MyChart scheduling logic, including decision trees and visit type rules, has to be respected by any external booker, and that is usually the hardest part of the build.

Which of these Assort Health uses at a given site, and whether its Epic booking is direct or staff confirmed, is the first question to ask. The second is whether the vendor has a Showroom listing, because many Epic sites will only approve listed applications and a listing shortens the security review. The third is how the agent identifies the caller against the Epic record, since misidentification is the failure mode with the highest consequence. Our integration questions guide covers the rest.

Until you have a written interface specification from the vendor, plan on your interface team owning the schedule feed and your Epic Cadence analyst owning the booking rules.

Little that a clinician sees, which is the point. The agent answers inbound calls, identifies the caller, understands intent, and either completes the task, such as a reschedule, cancellation, confirmation or new patient registration, or routes the call to the right department. The results appear in Epic as appointment changes and, for new patients, as registration data. The vendor's public case studies cite a 5 percent increase in appointment volume at one customer; that is a customer stated figure from one site.

For the buyer, the questions are about what the agent is allowed to write without a human. Rescheduling an existing patient into an open slot is low risk. Registering a new patient and creating a record is not, because duplicate and mismatched records are expensive to unwind. Our AI phone agent use case page sets out the containment, abandonment and error metrics to track, and the patient scheduling use case covers the booking rules an agent must respect.

• The integration method and, if applicable, the Showroom vendor client, raised through your integration request process.
• The schedule read and appointment write interfaces, with your Cadence analyst confirming that visit types, decision trees and provider rules are enforced for agent bookings.
• Patient identification rules: what the agent may accept as proof of identity before reading or changing anything.
• Security review and the business associate agreement, covering call recording retention, transcription subprocessors and model training. The HIPAA and AI page lists what to insist on.
• Telephony: call recording consent by state, TCPA review for outbound calls and texts, and how transfers reach your staff.
• A test plan against real scheduling scenarios and a change control slot.

Practices on a hosted Epic instance should expect the first two items to sit with the host. Ask the host how long their interface queue is before promising a go live date to the front desk.

The first gap is documentation. A vendor that leads with its athenahealth integration and does not publish an Epic page is telling you where its deepest experience lies. That may change; check the vendor's site again before you sign.

The second is the general risk of voice agents that book directly into Epic. Cadence rules are intricate, and an agent that books the wrong visit type creates work for the front desk and frustration for the clinician. Insist on a staged rollout: confirmations and cancellations first, reschedules second, new bookings and registration last.

The third is pricing, which is on request. Our Assort Health pricing page sets out what buyers report, and the AI phone agent comparison puts Assort beside Hyro, Notable and the other voice vendors, several of which do publish Epic Showroom listings.

• Which method is used to read the schedule and write appointments on our Epic release, and is there a Showroom listing?
• Are bookings written directly to the book or to a work queue for staff confirmation, and can we choose per visit type?
• How many Epic sites are live, on which releases, and can we speak to one without the vendor present?
• How does the agent identify callers, and what is the measured misidentification rate?
• Where are call recordings and transcripts stored, for how long, and is any of it used to train shared models? Put it in the BAA.
• What is the price per call, per completed task or per month at our volume, the minimum term and the exit terms?

Our vendor HIPAA question list extends the compliance items.

When a vendor's Epic claim rests on a logo rather than a specification, the review is the diligence. We obtain the interface specification, check it against your Epic release and Cadence build with your analyst, confirm a live Epic reference, and compare the result against voice vendors with documented Epic listings. If Assort Health is the right product for your phone volume, the review will say so; if the Epic path is immature for your site, it will say that too. We take no vendor commissions.

Our vendor selection service runs that process, and an AI readiness audit tells you first whether your scheduling rules are clean enough for any agent to book against. Book a call with your call volumes and your Epic release.