In the clinical day

Start with your patient-session routine

In an eligible US Epic desktop environment, 5.2 patient matching uses a traffic-light indicator to show whether the Dragon Copilot session aligns with the open patient chart. Optional auto-follow can open the matching session as the EHR patient changes. Review Microsoft’s patient-matching details.

Before changing a familiar routine, ask your administrator which behavior your environment supports. Then walk through a normal chart change with your team. Confirm how the clinician recognizes the current patient, finds the intended session, and responds when the context needs attention.

Keep patient identification and note review in the workflow. An indicator is a useful aid, but the team still needs to understand what it means and how to respond. If the behavior differs from expectations, document the application, EHR workflow, and steps that led to the issue so support can investigate.

A small preparation step

Get comfortable with the enhanced workspace before November

The interface transition is the part of this announcement every physician team should put on its preparation list. The enhanced experience arrived in 5.0 as an option; Microsoft says it becomes the physician default with 6.0 in November 2026.

Microsoft’s workspace guide shows how patient information, notes, transcripts, the library, and Copilot Chat fit together. Familiarize yourself with the tools you rely on most. A short practice session can reveal where local instructions or training need updating.

Try a focused walkthrough: find a session, check the microphone mode, locate a note and transcript, make a correction, and find the resources you normally use. Use your organization’s approved training environment and examples. Ask questions about tasks that feel unfamiliar rather than trying to learn every feature at once.

Team coordination

Give your administrator the right questions

Your organization’s administrator controls the relevant design settings. Epic Haiku iOS preparation also has webview and SMART on FHIR dependencies. Microsoft’s transition guidance directs organizations with unresolved readiness questions to their Customer Success Manager.

• Which physician groups already use the enhanced interface?
• Does our application and EHR setup meet the requirements?
• Who will communicate the change and provide orientation?
• Where should clinicians send workflow questions before and after the transition?

Bring those answers into a practical plan. A small group may need one focused session; a larger organization may need specialty-specific examples and a clear escalation route. Match the support to the people and workflows involved.

Make support specific

Use adoption data as a starting point for help

The physician analytics updates give organizations more ways to understand use. For clinicians, the useful question is what the team does with that information. A report should lead to a conversation about the workflow and the support people need.

If you are not using Dragon Copilot as often as expected, identify the reason. Are you unsure where a tool moved? Does the note need repeated edits? Is recording awkward in a particular room? Specific examples make it easier to distinguish training, configuration, hardware, and product questions.

The same principle applies to a successful workflow. Share what is working so the team can build useful guidance around real practice. Keep feedback focused on the task and the experience, with appropriate handling of any patient information.