Dictation and Speech Recognition Blog
Dragon Medical One vs. Dragon Copilot: Migration Status Report (Through 3.6.1, 2026)
Ten releases. Eighteen months. Where the real gap stands today. If your organization runs Dragon Medical One — and roughly 600,000 clinicians worldwide do — you have spent the last eighteen months hearing two contradictory stories. Story one: Dragon Medical One is the gold standard, battle-tested, deeply EHR-integrated, the dictation engine doctors actually trust. Story two: Microsoft is consolidating everything into Dragon Copilot, and DMO is the past. Both are true. Neither is the whole picture.
Here is the picture: Dragon Copilot has spent ten releases methodically closing the gap between itself and Dragon Medical One. Each release retired another reason a DMO administrator could legitimately say “not yet.” As of version 3.6.1 (May 2026), the remaining reasons are countable on one hand — and most of them have public roadmap signals.
This report is the migration status, version by version, gap by gap, sourced directly from Microsoft Learn’s release notes. It is updated each release.
The Short Answer
Is Dragon Copilot ready to replace Dragon Medical One? For most physician workflows in the United States, Canada, the United Kingdom, and Ireland: yes, with planning. The releases between 3.4.0 and 3.6.1 closed the substantive functional gaps — full text control across major EHRs, formatting parity, protected sections in Epic, PowerMic and mobile mic workflow triggers, Epic single sign-on. What remains are coverage gaps (specific M365 versions of Word, certain non-US regional configurations, Nuance-provisioned customers waiting on a few features Microsoft-provisioned customers already have), not architectural ones. For organizations not yet migrated to Dragon Admin Center, the migration is now a when question, not an if question.
What Changed Between January and May 2026
In the first five months of 2026, Microsoft shipped five Dragon Copilot releases:
- 3.4.3 (January 2026) — Nursing experience GA, Epic Rover enhancements
- 3.5.0 (January 2026) — Customizable templates, multi-intent prompts, full text control expansion, DMO formatting auto-applied
- 3.5.1 (February 2026) — The DMO migration release
- 3.6.0 (April 2026) — Multilingual, clinical letters, diagnosis-aware notes, nursing mobile preview, 120-minute ambient
- 3.6.1 (May 2026) — Epic SSO via SMART on FHIR, Information Assist governance, analytics consolidation
That is a release roughly every five weeks. Most enterprise software ships annually. The pattern across all five releases is the same: each one absorbs another piece of Dragon Medical One into Dragon Copilot, then adds something DMO never had. That dual motion is what makes this migration different from typical product retirement.
The Migration Scorecard
Below is the parity scorecard as of Dragon Copilot 3.6.1. Every “Yes” traces to a Microsoft Learn release-notes page; the version listed is the release that delivered the capability.
Dictation & Speech Recognition
| Capability | DMO | Dragon Copilot | Closed In |
|---|---|---|---|
| Cloud-based medical speech recognition | Yes | Yes | Foundation |
| Specialized medical vocabularies | Yes | Yes | 3.x baseline |
| PowerMic support | Yes | Yes | 3.x baseline |
| User-customizable vocabulary with audio training | Yes | Yes | 3.5.1 |
| Formatting preferences (capitalization, spacing, punctuation, numbers) | Yes | Yes — auto-migrated from DMO | 3.5.0 / 3.5.1 |
| User-visible formatting customization post-migration | Yes | Yes | 3.6.0 |
| Specialty-specific AI models (Home Health, Triage, ED, etc.) | Partial | Yes — ongoing model refresh | 3.5.1 (US/CA) |
EHR Integration & Full Text Control
| Capability | DMO | Dragon Copilot | Closed In |
|---|---|---|---|
| Epic Hyperdrive desktop dictation | Yes | Yes | 3.3.0 |
| eClinicalWorks (eCW) support | Yes | Yes | 3.2.0 |
| Intersystems Trakcare support | Yes | Yes | 3.2.0 |
| Allscripts full text control | Yes | Yes | 3.5.0 |
| Altera full text control | Yes | Yes | 3.5.0 |
| Altera Sunrise full text control | Yes | Yes | 3.5.1 |
| Cerner full text control | Yes | Yes | 3.5.0 |
| i.s.h.med full text control | Yes | Yes | 3.5.0 |
| Softway full text control | Yes | Yes | 3.5.0 |
| Microsoft Word (M365 desktop and non-M365) | Yes | Yes | 3.6.0 |
| Microsoft Outlook (non-M365) | Yes | Yes | 3.6.0 |
| Additional M365 versions (Word/Outlook) | Yes | In progress | 3.6.0 — “on the way” |
| Protected/read-only section detection (Epic) | Yes | Yes | 3.5.1 |
| Cerner MPages Smart Transfer (HPI, ROS, A&P, Physical Exam) | — | Yes | 3.2.0 |
| Self-service custom EHR edit control mapping | — | Yes | 3.6.1 |
| Epic single sign-on (SMART on FHIR) | Yes | Yes — Microsoft-provisioned at launch | 3.6.1 |
Workflows & Productivity
| Capability | DMO | Dragon Copilot | Closed In |
|---|---|---|---|
| Step-by-step / workflow commands | Yes | Yes — “Workflows” | 3.3.0 |
| Multi-step automation in workflows | Simpler step commands | Yes — multi-step | 3.3.0 |
| Keyboard shortcut workflow steps (Enter, Shift, etc.) | Yes | Yes | 3.5.0 |
| Voice command workflow steps (anchor, release, show anchored) | Yes | Yes | 3.5.0 |
| PowerMic button workflow triggers | Yes | Yes | 3.5.1 |
| PowerMic Mobile button workflow triggers | Yes | Yes | 3.6.0 |
| Keyboard shortcut workflow triggers | Yes | Yes | 3.5.1 |
| Global keyboard shortcuts | Yes | Yes | 3.2.0 |
| Customizable templates | Partial | Yes — multi-template, transcript-aware, 8,000-char | 3.3.0 / 3.5.0 |
Beyond Dragon Medical One
These are capabilities that Dragon Copilot has and Dragon Medical One does not. The list keeps growing.
| Capability | Dragon Copilot | Introduced |
|---|---|---|
| Ambient encounter capture and AI-generated note drafts | Yes | DAX lineage, integrated 3.x |
| Note Assist (multi-document generation, 10K-character prompts) | Yes | 3.3.0 |
| Information Assist with provenance and citations | Yes | 3.3.0 |
| DailyMed clinical reference (US) | Yes | 3.4.0 |
| Cross-client session management (web ↔ desktop ↔ embedded) | Yes | 3.4.0 |
| 120-minute ambient recording per session | Yes | 3.6.0 |
| Multilingual ambient (58 spoken languages → English notes) | Yes — US/CA | 3.6.0 |
| Auto-generated clinical letters (consultation, patient, referral) | Yes | 3.6.0 |
| Diagnosis-aware ambient notes pushed to Epic | Yes — Epic Nebula required | 3.6.0 |
| Multi-intent compound prompts in Chat | Yes — default-on | 3.5.0 / 3.6.1 |
| Epic FHIR API activation (7 new R4 endpoints) | Yes | 3.6.0 |
| Nursing experience (web, desktop, embedded, mobile preview) | Yes — GA | 3.4.3 / 3.6.0 |
| EHR-bound user identity verification | Yes | 3.5.0 |
| Information Assist governance in Dragon Admin Center | Yes | 3.6.1 |
| Mobile microphone (turn phone into the dictation mic) | Yes | 3.3.0 |
The “beyond DMO” column is roughly twice as long as the “remaining gaps” column. That ratio inverts the migration question. Dragon Copilot is no longer “DMO’s successor” in a defensive sense — it is a meaningfully different product class that happens to include DMO’s capabilities as a subset.
The Release-by-Release Migration Story
3.4.0 (November 2025) — Cross-Client Glue
3.4.0’s headline was cross-client session management — start a session on web, finish on desktop, edit on mobile. DMO never had this because DMO is a single Windows desktop client. This release also added DailyMed as a clinical reference source and Information Assist citation improvements.
For DMO admins: the embedded floating ambient recording window inside Dragon Copilot for Epic landed here. If your physicians live in Hyperdrive, this was the “ambient feels native to Epic” moment.
3.4.2 (December 2025) — Pronoun & Scope Cleanup
A minor release. The notable structural change was that nursing was now formally a peer experience to physician — every release note from this point forward labels features by experience scope. That metadata change matters more than it sounds: it means Microsoft now ships physician and nurse releases on the same cadence, with feature parity where applicable.
3.4.3 (January 2026) — Nursing Experience GA Nursing
The nursing experience went generally available. Dragon Copilot launched directly from Epic into a nursing web experience, with embedded enhancements for Epic Rover and admin-center guardrails for nursing templates.
DMO never had a dedicated nursing experience. This is the first major capability where Dragon Copilot is strictly ahead — there is no DMO equivalent to migrate from.
3.5.0 (January 2026) — The First Real DMO Migration Release
This is where the migration story stopped being incremental and became substantive.
What 3.5.0 closed:
- DMO formatting preferences automatically applied in Dragon Copilot. Dictation style, punctuation rules, section formatting — clinicians’ existing DMO configurations carried over without re-configuration.
- Full text control expanded to Allscripts, Altera, Cerner, i.s.h.med, and Softway. The moment Dragon Copilot’s editing behavior in non-Epic EHRs reached DMO parity.
- Workflows gained DMO-equivalent keyboard keys (Enter, Shift) and voice commands (anchor dictation, release dictation, show anchored app).
- Customizable templates gained transcript-aware modes — note + transcript, note only, transcript only — addressing a common DMO admin objection (“we can’t audit what the AI is doing”).
What 3.5.0 added beyond DMO: safe web search in the prompt field (US, default-on); multi-intent compound prompts in chat; verify EHR user linking for nursing — a security primitive DMO never offered.
3.5.1 (February 2026) — The Migration Release Microsoft Underplayed
If 3.5.0 was the first real migration release, 3.5.1 closed the most consequential remaining gaps.
- Protected section detection in Epic. Dragon Copilot now blocks dictated, typed, or AI-generated text from being inserted into read-only or system-generated sections of Epic notes — a hard requirement for Epic-heavy organizations worried about accidental-overwrite risk. DMO had this. Now Dragon Copilot does too.
- PowerMic device buttons trigger workflows. Combined with keyboard-shortcut triggers also added here, workflows can now be initiated by every input method DMO supported.
- Full text control extended to Altera Sunrise.
- Seamless migration of DMO formatting settings — capitalization, spacing, punctuation, number and measurement formats all carry over automatically.
- US/Canada AI model updates — Home Health and Triage specialty models live; HPI, A&P, and Emergency Medicine accuracy improvements; a streamlined process for ongoing specialty updates without a full release cycle.
- Dragon Copilot desktop available from the Microsoft Download Center.
This release should have been the one DMO administrators rallied around. Microsoft’s release notes treated it as a routine point release.
3.6.0 (April 2026) — Beyond DMO
3.6.0 was the release where Dragon Copilot stopped chasing DMO and started racing past it.
- 58 spoken languages → English clinical notes (US and Canada at launch). The UI stays in English, transcripts capture the spoken language, notes generate in English. DMO has nothing analogous.
- Auto-generated clinical letters — consultation summaries, patient letters, referral letters, created automatically from ambient recordings and surfaced in a new Documents section.
- Diagnosis-aware ambient notes for Epic Nebula customers — Assessment & Plan sections structured, diagnoses pushed back to Epic. Requires Epic’s November 2025 base release and Epic Nebula activation.
- Ambient recording extended from 75 to 120 minutes.
- Nursing mobile experience entered public preview — iOS and Android, unified patient-centric homepage, shift-based pending care summaries, cross-transcript Copilot chat.
- Epic FHIR API v2.5 activation — seven new R4 endpoints grounding AI-generated documentation in authoritative EHR data rather than inference alone.
3.6.1 (May 2026) — The Last Big Migration Friction
3.6.1 closed the single biggest remaining DMO migration friction point: Epic single sign-on for Dragon Copilot desktop, via SMART on FHIR. A toolbar button in Epic launches Dragon Copilot desktop with no second sign-in — exactly how Dragon Medical One worked, and its absence had been a real adoption barrier. (Microsoft-provisioned customers only at launch; Nuance-provisioned customers in a future release.)
- Multi-intent prompts default-on for both Nuance- and Microsoft-provisioned customers, graduating from 3.5.0’s limited rollout.
- Information Assist governance in Dragon Admin Center — manage trusted sources and coding suggestions at the organization or healthcare-group level.
- Self-service EHR edit control mapping — administrators map custom control class names to Dragon Copilot control types without filing a Microsoft ticket.
- Physician analytics consolidated into a single Overview dashboard.
The quieter story: 3.6.1 is the first release where the administrative experience of Dragon Copilot reached parity with DMO — admins now self-serve mappings, govern data sources, and read consolidated analytics in one place.
The Honest Gap List (As of 3.6.1)
Migration credibility requires naming what is not yet there. Here is the current list.
Functional Gaps
- Some Microsoft 365 Word/Outlook editions still pending full text control. 3.6.0 added Word M365 desktop, Word non-M365, and Outlook non-M365. Other M365 editions are roadmapped (“support for additional M365 versions is on the way”).
- Safe web search in Information Assist was deferred from 3.6.1 to a future release.
- Multilingual support (58 languages) is US/Canada only at launch. No public timeline for expansion to UK, Ireland, Germany, France, Netherlands, Belgium, or Austria.
- Diagnosis-aware notes require Epic Nebula — not all Epic customers have Nebula enabled.
Provisioning Gaps (Nuance-provisioned customers waiting on Microsoft-provisioned features)
- Epic SSO via SMART on FHIR — Microsoft-provisioned only at 3.6.1 launch.
- Information Assist governance — Nuance-provisioned customers route through their Customer Success Manager.
- Physician Overview dashboard analytics — Microsoft-provisioned only at 3.6.1.
Not gaps, but planning considerations: region scope (some AI-model, multilingual, and diagnosis-aware features are scoped by region) and Epic version dependencies (diagnosis-aware notes require Epic November 2025 base release; nursing backend requires Epic May 2025 release plus Vendor Services Project Nursing app v1.4). If your organization’s blocking issue is on the gap list, that is a fact to track release-by-release — not a reason to dismiss migration. The pattern across ten releases is that gaps close.
Migration Readiness: When Is It Safe to Move?
A practical readiness checklist, drawn from what the release notes tell us about deployment dependencies.
- Your EHR is Epic, Cerner, eClinicalWorks, Allscripts, Altera (including Sunrise), i.s.h.med, Intersystems Trakcare, or Softway.
- Your region is US, Canada, UK, Ireland, France, Germany, Netherlands, Belgium, or Austria.
- You are open to migrating from Nuance Command Center to Dragon Admin Center.
- Your physicians use PowerMic, PowerMic Mobile, or standard microphones — all supported.
- You want ambient documentation, not just dictation. Dragon Copilot’s ambient capabilities are a substantive upgrade over DMO.
- You serve a multilingual patient population outside the US/CA. Multilingual capture is US/CA only as of 3.6.0.
- You depend on specific M365 Word/Outlook editions. Verify current full-text-control coverage against the 3.6.0 release notes.
- You are Nuance-provisioned and require Epic SSO immediately. The capability is shipping; the rollout to Nuance-provisioned customers is “in a future release.”
- You require Epic Nebula features (diagnosis-aware notes). Confirm Nebula activation and Epic Vendor Services Application versions before scheduling.
- You operate exclusively in regions Dragon Copilot has not yet reached. Most expansion has been in North America and Europe.
- You depend on legacy Dragon Medical Practice Edition (DMPE) workflows. DMPE is end-of-life and was never the same product as DMO; migration paths are different.
What This Means for Voice Automated Customers
The migration is real, the cadence is fast, and the gap list is shrinking by the month. For organizations Voice Automated supports today:
- DMO is not at risk of imminent retirement. Microsoft continues to support and certify DMO. The migration is being pulled by Dragon Copilot’s growing capability set, not pushed by DMO’s deprecation.
- The migration window is opening, not closing. Each release makes Dragon Copilot a more credible move for a wider range of organizations.
- The administrative migration matters as much as the clinical one. Moving from Nuance Command Center to Dragon Admin Center is its own project, with its own readiness criteria. Several 3.5.x and 3.6.x features are gated on it.
- Implementation expertise has changed shape. DMO implementations rewarded deep knowledge of EHR text fields, Citrix, .NET runtimes, and PowerMic configurations. Dragon Copilot implementations reward all of that plus Epic Vendor Services applications, FHIR scoping, ambient template tuning, and Dragon Admin Center governance.
Voice Automated has been deploying Nuance and Microsoft healthcare voice technology since the products existed. The same expertise that handled DMO rollouts handles Dragon Copilot rollouts — extended. Dragon Medical One remains the proven, reliable engine clinicians trust today; Dragon Copilot is the platform that engine now lives inside. You do not have to choose between “what works today” and “what’s next” — the migration path keeps both.
Planning Your Dragon Copilot Migration? Start With an Assessment.
Migration affects clinical workflow, security posture, and budget — and the readiness criteria differ by EHR, region, and provisioning path. Voice Automated provides migration assessment, deployment planning, and Dragon Admin Center transition support, drawing on three decades of clinical voice implementation experience. Let’s map where your organization stands against the current release.
Frequently Asked Questions
Is Microsoft retiring Dragon Medical One?
No. Microsoft continues to support DMO. Dragon Copilot is positioned as the consolidation product — a unification of DMO’s dictation foundation with DAX Copilot’s ambient documentation. Migration is a customer choice on a customer timeline.
Is Dragon Copilot the same product as DAX Copilot?
No, but it absorbs DAX Copilot’s capabilities. DAX Copilot was the ambient documentation product layered on the DAX platform. Dragon Copilot unifies DMO’s dictation engine, DAX’s ambient capture, and a generative AI layer into a single product line with web, desktop, mobile, and embedded clients.
Does Dragon Copilot work in Epic?
Yes — extensively. Dragon Copilot for Epic supports Hyperdrive desktop dictation, embedded ambient recording, Epic Rover for nursing, Haiku and Canto for mobile, SMART on FHIR single sign-on (3.6.1), and Epic FHIR API integration with seven activated R4 endpoints (3.6.0). Specific capabilities require specific Epic releases and Vendor Services Application versions; Voice Automated can coordinate this with your Epic Technical Services team.
Do I need to leave Nuance Command Center to use Dragon Copilot?
Not immediately. Both Nuance-provisioned and Microsoft-provisioned customers can run Dragon Copilot. However, several recent features ship to Microsoft-provisioned customers first (Epic SSO, Information Assist governance, and Overview dashboard analytics in 3.6.1). Nuance-provisioned customers typically receive the same features in subsequent releases. Voice Automated plans the Dragon Admin Center migration as its own workstream.
What about HITRUST and HIPAA?
Dragon Copilot is deployed on Azure services that maintain HITRUST and SOC certifications; product-level certification is not claimed. The compliance posture is the same Azure healthcare cloud framework that supports the rest of Microsoft’s healthcare product line, and the same one Voice Automated has assessed for DMO and DAX Copilot deployments. Voice Automated is an implementation partner for these certified platform services — Voice Automated does not itself hold HITRUST certification.
How fast is Microsoft shipping?
Roughly every five weeks. Between September 2025 and May 2026, Microsoft shipped versions 3.2, 3.3, 3.3.2, 3.4, 3.4.2, 3.4.3, 3.5, 3.5.1, 3.6, and 3.6.1 — ten releases in eight months.
What is the next release likely to bring?
Public roadmap signals suggest expansion of multilingual support beyond US/CA, additional M365 Word/Outlook editions for full text control, broader rollout of 3.6.1 features to Nuance-provisioned customers, continued nursing experience expansion (mobile preview to GA), and the deferred safe web search capability. Confirmed roadmap items appear on Microsoft Learn as each release ships.
How This Report Is Maintained
Every feature and parity claim in this report traces to a Microsoft Learn release-notes page, reconciled against Voice Automated’s internal release changelog and verified on each Dragon Copilot release. This report is updated within five business days of each new release — the version number in the title increments as Microsoft ships. Source pages:
- Dragon Copilot 3.2 — learn.microsoft.com/…/whats-new/3-2
- Dragon Copilot 3.3 — learn.microsoft.com/…/whats-new/3-3
- Dragon Copilot 3.3.2 — learn.microsoft.com/…/whats-new/3-3-2
- Dragon Copilot 3.4 — learn.microsoft.com/…/whats-new/3-4
- Dragon Copilot 3.4.2 — learn.microsoft.com/…/whats-new/3-4-2
- Dragon Copilot 3.4.3 — learn.microsoft.com/…/whats-new/3-4-3
- Dragon Copilot 3.5 — learn.microsoft.com/…/whats-new/3-5
- Dragon Copilot 3.5.1 — learn.microsoft.com/…/whats-new/3-5-1
- Dragon Copilot 3.6 — learn.microsoft.com/…/whats-new/3-6
- Dragon Copilot 3.6.1 — learn.microsoft.com/…/whats-new/3-6-1
Ready To Take Your Medical Dictation to the Cloud?
Related Posts
Dragon Copilot 3.6: Multilingual Documentation in 58 Languages, Auto-Generated Clinical Letters & Mobile Nursing Platform (2026)
Voice Automated | Product Updates | April 2026 Healthcare organizations serving diverse patient populations have long faced a documentation barrier:
Dragon Copilot 3.5.1: AI Model Accuracy Updates, Protected Sections & DMO Migration Improvements (2026)
Voice Automated | Product Updates | February 2026 The gap between Dragon Medical One and Dragon Copilot keeps narrowing. Dragon
Dragon Copilot 3.5: Enhanced Templates, Safe Web Search & Expanded Nursing Capabilities in 2026
Voice Automated | Product Updates | January 2026 Clinical documentation keeps getting smarter. The latest Dragon Copilot release delivers a