Contracts · Updated

Business associate agreements: what HIPAA requires them to say

A business associate agreement is the written contract HIPAA requires before a practice or other covered entity lets a vendor create, receive, maintain or transmit patients' protected health information for it. Billing, practice management, cloud, IT, legal and consulting firms that handle the information usually need one; a mere courier or internet carrier does not. Under 45 CFR 164.504(e) and 164.314(a), the agreement must set the permitted uses and disclosures; require safeguards and Security Rule compliance; require reports of misuse, security incidents and breaches; bind subcontractors to the same terms; support access, amendment and accounting rights; open the vendor's books to HHS; require return or destruction at the end, where feasible; and let the practice terminate if the vendor violates a material term. The vendor is directly liable and must report a breach without unreasonable delay and no later than 60 calendar days after discovery.

What 45 CFR 164.504(e) requires a business associate agreement to say, and what to check (as of November 17, 2026; checks are our reading)
Required termWhat the rule saysWhat to check in the vendor's agreement
Permitted uses and disclosures"Establish the permitted and required uses and disclosures" of the information, and authorize nothing the practice could not do itself, except the vendor's own management and administration and data aggregation for the practice, if the contract allows them (164.504(e)(2)(i))Uses tied to the services bought; any use for the vendor's own purposes named and limited
No other use or disclosure"Not use or further disclose the information other than as permitted or required by the contract or as required by law" (164.504(e)(2)(ii)(A))No general license to de-identify, aggregate or analyze patient data unless you agree to it
Safeguards"Use appropriate safeguards and comply, where applicable, with subpart C" (the Security Rule) for electronic information (164.504(e)(2)(ii)(B); 164.314(a)(2)(i))A promise to comply with the Security Rule, not only "reasonable" or "industry standard" security
ReportingReport any use or disclosure the contract does not provide for, "including breaches of unsecured protected health information as required by § 164.410" (164.504(e)(2)(ii)(C)), and "any security incident of which it becomes aware" (164.314(a)(2)(i)(C))A deadline in days, well inside the 60-day legal maximum; what the first report contains; how routine unsuccessful attempts are reported
SubcontractorsEnsure subcontractors that handle the information "agree to the same restrictions and conditions that apply to the business associate" (164.504(e)(2)(ii)(D))Written flow-down to every subcontractor, and notice before a new one holds your data
Patient access"Make available protected health information in accordance with § 164.524" (164.504(e)(2)(ii)(E))A turnaround that leaves you time to meet your own deadline, and who answers the patient
AmendmentMake information available for amendment "and incorporate any amendments" under § 164.526 (164.504(e)(2)(ii)(F))How quickly the vendor makes corrections you approve
Accounting of disclosures"Make available the information required to provide an accounting of disclosures in accordance with § 164.528" (164.504(e)(2)(ii)(G))The vendor logs its own disclosures and sends them on request
Doing the practice's workWhere the vendor carries out a Privacy Rule obligation for the practice, "comply with the requirements of this subpart that apply to the covered entity" (164.504(e)(2)(ii)(H))Needed if the vendor handles patient requests for you
Books and recordsMake its internal practices, books and records available "to the Secretary for purposes of determining the covered entity's compliance" (164.504(e)(2)(ii)(I))No condition that HHS first obtain the vendor's consent or a subpoena
Return or destruction"At termination of the contract, if feasible, return or destroy all protected health information" and "retain no copies"; if that is not feasible, "extend the protections of the contract" and limit further uses (164.504(e)(2)(ii)(J))A date, a usable return format, a destruction certificate and a rule for backups
TerminationLet the practice terminate "if the covered entity determines that the business associate has violated a material term" (164.504(e)(2)(iii))No fee, lock-in or long notice period that makes the right unusable
If the practice learns of a pattern of breachA practice that "knew of a pattern of activity or practice of the business associate that constituted a material breach" is out of compliance unless it took reasonable steps to cure it and, if they failed, terminated "if feasible"; a vendor owes the same toward its subcontractors (164.504(e)(1)(ii)-(iii))A cure procedure, and the termination right above
Is this vendor a business associate? (as of November 17, 2026; "our reading" rows apply the definition to vendors it does not name)
Vendor or relationshipBusiness associate?Basis
Billing or claims processing companyYes"claims processing or administration" and "billing" are named functions (45 CFR 160.103, definition paragraph (1)(i))
Practice management company or MSO handling records, billing or administrationYes, where it handles the information"practice management" ((1)(i)) and "management, administrative" services ((1)(ii)); applying this to a typical MSO is our reading
Lawyer, accountant, consultant or accreditation body given patient informationYes"legal, actuarial, accounting, consulting" and accreditation services involving disclosure of the information ((1)(ii))
Cloud host or records storage companyYes, even if it never looks at the dataIt "maintains" the information ((1)(i)); HHS: a data storage company with access to it "qualifies as a business associate, even if the entity does not view the information" (78 FR 5566)
IT support or managed service provider with access to systems holding recordsYes (our reading)It creates, receives, maintains or transmits the information for the practice ((1)(i))
Telehealth video, records or patient messaging platformYes (our reading)The same test; see HIPAA for telehealth
Marketing agency given patient contact details to run the practice's campaignsYes (our reading)It receives the information for the practice ((1)(i)); whether each message is allowed is a separate question
Your vendor's own subcontractor, such as a billing company's cloud hostYes, of the vendor, which signs with it; the practice does notParagraph (3)(iii); 164.502(e)(1)
Internet service provider, phone carrier, postal or courier service that only carries the dataNo, a "mere conduit"Not in the regulation's text; HHS calls the exception "a narrow one" for "mere courier services" and "their electronic equivalents" (78 FR 5566)
Another health care provider receiving records to treat the patientNoExcluded for "disclosures by a covered entity to the health care provider concerning the treatment of the individual" (paragraph (4)(i))
Employees, volunteers and trainees under the practice's direct controlNo, they are workforceThe definition applies only "other than in the capacity of a member of the workforce"; workforce covers people "under the direct control" of the practice, "whether or not they are paid" (160.103)

When HIPAA requires a business associate agreement

A covered entity may let a vendor "create, receive, maintain, or transmit protected health information on its behalf" only if it "obtains satisfactory assurance that the business associate will appropriately safeguard the information", documented "through a written contract or other written agreement or arrangement" (45 CFR 164.502(e)). The Security Rule repeats this for electronic information and marks the written contract "Required" (164.308(b)). That contract is the business associate agreement.

Who counts is set by the definition of business associate in 45 CFR 160.103, which reaches a vendor's subcontractors too; the second table applies it to common vendors.

What the agreement must say

The required terms are in 45 CFR 164.504(e) and the first table above. Beyond what the agreement permits or the law requires, the vendor may not use or disclose the information at all (164.502(a)(3)), so silence in the agreement withholds a use rather than granting it (our reading).

For electronic information, the Security Rule adds three contract terms: comply with the Security Rule, bind subcontractors by a compliant contract, and "Report to the covered entity any security incident of which it becomes aware" (45 CFR 164.314(a)). A security incident includes "the attempted or successful unauthorized access" to information (164.304), so agreements usually give a standing notice for routine unsuccessful attempts and require prompt reports of the rest (our reading).

Breach reporting and the subcontractor chain

A vendor that discovers a breach of unsecured protected health information must notify the practice "without unreasonable delay and in no case later than 60 calendar days after discovery of a breach" (45 CFR 164.410). The clock starts when any employee, officer or other agent of the vendor, other than the wrongdoer, knew or with reasonable diligence would have known of the breach. The notice must identify each affected individual "to the extent possible", with the other details the practice needs for its own notices. In our reading, 60 days is a ceiling, not a working deadline: agreements commonly require a first notice within a few business days.

A vendor may let a subcontractor handle the information only after getting the same satisfactory assurances (164.502(e)(1)(ii)), and the contract rules apply "in the same manner" (164.504(e)(5)). A covered entity "is not required to obtain such satisfactory assurances from a business associate that is a subcontractor" (164.502(e)(1)(i)), so ask the vendor to confirm its subcontractor agreements exist (our reading).

Who is liable when a vendor gets it wrong

Business associates are directly liable. Under the HITECH Act, Security Rule sections 164.308, 164.310, 164.312 and 164.316 apply to a business associate "in the same manner that such sections apply to the covered entity", and the civil and criminal penalty provisions apply to a vendor that breaks those rules or the contract limits (42 U.S.C. 17931; 17934). HHS imposes civil money penalties on "a covered entity or business associate" that violates the rules (45 CFR 160.402(a)).

The practice can also answer for its vendor: a covered entity is liable for violations by "any agent of the covered entity, including a workforce member or business associate, acting within the scope of the agency" (160.402(c)). HHS has said the "essential factor" is the practice's "right or authority" to control the vendor's conduct, and labels such as independent contractor "do not control whether an agency relationship exists" (78 FR 5566): the relationship counts, not the label, as with independent contractor agreements (our reading).

Civil money penalties run by culpability tier, from $145 per violation where the entity did not know and with reasonable diligence would not have known, up to $2,190,294 for willful neglect not corrected within 30 days, with a calendar-year cap of $2,190,294 per tier (45 CFR 102.3, 2025 amounts). HHS said on October 21, 2026 that it "will continue to use the 2025 civil monetary penalty levels" for 2026 (91 FR 66566). Since 2019 it has applied lower annual limits as enforcement discretion: $25,000, $100,000, $250,000 and $1.5 million before inflation adjustment (84 FR 18151).

