HIPAA compliance checklist for AI documentation tools

Ask these before you upload a session

A session recording is about as sensitive as PHI gets. Any AI tool that stores, transcribes or summarizes it is a business associate under HIPAA, and the same rules apply to it as to your EHR.

Each item below is labeled as a HIPAA requirement or a best practice, because vendors often blur the two. Send the list to any vendor you are considering and ask for written answers. Under each item we say how MH Scribe handles it, so you have one set of answers to compare against.

The checklist

1. Business Associate Agreement (BAA)

HIPAA requirement. The vendor must sign a Business Associate Agreement, which legally obligates them to protect PHI in accordance with HIPAA. Without a BAA, using an AI tool to process patient data is a HIPAA violation. Verify that the BAA covers all aspects of data handling, including processing, storage, and deletion, and that the vendor's own subprocessors are covered too.

MH Scribe: Our BAA is part of our Terms of Service, so it is in place from signup with no separate paperwork. Every subprocessor that handles PHI (AWS, including Amazon Bedrock for AI generation, and our transcription provider) is covered by a BAA.

2. Encryption in transit and at rest

Best practice (addressable under HIPAA today). Patient data should be encrypted in transit and at rest. Under the current Security Rule, encryption is addressable: you implement it or document an equivalent alternative. A January 2025 proposed rule would make it required, but it has not been finalized. Look for modern TLS in transit and AES-256 at rest; weak or outdated protocols are a red flag.

MH Scribe: TLS encryption in transit and AES-256 encryption at rest, with AWS KMS key management.

3. Access controls

HIPAA requirement, with best-practice extras. HIPAA requires unique user IDs and access limited to authorized people, and treats automatic logoff as addressable. Best practices include multi-factor authentication (MFA), least-privilege access, and isolating each customer's data from every other account.

MH Scribe: MFA support and automatic session management via Clerk. Each clinician's workspace is isolated from every other account.

4. Audit controls and logging

HIPAA requires audit controls: mechanisms that record and examine activity in systems containing PHI. It does not prescribe exactly what to log or for how long. Logging who accessed what and when, protecting logs from tampering, and keeping them for six years are common best practices that help with investigations, not current HIPAA mandates.

MH Scribe: AWS infrastructure logging, including storage access logs and application logs. We do not currently offer an in-app audit log for customers.

5. Data retention and deletion

Best practice. The vendor should state clearly how long it keeps audio recordings, transcripts, and notes, and how deletion works, including how long deleted data can persist in backups.

MH Scribe: Session audio is deleted automatically 30 days after upload, and you can delete a recording yourself at any time before then. Notes and transcripts stay in your account until you delete them.

6. No model training on PHI

Best practice, and one of the most important for AI tools. Your patients' session data should never be used to train, fine-tune, or improve AI models. Some general-purpose AI platforms use customer data for training by default. Look for a contractual commitment that PHI is never used for model improvement.

MH Scribe: Patient data is never used to train AI models. That commitment is in our Terms of Service, which include the BAA.

7. Breach notification

HIPAA requirement. A business associate must notify you of a breach without unreasonable delay and no later than 60 days after discovery, with the information you need to notify affected patients and HHS. Sooner is better.

MH Scribe: Documented breach notification procedures. We commit to prompt notification and to supporting your investigation.

8. Workforce training

HIPAA requirement. HIPAA requires security awareness training for workforce members. Ask vendors how they train anyone who may have access to systems containing PHI, and how often.

MH Scribe: Access to production systems is limited to the founder.

9. Infrastructure certifications such as SOC 2

Best practice. HIPAA does not require any certification, but independent audits are a useful signal. A SOC 2 Type II report verifies that security controls were maintained over time. Also look at the infrastructure provider's own certifications (e.g., AWS SOC 2, ISO 27001).

MH Scribe: Hosted on AWS (SOC 2 Type II infrastructure) with US-only data residency.

10. Patient consent

