Smarter eCommerce Product Management at Scale📦
June 10, 2026
Healthcare practices often ask whether they need a Business Associate Agreement (BAA) when using marketing and automation tools. This article explains what a BAA is, what it covers, and when it’s required.
A Business Associate Agreement (BAA) is a HIPAA-required contract between a healthcare provider (Covered Entity) and a vendor/partner (Business Associate) that may handle PHI.
A BAA defines:
What PHI can be used for
Safeguards that must be in place
Breach reporting responsibilities
Who else can access PHI (subcontractors)
Rules for returning or destroying PHI
A BAA is typically required when a vendor may:
Store or transmit patient/client data
Handle intake forms containing health details
Access notes or communications that include PHI
Send emails/SMS where PHI may appear
Maintain calendars/invoices that could contain PHI context
In short: if PHI could exist in the tool, a BAA is usually required.
They are not the same.
NDA / Confidentiality Agreement:
General promise to keep information private
Not HIPAA-specific
Does not address HIPAA breach duties or safeguards
BAA:
HIPAA-specific legal agreement
Includes required HIPAA clauses and obligations
Addresses breach notification and PHI handling rules
Many practices use both, but an NDA does not replace a BAA.
If you use Xtreme Automator® in PHI-free marketing mode, you may not need a BAA (because PHI should not enter the platform).
If you enable our HIPAA Compliance Add-On and use Xtreme Automator® for workflows where PHI may exist (messages, forms, notes, etc.), a BAA is required.
If you answer “yes” to any of these, you likely do:
Will patients/clients message you inside the platform?
Will you store intake details in forms/surveys?
Will staff add notes that reference clinical needs?
Will emails/SMS include personal health details?
Will you store attachments that could contain PHI?
If “no” to all, PHI-free marketing mode may be a better fit.