Behavioral health organizations plan meticulously for clinical crises. There are protocols for a client in acute distress, for a safety concern, for a difficult termination. Ask the same organization what happens if the EHR is unreachable at 8 a.m. on a Tuesday, and the answer is usually a long pause followed by "we'd call IT."
That gap matters because the day doesn't stop. Clients are already in the parking lot. Clinicians need schedules, histories, and treatment plans. Intake needs to verify insurance. Billing needs to close yesterday. When the system that holds all of it is unavailable, the question isn't whether you'll improvise — it's whether you'll improvise well, and whether the improvising creates a compliance problem on top of an operational one.
The improvisation is where the risk hides
Watch what naturally happens during an unplanned outage. Someone photographs a schedule with a personal phone. Notes get drafted in a personal email account "just until it's back." A clinician texts a colleague a client's name to confirm an appointment. None of it is malicious — all of it is PHI moving to places your safeguards don't reach, created under time pressure, and rarely cleaned up afterward.
The one-page downtime plan
This doesn't need to be a binder. One page, printed — because if it only exists in the system that's down, it doesn't exist:
- Who to call, in order, with real phone numbers — your IT provider, your EHR vendor's support line, and the internal person who decides whether to cancel or continue
- How the day proceeds — a paper intake and session-note form approved in advance, so documentation stays consistent and defensible
- What staff must not do — no personal email, no personal phone photos, no texting client identifiers, no personal cloud storage. Say it explicitly; the pressure of the moment overrides good instincts
- Who tells clients what, and the script for it, so front desk isn't inventing language while people wait
- How the paper gets back in — who enters it, by when, and who confirms it's complete and then destroys the paper securely
- Access to the schedule — a known, secure way to see today's appointments when the EHR is down, decided in advance rather than at 8:05
Then test the assumption underneath it
Most downtime plans quietly assume the data comes back. That assumption is only true if your backups are separated from your network and have actually been restored — not just reported as successful. A restore test once a quarter is what converts "we have backups" into "we can be operational by this afternoon." It's also, not coincidentally, what your cyber-insurance carrier and your risk assessment both want documented.
Write the one-pager this week, print it, and put a copy at the front desk and in every clinician's office. Then ask your IT provider one question: when was our backup last test-restored, and how long would a full recovery take? Our free security assessment answers both — findings are yours either way.
You can't prevent every outage. You can decide, calmly and in advance, what a bad morning looks like — so the day bends instead of breaking, and nothing about the improvising comes back as a compliance finding later.
Andrew — Founder, NextGen Strategy Partners
Veteran-owned managed IT for the nonprofits, schools, behavioral health providers, and medical & dental practices of McHenry & Lake Counties. Request a free security assessment →