Skip to content
Lexyno
Back to Academy
ComplianceMay 26, 2026Updated Oct 14, 20269 min readJun LeeJun Lee

AI Demand Letters and HIPAA: What PI Attorneys Must Know

AI Demand Letters and HIPAA: What PI Attorneys Must Know

HIPAA applicability depends on the firm's role and the data flow. Here is where BAAs fit, and why "HIPAA-compliant" is not a label a vendor can claim.

Jun Lee
Jun Lee
Co-Founder & CTO

Almost every firm that evaluates an AI demand letter tool asks us the same thing. "Is this HIPAA compliant?" It's the right question, asked the wrong way.

HIPAA compliance isn't a checkbox a vendor ticks. It's a legal relationship that either exists or doesn't. This post is about what that relationship requires, and why the honest answer is more than a yes or no on a sales page.

Insurance and medical forms on a desk next to a stethoscope, representing protected health information in a PI case file
A demand file is full of health information. Who may handle it depends on roles and contracts, not on the file type.

Does HIPAA Apply to a PI Firm's Medical Records?

Not automatically. Holding medical records doesn't make a plaintiff PI firm a HIPAA covered entity, or every vendor its business associate; HIPAA turns on the parties' legal roles and the actual data flow. Confidentiality duties, protective orders and state privacy laws can still limit what you do.

A demand letter carries highly sensitive information: diagnoses, treatment dates, provider names, billing codes. That's exactly why the question matters.

But that nuance isn't permission to use consumer tools casually. Other rules still apply where HIPAA doesn't. Your confidentiality duties, protective orders, client instructions, state privacy laws and vendor contracts can all set stricter limits.

PartyWhat it does with the recordsWhere it usually stands under HIPAA
Treating providerCreates the records and sends them on the client's authorizationTypically a covered entity
Plaintiff PI firmReceives the records to build the claimNot automatically a covered entity; depends on its role and the data flow
AI or software vendorProcesses the records for the firmA business associate only if the relationship and data flow make it one

Can You Use ChatGPT for a Demand Letter With Medical Records?

Don't paste a client's identifiable medical records into ChatGPT, Claude, Gemini or any other consumer AI interface. A consumer subscription isn't the same contractual or technical service as an eligible enterprise API. Even where HIPAA doesn't govern your firm, confidentiality and privacy duties still call for a controlled workflow.

This isn't a knock on those products. They're built for general use, not regulated health data, and they say so.

The point is that two questions get confused. "Is this AI smart enough to help?" is one. "Is this AI tool authorized to touch this data?" is the other, and it's the only one that matters here.

Attorney reviewing a vendor agreement at a desk with a tablet before approving an AI tool
Before any tool touches client records, read the contract that covers it.

What Does a Business Associate Agreement Require?

A BAA is a binding contract, not a marketing checkbox. It obligates the vendor to safeguard the data under HIPAA's Security Rule, use it only for the services performed, control any sub-processors that touch it, and report breaches within a defined window.

That last point is easy to miss. Check the vendor's notification window against your own obligations.

Under HIPAA's Breach Notification Rule, a covered entity must notify affected individuals without unreasonable delay. The outer limit is 60 days after discovering a breach. A slow vendor can use up much of that time before you even hear about it.

"HIPAA-compliant" is not a label a vendor can self-certify. It is the outcome of a signed BAA plus the safeguards required underneath it — and a vendor can have excellent security and still be non-compliant without one.

Why Do Sub-Processors Matter?

Most AI products don't run on one system. They route data through one or more model providers, a database layer, and often a separate document-processing service. Each one that touches PHI is a sub-processor, and a BAA that doesn't cover every one of them leaves a gap.

This is the part that catches firms off guard. So the right question isn't "do you have a BAA?" It's "does your BAA cover every system this data actually passes through?"

Public consumer AIProperly governed AI vendor
Signs a BAANoYes — covering the full data flow
Sub-processors namedN/AShould be explicitly listed
Breach notificationNot HIPAA-governedDefined window, contractually set
Safe to enter real PHINeverOnly once the BAA is in place
Hand highlighting clauses in a printed contract to check which sub-processors a business associate agreement covers
Look for the list of sub-processors. If it isn't there, ask for it.
Try Lexyno FreeGenerate a mock demand letter from your own records.

Where Lexyno Stands Today

We think the honest answer matters more than the convenient one. So here's our current position, plainly.

Lexyno has Business Associate Agreements covering the two model providers used in the product pipeline, OpenAI and Anthropic. In production, Anthropic's Claude models run through Amazon Bedrock, and that path is covered by Lexyno's BAA with Amazon Web Services. Gemini was removed from the product pipeline rather than kept as an uncovered fallback.

Those agreements cover specific API services, organizations, endpoints and eligible features. They don't cover public ChatGPT, Claude's consumer interfaces, or every third-party tool.

So Lexyno doesn't treat a signed BAA as a blanket "HIPAA compliant" label. Contractual coverage, access controls, data minimization, retention, incident response and your own legal role all have to line up with the actual data flow.

What to Ask Any AI Vendor Before You Send Real Records

Whether you're evaluating Lexyno or anyone else, this is the checklist:

  • Will you sign a BAA, and is it in place before any real PHI is processed?
  • Does the BAA name every sub-processor the data passes through, not just the primary product?
  • What is the contractual breach notification window, and does it leave you enough time to meet your own 60-day obligation?
  • How is data used and retained? Is it used to train the vendor's models, and how long is it stored?
  • Which exact service and configuration are covered, and is there any consumer interface or uncovered fallback in the path?
Professional working through a vendor security questionnaire on a laptop at her desk
Ask every vendor the same five questions, and get the answers in writing.

A vendor that answers these clearly is a more trustworthy partner, even if some answers are "not yet." Worry about the one that just says "yes, we're HIPAA compliant" and moves on.

Compliance is a process you can check. It isn't a label you take on faith. See how this fits the rest of the work in our AI medical chronology guide and the free personal injury demand letter template.

Frequently asked questions

Do not put identifiable client medical records into a consumer chatbot. Whether HIPAA applies depends on the firm's legal role and the data flow, but confidentiality duties, protective orders, state privacy law, and vendor terms can still restrict disclosure. Use a governed product workflow whose contracts and controls cover the specific service handling the records.

A BAA is a legally binding contract used when a covered entity or business associate engages another party to handle protected health information. It defines permitted uses, safeguards, sub-contractor obligations, and breach duties. A plaintiff PI firm is not automatically a HIPAA covered entity simply because it possesses medical records, so the parties' roles and actual data flow must be assessed rather than inferred from the file type alone.

"HIPAA-compliant" is not a status a vendor can self-certify or a product can claim out of the box. Compliance is the result of a signed BAA plus the technical, administrative, and physical safeguards required by the Security Rule. A vendor can have strong encryption and access controls and still be non-compliant if no BAA is in place, or if the BAA does not cover the specific way PHI flows through the product.

Ask directly: will you sign a Business Associate Agreement, and does it cover every AI model or sub-processor that touches the data, not just the primary product? Many AI products route data through several underlying model providers, and a BAA that does not name those sub-processors leaves a gap. Also ask how data is used, retained, and whether it is used to train the vendor's models.

Removing or masking identifying details before data reaches an AI system is a recognized way to reduce HIPAA exposure while a vendor relationship matures, because properly de-identified data falls outside HIPAA's PHI definition. It is a reasonable interim safeguard during evaluation, but it is not a substitute for a signed BAA once a firm is processing real client records in production.

Related posts

What's next?

Ready to see the difference in your next case?

Put these strategies to work. Try a mock demand generated by Lexyno today.

Request Evaluation Access