Move your team from Microsoft Dragon Copilot to eClinicalWorks.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in eClinicalWorks — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Microsoft Dragon Copilot is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Dragon Copilot and eClinicalWorks both capture the encounter ambiently and draft the note. A practice on eClinicalWorks can cut the standalone Dragon Copilot contract by switching the ambient workflow to Sunoh.ai, the AI scribe natively wired into the eCW Progress Note. Sunoh transcribes the visit, sorts the content into the SOAP/Progress Note sections, and pre-fills coded and uncoded diagnoses, allergies, treatment plans, plus labs/imaging/medication orders and follow-up details; the clinician reviews and imports straight into the Progress Note inside eClinicalWorks (desktop, eClinicalTouch iPad, or eClinicalMobile). No separate Dragon Copilot app or paste-back. Keep the eClinicalWorks EHR; cut the standalone Dragon Copilot.
- Warning: Sunoh.ai is a paid add-on to the deployed eCW license (publicly listed around $149/user/month, with possible additional monthly charges) — confirm seats are provisioned before cancelling Dragon Copilot.
- Warning: Re-validate Dragon Copilot's specialty note templates against Sunoh's Progress Note section mapping and rebuild any custom templates/fields on the eCW side.
- Warning: The clinician must review and import each draft into the Progress Note (and confirm captured orders) — output is a draft, not auto-filed.
- Warning: Patient consent for ambient recording still applies in the Sunoh/eCW workflow.
Dragon Copilot surfaces coding suggestions from the encounter; eClinicalWorks has native coding support built in. A practice on eClinicalWorks can drop Dragon Copilot's coding output and lean on the eCW Clinical Rules Engine (CRE), which automatically drops/suggests the appropriate codes based on the clinical documentation as encounters are completed and feeds them into the integrated charge/claim workflow in the same EHR (CRE reminders and alerts prompt correct coding on the first pass). Because CRE runs on the encounter the clinician already documented, the codes attach directly to the note and billing record with no separate tool or paste-back. Keep the eClinicalWorks EHR/PM license; cut the standalone Dragon Copilot and let CRE (plus the embedded eva assistant in-context) handle coding.
- Warning: eCW CRE is rules-based (drops codes from documentation triggers), not the same as Dragon Copilot's generative coding suggestions — re-validate E/M level and diagnosis logic, and expect to tune CRE rules so coverage matches what Dragon previously flagged.
- Warning: Fully autonomous GenAI chart coding on eClinicalWorks is largely supplied by third-party add-ons, not the built-in CRE — if the practice depended on Dragon Copilot for narrative/GenAI coding depth, confirm CRE (or an eCW-side add-on) meets that need before cancelling.
- Warning: Confirm CRE and the charge/claim workflow are configured for the practice's specialties and payer rules before relying on it in place of Dragon Copilot.