All articles
HIPAAComplianceHealthcare

What a Business Associate Agreement Must Include

The clauses a HIPAA business associate agreement must contain, checked line by line against 45 CFR 164.504(e), plus when you need one and what it won't do.

By the Clarigo Editorial Team · November 18, 2026 9 min read

Share
Short answer: A HIPAA business associate agreement (BAA) must set out what the vendor may do with protected health information (PHI), bind it to use safeguards and the Security Rule, require it to report misuse, security incidents and breaches, flow the same terms down to its subcontractors, support patients' access, amendment and accounting rights, open its records to HHS, return or destroy PHI at the end, and let the covered entity terminate for a material breach. Those terms come from 45 CFR 164.504(e) and 164.314(a).

A BAA is the contract that lets a hospital, clinic or health plan share patient data with a vendor. Most people sign one without reading it, because it arrives as a template. That is a mistake on both sides: the clauses decide who reports what, how fast, and what happens to the data when the relationship ends.

This guide walks through each required clause against the regulation text, explains when a BAA is needed and when it is not, and covers what a BAA cannot do for you. It is general information, not legal advice. Have a healthcare lawyer review any agreement before you sign it.

When you need a BAA

HIPAA applies to covered entities (health plans, health care clearinghouses, and health care providers that carry out certain transactions electronically) and to their business associates. The definition in 45 CFR 160.103 makes a person or company a business associate when, outside the covered entity's own workforce, it creates, receives, maintains or transmits PHI on the covered entity's behalf, or provides services such as legal, accounting, consulting, data aggregation, management or administration that involve PHI.

In practice that includes most software vendors in healthcare: the company hosting a patient portal, the billing platform, the cloud provider storing records, the developer with production access, and the AI vendor whose scribe drafts clinical notes. The definition also names health information organizations, e-prescribing gateways and other data transmission services that need routine access to PHI.

Under 45 CFR 164.502(e), the satisfactory assurances a covered entity needs from a business associate must be documented in a written contract or other written arrangement that meets 164.504(e). That written contract is the BAA. If you are building software that will touch PHI, our HIPAA-compliant software development page explains how we set this up from day one.

When you do not need one

The same definition lists who is not a business associate:

  • A health care provider receiving PHI for treatment. A hospital sending records to a referring specialist does not need a BAA with that specialist.
  • A plan sponsor receiving data from a group health plan, where the separate plan-document rules in 164.504(f) apply and are met.
  • A government agency determining eligibility for, or enrollment in, a government health plan, where the law authorizes it.
  • A covered entity in an organized health care arrangement performing functions for that arrangement.
  • Your own workforce. Employees, volunteers and trainees under your direct control are workforce members, not business associates.

Two more cases come up often. A vendor that never creates, receives, maintains or transmits PHI for you, such as a design agency working only with dummy data, is not a business associate. And a consumer health app that a patient chooses and uses for themselves is usually outside HIPAA altogether, because it is not acting on a covered entity's behalf. We cover that case in our article on HIPAA rules for mobile health apps, and our healthcare app development team can tell you which rules apply to your product.

The required clauses, one by one

The table maps each clause to the paragraph of 45 CFR 164.504(e) or 164.314(a) that requires it.

