Microsoft and Nuance: the recording is the asset to govern
Microsoft’s April 2021 agreement to buy Nuance put ambient clinical documentation inside a large cloud platform. For health systems, the decisions that mattered concerned the encounter recording itself, the review workflow around the draft note, and the contract governing both.
Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
The week
On April 12, 2021, Microsoft announced an agreement to acquire Nuance Communications for $56 per share, a deal valued at about $19.7 billion including net debt. Nuance was best known in healthcare for Dragon Medical speech recognition, widely used by clinicians to dictate notes, and for its newer Dragon Ambient eXperience (DAX), which captured the conversation between clinician and patient and turned it into draft clinical documentation. Microsoft framed the deal around its cloud for healthcare and its push into industry-specific cloud services. The acquisition needed regulatory approvals in several jurisdictions and closed in March 2022.
Much of the 2021 commentary on the deal focused on the price and on Microsoft’s healthcare ambitions. For health system leaders, the consequential question was what ambient documentation asks of an organization. Dictation captures what a clinician chooses to say. Ambient tools listen to the whole encounter, including the patient. That changes three things, which we take in turn: the recording, a new class of clinical data; the workflow that turns it into a signed note; and the agreement that governs what the vendor may do with both.
The recording: a new class of clinical data
Ambient capture records the full conversation. That may include sensitive disclosures, family members in the room, and information that never makes it into the note. When held by or for a covered entity, the audio and transcript are protected health information, and they raise questions most organizations had never answered for dictation.
How is the patient told the encounter is being recorded, and how do they decline? Is the audio kept after the note is signed, and if so for how long and why? Who can listen to it, and is it part of the designated record set that a patient can request? State laws on recording conversations add a layer, since some require the consent of every party. Organizations should check with counsel on how these rules apply in each state where they operate.
Each answer has a cost. Deleting audio soon after signing limits breach exposure and discovery risk, but removes the ability to check a disputed note against what was said. Keeping it supports quality review and model improvement, but creates a large, sensitive archive. There is no universally right answer. There is a wrong process, which is letting the vendor’s default retention setting decide. Privacy, compliance, clinical leadership and information security need to settle these questions together, before the first pilot clinic goes live.
The workflow: where the draft lands and who checks it
An ambient tool produces a draft. The clinician reviews, edits and signs it. The quality of that loop decides whether the tool saves time or moves work around. If the draft lands outside the EHR and must be copied in, the gain shrinks and errors creep in. If it lands inside the note, with clear marking of AI-generated text until the clinician accepts it, review is faster and the record is clearer.
Clinical accountability must stay explicit. The signed note is the clinician’s, and policies should say so. Training should cover the specific ways these drafts go wrong: omissions of things said late in a visit, findings attributed to the wrong body side, and plausible statements nobody made. Some organizations add a periodic audit, comparing a sample of signed notes against their source audio, to see whether review is catching errors.
Measuring value belongs here too. Ambient tools are sold on time saved and burnout reduced. Those benefits are plausible, and clinicians who used early versions often reported relief, but vendor case studies are not neutral evidence. Health systems that evaluated well defined their measures before the pilot: after-hours documentation time from EHR audit logs, note completion times, clinician-reported burden, and the frequency and type of edits. They compared like with like by specialty and visit type, since a primary care visit differs from a procedure-heavy clinic. And they priced the scaled version, because per-clinician subscription fees that look modest in a pilot become a major line item across a large medical staff.
The agreement: what the vendor may do with the data
A business associate agreement sets HIPAA obligations. It does not settle every question that matters for AI. Health systems need clarity on whether audio and transcripts may be used to train or improve models. If so, is that use limited to de-identified data, and how is a voice recording de-identified at all? The contract should also say where data is stored and processed, which subcontractors touch it, and what happens to it at contract end. Voice is itself a biometric identifier in some contexts, which makes casual reuse riskier than it looks.
Consolidation raises the stakes. When a specialist vendor becomes part of a large platform company, its data practices may change to fit the parent’s architecture and product plans. A contract written for a standalone dictation vendor may not anticipate that. Health systems with existing Nuance agreements had good reason to review them once the deal was announced, especially clauses on data use, assignment and change of control.
The deal also signaled that ambient documentation would be sold as part of large cloud and EHR platforms, not as a niche tool. That brings integration and investment. It also ties a clinical AI choice to a platform relationship, which affects pricing power at renewal and the cost of switching. A health system should know, before signing, how prices may change at renewal and how it would export its configurations and stop the service if it needed to.
With hindsight
Looking back from 2026, the deal anticipated one of the fastest adoptions of a clinical AI tool on record. After large language models arrived, ambient documentation moved from pilot to broad deployment between 2023 and 2025. Microsoft folded Nuance’s products into what it now markets as Dragon Copilot, many other ambient scribe vendors entered the market, and EHR vendors moved into ambient documentation themselves. Clinicians generally value the reduced documentation burden, though published evidence on time saved and note accuracy varies by setting and study design. The governance questions above proved to be the right ones. Patient notice, audio retention, training rights and clinician review policies became standard parts of ambient deployments, and organizations that settled them before rollout avoided retrofits. Concentration remains a live concern as ambient tools become features of a small number of platforms.