Ambient scribe
Microsoft Dragon Copilot
Microsoft Dragon Copilot combines Dragon Medical One and DAX Copilot capabilities into an AI clinical workflow assistant for dictation, ambient documentation, generated notes, summaries, and EHR-integrated clinician workflows. Microsoft provides unusually detailed consent, retention, anonymization, model-improvement, and transparency documentation, but patient control remains mostly deployment-mediated.
Public-source research has been drafted; final human publication review and change-log detail are still required.
Summary judgment · 36% toward patient-directed
Mixed, institution-led
Dragon Copilot is enterprise clinical workflow infrastructure; Microsoft publishes detailed governance material, but patients still have limited direct control over the documentation and AI lifecycle.
Patient agency
How this tool changes agency
After Visit Summary outputs may support understanding, but Dragon Copilot is not a patient-controlled reflection, navigation, or appeal tool.
Consent is documented, but opt-out workflow, refusal pressure, and alternatives depend on the health system.
Patient-facing signals
Who does this AI serve?
Dragon Copilot is designed for clinicians and healthcare organizations, with EHR and workflow integration.
Can patients tell AI is involved?
Microsoft says consent is required before recording, and some DAX deployments publish patient explainers; actual notice remains deployment-specific.
Can patients meaningfully choose?
Consent is documented, but opt-out workflow, refusal pressure, and alternatives depend on the health system.
Can patients correct or challenge what the AI produces?
Clinician review is required, but patient access to transcript/audio and AI-specific dispute routes are not guaranteed by product-level materials.
Does it help patients understand or act?
After Visit Summary outputs may support understanding, but Dragon Copilot is not a patient-controlled reflection, navigation, or appeal tool.
Text findings
Who is left out or burdened?
Evidence incomplete
Documentation identifies limitations and need for human review, but public evidence by accent, language, disability, specialty, interpreter use, and patient population remains incomplete.
What happens to patient data?
Detailed enterprise data lifecycle, limited direct patient control
Microsoft documents audio/transcript/AI content retention, anonymization, model improvement, and revocation limits. Patient rights still flow through customer and Microsoft governance.
Are the clinical boundaries clear?
Relatively clear
Transparency materials say outputs require qualified healthcare professional review and identify unsupported use cases.
Who defined what good looks like?
Mostly vendor, clinician, and health-system-defined
Public evidence focuses on documentation workflow, clinical efficiency, and clinician experience; patient agency and correction outcomes need more evidence.
Review method
Deep public-source review of Microsoft product pages, Microsoft Learn documentation, privacy/security/transparency whitepapers, health-system patient explainers, and published ambient-scribe research; no vendor interview or hands-on deployment testing.
Draft profile · Medium draft