Integrating AI Agents with athenahealth

Four, and they differ mostly in who has done the work for you.

The row you are on determines almost everything else: who you call when it breaks, whose security review applies, and whether the agent can see the patient before it writes about them. We ask the same question on every platform, which is why the EHR integration pages share a shape.

It means the ambient scribe decision has partly been made for you, and it is worth understanding the shape of that.

athenahealth announced its partnership with Abridge in February 2025 and has since added others, so a clinician on athenaOne can select from several embedded ambient vendors rather than one. Microsoft's Dragon Copilot was announced for athenaOne in a collaboration disclosed in late 2025. Suki was named preferred solution partner for ambient intelligence in January 2026. athenahealth has reported that a large majority of athenaOne customers use at least one partner solution.

Three practical consequences. First, a single contract genuinely reduces your procurement and security work, and for a small group that saving is not trivial. Second, the pricing you see is athenahealth's, not the vendor's, so the usual comparison against a vendor's direct list price does not apply cleanly. Third, if the right product for your specialty is not in the set, connecting it is possible but you are doing it on ordinary Marketplace terms against curated competitors that are already inside the chart.

Test the output, not the arrangement. Run two of the embedded options against the same real encounters in your own specialty before committing, because the differences between them are larger than the marketing suggests. The scribe comparison sets out what those differences are.

You should care because it is the cheapest due diligence available to you.

The published process runs application, technical review of API usage and data handling, security review covering encryption, access controls and testing evidence, then publication. Ask a prospective vendor when they last went through it and what changed. A vendor that was reviewed three years ago and has since rebuilt its architecture on a new model provider has a listing that describes a product that no longer exists.

Ask also what athenahealth's review did not cover. Retention periods, subprocessor lists, model training on your data and breach notification timelines are contract questions, not certification questions, and the HIPAA and AI page lists what to insist on.

Less than on an enterprise platform, but not nothing, and the steps people skip are always the same ones.

• Name one owner. Even on a curated platform, someone has to make decisions about data and answer the vendor's questions.
• Authorise the application against your data. A listing is not an activation.
• Get the business associate agreement moving in parallel with the technical work.
• Decide which clinicians pilot it, and agree what a good note looks like before you start rather than after.
• Set a decision date. Practices that skip this do not fail, they drift.

We build this into a deployment roadmap because it is where ambulatory projects stall, and the stall is almost never technical.

Certified health IT has to publish its API documentation and terms, and the information blocking provisions constrain what a developer may do to obstruct access to electronic health information. On a curated platform this matters more, not less, because curation and obstruction can look similar from the outside.

The HTI-1 rule also brought transparency requirements for predictive decision support shipped inside certified software. If AI functionality is generating content inside athenaOne that influences care, those disclosures exist and you can ask for them.

If a vendor you want cannot get connected and the reason you are given does not survive a follow up question, that is the conversation to have, early and politely.

Ambient documentation, because the platform has removed most of the friction and because the failure mode is a draft a clinician corrects rather than a wrong action taken automatically.

The phone is second and often the bigger number. Scheduling and inbound call handling are high volume and low clinical risk, and athenahealth's proprietary APIs cover the practice management data those agents need in a way FHIR alone does not.

Revenue cycle work is third and travels well, particularly eligibility and authorization, where payer connectivity partners have long standing documented integrations. Prior authorization automation is the usual entry point.

Anything that orders, prescribes or acts without human review belongs later, and belongs in a governance conversation rather than a procurement one. If you want the money framing first, the ROI calculator shows its assumptions on the page.

It is worth knowing rather than worrying about. athenahealth has been privately held since Hellman and Friedman and Bain Capital completed a take private transaction valued at 17 billion US dollars, closing in early 2022. It is not a public company, so you will not find quarterly disclosure to read before you sign.

The practical implication is ordinary: on a bundled platform, the price of the AI is set by the platform and can move at renewal independently of the underlying vendor's own pricing. Ask what happens at renewal, ask what happens if athenahealth changes which vendors are embedded, and get the answer in the contract rather than in an email.

Start inside the curated set, because the procurement saving is real and the security work is already largely done. Run two options against real encounters, in your own specialty, with a date on which you will decide.

Only step outside the set when you have a specific reason: a specialty the embedded vendors handle badly, a workflow they do not cover, or a price you cannot make work. Then treat it as a genuine integration project rather than a subscription.

If you are also comparing platforms, NextGen and Veradigm answer the same first party question differently. Mapping that comparison for your own practice is what our vendor selection work is for.