I explain Business Associate Agreement basics in plain terms and why they matter. I share a simple checklist you can use to decide when you need one and what to include.
What a BAA is
A Business Associate Agreement is a HIPAA required contract that sets rules for vendors who handle protected health information (PHI) for you. HIPAA is a health privacy law, and protected health information means any data that can identify a person and relates to their health or care. A BAA spells out what the vendor may do with that data and how they must protect it. Confirm specifics with your attorney or compliance advisor.
When you need one
You need a BAA when a service provider creates, receives, maintains, or transmits protected health information (PHI) on your behalf. Common examples include IT providers that manage backups, cloud or email services used for protected health information (PHI), e-fax or billing services, online forms that collect patient details, and support vendors who can see records while helping your staff. If a vendor will not see or handle protected health information (PHI) at all, a BAA may not be required, but get legal confirmation before you proceed.
What a BAA should cover
- Permitted and required uses and disclosures of PHI.
- Administrative, physical, and technical safeguards the vendor must maintain.
- Duty to report a suspected breach and cooperate with your response.
- Flow down terms to any subcontractors with access to the same data.
- Support for patient rights requests when the law applies, like access or an accounting of disclosures.
- How services end, including returning or securely destroying data.
- Rights to verify compliance, such as reasonable documentation or audits.
Steps to get it done
- List vendors and tools that touch your data, including hosting, forms, backups, support, and analytics.
- Mark which ones could see PHI. If yes, get a signed BAA before sharing anything.
- Use the vendor's BAA or have counsel review your template. Check the items above are included.
- Store signed BAAs in one place, assign an owner, and review on a schedule.
- Train staff not to send PHI to any vendor without a BAA. Add a quick check in your help desk intake.
- Configure systems to minimize PHI in logs and emails, and include backups and monitoring in scope.
- When a vendor leaves, shut off access and confirm return or destruction of data in writing.
A quick example
For a medical practice using cloud storage, online intake forms, and an e-fax tool, I mapped data flows, identified which vendors could see PHI, signed BAAs with those vendors, and adjusted settings to avoid extra identifiers. Counsel reviewed the templates before signature.
How I can help
I can organize your vendor list, map data flows, and prepare action steps under my Security & Compliance > HIPAA Compliance service so you move forward with confidence.
Get the next one in your inbox
Pick your topics and how often, from weekly to quarterly. I send a confirmation email first, and you can change or stop it any time.
Get more like this by emailMore in Security & Compliance
ADA levels and expectations
I explain ADA and WCAG levels in plain words and give clear steps to meet common expectations.
ADA quick audit
I share a quick ADA website checklist you can run this week to catch common issues.









