How Ransomware Hits a Nursing Home: The First Hour, the First Week, and the Year After

It’s 6:40 a.m. The night nurse on the second floor can’t sign in to the med cart laptop. The unit clerk’s desktop shows a note she’s never seen, and every shared folder file ends in the same strange extension. Someone calls the EHR vendor. Their status page is green. The chart is fine.

Nobody in the building can get to it.

That’s the part most articles on how ransomware affects a business miss. They talk about ransom demands and stolen data. In a skilled nursing facility, the first damage is access. The 8 a.m. med pass, a hospital discharge waiting for a bed, and Friday’s payroll all depend on the same few logins, laptops and network switches. Ransomware goes after exactly those.

The short answer: ransomware affects a nursing home in three waves. In the first hours, staff lose the workstations, logins, printers and sometimes phones they need to reach the EHR and eMAR, so care moves to paper. In the first weeks, billing, admissions, payroll and vendor connections stall while systems are rebuilt. For a year or more after, the facility carries the regulatory and legal tail: a presumed HIPAA breach unless a documented risk assessment shows otherwise, notification deadlines, and survey questions about its emergency plan. How long each wave lasts depends less on the attacker than on a few things you can check this month.

Your chart is probably fine. Your way to it isn’t.

Most SNFs now run a cloud EHR. That changes what ransomware takes from you. An attacker inside your building’s network usually can’t encrypt your vendor’s servers. What they can encrypt or lock is everything local that stands between a nurse and the chart:

  • Domain logins. If the attacker owns your Active Directory, every workstation sign-in, every Wi-Fi connection tied to those accounts and every shared drive goes with it.
  • Workstations and med cart laptops. Encrypted or pulled off the network by your own team to stop the spread. Either way they’re unusable.
  • Printing and fax. Face sheets, MARs, transfer packets and pharmacy orders often run through a local print server or a fax setup on the same network.
  • Phones. If your phone system is an on-site server or depends on the same network, families, hospitals and the pharmacy may not reach you either.
  • Shared folders. Scanned admission packets, staffing schedules, policy binders and the emergency plan itself often live on a file server. If the only copy of your downtime procedures sits on that server, you will be reading them off a phone or not at all.

This is why a nursing home can be “down” while its EHR vendor reports no outage. Plan for that case. It is the likely one.

When the vendor is the one hit

The second case is worse. In November 2019, ransomware hit Virtual Care Provider Inc., a Milwaukee company that hosted IT for post-acute providers. Healthcare IT News reported that its clients included 110 nursing home organizations across 45 states, that the attackers demanded $14 million, and that web service, email, phones, billing and EHRs were affected depending on what each facility bought. The company said it was restoring Active Directory, email, eMAR and EHR servers first.

Read that restore order again. Even the vendor had to bring back logins before it could bring back charts. And none of those 110 organizations had done anything wrong inside their own walls.

The lesson isn’t to avoid hosted IT. It’s to know, for each vendor that holds resident data or runs a care workflow, what you would do for a week without them. That means a written answer for the EHR, eMAR, pharmacy, lab, billing, payroll and timekeeping, not a general promise to “go to paper.”

The first week: care continues, the business stalls

Nursing staff know paper. Downtime MARs and paper charting are uncomfortable, slow and error-prone, but most teams can run them for a shift or two. When ransomware hit Memorial Hospital and Manor, a Georgia hospital with an attached nursing home, in November 2024, the facility told the public it had lost access to its EHR and moved to a paper-based process (Security Affairs).

The business side breaks faster than the clinical side, and it’s harder to run on paper:

  • Admissions. Referrals from hospitals keep coming. Without access to referral portals, insurance verification and your own census, you either slow down admissions or accept residents with less information than you’d want.
  • Billing and cash. Claims, MDS transmissions and remittances depend on systems and vendor connections you may have just cut off on purpose. Revenue doesn’t stop being earned. It stops arriving.
  • Payroll and timekeeping. Time clocks, agency hours and differentials have to be reconstructed by hand if the system that holds them is down on payday. Missing a payroll is how an IT incident becomes a staffing incident.
  • Vendor connections. Every VPN, remote-support tool and integration gets switched off during containment. Turning each back on safely is slow, and it should be.

The year after: the regulatory tail

Three obligations follow a ransomware incident long after the systems are back.

HIPAA. HHS’s Office for Civil Rights treats encryption of electronic PHI by ransomware as a presumed breach. That holds unless the facility can document, through a four-factor risk assessment, a low probability that the data was compromised. A breach starts notification clocks for residents, HHS and, for larger breaches, the media.

CMS emergency preparedness. Under 42 CFR 483.73, your emergency plan has to rest on an all-hazards risk assessment. It must also include policies for medical documentation that keep resident information available and confidential. After a real incident, expect a surveyor to ask whether your plan anticipated a cyberattack and whether staff followed it.

The HIPAA Security Rule’s contingency plan. Data backup, disaster recovery and emergency-mode operation plans are required, not optional, under 45 CFR 164.308(a)(7). An incident tests whether yours existed on paper or in practice.

What separates a bad day from a bad month

We’ve worked ransomware incidents from the inside. The attacker’s skill matters less than what they find when they get in. These are the failure points we see make recovery long, and what to check before you need to:

Failure point What it looks like on the day What to check this month
Forgotten admin accounts An old installer or vendor account, created years ago and never disabled, still has domain admin rights and gets used to reach your servers Pull a list of every domain admin and every account that hasn’t signed in for 90 days. Disable what nobody can explain.
Leftover remote-access tools Old copies of TeamViewer, LogMeIn or VNC on a few machines, installed by a former vendor or for one-time support Inventory remote-access software on every device. Keep the one your IT provider manages and remove the rest.
Flat network Ransomware spreads from one infected PC across shared drives while your team isolates machines one at a time Separate clinical devices, business workstations, guest and resident Wi-Fi, and building systems such as nurse call and door access into their own network segments.
Backups nobody has restored The backup exists, but the last good job ran two days ago, or it sits on the same network and is encrypted too Confirm at least one copy is offline or immutable. Do a real test restore of a server, not just a file, and write down how long it took.
Downtime kit on the file server Paper MARs, contact lists and the emergency plan are only on the encrypted drive Keep a printed, dated downtime binder at every nursing station and a copy outside your network.
No one knows who decides Twenty minutes of debate over whether to unplug the network Name who can order isolation, who calls the cyber insurer, who calls counsel, and who talks to families. Put it on one page.

The incidents that recover cleanly look similar. A replica or backup of the main server was intact, so the team could boot it with no network access, check it, lock it down and reconnect it. Every admin password was changed. Unexplained accounts and remote tools were removed before anything came back online. That’s hours of disciplined work, and it only works if the clean copy exists before the attack.

A tabletop exercise is the cheapest way to find these gaps. Run your next CMS emergency preparedness exercise as a ransomware scenario that starts at 6:40 a.m. with a locked med cart laptop. You’ll learn more from the first thirty minutes than from any policy review.

Quick answers

Can ransomware take down PointClickCare or another cloud EHR? It rarely encrypts the vendor’s own systems from your network. It can still cut every nurse off from the chart by locking your logins, workstations, Wi-Fi and printers. If the vendor itself is attacked, as happened to a nursing home hosting provider in 2019, the chart can be unavailable for every facility it serves.

What is the biggest business impact of ransomware on a nursing home? Usually it’s lost access, not the ransom. Admissions slow, claims and payroll stall, and staff spend days on paper workarounds while systems are rebuilt. Then come the breach analysis, notifications, legal costs and survey questions.

Should a nursing home pay the ransom? The FBI advises against paying, and payment doesn’t guarantee your data comes back or stays private. Paying certain groups can also create sanctions problems. Make that decision with your cyber insurer and legal counsel, never alone at 7 a.m. A tested offline backup is what keeps it from being your only option.

Is a ransomware attack automatically a HIPAA breach? HHS presumes it is when electronic PHI was encrypted. The facility can rebut that only with a documented four-factor risk assessment showing a low probability of compromise.

How long does recovery take? It depends on your backups and how much of the network the attacker reached. A facility with a clean, tested backup and a segmented network can restore core systems in days. One rebuilding from scratch can take weeks.

Find your failure points before an attacker does

Every item in the table above can be checked without an incident. RDE’s HIPAA security risk assessment for nursing homes looks at exactly these: admin accounts, remote access, network segments, backups and downtime readiness. You get a written list of what to fix first. If you’d rather start with a conversation about your building, talk to RDE or read how we support skilled nursing IT.

Share this article

Share on Facebook
Share on Twitter
Share on Linkdin
Share on Pinterest

Leave a comment

Find out what your IT really needs.

A free assessment of your network, backups and security, with a written report of what we found. No obligation.