Is an AI Scribe HIPAA Compliant? A BAA and Consent Checklist Before Go-Live

No AI scribe is "HIPAA compliant" in the sense of being certified; HHS does not certify products. A practice can use one lawfully when the vendor signs a business associate agreement covering the service, the practice has done its own risk analysis, and consent, retention and access settings are decided and documented before the first patient.

That framing changes the buying question. "Is it compliant?" has no clean answer, and vendor pages that say "HIPAA compliant" in large letters are describing their own controls. The useful question is a checklist: does this vendor, for this product and plan, sign a BAA, and have we done what a BAA does not do for us? A good vendor answer to each item is a document, a named setting or a clause number; a weak one is an adjective.

Follow me on Instagram@sagnikteaches

The BAA is the gate, and what it does and does not do

A business associate agreement is the contract HIPAA requires when a vendor creates, receives, maintains or transmits protected health information on your behalf. HHS's cloud-computing guidance says a covered entity may use a cloud service for electronic protected health information provided it enters a HIPAA-compliant BAA with the provider and otherwise complies with the rules. The same guidance says a provider that stores only encrypted data, with no key, is still a business associate. So a scribe vendor cannot argue its way out by saying "we cannot read it".

Connect on LinkedInSagnik Bhattacharya

No BAA, no patient audio. That is the rule for go-live. It is also worth being clear about what the BAA leaves with you. The agreement does not make the product accurate, it does not do your risk analysis, it does not write your policies, and it does not cover features or plans it does not name. HHS's guidance expects you to understand the cloud environment well enough to run your own risk analysis and risk management, and to check that service-level terms are consistent with the BAA and do not stop you accessing your own data.

Subscribe on YouTube@sagnikteaches

Three practical points before you sign.

• Which product and plan does the BAA cover? A vendor may offer a BAA only on its paid or enterprise plan, or only for certain features. A BAA that covers the scribe but not the "chat with your notes" add-on leaves a gap.
• Who signs? The BAA must be signed by someone with authority to bind your practice, not a clinician clicking through a trial.
• Is it a standing agreement or a click-through? Either can be valid; keep a copy with the date and the version.

Why "compliant" is not a certification, and what to ask for instead

Vendors often point to SOC 2, HITRUST or ISO 27001 reports. These are useful evidence about security controls, and a practice can reasonably ask for the report summary under a non-disclosure agreement. They are not a HIPAA certificate, and none replaces a BAA. Treat them as inputs to your risk analysis: what was in scope, what period it covers, and whether the scribe service itself was in scope.

An illustrative contrast. Vendor A says "HIPAA compliant" and supplies nothing else. Vendor B supplies a BAA, a security-report summary scoped to the scribe, a subprocessor list, a retention schedule and a named contact for incidents. Vendor B has not proved it is safe, but you have something to assess. Vendor A has given you a slogan.

The pre-go-live checklist, in order

Run these ten checks before the first live patient. Where an answer is "not yet", the scribe stays in test mode with no real patient data.

1. BAA signed for this product and plan. Filed, dated, covering all features you will switch on.
2. Model-layer coverage. The vendor names the AI model providers it uses and confirms they are covered by agreements that flow down. Ask whether any model provider retains prompts or audio, and for how long.
3. No training on your data. Written confirmation that audio, transcripts and notes are not used to train models, by contract rather than a user setting.
4. Retention and deletion. What happens to audio, transcripts and drafts, how long each is kept, and how deletion is done and proved. Many practices prefer audio deleted as soon as a note is generated.
5. Access controls. Individual logins, multi-factor authentication, role-based access, and an audit log you can export.
6. Minimum necessary. The scribe captures what is needed for the note. Check whether you can pause or discard parts of a recording, and whether the product ingests more than the consultation (for example, pulling a whole chart).
7. Consent and notice. A decision on how patients are told or asked, plus a script, a notice and a record in the chart.
8. Clinician review. Every note is read and signed by the clinician before it enters the record, and the workflow makes that impossible to skip.
9. Incident process. The BAA states how fast the vendor tells you about a breach, and you have a named person and plan on your side.
10. Your own paperwork. Risk analysis updated to include the scribe, staff trained, policy amended, and an exit plan for retrieving data if you leave.

The tutorial on AI scribe security: audio, retention and BAA vendor questions expands items two to five into a question list for a vendor call. Here the aim is the gate and the order.

Model-layer coverage: the question vendors skip

Many scribes are built on a third-party AI model. The consultation audio may pass through a speech-to-text service and then a language model, and each is a potential business associate of the vendor. HHS's guidance says a business associate that subcontracts with a cloud provider to handle protected health information makes that provider a subcontractor business associate. So the chain needs agreements at each link.

Ask three questions in writing. Which companies process my audio and text, in order? Is there a BAA, or equivalent agreement, at every link? Does any of them retain content or use it for training? A good answer names the providers and states the agreements. A weak answer says "we use enterprise-grade AI". An illustrative failure: a vendor with a signed BAA uses a model provider under standard consumer-grade terms for a "summary polish" step, so transcripts leave the covered chain. The BAA looked fine, but one feature broke it. This is why the "which features does the BAA cover" check matters.

De-identification claims: read them sceptically

Some vendors say they de-identify data before processing. HIPAA recognises two de-identification methods: Safe Harbor, which removes 18 specified types of identifiers and requires that the covered entity has no actual knowledge the remainder could identify an individual, and Expert Determination, where a person with appropriate statistical and scientific expertise determines, and documents, that the risk of re-identification is very small. A claim that the vendor "strips names" is neither of those.

Consultation audio is hard to de-identify. People say names, workplaces, towns, relatives' names and dates, and a voice is itself an identifier in practice. A transcript that replaces "Mrs [name]" can still leave the story identifying. So treat any de-identification feature as an extra safeguard, not a reason to skip the BAA. A good vendor answer says which method is used, where in the pipeline, and what the error rate is. If the answer is vague, assume no de-identification for the purpose of your risk analysis.

Minimum necessary in an ambient scribe

HIPAA's minimum necessary standard asks you to limit uses and disclosures of protected health information to what is needed for the purpose, with exceptions such as disclosures to a health care provider for treatment. An ambient scribe records everything in the room, so apply the idea to the settings. Can the clinician pause recording for a sensitive part of the consultation? Can a family member's conversation be excluded? Does the product pull the chart, and if so which parts? Can you switch off features you do not need, such as sharing notes to a patient portal or a "memory" of previous visits?

A worked example, illustrative. A four-clinician primary care practice reviews a scribe's settings and finds three defaults it does not want: audio retained for 30 days, a transcript search feature visible to all staff, and a "learns your style" feature that keeps previous notes. It asks the vendor to set audio deletion at note generation, restrict transcript search to the treating clinician, and disable style learning until covered by the BAA. The vendor agrees to two and refuses one, so the practice keeps style learning off. The checklist did its job: it turned a product's defaults into the practice's decisions.

Consent: what the law asks and what trust asks

HIPAA permits a covered entity to use and disclose protected health information for treatment, payment and health-care operations without a separate patient authorisation, and a business associate working under a BAA fits within that. So HIPAA by itself does not say "get consent for the scribe". Other rules often do. Recording laws vary: some places require the consent of everyone recorded, so a clinician recording a consultation without telling the patient may break the law regardless of HIPAA. Professional bodies and some state rules add expectations. And patient trust matters in practice: a patient who discovers a recording they were not told about may not come back.

A sensible default for a small practice is to tell every patient and ask for agreement, every time, with an easy opt-out. A script of the kind used in clinics (illustrative): "We use a tool that listens to our conversation and drafts my notes. I read and correct every note. The audio is deleted after the note is created. Are you happy for me to use it today? Saying no will not change your care." The practice notes the answer in the chart. For the longer rollout question, see how to roll out an AI scribe without losing patient trust.

