Skip to main content
Back to Blog
HIPAA Compliance
February 12, 2026
6 min read

Does an AI Scribe Need a BAA? What It Must Include

For US practices under HIPAA, yes, before the first visit. What a BAA for an AI scribe or speech-to-text vendor must cover, and the red flags to check.

By the Transcribe Health team

Published

black iphone 5 beside brown framed eyeglasses and black iphone 5 c. Cover image for: Does an AI Scribe Need a BAA? What It Must Include.
black iphone 5 beside brown framed eyeglasses and black iphone 5 c. Photo by Dan Nelson on Unsplash

What a BAA is and why you need one before day one

A Business Associate Agreement is a legal contract between a covered entity (your practice) and any vendor that handles Protected Health Information on your behalf. Under HIPAA, this isn't optional. It's the law.

The moment an AI medical scribe processes a patient encounter, it becomes a Business Associate. It receives, creates, and transmits PHI. Without a signed BAA in place before that first transcription, both you and the vendor are in violation of HIPAA - even if nothing goes wrong.

OCR treats a missing BAA as a violation in its own right. In 2016, Raleigh Orthopaedic Clinic paid $750,000 after handing patients' x-ray films to a vendor without a BAA, and North Memorial Health Care paid $1.55 million after a contractor it had no BAA with lost an unencrypted laptop. In both cases the missing agreement was a central finding.

What your BAA must include

HIPAA specifies required elements for every Business Associate Agreement. A BAA for an AI medical scribe should cover all of them plus some AI-specific provisions:

Required by HIPAA (45 CFR 164.504(e)):

  • Permitted and required uses of PHI by the Business Associate
  • Agreement not to use or disclose PHI beyond what the contract allows
  • Requirement to implement appropriate safeguards
  • Obligation to report breaches and security incidents
  • Agreement to make PHI available to patients who request it
  • Requirement to return or destroy PHI when the contract ends
  • Agreement that subcontractors must follow the same rules

AI-specific provisions you should add (in the BAA or a companion data processing agreement):

  • Model training restrictions: Explicit prohibition on using patient data to train, fine-tune, or improve AI models
  • Data processing locations: Where audio and text data is processed and stored, including specific cloud regions
  • Third-party AI services: Disclosure of any sub-processors (cloud AI APIs, speech-to-text services) that touch PHI
  • Automated decision-making: Clarity on whether the AI makes clinical decisions or only generates documentation
  • Data minimization: Commitment to process only the minimum necessary PHI

The subcontractor problem with AI vendors

This is where many AI scribe BAAs fall short. Your vendor might have airtight security. But if they send patient audio to a third-party speech recognition API, that third party is a subcontractor - and they need their own BAA with your vendor.

Here's the chain of responsibility:

Entity Role BAA Required With
Your practice Covered Entity AI scribe vendor
AI scribe vendor Business Associate Your practice + all subcontractors
Cloud provider (AWS, GCP) Subcontractor AI scribe vendor
Third-party AI API Subcontractor AI scribe vendor

Ask your vendor directly: "Do you use any third-party services to process patient audio or generate transcriptions?" If yes, verify they have BAAs in place with every one of those services. Major cloud providers like AWS, Google Cloud, and Microsoft Azure all offer HIPAA BAAs - but the vendor must have activated them.

Some consumer AI APIs explicitly refuse to sign BAAs. If your vendor relies on one of those, your patient data is flowing through non-compliant infrastructure. Before you sign anything, it's worth understanding exactly where your patient data goes with an AI scribe and which providers sit in the processing chain.

Common BAA mistakes that expose your practice

Mistake 1: Using a template BAA without customization. Generic templates miss AI-specific concerns like model training, data processing pipelines, and automated decision-making. Work with a healthcare attorney to add these provisions.

Mistake 2: Not verifying subcontractor BAAs. Your BAA with the vendor is worthless if they're sending PHI to a subcontractor without their own agreement. You need written confirmation that the entire chain is covered.

Mistake 3: Forgetting to update the BAA. AI products evolve fast. If your vendor adds a new AI model, switches cloud providers, or starts processing data in a different region, your BAA should be updated to reflect those changes.

Mistake 4: No termination clause for data destruction. What happens to your patient data when you cancel the service? The BAA should specify timelines for data destruction and provide certification that it's been completed. This ties directly to the vendor's data retention policy for AI clinical notes - ask to see both.

Mistake 5: Not asking what happens to de-identified data. HIPAA lets a business associate de-identify PHI when its BAA permits it, and many BAAs do. Ask what the vendor then does with that data. If it feeds the vendor's own analytics or research, that may not align with your patients' expectations or your state's privacy laws, even when the de-identification meets HIPAA standards. Look for the answer in the BAA and in any data processing agreement that comes with it.

How to evaluate a vendor's BAA before signing

Before you sign, run through this checklist:

  • Does the BAA explicitly name the AI scribe service and describe how PHI will be used?
  • Is there a prohibition on using PHI for model training or product improvement, in the BAA or a companion data processing agreement?
  • Are all subcontractors identified with their own BAA status confirmed?
  • Does it specify breach notification timelines (72 hours or less)?
  • Are data retention and destruction policies clearly defined?
  • Does it address data residency - where PHI is stored and processed?
  • Is there a right-to-audit clause allowing you to verify compliance?
  • Does the termination section require certification of data destruction?

If any of these are missing, push back before signing. A vendor that's serious about compliance will welcome the scrutiny.

The BAA is one line item on a longer list. Once it's in place, walk through the full HIPAA compliance checklist for AI documentation to confirm the safeguards behind the contract are real.


Transcribe Health provides a BAA covering HIPAA requirements on every plan, and our Data Processing Agreement, which works alongside it, prohibits using patient data to train, fine-tune or improve AI models. See our compliance standards for the safeguards behind it.

That includes the Free plan. Create a free account and accept the BAA in the app before your first session. No sales call, no credit card.


This article is for informational purposes only and does not constitute legal or compliance advice. BAA requirements may vary based on your specific circumstances and applicable state laws. Consult with a qualified healthcare attorney for guidance on your Business Associate Agreements.

Frequently asked questions

Does an AI medical scribe need a BAA?
Yes. The moment an AI medical scribe receives, creates, or transmits Protected Health Information it becomes a HIPAA Business Associate, and a covered entity must have a signed Business Associate Agreement in place before the first patient encounter is processed. Using the tool without one is a HIPAA violation on its own, even if no breach ever occurs.
Is a signed BAA enough to make an AI scribe HIPAA compliant?
No. A BAA is necessary but not sufficient. It is a contract that assigns responsibility; it does not verify that encryption, access controls, audit logging, and subcontractor agreements are actually in place. Treat the BAA as the floor and still review the vendor's safeguards and subprocessor list.
Who signs the BAA, and what about the vendor's subcontractors?
Your practice (the covered entity) signs with the AI scribe vendor (the business associate). The vendor is then separately responsible for signing its own BAAs with every subcontractor that touches PHI, such as cloud hosting and any third-party AI or speech-to-text service. You should get written confirmation that the whole chain is covered.
What AI-specific clauses should a BAA for an AI scribe include?
Beyond the clauses HIPAA requires at 45 CFR 164.504(e), an AI scribe BAA, or the data processing agreement that accompanies it, should explicitly prohibit using PHI to train or improve AI models, disclose sub-processors and data-processing regions, clarify that the AI generates documentation rather than making clinical decisions, and commit to data minimization.
What happens to patient data when I cancel the service?
The BAA should require the vendor to return or destroy all PHI within a defined timeline after termination and to certify that destruction in writing. If the termination section is silent on data destruction, treat that as a red flag before signing.
Does Transcribe Health provide a BAA?
Yes. Transcribe Health signs a BAA covering the HIPAA-required elements on every plan. Our Data Processing Agreement, which works alongside the BAA, prohibits using patient data to train, fine-tune or improve AI models.
baahipaacomplianceai-scribebusiness-associate-agreement

Related Resources

Bring AI support to your clinic

Explore clinical notes, Dorvi and tools for the work around each visit. Start a 14-day free trial, with the first charge on day 15.

Start Free Trial

This article is informational and not medical or legal advice. See our medical and legal disclaimer and our editorial policy for how we research and attribute content. Consult a licensed clinician for medical decisions and a licensed attorney for regulatory interpretation in your jurisdiction.