Ambient scribe
Microsoft Dragon Copilot
Microsoft Dragon Copilot supports clinician-controlled documentation and nursing workflows. Clinicians approve the output. Declining encounter recording may still allow later AI processing of clinician dictation, and revocation does not remove data already anonymized.
Checklist assessment dated October 30, 2026. Independent confirmation is incomplete. Hugo has not personally verified this service.
Agency checklist · October 30, 2026
Constrains 2 of 12 yes
Document-based draft. Independent confirmation is incomplete. Hugo has not personally verified this service.
Assessed function: Microsoft Dragon Copilot clinician documentation and nursing workflows (dictation, ambient note generation, flowsheet capture, generative drafts), deployed by healthcare organizations. Institutional AI affecting the patient record, not a patient-operated assistant.
Astra review conflicted: OpenAI model in role record.
A no can mean missing documentation or institution-dependent control; it does not by itself establish harmful behavior. These categories are not clinical safety or product-quality ratings.
- Public documents do not establish actual product behavior.
- The independent review screened rules and selected evidence; it did not replicate all twelve answers for this tool.
See all twelve answers and their evidence
| Question | Answer | Evidence / review | Source and reasoning |
|---|---|---|---|
| 1. Told it is AI | No | deployer-dependent Not independently replicated | Requires patient consent (per organization policy) for recording.Source Microsoft's own terms make the customer solely responsible for notices and consents (Service Specific Terms). No patient-facing AI notice is built in by Microsoft that the sources show. Whether a patient is told depends on the deploying organization. |
| 2. Operator and model maker named | Yes | documented Not independently replicated | Dragon Copilot is powered by Microsoft’s conversational and ambient AI capabilitiesSource Microsoft is named as the operator and AI maker. The Transparency note also names Azure OpenAI Service content filters. The deploying clinic or health system that actually runs it in a given encounter is not named by Microsoft and varies. |
| 3. Patient chooses to use it | No | deployer-dependent Not independently replicated | only intended to be used by a qualified member of an individual's care teamSource Use is by the clinician on the customer's behalf. The patient does not start or choose it. |
| 4. Patient sets the task | No | documented Not independently replicated | The clinician controls all decisions related to healthcareSource The clinician and organization set the task and outputs (notes, referral letters, after-visit summaries). The patient does not set the purpose. |
| 5. Patient can decline or stop | No | deployer-dependent Not independently replicated | if a patient prefers not to have the encounter itself be recordedSource Microsoft documents that a clinician can dictate after the visit instead of recording the encounter. That is narrower than declining AI-assisted documentation, since dictation still produces an AI draft. Recording consent is per organization policy. |
| 6. Patient sees the AI output | No | documented Not independently replicated | The generated clinical documentation is returned to the clinician for review.Source Output goes to the clinician. The patient sees at most a clinician-reviewed after-visit summary, not the AI's own output. |
| 7. Patient can correct or challenge | No | deployer-dependent Not independently replicated | how Microsoft can assist the customer in fulfilling data subject rightsSource Any route is through the customer (covered entity). No patient-facing correction or contest route is documented by Microsoft. |
| 8. Patient can get a copy | No | deployer-dependent Not independently replicated | The customer is solely responsible for downloading, exporting, and permanently storing all relevant Dragon Copilot dataSource Retention is up to 90 days (FAQ) and the customer files to the EHR. The patient has no direct access to a copy. |
| 9. Patient can delete | No | deployer-dependent Not independently replicated | a patient revokes previously provided consent, a customer can log a ticket with customer supportSource Deletion of identifiable data after consent revocation is initiated by the customer, not the patient. The same page says anonymized data created before revocation will not be purged. |
| 10. Training or sale does not override patient choice | No | documented Not independently replicated | Dragon Copilot's AI/ML models are trained solely on anonymized data.Source Customer Data is anonymized within 90 days and used to improve models. No patient opt-out is documented. Opt-out exists only as the customer purging identifiable data on a revoked consent. |
| 11. Patient can run it or take it elsewhere | No | not-documented Not independently replicated | Quotation not recorded; evidence repair pending. Source Cloud service licensed to health organizations. No patient route to run it or move the function with their data. |
| 12. No advertising or data business | Yes | documented Not independently replicated | Microsoft will not disclose or provide access to any Processed Data except: (1) as Customer directsSource Source is the Microsoft Product and Services DPA (WW, English, May 2026 docx) linked from the Licensing page. The DPA also says Microsoft will not use Customer Data for user profiling or advertising or similar commercial purposes. Caveats: Microsoft uses anonymized data internally to improve models (counted under Q10), uses subprocessors and human annotators, and the DPA binds the customer relationship, not the patient directly. |
Initial coding: Claude Sonnet helpers, compiled by Claude Opus 5.5 (Anthropic). Selective review and corrections: GPT-6 Astra (OpenAI). Editor: Hugo Campos. Acceptance of corrections is not product verification.
Checklist rules · Independent review and limitations · Later evidence follow-up
Earlier v1.3 assessment and control finding
Historical assessment under different rules. It does not set the current checklist zone.
Agency finding, before method v1.3
Mixed, institution-led
Control axis not applicable: clinician-operated
Historical editorial placement, pre-method: 36. No longer shown on the control axis.
This profile has not yet been reviewed under the published method. Its finding and any number are editorial placements made before the method existed.
- Evidence
- Documentary review. Public sources only, no hands-on testing by HugoScore.
- Review status
- AI draft. No person has settled the findings.
Earlier evidence and assessment
The sections below preserve the earlier review. Its classifications and provenance are historical; the checklist above gives the current draft classification.
Earlier finding · Control axis not applicable: clinician-operated
Method v1.3. The control line is evidence for how the agency finding arose, not a quality score. Legacy editorial placement, pre-method: 36. Not comparable with v1.3 positions.
Mixed, institution-led
Microsoft Dragon Copilot supports clinician-controlled documentation and nursing workflows. Clinicians approve the output. Declining encounter recording may still allow later AI processing of clinician dictation, and revocation does not remove data already anonymized.
Patient agency
How this tool changes agency
Better documentation may support subsequent patient review, but the product assigns the patient no direct evidence-inspection or editing workflow in these materials. Clinician benefit is not evidence of increased patient authorship.
Local consent wording, access to transcripts, AI-specific correction routes, patient-facing release of outputs, and actual enforcement.
Patient agency assessment
Who sets and changes the goal?
The clinician sets the documentation task and approves its consequences. Refusing encounter recording can change capture method, but is not the same as preventing later AI processing of clinician dictation.
What can the patient understand, question, or do?
Better documentation may support subsequent patient review, but the product assigns the patient no direct evidence-inspection or editing workflow in these materials. Clinician benefit is not evidence of increased patient authorship.
Can the patient evaluate the conditions of use?
The lifecycle and revocation limits are specifically disclosed. Effective consent still depends on what the healthcare organization tells the patient and how requests are handled.
Text findings
Conditions of use
Published controls and their limits
The lifecycle and revocation limits are specifically disclosed. Effective consent still depends on what the healthcare organization tells the patient and how requests are handled.
What remains unknown?
Not tested or not established
Local consent wording, access to transcripts, AI-specific correction routes, patient-facing release of outputs, and actual enforcement.
Who evaluated this?
AI-assisted public-source draft
Vendor statements describe published conditions, not independently verified behavior. No clinical, security, accessibility, or legal validation is claimed. Earlier evidence remains dated in the report and history.
Sources checked
- https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/whitepapers/privacy
- https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/about/faqs
Source-specific findings and retrieval limitations are recorded in the full report.
Earlier review provenance
Criteria
CAIHL-derived HugoScore framework and September 7 qualitative review priorities. Draft v1.2 numerical anchors remain unadopted.
Reviewer
AI-assisted public-source reassessment prepared in OpenAI Codex.
AI / model
OpenAI Codex / GPT-6
Human review
Hugo Campos authorized publication of these AI-assisted draft reassessments on September 8, 2026. This does not claim comprehensive human verification of every finding.
Review date
2026-09-08
Limitations
Local consent wording, access to transcripts, AI-specific correction routes, patient-facing release of outputs, and actual enforcement. No live product use, patient-data upload, account creation, code audit, clinical evaluation, or independent implementation validation.
Earlier review method
Focused public-source reassessment using CAIHL: patient authority, critical capacity, and informed control. Existing evidence plus one focused primary-source pass and at most one targeted follow-up. No live product testing. Numerical scores remain provisional editorial placements, not a new calculation.
Document-based draft · Medium for product governance (AI-assisted draft)