Does Nabla Integrate With athenahealth?

Through the athenahealth Marketplace programme, which requires an application, a technical review of API usage and data handling, a security review and a published listing. From there Nabla uses athenaOne's interfaces: the FHIR R4 API with OAuth 2.0 for standard clinical resources and the proprietary athenaOne APIs for the appointment schedule and the encounter document sections that FHIR does not address directly. The section level write back Nabla describes is an athenaOne API capability, not a browser paste, and that matters for reliability.

Nabla also sells Nabla Connect, an embeddable module that lets any EHR host Nabla inside an iFrame. That is aimed at EHR vendors rather than practices and is not the athenaOne route. If a reseller mentions Connect, ask which one you are being sold.

The incumbent is Ambient Notes. Nabla is competing from outside the encounter against Abridge, Suki, Microsoft Dragon Copilot and iScribe, which are already inside it under one athenahealth contract. Its counter is breadth: 35 languages, 55 specialties and a published individual plan.

The clinician opens the synced appointment in Nabla, records the visit with consent, and receives a structured draft in Nabla within seconds of the visit ending. On approval the content is sent to the matching athenaOne encounter, section by section, where the clinician reviews and signs in athenaOne. Nabla also produces patient instructions and, in its general product, coding suggestions across specialties; confirm whether the coding output is written to athenaOne or displayed only in Nabla.

Multilingual support is the practical differentiator for many ambulatory groups: Nabla lists 35 languages for the encounter and generates the note in the clinician's language. For federally qualified health centres and practices with large Spanish speaking panels, that is often the deciding feature, and the community health centre page covers what else to check.

For the financial case, run the ROI calculator with your own visit volume rather than borrowing Nabla's 24 percent figure. The ambient scribe use case page lists the write back questions that separate the products.

One more practical point for groups with several sites: Nabla's appointment sync is per athenaOne department and provider, so confirm at onboarding that every location's schedule is mapped, and decide who at the practice reconciles a note that Nabla could not match to an encounter. Small groups usually leave that to the clinician; larger ones give it to a medical assistant with a daily check, which is cheap and removes the most common source of missing notes.

You are the customer of record, so the approvals are yours. Your practice authorises the Nabla Marketplace app against your athenaOne data, signs a BAA directly with Nabla, assigns licences and owns the support relationship. The Marketplace review covered Nabla's API usage and security controls at the time of review. It did not cover retention periods, subprocessors, model training on your data or breach notification timelines, which are contract terms. The HIPAA and AI page sets out the minimum, and the vendor questions checklist gives you a form to send.

Nabla is a French company with a United States operation. Ask where audio, transcripts and notes for United States patients are stored and processed, and get the answer in the BAA rather than in an email. Nabla's registry entry on this site records a BAA as standard.

Name one owner and set a decision date. Nabla's onboarding is fast by design; the delays are usually the BAA and the question of which clinicians pilot it.

• Outside Ambient Notes. Separate contract, separate security review, and no in product switching between engines.
• Chart read depth depends on a roadmap. Nabla's early 2026 plan added reading of reason for visit, prior encounters and medications. Confirm what is live for your practice rather than what was announced.
• Organisation pricing is not published. Nabla publishes an individual clinician plan; group pricing is on request. The Nabla pricing page covers what is disclosed and what to ask.
• Structured diagnoses and orders are not documented for athenaOne. Not published. Checked September 2026.
• Appointment sync assumptions. Section level write back relies on the Nabla session matching the right athenaOne encounter. Ask how mismatches are prevented and surfaced.

Ask, in writing: which athenaOne interfaces and scopes the app uses; which chart data is read before drafting and whether that is live today; which sections are written and what happens when a section already contains text; whether diagnoses land as structured entries; how a failed or mismatched write is surfaced; where United States data is stored and for how long; whether your encounters train shared models; the organisation price per clinician; and the offboarding process including return of transcripts. The EHR integration question list is the full set.

Ask athenahealth whether the Nabla listing has been re reviewed since 2024 and whether anything about the integration has changed.

Then trial Nabla against one Ambient Notes model on the same real encounters, in your specialty and your languages. The scribe comparison sets out what to score.

Nabla's published detail is better than most, but it is still the vendor's account, and the embedded Ambient Notes options have a procurement advantage that has nothing to do with note quality. Clunic takes no vendor commissions. Our vendor selection engagement runs Nabla and the Ambient Notes models against your encounters, checks the roadmap claims against what is actually live, and tells you which to choose and what to negotiate. If you already know it is Nabla, an AI readiness audit checks consent, retention and governance before recordings start. Book a call to start.