Is Dictation HIPAA Compliant? What Makes It Safe

No dictation app is HIPAA compliant on its own. HIPAA does not certify software. It sets duties for the people and organizations that handle protected health information, so whether dictation meets them depends on who runs it, where the audio goes, and what contracts and safeguards surround it. The same tool can be a reasonable choice for a clinician working offline on a locked laptop and a compliance failure in a clinic that sends patient audio to a vendor's cloud account with no contract.

HIPAA defines a business associate as a person who, other than as a member of the covered entity's workforce, creates, receives, maintains or transmits protected health information ¹. For dictation, that definition is the one to check first. A speech recognizer that receives patient audio is handling that information for the clinic, so the vendor is in that role.

This guide covers the HIPAA side of dictation and is part of our voice privacy overview. For the general privacy picture, read Is Voice to Text Safe? How to Dictate Privately. For what a particular recognizer keeps, see whether Whisper AI is safe and how long voice data is kept.

No dictation app is HIPAA compliant by itself; the way you use it is

Compliance comes from the arrangement around the tool. Four things decide it for most dictation setups:

1. Who receives the audio. A recognizer on your own device does not send audio to anyone. A cloud recognizer does, and that vendor needs a contract.
2. What the vendor may do with it. Training, human review and long storage are each a separate use, and each can change whether the vendor is acting for you.
3. Which safeguards the covered entity has in place. These include encryption, unique user IDs, logoff, audit trails and a documented risk analysis.
4. Whether the vendor signs. A business associate agreement (BAA) is the contract HIPAA requires for this relationship. A signed BAA is one part of the program, not the whole of it.

Our reading of the sources is simple. If a product sends patient audio to a server you do not control, check for a signed BAA first. If it never sends audio anywhere, the BAA question largely falls away, but the device still has to be secured. The sections below take each case in turn.

Any vendor that receives patient audio is a business associate and needs a BAA

HHS's cloud guidance answers the core question directly. The covered entity and a cloud provider that holds its health information "must enter into a HIPAA-compliant business associate agreement (BAA)" ².

HHS's general rule for vendors is broader than cloud storage. In its health app guidance, HHS says that "most vendors or contractors (including subcontractors) that provide services to or perform functions for covered entities that involve access to PHI are business associates" ³. A transcription service that receives recordings made during care is a clear example.

The Privacy Rule lets a covered entity share protected health information with a business associate, and let the business associate handle it, if the covered entity obtains "satisfactory assurance" that the business associate will appropriately safeguard the information ⁴. In practice, the BAA is that written assurance.

Google's HIPAA page takes the same approach. It says that "Google Cloud and Google Workspace support HIPAA compliance within the scope of a Business Associate Agreement, but ultimately you are responsible for evaluating your own HIPAA compliance" ⁵. It also tells the customer to decide two things: whether the customer is a covered entity or a business associate, and "Whether you require a Business Associate Agreement with Google" ⁶.

The practical question is therefore whether the dictation feature you use is covered by the BAA, not whether the company offers BAAs at all. A BAA covers the services it names, not every product the same company sells.

Consumer voice typing comes without a BAA and is not meant for patient information

Consumer voice typing is the case most people ask about. Windows is a clear example. Microsoft says that online recognition sends voice data to Microsoft "only to provide the service and create text transcriptions" ⁷. Voice typing converts speech to text using online speech recognition ⁸. So patient audio dictated through that path goes to a cloud service, and the sources we read do not show that service offered under a BAA for this use.

We did not find a Microsoft statement that the Windows feature is covered by a BAA, so treat it as not covered unless you confirm otherwise in writing. Our question on Microsoft dictation and HIPAA walks through the same reasoning.

Google Docs voice typing raises a different issue. Google says voice typing in Docs works with the latest versions of Chrome, Edge and Safari, and that the web browser controls the speech-to-text service ⁹. The document lives in Google Workspace, which has a BAA route, but the speech step runs in a browser service. We did not find a Google statement that the browser's speech service is inside the Workspace BAA. Our question on Google voice typing and HIPAA covers this in more detail.

The table below lists the tools this guide reviewed and what each vendor's own pages say about where recognition runs and whether a BAA is offered.

Medical dictation products are built to sign a BAA

Clinical products are built around these contracts. Philips describes Dragon Medical One as "cloud-based clinical speech recognition for documenting care in the EPR and beyond" ¹², where EPR is the electronic patient record. Because it is cloud-based, it belongs in the BAA analysis. We did not confirm from Nuance's own pages which agreement applies to a given Dragon Medical One deployment, so ask the vendor or reseller for the document that governs your setup. The medical dictation guide covers how these products are used in practice, and the Dragon Medical One term explains the product.

A vendor's description of a medical product is a starting point, so check it against the contract before you rely on it. A setting that limits storage is useful, but it is not a substitute for a BAA.

Some institutions restrict tools that lack the right contract. If your organization has a list of approved tools, check that list before you dictate patient information.

On-device dictation keeps PHI on your hardware, but device security rules still apply

When recognition runs on the device, the audio never reaches the vendor, so there is no third party in that step. Apple's own policy describes this. Keyboard settings show whether dictated audio and transcripts are processed on the device or sent to Apple servers ¹¹. Apple also says dictation sent to its servers is not stored unless you opt in to Improve Siri and Dictation ¹⁴. For patient information, that opt-in should stay off.

