Do we need to sign anything? Business Associate Agreements explained simply

A Business Associate Agreement (BAA) sounds formal, but think of it as a safety contract: "We are trusting you with patient information—here is how you must protect it, what happens in a breach, and how we end the relationship if needed."

Who needs a BAA?

If a company creates, receives, maintains, or transmits patient information for your practice—not just sells you paperclips—you probably need a BAA.

Common examples: EHR hosting, billing services, cloud storage, IT support with server access, email services that see message content, and many telehealth platforms.

What if we skip it?

You can be out of compliance even if the vendor is great. Regulators expect paperwork that matches reality. Patients also lose clarity about who is responsible if data is mishandled.

How do you get one?

Ask the vendor. Serious healthcare vendors expect this question. They often have a standard BAA ready to sign. Read it—or have counsel read the first one—and keep a copy where you can find it.

Does the vendor's "HIPAA compliant" badge replace a BAA?

No. A badge might describe their controls, but your practice still needs the contract that spells out legal duties.

Want a deeper dive?

Our intelligence article walks through BAAs in more detail for teams negotiating terms: What is a BAA?