Dictation and Speech Recognition Blog
Dragon Copilot 5.2 Is Here: Patient Matching, Nursing on Android, and Getting Ready for 6.0 in November
Dragon Copilot 5.2 is herePatient matching, nursing on Android, and analytics that show who is really using it
Available now — and the release that starts the clock on 6.0, when the enhanced physician experience becomes the default in November.
Two questions follow every ambient documentation rollout. Is the note attached to the right patient? And is anyone actually using this? Dragon Copilot 5.2 answers both more directly than any release before it — a traffic-light check that the session matches the patient open in the EHR, and a much deeper set of adoption and utilization analytics for physician and nursing leaders. For nursing, it also brings Android devices into the embedded experience, older lines and drains into ambient documentation, and a preview of Spanish (US) support.
Where 5.2 sits
For physicians: patient matching
When a clinician switches patients in the EHR, Dragon Copilot now detects the change and shows a traffic-light indicator comparing the active Dragon Copilot session with the patient open in the chart. An optional auto-follow setting opens the matching session automatically, so documentation stays with the right record without manual navigation.
Green: matched
The active session matches the patient open in the EHR. Keep working.
Orange: partial match
Dragon Copilot has found a potential match and lets the clinician pick the right existing session.
Red: mismatch
The session and the chart do not match. Dragon Copilot offers options to select the correct session before the clinician continues.
For physician leaders: analytics on adoption and utilization
Licenses are easy to count. Knowing where Dragon Copilot is working, and where it is quietly being abandoned, is harder. 5.2 adds the cuts that most rollouts end up building by hand.
Compare healthcare groups
Filter analytics to a group configured in Dragon admin center, see which group each clinician belongs to, and compare usage across groups. Groups must be assigned to users for this to work.
Specialty and user type
The Overview dashboard can now show adoption and utilization by primary specialty and by user type — so enablement effort goes where it is needed.
Drop risks and dropped users
Analytics now separates clinicians who may be at risk of disengaging from those who have stopped using Dragon Copilot — the list to work for timely re-engagement.
EHR IDs and cleaner labels
User-level reporting shows EHR IDs, and specialty and role names are easier to read, making it simpler to match usage to the user records you manage.
Deleted sessions now counted
Deleted sessions are included in product analytics, for a more complete picture of actual use.
For nursing: Android, older LDAs, flowsheet profiles, and Spanish
Android in the EHR’s mobile nursing app (GA)
Nurses on Android devices get the same ambient documentation, review and workflow support already available on iOS. It requires a recent EHR release with SMART on FHIR configured, Android 11 or later (13 recommended), and the vendor-side app updates — setup Voice Automated can coordinate with your EHR team.
Lines, drains and airways up to five years old (GA)
Ambient documentation now covers LDAs up to five years old, up from the previous 120-day limit, in production and test environments (not yet in playground environments). No action required.
Flowsheet profiles (preview)
Administrator-configured profiles tailor Dragon Copilot to care settings, patient populations and workflows — a curated set of flowsheet templates and settings such as LDAs — without changing the underlying EHR profile. Admins assign profiles, or can let users choose their own (off by default), including in bulk.
Spanish (US) support (preview)
Once enabled for the organization, users can turn on Spanish so English and Spanish are both recognized in the same session. The transcript may include Spanish; the AI output, such as flowsheet extraction, is returned in English only.
Nursing analytics (GA)
Usage trends over time by site, unit and role; usage reporting through your existing reporting experience; summary totals in the Overview and User engagement details dashboards; and EHR IDs aligned with Dragon admin center. “Service line” is also now called “care setting” throughout — a rename only.
What our preview got right — and what it missed
Landed as planned
Patient matching, the Spanish (US) nursing preview, the enhanced flowsheet profile manager, profile selection, the care-setting rename, nursing usage reporting and trends, and most of the physician analytics — specialty and user type filters, drop risks, EHR IDs and deleted sessions — all appear in the 5.2 release notes.
Not in our preview
Android support for nursing, LDAs up to five years old, healthcare group comparison in physician analytics, and the DAX Copilot / Dragon Copilot reporting change were not in our roadmap post. They are in the 5.2 notes — and so is the November date for the enhanced experience becoming the default.
Summary totals: listed for nursing
The roadmap listed physician summary totals for 5.2. The 5.2 notes list summary totals only for the nursing dashboards, and 5.1’s notes had already listed them for physicians. If reporting depends on them, check your own dashboards.
The full pre-release view is still available: What’s coming in Dragon Copilot 5.2 & 6.0 →
Get physicians ready for 6.0 in November
Dragon Copilot 5.0 introduced an enhanced, content-first interface that organizations could opt into. Microsoft says that with Dragon Copilot 6.0, planned for November 2026, the enhanced experience becomes the default for all physician customers, and it encourages organizations to let users try it now so the change is familiar before it arrives. Several recent capabilities, including 5.1’s “Hey Dragon” standby mode, already depend on it.
Turn on the new design now
In Dragon admin center, an administrator enables Switch to new design and, where applicable, the iOS webview setting. For Nuance-provisioned organizations, enablement goes through Microsoft — Voice Automated can coordinate it for you.
Embedded iOS users need SMART on FHIR
To bring physicians who document in the EHR’s iOS mobile app onto the enhanced experience, your organization must have SMART on FHIR implemented. If that will not be in place before 6.0, plan for it now.
Also planned for 6.0
Microsoft’s roadmap lists enhanced default Physical Exam and Assessment & Plan templates for November — clearer organization and more consistent output. Planned, not released.
See 5.2 live — and what 6.0 means for your physicians
Live walkthrough on Zoom — Wednesday, October 28, 9:00am PT, with Henry Majoue. Patient matching, the new analytics, the nursing updates, and a practical plan for the 6.0 switch. Call or get in touch to reserve your spot.
Where 5.2 fits in your move from Dragon Medical One
None of this is a reason to pause Dragon Medical One. The analytics make a measured, group-by-group Dragon Copilot rollout easier to manage; they do not make today’s DMO deployment any less complete.
Weighing the move from DMO?
Our living, version-by-version breakdown shows where each capability stands today — the practical view, not the roadmap view.
Not on 5.1 yet?
Hands-free standby, foot-pedal shortcuts and AI templates that reach the chart — the release before this one.
Planning around the roadmap?
Our preview of 5.2 and 6.0, written from Microsoft’s published plan before release.
Why go through Voice Automated
Microsoft makes the product; we make it work in your clinic. Voice Automated is an authorized Microsoft partner with three decades in healthcare voice — and a long-time implementer of Dragon Medical One, the product named Best in KLAS six consecutive years (2021–2026). We scope the right setup for your specialty, handle rollout and training, and support your team after go-live — because new capabilities succeed on adoption, not just installation.
Rolling out Dragon Copilot 5.2?
Fifteen minutes with our implementation team — whether patient matching applies to your EHR, setting up flowsheet profiles, reading the new analytics, and a plan for the 6.0 switch.
Frequently asked questions
For physicians, Dragon Copilot 5.2 adds patient matching, a traffic-light check that the active session matches the patient open in the EHR, and new adoption and utilization analytics, including healthcare group comparison, specialty and user type filters, and drop-risk reporting. For nursing, it adds Android support in the EHR’s mobile nursing app, ambient documentation for lines, drains and airways up to five years old, and, in public preview, flowsheet profiles and Spanish (US) support, along with new nursing usage analytics.
When a clinician switches patients in the EHR, Dragon Copilot detects the change and shows a traffic-light indicator: green when the session matches the open patient, orange for a potential match the clinician can select, and red for a mismatch, with options to choose the correct session. An optional auto-follow setting opens the matching session automatically. Microsoft lists patient matching for Dragon Copilot desktop in the United States, for one specific EHR integration.
Yes. Starting with Dragon Copilot 5.2, organizations must create at least one flowsheet profile in Dragon admin center. Without one, all test cases in AI customization manager show a Needs review status. Android support also requires EHR-side setup, including SMART on FHIR.
Microsoft says Dragon Copilot 6.0 is planned for November 2026, and that with it the enhanced user experience becomes the default for all physician customers. Microsoft encourages organizations to enable the new design in Dragon admin center now so users can become familiar with it before the transition. Physicians who use the EHR’s iOS mobile app need SMART on FHIR implemented to use the enhanced experience.
Dragon Copilot is deployed on Microsoft Azure services that maintain HITRUST and SOC certifications. Product-level certification is not claimed; the platform is the correct scope. Voice Automated is an implementation partner for these certified platform services.
Ready To Take Your Medical Dictation to the Cloud?
Related Posts
eClinicalWorks Is Ending Its Built-In Dragon Medical One: How to Keep Dictating After Mid-November 2026
Voice Automated · Authorized Microsoft Partner Dictating in eClinicalWorks with Dragon? Mid-November changes that.eCW’s built-in Dragon Medical One is ending.
Dragon Copilot Clinical Note Updates: Context-Aware HPI, Psychology and Psychiatry Notes (September 2026)
Voice Automated · Authorized Microsoft Partner Dragon Copilot’s clinical notes have changedA context-aware HPI, a rebuilt psychology note, and a
Dragon Copilot 5.1: Hands-Free “Hey Dragon” Recording, Foot Pedal Support, and AI Template Workflows (2026)
Voice Automated · Authorized Microsoft Partner Dragon Copilot 5.1Hands-free recording, foot pedals, and AI templates that reach the chart A