Published
Sources checked through , 5 p.m. Pacific · facts checked and fully reviewed · 3 min read
A November 19 follow-up to KPSGILL’s Dragon Copilot 6.0 investigation.
Ask a hospital how long it keeps an ambient recording and you may get a single number. Ask where a copy could have been sent before the timer expired and you may get a different answer. Microsoft’s November 18 nursing release gives administrators and clinicians a concrete reason to ask the second question. The company said nursing audio and transcript export to a customer-configured Microsoft Fabric environment reached general availability. Microsoft expressly describes the exported nursing material as identifiable. A general availability announcement establishes a capability. The organization’s configuration and access records establish whether it used that capability for a given encounter. November 18 nursing announcement
The product name matters even before an export occurs. Microsoft’s DAX Copilot for Epic FAQ describes 30-day retention for DAX session information and 30-day access to the combined transcript in its Epic activity. A separate Dragon Copilot FAQ, updated July 27, describes retention of audio, recognized text, transcripts and flowsheet values for up to 90 days. The signed chart, the source service and any customer-held copy each need their own answer. DAX Copilot for Epic FAQ · Dragon Copilot FAQ
There is a physician-specific record, too. A Microsoft Learn administration page last updated May 1 describes a Physicians toggle and separate choices for audio, transcripts and notes. Administrators choose the Fabric workspace and lakehouse for the export. That earlier document is important context for November’s nursing release. It identifies a second place to look when someone asks whether an encounter recording still exists. Whether any copy survives turns on the configuration at the time, selected data types, destination retention settings and any later deletion or preservation action. Physician export configuration
A different November 16 release expands what can inform a conversation inside Dragon Copilot Chat. Microsoft made Work IQ generally available. Its examples show a clinician retrieving an email or Teams message through existing permissions and following a reference to the source. Administrator setup, billing and user consent are part of that workflow. A link back to an email explains the origin of a chat response. It does not by itself show that anything from the email entered a signed patient note. Those are separate events that a reviewer would have to establish. Microsoft’s Work IQ announcement
For nursing, Microsoft also announced public previews of synthetic-patient simulation and session review. The latter can compare AI-extracted values with nurse corrections. These capabilities offer a practical exercise. Have a synthetic patient report a symptom that has already resolved. Then introduce a correction. Follow the original statement and correction through the generated output and the final filed value. Check whether a later reviewer can distinguish what was spoken, what the software extracted and what the nurse accepted. Document the product version, professional role and preview eligibility alongside the result. Nursing release · Earlier KPSGILL version review
For an actual retrospective review, the more productive request is narrow. Identify which encounter artifacts existed on the encounter date, where each was held, which role could retrieve it, and the applicable deletion or preservation rule at each destination. Have the reviewer distinguish firsthand recollection, signed documentation, source material actually inspected, and any remaining gap. That process gives a physician, a patient and a quality reviewer a shared account of what they can still verify. KPSGILL ambient documentation investigation