ClauseWhere it comes fromWhat it must sayWhat to check
Permitted uses and disclosures164.504(e)(2)(i)The uses and disclosures of PHI the business associate is allowed or required to makeIs the scope tied to the actual service, not "any lawful purpose"?
No other use164.504(e)(2)(ii)(A)No use or disclosure beyond the contract or what the law requiresAre analytics, product improvement or AI training carved out or prohibited?
Safeguards and Security Rule164.504(e)(2)(ii)(B), 164.314(a)(2)(i)(A)Appropriate safeguards, and compliance with the Security Rule for electronic PHIDoes it name the Security Rule, not just "reasonable security"?
Reporting164.504(e)(2)(ii)(C), 164.314(a)(2)(i)(C)Report any use or disclosure not allowed by the contract, any security incident, and breaches of unsecured PHI under 164.410Is there a defined deadline and a named contact?
Subcontractors164.504(e)(2)(ii)(D), 164.314(a)(2)(i)(B)Subcontractors handling PHI agree to the same restrictions and conditionsDoes the vendor list who its subcontractors are?
Patient access164.504(e)(2)(ii)(E)Make PHI available for access under 164.524How fast will it hand data over when a patient asks?
Amendment164.504(e)(2)(ii)(F)Make PHI available for amendment and apply amendments under 164.526Can corrections be made in its system?
Accounting of disclosures164.504(e)(2)(ii)(G)Provide the information needed for an accounting under 164.528Does it log disclosures in a form you can use?
Covered entity duties164.504(e)(2)(ii)(H)Follow the Privacy Rule wherever it performs one of your obligationsRelevant if it sends notices or handles requests for you
Books and records164.504(e)(2)(ii)(I)Open its practices, books and records on PHI to the HHS SecretaryPresent, usually without changes
Return or destroy164.504(e)(2)(ii)(J)At termination, return or destroy PHI and keep no copies, or extend protections where that is not feasibleFormat, timeline and proof of deletion, including backups
Termination164.504(e)(2)(iii)The covered entity may terminate if the business associate violates a material termIs the right real, or buried behind long cure periods?

Clauses the rule allows but does not require

The contract may let the business associate use PHI for its own proper management and administration, or to carry out its legal responsibilities, under 164.504(e)(4). It may also permit data aggregation services relating to the covered entity's health care operations. Read these carefully: they are the paragraphs vendors widen.

Breach and incident reporting: the clause that matters most

Under 45 CFR 164.410, a business associate must notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery. A breach counts as discovered on the first day it is known, or would have been known with reasonable diligence, to any employee, officer or agent other than the person who caused it. The notice must identify, as far as possible, each affected individual, along with the other information the covered entity needs for its own notices.

Sixty days is the outer limit, not a target. The covered entity has its own deadline to notify patients, and it cannot start until it hears from you. Covered entities commonly negotiate a much shorter reporting window in the BAA, and a vendor that has a working incident process should be able to accept one.

Also note the wording "security incident" in 164.314. That is wider than a breach. Agree in the contract on how routine, unsuccessful attempts (port scans, blocked logins) are reported, so neither side drowns in notices nor misses a real event.

Subcontractor BAAs

The obligations flow down the chain. Under 164.502(e)(1)(ii), a business associate may let a subcontractor create, receive, maintain or transmit PHI only after getting the same satisfactory assurances, and 45 CFR 164.314(a)(2)(iii) applies the same contract requirements to that relationship. The covered entity does not need a direct agreement with the subcontractor.

For a software product, the chain is usually: clinic, then your company, then your cloud host, email or SMS provider, error tracker and any AI model provider that sees PHI. Each link needs its own BAA. A common gap is a monitoring or logging tool that quietly receives PHI in error messages without one. Our HIPAA-compliant cloud hosting setup keeps that list short and documented.

The rule also works upward: a business associate that knows of a pattern of activity by a subcontractor that materially breaches the contract must take reasonable steps to cure it, and terminate if that fails and termination is feasible (164.504(e)(1)(iii)). The same duty applies to a covered entity that knows of such a pattern by its business associate.

What a BAA does not do

  • It does not make anyone compliant. It is a promise. The vendor still has to run a risk analysis, apply the Security Rule safeguards and train its people.
  • It does not certify a product. There is no HIPAA certification issued by HHS, so "HIPAA certified" on a sales page means nothing on its own.
  • It does not cover data outside its scope. If you send PHI to a service the agreement excludes, the BAA does not protect that data.
  • It does not shift your own duties. The covered entity still owes patients their notices and rights, and must act if it learns its vendor is in material breach.
  • It does not settle commercial risk. Who pays for breach notification, insurance, indemnities and liability caps are commercial terms that the regulation does not set. Negotiate them separately.

