Can an AI scribe work with athenaPractice, the athenahealth EHR that was GE's Centricity Practice Solution? Yes, inside one boundary: DeepCura's athenaPractice connection reads your schedule and your patients, and writes nothing back. Your athenaPractice appointments appear on DeepCura's schedule, refreshed about every 15 minutes; Start visit checks the patient against athenaPractice before any chart opens; the AI scribe writes the note to your own template; and the note goes into athenaPractice as notes do today: pasted. Where you stand decides the rest:
- On athenaPractice, in your office or with a hosting partner: this guide. Your IT team and DeepCura support set the connection up; here is the list.
- On athenaOne: a different DeepCura connection, which writes the note, diagnoses, orders and charges back. See the athenaOne guide.
- On athenaFlow (formerly Centricity EMR): not verified yet. Ask DeepCura support before you plan on it.
- Moving to athenaOne anyway: athenaAmbient comes with it, compared below.
- Need diagnoses, orders or charges filed into athenaPractice by the scribe: no scribe we could verify does that on athenaPractice today, DeepCura included.
DeepCura publishes this guide and is one of the tools discussed. DeepCura's athenaPractice behaviour is described from the product's code and its test suite. Other vendors are described only from their own public pages, on the dates in the references, and are recommended where they fit better. There are no screenshots: we have no capture of the athenaPractice screens yet, and a mock-up would be worse than none. No independent clinician reviewed this page.
In that box, "athenahealth" means athenaOne. athenaPractice is not on the write-back list, for the reasons below.
Which athena you run decides what connects
athenahealth's EHRs come from two families, and the names are easy to mix up:
- athenaOne is athenahealth's cloud EHR. DeepCura reaches it through athenahealth's cloud APIs, with access granted on the athenahealth Marketplace, and writes back into it.
- athenaPractice is the former Centricity Practice Solution, and athenaFlow the former Centricity EMR, both renamed by early 2020 [2][3]. athenaPractice runs on the practice's own servers or with a hosting partner, and, like athenaFlow, it can run athenahealth's API Server: a FHIR R4 interface that runs alongside the EHR [1].
So the athenaOne connection cannot simply be pointed at athenaPractice: an athenaPractice API Server answers only what the practice opens to it, under a login the practice creates. DeepCura's athenaPractice connection is separate software, built for that server.
One requirement sits on athenahealth's side: in the API Server, appointments and patients are practice-management resources, available when athenaPractice is configured with its practice-management license [1]. A practice that schedules in another system has no athenaPractice appointments for this connection to read.
What DeepCura reads from athenaPractice, and what it never writes
The connection signs in to your API Server with one practice-wide login. Its client has exactly one call that sends anything, the sign-in; every other call is a read. This is all of it:
| What DeepCura reads | When | What it does with it |
|---|---|---|
| The practitioner list | When the owner connects, then once a day | Shows the active practitioners by name, so the owner can match each one to a team member |
| Appointments of the practitioners the owner matched | About every 15 minutes, from yesterday through up to 60 days ahead | Keeps each visit's time, length, visit type, location, provider and status. The appointment's reason, description and comments are dropped on read and stored nowhere |
| The patient's record, and the visit again | To name a visit; at Start visit | Confirms the visit still names that patient and is not cancelled, then uses the name, date of birth, medical record number, phone and email to find or make the chart. Any Social Security number athenaPractice lists as an identifier is dropped on read, never stored or logged |
What it never does:
- Write. No note, problem, order, medication, allergy or charge goes into athenaPractice, nothing is signed, and no athenaPractice appointment is booked, moved or cancelled from DeepCura. Cancel or move a visit in athenaPractice; DeepCura's copy follows at the next sync.
- Show the scribe your athenaPractice chart. The scribe does not see athenaPractice's problem lists, medications, allergies, results or earlier notes; it writes from the visit and from what is already on the patient's DeepCura chart.
Your athenaPractice schedule on DeepCura's calendar
DeepCura's servers collect the schedule; your browser never talks to athenaPractice. About every 15 minutes a sync asks athenaPractice for each matched practitioner's visits and writes them into that practitioner's lane on DeepCura's calendar. Nobody else's visits are asked for. New visits appear, moved ones move, cancellations and no-shows follow, and past visits stay as history.
The calendar says how current it is: first sync pending right after connecting (the schedule appears within about 15 minutes), the time of the last update when a sync is late, needs attention when athenaPractice refused the practice's sign-in, and a "shown from" date, because days before it may be missing visits and, in the product's words, "an empty day there is not a free day."
Visit times are filed in the time zone on the practice owner's DeepCura account, and it must be one the practice set or confirmed: a zone a web browser guessed at first login is refused, since a wrong one would put every visit hours off. DeepCura support confirms a right one with you; the Setup Assistant in Settings → Scheduling corrects a wrong one.
Start visit: the patient is checked against athenaPractice at the click
Every athenaPractice visit on the calendar carries Start visit. Before a chart opens, DeepCura reads the visit and the patient's record from athenaPractice again. If the visit now names a different patient, nothing opens and you are asked to start it again from the schedule; if athenaPractice lists it as cancelled, or the record holds no current name, it cannot be started. Then DeepCura finds the patient's one chart in your practice, or makes it:
- Seen before through athenaPractice: the same chart, whoever starts the visit.
- A strong match (athenaPractice's medical record number on a chart, or a phone number or email with the date of birth and the same name): the chart opens with a notice of what matched, telling you to "check it is the same person before charting. If it is not, do not chart there: contact DeepCura support." There is no one-click Not the same person? for athenaPractice yet.
- Name and date of birth only: never linked on their own. You are asked "Is this the same patient?", can open each candidate chart, and choose Same patient or New patient - make a new chart.
- No match: a new chart in the patient's athenaPractice name, under the visit's provider.
A read-only team member sees the visit but cannot start it. Start visit costs no credits.
After the visit, the note is pasted into athenaPractice
The note follows a template built for your account, not one picked from a fixed library: Emily, the onboarding agent, drafts it on the setup call, Talk to Template or Start from Sample Note build one from a description or a de-identified note, and the Network Template Gallery holds templates clinicians chose to share. The coding step suggests ICD-10, CPT and E&M codes for you to enter, and coded facts from the conversation arrive in Ambient Data Review as suggestions, each with the words it came from; nothing enters the DeepCura chart until you approve it.
Then you copy the note into the athenaPractice visit and sign it there; diagnoses, orders, prescriptions and charges are entered in athenaPractice as today. On athenaOne or Veradigm EHR, DeepCura files many of those items itself; on athenaPractice it does not. What the connection saves is the schedule, the right chart and the note, not the clicks after it.
What your IT team sets up, and what DeepCura support does
An athenaPractice connection is a small IT project, not a self-serve toggle. Until DeepCura support has set your practice up, the athenaPractice card does not appear in Settings at all.
| Step | Who | What it involves |
|---|---|---|
| 1. The API Server | Your IT team or hosting partner | athenaPractice's FHIR R4 API Server running, as athenahealth's API Server guide describes, with athenaPractice licensed for practice management [1] |
| 2. A network path | Your IT team | DeepCura's servers reach the API Server at a stable IP address, on its HTTPS port. Open that port to DeepCura's fixed server addresses only; support gives you the list. DeepCura connects by address, not by host name |
| 3. The certificate | Your IT team, with support | The server's certificate must chain to athenahealth's own root certificate; you confirm its SHA-256 fingerprint with support, who pins it. When you renew the certificate, send the new fingerprint first: until it matches, DeepCura sends nothing |
| 4. DeepCura's application | Your athenaPractice administrator | Authorize DeepCura's registered application on your API Server |
| 5. The API user | Your athenaPractice administrator | One dedicated user for DeepCura, enabled for API access, with view rights to scheduling, patients and the practitioner list: the rights the connection uses |
| 6. The settings | DeepCura support | Stores the server's address, port, database name and fingerprint, and the API user's password: entered by support, stored encrypted, never shown on a screen. Confirms the practice's time zone with you |
| 7. Connect | The practice owner | Settings → Integrations → Connect athenaPractice. DeepCura checks the server and the login before it saves anything |
| 8. The team | The practice owner | On the Team Members page: who is on the practice's schedule, and which team member each athenaPractice practitioner is |
Two things to plan for. Directory accounts lock after failed sign-ins, so DeepCura never retries a refused one: the connection shows Needs attention, and the fix goes through DeepCura support. And a new API user or server address means the owner connects again after support updates the settings; a changed password or a renewed certificate needs only the settings update.
One practice login, held by the owner
athenaPractice gives DeepCura one login for the whole practice. Only the workspace owner connects, reconnects or disconnects it, and the owner's Settings card says it plainly: "there is nothing to type here." Nobody else holds an athenaPractice login in DeepCura.
On the Team Members page the owner switches each team member onto the practice's schedule or off it, and matches each athenaPractice practitioner to a team member. Only matched practitioners' visits are read. Take a practitioner or their team member off, and their upcoming visits leave DeepCura's calendar within minutes; they return when matched again. Who sees which visits follows the practice's Team visibility for EHR schedules setting: Shared, or Separated by department. A team member whose own profile is connected to another EHR keeps seeing that schedule until they disconnect it.
Disconnect hides the practice's schedule from every team member at once and removes its upcoming visits from DeepCura; the team list stays, and connecting again brings the schedule back.
What an athenaPractice clinic day costs in credits
$129 per provider per month buys 1,000 credits a month across every AI agent; there is no unlimited tier. The athenaPractice connection itself costs nothing: the schedule sync and Start visit spend no credits, and there is no push to pay for. A visit spends credits on the note (1 credit on a standard model, 3 on premium models, 15 on the deepest tier) and on recording (0.1 credit at the start and 0.1 per three-minute auto-save).
| Visit | Standard model | Premium model |
|---|---|---|
| 15-minute follow-up | ≈ 1.6 credits (1 note + 0.1 start + ~5 auto-saves) | ≈ 3.6 |
| 40-minute new patient | ≈ 2.4 credits (1 + 0.1 + ~13 auto-saves) | ≈ 4.4 |
| Schedule sync and Start visit | 0 | 0 |
Eighteen visits a day, fourteen follow-ups and four new patients, come to 14 × 1.6 + 4 × 2.4 = 32 credits; over 20 clinic days that is about 640 credits a month, inside 1,000. A premium model on every note adds about 720 a month and takes you past it, which is what the $59/month add-on (raises the allotment from 1,000 to 2,000 credits) is for. Annual billing is $999 per provider; seats cost $116 each at 3–5, $110 at 6–10 and $101 at 11+; the free trial includes credits and needs no card (plans page).
Which AI scribe fits which athenaPractice practice
How we judged. Weighted for an athenaPractice practice: works with an on-premises athenaPractice through athenahealth's API rather than screen automation (20%) · the right patient bound to the visit (20%) · the athenaPractice schedule inside the scribe (15%) · how much retyping is left after the note (20%) · IT setup effort (10%) · a published price and the cost per visit (15%). DeepCura is judged from its code and tests, other vendors from their own public pages on the dates in the references. No head-to-head trial was run, so this is a fit table, not a score.
| Practice situation | Strongest fit | Why | Trade-off |
|---|---|---|---|
| Wants the athenaPractice schedule, the right chart at each visit and a note built to its own template, and can do the IT setup | DeepCura | Schedule synced about every 15 minutes; Start visit checks the patient against athenaPractice; template-built note; phones and inbox in the same account | Nothing written back: the note is pasted. An IT project. A new connection (November 2026). Credits, not an uncapped allowance |
| Moving to athenaOne anyway | athenaAmbient [4] | athenahealth's own ambient scribe, built into athenaOne at no extra charge | An athenaOne feature: the announcements we found do not mention athenaPractice. A migration is a project of its own |
| Wants an ambient note with no IT project, and will paste it | Freed AI [5] | Least setup: nothing touches your server | Its push is an extension for browser-based EHRs, and its athena page covers athenaOne. No athenaPractice schedule or patient link |
| Wants a free tier first, or dictation into athenaPractice's own screens | Heidi Health [6] | A free tier; a desktop app that, in Heidi's words, "goes where the browser can't" and lets you "dictate anywhere on your screen" | Its integrations page names athena, not athenaPractice. Paste the note |
| Wants AI notes with human review, from a vendor that lists Centricity | ScribeRyte by ScribeEMR [7] | Lists "Centricity / GE Healthcare" among the EMRs it serves; AI-only or AI plus human review | No published price; its page does not say how notes reach a Centricity chart. Ask before you buy |
| Needs diagnoses, orders or charges filed into athenaPractice by the scribe | None we could verify (2026-11-17) | No vendor above states it for athenaPractice | Keep entering them in athenaPractice, or look at athenaOne, where DeepCura files them |
| Tool | Plans | Monthly | Included / limits | Verified |
|---|---|---|---|---|
| DeepCura | All AI agents, per provider | $129 ($83.25 billed annually) | 1,000 credits/mo; 1 credit per standard note; +$59/mo add-on raises it to 2,000; seat tiers from $101 | 2026-08-17 |
| athenaAmbient (athenaOne) | Included for athenaOne customers | Free | native ambient notes inside athenaOne; generally available since August 2026, no added fee | 2026-11-17 |
| Freed AI | Starter · Core · Premier | $39 · $79 · $119 ($104 billed annually) | 40 notes/mo · unlimited notes · EHR push + ICD-10/CPT; 7-day trial | 2026-09-27 |
| Heidi Health | Free · Clinician | Free · $150 ($110 billed annually) | unlimited transcription + standard templates; advanced features gated · per user; 14-day free trial; custom templates | 2026-09-27 |
Vendor prices verified on the dates shown (earliest 2026-08-17); vendors change plans — confirm with each vendor before buying. DeepCura row: current plan; competitor rows: publicly published prices.
ScribeRyte publishes no price, so it is not in the table. In depth: the Heidi Health review and the Freed AI review.
Where DeepCura is not the right pick: a practice that needs the scribe to file structured data into athenaPractice; one whose IT cannot open the API Server to an outside service, or whose server certificate does not chain to athenahealth's root; an athenaFlow practice, until support has verified athenaFlow; a practice whose real problem is the clicks after the note. DeepCura's own limits, plainly: credits rather than an uncapped allowance, templates built rather than picked from a list, no one-click undo for a wrong chart match on athenaPractice yet, and a connection that is new, with a shorter track record than the athenaOne or eClinicalWorks integrations. For the wider field, see the AI scribe comparison.
Beyond the note: phones and inbox beside an athenaPractice schedule
DeepCura calls itself an Electronic Health Workforce: AI staff working around the EHR, not only a scribe. Connecting athenaPractice leaves the AI voice features on. Two of them matter here:
- The AI receptionist answers calls on the practice's DeepCura number. An appointment it books goes on DeepCura's calendar, not into athenaPractice, so someone enters it there. When DeepCura books, by staff or by voice, it treats each matched provider's athenaPractice visits as busy time, and if it cannot read them it offers no time at all rather than guess. It cannot cancel or move an athenaPractice visit; for a cancellation it offers to take a message for your staff. More in the AI receptionist guide.
- The AI inbox for fax, email and SMS proposes each action, such as filing a fax to a chart or drafting a reply, and does nothing until you confirm.
Talk to Emily, DeepCura's onboarding agent
She builds your template on the call; DeepCura support sets up athenaPractice with your IT team. $129/mo · 1,000 credits/mo · free trial, no card.
+1 (415) 549-1829Available 24/7 · Set up in seconds · No credit card required
Security of a connection into your own server
Every customer is covered by a Business Associate Agreement; PHI is encrypted in transit and at rest; customer data is not used to train models. For athenaPractice specifically:
- The server is proven first: before a byte is sent, its certificate must chain to athenahealth's root and match the fingerprint you confirmed; a mismatch sends nothing.
- The login stays with support: the API user's password is entered by DeepCura support, stored encrypted, and never shown or typed on a DeepCura screen.
- Less is kept: appointment comments and any Social Security number are dropped on read, and the client that talks to your server logs only an operation, a status and a time, never an address, an ID or a record's content.
- Recordings stay in your account and can be removed; recording consent follows your state's law.
Frequently Asked Questions
Does DeepCura work with athenaPractice?
Yes, since November 2026, through athenaPractice's FHIR R4 API Server and one practice-wide login that DeepCura support sets up with your IT team. It reads your schedule about every 15 minutes and checks the patient against athenaPractice at Start visit. It writes nothing back: you paste the note in.
What is the difference between athenaPractice and athenaOne?
athenaOne is athenahealth's cloud EHR; athenaPractice, formerly Centricity Practice Solution, runs on the practice's own servers or with a hosting partner. DeepCura's athenaOne connection writes notes, diagnoses, orders and charges back; its athenaPractice connection reads the schedule and patients and writes nothing.
Is Centricity EMR the same as athenaPractice?
No. Centricity EMR is now athenaFlow, and Centricity Practice Solution is now athenaPractice; both were renamed by early 2020. DeepCura's connection was built and tested for athenaPractice; athenaFlow has not been verified yet, so ask support before you plan on it.
Does DeepCura write notes back into athenaPractice?
No. The connection only reads; the one call it sends is its sign-in. You paste the note into the athenaPractice visit and sign it there, and enter diagnoses, orders, prescriptions and charges in athenaPractice as before.
What does our IT team need to set up?
athenaPractice's FHIR R4 API Server, licensed for practice management; a stable IP address with its HTTPS port open to DeepCura's fixed server addresses; the certificate's SHA-256 fingerprint, confirmed with support; DeepCura's application authorized; and one API user with view rights to scheduling, patients and practitioners. If your server is hosted, your hosting partner does the network part.
Is athenaAmbient available on athenaPractice?
athenahealth describes athenaAmbient as built into athenaOne at no extra charge; the announcements we found do not mention athenaPractice (checked November 17, 2026). It comes with a move to athenaOne; for athenaPractice, ask athenahealth.
How much does DeepCura cost for an athenaPractice practice?
$129 per provider per month, or $999 a year, with 1,000 credits a month. The connection spends no credits; a standard note costs 1 credit plus 0.1 per recording start and per three-minute auto-save, about 1.6 for a 15-minute follow-up. A $59 add-on raises the allotment to 2,000.
Is the connection secure?
Yes: a Business Associate Agreement with every customer, encryption in transit and at rest, and no model training on customer data. DeepCura checks your server's certificate before it sends anything, keeps the API user's password encrypted and off every screen, and drops appointment comments and any Social Security number on read.
References
[1] athenahealth, FHIR R4 API documentation for the API Server in athenaPractice and athenaFlow, "Supported APIs" (docs.mydata.athenahealth.com/fhir-r4) — accessed 2026-11-17.
[2] athenahealth, apiserver-athenaFlex repository on GitHub: README ("athenaPractice and athenaFlow FHIR API Developer Support Forum") and wiki (2018: "Centricity Practice Solution and Centricity EMR FHIR API Developer Support", with GE's FHIR documentation) (github.com/athenahealth/apiserver-athenaFlex) — accessed 2026-11-17.
[3] InteliChart, "InteliChart Recognized as Certified athenahealth Partner" (March 5, 2020): "athenaFlow™ was formerly known as Centricity EMR. athenaPractice™ was formerly known as Centricity Practice Solutions." (intelichart.com) — accessed 2026-11-17.
[4] HIT Consultant, "How athenaOne's Native Ambient AI Saves Two Workdays Monthly Per Clinician" (August 13, 2026). hitconsultant.net — accessed 2026-11-17.
[5] Freed AI, "Athena AI Scribe" (getfreed.ai/resources/athenahealth-ai-scribe) — accessed 2026-11-17.
[6] Heidi Health, integrations page (heidihealth.com/integrations) — accessed 2026-11-17.
[7] ScribeEMR, "EMRs We Serve" (scribeemr.com/emrs-we-serve) — accessed 2026-11-17.
[8] DeepCura, "Plans & Pricing" and Trust Center. deepcura.com/plans-pricing · trust.deepcura.com