HIPAA Termination Access Revocation Policy Template

Kevin Henry

HIPAA

Published Updated

10 minutes read
Share this article
HIPAA Termination Access Revocation Policy Template

Use this template to document how your organization removes or changes workforce access to electronic protected health information (ePHI) when a worker leaves or no longer needs the same access. Replace bracketed fields with your organization’s procedures, roles, systems, and timelines.

When HIPAA access must be terminated or changed

Policy statement: [Organization] will terminate a workforce member’s access to ePHI when their employment or other work arrangement ends. The organization will also review and change access when a workforce clearance determination, job change, or other change means the person should no longer have the same access.

The HIPAA Security Rule calls for termination procedures when a workforce member’s employment or other arrangement ends, and when access must change based on a workforce clearance determination. It does not specify a universal number of minutes or hours for completing revocation. Set an internal deadline that reflects your risk, operations, and separation processes, and apply it consistently. See 45 CFR § 164.308(a)(3)(ii)(C).

  • For a planned departure, schedule access removal to take effect no later than the worker’s final authorized work time.
  • For an involuntary separation or urgent security concern, coordinate removal with the separation so access is disabled at the approved effective time.
  • For a transfer or role change, remove or reduce permissions that are no longer appropriate; grant new access only through the organization’s authorization process.
  • Apply the procedure to employees and other workforce members, including contractors, temporary workers, trainees, and volunteers where applicable.

The HHS HIPAA Audit Protocol identifies voluntary and involuntary departures, contractor arrangements, account deactivation, access-device recovery, and access changes after job-description changes as matters an organization’s procedures may address.

Who initiates and carries out access revocation

Policy statement: [Organization] assigns responsibility for reporting departures and access changes, approving the effective time, carrying out removals, and confirming completion. Each task must have a named role or designated alternate.

  • Supervisor or department leader: Notifies Human Resources and the designated access-removal team as soon as a departure, transfer, leave, or access change is known. Confirms the worker’s last authorized work time and identifies organization-issued property and any organization information under the worker’s control.
  • Human Resources or workforce administration: Confirms the separation or role-change details, records the effective time, and sends the required notification through the approved process.
  • IT or identity and access management (IAM): Disables or modifies accounts, authentication methods, permissions, and remote access, and records completion in the organization’s ticketing or access-management system.
  • Facilities or physical security: Deactivates badges and collects keys, tokens, and other physical access devices.
  • System owners and managers: Identify application-specific, privileged, vendor-hosted, or locally managed access that central IAM may not control, and verify the required action is complete.
  • Security or privacy official: Oversees the procedure, reviews exceptions, and coordinates investigation if access remains active or suspicious activity is identified.

When a system is managed by a vendor or business associate, [Organization] will assign an owner to submit and track the deprovisioning request, obtain confirmation, and escalate delays under applicable agreements and internal procedures.

How to disable accounts and revoke credentials

Policy statement: The assigned access-removal team will use the workforce member’s identity and a current inventory of their access to disable accounts and revoke credentials by the approved effective time. The team will document systems checked, actions taken, exceptions, and completion evidence.

  1. Confirm the person’s identity, status, effective date and time, manager, and applicable access inventory.
  2. Disable the person’s central identity-provider and directory accounts, and invalidate active sessions where the system supports it.
  3. Remove or disable access to the electronic health record, clinical and billing systems, email, collaboration tools, file stores, cloud services, databases, administrative consoles, and other systems that contain or provide access to ePHI.
  4. Disable remote access, including VPN, virtual desktop, remote support, mobile access, and other remote access account deprovisioning tasks.
  5. Revoke or reset authentication credentials, including passwords, multifactor authentication methods, smart-card certificates, hardware or software tokens, recovery methods, and organization-issued device credentials.
  6. Review privileged, local, shared, service, and application-specific accounts. Remove the individual’s authorization; where a shared credential or secret may be known to the departing worker, rotate it according to the organization’s security procedure.
  7. Review connected devices and sessions. Where appropriate, remove organization access or use approved device-management procedures for organization-managed equipment.
  8. Preserve required records, business data, and audit evidence under the organization’s retention and continuity procedures. Do not delete an account’s records merely to remove a person’s access.

For each action, record the responsible person or system, completion time, result, and any unresolved exception. The HIPAA Security Rule also addresses access controls and user access establishment and modification; see 45 CFR § 164.308(a)(4) and HHS’s Summary of the HIPAA Security Rule.

How to recover badges keys tokens and smart cards

Policy statement: The supervisor and designated physical-security or IT staff will recover or deactivate organization-issued access devices when a workforce member’s access ends or changes.

  • Request return of ID badges, keys, access cards, smart cards, hardware authentication tokens, organization-owned phones, and other issued access devices.
  • Deactivate badges and electronic access cards in the access-control system by the approved effective time, even if the physical item has not yet been returned.
  • Change or rekey locks, shared access codes, or other physical credentials when a device is missing or the organization’s risk assessment indicates a change is appropriate.
  • Revoke authentication tokens and certificates in the systems that issued or trust them; collect hardware tokens where feasible.
  • Record each item as returned, deactivated, missing, or subject to follow-up. Escalate missing items under the organization’s security-incident and lost-property procedures when appropriate.

