A billing vendor sends over a signed BAA. The legal names are right. The signature blocks are complete. Nobody at the practice can say which inbox receives an incident notice, who can authorize support access, or what evidence arrives when the contract ends.
The document exists. The operating agreement does not.
Takeaways
- Start with the HHS sample provisions, then adapt them to the real service and contract.
- Classify the vendor from its work and data flow, not its marketing category.
- Add a responsibility schedule with owners, notice routes, evidence, and exit steps.
- Test the schedule with an invented incident before signing.
This worksheet is educational, not legal advice. Have qualified privacy and contract counsel review the final agreement and its relationship to the services contract.
Decide why the agreement is required
HHS explains that a business associate generally performs certain functions or services for a covered entity and has access to protected health information in that role. Its business-associate guidance also describes exceptions and arrangements that need separate analysis.
Write a short classification note before editing a template:
| Question | Practice record |
|---|---|
| What service is being bought? | named service and contract version |
| What information can the vendor create, receive, maintain, or transmit? | field-level data-flow inventory |
| On whose behalf is the work performed? | covered function or service owner |
| Which exception was considered, if any? | reasoning and reviewer |
| What changes trigger a new review? | scope, data, subprocessors, hosting, or integration |
Do not let a checkbox replace that note. The same vendor can have different roles under different services.
Use the HHS provisions as the legal spine
HHS publishes sample BAA provisions. They cover the business associate’s permitted uses and disclosures, safeguards, reporting, subcontractors, support for certain individual rights, access for HHS, and return or destruction at termination. HHS says the language is sample language, not a complete contract for every arrangement.
A practice can turn that spine into a drafting checklist:
- identify both parties and the services agreement the BAA supports;
- define permitted uses and disclosures without silently expanding the service;
- state safeguard and reporting duties in language counsel approves;
- address subcontractors that handle protected health information;
- assign support for access, amendment, accounting, and government requests where applicable;
- set termination, return, destruction, and infeasibility handling;
- reconcile conflicts with the master agreement, order form, privacy notice, and incident plan.
The regulation at 45 CFR 164.504 contains the contract requirements. Quote the current rule through counsel rather than copying a summary from a vendor page.
Attach the schedule people will actually use
The BAA should not become a technical runbook, but the contract file needs a controlled companion that translates duties into action.
BAA RESPONSIBILITY SCHEDULE
Service and contract version: ____________________________
Covered data flows: ______________________________________
Permitted support-access route: __________________________
Practice privacy contact and backup: _____________________
Vendor security contact and backup: ______________________
First incident-notice route: _____________________________
Required initial facts: __________________________________
Update cadence during an open event: _____________________
Subcontractor evidence owner: ____________________________
Access/amendment/accounting request owner: _______________
Termination export format and owner: _____________________
Return/destruction evidence: _____________________________
Annual and change-triggered review date: _________________
Keep the schedule versioned with the agreement. A support email, hosting region, or subprocessor list can change while the signature page stays untouched.
Run two hostile contract tests
For the first test, invent a support case in which a vendor technician needs temporary access to troubleshoot an export failure. Ask who approves access, what the technician can see, when access ends, and what event evidence remains. Compare the answer with the contract and product configuration.
For the second, invent an incident discovered late on a Friday. Send no real patient information. Have the vendor and practice teams find the notice route, open an event record, exchange the agreed initial facts, assign updates, and preserve decisions. A clause that nobody can execute is unfinished work.
The vendor risk-assessment guide covers diligence beyond the contract. The incident-response plan covers the practice’s response lane. Keep both connected to the BAA schedule.
Make exit evidence part of the purchase
Ask the vendor to demonstrate export and termination before renewal pressure begins. Record format, scope, encryption, delivery, validation, residual copies, legal holds, backup treatment, and the evidence used to close the account. If return or destruction is infeasible, the HHS sample language addresses continued protection and limited further use; counsel should adapt that provision to the arrangement.
Patient Square does not provide legal advice or decide whether a vendor is a business associate. When Patient Square is evaluated, confirm the selected service, contractual documents, data flow, retention, access, and current security information in writing. A signed BAA is necessary for many relationships. Its value appears when the practice can carry out every assigned duty.