A Business Associate Agreement (BAA) is a legally binding contract between a HIPAA-covered entity (like a healthcare provider, health plan, or healthcare clearinghouse) and a business associate — any person or organization that performs services involving access to protected health information (PHI).
In plain terms: if you are a healthcare organization and you use a third-party service that will see, store, process, or transmit patient data, you need a BAA with that vendor before a single byte of PHI touches their systems.
The BAA is not a nice-to-have. It is a federal requirement under the HIPAA Privacy Rule and the HITECH Act. Operating without one when you should have it is itself a HIPAA violation, regardless of whether a breach ever occurs.
You need a BAA any time a third party will have access to PHI in the course of providing services to your organization. Common examples include:
You do not need a BAA when:
HIPAA regulations at 45 CFR § 164.504(e) specify the required elements. A valid BAA must:
The penalties for failing to have a BAA in place are severe:
Financial penalties: The HHS Office for Civil Rights (OCR) has imposed millions of dollars in fines specifically for BAA failures. In recent years, settlements have ranged from $100,000 to over $5 million for BAA-related violations.
Breach liability: Without a BAA, there is no contractual framework for how a vendor handles a breach. You have no legal recourse and no defined notification timeline. You are exposed on every front.
Reputational damage: Patients trust you with their most sensitive information. A breach resulting from a missing BAA signals negligence at the most basic level of compliance.
Criminal exposure: In cases of willful neglect, individuals can face criminal charges including fines up to $250,000 and imprisonment for up to 10 years.
Use our penalty calculator to estimate the potential financial impact of a violation.
Most established software vendors that serve healthcare have BAA processes in place:
Large vendors (AWS, Google, Microsoft, etc.): Typically offer a standard BAA that you accept through their admin console. These are non-negotiable but generally comprehensive.
Mid-size SaaS vendors: Usually have a standard BAA template. Some include it in their enterprise or healthcare-specific plans. Others provide it on request.
Small vendors or startups: May not have a BAA ready. This is a red flag but not necessarily a disqualifier — they may be willing to sign one. If they refuse or don't understand what a BAA is, do not use them for PHI.
Our HIPAA compliant software directory indicates which vendors offer BAAs, making it easy to filter for compliant options from the start.
Mistake 1: Assuming a BAA exists because the vendor says they are "HIPAA compliant." Marketing claims are not contracts. If you do not have a signed BAA document, you do not have a BAA.
Mistake 2: Using a generic template without legal review. BAAs should be reviewed by legal counsel familiar with HIPAA. A poorly drafted BAA can leave significant gaps in your protection.
Mistake 3: Failing to track and manage BAAs. You need a system to track every BAA — who signed it, when, what it covers, and when it expires. Many organizations discover missing BAAs only during an audit.
Mistake 4: Not updating BAAs when relationships change. If a vendor's scope of services changes, or if they start handling different types of PHI, the BAA should be updated to reflect the new reality.
Mistake 5: Ignoring subcontractor BAAs. Your vendor is responsible for their subcontractors, but you should verify they have the appropriate agreements in place. A breach at a sub-subcontractor with no BAA is still your problem.
A Non-Disclosure Agreement (NDA) is not a substitute for a BAA. An NDA is a general confidentiality agreement; a BAA is a HIPAA-specific contract with legally defined requirements. You may need both, but an NDA alone does not satisfy HIPAA requirements.