HHS’s HIPAA Security Rule implementation guidance discusses recovering access-control devices, such as badges, keys, and access cards, and deactivating computer accounts when employment ends.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

How to coordinate workforce departures with access removal

Policy statement: Human Resources, the supervisor, IT/IAM, facilities, and system owners will coordinate departures through a documented workflow. The workflow will identify the effective time, required actions, responsible parties, and escalation contact.

  1. HR or the supervisor submits a departure or access-change request through [approved system or contact], including the person’s name, unique identifier, role, effective time, manager, and known access needs.
  2. The request is routed to IT/IAM, facilities, and relevant system owners using the organization’s access inventory and notification list.
  3. For involuntary or otherwise sensitive separations, the supervisor coordinates with HR and security to limit advance disclosure where appropriate and to align account, remote, and physical-access removal with the authorized effective time.
  4. Before removing access that may affect patient care or essential operations, the responsible manager arranges authorized coverage and continuity. That planning does not authorize the departing worker to retain access after the approved end time.
  5. Managers arrange the secure transfer of work files or records needed for continued operations through approved organizational accounts and processes, not by retaining the former worker’s credentials for routine use.
  6. Each team reports completion or a documented exception to the workflow owner. The owner tracks unresolved actions to closure and escalates delays under [organization’s escalation procedure].

For transfers and other role changes, use the same coordinated process to remove access that is no longer appropriate and to authorize any new access before it is granted.

How to verify former workers no longer have active access

Policy statement: The workflow owner or designated reviewer will verify that required access-removal actions are complete and will retain an auditable record of the review.

  • Compare the completed request against the person’s known access inventory, including central accounts, remote access, ePHI systems, local accounts, privileged access, and physical devices.
  • Review account status and deprovisioning evidence in the identity provider, directory, application consoles, VPN or remote-access systems, and physical-access system, as applicable.
  • Obtain confirmation from system owners or vendors for access they manage outside the central identity system.
  • Check for unresolved sessions, credentials, tokens, badges, keys, or access exceptions, and assign any follow-up to a named owner with a deadline.
  • Document the reviewer, date, systems checked, evidence reviewed, exceptions, and resolution. Use access logs or reports when appropriate to investigate possible post-separation activity.

If the review identifies successful or attempted unauthorized access, follow the organization’s security-incident response and reporting procedures. The HHS Security Rule guidance describes the Security Rule’s incident-response and information-system activity-review requirements.

HIPAA workforce security requirements and policy limitations

This template supports the HIPAA Security Rule workforce security requirement, including 45 CFR 164.308(a)(3)(ii)(C). The provision labels termination procedures “addressable.” Addressable does not mean an organization can simply ignore the specification: the organization must assess whether it is reasonable and appropriate in its environment and, when it is not, document that determination and implement an equivalent alternative measure as required by the Security Rule.

The workforce clearance procedure under 45 CFR 164.308(a)(3)(ii)(B) concerns determining whether workforce access is appropriate. Access changes made under that process can trigger the need to modify a user’s rights. These requirements support the broader HIPAA Security Rule workforce security and electronic protected health information access safeguards.

HIPAA does not prescribe this template’s job titles, specific technologies, or a universal hour-by-hour revocation schedule. Tailor it to your organization’s risk analysis, systems, workforce arrangements, state and other applicable laws, contracts, and operational needs. The Security Rule requires reasonable and appropriate safeguards, written policies and procedures, and documentation; required Security Rule documentation must generally be retained for six years from its creation or the date it was last in effect, whichever is later. See 45 CFR § 164.316.

In summary: Define who reports a departure, who removes each type of access, when removal takes effect, how devices and credentials are recovered or revoked, and how completion is verified and documented. Review and adapt this procedure to your organization rather than treating a template as a guarantee of compliance.

FAQs

When must HIPAA access be revoked after a workforce member leaves?

The HIPAA Security Rule requires procedures to terminate access when a workforce member’s employment or other arrangement ends, but it does not set a universal number of hours or minutes. Your policy should establish a clear effective time and operational deadline based on your risk and separation process. For a job or access change, review and modify access when the person’s authorized access should change.

Who is responsible for initiating access removal?

HIPAA does not assign this task to a particular job title. Your policy should name the role that reports the departure—often a supervisor or Human Resources—and assign IT/IAM, facilities, system owners, and a workflow owner responsibility for completing and verifying their respective actions.

Which accounts and credentials should a termination policy address?

Address central identity and directory accounts, systems containing or providing access to ePHI, email and cloud tools, remote access, privileged and local accounts, application-specific access, active sessions, multifactor authentication methods, certificates and tokens, and shared credentials that may need rotation. Also include physical badges, keys, access cards, and smart cards.

How can an organization verify that a former worker no longer has access?

Compare the completed removal record against an access inventory; review account, application, remote-access, and physical-access status; obtain confirmation for vendor-managed systems; and document the reviewer, evidence, completion times, and exceptions. Investigate any suspected post-separation access under your security-incident procedures.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles