Skip to main content
HIPAA

Business Associate Agreements (BAA) Explained

Published
Last updated
HIPAA
A glowing contract with a signature line and a medical shield, linked to a hospital on one side, a cloud server on the other and a smaller subcontractor agreement below, representing a HIPAA business associate agreement

If you sell software or services to US healthcare organisations, a business associate agreement (BAA) is usually one of the first documents your customer sends. This guide explains who counts as a business associate, what a BAA must contain, how subcontractor BAAs work and the red flags to check before you sign. For hands-on help, see our HIPAA compliance consulting page.

This is a practical guide, not legal advice. Have your lawyer review any BAA before you sign it.

What is a business associate under HIPAA?

A business associate is a person or company that creates, receives, maintains or transmits protected health information (PHI) on behalf of a covered entity, such as a healthcare provider, health plan or healthcare clearinghouse. Cloud software vendors, billing companies, IT support providers and analytics firms are common examples when they handle PHI for a covered entity.

HIPAA applies to covered entities and to their business associates. Once you are a business associate, you must sign a BAA with the covered entity and you are directly responsible for meeting the HIPAA Security Rule for the ePHI you handle.

Some quick tests:

  • You host or process patient data for a hospital or clinic. You are almost certainly a business associate.
  • Your support team can see PHI in customer accounts. Access counts, even if you never download it.
  • You only see data that has been properly de-identified. You may not be a business associate. Check carefully before relying on this.
  • Your company is outside the US. Location doesn't change the answer. What matters is whether you handle PHI for a covered entity or business associate.

What is a business associate agreement (BAA)?

A business associate agreement is the contract between a covered entity and a business associate, or between a business associate and its subcontractor, that sets out how PHI may be used and protected. HIPAA requires one before the business associate handles PHI. It turns HIPAA obligations into contractual commitments that both sides can rely on.

A BAA is usually a separate document or an addendum to your main services agreement. Large healthcare customers tend to use their own template, and many cloud and software vendors offer a standard BAA of their own.

What must a BAA contain?

A BAA must state the permitted uses and disclosures of PHI, require appropriate safeguards, require reporting of breaches and security incidents, pass the same duties to subcontractors, and require the return or destruction of PHI when the contract ends. It also commits the business associate to support individuals' rights and to make its records available when required.

The core clauses to look for:

ClauseWhat it coversWhat to check
Permitted uses and disclosuresWhat you may do with PHIIt matches the service you actually provide
SafeguardsYour duty to protect ePHI under the Security RuleYou can meet it with your current controls
Breach and incident reportingHow and when you tell the customerThe deadline is one you can actually meet
SubcontractorsPassing the same duties down the chainYou have BAAs with your own vendors
Individual rightsHelping with access and amendment requestsYou can find and export a person's records
Records and booksMaking records available when requiredYou keep the documentation
Return or destructionWhat happens to PHI at the endYou can delete it from backups as well
TerminationEnding the contract if terms are brokenThe trigger and notice are reasonable

On breach reporting, remember the wider rule: individuals must be notified without unreasonable delay and no later than 60 days after discovery. If more than 500 residents of a state or jurisdiction are affected, HHS and the media must also be notified. Customers often ask business associates to report much faster than 60 days, so they have time to meet their own duties.

What are subcontractor BAAs?

A subcontractor BAA is the agreement a business associate signs with its own vendor when that vendor creates, receives, maintains or transmits PHI on its behalf. The subcontractor takes on the same duties, so HIPAA protection follows the data down the chain. Your cloud provider, backup service and support tools may all need one.

Map your vendors against the data flow you drew in your risk analysis. For each vendor that touches PHI:

  1. Confirm the vendor will sign a BAA, and which of its services the BAA covers.
  2. Sign it before any PHI reaches that vendor.
  3. Configure the service the way the vendor's BAA and documentation require.
  4. Keep a register of signed BAAs with renewal dates.

For SaaS teams, the cloud provider's BAA is the big one. See HIPAA compliance for SaaS companies for how the shared responsibility model works.

What red flags should you check before signing a BAA?

Check for breach reporting deadlines you can't meet, unlimited liability or indemnity, obligations that go beyond HIPAA, audit rights with no notice limits, and terms that cover services you don't provide. CyberWave GRC reviews BAAs as part of HIPAA readiness so the commitments match the controls you actually run. Your lawyer should still review the final contract.

  • Very short breach deadlines. A few hours may be impossible if your investigation process takes longer.
  • Uncapped liability. This is a commercial and legal question, not a security one, so involve your lawyer.
  • Security requirements beyond HIPAA. Some customers add their own standards, such as specific encryption or testing duties. Make sure you can meet them.
  • Vague scope. The BAA should describe the PHI and services it covers.
  • Deletion you can't perform. Check that you can return or destroy PHI, including backups, within the stated time.
  • No subcontractor flexibility. You need to be allowed to use the vendors your service depends on.

How do BAAs work for vendors outside the US?

A company in India or elsewhere outside the US that creates, receives, maintains or transmits PHI for a US covered entity or business associate is a business associate and needs a BAA. Location doesn't matter; the data and the relationship do. Your US customer will almost always require a signed BAA before sharing any PHI with your team.

Indian vendors should also check data flows across borders, remote access by offshore teams and any local subcontractors. Our guide to HIPAA compliance for Indian companies covers the full picture.

What else do you need besides a signed BAA?

A BAA is a promise to comply, not proof that you do. Alongside it you still need a risk analysis, documented administrative, physical and technical safeguards, workforce training and a breach response process. Customers increasingly ask for evidence too, such as an independent third-party assessment report, before they trust a vendor with PHI.

There is no official HIPAA certification. Vendors show compliance through a risk analysis, documented safeguards and an independent assessment. Start with our HIPAA risk assessment guide, then use the HIPAA compliance checklist to see what assessors expect.

How should you prepare before your first BAA?

Before your first BAA, map where PHI will flow, complete a risk analysis, put the core safeguards in place, sign BAAs with any vendor that will touch PHI and set up a breach response process with realistic timelines. Then you can sign with confidence, because you know the commitments match how your service actually works.

A short internal checklist helps:

  • PHI data flow diagram, approved by engineering.
  • Risk analysis and risk management plan.
  • Policies for access, encryption, logging, incident response and retention.
  • Signed subcontractor BAAs.
  • A named person responsible for HIPAA compliance.
  • Documentation kept for six years.

Frequently asked questions

Yes. An Indian company that creates, receives, maintains or transmits protected health information for a US covered entity or business associate is a business associate under HIPAA, so it needs a signed BAA. Where your company is based does not change this. US customers will normally ask you to sign one before they share any patient data with you.

No. A BAA is a contractual promise to protect PHI, not proof that you do. You still need a risk analysis, documented administrative, physical and technical safeguards, workforce training and a breach response process. There is no official HIPAA certification, so customers often ask for an independent third-party assessment report as evidence as well.
Hi! I'm your AI Assistant 💬