Does Dragon Copilot Work With eClinicalWorks?

On the browser and the desktop, not on eClinicalWorks' FHIR API. The web extension gives Dragon Copilot desktop awareness of the text fields in the open eCW page so that dictation lands at the cursor and section transfer can target the right field. The ambient drafting itself happens in Microsoft's cloud from audio captured by the desktop or mobile app. The clinician reviews the draft in Dragon Copilot, then transfers it, section by section or wholesale, into eClinicalWorks and signs there.

Some Microsoft resellers offer a middleware layer, marketed as Clinical Note Exchange, that they say improves the eCW connected workflow for Dragon Copilot. That is a reseller product, not a Microsoft one, and it should be evaluated and contracted as such.

The incumbent is Sunoh.ai, developed by healow, which eClinicalWorks positions explicitly against standalone scribes on the grounds that a deeply integrated one maps data into discrete fields without copy and paste. Dragon Copilot's section transfer is Microsoft's answer to that argument; it narrows the gap without closing it.

Two things. It types where the cursor is, with medical vocabulary and voice commands, which for many eCW practices already running Dragon Medical One is the continuity they want. And it produces an ambient draft in its own window that the clinician transfers into eCW by saying, for example, transfer assessment and plan. Microsoft's release notes list the section names and their spoken variants and note that the voice command works in the narrow and standard app views but not the compact one.

Beyond the note, Dragon Copilot's general feature set includes custom styles and prompts that reshape a draft, encounter summaries and, in embedded EHR deployments, order and referral drafting. Which of those are usable with eCW is not published beyond dictation and transfer. Not published. Checked September 2026. The ambient scribe use case page explains why the chart read and the structured write are the dividing lines between scribe tiers.

For the financial case, run the ROI calculator at the per user price your reseller quotes rather than at Microsoft's headline figures, and count the Dragon Medical One licences you would retire.

A desktop deployment. Someone installs Dragon Copilot desktop and the web extension on each clinician machine, manages users in the Dragon admin centre, and keeps both current. If you already run Dragon Medical One that is the same person; if you do not, it is a new operational task for a practice that may not have IT. Nothing needs to be authorised inside eClinicalWorks, because the connection is on your side of the screen.

Commercially, you sign with Microsoft or a reseller, accept Microsoft's healthcare product terms and BAA, and confirm data residency for audio and drafts. The HIPAA and AI page sets out the retention, training and subprocessor terms to confirm, and the vendor questions checklist gives you the form. Microsoft's terms are standardised, which is convenient and also means there is little to negotiate below enterprise scale.

Consent is your job. Decide the recording script before the first ambient encounter and check the state AI law map for states that require written notice.

• No documented chart read on eCW. The draft is grounded in the conversation, not the eClinicalWorks record.
• Transfer, not mapping. Sections are moved by voice command into the open field; the automatic field mapping Microsoft documents for Cerner MPages is not listed for eCW.
• Screen dependence. The web extension works on the rendered eCW page in the browser and can be affected by layout changes.
• Pricing not published. Microsoft and resellers quote per user, usually inside a wider agreement. The Dragon Copilot pricing page covers what to ask for.
• Reseller middleware is a separate product. Evaluate any Clinical Note Exchange style layer on its own contract and security terms.
• Enterprise sales motion. Microsoft's eCW route requires a sales engagement before hands on evaluation, which slows a small practice pilot.

Ask, in writing: which eClinicalWorks version and browser combinations are supported for dictation at the cursor and section transfer; whether any eCW chart data is read before drafting; which sections transfer and what happens when a field already contains text; whether the transfer can be triggered without voice for clinicians who prefer not to; the per user price and how existing Dragon Medical One licences convert; whether the reseller's implementation includes the extension rollout; where audio and drafts are stored and for how long; and whether your data trains shared models. The EHR integration question list is the full set.

Ask eClinicalWorks whether anything in your agreement constrains third party scribes, and what Sunoh.ai would cost you on the same terms.

Then trial Dragon Copilot against Sunoh.ai on the same real encounters and inspect the eCW note after each transfer. The scribe comparison sets out what to score.

Dragon Copilot on eClinicalWorks is sold through a channel with strong incentives to convert every Dragon Medical One seat, and eClinicalWorks has equally strong incentives to sell you Sunoh.ai. Neither has looked at your encounter mix or your appetite for a desktop deployment. Clunic takes no vendor commissions and no reseller relationship. Our vendor selection engagement runs both against your encounters, reads the licensing, and tells you which route and which terms to accept. For multi site groups, our deployment roadmap sequences the rollout. Book a call to start.