HHS remote-use guidance frames offsite ePHI access as a risk-management matter. A useful approval log has one entry per access workflow and records the approver, safeguards, and evidence retained.
Minimum approval record
| Field | Record |
|---|---|
| Workflow | Task and system |
| Information | ePHI available to the user |
| User and device | Role, device, and location |
| Safeguards | Controls selected by the agency |
| Approval | Owner, date, review date, and exception |
Read the HHS remote-use guidance with the agency's own risk analysis. A completed log is evidence of review, not a compliance guarantee.
Keep exceptions visible
If a user needs a different device, location, or access path, add an exception record. State who approved it, why it is needed, what compensating control exists, and when it will be reviewed.
FAQ
Is approval permanent?
Not by default. The agency's policy determines review timing and triggers for reapproval.
Does the log replace access controls?
No. It records the decision and evidence. Technical and administrative safeguards still operate separately.
Can a VA maintain the log?
Yes, if assigned. The agency's security owner approves access and exceptions.
Related research
Use this log with the remote device checklist.

