How to Respond When a Departing Employee Downloads PHI
What should trigger a PHI incident response?
Treat an unexpected or unusually large download of protected health information (PHI) by a departing employee as a security incident to investigate—not as automatic proof of a reportable breach. A download may have been authorized for a legitimate work purpose, but it may also indicate access or use outside the employee’s role or your policies.
Start your security incident response when monitoring, a manager, or another workforce member flags activity such as bulk exports, searches unrelated to assigned duties, transfers to personal email or cloud storage, or use of removable media. Preserve the alert and report it promptly to your privacy and security leads. HIPAA requires regulated organizations to identify and respond to suspected or known security incidents, mitigate harmful effects where practicable, and document incidents and their outcomes. See the HHS explanation of HIPAA security incident procedures.
Coordinate privacy, security, human resources, and legal personnel as appropriate. Limit discussion to people who need the information to investigate, contain the incident, and make decisions. Follow your incident-response and workforce access termination procedures, and avoid confronting the employee in a way that could prompt deletion of evidence before it is preserved.
How should you secure accounts and revoke access?
Contain the risk promptly while preserving relevant evidence. Disable or restrict the former employee’s accounts and access rights, including remote access, email, file-sharing services, electronic health records, virtual private networks, and third-party applications. Revoke active sessions, authentication tokens, API keys, and other credentials where applicable; reset shared credentials the employee could know.
Coordinate the timing with your investigation team so that access is cut off without unnecessarily destroying useful evidence. Check for delegated access, forwarding rules, connected applications, and other accounts or devices that could provide continued entry. Document what was disabled, by whom, and when.
The HIPAA Security Rule calls for procedures to terminate a workforce member’s access to electronic protected health information (ePHI) when employment or another workforce arrangement ends. This is a required implementation specification within the workforce security standard. See 45 CFR § 164.308.
Which logs and devices should you preserve and review?
Preserve relevant evidence before routine retention periods or automated processes remove it. Secure PHI access audit logs, authentication records, endpoint and mobile-device management records, email and cloud-service logs, file-transfer histories, network records, and alerts covering the employee’s accounts and devices. Record the time period, systems reviewed, and any gaps in available data.
Review records for what was accessed or downloaded, when it happened, how much information was involved, the user account and device used, and whether files were transferred, shared, printed, or deleted. Compare the activity with the employee’s job duties, approved work requests, and departure timeline. HIPAA requires audit controls that record and examine activity in systems containing or using ePHI. See HHS’s HIPAA audit protocol.
Identify organization-owned computers, phones, storage media, and other equipment that may contain PHI. Preserve them securely and have qualified personnel collect or examine them under your evidence-handling procedures. Avoid unnecessary changes to a device before relevant information has been preserved; document who handled each item and when.
How can you determine whether PHI was accessed or retained?
Build a timeline from the available logs and device evidence. Distinguish a file listing or download attempt from evidence that a file was successfully transferred, opened, or retained. Where feasible, verify whether data went to an external destination, such as a personal email account, removable drive, personal cloud storage, or another device.
Determine the nature and amount of PHI involved, including identifiers and the likelihood that individuals could be identified. Establish whether the employee was authorized to access the information and whether the activity was within the scope of that authorization. Ask whether the information was returned, securely deleted, or otherwise made inaccessible, and preserve evidence supporting any conclusion.
Document what is known, what remains uncertain, and the sources supporting each finding. If you cannot establish whether PHI was acquired or retained, record that limitation rather than treating a lack of evidence as proof that no access occurred.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhen does a PHI incident qualify as a reportable breach?
Not every employee PHI download requires breach notification. A download that was permitted under the Privacy Rule and your policies is not automatically a breach. However, an impermissible acquisition, access, use, or disclosure of PHI is presumed to be a breach unless an exception applies or the organization demonstrates a low probability that the PHI was compromised through a documented HIPAA breach risk assessment.
The assessment must consider at least four factors: the nature and extent of the PHI, including identifiers and re-identification risk; who used or received the PHI; whether it was actually acquired or viewed; and the extent to which risk was mitigated. Consider the evidence as a whole, including the employee’s access rights, the transfer destination, whether the employee kept or shared copies, and any verifiable deletion or return. See the HHS Breach Notification Rule guidance and 45 CFR § 164.402.
Notification obligations generally apply when the incident involves a breach of unsecured PHI. If the information was encrypted or otherwise rendered unusable, unreadable, or indecipherable in accordance with HHS guidance, the breach-notification analysis may differ. Document the basis for your decision and consult counsel when facts, applicable state laws, or contractual obligations are uncertain.
How should you document mitigation and notify affected parties?
Create security incident documentation that records when the incident was discovered, how it was reported, the response actions and their timing, the evidence reviewed, the PHI involved, the risk assessment, mitigation efforts, and the reasons for your notification decision. Include unresolved questions and any follow-up steps. HIPAA requires documentation of security incidents and their outcomes; HHS also explains that organizations must be able to demonstrate that required notices were provided or that notification was not required.
Mitigation may include disabling access, securing affected accounts and devices, requesting the return or secure deletion of PHI, and taking practical steps to prevent further access or disclosure. Record what you did and the evidence that supports any conclusion that risk was reduced.
If the event is a breach of unsecured PHI, covered entities generally must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery. Breaches affecting 500 or more individuals also require notice to HHS without unreasonable delay and within that 60-day period; breaches affecting fewer than 500 individuals must be reported to HHS within 60 days after the end of the calendar year in which they were discovered. A breach affecting more than 500 residents of a state or jurisdiction also requires notice to prominent media serving that area. Business associates must notify the covered entity under the applicable rule and business associate agreement. See HHS’s breach notification requirements. State law or contracts may require additional or faster action.
What steps protect PHI on personal devices after departure?
Determine whether the employee used a personal phone, computer, removable drive, or personal account to access or store PHI. Follow your BYOD policy and applicable law to request the return or secure deletion of organizational PHI, and document the request and response. If the device is enrolled in mobile-device management, consider a selective removal of organizational data when available and appropriate. Avoid an indiscriminate remote wipe that could destroy personal information or evidence; coordinate with privacy, security, and legal personnel.
When a device is returned or otherwise made available to the organization, have qualified personnel verify that organizational PHI has been removed or securely retained as required. HIPAA requires policies and procedures addressing the final disposition of ePHI and removal of ePHI from electronic media before reuse. Appropriate device media sanitization methods depend on the media and circumstances. Do not assume that deleting a visible file or account removes every copy, including synchronized files or backups.
For future departures, use a documented offboarding process that coordinates workforce access termination, return of organization-owned equipment, review of unusual PHI transfers, and clear instructions for removing work data from personal devices. Prompt containment, careful evidence review, a documented risk assessment, and timely notification when required are the core steps for responding responsibly.
FAQs
What should an organization do first when a departing employee downloads PHI?
Open a security incident response, notify the appropriate privacy and security leads, preserve relevant logs and evidence, and promptly contain further access. Establish what information was involved, whether the download was authorized, and whether PHI was transferred or retained before deciding whether breach notification is required.
How quickly should access be revoked?
Revoke or restrict access promptly in accordance with your offboarding and incident-response procedures. The HIPAA Security Rule requires procedures for terminating ePHI access when a workforce member’s employment or arrangement ends, but it does not specify a universal number of minutes or hours. Preserve relevant evidence while containing access.
Does every employee PHI download require breach notification?
No. A download that was authorized and within the employee’s work duties is not automatically a breach. An impermissible use or disclosure is presumed to be a breach unless an exception applies or a documented risk assessment demonstrates a low probability that PHI was compromised. Notification rules generally concern breaches of unsecured PHI.
How should an organization handle PHI stored on a former employee’s personal device?
Follow the organization’s BYOD policy and applicable law. Request return or secure deletion of organizational PHI, preserve relevant evidence, and use selective work-data removal where appropriate and available. Avoid wiping an entire personal device without authorization and a careful assessment of evidence and personal data impacts.
Table of Contents
- What should trigger a PHI incident response?
- How should you secure accounts and revoke access?
- Which logs and devices should you preserve and review?
- How can you determine whether PHI was accessed or retained?
- When does a PHI incident qualify as a reportable breach?
- How should you document mitigation and notify affected parties?
- What steps protect PHI on personal devices after departure?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today