HIPAA Compliance for AI Medical Scribes: A Practical Guide

Kevin Henry

HIPAA

Published Updated

9 minutes read
Share this article
HIPAA Compliance for AI Medical Scribes: A Practical Guide

When does an AI scribe vendor need a business associate agreement?

A vendor generally needs a business associate agreement (BAA) when it creates, receives, maintains, or transmits protected health information (PHI) on behalf of a HIPAA-covered practice. An AI scribe that processes identifiable visit audio or transcripts for a practice will usually fit that role. A vendor does not avoid business associate status merely because it stores encrypted data or cannot decrypt it. HHS guidance on HIPAA and cloud computing explains that a provider processing or storing ePHI on behalf of a covered entity is a business associate.

Before sending PHI to the system, confirm that the BAA describes the scribe service and limits the vendor’s uses and disclosures to permitted purposes. If the vendor relies on cloud hosts, transcription services, or other subcontractors that handle PHI, those parties generally need downstream business associate agreements with equivalent restrictions. HHS business associate guidance describes these requirements and the required BAA provisions.

A vendor that only supplies software without handling PHI may not be a business associate for that activity. A narrow conduit exception may also apply to a service that only transmits information and stores it temporarily as needed for transmission. Assess what the vendor and its service providers actually do—not only how the product is described.

What security safeguards protect PHI used by AI scribes?

The HIPAA Security Rule requires covered entities and business associates to use appropriate administrative, physical, and technical safeguards to protect electronic PHI’s confidentiality, integrity, and availability. The rule is risk-based; it does not prescribe one product or technical configuration for every practice. HHS’s Security Rule overview summarizes the standards in effect.

Ask how the vendor manages access, monitors system activity, protects data during transmission and storage, handles security incidents, and restores information after an outage. Also review its risk-management practices, workforce controls, physical safeguards for systems and devices, and procedures for backups and secure disposal. Encryption is important, but HHS cautions that it does not replace other safeguards, such as risk analysis and protections for the systems that store the data. HHS cloud-computing guidance explains why encryption alone is not enough.

Consider whether the product supports role-based permissions, unique user accounts, audit logs, and strong authentication. These are practical review points, not a claim that HIPAA mandates a specific vendor feature in every case. Some Security Rule implementation specifications are “addressable,” which calls for an appropriate assessment and documented decision rather than automatic omission. HHS’s Security Rule summary describes the safeguards and the required-versus-addressable distinction.

Apply the minimum necessary standard where it applies: limit PHI access and use to what is reasonably needed for the purpose. The standard does not apply to disclosures between health care providers for treatment, but practices should still consider role-based access and avoid unnecessary exposure of PHI. HHS minimum necessary guidance explains the standard and its exceptions.

Visit audio can contain PHI when it identifies a patient or could reasonably be used to identify them. HIPAA does not require a practice to record oral communications or to keep recordings after transcription. If a recording is retained and used to make decisions about a patient, it may qualify as part of the designated record set. HHS guidance on oral communications explains these points.

HIPAA generally permits covered entities to use or disclose PHI for treatment, payment, and health care operations without obtaining separate patient consent, but that does not settle every question about recording a conversation. The recording’s purpose, the vendor’s role, other applicable laws, and practice policy all matter. A HIPAA notice acknowledgement is not, by itself, permission for a separate use that requires authorization. HHS guidance on consent and authorization explains the distinction.

Recording rules vary by jurisdiction. Federal law includes an exception for certain recordings when a party to the communication or one party has given prior consent, but that does not resolve stricter state requirements. For example, California Penal Code § 632 addresses recording confidential communications without the consent of all parties, subject to the statute’s definitions and exceptions. Check the laws that apply to the locations and circumstances involved.

As a practical safeguard, tell patients before recording begins that an AI scribe will capture the visit, explain what it does with the audio, and answer questions. Decide in advance how staff should respond if a patient objects, including whether a non-recording workflow is available. Have legal or compliance staff review the notice and workflow against applicable law and organizational policy.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

How to assess AI scribe data processing, retention, and sharing

Map the information the tool handles at each stage: live audio, transcript, draft note, prompts, system logs, backups, and any data sent to support teams or subcontractors. Ask where processing and storage occur, who can access the data, which downstream business associate agreements are in place, and whether information leaves the vendor’s environment for any other purpose.

Set clear contract terms for permitted processing, access, incident reporting, return or destruction of PHI, and subcontractor changes. The BAA should describe permitted uses and disclosures and address return or destruction of PHI at termination where feasible. HIPAA does not expressly require a business associate to provide security documentation or permit customer audits, so practices can negotiate those assurances as part of procurement and risk management. HHS’s BAA provisions and cloud-computing guidance explain these requirements and considerations.

Define separate retention and deletion rules for raw audio, transcripts, draft notes, and backups. HIPAA generally does not require a business associate to keep ePHI after providing its service, and the Privacy Rule says covered entities are not required to retain recordings after transcription. If recordings are retained and used to make decisions about a patient, they may be part of the designated record set. Coordinate deletion practices with your record-retention policies and other applicable laws.

Use the minimum necessary standard where applicable, and ask whether the vendor can reduce identifiers in information used for approved purposes. De-identification of health information under HIPAA must follow one of the recognized methods—Expert Determination or Safe Harbor. Simply removing a name does not automatically make a transcript de-identified. HHS de-identification guidance describes both methods.

Can AI scribe vendors use PHI to train models?

There is no blanket answer that applies to every AI scribe. A business associate may use PHI only as permitted by its BAA and the HIPAA Rules; the BAA cannot authorize a use that would violate the Privacy Rule if performed by the covered entity. A service agreement to create clinical notes should not be treated as automatic permission for the vendor to use identifiable recordings to improve a general-purpose model or for another independent purpose. HHS business associate guidance explains the limits on business associate uses and disclosures.

Before adopting a product, ask directly whether the vendor uses audio, transcripts, notes, or metadata for model training, evaluation, benchmarking, or product improvement. Require the contract to state which uses are permitted and which are prohibited, including any uses by subcontractors. If a proposed use is not otherwise permitted under HIPAA, the vendor and practice need an appropriate legal basis, such as a valid authorization where required, or properly de-identified information.

For HIPAA de-identification, the information must meet the Safe Harbor or Expert Determination method; removing a patient’s name alone is not enough. Once information is de-identified under the Privacy Rule, it is no longer PHI, though other laws or contractual restrictions may still apply. HHS guidance on de-identification explains the standard.

How should clinicians verify AI-generated medical notes?

Treat an AI-generated note as a draft, not a completed clinical record. Before approving or signing it, compare it with the encounter and correct errors, omissions, unsupported statements, and misattributed speech. Check patient identity, medications and doses, allergies, relevant negatives, examination findings, assessment, and plan—especially details that could affect care.

Practices should train clinicians and staff on the tool’s limits and establish a consistent review process before notes enter the medical record. The clinician who reviews and signs should use professional judgment rather than assume that fluent wording means the note is accurate. American Medical Association guidance on health AI advises clinicians to review AI-generated documentation and validate what they sign.

In practice, a sound program combines a BAA and clear downstream contracts with risk-based safeguards, transparent recording practices, defined data-use and retention limits, and clinician review before notes are finalized.

FAQs

Does an AI medical scribe need a business associate agreement?

Usually, yes, if the vendor creates, receives, maintains, or transmits identifiable PHI on behalf of a HIPAA-covered practice. A BAA should be in place before the vendor handles that PHI, and subcontractors that handle it generally need downstream business associate agreements.

Can an AI scribe use patient recordings to train its model?

Only when the use is permitted under HIPAA and the applicable BAA, or when the information is properly de-identified or another valid legal basis applies. Do not assume that a vendor may use identifiable recordings for general model training simply because it provides scribing services.

HIPAA does not require practices to record visits, and it generally permits certain treatment, payment, and health care operations uses without separate patient consent. Whether recording requires consent or another form of notice depends on applicable recording laws, the specific use, and practice policy. Informing patients before recording begins is a practical way to support transparency.

Who is responsible for verifying AI-generated clinical notes?

The clinician reviewing and signing the note should verify that it accurately reflects the encounter and correct errors before finalizing it. The practice should set a clear review workflow; the vendor’s contractual and legal responsibilities remain separate from the clinician’s review.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles