A business associate agreement (BAA) is more than a signature page for a healthcare SaaS vendor. It should connect the services you provide with the safeguards, incident responsibilities, subcontractor controls, and operational evidence needed to handle protected health information (PHI) responsibly. This reusable business associate agreement checklist helps technology and compliance teams review a new BAA, renew an existing agreement, or reassess the relationship after a product or vendor change.
Overview
Start by treating the BAA review as a vendor-assurance workflow rather than a contract-only task. The agreement should be consistent with the actual data flows, cloud architecture, support model, and security procedures used by the healthcare SaaS company. A contract cannot compensate for an inaccurate service description or controls that the business associate cannot operate in practice.
Before signing, assign an owner for the review and collect four inputs:
- Service scope: What the vendor or SaaS platform does, which environments are involved, and whether the service creates, receives, maintains, or transmits PHI.
- Data-flow details: The categories of PHI involved, systems that store or process it, access paths, integrations, and expected retention or deletion behavior.
- Control evidence: Relevant security policies, audit reports, penetration-test summaries, incident procedures, access-control descriptions, and continuity documentation.
- Contract records: The BAA version, related services agreement, data-processing terms, security addendum, subprocessors, effective date, renewal date, and approved signatories.
Use the BAA as one part of a broader third-party risk assessment. For cloud responsibilities that are split between your team, a SaaS provider, and an infrastructure host, compare the contract with a cloud compliance shared responsibility matrix. The goal is to identify gaps before onboarding, not to discover them during an incident.
Checklist by scenario
1. New vendor or new SaaS service
Complete these checks before the service receives access to PHI:
- Confirm whether the relationship involves a business associate role and document the reasoning.
- Describe the covered services and data-handling activities precisely. Avoid a vague description such as “technology services” when the vendor provides storage, analytics, support, or claims processing.
- List the PHI categories and user populations involved, including data sent through APIs, logs, backups, support tickets, and testing environments.
- Verify that the vendor has identified the systems and locations where PHI may be stored or processed.
- Check that permitted uses and disclosures are limited to the services and purposes agreed by the parties.
- Confirm that the vendor will use appropriate safeguards and will support applicable privacy and security obligations assigned to it.
- Review how the vendor handles access requests, corrections, restrictions, accounting-related requests, and other customer assistance requirements that may apply to the service.
- Identify all subcontractors that may handle PHI, or require a documented process for approving, notifying, and reviewing them.
- Confirm that the vendor can return or securely destroy PHI when the relationship ends, subject to documented retention requirements.
- Record the BAA status, contract owner, security reviewer, legal reviewer, signature date, and service go-live approval.
2. Renewal of an existing BAA
A renewal should test whether the original agreement still matches reality. Compare the current BAA with the last review and ask:
- Has the product added new features, integrations, artificial intelligence functions, analytics, or support channels?
- Has the PHI volume, sensitivity, retention period, or user population changed?
- Have hosting regions, cloud providers, subprocessors, or support locations changed?
- Did the vendor experience an incident, material control change, audit finding, or unresolved security issue?
- Are the contact details and escalation paths still accurate?
- Do the BAA, master services agreement, security addendum, privacy terms, and subprocessor agreement use consistent definitions and obligations?
- Can the vendor provide current evidence that its stated controls are operating as expected?
Do not treat an unchanged signature page as proof that the relationship is unchanged. A short renewal review can reveal that the original scope no longer covers the deployed architecture.
3. Service expansion or material change
Trigger an out-of-cycle review when the vendor begins handling a new PHI category, connects to a new clinical or business system, changes its hosting model, introduces a new support workflow, or adds a subcontractor with access to PHI. Update the covered-data worksheet and determine whether the existing BAA and related agreements still cover the expanded use.
4. Incident or suspected breach
Use the agreement and incident-response plan together. Compare the BAA’s requirements with the operational playbook for detection, investigation, escalation, documentation, and notification. Track who must notify whom, through which channel, with what initial information, and how follow-up updates will be handled. Keep the contractual timeline distinct from the internal target for urgent escalation.
| Review point | Questions to answer |
|---|---|
| Discovery | When and how was the event identified, and who owns the first escalation? |
| Scope | Which systems, records, users, and subcontractors may be involved? |
| Notification | What does the BAA require, who sends the notice, and what information is available? |
| Evidence | What investigation records, decisions, containment actions, and corrective measures must be retained? |
For a fuller operational sequence, see the HIPAA breach response workflow and adapt it to the contract’s escalation requirements.
What to double-check
Covered data and service scope
Walk through a real user journey rather than relying only on contract language. Document where PHI enters the platform, how it moves between services, what appears in logs or alerts, which support personnel can access it, and when it is deleted. Include non-production environments, exports, backups, and temporary files where relevant.
Incident and breach-notification language
Separate security incidents, suspected breaches, service outages, and routine support events. Confirm the parties’ definitions, escalation contacts, required notice content, cooperation duties, investigation support, and recordkeeping expectations. If the agreement uses a notification period, ensure the vendor’s incident team can realistically meet it and that the obligation is reflected in the incident response policy.
Subcontractors
Request a current subprocessor list and identify which providers can access PHI. For each one, record the service, data access, hosting role, approval or notice method, and review date. Confirm that subcontractors handling PHI are bound by appropriate written obligations. Reconcile this list with your vendor register and public subprocessor page where applicable. The subprocessor management workflow offers a useful structure for maintaining the register, even when the BAA review is focused on HIPAA.
Return, destruction, and retained copies
Ask how PHI is returned or destroyed at termination, how deletion is verified, and whether backups or legal retention requirements affect the process. Document the exception, owner, and eventual deletion or review date rather than accepting an indefinite retention statement.
Signature and evidence register
Maintain one record for each BAA with the vendor name, service, scope, version, effective date, expiration or renewal date, signatories, subcontractor review, risk rating, open issues, and next review date. Store the executed agreement where procurement, legal, security, and incident-response teams can locate it quickly.
Common mistakes
- Signing a generic BAA without validating the data flow. The agreement may use acceptable wording while omitting a new integration, log stream, or support process.
- Assuming a security certification replaces contract review. Assurance reports can support the assessment, but they do not establish your specific service scope or responsibilities.
- Ignoring subcontractors. Cloud hosting, monitoring, customer support, and backup providers may all affect PHI handling.
- Leaving incident contacts untested. An accurate phone number and escalation mailbox matter only if the relevant teams monitor them and know the process.
- Failing to reconcile related agreements. Conflicting terms across a BAA, master agreement, security addendum, and privacy document create avoidable ambiguity.
- Reviewing only at renewal. Product and architecture changes can make an agreement outdated long before its renewal date.
- Keeping an informal signature trail. A spreadsheet or contract register should show approval status, not just whether someone remembers signing.
When to revisit
Revisit the BAA inventory before annual planning or seasonal vendor reviews, at every renewal, and whenever workflows or tools change. Also trigger a review when a service adds a new integration, changes cloud infrastructure, introduces a new data-processing feature, changes support access, replaces a subcontractor, or experiences a security incident.
Make the process practical by setting a recurring calendar review and assigning an accountable owner. At each review, export the current vendor and subprocessor lists, compare them with contract records, sample the documented data flows, and close or formally accept open issues. If the review identifies a material change, pause the affected expansion until legal, security, privacy, and operational owners agree on the updated scope.
Finally, keep this checklist with the vendor register and incident-response materials. A BAA is most useful when the people responsible for onboarding, cloud operations, support, and incident triage can find it and understand what it requires. This is operational guidance, not a substitute for advice on a specific agreement or regulatory situation; obtain qualified legal review when the relationship, data, or risk is complex.