HIPAA Compliance Checklist for Law Firms Using AI
Critical Warning for Attorneys
73% of law firms use non-HIPAA-compliant AI tools (ChatGPT, Claude.ai, Gemini) with medical records. Each medical record uploaded to non-compliant tools is a potential HIPAA violation with penalties ranging from $100 to $50,000 per record. A single case with 1,000 pages of medical records = $100,000 to $50,000,000 in potential exposure.
What Is HIPAA and Why It Applies to Legal AI
HIPAA (Health Insurance Portability and Accountability Act) is a federal law protecting the privacy and security of Protected Health Information (PHI). When attorneys handle medical records in medical malpractice or personal injury cases, they become covered entities under HIPAA and must comply with its requirements.
What Qualifies as Protected Health Information (PHI)
PHI is any health information that can identify an individual. This includes:
- Medical records: Diagnoses, treatments, medications, test results, physician notes, nursing documentation
- Identifying information: Patient name, date of birth, Social Security number, medical record number, address, phone number
- Images: X-rays, CT scans, MRIs, photographs of patients
- Billing records: Insurance claims, payment history
- Communications: Emails, texts, or messages containing patient health information
Critical point: Even with patient consent to use their medical records in litigation, attorneys must still protect PHI from unauthorized disclosure under HIPAA.
The 5 Core HIPAA Requirements for AI Tools
1. Business Associate Agreement (BAA)
Any third party that handles PHI on behalf of a covered entity must sign a BAA. This legally binding contract requires the vendor to:
- Implement safeguards to protect PHI
- Report any data breaches within 60 days
- Not use or disclose PHI except as permitted by the agreement
- Return or destroy PHI when the relationship ends
If an AI vendor refuses to sign a BAA, you CANNOT use their tool with medical records. Period. This immediately disqualifies ChatGPT Free/Plus, Claude.ai (web interface), Gemini, and most consumer AI tools.
2. Encryption
HIPAA requires PHI to be encrypted both:
- At rest: Stored data must be encrypted on servers (AES-256 standard)
- In transit: Data moving between your computer and vendor servers must use TLS/SSL encryption
3. Access Controls
Only authorized individuals should access PHI. Requirements include:
- User authentication (passwords, multi-factor authentication)
- Role-based permissions (paralegals see different data than attorneys)
- Audit logs tracking who accessed what data and when
- Automatic logout after inactivity
4. Data Residency and Third-Party Access
You must know:
- Where PHI is physically stored (US data centers preferred for legal compliance)
- Whether vendor uses third-party LLMs (OpenAI, Anthropic, Google) that may access your data
- Whether data is used for AI training (HIPAA violation if PHI trains public models)
5. SOC 2 Type II Certification
SOC 2 Type II is an independent audit verifying vendor security controls over a 6-12 month period. While not legally required for HIPAA, it's considered best practice and provides assurance that vendor actually implements claimed security measures.
15-Point Vendor Evaluation Checklist
Before uploading medical records to any AI tool, ask vendors these questions:
| # | Question | Required Answer |
|---|---|---|
| 1 | Do you offer a Business Associate Agreement (BAA)? | ✅ YES (free, included) |
| 2 | Is PHI encrypted at rest and in transit? | ✅ YES (AES-256 + TLS) |
| 3 | Where is data physically stored? | US data centers preferred |
| 4 | Do you use third-party LLMs (OpenAI, Anthropic, Google)? | ❌ NO third-party LLMs |
| 5 | Is my data used to train AI models? | ❌ NO training on customer data |
| 6 | Are you SOC 2 Type II certified? | ✅ YES (verify report date) |
| 7 | Do you provide audit logs showing who accessed PHI? | ✅ YES (downloadable logs) |
| 8 | What happens to my data if I cancel my subscription? | Immediate deletion (verify timeline) |
| 9 | How do you handle data breaches? | 60-day notification per HIPAA |
| 10 | Do you support multi-factor authentication (MFA)? | ✅ YES |
| 11 | Are role-based access controls available? | ✅ YES (attorney vs paralegal permissions) |
| 12 | Is data backed up? How often? | Daily backups minimum |
| 13 | Do you have cyber insurance covering HIPAA breaches? | ✅ YES (ask coverage amount) |
| 14 | Can I export my data at any time? | ✅ YES (full export capability) |
| 15 | Have you ever had a HIPAA violation or data breach? | ❌ NO (verify independently) |
Red flag: If vendor cannot answer these questions clearly or refuses to provide documentation, do NOT use their tool with medical records.
Common AI Tools: HIPAA Compliance Status
| AI Tool | HIPAA Compliant? | Notes |
|---|---|---|
| ChatGPT Free/Plus | ❌ NO | No BAA. OpenAI does NOT offer HIPAA compliance for consumer plans. Enterprise plan costs $60K+/year and requires custom contract. |
| Claude.ai (web) | ❌ NO | No BAA for web interface. Anthropic API offers HIPAA compliance for enterprise customers only. |
| Google Gemini | ❌ NO | No BAA. Google Workspace Enterprise with Gemini add-on required for HIPAA ($30/user/month minimum). |
| Casetext CoCounsel | ❌ NO | Thomson Reuters does NOT offer BAA. Not HIPAA compliant at any price. |
| Harvey AI | ⚠️ UNCLEAR | Claims HIPAA compliance for enterprise customers, but uses third-party LLMs. Verify BAA and data handling. |
| LexHound | ✅ YES | BAA included free with all plans. Zero data egress. No third-party LLM access. Google Cloud HIPAA-compliant infrastructure. |
Real-World HIPAA Violation Scenarios
Scenario 1: The ChatGPT Medical Chronology
What Happened:
Solo practitioner uploaded 800 pages of medical records to ChatGPT to "summarize key findings." ChatGPT generated helpful chronology. Attorney used it for trial prep.
HIPAA Violation:
- No BAA with OpenAI = unauthorized disclosure of PHI
- 800 pages × average 5 patient identifiers per page = 4,000 potential violations
- Penalty range: $400,000 (if $100/violation) to $200,000,000 (if $50,000/violation)
Additional Exposure:
Client can sue attorney for negligent handling of PHI. State bar may file ethics violation for breach of client confidentiality.
Scenario 2: The Email Forward to Non-Compliant AI
What Happened:
Paralegal forwarded medical records via email to personal Gmail account, then uploaded from Gmail to Claude.ai for analysis.
HIPAA Violations (Multiple):
- Forwarding PHI to personal email (unencrypted) = violation #1
- Storing PHI in personal Gmail (no BAA) = violation #2
- Uploading to Claude.ai (no BAA) = violation #3
How to Implement HIPAA-Compliant AI in Your Firm
Step 1: Conduct Vendor Due Diligence
- Request BAA from AI vendor (should be provided immediately, no negotiation)
- Request SOC 2 Type II audit report (verify date within last 12 months)
- Review vendor's privacy policy and data handling procedures
- Ask the 15 questions from checklist above
Step 2: Execute BAA Before Uploading Any PHI
Do NOT start free trial or upload sample records before BAA is fully executed. One record uploaded before BAA = HIPAA violation.
Step 3: Train Staff on HIPAA Requirements
All staff handling medical records must understand:
- What PHI is and why it must be protected
- Which tools are HIPAA-compliant (approved list)
- Which tools are prohibited (ChatGPT, Claude.ai, Gemini, etc.)
- How to report suspected HIPAA violations
Step 4: Implement Firm Policies
Create written policies covering:
- Approved AI tools for medical record analysis
- Prohibited tools
- Process for vetting new AI vendors
- Incident response plan if HIPAA violation suspected
- Annual HIPAA training requirement for all staff
Step 5: Monitor and Audit
Quarterly review:
- Which AI tools staff are using (survey or monitoring)
- Audit logs from compliant AI tools (who accessed what PHI)
- Any reported incidents or close calls
- Updates to vendor compliance status (BAA still active? SOC 2 current?)
What to Do If You've Already Used Non-Compliant AI
If you've already uploaded medical records to ChatGPT, Claude, or other non-compliant tools:
- Stop immediately: Do not upload any additional PHI
- Delete data if possible: Many tools allow account deletion (ChatGPT has data deletion option)
- Document the incident: When it happened, what data was exposed, remediation steps taken
- Consult HIPAA compliance counsel: Determine if self-reporting to OCR (Office for Civil Rights) is required
- Implement compliant alternative going forward: Switch to HIPAA-compliant legal AI tool
Do NOT self-report unless legally required or advised by counsel. Not all HIPAA violations require self-reporting. Consult with healthcare privacy attorney before reporting to OCR.
Conclusion: HIPAA Compliance Is Non-Negotiable
HIPAA compliance isn't optional or overly cautious—it's a legal requirement with severe financial and professional consequences for violations. The convenience of ChatGPT or Claude is not worth:
- $100-$50,000 per record in penalties
- Malpractice lawsuits from clients
- State bar discipline
- Reputation damage
Fortunately, HIPAA-compliant AI tools exist that provide the same capabilities (medical chronology, document analysis, timeline reconstruction) without the compliance risk. Choose tools with BAA, SOC 2, and proven HIPAA track records.
Use HIPAA-Compliant AI Risk-Free
LexHound includes a signed BAA and zero data egress with every plan. Start your free trial with zero HIPAA risk.