Does Freed Push Notes Into athenahealth?

On the browser, not on athenaOne's APIs. The Chrome extension identifies the fields in the open athenaOne encounter and inserts text into them. Freed's general EHR Push documentation says it appends to existing text by default and can be set to prepend, and that unmatched diagnoses are placed in the A&P summary rather than created as new problems. Because the extension works on the rendered page, it only works in browser based athenaOne in Chrome, and a change to athenaOne's screen layout can break the mapping until Freed updates the extension. Freed maintains a separate troubleshooting article for athena for exactly that reason.

For a solo clinician or a small practice without IT, this trade is often correct. There is nothing to authorise, nobody to raise a ticket with, and the note ends up in the right fields most of the time. For a group, the lack of a chart read and the dependence on the screen are real costs. The small practice buying guide covers when the lighter tools are the right answer.

It places text. The clinician records the visit in the Freed web app with consent, reviews the SOAP formatted draft in Freed, opens the athenaOne encounter on the HPI tab, and clicks Push. The extension fills HPI, ROS, physical exam, the A&P summary or matched diagnosis cards, and patient instructions. The clinician then reviews and signs in athenaOne as normal.

What Freed does not do in athenaOne: read the problem list or medication list, pend orders, create diagnoses, or generate an after visit summary in athenaOne's patient communication tools. Freed produces patient instructions in its own app and pushes them to the field; anything beyond that is manual. The ambient scribe use case page explains why the chart read and the structured write are what separate a scribe that saves typing from one that saves the clicks after typing.

Freed's registry entry on this site records published individual plans from 39 to 119 US dollars per month, checked in August 2026, with the Premier plan enabling unlimited EHR Push and lower tiers capped. Group pricing is on request. That transparency is rare in this category and is the reason many clinicians start here; run the ROI calculator at the Premier price against your visit volume.

Technically, almost nothing: install a Chrome extension and sign in. That is the appeal, and it is also the risk. Because there is no app authorisation in athenaOne, there is no scope list and no athenahealth review of what the extension touches. A clinician can adopt Freed without the practice knowing, which means audio recordings of your patients are being processed by a vendor with whom the practice may have no BAA.

Freed's registry entry records a BAA as standard, and Freed offers one to individual subscribers. Make sure the practice, not just the clinician, is party to it. The HIPAA and AI page sets out the retention, training and subprocessor terms to confirm, and the practice AI policy template covers how to stop unsanctioned scribe use without banning the useful kind.

Browser extension hygiene is also yours. Extensions run with access to whatever page is open, so the practice should decide which extensions are allowed on machines that display athenaOne and review them periodically.

• No chart read. The draft is grounded in the conversation only. Prior problems, medications and results are not in front of the model.
• No new diagnoses. Unmatched diagnoses go to the A&P summary as text; someone still has to add them to the problem list.
• Screen dependence. The push works from the HPI tab in browser based athenaOne in Chrome, in the same profile as the Freed login, and can break when the layout changes.
• Silent partial pushes. Freed's own guidance warns about clicking other tabs mid transfer. Ask what the clinician sees when a field fails to fill.
• Marketplace status unverified. Freed says it is listed; we could not confirm it in September 2026. Either way the mechanism is the extension.
• Group terms not published. The Freed pricing page covers the published individual tiers and what to ask for at group scale.

Ask, in writing: whether the practice can be the BAA counterparty for all its clinicians; where audio, transcripts and notes are stored and for how long; whether recordings train shared models; what the extension can access on pages other than the encounter; how a failed or partial push is surfaced; what the group price is and whether EHR Push is included; and how notes are exported at offboarding. The vendor questions checklist gives you the form.

Ask yourself whether the missing chart read matters for your specialty. In a low complexity, high volume clinic it often does not. In a practice managing many chronic conditions per visit it usually does, and an Ambient Notes model or an API integrated scribe such as Nabla is the fairer comparison.

Then test it on ten real encounters and inspect the athenaOne encounter after each push, not the Freed screen. The scribe comparison sets out what to score.

Freed is the honest budget option on athenaOne, and the question is not whether it works but whether the trade it makes is the right one for your practice, and whether the clinicians already using it have put the practice at compliance risk. Clunic takes no vendor commissions. Our vendor selection engagement compares Freed against the Ambient Notes models and the API integrated scribes on your own encounters and tells you where the extra cost buys something real. An AI readiness audit finds the unsanctioned scribe use first. Book a call to start.