HHS's software-vendor FAQ asks whether the vendor's functions or services involve access to protected health information. The operational takeaway is to review the actual support path, not assume that software access is incidental or that a product name settles the question.
Trace the support path
| Question | Evidence |
|---|---|
| What can support staff see? | Role and field permissions |
| When can they see it? | Ticket, session, or approval record |
| What service requires access? | Contract and support description |
| Is access logged? | Audit record and retention rule |
| Who reviews the relationship? | Named privacy or contract owner |
Use the HHS software-vendor FAQ for the relationship analysis. Do not call a vendor compliant based on this worksheet.
Separate application use from maintenance access
An agency employee's normal use of a system and a vendor technician's support access are different facts. Document both, including emergency access and the approval route.
FAQ
Does remote support automatically make a vendor a business associate?
No. Review the functions, access, and arrangement. Remote location is only one fact.
Should every support session be recorded?
Use the agency's approved security and privacy policy. The review should identify what evidence exists and who can inspect it.
Can a VA classify the vendor?
A VA can collect contracts and session evidence. The agency's privacy or legal owner should make the classification.
Related research
See the cloud provider review and remote access safeguards.