Our reading is that on-device recognition removes the BAA question for the recognition step. It does not remove the Security Rule. The device holds the transcript and the recording, and HIPAA's safeguards still apply to that copy. We did not find an Apple document offering a BAA for Dictation. The on-device case does not turn on one, but a clinic should still write the device into its risk analysis.

Yap, which we make, is an on-device dictation app for Mac and Windows. Recognition runs on your computer. That is a fact about where audio goes, and it is the reason the BAA question does not arise for recognition. It does not make the app HIPAA compliant on its own: the clinic still has to secure the device, control access and document its decisions. If you are under HIPAA, ask every vendor, including us, for its written terms before you put patient information through it. You can download the app to test it on your own device.

The Security Rule expects encryption, access control and audit trails around dictation

The Security Rule names the safeguards a covered entity or business associate must maintain for electronic protected health information. Dictation touches most of them, because the audio, the transcript and the editing history are all electronic records. The table below lists the requirements that matter most for a dictation workflow and what each one means in practice.

The risk analysis is the anchor. Every other safeguard is a decision the covered entity makes and records, and the analysis is where the decisions are justified. HIPAA makes it a required specification, not an optional one ¹⁵.

Breach handling is the other half of the picture. If a dictated recording or transcript is exposed, the covered entity has a clock. HIPAA's Breach Notification Rule requires notice to affected individuals "without unreasonable delay and in no case later than 60 calendar days after discovery of a breach" ²⁰. Sixty days is the outer limit, not a target, so a clinic should know its dictation tools' logs well enough to find a problem quickly.

Human review is a separate risk that the safeguards do not solve by themselves. In 2019 the Guardian reported that Apple contractors "regularly hear confidential medical information" as part of quality control for Siri ²¹. That was about one vendor's review process in 2019, but it shows why a clinic should ask any vendor whether people listen to recordings, and what its contract says about it. Our guide on whether dictation apps train AI on your voice covers the training side of the same question.

Ambient AI scribes add a recording consent question to the HIPAA question

An AI scribe that records the whole visit adds two questions to the dictation questions above. The first is whether HIPAA allows the use at all. HIPAA permits a covered entity to use or disclose protected health information "for its own treatment," and documenting care is part of treatment ²². The second is consent to the recording itself, and that is a question of state law, not HIPAA.

Recording consent depends on where the visit happens. California's Penal Code 632 punishes a person who intentionally records a confidential communication "without the consent of all parties" ²³, which is the all-party consent rule. Federal law takes a different approach, the one-party consent rule: the Wiretap Act says it is not unlawful to intercept a communication when the interceptor is a party to it, or when "one of the parties to the communication has given prior consent" ²⁴. Check the law where the patient is, not only the federal default. Our guide to recording consent laws lists the differences, and the question on whether patients have to consent to AI scribes applies them to this case.

Patients can be willing, but they want details. In a 2025 Australian study of allied health practices, patients were comfortable consenting to an AI scribe in their own appointments, but some acknowledged that other patients might need "additional information about data storage and security" to make an informed decision ²⁵. A consent script that says only "this visit is being recorded" leaves out the questions patients ask.

Accuracy matters for the record as well as for privacy. In a UC Davis pilot of 356 reviewed notes, the most common error was an accidental omission, which appeared in 18 percent of the reviewed notes ²⁶. Hallucinations, meaning content the recording did not support, appeared in 11.5 percent of them ²⁷, and accidental inclusions in 9.3 percent of them ²⁸. Review the note before you sign it, whichever tool wrote it.

The chart shows that omissions were the most common error category in that pilot. The counts are physician reports, not a line-by-line audit against the recordings, and the study covers a single health system. Read it as a signal about what to check, not as a rate that applies everywhere.

How to check a dictation tool before patient information goes through it

Use this sequence for any tool, including ours.

1. Ask where recognition runs. On Windows, open Settings, then Privacy & security, then Speech, and check the Online speech recognition switch ²⁹. Turning it off keeps only device-based features ¹⁰.
2. If audio leaves the device, ask for a signed BAA that names the dictation feature, not just the company.
3. Check training, storage and human review in the contract, not only on the marketing page.
4. Confirm access controls: a unique login for each clinician, logoff on shared machines, and an audit log that you can read.
5. Add the tool to your risk analysis, with the decision and its reason.

For the general settings to review, see how to delete voice recordings. Our overview of medical dictation and AI medical scribes covers the clinical workflows in more depth, and the Mac privacy guide explains what Apple keeps. For the cloud question in general, read whether AI dictation apps send text to the cloud, and for offline tools, whether Whisper can run offline.

Questions this guide answers

• Is Microsoft dictation HIPAA compliant?
• Is Google voice typing HIPAA compliant?
• Do you need a BAA for dictation software?, covering when a vendor must sign one
• Is on-device dictation HIPAA compliant?, covering the on-device case in more detail
• Do patients have to consent to AI scribes?

Whether a dictation tool is safe for patient information is a question about the whole arrangement: the contract, the place the audio goes, and the safeguards around the device. The sources above answer each part of it. Where a vendor's page makes a claim, check it against the contract, and where a source is silent, treat the feature as not covered until someone confirms it in writing.