CASETEXT IS NOT HIPAA COMPLIANT
If you upload medical records with PHI (Protected Health Information) to Casetext CoCounsel, you are violating HIPAA.
Thomson Reuters does NOT sign BAAs for Casetext at any price point
Penalties: $100 - $50,000 per violation
Risk: Malpractice exposure, bar discipline, client lawsuits
Short Answer: No. Casetext CoCounsel (owned by Thomson Reuters) is NOT HIPAA compliantand Thomson Reuters does not offer Business Associate Agreements (BAAs) for Casetext users at any subscription tier. Using Casetext CoCounsel with medical records containing Protected Health Information (PHI) violates HIPAA and exposes attorneys to penalties of $100-$50,000 per violation. This applies to ALL Casetext plans, including enterprise accounts. There is no HIPAA-compliant version of Casetext available.
The Casetext HIPAA Compliance Problem
Casetext CoCounsel is one of the most popular legal AI tools, trusted by thousands of attorneys for legal research, document review, and brief writing. Many attorneys assume that "if major law firms use Casetext, it must be HIPAA compliant." However, Casetext is NOT HIPAA compliant, and Thomson Reuters has made no public commitment to offering HIPAA compliance for Casetext at any price.
Why Casetext Is NOT HIPAA Compliant
No Business Associate Agreement (BAA) Available
Thomson Reuters does not sign BAAs for Casetext CoCounsel at any subscription level. Without a BAA, using Casetext with PHI is a HIPAA violation, regardless of how expensive your Casetext subscription is.
No HIPAA Compliance Certification
Casetext's Terms of Service and Privacy Policy do not mention HIPAA compliance. There is no SOC 2 Type II certification publicly disclosed for Casetext. Thomson Reuters has not stated that Casetext is HIPAA-ready.
Third-Party LLM Usage
Casetext CoCounsel uses third-party large language models (LLMs), including OpenAI's GPT-4. Documents you upload to Casetext may be processed by external AI providers without HIPAA protections.
No Audit Trails or Breach Notification
HIPAA requires detailed audit logs showing who accessed PHI and when, plus breach notification procedures. Casetext does not provide HIPAA-compliant audit trails or breach notification.
Unknown Data Retention Policies
HIPAA requires specific data retention and deletion timelines. Casetext's data retention policy for uploaded documents is not publicly documented in a HIPAA-compliant manner.
Real-World HIPAA Violation Scenario
Example: Personal Injury Firm Using Casetext CoCounsel
Firm: Mid-size personal injury firm (8 attorneys)
Action: Uploads 10,000 pages of medical records to Casetext CoCounsel for document review
Casetext Subscription: Enterprise plan at $150/user/month = $14,400/year
Reasoning: "We pay $14K/year for Casetext. It must be enterprise-grade and HIPAA compliant."
HIPAA Violations:
- No BAA with Thomson Reuters = violation (at any price)
- 10,000 pages with patient PHI = 10,000 separate violations
- Documents processed by third-party LLMs = additional PHI disclosure
- No audit trails = cannot prove HIPAA compliance
Penalty Exposure: $1,000,000 - $500,000,000 (assuming OCR charges minimum $100/page)
Additional Risks:
- Client can sue firm for exposing their medical records
- Bar discipline for all 8 attorneys (ethics violation)
- Reputation damage: "Law firm leaked medical records to Thomson Reuters AI"
- Malpractice insurance may deny coverage (intentional violation)
- Opposing counsel could file motion to disqualify entire firm
Why Doesn't Thomson Reuters Offer a BAA for Casetext?
Thomson Reuters has not publicly stated why they don't offer HIPAA compliance for Casetext. Possible reasons include:
Third-Party LLM Dependencies
Casetext uses OpenAI's GPT-4 and other third-party models. Achieving HIPAA compliance would require BAAs with every AI provider, which may be technically or economically infeasible.
Infrastructure Not HIPAA-Ready
HIPAA compliance requires specific security controls (encryption at rest and in transit, audit logging, breach notification, data segmentation, etc.). Casetext's infrastructure may not be designed for HIPAA compliance.
Cost-Benefit Analysis
Achieving and maintaining HIPAA compliance is expensive. Thomson Reuters may have determined that the healthcare legal market segment is not large enough to justify the investment.
The HIPAA-Compliant Alternative: LexHound
LexHound is the only legal AI platform built specifically for attorneys handling PHI, with full HIPAA compliance from day one and more advanced document analysis features than Casetext.
| Feature | Casetext CoCounsel | LexHound |
|---|---|---|
| HIPAA Compliant | No (at any price) | Yes |
| Business Associate Agreement (BAA) | Not offered | Included free |
| Subscription | $65-$150/user/month | $999/seat/month ($8,999/seat/year) |
| Cost per case (20 cases/year, 1 seat) | $539 - $1,090 | $450 - $599 (unlimited docs) |
| Per-Document Fees | $10-20 per document | $0 (unlimited) |
| Medical Chronology | Manual extraction | Automatic (10 min) |
| Timeline Reconstruction | No | Yes |
| Graph RAG (Entity Relationships) | No (keyword only) | Yes |
| Document Search Method | Keyword search | Graph RAG (finds relationships) |
| Medical Terminology Understanding | General AI | Medical-specific training |
| Third-Party LLMs | Yes (OpenAI GPT-4) | No (Google Vertex AI only) |
| Data Egress Outside Secure Boundary | Yes (multiple providers) | Never (stays in GCP) |
| Safe for Medical Records | No (HIPAA violation) | Yes |
Cost Comparison: Casetext vs LexHound
Personal Injury Practice (20 cases/year, one analyst seat)
Casetext CoCounsel
- Subscription (1 seat): $65-$150/user/month ($780 - $1,800/year)
- Per-Document Fees: $10-20 per document
- 20 Cases (avg 50 docs each): +$10,000 - $20,000
- Total Annual Cost: $10,780 - $21,800
- Cost Per Case: $539 - $1,090
- HIPAA Compliance: NOT COMPLIANT
LexHound
- Subscription (1 seat): $999/month ($8,999/year on annual billing)
- Per-Document Fees: $0 (unlimited)
- 20 Cases (unlimited docs): $0 additional
- Total Annual Cost: $8,999 - $11,988
- Cost Per Case: $450 - $599
- HIPAA Compliance: FULLY COMPLIANT
Lower cost per case with no per-document fees—and you stay fully HIPAA compliant (priceless for avoiding violations). Casetext offers no BAA at any price.
What Attorneys Should Do
Use Casetext for Legal Research (No PHI)
Casetext is excellent for legal research, case law analysis, and brief writing as long as you don't upload any documents containing PHI. Use Casetext for contracts, appellate work, and non-medical litigation.
NEVER Upload Medical Records to Casetext
Every medical record you upload to Casetext is a HIPAA violation. "We pay for Enterprise Casetext" does NOT mean "Casetext is HIPAA compliant." Thomson Reuters does not offer HIPAA compliance at any price.
Use LexHound for Medical Records Analysis
For medical malpractice, personal injury, or any case with medical records, use LexHound. You get full HIPAA compliance, more advanced features (Graph RAG, medical chronology), and pay less than Casetext Enterprise.
Frequently Asked Questions
Will Thomson Reuters add HIPAA compliance to Casetext in the future?
Thomson Reuters has not publicly announced plans to make Casetext HIPAA compliant. As of 2026, there is no indication that HIPAA compliance is on their roadmap. Do not use Casetext with medical records in hopes that "it will be HIPAA compliant someday."
Can I request a custom BAA from Thomson Reuters for Casetext?
You can ask, but Thomson Reuters does not offer custom BAAs for Casetext at any subscription level. Multiple law firms have requested BAAs and been denied. The infrastructure is simply not HIPAA-ready.
What if my firm already uploaded medical records to Casetext?
Stop immediately. Do not upload any more medical records. Delete documents containing PHI if possible. Consider consulting with a HIPAA compliance attorney about your exposure. Switch to LexHound for all future work involving PHI.
Does Casetext use my documents to train their AI?
Casetext's privacy policy states they may use uploaded documents to improve their services, which could include AI training. This is another reason NOT to upload medical records—your client's PHI could become part of Casetext's training data.
Can I use Casetext if I anonymize medical records first?
True anonymization (removing all 18 HIPAA identifiers) is extremely difficult and time-consuming. Most attorneys attempting to "anonymize" still leave dates, account numbers, or other identifiers. Even then, you're spending hours on anonymization instead of using a HIPAA-compliant tool like LexHound.
Is Westlaw Edge HIPAA compliant?
Westlaw Edge (Thomson Reuters' other legal research platform) also does NOT offer HIPAA compliance or BAAs. The same HIPAA prohibition applies: do not upload medical records to Westlaw Edge.
How is LexHound different from Casetext?
LexHound is HIPAA-compliant and purpose-built for legal work with medical records. LexHound uses Graph RAG (finds entity relationships, not just keywords), automatic medical chronology, and timeline reconstruction. Casetext is excellent for legal research and brief writing, but NOT for analyzing medical records.
Can I use both Casetext and LexHound together?
Yes. Many firms use Casetext for legal research (case law, statutes, briefs) and LexHound for medical records analysis. This gives you the best of both worlds: Casetext for legal research, LexHound for HIPAA-compliant document analysis.
What about Casetext Compose (brief writing)?
Casetext Compose is NOT HIPAA compliant. If you're writing a brief that includes medical facts or quotes from medical records, do not use Casetext Compose. Use LexHound to analyze the medical records, then write the brief in Word/Google Docs.
Does Casetext have SOC 2 certification?
Thomson Reuters has SOC 2 certification for some products, but Casetext's specific SOC 2 status is not publicly disclosed. Even if Casetext had SOC 2, that does NOT equal HIPAA compliance. HIPAA requires a signed BAA plus specific security controls that SOC 2 alone doesn't guarantee.