# What Is a Business Associate Agreement?

A Business Associate Agreement (BAA) is a written contract required under the Health Insurance Portability and Accountability Act (HIPAA) between a covered entity and any vendor that creates, receives, maintains or transmits protected health information on its behalf. It sets out permitted uses, saf

**Category:** Articles
**Written by:** Zain Qayyum
**Last updated:** Nov 13, 2026
**Source:** https://signals.medsender.com/articles/what-is-a-business-associate-agreement

---

A Business Associate Agreement (BAA) is a written contract required under the Health Insurance Portability and Accountability Act (HIPAA) between a covered entity and any vendor that creates, receives, maintains or transmits protected health information on its behalf. It sets out permitted uses, safeguards, breach notification duties, and what happens to the data when the relationship ends.

Because the required contents are fixed by regulation, most agreements look alike. That similarity is exactly what gets practices into trouble, because it encourages signing without reading. The parts that vary are the parts that matter.

## TL;DR

A Business Associate Agreement is what makes it lawful to hand patient data to a vendor, not proof the vendor is careful with it.

HIPAA fixes the required contents, so the differences between agreements sit in timings and exceptions.

Breach notification timing, subcontractor handling and termination terms are the three clauses worth real attention.

A System and Organization Controls (SOC) 2 Type II report answers a different question. You want both.

Whether a vendor trains artificial intelligence (AI) on your data is usually outside a standard agreement and has to be asked separately.

Of nine vendors checked on 12 November 2026, Medsender and eight competitors, two state publicly that an agreement is executed with every customer.

## Who Needs a Business Associate Agreement, and When

The obligation attaches to the work, not to the size of the vendor. If a company creates, receives, maintains or transmits protected health information on your behalf, it is a business associate and the agreement is required. Practices routinely under-count how many of their vendors qualify.

### Vendors That Qualify Without Looking Like It

Fax and document vendors, scheduling tools, billing services, transcription, answering services and analytics providers are all business associates. So is any vendor whose support staff can see a chart in order to troubleshoot. The test is access to protected health information in the course of providing the service, not whether access is routine.

### Subcontractors Inherit the Obligation

A business associate must bind its own subcontractors to equivalent terms. That chain matters more than it used to, because a modern software vendor may rely on hosting providers, model providers and support tooling that each touch data in some form. You are accepting the whole chain, not just the company on the invoice.

## What HIPAA Requires the Agreement to Contain

The Privacy Rule sets out the required elements, which is why agreements converge on the same shape. Knowing the list is useful mainly so you can see what a particular vendor has added, removed or qualified.

### The Required Elements

The permitted uses and disclosures of protected health information

A commitment to use appropriate safeguards and to prevent unauthorised use or disclosure

An obligation to report breaches and security incidents to the covered entity

A requirement to bind subcontractors to equivalent terms

Return or destruction of protected health information at termination, where feasible

### Where Agreements Actually Differ

Two agreements can contain all five elements and still leave you in very different positions. One may require breach notification without unreasonable delay, another within five business days. One may commit to returning data in a structured format, another to destruction only. Those differences are the negotiation.

## What the Agreement Does Not Do

Most of the misunderstanding about Business Associate Agreements sits here, and it is worth being blunt. A signed agreement establishes obligations. It does not establish that the vendor meets them.

### It Is Not Evidence of Security

Signing is a contractual promise. An audit is evidence. A SOC 2 Type II report tests whether controls operated over a period of time, which is a fundamentally different assurance from a signature on a contract. A vendor with an agreement and no audit has told you what it intends to do. A vendor with both has also shown its work.

### It Does Not Tell You Where Your Data Lives

Data residency, retention periods and the identity of subprocessors generally sit outside the agreement. If those matter to you, and for most practices residency and retention do, they have to be asked separately and confirmed in writing. See our guide to[what healthcare vendors publish about data export and residency](/listicles/healthcare-vendors-data-export-residency-retention).

### It Does Not Cover Model Training

Whether a vendor uses your patient data to train machine learning models is rarely addressed by a standard agreement. The contract governs use and disclosure. Training sits awkwardly across those categories, and most templates predate the question entirely. If the vendor runs AI over your documents or calls, put the question directly and get the answer as a contract term rather than an assurance in a demo.

## Four Things to Check Before You Sign

Four clauses change outcomes in practice. Everything else in a standard agreement is largely boilerplate shaped by the regulation, so this is where to spend review time.

### How Fast They Must Tell You About a Breach

Your own notification obligations begin when you discover a breach, and in practice that often means when the vendor tells you. Their timing becomes your exposure. Without unreasonable delay is the regulatory floor. A specific number of days is better, and shorter is better still.

### What Happens to Subcontractors

Ask who they are. A vendor that cannot name its subprocessors cannot meaningfully answer for them, and you are being asked to accept a chain you cannot see. Some vendors publish a subprocessor list and commit to notifying customers of changes. That is the standard worth holding out for.

### What Happens to Your Data at Termination

Return or destruction, in what format, within what window, and at what cost. This clause is the one nobody reads at signing and everybody needs at the exit. A commitment to destroy data is not the same as a commitment to give it back first, and a practice switching vendors usually needs both. Our guide to[what happens to patient data when you leave a vendor](/articles/what-happens-to-patient-data-when-you-leave-a-vendor)covers the mechanics.

### Whether You Are Being Charged for It

Some vendors treat the agreement as a paid add-on or reserve it for higher tiers. Others include it with every account. Neither is unlawful, but it tells you something about how the vendor views compliance, and it belongs in the pricing conversation rather than after it.

## What Healthcare Vendors Actually Publish About This

We read the public pages of nine healthcare software vendors on 12 November 2026, Medsender and eight competitors, looking for a plain statement about whether a Business Associate Agreement is executed with every customer. The results were thinner than expected.

**Two state it explicitly.**Medsender says an agreement is included free with every account. Linear Health states that one is executed with every customer.

**One refers to it indirectly.**Brevium describes a BAA-backed environment without stating that it applies universally.

**Six say nothing at all**about a Business Associate Agreement on their public pages.

That silence is not evidence of refusal. Almost every healthcare vendor will sign one, because almost every healthcare vendor has to. The point is narrower and more practical: you cannot tell from the website, so it goes on the question list rather than being assumed. Our guide to[vetting a healthcare AI vendor](/articles/vet-healthcare-ai-vendor-baa-trust-center)sets out the wider checklist.

## How to Ask, and What a Good Answer Looks Like

The mechanics of asking matter more than the wording. A vendor's response time on this request is itself informative, and it costs nothing to find out early.

### Ask Before the Demo, Not After the Quote

A vendor that produces an agreement within a day usually has a compliance function and a trust centre behind it. A vendor that needs three weeks is telling you something about how often the question comes up internally. Either way, you learn it earlier and cheaper by asking first.

### Pair It With Two Other Requests

Ask for the SOC 2 report, which is commonly shared under a non-disclosure agreement through a trust centre. Then ask for a written answer on data residency, retention and model training, since none of those are reliably covered by the agreement itself. Three requests, one email, and the combination tells you more than any of them alone. For the AI-specific questions, see[how HIPAA applies to AI processing of patient records](/articles/hipaa-compliant-ai-processing-patient-records).

## Where This Leaves a Practice Choosing a Vendor

Treat the Business Associate Agreement as the entry requirement rather than the decision. It is necessary, it is largely standardised, and on its own it distinguishes almost nobody. The questions that actually separate vendors are the ones the agreement does not answer: how fast they tell you when something goes wrong, who else touches the data, what you get back when you leave, and whether your patients' information is being learned from.

If you are building a vendor questionnaire, those four belong near the top. And if a vendor cannot answer them in writing, that is an answer too. Have your own counsel review any agreement before you sign it, because the terms that matter here are contractual rather than technical.

## FAQs

Common questions from practices evaluating a vendor that will handle patient data.

### Who Needs to Sign a Business Associate Agreement?

Any vendor that handles protected health information on your behalf. The test is whether they touch the data while delivering your service, not how often they do it. Their own subcontractors must be bound to equivalent terms as well, so ask who sits behind the company named on your invoice.

### Is a Business Associate Agreement the Same as HIPAA Compliance?

No. The agreement creates obligations; it does not demonstrate that they are met. Compliance is a programme of safeguards, training and operating controls. A signed agreement with no audit behind it tells you what a vendor has promised, rather than what the vendor actually does day to day.

### Should a Vendor Charge for a Business Associate Agreement?

Practice varies and neither approach is unlawful. Some vendors include the agreement with every account, while others treat it as a paid add-on or a higher-tier feature. Ask during the pricing conversation rather than afterwards, because it is easier to negotiate before a quote has been agreed.

### What Should the Agreement Say About Breach Notification?

At minimum, that the vendor reports breaches and security incidents to you. The clause worth negotiating is timing, because your own notification obligations begin at discovery. Without unreasonable delay is the regulatory floor, and a specific number of days is materially better for managing your own exposure.

### Does a Business Associate Agreement Cover AI Model Training?

Usually not. Standard agreements govern use and disclosure, and most templates predate the question entirely. If a vendor runs AI over your documents or calls, ask directly whether your data trains its models, including in de-identified form, and get that answer written into the contract itself.

### What Happens to Your Data When the Agreement Ends?

The agreement should require return or destruction of protected health information where feasible. Check the format, the window and the cost, and confirm that return comes before destruction. A practice switching vendors usually needs its data back in a usable form, not simply deleted on the vendor's timetable.
