HHS publishes sample provisions for business associate agreements. The useful count for an agency is the number of agreement questions answered and reviewed, not a made-up “compliance score.”
Build a review index
| Review area | Question to answer | Evidence |
|---|---|---|
| Permitted work | What services and uses are described? | Signed agreement and scope |
| Safeguards | What security expectations are documented? | Policy and control references |
| Incident handling | How are suspected incidents reported? | Notice route and owner |
| Subcontractors | What downstream relationships are covered? | Inventory and agreements |
| Termination | What happens when the work ends? | Return, destruction, or access record |
The HHS sample provisions are a starting point for review. Counsel should adapt any agreement to the facts and applicable law.
Connect the contract to the workflow
Compare each provision with the actual systems, users, and data flows. A contract folder alone does not show whether access is limited, reviewed, or removed when the work changes.
Record the agreement version, effective date, reviewed scope, and unresolved questions. Keep an owner for each open item.
FAQ
Is HHS's sample language a required template?
No. It is guidance for sample provisions. The agency needs a review suited to its arrangement.
Should a cloud provider be ignored because it is not a staffing vendor?
No. HHS cloud guidance addresses business-associate questions for cloud arrangements. Review the provider's actual role and access.
What can a VA do?
A VA can maintain the agreement index and collect evidence. Legal and privacy owners decide unresolved obligations.
Related research
Read the business-associate threshold before using this review index.

