Why Downtime Plans Fail
The plan is rarely wrong. It is usually a PDF on the system that is down, listing a phone number nobody answers anymore.
CareScope Editorial/August 22, 2026/3 min read
The short version
- Most downtime plans have never been read aloud by the people who would use them.
- The three most common failures: the plan is stored on the unavailable system, contacts are stale, and nobody knows who declares downtime.
- A one-hour tabletop exercise finds more than a written risk assessment.
Why it matters
When a practice loses its EHR, clearinghouse, or internet connection for a day, the damage is mostly operational: patients waiting, notes on paper that will need entering, claims that do not go out. The difference between a rough morning and a lost week is whether the staff who answer the phones have rehearsed the first thirty minutes.
The three failures that repeat
The plan lives where you cannot reach it. Stored in the EHR, on a shared drive that depends on the same network, or in an email account that requires the system that is down. Print it. Put copies at the front desk and in the clinical area.
The contacts are stale. Vendor support numbers change, account managers leave, and the escalation path in the document is two reorganizations old. Verify contacts twice a year; it takes twenty minutes.
Nobody knows who decides. Staff wait forty minutes for someone to say "we are going to paper" because no one is sure they are allowed to. Name the role, not the person, and name a backup.
Run the exercise
Gather the front desk, a clinician, and a biller for one hour. Scenario: the EHR is unavailable at 8:15am on a full schedule. Walk through the first thirty minutes out loud. Who tells patients what? Where are the paper forms? How do you know which appointments exist today? Who calls the vendor, and what account number do they need?
You will find three or four gaps. Fix them the same week and the exercise pays for itself the first time something breaks.
A continuity plan nobody has read out loud is a document, not a plan.
The CareScope take
Print the plan, verify the contacts, name who declares downtime, and run one tabletop this quarter. That is the whole assignment, and it costs an hour of four people''s time.
Skip the elaborate binder. Practices that recover well have a short, current, rehearsed plan — not a thorough one.
Sources
- HIPAA Security Rule, including contingency planning requirements (45 CFR 164.308(a)(7)) — HHS Office for Civil Rights
- #StopRansomware Guide — CISA
- Health Industry Cybersecurity Practices (HICP) — HHS 405(d) Program
CareScope cites primary sources — regulators, standards bodies, and published research — wherever a claim depends on them. Reporting is editorially independent and is not legal advice.
continuity · operations · resilience