Skip to main content
HIPAA Compliance

HIPAA Compliance Checklist for Law Firms Using AI

By Thomas WernerPublished Last updated 11 min read

If your firm handles protected health information (PHI) for a covered entity, such as a hospital, insurer, or physician practice, HIPAA treats your firm as a business associate. You need a Business Associate Agreement (BAA) with any AI vendor that touches that PHI. If you receive records on behalf of a plaintiff, HIPAA may not bind you directly, but your duties of competence and confidentiality (ABA Model Rules 1.1 and 1.6) and protective orders call for the same safeguards.

Quick Checklist

  • Decide whether your firm handles PHI for a covered entity (then HIPAA treats you as a business associate)
  • Sign a Business Associate Agreement (BAA) with any AI vendor before uploading PHI, including for a trial
  • Confirm where the AI models run, and that PHI never leaves the vendor's BAA-covered environment
  • Confirm in writing that your data is never used to train AI models
  • Check encryption (at rest and in transit), access controls, MFA, and audit logs
  • Know the vendor's breach-notice window and its deletion timeline after you cancel
  • Write a firm policy: approved tools, prohibited tools (consumer AI apps), and who to tell about a mistake
  • Train everyone who touches medical records, and review tool use at least yearly

When HIPAA Applies to a Law Firm

HIPAA binds covered entities (health plans, health care clearinghouses, and most health care providers) and their business associates. Law firms are not covered entities. Whether HIPAA reaches your firm depends on how you got the records:

  • You represent a covered entity (for example, defense counsel for a hospital): your firm is a business associate. You need a BAA with your client, and BAAs with any subcontractor that handles the PHI, including your AI vendor (45 CFR 164.502(e), 164.504(e)).
  • You represent a patient and received records through the client's authorization: HIPAA usually doesn't bind your firm for those records. Confidentiality rules and protective orders still limit where they can go.

Either way, ABA Formal Opinion 512 (2024) on generative AI asks lawyers to understand how a tool handles client information before using it. A vendor that signs a BAA and documents its safeguards makes that straightforward.

What counts as PHI

PHI is individually identifiable health information. In litigation files that includes:

  • Medical records: diagnoses, treatments, medications, test results, physician and nursing notes
  • Identifiers: names, dates of birth, Social Security numbers, medical record numbers, addresses, phone numbers
  • Images: X-rays, CT scans, MRIs, patient photographs
  • Billing records: claims and payment history
  • Communications that contain health information

Removing names alone doesn't de-identify a record. HIPAA's Safe Harbor method removes 18 kinds of identifiers (45 CFR 164.514(b)).

The 5 Core Safeguards to Check in Any AI Tool

1. A Business Associate Agreement

A BAA is the contract that binds the vendor to protect PHI. It should require the vendor to safeguard PHI, use it only as the agreement permits, report breaches and security incidents to you within a stated time (HIPAA allows up to 60 days; many BAAs set a much shorter window), flow the same terms down to its subcontractors, and return or destroy PHI when the relationship ends.

If a vendor won't sign a BAA, don't upload PHI to it. That rules out consumer plans such as ChatGPT Free and Plus, the Claude.ai consumer apps, and the Gemini consumer app. Business tiers differ by vendor and plan, so check each one (see which legal AI tools are HIPAA compliant).

2. Encryption

Encryption is an “addressable” safeguard under the HIPAA Security Rule (45 CFR 164.312), which means you must implement it or document why an equivalent measure is reasonable. In practice, expect AES-256 at rest and TLS 1.2 or higher in transit. Properly encrypted PHI also falls under HHS's breach safe harbor.

3. Access controls

  • Unique user accounts with multi-factor authentication
  • Role-based permissions
  • Audit logs showing who accessed what and when
  • Automatic logout after inactivity
  • A clear rule on when vendor staff may access your files

