Guides
HIPAA-Compliant AI for Psychologists: A Checklist
By JD & RebeccaApril 1, 202610 min read
"HIPAA compliant" now appears on AI scribes, chatbots, transcription services, note assistants, and report-drafting tools. Some of those vendors have done the work. Some have not.
The label itself proves little. There is no federal certification for HIPAA-compliant software and no government registry of approved AI tools. What matters is whether the vendor will sign a Business Associate Agreement (BAA) with you and whether its safeguards hold up when you ask specific questions.
This checklist applies to any AI tool that touches client data, whatever it does. Work through it before the first real client detail goes in.
The Checklist at a Glance
- BAA: the vendor signs one, on the plan you are buying, before any client data goes in.
- Retention and training use: client data is not kept longer than needed and is never used to train AI models.
- Hosting: you know where data is processed and stored, and whose SOC 2 report covers it.
- Encryption: TLS in transit and AES-256 at rest, with the versions stated.
- Access controls and audit logs: multi-factor authentication, role-based access, and a record of who accessed what.
- Tier: you are on a business or clinical plan covered by the BAA, not a consumer tier.
Then check the red flags and the questions for your type of tool.
1. A Signed BAA
Under HIPAA, a vendor that creates, receives, stores, or transmits protected health information (PHI) on your behalf is a business associate. You need a signed BAA with them before any client data goes in.
A BAA commits the vendor to:
- Use client data only to provide the service to you
- Protect it with appropriate safeguards
- Report breaches to you within the time the BAA sets (HIPAA's outer limit is 60 days from discovery)
- Require its subcontractors to meet the same obligations
- Return or destroy the data when the relationship ends
Questions to ask:
- Who signs the BAA, and when? Can you sign it at signup, or do you need to contact sales?
- Which plans does it cover? A BAA on one plan does not cover another.
- Does it cover the trial period?
- Which subcontractors handle client data, including the AI model provider, and are they covered by their own BAAs?
For psychologists, PHI in an AI workflow includes client names and identifiers, session audio and transcripts, test scores and uploaded score reports, behavioral observations, history, diagnostic impressions, and the text of reports and notes.
2. Data Retention and Training Use
Most AI tools are built on large language models run by a separate model provider. Your data may pass through both the tool vendor's systems and the model provider's.
Two questions matter most:
Is client data used to train AI models? It should never be, by the vendor or by the model provider. Get the answer in writing, in the BAA or the terms.
How long is data kept, and where? Ask separately about:
- The AI processing step. Zero Data Retention (ZDR) means the model provider does not store your inputs or outputs after processing the request. That keeps client data out of provider logs that may have weaker access controls.
- The vendor's own storage. Your reports, notes, uploaded documents, and audio are stored somewhere. Ask how long each is kept and how deletion works.
- Backups and logs. Deleted data can remain in backups and logs for a while. Ask when those copies are deleted.
Also ask how you request deletion of your data, including from subcontractors, and what happens to it if you cancel.
3. Where Data Is Hosted: Infrastructure SOC 2 vs Vendor SOC 2
SOC 2 Type II is an independent audit of security controls over a period of time. It comes up in almost every vendor conversation, and it is often described loosely.
There are two different claims:
- Hosted on SOC 2 Type II certified infrastructure. The cloud provider the vendor runs on has been audited. This covers the data centers, physical security, and the provider's own controls.
- The vendor holds its own SOC 2 Type II report. The vendor's own controls and processes have been audited.
Both can be legitimate, but they are not the same thing. A vendor hosted on audited infrastructure has not necessarily had its own controls audited. Read the claim carefully, and if a vendor says it is SOC 2 certified, ask to see the report and check whose name is on it.
SOC 2 is also not HIPAA compliance. It is a security audit. The BAA and the safeguards in this checklist still apply.
Questions to ask: In which countries is data processed and stored? Whose SOC 2 report covers it? Can you review the report or a summary under a nondisclosure agreement (NDA)?
4. Encryption in Transit and at Rest
Ask which standards the vendor uses. "Bank-level encryption" and "encrypted" without stated standards do not give you enough detail to evaluate the safeguards.
- In transit: TLS 1.2 or higher between your device and the vendor. TLS 1.3 is the current version.
- At rest: AES-256 for stored data, including uploaded files, generated drafts, audio, and backups.
- Between services: data moving between the vendor and its model provider should also be encrypted.
The HIPAA Security Rule treats encryption as an addressable safeguard, which in practice means a vendor handling client data should be able to show you it is in place.
5. Access Controls and Audit Logs
HIPAA expects you to control who can reach client information and to keep a record of access.
Check for:
- Multi-factor authentication on every account
- Role-based access, so staff see only the clients and functions they need
- Audit logs of who viewed, created, edited, exported, or deleted records, and when
- Automatic sign-out after inactivity
- Fast removal of access when a staff member leaves
- Vendor staff access: who at the vendor can see your data, under what conditions, and whether it is logged
For group practices and assessment clinics, test the permission model against your real structure: clinicians, trainees, supervisors, and billing staff.
6. Consumer vs Business Tiers of General AI Tools
Check the exact plan and features you intend to use. A vendor's BAA may cover only part of what it sells.
Consumer tiers do not include a BAA. Free and standard consumer plans of general-purpose AI chatbots and productivity apps are not covered by a BAA. Entering client details into one is a HIPAA exposure, whatever the vendor's marketing says about security.
Some vendors sign BAAs on business or API plans after review. That can make a general AI tool usable with client data, but only on the covered plan, with the settings the agreement requires, and often only for certain features. Confirm all three in writing.
Even a covered general tool is not built for clinical documentation. It has no score structure, no report sections, and no clinical review workflow. You supply all of that, every time.
"Free" and "HIPAA compliant" rarely go together for general tools. A free clinical trial is different: some clinical vendors let you sign a BAA before the trial starts.
De-identification is harder than it looks. HIPAA's Safe Harbor method lists 18 kinds of identifiers, including dates, locations, and unique characteristics. Removing a name is not enough, and in a small community a combination of clinical details can identify someone. If you cannot fully de-identify, use a tool covered by a BAA.
How the Checklist Applies by Tool Type
The six checks apply to every AI tool that touches client data. Each type also raises questions of its own.
AI scribes and session note assistants
- Is audio deleted after the note is drafted, and when?
- Is the transcript kept, and where?
- How do you record client consent to recording, and what happens if a client declines?
- Can you edit the note before it enters the record?
General-purpose AI chat
- Is your account on a plan covered by the BAA, or a consumer tier?
- Are chat history and memory features covered, or do they need to be off?
- Do other people in your organization share the workspace?
Transcription services
- Does the BAA cover the transcription service and any human reviewers it uses?
- Are files deleted after transcription, and when?
Report-drafting tools
- Is the BAA signed before you enter scores or notes, including during a trial?
- How long are uploaded score reports and drafts kept?
- Does the tool draft only from what you entered, with your review of every section?
- Does ZDR apply to every AI step, including score import?
For report-drafting tools specifically, our guide to evaluating report-writing software for HIPAA goes deeper, and the buyer's guide covers non-compliance criteria such as assessment coverage and clinician control.
Red Flags
Stop evaluating a tool if:
- The vendor won't sign a BAA, or says one isn't needed
- The BAA is only available on a plan you are not buying
- The vendor can't say which model provider processes your data
- The terms allow your data to be used for "product improvement" or model training
- Retention periods for data, files, audio, and backups are not stated
- "SOC 2 certified" turns out to mean the cloud provider, and the vendor won't clarify
- Encryption is described without standards
- There is no multi-factor authentication or audit log
- You are asked to enter real client data before the BAA is signed
- Security answers are given only verbally, never in writing
Without specific written answers, you cannot verify the vendor's security claims.
School Settings: FERPA Adds a Layer
School psychologists handle education records governed by the Family Educational Rights and Privacy Act (FERPA). Psychoeducational evaluations and the data behind eligibility decisions are education records.
- Districts usually require their own data agreement before any software touches student data, separate from a BAA.
- Student data should never be used for AI training or product improvement.
- Check your district's policy on documenting AI use in evaluations.
See our FERPA compliance overview for more.
How PsychReport Answers the Checklist
PsychReport is a report-drafting tool for psychological assessments. Here is how it answers each item:
- BAA: self-service BAA, signed at onboarding before you enter client data.
- Retention and training use: Zero Data Retention (ZDR) for all AI processing; client data is never used to train AI models.
- Hosting: hosted on SOC 2 Type II certified infrastructure.
- Encryption: TLS 1.3 in transit and AES-256 at rest.
- Access controls and audit logs: multi-factor authentication, role-based access controls, audit logs, and automatic sign-out after inactivity.
- Tier: the self-service BAA is included on every plan.
PsychReport does score entry and drafting. It does not score tests or make diagnoses, and the clinician reviews, edits and signs every report. Full details are on the security page, and our HIPAA compliance overview covers the regulatory side.
Frequently Asked Questions
What makes an AI tool HIPAA compliant?
There is no official HIPAA certification for software. In practice, an AI tool is usable with client data when the vendor signs a Business Associate Agreement (BAA) with you and has the safeguards the HIPAA Security Rule expects: encryption, access controls, audit logs, and clear rules on retention and deletion. The BAA is what makes the vendor legally accountable. A marketing badge is not.
Are free AI tools HIPAA compliant?
Consumer and free tiers of general AI tools do not include a BAA, so they should not be used with client data. Some vendors sign BAAs on business or API plans after review. A free trial of a clinical tool is different: some clinical vendors let you sign a BAA before the trial starts.
Is SOC 2 the same as HIPAA compliance?
No. SOC 2 is an independent audit of security controls. HIPAA is a law with specific obligations, including the BAA. Also check whose SOC 2 report it is: a vendor can run on SOC 2 Type II certified infrastructure without holding a SOC 2 report for its own company. Both can be legitimate, but they are different claims.
What is Zero Data Retention (ZDR)?
Zero Data Retention means the AI model provider does not store your inputs or outputs after processing the request. It keeps client information out of provider logs and out of model training. Ask whether ZDR applies to every AI step in the tool, not just some.
Can I test an AI tool with real client data before signing a BAA?
No. A signed BAA should be in place before any real client data enters the system, including during a trial. Use clearly labeled synthetic cases to test a tool until the BAA is signed.
Does removing the client's name make data safe to use in a general AI tool?
Not by itself. HIPAA's Safe Harbor method of de-identification lists 18 kinds of identifiers, including dates, locations, and other unique details, and a combination of clinical facts can still identify a person. If you cannot fully de-identify the information, use a tool covered by a BAA.
This article provides general information about HIPAA considerations for psychologists evaluating AI tools and does not constitute legal advice. Consult a qualified healthcare attorney for guidance specific to your practice and jurisdiction.
Ready to Reclaim Your Time?
Start your free trial of PsychReport.ai and experience how AI-assisted report writing can give you back hours each week.
Start Your Free Trial