Special cases need a rule before go-live: minors, patients who lack capacity, interpreters on the call (a third person's voice and a second language), sensitive consultations such as mental health, sexual health or safeguarding, and visits with a family member present. A simple policy is: scribe off by default for these, on only if the clinician judges it appropriate and the patient agrees.

Retention, access and the exit plan

Four questions about time. How long is the audio kept? How long are transcripts and draft notes kept? How long do logs stay? And what happens to everything when you stop paying? The best answer for audio is "deleted when the note is generated or within a short, configurable window". The best answer for the final note is that it lives in your record system, not the scribe vendor's.

Ask for an export in an open format, and test it before go-live by exporting a dummy encounter. Ask also what the vendor does with data at termination, and whether deletion is certified in writing. HHS's guidance notes that a BAA must require the vendor to return or destroy protected health information at the end of the contract where feasible, and that the service terms must not stop you getting at your own data.

A two-week pilot before real patients

Do not go live in one step. Run a structured pilot.

1. Days 1 to 3, synthetic encounters. Staff role-play consultations with invented patients. Check the notes for accuracy, check what is stored, check deletion works, and try to break the review step.
2. Days 4 to 7, one clinician, consenting patients. One clinician, the full consent script, a daily sample of notes checked against the clinician's memory.
3. Days 8 to 14, the rest of the team, if the error rate and consent log look right.

Count errors in categories: wrong drug or dose, a negative turned positive, a missing allergy, an invented finding, a wrong side or site. Any invented finding or wrong dose triggers a review before you continue. A pilot with ten patients per clinician is a modest sample, so treat it as a way to find process faults, not as proof of accuracy.

Comparing two vendor replies side by side

An illustrative comparison shows how the checklist sorts vendors. A small paediatric practice sends the eight questions to two scribe vendors and fills in a grid.

Vendor A may be perfectly decent, but every answer is a phrase rather than a fact, and "not by default" means a setting exists that someone could change. Vendor B has handed the practice something it can file with its risk analysis. Note what the grid does not tell you: nothing in it says which scribe writes the more accurate note. That is what the pilot is for.

A realistic error and how the review step catches it

An illustrative case for the pilot log. During a consultation the clinician says, "no known drug allergies, but she had a rash on penicillin as a child, so I'll note that as an intolerance to confirm." The draft note reads "No known drug allergies" and drops the penicillin rash. The clinician, reading the draft before signing, notices the omission and adds the entry. In the pilot log the error is classed as "missing allergy", the highest-severity category, and counted.

The lesson is in the process rather than the product. Any scribe will occasionally drop or distort an item, so the safeguard is a review step that cannot be skipped and a habit of checking allergies, medicines, doses and the plan first. Build the note layout so those fields appear at the top of the draft, and make sign-off a deliberate click. If a clinician stops reading drafts carefully after a few good weeks, that is the moment the risk is highest, so audit a random sample each month and compare it with the clinician's own recollection.

Vendor questions to send in writing

Email these to every vendor on your shortlist and compare answers side by side. Ask for replies in writing and keep them with your BAA.

• Will you sign a BAA for this product and plan, and does it cover every feature we intend to use?
• Which AI model and speech providers process our data, and do agreements flow down to each?
• Is our data used to train or improve any model, yours or a provider's?
• Where is data stored, how long is audio kept, and how is deletion done and proved?
• What security reports can you share, and did they cover this product?
• What is your breach notification time, and who do we contact?
• Can we export notes and logs, and what happens to our data when we leave?
• What de-identification method, if any, do you use?

If the answers come back vague, that is information. The comparison tutorial on what AI scribes cost small clinics helps once you have a shortlist that passes.

How to tell your go-live is safe enough

You have a signed BAA that names the product, a model-layer answer in writing, a consent script and a chart field to record it, a retention setting you chose, a tested export, a risk analysis that mentions the scribe, and a named person for incidents. You have run synthetic and limited pilots and counted errors. If any item is missing, you are not ready, and the answer to "is it compliant" for your practice is "not yet". This tutorial is practical guidance, not legal advice; have a qualified adviser review your BAA and policies.

If it would help to run this checklist against a specific vendor with someone, my AI implementation consultation covers that. Otherwise, send the eight vendor questions today and see who answers properly.

Questions practices ask before go-live

Is there a HIPAA certification an AI scribe can hold?

No. HHS does not certify products as HIPAA compliant. A vendor can say its service supports compliance, sign a business associate agreement and pass a security audit such as SOC 2 or HITRUST, but the practice still owns its own risk analysis and policies.

Do we need patient consent to use an AI scribe?

HIPAA does not itself require a separate consent for a business associate to process records for treatment and operations. Recording laws, state rules, professional guidance and your own notice may still require telling patients or getting permission, so check those and record the decision.

Does 'de-identified' mean we can skip the BAA?

Only if the data is de-identified under HIPAA's own Safe Harbor or Expert Determination methods. A vendor's statement that it removes names is not the same thing, and audio of a consultation contains voices and details that are hard to strip. Ask for the method in writing.

What if the scribe vendor uses another company's AI model?

Then that model provider is a subcontractor, and the vendor's BAA must flow down to it. Ask who the model provider is, whether it has its own BAA with the vendor, and whether it keeps or trains on your data.

Further reads

• What Is an AI Scribe and How Does It Work in a Consultation? — How a scribe works inside a consultation.
• Is an AI Scribe Worth It for a Small Private Clinic? — Whether a scribe pays off for a small private clinic.
• HIPAA-Compliant AI Assistants for a Medical Office: BAA by Plan — BAA position by plan for general assistants.
• HIPAA-Compliant AI Receptionist: A BAA and Retention Checklist — The same checks for an AI receptionist.
• AI Usage Policy for a Medical Practice: Template and HIPAA Rules — A usage policy to sit behind the checklist.
• AI Dictation Software for Doctors: Dictation or Ambient Notes? — Dictation or ambient notes: which suits your practice.
• Heidi Health for Dentists: Setup, Templates and Patient Consent — A step-by-step Heidi setup for a dental practice: the plan to start on, template tweaks, getting notes into the PMS, and patient consent wording.
• AI Charting for Dietitians: Drafting ADIME Notes With a Review Step — Draft Assessment, Diagnosis, Intervention and Monitoring notes with AI, then check each line before it enters the record.
• AI Scribe Consent Form: US Wording and State Recording Laws — Template wording for an AI scribe consent form, a plain map of one-party and all-party recording states, and an opt-out that still gets the patient seen.
• AI Scribe for Chiropractors: Chiro Tools vs Heidi and Jane — Chiro-specific scribes against Heidi and Jane for SOAP notes, with prices, a 90-second review routine and the payer documentation points a scribe can miss.
• Is ChatGPT HIPAA Compliant? Free, Business and Clinician Plans — Which ChatGPT plans can sign a BAA, which cannot, and the do-not-paste rules to give your front desk and clinicians.
• Is Claude HIPAA Compliant? Which Plans Offer a BAA — A plain plan-by-plan table of where Claude can sign a BAA, who has to click accept, and what stays outside the agreement.
• Jane App for Chiropractors: The AI Scribe and Online Booking — Step-by-step set-up for Jane's AI Scribe (five free notes a month, unlimited add-on) and online booking in a chiropractic clinic.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: HHS guidance on HIPAA and cloud computing (business associates, encrypted data, no-view services, return or destruction at termination); 45 CFR 164.502, 164.506 and 164.514 on eCFR (checked November 2026).