4. Where the data and the AI models live

  • Where PHI is stored (a named region; US storage if your clients require it)
  • Where the AI models run, and whether PHI ever leaves the vendor's BAA-covered environment
  • Whether your data is used to train AI models (it shouldn't be, and the BAA should say so)

5. Independent security attestation

Ask for an independent security attestation such as a SOC 2 Type II report. HIPAA doesn't require one. If a vendor doesn't have one, ask how it assesses its own controls: risk assessments, access logging, and staff access policies.

15 Questions to Ask Any AI Vendor

QuestionWhat a good answer looks like
Will you sign a Business Associate Agreement (BAA)?Yes, before any PHI is uploaded, including for a trial
Is PHI encrypted at rest and in transit?Yes (for example AES-256 at rest, TLS 1.2+ in transit)
Where is data stored?A named region; US storage if your clients or protective orders require it
Where do the AI models run, and does PHI ever leave your BAA-covered environment?Models run inside the vendor's BAA-covered environment; PHI is never sent to consumer AI services
Is my data used to train AI models?No, and the contract says so
Do you have an independent security attestation, such as a SOC 2 Type II report?A current report, or a clear account of how the vendor assesses its own controls
Do you keep audit logs of who accessed PHI?Yes, retained for a stated period
What happens to my data if I cancel?A defined deletion timeline, plus deletion on request
How fast will you notify us of a security incident?A stated window in the BAA (HIPAA's outer limit is 60 days)
Do you support multi-factor authentication (MFA)?Yes
Can access be limited by role?Yes
Is data backed up, and how often?Yes, on a stated schedule, with backups covered by the same protections
Can staff at the vendor see our files?Only with your permission, and every access is logged
Can I get my files and work product out?Yes, in standard formats
Have you had a security incident involving customer data?Ask, and ask what changed afterward

If a vendor can't answer these clearly, or won't put the answers in writing, don't upload medical records to it.

Consumer Plans vs Business Plans

The same AI brand can have very different terms by plan. Consumer plans generally don't come with a BAA; some vendors offer a BAA on specific business or enterprise tiers, under specific contract terms. Before anyone at your firm uploads PHI, confirm the exact plan, the signed BAA, and which features it covers. Our comparisons go tool by tool:

VendorProduct / planBAANotes and source
OpenAIChatGPT Free, Plus, Pro, BusinessNo BAAOpenAI does not offer a BAA for these plans. OpenAI: HIPAA eligible products
OpenAIChatGPT Enterprise, Edu, ChatGPT for HealthcareBAA availableThrough OpenAI sales; covers listed functionality only. OpenAI: HIPAA eligible products
OpenAIOpenAI APIBAA availableFor eligible endpoints; requested through OpenAI. OpenAI: BAA for the API
AnthropicClaude Free, Pro, Max, TeamNo BAAAnthropic does not offer a BAA for these plans. Anthropic: BAA products
AnthropicClaude Enterprise; Claude APIBAA availableEnterprise once HIPAA is enabled by the organization; API for eligible features. Anthropic: BAA products
GoogleGemini with a personal Google accountNo BAAConsumer accounts have no BAA. Gemini in Chrome is excluded even on Workspace. Google: HIPAA Included Functionality
GoogleGemini app and Gemini in Workspace (Google Workspace)BAA availableUnder the Workspace BAA an administrator accepts; some features may be blocked. Google: HIPAA Included Functionality
Thomson ReutersCoCounsel Legal (formerly Casetext)BAA availableThomson Reuters says it maintains BAAs; covered plans and terms are not published. Thomson Reuters: legal AI data security
HarveyHarvey (enterprise agreements)BAA availablePHI use requires an executed Harvey Business Associate Addendum; covered tiers not published. Harvey Platform Agreement
LexHoundEvery plan, including single seats and the 14-day free trialBAA availableSigned before any documents are uploaded; downloadable in the app. LexHound: HIPAA compliance
As of , from each vendor's published documentation. Vendor terms change; confirm the BAA for your specific plan before uploading PHI.

A Common Mistake: The Personal-Account Workaround

An illustrative example: a paralegal forwards medical records to a personal Gmail account, then uploads them to a consumer AI app to get a quick summary. That's three separate problems: PHI sent by unencrypted email, PHI stored in a personal account with no BAA, and PHI uploaded to a consumer AI tool with no BAA. A written policy and an approved tool remove the reason to improvise.

How to Roll Out AI Safely in Your Firm

Step 1: Vet the vendor

  • Ask the 15 questions above and get the answers in writing
  • Request the BAA and any security attestation the vendor has
  • Read the privacy policy and data-handling terms

Step 2: Sign the BAA before any PHI goes in

Don't start a trial or upload sample records until the BAA is signed. (LexHound signs it before your trial starts.)

Step 3: Train your staff

  • What PHI is and why it must be protected
  • Which tools are approved
  • Which tools are prohibited: consumer AI apps without a BAA
  • Who to tell, right away, if PHI goes somewhere it shouldn't

Step 4: Write firm policies

  • Approved AI tools for medical records
  • Prohibited tools
  • How new AI vendors get vetted
  • An incident response plan
  • Annual training

Step 5: Review regularly

  • Which AI tools staff actually use
  • Audit logs from approved tools
  • Reported incidents and near misses
  • Each vendor's status: BAA still in force, security documentation current

If PHI Has Already Gone Into a Consumer AI Tool

  1. Stop: no further uploads.
  2. Delete what you can: many tools let you delete conversations or accounts.
  3. Document it: what was uploaded, when, by whom, and what you did about it.
  4. Talk to privacy counsel about your notice duties. If your firm is a business associate, the duty is to notify the covered entity you work for (45 CFR 164.410), which then decides on notice to patients and HHS.
  5. Switch to an approved tool so it doesn't happen again.

What's at Stake

Where HIPAA applies, HHS assesses civil penalties per violation, in four tiers based on culpability, with an annual cap for each provision violated; the amounts are adjusted for inflation each year (45 CFR 160.404). See HHS's enforcement pages for current figures. Where it doesn't, confidentiality rules and protective orders still apply.

Conclusion: Protect PHI Before You Upload It

HIPAA (where it applies), your duty of confidentiality under ABA Model Rule 1.6, and ABA Formal Opinion 512 on generative AI all point the same way: use AI tools that sign a BAA, keep PHI in a protected environment, and verify what the tool produces.

Try LexHound With a BAA From Day One

LexHound signs a BAA with every customer, including for the 14-day free trial. Zero data egress; your data is never used to train AI models.

This checklist is educational content, not legal advice. Talk to your own privacy counsel about your firm's obligations.

Frequently Asked Questions

Is a law firm a HIPAA covered entity?

Usually not. Covered entities are health plans, health care clearinghouses, and most health care providers. A law firm that handles protected health information for a covered entity, such as defense counsel for a hospital, is a business associate and needs BAAs with the vendors that touch that PHI.

Do plaintiff attorneys need to follow HIPAA?

Often HIPAA does not bind a plaintiff's firm directly for records received through the client's authorization. Confidentiality duties under ABA Model Rule 1.6 and any protective order still apply, so the same safeguards make sense, including a BAA with your AI vendor.

Can I use ChatGPT with medical records?

Not the consumer plans: they don't come with a BAA. Some vendors offer business tiers with a BAA; check the specific plan and contract before uploading any PHI.

What should a BAA with an AI vendor include?

Permitted uses of PHI (and no training on it), required safeguards, breach and incident notice to you within a stated time, flow-down to subcontractors such as the cloud provider, and return or destruction of PHI when the relationship ends.

What should a firm do if PHI was uploaded to a consumer AI tool?

Stop further uploads, delete the data where the tool allows it, document what happened, and talk to privacy counsel. If your firm is a business associate, your notice duty runs to the covered entity you work for (45 CFR 164.410).