Move your team from eClinicalWorks to Nabla.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Nabla — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in eClinicalWorks is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Nabla Copilot and eClinicalWorks' Sunoh.ai both listen to the patient-provider conversation ambiently and draft a structured progress note with orders and follow-ups for the clinician to review. A practice on eClinicalWorks running Nabla as a separate contract can move that workflow in-family: adopt Sunoh.ai, the ambient AI scribe natively wired into the eCW Progress Note, which transcribes the visit, sorts content into SOAP sections, and pre-fills coded/uncoded allergies, diagnoses, treatment plans, labs, imaging, medication orders and follow-ups — the provider then edits and imports directly into the eClinicalWorks Progress Note. Capture runs on the desktop EHR, eClinicalTouch (iPad) and eClinicalMobile rather than the Nabla app, and output lands in the same encounter eCW already uses for coding and billing instead of being pasted back. Keep eClinicalWorks, cut Nabla.
- Warning: Sunoh.ai is itself a paid add-on (listed at $149/user/month, with possible per-visit usage pricing) — this swaps one ambient subscription for another; the gain is native landing in the eCW Progress Note, not a cost elimination. Confirm Sunoh licensing before cancelling Nabla.
- Warning: Re-create Nabla's specialty templates (SOAP/APSO/WCC) in Sunoh/eCW; Sunoh categorizes into the eCW Progress Note structure, which differs from Nabla's note layout and needs clinician validation.
- Warning: Sunoh is marketed as EHR-agnostic but is most deeply integrated with eClinicalWorks — verify your eCW version and the Progress Note import flow are supported before switching.
- Warning: Reconcile or export any Nabla note history you must retain before the contract ends; Nabla retains no audio by default, so anything not already filed to eCW should be settled first.
Nabla surfaces real-time codes (ICD-10, HCC, MCC, with E/M and CDI nudges) alongside the note for clinician review. eClinicalWorks covers the same documenting-and-closing step natively through its Clinical Rules Engine (CRE): when documentation triggers a rule (a diagnosis, vital, or lab value in range), the CRE automatically drops the matching ICD-10/CPT code into the note and feeds it to the integrated charge/claim workflow, with the eva assistant available in-context. Because coding runs on the encounter the clinician already documented in eCW, the codes attach directly to the note, orders and billing record rather than being reconciled from a separate Nabla list. A practice can therefore retire Nabla's coding layer and rely on eCW's built-in CRE/E&M coding. Keep eClinicalWorks, cut Nabla.
- Warning: eCW's native coding is rules-based (CRE), not autonomous GenAI chart coding — its suggestion depth differs from Nabla's AI coding, so run a parallel period and validate CRE output before dropping Nabla; deeper AI coding on eCW is generally a separate third-party add-on.
- Warning: Confirm the Clinical Rules Engine is configured/enabled for your encounters (CRE is included at no cost on eCW version 12, but rules must be set up to fire) before relying on it in place of Nabla.
- Warning: If any downstream system consumed Nabla's FHIR-normalized ICD-10/LOINC export, re-point it to eCW's coded encounter/charge data; field shapes and code sets will not match Nabla's API one-to-one.