Does Heidi Health Connect to athenahealth?

Through the Marketplace request process and then over athenaOne's interfaces for two operations: reading the schedule and writing note sections to an encounter. Heidi does not publish which athenaOne APIs it calls or with which scopes. The appointment sync implies read access to the schedule and patient demographics; the section push implies write access to encounter document sections. Ask for the scope list, because it tells you what Heidi can see beyond the two operations it describes.

Heidi's approach differs by platform. On eClinicalWorks it routes through a third party widget platform; on athenahealth it uses the Marketplace request and a direct connection. That is worth knowing if you run more than one EHR, and the Heidi eClinicalWorks page covers the other route.

The incumbent comparison is direct. An Ambient Notes model starts inside the encounter, is reviewed by athenahealth and is billed by athenahealth. Heidi starts in its own app, is set up by Heidi, and is billed by Heidi, with a free tier that Ambient Notes cannot match.

The clinician sees the day's synced appointments in Heidi, selects the patient, records the visit with consent, and reviews the draft in Heidi using the practice's templates. One click pushes the mapped sections into the corresponding athenaOne encounter, where the clinician reviews and signs in athenaOne. Heidi's templating is the feature clinicians cite most: notes can be structured to a specialty or an individual style, and the section linking means the structure survives the push.

What Heidi does not do in athenaOne, as far as its documentation shows: read prior problems, medications or results; create diagnoses; pend orders; or produce after visit communication inside athenaOne. Patient facing documents are generated in Heidi and handled from there. The ambient scribe use case page explains why the chart read and structured write are the dividing line between scribe tiers.

Heidi's registry entry on this site records a free tier plus paid Clinician, Practice and Enterprise tiers, with no dollar amounts on the public page in August 2026. The free tier is the reason many clinicians are already using Heidi with athenaOne before the practice has decided anything. Run the ROI calculator against a quoted paid tier rather than against the free one, because the free tier's limits will not survive a full clinic day.

The Marketplace request is submitted from your athenahealth account, which means a practice administrator is involved, and that is a good thing. It is the moment to sign a BAA with Heidi on behalf of the practice rather than leaving individual clinicians on individual terms. Heidi's registry entry records a BAA as standard.

The approvals are yours: confirm the scope list Heidi requests, sign the BAA, decide which clinicians are connected, and set the retention terms. Heidi is an Australian company with a United States operation; ask where United States patient audio, transcripts and notes are stored and processed and get the answer into the BAA. The HIPAA and AI page sets out the minimum terms, and the practice AI policy template covers how to bring clinicians already on the free tier under a practice agreement.

Consent is your job. Decide the recording consent script before the first synced appointment, and check the state AI law map for states that require written notice.

• No documented chart read. The draft is grounded in the conversation and the template, not the athenaOne record.
• No documented structured diagnoses or orders. Someone still updates the problem list and enters orders after the push.
• Manual setup. Two to three business days per Heidi, and a dependency on Heidi's team rather than a self serve authorisation.
• Scope list not published. Ask what Heidi can read beyond the schedule.
• No published dollar pricing. Tier names are public; amounts are not. Not published. Checked September 2026. The Heidi pricing page covers what is known and what to ask.
• Free tier sprawl. Clinicians can start on the free tier without the practice knowing, and the practice carries the compliance exposure.

Ask, in writing: which athenaOne scopes the integration requests; whether any clinical data is read before drafting; which sections are written and what happens when a section already contains text; whether diagnoses are matched to existing cards or left as text; how a failed push is surfaced; where United States data is stored and for how long; whether your recordings train shared models; the per clinician price for the Practice tier and what its limits are; and how notes and transcripts are returned at offboarding. The EHR integration question list is the full set.

Ask athenahealth to confirm there is no fee on its side for the Heidi connection, in writing, since Heidi's statement is not athenahealth's.

Then test it on ten real encounters, inspecting the athenaOne encounter after each push, alongside one Ambient Notes model on the same days. The scribe comparison sets out what to score, and the small practice buying guide covers when a lighter tool is the right answer.

Heidi is likely already in your practice on the free tier whether or not you have chosen it, and the question is whether to standardise on it, upgrade it, or replace it with an embedded Ambient Notes model that reads the chart. Clunic takes no vendor commissions. Our vendor selection engagement compares Heidi against the Ambient Notes models and the API integrated scribes on your own encounters and tells you where the extra integration depth is worth paying for. An AI readiness audit maps the unsanctioned use first. Book a call to start.