A business associate agreement (BAA) is the contract that lets a covered entity share PHI with a vendor that performs functions or services on its behalf. HIPAA requires it: a covered entity may disclose PHI to a business associate, or allow it to create, receive, maintain or transmit PHI, only with satisfactory written assurances (§164.502(e), §164.308(b)). The minimum contents are set by §164.504(e) for the Privacy Rule and §164.314(a) for the Security Rule.
This page explains those required terms, who does and does not need a BAA, and which provisions are commonly negotiated even though the rule does not require them. It is educational, not legal advice; BAAs are contracts and should be reviewed by your legal counsel.
Key points
- Required content comes from §164.504(e) and §164.314(a); HHS publishes sample provisions.
- Business associates are directly liable under HIPAA, with or without a signed BAA.
- Subcontractors that handle PHI need BAAs with the business associate that engages them.
- Indemnification, shorter notice windows and insurance are negotiated terms, not HIPAA requirements.
Who is a business associate?
Under §160.103, a business associate is a person or entity, other than a member of the covered entity’s workforce, that creates, receives, maintains or transmits PHI on behalf of a covered entity for a regulated function or activity, or provides certain services (legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation or financial) involving PHI. A subcontractor that does the same for a business associate is also a business associate.
| Usually a business associate | Usually not a business associate |
|---|---|
| Cloud hosting and storage providers that maintain ePHI — even if encrypted and they hold no key | Workforce members, including employees, volunteers and trainees under the entity’s direct control |
| EHR, practice management and billing software vendors | Conduits that only transmit PHI and do not store it beyond temporary transmission (e.g., postal service, couriers, internet access providers) |
| Medical billing and coding companies, clearinghouses acting for a provider | Another provider receiving PHI for treatment |
| IT managed service providers with access to systems containing PHI | Banks processing payments under the HIPAA §1179 exemption |
| Shredding and e-waste vendors | Janitorial or maintenance services with only incidental exposure |
| Outside consultants, lawyers and accountants whose work involves PHI | Covered entities in an organized health care arrangement disclosing to each other for joint activities |
Terms a BAA must contain
The table summarizes the required elements from §164.504(e)(2) and §164.314(a)(2). HHS’s sample business associate agreement provisions track these closely.
| Required term | Source |
|---|---|
| Establish the permitted and required uses and disclosures of PHI by the business associate | §164.504(e)(2)(i) |
| Not use or further disclose PHI other than as permitted by the contract or required by law | §164.504(e)(2)(ii)(A) |
| Use appropriate safeguards and comply with the Security Rule for ePHI | §164.504(e)(2)(ii)(B), §164.314(a)(2)(i)(A) |
| Report uses or disclosures not provided for by the contract, including breaches of unsecured PHI under §164.410 | §164.504(e)(2)(ii)(C) |
| Report security incidents of which it becomes aware | §164.314(a)(2)(i)(C) |
| Ensure subcontractors agree to the same restrictions and conditions | §164.504(e)(2)(ii)(D), §164.314(a)(2)(i)(B) |
| Make PHI available for individuals’ access requests | §164.504(e)(2)(ii)(E) |
| Make PHI available for amendment and incorporate amendments | §164.504(e)(2)(ii)(F) |
| Make information available for an accounting of disclosures | §164.504(e)(2)(ii)(G) |
| Comply with Privacy Rule requirements when carrying out a covered entity’s obligation | §164.504(e)(2)(ii)(H) |
| Make internal practices, books and records available to HHS | §164.504(e)(2)(ii)(I) |
| At termination, return or destroy PHI if feasible; otherwise extend protections and limit further use | §164.504(e)(2)(ii)(J) |
| Authorize termination by the covered entity if the business associate violates a material term | §164.504(e)(2)(iii) |
Permitted uses for the business associate’s own purposes
A BAA may not authorize the business associate to use or disclose PHI in a way that would violate the Privacy Rule if done by the covered entity, with limited exceptions. If the contract allows it, the business associate may use PHI for its own proper management and administration and to carry out its legal responsibilities, and may provide data aggregation services relating to the covered entity’s health care operations (§164.504(e)(2)(i), (e)(4)). De-identification rights are not automatic; if a vendor wants to de-identify data for its own products, the BAA should say so explicitly.
The subcontractor chain
- 1
Covered entity → business associate
The covered entity signs a BAA with each vendor that handles PHI on its behalf.
- 2
Business associate → subcontractor
The business associate signs a BAA with any subcontractor that creates, receives, maintains or transmits PHI for it (§164.502(e)(1)(ii), §164.308(b)(2), §164.504(e)(5)).
- 3
Further down the chain
Each subcontractor does the same with its own subcontractors. The covered entity does not need a direct BAA with downstream subcontractors.
- 4
Flow-down consistency
Each downstream agreement must contain the same restrictions and conditions that apply to the party above it.
Commonly negotiated terms (not required by HIPAA)
The following provisions appear in many BAAs but are matters of negotiation and contract law, not HIPAA requirements. Whether to include them is a business and legal decision for each party and its counsel.
| Negotiated term | What it typically covers |
|---|---|
| Shorter breach notice window | Notice to the covered entity within a set number of days or hours, shorter than the 60-day outer limit in §164.410 |
| Indemnification | Who bears costs and liability arising from the other party’s breach of the BAA |
| Breach cost reimbursement | Notification letters, call centers, credit monitoring and forensic costs |
| Cyber insurance | Minimum coverage levels the business associate must carry |
| Security standards | Specific controls such as encryption, MFA, or SOC 2 or HITRUST reports |
| Audit rights | The covered entity’s right to assess or receive evidence of the vendor’s safeguards |
| Offshore restrictions | Limits on storing or accessing PHI outside the United States |
| Data return format and timing | How and when PHI is returned at termination |
Managing BAAs across the organization
If you are a vendor yourself, expect covered entities to send their own BAA template. Mapping your actual controls to the required terms before you sign — and working alongside your legal counsel on negotiated terms — avoids committing to obligations you cannot meet. See also HIPAA consulting for business associates.
- 1
Inventory vendors
List every vendor and determine whether each touches PHI. Include free tools and shadow IT discovered during a HIPAA gap analysis.
- 2
Classify
Decide whether each is a business associate, a conduit, or outside HIPAA, and document the reasoning.
- 3
Execute and store
Sign BAAs before PHI is shared and keep them in a central repository for at least six years after they last apply.
- 4
Review
Re-check the inventory annually and whenever a vendor’s service or data access changes. Our business associate compliance service supports this from either side of the contract.
Frequently asked questions
Is a BAA legally required?
Yes. A covered entity may share PHI with a business associate only with satisfactory written assurances that meet §164.504(e) and §164.314(a). Business associates need equivalent agreements with their subcontractors.
Does a cloud provider that never sees our data need a BAA?
Generally yes. HHS guidance says a cloud service provider that maintains ePHI is a business associate even if the data is encrypted and the provider has no decryption key. The conduit exception covers transmission-only services.
Are business associates liable if no BAA was signed?
Yes. Since the HITECH Act and the 2013 Omnibus Rule, business associates are directly liable for certain HIPAA requirements, including Security Rule compliance, whether or not a BAA exists. The missing BAA is also a violation in its own right.
Can we use the HHS sample BAA as-is?
HHS’s sample provisions are a starting point that reflects the required terms. They do not cover state law or business terms such as indemnification, and they should be adapted and reviewed by legal counsel.
How quickly must a business associate report a breach?
Under §164.410, without unreasonable delay and no later than 60 calendar days after discovery. Many BAAs negotiate a shorter window, which then becomes the contractual obligation.
Is this page legal advice?
No. It is educational information about the regulatory requirements. Contract language, state law and negotiated terms should be reviewed by qualified legal counsel.
Authoritative sources
- HHS: Sample Business Associate Agreement Provisions
- eCFR: 45 CFR Part 164 (Security and Privacy)
- HHS: Guidance on HIPAA & Cloud Computing
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.