Workforce access: closing a login the day someone leaves
What gets closed, who runs the checklist, and how the office proves the login stayed closed.

When a workforce member leaves, the practice has to end that person’s access to electronic protected health information. The same day is the workable rule. Close the logins, collect the devices, and write down what was closed. A farewell email is not a termination procedure.
The medical assistant’s last day was Friday. On Monday the EHR still accepts that password. The laptop is in a backpack that already went home. Nobody has a list of the other systems the password opened.
The standard is workforce security in 45 CFR 164.308(a)(3). The practice implements policies so workforce members have the access they are supposed to have, and so people who should not have access do not get it. Termination procedures are the addressable specification for ending access when employment or another arrangement ends. Addressable means you do it when it is reasonable, or you document why not and what you do instead. For a departure, ending access is reasonable. HHS describes the Security Rule on its security rule overview, and the companion guide is NIST SP 800-66r2. None of them says “sometime next week.”
Build the checklist in the managed IT work the office already uses to create logins. The person who can create an account is the person who can close one, or they have a named backup. If the only person who knows how to disable a user is the person who just left, the procedure was never real.
What gets closed
Close every door the person could open, not only the EHR icon on the desktop. The EHR, the portal admin role, the billing system, email, the VPN, the file share, the copier scan-to-email address, and any remote tool a vendor installed. A list that says “EHR: done” and ignores the mailbox will leave the schedule in a phone. Write the systems this office actually has, on one card, and check every line.
Disable the account. Do not only change the password and leave the name active, unless you have a written reason to keep it for a mailbox forward and a date when the forward ends. A password change that three people know is a shared login with a new secret. Disabling is cleaner. If a forward is required for patient calls, forward to a role mailbox, not to a coworker’s personal folder, and end the forward on a date written on the card.
Collect tokens and devices the same day. Keys, badges, phones, laptops, and any USB drive that was issued. The device step is the one described in device and media disposal. A disabled login does not wipe a laptop in a car. Name who collects the hardware so it is not left as “someone at the desk.”
Check for accounts the practice does not think of as IT. A lab portal, a clearinghouse, a vaccine registry, a bank login used for refunds. If the person was the only name on that site, move the ownership before they leave, not after the next invoice fails. The card should have a blank line for “other sites” so the manager fills it from memory while the person is still in the building to be asked.
Who does it, and when
Same day as the last shift, or earlier if the departure is not friendly. Waiting for payroll to “process the term” is how a weekend of access happens. Payroll can run on its own clock. The login clock is the last hour of the last shift. Put both clocks on the card so they are not treated as one task.
Name two people who can run the card. One is enough when the office is calm. Two is what you need when the person leaving is the one who usually runs it. The backup should have done the steps once, on a test account, before they are the only one in the building. A procedure that lives in one person’s head leaves with them.
Supervision and clearance are the other addressable pieces of the same standard. They are about who is allowed in, not only who is let out. Decide what check you do before a login is created, write it in a sentence, and do not invent a background-check product the office does not use. If the check is “the hiring manager confirms the person and the role,” say that. Then the role they receive should match minimum necessary, not a copy of the last person’s full access.
A person who changes jobs inside the office is a partial termination. Close the access the old job had and open what the new job needs. Leaving both in place because it is “easier for coverage” is how a biller still has a clinician template six months later. Treat the internal move as a departure from the old role on the same card, with a line for what was removed.
The page you keep
One page per departure. Name, last day, each system marked closed or not applicable, devices returned, who did the work, and the date it was done. Attach nothing that contains a password. The page proves the procedure ran. It does not need to be a form from a vendor. A shared checklist with the boxes ticked is enough, if it is filed where the next person can find last Friday’s.
Then look at the audit log the next business day. The question is whether that login succeeded after the time you claim it was closed. One successful login after the disable time means the disable missed a door. Fix that door and add it to the card. A page that says “closed” and a log that says “opened at 9 p.m.” cannot both be the story you tell.
Keep the pages with the security record for as long as you keep the other workforce records. The rule does not set a separate retention period for this checklist. Pick the same period you already use for the training attendance list, and write it on the folder. A checklist thrown out at the end of the month cannot answer a question in the spring about who still had access in January.
If a login cannot be closed because a vendor owns it, open a ticket the same day and write the ticket number on the page. Check the ticket until the vendor confirms the disable. “We emailed them” is not a closed line. The page stays open until the confirmation is in the folder.
Before the next departure
Run the card on a test user once, before you need it for a real person. Create the test login, disable it, and confirm it cannot sign in. Time the steps. If the disable takes a vendor ticket and two days, you do not have a same-day procedure, and you should change the contract or the admin rights before the next resignation. The drill is the proof. A policy sentence is not.
Tell managers the card exists and that they do not get to skip it for a “good leaver.” Friendly departures are how shared passwords survive, because nobody wants to feel rude. The card is not an accusation. It is the same list for everyone. The security awareness huddle can say that once, so the last day is not a surprise.
Qventive’s assessments at 200 Passaic Street in Hackensack start with the last person who left. Which logins were closed, which devices came back, and whether the audit log shows a sign-in after that hour. If the answers are a search, the termination spec is not operating. The same question belongs with the safeguards the practice already claims.
When you add a new system, add a line to the card the same week. A clearinghouse portal created in March and missing from the departure list will still accept the old user in December. The card is part of go-live, next to who receives the admin login. Review it each quarter against the systems you pay for. A line for a product you cancelled is noise. A missing line for a product you added is a door.
Students, locums, and weekend coverage get an end date on the day the login is created. Someone looks at that date when it arrives and runs the card. An arrangement that “ended last month” with the login still live is a termination you forgot, not a special case. Write the end date where the backup person can see it without asking the person who is already gone.
After a busy month of departures, read the pages as a set. If the same line is blank on every card, that system is not in the habit. Fix the line, not the people. If a card is missing entirely, the backup never ran it, and the next departure needs a named person who is not on vacation. The stack of pages is the training. A new manager should close a test account from the card before they close a real one.
Workforce access: common questions
When should access be closed after someone’s last day?
Is changing the password enough?
Which systems belong on the checklist?
What about a person who changes jobs but stays?
How do you know the disable worked?
Let’s meet
A free practice technology assessment walks the last departure and shows which logins were still open the next morning.