HHS security guidance addresses risks associated with remote use of electronic protected health information. A remote-workstation review should identify the person, device, access path, and safeguard evidence rather than rely on a general policy statement.
Workstation review
| Field | Evidence | Owner |
|---|---|---|
| User | Role and approved purpose | Access owner |
| Device | Managed device or approved context | IT owner |
| Access path | Application and authentication method | Security owner |
| Safeguard | Policy or technical control | Security owner |
| Review | Date and disposition | Agency designee |
Use HHS remote use guidance with the agency's risk analysis. The worksheet does not certify a device or create a universal control list.
Review the actual workflow
Document where the user works, what information the task requires, and how the agency handles loss, access changes, and support. Route exceptions to the security owner.
Evidence table
| Check | Evidence | Follow-up |
|---|---|---|
| Purpose is documented | Task record | Narrow unclear purpose |
| Device is identified | Inventory entry | Resolve unknown device |
| Access is authorized | Approval record | Review entitlement |
| Exception is tracked | Action log | Assign disposition |
FAQ
Does remote access automatically violate HIPAA?
No. The agency must assess its safeguards and risks under the applicable requirements. Use HHS guidance and qualified advice.
Is a password policy enough?
Do not assume that. Review the full workflow, device, access, and incident controls relevant to the risk analysis.
Can an assistant approve remote access?
An assistant can gather evidence. The designated security or privacy owner should approve access scope.
Related research
Compare this with the remote access safeguards review and HIPAA software vendor access review.

