Move your team from Microsoft Dragon Copilot to Epic.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Epic — 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 Epic both capture the visit ambiently and draft the clinical note. A practice on Epic can retire the standalone Dragon Copilot contract by turning the same workflow on inside the chart: enable Epic's in-app ambient documentation — DAX Copilot embedded in Epic (the Microsoft/Nuance ambient that became Dragon Copilot) or Epic's native 'Art' / AI Charting. Clinicians launch it from the EHR toolbar or the Actions menu in the Epic Notes activity, record the encounter via the Epic mobile apps (Haiku/Canto), and the draft writes straight into the encounter's SmartSections (HPI, Assessment & Plan, Physical Exam, Results) for sign-off — no separate Dragon Copilot login or paste-back. Keep Epic as the system of record; cut the standalone Dragon Copilot.
- Warning: Epic's ambient is a licensed add-on (DAX Copilot in Epic, or Epic's native ambient/Art) and partner ambient vendors may carry their own per-clinician fee — confirm it is enabled and provisioned for the clinicians before cancelling Dragon Copilot.
- Warning: Re-validate Dragon Copilot's specialty note templates against Epic's SmartSection/SmartPhrase layout; the section mapping and any custom formatting must be rebuilt on the Epic side.
- Warning: Patient consent for ambient recording still applies — keep the consent step in the Epic-app workflow.
- Warning: Output is a draft, not auto-filed: clinician review/sign-off in Epic is required before the note enters the record.
Dragon Copilot generates coding suggestions off the documented encounter; Epic does the same natively. A practice on Epic can stop relying on Dragon Copilot's coding output and use Epic's own revenue-cycle coding instead: Epic's Coding Assistance (under 'Penny', Epic's AI for the revenue cycle) tees up diagnosis and procedure codes from the clinical content of each visit, recommends Level of Service from the data entered during the visit, surfaces CDI query opportunities, and feeds the codes straight onto the same chart's claim in Resolute. Because it reads the very documentation it bills against, there is no export/round-trip. Keep Epic and its revenue-cycle license; cut the standalone Dragon Copilot, and let Penny/Coding Assistance carry the coding.
- Warning: Epic's AI coding (Penny / Coding Assistance) is part of the Epic revenue-cycle license/configuration — confirm Coding Assistance is enabled for the relevant departments before relying on it in place of Dragon Copilot.
- Warning: Re-validate any Dragon Copilot coding logic against Epic's NoteReader CDI / Coding Assistance output; do not assume code-for-code parity, and reconcile Level-of-Service rules.
- Warning: Autonomous ('no-touch') coding via Penny is rolling out starting with Emergency Department and Radiology — most encounter types still expect coder/clinician review, so keep a human in the loop during cutover.