Not a HIPAA requirement, but often required elsewhere. HIPAA does not require patient consent to use a business associate's tool, but many state laws require consent from everyone in a conversation before it is recorded, and professional ethics codes call for informed consent. The tool should support the consent process.

MH Scribe: A free patient consent form you can edit for your practice, plus a guide with scripts for bringing up AI notes with patients.

What a vendor cannot do for you

A signed BAA and good encryption cover the vendor's side. Your practice still owes its own risk analysis, written policies, and a record of which tools touch PHI. Add your AI scribe to that list the day you start using it.

Our infrastructure, subprocessors and access controls are listed on the Security page.

Frequently asked questions

Does a HIPAA-compliant AI scribe need to sign a Business Associate Agreement (BAA)?

Yes. A BAA legally obligates the vendor to protect PHI under HIPAA; using a vendor to process PHI without one is a HIPAA violation. MH Scribe embeds its BAA directly in the Terms of Service, so accepting the Terms at signup puts the BAA in place, with no separate paperwork. Every subprocessor that handles PHI for MH Scribe is covered by its own BAA. If a vendor calls itself HIPAA compliant but will not sign a BAA, do not use it with patient data.

Should patient data be encrypted in transit and at rest?

It should be. Under the current HIPAA Security Rule, encryption is an addressable implementation specification: you must implement it or document why an equivalent alternative is reasonable. A January 2025 proposed rule would make encryption required, but it has not been finalized. Modern TLS in transit and AES-256 at rest are widely recommended best practices. MH Scribe encrypts data in transit with TLS and at rest with AES-256, using AWS KMS key management.

What access controls should an AI documentation tool have?

HIPAA requires unique user identification and procedures that limit PHI access to authorized people; automatic logoff is addressable. Best practices include multi-factor authentication, least-privilege access, and data isolation between accounts. MH Scribe supports MFA and automatic session management via Clerk, and each clinician's workspace is isolated from every other account.

Does HIPAA require audit logging of PHI access?

HIPAA requires audit controls: mechanisms that record and examine activity in systems containing PHI. It does not prescribe exactly what to log or how long to keep logs. Logging access in detail, protecting logs from tampering, and retaining them for six years are common best practices, not current HIPAA mandates. MH Scribe relies on AWS infrastructure logging, such as storage access logs and application logs; it does not currently offer an in-app audit log for customers.

What data retention and deletion policies should the vendor have?

The vendor should tell you clearly how long it keeps recordings, transcripts, and notes, and how deletion works. MH Scribe deletes session audio automatically 30 days after upload, and you can delete a recording yourself at any time before then. Notes and transcripts stay in your account until you delete them.

Is my patient data used to train AI models?

It should not be. Look for a vendor that contractually commits never to use PHI to train, fine-tune, or improve AI models, and check the terms of any general-purpose AI platform before using it with patient data. MH Scribe never trains on patient data, and that commitment is in its Terms of Service (which include the BAA).

What breach notification procedures should the vendor commit to?

HIPAA requires a business associate to notify the covered entity of a breach without unreasonable delay and no later than 60 days after discovery, with the information needed to notify affected patients and HHS. MH Scribe has documented breach notification procedures and commits to prompt notification and investigation support.

Does the vendor train its staff on HIPAA?

HIPAA requires security awareness training for workforce members. Ask vendors how they train anyone with access to systems containing PHI. At MH Scribe, access to production systems is limited to the founder.

Should the infrastructure have certifications like SOC 2?

HIPAA does not require any certification, but independent audits are a useful signal. Look for SOC 2 Type II reports and the infrastructure provider's certifications (for example, AWS SOC 2 and ISO 27001). MH Scribe is hosted on AWS (SOC 2 Type II infrastructure) with US-only data residency.

Do I need patient consent for AI-assisted documentation?

HIPAA does not require patient consent to use a documentation tool from a business associate that has signed a BAA. However, many state laws require consent from everyone in a conversation before it is recorded, and professional ethics codes call for informed consent about how sessions are recorded and documented. MH Scribe provides a free patient consent form you can edit and a guide to introducing AI documentation to patients.