HHS publishes sample business associate agreement provisions that many templates start from. They are a starting point, not a finished contract.

A checklist before you sign

  1. Confirm the vendor actually handles PHI, and on whose behalf.
  2. Tie permitted uses to the service, and say explicitly whether de-identification or model training on your data is allowed.
  3. Set a reporting deadline shorter than 60 days, and name contacts on both sides.
  4. Ask for the subcontractor list and how you will hear about changes.
  5. Agree how data is returned (format) and destroyed (including backups), and how fast.
  6. Check that the termination right is usable.
  7. Line the BAA up with the main services agreement so the two do not conflict.

If you are unsure where your gaps are, a short HIPAA compliance assessment maps your vendors and data flows before an auditor or a customer does.

How we handle BAAs in our own products

Our own healthcare products follow this rule strictly. Clarigo Clinic OS automates the front office for specialty clinics, and we sign a BAA before any patient data is touched. A person approves anything medical or financial, and every action is in a full audit trail. Clarigo EHR is a cloud EHR with HL7 and FHIR interfaces, encryption and role-based access, and its AI scribe only drafts notes for clinicians to sign. For a wider view of building HIPAA software, read our HIPAA-compliant app development guide.

About Clarigo Infotech

Clarigo Infotech is an AI-first software and app development company in Indore, India. Since 2016, our in-house senior team has delivered 600+ projects for clients in 20+ countries. Our HIPAA-trained team has HL7 and FHIR integration experience, and we offer 24/7 support. Senior engineers typically cost US$25 to US$49 per hour, a first version (MVP) is usually live in roughly 25 to 30 days, and you own the source code. To review the BAAs and vendors behind your product, talk to our team.

Frequently asked questions

What must a HIPAA business associate agreement include?

+

Under 45 CFR 164.504(e) and 164.314(a), it must set the permitted uses and disclosures of PHI, bar any other use, require safeguards and Security Rule compliance, require reporting of improper uses, security incidents and breaches, flow the same terms down to subcontractors, support patient access, amendment and accounting of disclosures, open records to HHS, require return or destruction of PHI at the end, and allow termination for a material breach.

How quickly must a business associate report a breach?

+

45 CFR 164.410 requires notice to the covered entity without unreasonable delay and no later than 60 calendar days after the breach is discovered. That is the legal maximum. Many covered entities negotiate a much shorter window in the BAA, because they need time to notify patients themselves.

Do I need a BAA with a doctor I refer a patient to?

+

No. The HIPAA definition of business associate excludes a health care provider receiving PHI from a covered entity for the treatment of the individual. BAAs are for vendors and service providers acting on your behalf, not for other providers treating the same patient.

Does a subcontractor need its own BAA?

+

Yes. A business associate must get the same written assurances from any subcontractor that creates, receives, maintains or transmits PHI for it, such as a cloud host, email provider or AI model provider. The covered entity does not need to sign directly with the subcontractor.

Does signing a BAA make a vendor HIPAA compliant?

+

No. A BAA is a contractual promise. The vendor still has to carry out a risk analysis, apply the Security Rule safeguards, train its staff and follow its own policies. HHS does not certify products or vendors as HIPAA compliant.

From our own work

Projects our team has delivered that relate to this article.

About the author

Clarigo Editorial Team

Written by the team at Clarigo Infotech, an AI-first software and app development company in Indore, India. Since 2016 our in-house team has delivered 600+ projects for clients in 20+ countries, and our articles draw on that work. Read about the company, or see our case studies and portfolio.

Found this useful? Share it with your team.

Planning something like this?

Get a free consultation. A senior engineer replies within one working day with a scoped plan.

How should we contact you?

No obligation. We reply within one working day.

Keep reading