HIPAA-Compliant AI Note Takers: What a BAA Actually Covers

There is no such thing as a HIPAA-certified AI note taker. No agency certifies software as HIPAA compliant. When a vendor's site says “HIPAA certified,” that line came from their marketing team, not an auditor. The question that actually matters is narrower and much easier to check: will they sign a Business Associate Agreement, and does it cover the feature you want to point at patient data?

That second half is where teams get caught. Several large platforms will sign a BAA for their core product and leave the AI features out of it. Which are, of course, the features you came for.

Last updated August 2026. Vendor terms move quickly, so confirm current coverage with the vendor before you send them anything.

If a vendor creates, receives, stores, or transmits protected health information (PHI) for you, HIPAA calls them a business associate. That triggers a short and specific list:

• A signed BAA. This is the contract that makes the vendor legally accountable for the PHI you hand over. Without one, sending them PHI is itself a violation, however good their encryption is.
• Security Rule safeguards. Access controls, audit logging, encryption in transit and at rest, and a written incident response process.
• Breach notification. They have to tell you about a breach of unsecured PHI without unreasonable delay, so you can meet your own deadlines.
• Minimum necessary use. They can only use PHI the way the BAA allows. That rules out secondary uses, and training AI models on your patient data is the one to watch.
• Subcontractor flow-down. If your audio gets routed to a third-party model provider, that provider is a subcontractor and needs its own BAA. Ask who is in the chain.

The common failure in 2026 is not a vendor refusing to sign a BAA. It is a vendor signing one that quietly does not cover the AI. Two of the biggest platforms work this way:

Zoom. Zoom offers a BAA on Zoom for Healthcare and eligible Business and Enterprise plans, covering Meetings, Webinars, Phone, Team Chat, and Rooms. But turning on HIPAA mode disables a set of AI Companion features, and only some of what remains, such as smart recording and meeting summary, sits inside the BAA. The compliant setup is the less capable one. Zoom's HIPAA documentation

Notion. Notion will sign a BAA, but only for Enterprise customers above a minimum seat count, and Notion AI is excluded from that coverage on every plan. You can store PHI in a Notion database. You cannot point Notion AI at it. Notion's HIPAA help page

The pattern repeats because of how these products get built. Compliance reviews the platform, the AI ships later on a different legal footing, and the carve-out never comes up in the sales call. So ask for the BAA's scope in writing, feature by feature, rather than a yes or no about the company.

Most vendor security pages answer the easy questions and skip the ones that decide whether you can use the product at all. Put these five in writing:

1. Will you sign a BAA, and on which plan? If the answer is “Enterprise only,” get the price before you get attached. The compliant tier is often several times the number you were first quoted.
2. Does the BAA name the AI features? Not “is the product covered” but whether transcription, summarization, and any AI chat or agent features are each in scope. This is exactly where Zoom and Notion diverge from their own marketing.
3. Which subprocessors receive PHI? If audio goes to OpenAI, Anthropic, Google, or a hosted speech service, each is a subcontractor that needs its own BAA and a no-training commitment. Ask for the list, not a reassurance.
4. Is our data used for training or product improvement? “We don't sell your data” is a different and much weaker promise. You want a contractual ban on training and on humans reviewing your recordings.
5. How long is audio kept, and can we set it to zero? Real-time processing with immediate deletion is not the same as ninety-day retention with a delete button. Retention you cannot configure is retention you will have to defend in an audit.

Every question above exists because PHI is leaving your organization and landing on someone else's servers. When the audio never leaves the device, most of the analysis stops applying:

• No disclosure to a business associate, because the vendor never receives the PHI.
• No subprocessor chain to audit, because no third-party model provider is in the path.
• No retention policy to negotiate, because there is no server-side copy.
• No exposure to a vendor changing its policy later, because the model runs on hardware you control.
• Works with no network access, which matters in facilities where clinical machines are deliberately offline.

The trade-off is real and worth stating. Local models need a reasonably modern machine, the largest and most accurate ones are slower on older hardware, and you give up the convenience of a meeting bot that joins calls on your behalf. For a lot of clinical dictation that is a good trade. For high-volume ambient scribing across a large practice, it may not be.

This is the design OpenWhispr is built around, and it is the reason we think the local option matters more than any certificate we hold.

These three get bundled together in procurement conversations, and they answer genuinely different questions. Knowing which is which saves time on both sides of a security review:

• SOC 2 is a report, not a certificate. An independent auditor produces it against the Trust Services Criteria. Type I looks at how controls are designed on one date. Type II tests whether they actually worked over a period, usually three to twelve months, and it is the one worth asking for. Anyone calling themselves “SOC 2 certified” is describing a document that does not work that way.
• ISO 27001 really is a certification. An accredited body certifies an organization's information security management system against the standard, on a three-year cycle with surveillance audits. Ask for the certificate number, who issued it, and above all the scope statement, which tells you what is actually covered.
• HIPAA is a law, with no certificate at all. Compliance is an ongoing obligation you demonstrate through safeguards, policies, risk analysis, and signed BAAs. SOC 2 and ISO 27001 are good evidence that a vendor runs a serious security program. Neither one replaces a BAA.