HIPAA and Compliance

Ransomware Downtime Procedures for the Front Desk

How the front desk keeps a practice running when the EHR is down: paper kits, contact lists, scheduling, patient scripts and the recovery steps afterward.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Plan for the day the screens go dark
  2. What goes in a front desk downtime kit
  3. The first hour
  4. Running the schedule on paper
  5. Scripts for patients
  6. When systems come back
  7. Ransomware is also a privacy question
  8. Test the plan twice a year
  9. Frequently asked questions
  10. References
HIPAA and Compliance: Ransomware Downtime Procedures for the Front DeskArticle coverHIPAA AND COMPLIANCERansomware DowntimeProcedures for theFront DeskAva Medical IntakeInsightsHIPAA and Compliance: Ransomware Downtime Procedures for the Front DeskArticle coverHIPAA AND COMPLIANCERansomware DowntimeProcedures for theFront DeskAva Medical Intake

Key takeaways

  • The Security Rule requires a contingency plan, including a data backup plan, a disaster recovery plan and an emergency mode operation plan.
  • Ransomware complaints to the FBI rose each year from 2022 to 2024, and the FBI again named ransomware the most pervasive threat to critical infrastructure.
  • A front desk downtime kit, printed in advance, decides whether an outage means a slow day or a closed office.
  • After systems return, every paper record must be reconciled, and the incident assessed as a possible breach.

Plan for the day the screens go dark

Most practices have a plan for a power cut. Fewer have one for the morning when every workstation shows a ransom note, the EHR is unreachable and the phone system's call routing has stopped working. Yet ransomware remains one of the most common attacks reported to the FBI. In its 2024 report, the Internet Crime Complaint Center said ransomware was again the most pervasive threat to critical infrastructure, and total ransomware complaints rose from 2,825 in 2023 to 3,156 in 2024[1].

Ransomware complaints reported to the FBI's Internet Crime Complaint CenterComplaints filed with IC3, all victim types
Ransomware complaints reported to the FBI's Internet Crime Complaint CenterLine chart. 2022: 2,385 complaints; 2023: 2,825 complaints; 2024: 3,156 complaints.2,250 complaints2,500 complaints2,750 complaints3,000 complaints3,250 complaints2022202320242022: 2,385 complaints2023: 2,825 complaints2024: 3,156 complaints3,156 complaints2,385 complaintsRansomware complaints reported to the FBI's Internet Crime Complaint CenterLine chart. 2022: 2,385 complaints; 2023: 2,825 complaints; 2024: 3,156 complaints.2,250 complaints2,500 complaints2,750 complaints3,000 complaints3,250 complaints202220242022: 2,385 complaints2023: 2,825 complaints2024: 3,156 complaints3,156 complaints2,385 complaints

Source: Federal Bureau of Investigation, Internet Crime Complaint Center (IC3), 2024[1]

Show the data
PeriodValue
20222,385 complaints
20232,825 complaints
20243,156 complaints

The HIPAA Security Rule already expects you to plan for this. A contingency plan is a required standard, and three of its parts are required specifications: a data backup plan that keeps retrievable exact copies of electronic patient information, a disaster recovery plan to restore lost data, and an emergency mode operation plan that keeps critical business processes running while you are in crisis[2]. The emergency mode plan is the front desk's part of the job.

What goes in a front desk downtime kit

Keep a physical kit in a labeled box or binder at each front desk, with a second copy off site or with the practice manager. If it only exists on the network drive, it will not exist on the day you need it.

  • Tomorrow's schedule, printed or exported every evening to an encrypted device that is not connected to the network, with patient names, times, providers and phone numbers.
  • Blank paper registration, check-in, consent and encounter forms, enough for at least two days of patients.
  • A paper appointment book or grid for each provider, with visit types and lengths.
  • A paper log for incoming calls, messages and refill requests, with columns for time, caller, callback number, reason and who took it.
  • A contact sheet: IT support, EHR vendor, phone vendor, internet provider, cyber insurance hotline, practice owner, privacy officer, nearby pharmacies, labs and the hospital.
  • Receipt book and a manual way to take payments, or a decision to defer collections until systems return.
  • Printed patient scripts for the phone and the counter, and a sign for the front door.
  • Pens, clipboards, a stapler and secure folders or a lockable box for completed paper forms.

Do not plug anything from the kit into an infected network. A USB drive with tomorrow's schedule should only be opened on a standalone device the IT team has confirmed is clean.

The first hour

  1. Disconnect, do not delete

    Unplug affected computers from the network or turn off Wi-Fi as your IT partner directs. Do not wipe machines or pay anything; evidence matters.

  2. Call the incident contacts

    IT support first, then the practice owner, privacy officer and cyber insurer if you have one. Use phones that do not depend on the affected network.

  3. Declare downtime

    One person, usually the practice manager, announces that the office is on downtime procedures and hands out the kit.

  4. Triage today's schedule

    Using the printed schedule, decide which visits go ahead on paper, which need to be moved and which are urgent and must not be missed.

  5. Set up the phones

    If the main line still works, switch to paper call logs. If it does not, forward the number to a mobile phone or the backup line in your plan.

  6. Start an incident log

    Record times, actions and decisions as they happen. The security incident procedures in the rule expect incidents and their outcomes to be documented[2].

