
BAA Agreement: What Is a HIPAA Business Associate Agreement and Who Needs One?
A BAA agreement — a Business Associate Agreement — is a legally required contract under HIPAA between a covered entity, such as a hospital or health plan, and a business associate, a vendor that creates, receives, maintains or transmits protected health information (PHI) on its behalf. The agreement sets out how the vendor may use PHI, the safeguards it must apply, and what happens if it breaches the contract.
If you run a healthcare organisation, or you sell software or services to one, the BAA is not paperwork to rush through. It determines who is responsible when PHI is exposed, and it is one of the first documents regulators ask for after a breach. A missing or weak BAA can turn a manageable incident into a costly enforcement action — for both sides.
What Is a BAA Agreement?
BAA stands for Business Associate Agreement. Under the Health Insurance Portability and Accountability Act (HIPAA), a covered entity — a health plan, a healthcare clearinghouse or a healthcare provider that transmits health information electronically — may only disclose PHI to a business associate if it has a signed BAA in place.
The BAA is a contract, but it is a contract with content prescribed by regulation. The HIPAA Privacy Rule and Security Rule require it to include specific terms, and the US Department of Health and Human Services (HHS) publishes sample language. It does not replace a service-level agreement or a data processing agreement; it sits alongside them, covering the HIPAA obligations that other contracts may not mention.
Who Is a Business Associate?
A business associate is a person or organisation that performs functions or provides services on behalf of a covered entity that involve PHI. That includes billing and claims processing, data analysis, cloud hosting and storage, email and messaging services, and software used to manage patient records.
Common examples include an electronic health records (EHR) vendor, a cloud provider hosting a hospital’s data, a medical billing company, a law firm handling healthcare matters, an external IT provider with access to systems holding PHI, and a shredding company destroying patient records. If the vendor’s work requires access to PHI, it is likely a business associate — even if it never intended to see the data.
Who Needs a BAA?
| Vendor or service | Needs a BAA? | Why |
|---|---|---|
| Cloud hosting (EHR, backup) for a hospital | Yes | Creates, stores or transmits PHI on the hospital’s behalf |
| Medical billing company | Yes | Processes claims containing PHI |
| Email provider used for patient messages | Yes | Transmits PHI, even if only occasionally |
| Analytics provider on de-identified data | Usually no | Properly de-identified data is not PHI, if the rules are followed |
| Office cleaner with no data access | No | Does not create, receive or maintain PHI |
| Subcontractor of a business associate | Yes | A business associate needs a BAA with its own subcontractors that handle PHI |
The subcontractor row is the one most organisations miss. A BAA is not a single link in a chain; it flows down. If your EHR vendor uses a subcontractor to host data, that subcontractor must have its own BAA with the vendor. When you sign a BAA, ask the vendor about its own subcontractors — their security is part of your risk.
What Must a BAA Include?
HHS requires a BAA to cover, at minimum, the following obligations:
- Permitted uses and disclosures. The business associate may use or disclose PHI only as the agreement allows, or as the law requires.
- Safeguards. The business associate must use appropriate safeguards to prevent unauthorised use or disclosure, including the administrative, physical and technical safeguards of the HIPAA Security Rule.
- Reporting. It must report to the covered entity any use or disclosure it was not permitted to make, and any security incident it becomes aware of — including breaches of unsecured PHI.
- Subcontractor flow-down. It must ensure that any subcontractor that handles PHI agrees to the same restrictions and conditions.
- Access and amendment. It must support the covered entity’s obligations to give individuals access to their PHI and to amend it, and must make its books available to HHS on request.
- Return or destruction. At the end of the agreement, it must return or destroy PHI if feasible, or if not feasible, keep protecting it and limit its use.
- Termination. The covered entity must be able to terminate the agreement if the business associate breaches a material term and does not cure it.
Those are the minimum terms. In practice, good BAAs also add incident response timelines, audit and inspection rights, insurance expectations, a clear allocation of breach costs, and a mechanism to update the agreement when HIPAA rules or business needs change. Those extras are worth negotiating before you sign, because after a breach is too late. For the broader security duties behind those safeguards — how organisations protect the data they hold — see our guide to data security management.
BAA vs Other Agreements
A BAA is often confused with other contracts. A data processing agreement (DPA) serves a similar purpose under the GDPR for the European Union, and many vendors sign both. A service-level agreement (SLA) sets availability and support expectations, but says little about PHI. A non-disclosure agreement (NDA) promises confidentiality, but does not carry HIPAA’s specific obligations — a signed NDA does not satisfy the BAA requirement, and regulators will not accept it as a substitute.
Common BAA Deficiencies and Red Flags
Enforcement actions and audits repeatedly show the same problems. The most common is a missing BAA altogether: a hospital starts using a vendor’s tool, PHI flows into it, and no one ever checks for the agreement. Others include templates signed without review, outdated agreements that do not reflect current services, BAAs that name the wrong entity, and failures to update agreements after a merger, a vendor change or a new product.
Red flags when reviewing a vendor’s BAA include: no breach notification timeline, no right to audit or receive compliance reports, no obligation to flow terms down to subcontractors, vague security language with no reference to HIPAA safeguards, and a one-sided termination clause that cannot be used when a vendor is at fault. If you find any of these, raise them before signing, or be prepared to change vendor.
How to Put a BAA in Place: A Practical Process
- Inventory your vendors. List every vendor that touches PHI, and which of them has a signed BAA. That inventory is also useful when you review your compliance, as our guide to information security audits explains.
- Rank them by risk. A cloud host with all your records is a higher priority than a shredding firm with one-off access.
- Use the HHS template as a baseline. Start from the official sample language, then add the extras above that fit your risk. Do not sign a vendor’s form blind, and treat a vendor that refuses to sign a BAA as a vendor you cannot use for PHI.
- Keep a signed record. Store the executed agreement, its date and its scope, and assign an owner and a review date for each one.
- Monitor and renew. Check that the vendor is actually meeting its obligations — through questionnaires, audits and incident reporting — and revisit the BAA when the service or the data changes.
Remember that a BAA is a compliance control, not a substitute for technical safeguards. The vendor still needs to encrypt PHI at rest and in transit, control access to it and respond to incidents. On encryption specifically, our explainer on what data at rest is and how to protect it covers the basics every covered entity and business associate should know.
What Happens Without a BAA?
Failing to have a required BAA is a HIPAA violation in itself, even if no breach has occurred. When a breach happens without a BAA in place, regulators and investigators treat it as an aggravating factor, and civil penalties can reach tens of thousands of dollars per violation, with higher amounts for wilful neglect. The vendor that handled PHI without a BAA is also directly liable under HIPAA, even though it was not the covered entity. The absence of an agreement also damages the relationship after an incident: without agreed incident duties and cost allocations, disputes about who pays for notification and remediation can be long and expensive.
Frequently Asked Questions
What does BAA stand for in HIPAA?
BAA stands for Business Associate Agreement. It is a contract required by HIPAA between a covered entity — such as a hospital or health plan — and a business associate that creates, receives, maintains or transmits protected health information on its behalf.
Who needs to sign a BAA?
Any vendor that handles PHI on behalf of a covered entity needs to sign a BAA — for example, cloud providers, billing companies, EHR vendors, email providers and IT firms. The business associate must also sign a BAA with any subcontractor it uses that handles PHI.
Is a BAA the same as an NDA?
No. An NDA is a general confidentiality promise, while a BAA is a contract with specific HIPAA-mandated terms about permitted uses, safeguards, breach reporting and termination. A signed NDA does not satisfy the requirement for a BAA.
Can a BAA be signed electronically?
Yes, if the electronic signature method is valid under the law and you retain a reliable executed copy. The important thing is a signed, dated agreement that is available if — or when — it is needed.
How long does a BAA last?
A BAA typically remains in force for as long as the business associate handles PHI under the agreement, and its obligations to protect, return or destroy PHI survive termination. Review it when the services, the data or the rules change.
Conclusion
A BAA agreement turns a vendor relationship into a shared duty: the covered entity decides what a vendor may do with PHI, and the vendor promises to protect it, report problems and pass those duties down the chain. Before you send a vendor your patients’ data, check that a current, signed BAA is in place, that it covers the services you actually use, and that you have a way to hold the vendor to it. An hour spent on the agreement now can save a very difficult — and expensive — conversation later.