Terms worth negotiating beyond the minimum

HIPAA sets the floor, and vendor forms usually stop there. If you are the vendor, agree only to deadlines and audits you can meet, and pass the same terms down to your subcontractors. In our reading, beyond the first table's checks, these terms are worth settling:

  • Who pays for investigation, patient notices and other costs of a breach the vendor causes, and whether the liability cap carves those out.
  • Cyber insurance the vendor must carry.
  • Where the data is stored, and evidence of security on request, such as an independent audit report.
  • Which document controls if the vendor's online terms of service conflict with the agreement.
  • Governing law: North Carolina, for a North Carolina practice.

Rule changes to watch

A final rule amending the Privacy Rule (RIN 0945-AA00) was published in the Federal Register on November 19, 2026 (91 FR 74848, FR Doc. 2026-23429). In its own words, "The final rule is effective on January 19, 2027," and regulated persons "must comply with the applicable requirements of this final rule by July 19, 2027." It leaves 164.504(e) and the Security Rule unchanged, but three changes reach these agreements. Today a practice must act on a patient's access request "no later than 30 days after receipt of the request", with one extension of up to 30 days (164.524(b)(2)); the final rule cuts the first period to "no later than 15 calendar days", keeping one extension of up to 30 calendar days. Today a vendor must disclose electronic copies to "the covered entity, individual, or individual's designee" as needed (164.502(a)(4)(ii)); under the final rule it discloses to the patient or designee only "when specified in the written contract". And under revised 164.532(e), a compliant agreement signed before publication, and not renewed or modified between the effective and compliance dates, stays deemed compliant until it is renewed or modified on or after the compliance date, or January 18, 2028, whichever is earlier. The rule also excludes telecommunications relay service providers, for relay communications, from the business associate definition (new 160.103 paragraph (4)(v)).

The Security Rule changes HHS proposed on January 6, 2025 (90 FR 898, RIN 0945-AA22) are still only a proposal: as of November 17, 2026 the Federal Register shows no final rule or withdrawal under that RIN. They would require written verification of each vendor's technical safeguards "at least once every 12 months" and a contract term requiring the vendor to report activation of its contingency plan "in no case later than 24 hours after activation".

Common questions

Does every vendor need to sign a business associate agreement?

No, only vendors that handle protected health information for the practice. A provider receiving records to treat the patient is not one, nor is the practice's workforce or, in HHS's view, a carrier that only transmits data. A company that stores the data is one even if it never looks at it.

How quickly must a business associate report a breach?

Without unreasonable delay and no later than 60 calendar days after discovering a breach of unsecured protected health information (45 CFR 164.410). It must also report any security incident and any use or disclosure the agreement does not allow. Most practices negotiate a much shorter deadline, stated in days (our reading).

Are business associates directly liable under HIPAA?

Yes. The HITECH Act applies the Security Rule's safeguard sections and the civil and criminal penalty provisions to business associates (42 U.S.C. 17931 and 17934), and HHS imposes civil money penalties on them (45 CFR 160.402). A practice can also be liable for a vendor acting as its agent.

Can I sign the vendor's standard business associate agreement?

Yes, if it contains every term 45 CFR 164.504(e) requires and nothing in the vendor's other terms overrides it. Then check what it leaves out: notice deadlines, breach costs and the vendor's own use of the data are where standard forms tend to favor the vendor (our reading).

Update log

  • November 20, 2026. The HIPAA Privacy Rule final rule was published November 19, 2026 (91 FR 74848). Its link now points to the published document, and its dates are now the ones it states: effective January 19, 2027, compliance by July 19, 2027 (this page had computed January 18 and July 17, 2027).
  • November 17, 2026. Published. 45 CFR 160.103, 160.402, 160.404, 102.3, 164.304, 164.308, 164.314, 164.410, 164.502, 164.504 and 164.524 (eCFR, up to date as of November 13, 2026), 42 U.S.C. 17931 and 17934 (uscode.house.gov, current through Pub. L. 119-124), HHS's 2013 Omnibus Rule preamble, its 2019 and October 2026 penalty notices, the January 2025 proposed Security Rule with a Federal Register check of its status, and the HIPAA Privacy Rule final rule on public inspection (FR Doc. 2026-23429), all read at the source November 17, 2026.

Sources

Related

Published November 17, 2026; updated November 20, 2026. General information, not legal advice. See the disclaimer.

Signing a vendor's business associate agreement, or sending your own?

DPS Law drafts and reviews business associate agreements for practices, clinics and med spas, and for the billing, IT, management and marketing vendors that serve them, including the subcontractor agreements behind them, under HIPAA and North Carolina law. Our attorney is licensed in North Carolina only.

Business and contract law