HHS describes a business associate by the function performed for a covered entity and the relationship to protected health information. The safe starting point is a documented role and data-flow review, not a claim that a named service is compliant.
The threshold questions
| Question | Evidence to collect | Reviewer |
|---|---|---|
| What function is performed? | Work order and workflow map | Privacy owner |
| Is PHI created, received, maintained, or transmitted? | Field and system inventory | Security owner |
| Is the person workforce or an outside party? | Contract and access record | Legal or HR owner |
| Is access incidental or part of the service? | Actual task steps | Privacy owner |
| What agreement is required? | Counsel-reviewed contract record | Contract owner |
The HHS Business Associates guidance should be read with the facts of the specific arrangement. This article is an operational worksheet, not legal advice.
Keep four relationships separate
Do not use “contractor” as a substitute for a HIPAA relationship analysis. A workforce member, outside business associate, subcontractor, cloud provider, and party with incidental contact can have different obligations.
Write down who decides the classification and where the decision is stored. If the facts change, reopen the review rather than carrying forward an old label.
FAQ
Does a remote location determine business-associate status?
No. Location is one fact in the workflow. The function and access relationship still need review.
Does signing a BAA prove compliance?
No. HHS contract provisions are one part of the relationship. The covered entity still evaluates its safeguards and responsibilities.
Can an administrative worker make the classification?
The worker can gather facts and maintain the file. The agency should assign the legal or privacy decision to the appropriate owner.
Related research
Pair this threshold worksheet with remote access safeguards and the remote ePHI risk review.

