Compliance · 2026-04-25 · 11 min read

Business Associate Agreements in 2026: What the Rules Require and a BAA Checklist

Business associates have been directly liable under the Security Rule since 2013, and the January 2025 proposal would add annual safeguard verification if finalized. Here are the elements every BAA must contain, the terms hospitals commonly add, and how to keep your business associate inventory current.

Business Associate Agreements in 2026: What the Rules Require, What May Change, and a BAA Checklist

If you are a covered entity, you probably have a folder of Business Associate Agreements, many built on a template that has not changed much since the 2013 Omnibus Rule. If you are a health-tech vendor, you are on the other side of that folder: every hospital, clinic or payer you sell to sends you its BAA, and you need your own BAAs with the subprocessors that handle PHI for you.

This guide covers what HIPAA requires a BAA to contain today, what the January 2025 proposed Security Rule update would change if it is finalized, the terms hospitals commonly add on top, and how to keep business associate management from living in a spreadsheet.

What has and has not changed

Two things are often confused.

What is already law. Since the HITECH Act and the 2013 Omnibus Rule, business associates have been directly liable for complying with the HIPAA Security Rule and for parts of the Privacy Rule, not just contractually bound. A subcontractor that handles PHI for a business associate is itself a business associate and needs its own BAA. Breach notification has not changed either: a business associate must notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 days after discovery (45 CFR 164.410).

What is only proposed. In January 2025 HHS proposed a major update to the Security Rule (90 FR 898). If finalized as written, it would require business associates to verify to covered entities, at least once every 12 months, that they have deployed the required technical safeguards, and to notify covered entities within 24 hours of activating a contingency plan. It would also make MFA and encryption required for everyone, with limited exceptions. As of November 2026 the proposal has not been finalized, and final action is not expected before 2027. It does not create a 72-hour breach notification deadline.

So a BAA signed years ago is not invalid because of a "2026 rule." It may still be incomplete against the requirements that have applied since 2013, and it may not match what your customers now expect.

Why BAAs deserve attention now

Health-tech companies and their customers rely on more vendors that touch PHI than most teams realize: cloud hosting, email and fax services, support and ticketing tools, analytics, transcription, AI model providers and the IT managed-service provider. Each one that creates, receives, maintains or transmits PHI for you is a business associate, and disclosing PHI to one without a BAA is itself a HIPAA violation. OCR has resolved enforcement cases over missing BAAs, and hospital security reviews routinely ask vendors to list their subprocessors and confirm a BAA is in place with each.

The required elements: what every BAA must contain

Under 45 CFR 164.504(e) and, for ePHI, 164.314(a), a BAA must:

  1. Establish the permitted and required uses and disclosures of PHI by the business associate, and not authorize uses the covered entity itself could not make.
  2. Prohibit other uses and disclosures except as the contract permits or the law requires.
  3. Require appropriate safeguards, including compliance with the Security Rule for ePHI.
  4. Require reporting to the covered entity of any use or disclosure not provided for by the contract, including breaches of unsecured PHI as 164.410 requires, and of security incidents.
  5. Require subcontractors that handle PHI to agree to the same restrictions and conditions, through their own BAAs.
  6. Support individual rights: make PHI available for access and amendment, and provide the information needed for an accounting of disclosures.
  7. Require compliance with the Privacy Rule to the extent the business associate carries out a covered entity's Privacy Rule obligation.
  8. Make internal practices, books and records available to HHS for determining compliance.
  9. Return or destroy PHI at termination where feasible, and extend protections to any PHI that cannot be returned or destroyed.
  10. Authorize termination by the covered entity if the business associate violates a material term.

HHS publishes sample BAA provisions that cover these elements. If your template is missing any of them, fix that first.

Terms hospitals commonly add

Beyond the required elements, many hospitals, clinics and payers add contract terms. None of these is required by HIPAA, but you should expect to see them and decide in advance which you can accept:

  • A shorter breach notification deadline than the 60-day regulatory outer limit, plus a deadline for reporting security incidents.
  • Named security controls, such as MFA on systems with PHI, encryption at rest and in transit, and logging. Many of these appear in the proposed Security Rule update.
  • Evidence and audit rights: a SOC 2 report, a penetration test summary, completion of a security questionnaire, or the right to assess on request.
  • Subcontractor terms: a current list of subprocessors that handle PHI, and notice before adding new ones.
  • Data location and AI terms: where PHI is stored and processed, and whether vendors, including AI model providers, may use PHI to train models.
  • Insurance and indemnification: cyber liability coverage minimums and allocation of breach costs.
  • Return or destruction timelines after termination, with written certification.

For a vendor, the useful exercise is to compare each customer's BAA with what you can actually deliver, and to make sure the BAAs you sign with your own subprocessors give you at least the notice periods you have promised your customers.

Common BAA mistakes

The phantom inventory. Compliance has one vendor list, finance has another, and engineering knows about a third set of tools. Not knowing about a business associate is not a defense.

The stale template. An old BAA that omits security incident reporting, subcontractor flow-down or the Security Rule compliance clause.

The missing subprocessor BAA. A vendor signs BAAs with its customers but not with the cloud, email, support or AI providers that actually hold the PHI.

The evergreen renewal. A BAA that renews automatically while the vendor changes ownership, subcontractors or security posture without review.

The wrong signer. A BAA signed by someone without authority to bind the business associate.

The small vendors. The fax-to-email service, the SMS reminder provider or the transcription tool that handles PHI in small volumes but still needs a BAA.

Building your business associate inventory

Before you can review BAAs, you need to know who your business associates are. A practical approach is to reconcile four sources:

  1. Accounts payable: every vendor paid in the last 24 months.
  2. Single sign-on and identity records: every external system your team logs into.
  3. Email and file-sharing records: external domains that receive data that may include PHI.
  4. Team interviews: the tools each team actually uses, including ones nobody approved.

For each vendor, record whether it creates, receives, maintains or transmits PHI, what PHI it touches, and whether a BAA is in place. Most organizations find vendors they had not listed.

Keeping it current

A BAA program is not annual paperwork. Practical habits:

  • Review high-risk vendors more often: anyone hosting PHI at scale, any AI vendor processing clinical data, and any vendor with a recent ownership change.
  • Track expiry and renewal dates, along with the date you last reviewed each vendor's security evidence.
  • Ask for subcontractor changes and enforce the contractual right to be told.
  • Test the notification path at least annually with a tabletop exercise that simulates a business associate breach.

How Shieldra helps

Shieldra's vendor and BAA tracking, included in the Premium plan, keeps this in one place. You record each vendor and subprocessor, whether it has PHI access and what types, its BAA status with signed and expiry dates, and the signed BAA itself, stored next to the vendor record. Shieldra lists and highlights the BAAs that are expiring soon on the Vendors page, and lets you record a risk assessment for each vendor. The inventory is one you build and maintain; Shieldra does not discover vendors automatically from accounting or identity systems.

Shieldra does not draft or review contracts and does not give legal advice. Have counsel review your BAA template and any customer terms you are asked to accept.


Sources: 45 CFR 164.502(e), 164.504(e), 164.314(a) and 164.410; HHS sample business associate agreement provisions; Federal Register, 90 FR 898 (January 6, 2025). This article is general information, not legal advice.