Running the schedule on paper

Downtime is not the moment to keep every appointment. Clinicians will be slower without the chart, so most practices cut the schedule to a level they can safely manage. Prioritize patients with acute needs, procedures that cannot be postponed and patients who have already traveled to you. Move routine follow-ups and annual visits first.

  • Write every new appointment in the paper book in pen, with the patient's full name, date of birth and callback number.
  • Mark each paper encounter form with the date, time and staff initials so it can be entered later.
  • Keep completed forms in a single secure folder per day, never loose on the counter.
  • Do not rebook patients in a personal phone or a spreadsheet on an unmanaged laptop.

The phone matters more than usual during an outage. MGMA notes that the phone often remains the real front door for a large share of patients, despite portals and automated reminders[3]. If the portal and reminder texts are down, patients will call, and they will call more than once.

Scripts for patients

Phone script: Thank you for calling. Our computer systems are temporarily unavailable, so we are working on paper today. We can still help with urgent needs. May I take your name, date of birth and a callback number, and the reason you are calling? If this is an emergency, please hang up and call 911.

Rescheduling script: Because our systems are down, we are moving some routine visits to protect patient safety. I am very sorry for the inconvenience. Can I offer you a new time now and confirm it by phone once our systems are back?

Keep the explanation short and factual. Do not speculate about hackers, stolen data or when systems will return. Patients can be reached directly while the portal is down, since about nine in ten adults own a smartphone[4], but only send texts from systems the IT team confirms are unaffected and covered by an agreement.

When systems come back

  1. Wait for the all-clear

    Only reconnect workstations and log in when IT confirms the environment is clean. Reset passwords as directed.

  2. Reconcile every paper record

    Enter each paper registration, encounter, message and appointment into the EHR, marking entries as late entries with the original date and time. Check off each form as entered.

  3. Return the calls

    Work through the paper call log, starting with clinical and refill requests.

  4. Secure or shred the paper

    Scan forms that must be kept, file them according to your record policy, and shred the rest through your shredding vendor.

  5. Debrief

    Within a week, hold a short review: what worked, what was missing from the kit, and what to change in the plan.

Ransomware is also a privacy question

An attack that encrypts or copies patient information is an impermissible acquisition or use of that information. Under the Breach Notification Rule it is presumed to be a breach unless a documented risk assessment shows a low probability that the information was compromised[5]. Your IT partner's forensic findings, such as whether data was taken off the network, feed directly into that assessment.

If it is a breach, patients must be notified without unreasonable delay and no later than 60 calendar days after discovery[6]. The downtime plan should therefore name the privacy officer as part of the incident team from the first hour, not as an afterthought once systems are running again.

Test the plan twice a year

Testing and revising the contingency plan is an addressable part of the Security Rule[2], which means you must assess it and either do it or document a reasonable alternative. A tabletop drill is the cheapest version. Pick a quiet afternoon, announce that the EHR and phones are down, and have the front desk run the next hour from the kit. Time how long it takes to find the schedule, set up call logging and check in a mock patient.

Example (fictional): A four-provider family practice runs its first drill and discovers the printed schedule was last updated three weeks ago, the IT support number on the contact sheet is out of date, and nobody knows how to forward the main phone line. Each gap takes minutes to fix in a drill. Discovered during a real attack, each would have cost hours.

Frequently asked questions

Should we pay the ransom?

That decision belongs to the practice owner with legal counsel, the cyber insurer and law enforcement, not the front desk. Staff should disconnect devices, call the incident contacts and switch to downtime procedures.

How much paper should we keep in the downtime kit?

Enough for at least two full clinic days of registrations, encounters and call logs. Restock after every drill or real outage.

Is a ransomware attack always a reportable breach?

It is presumed to be one unless a documented risk assessment shows a low probability that patient information was compromised. Involve your privacy officer from the start.

Can we use personal phones during downtime?

Only for calls if the plan allows it. Do not store patient lists, photos of forms or texts with patient details on personal devices.

References

  1. Federal Bureau of Investigation, Internet Crime Complaint Center (IC3) (2024). Internet Crime Report 2024 (opens in a new tab) ↑

  2. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.308 - Administrative safeguards (opens in a new tab) ↑

  3. Medical Group Management Association (MGMA) (2026). Phones are still a bottleneck costing medical practices time they can't afford (opens in a new tab) ↑

  4. Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) ↑

  5. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.402 - Definitions (breach) (opens in a new tab) ↑

  6. Legal Information Institute, Cornell Law School (current). 45 CFR § 164.404 - Notification to individuals (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo