It's mid-morning, the waiting room is full, and the health record system won't load. Within a minute every person in the building is asking the same question, and nobody is sure whose job it is to answer. The outage itself is rarely the worst part. The confusion is.
A downtime plan removes the confusion. It doesn't need to be long. It needs to exist, on paper, where people can find it.
First, find out what is actually down
"The EHR is down" can mean three very different things, and the right response depends on which. One computer can't reach it: that's a local problem with that machine. Nobody in the office can reach it, and other websites won't load either: that's your internet or network. Nobody can reach it, but everything else works: that's most likely the vendor's service.
Two quick checks sort it out. Try another computer, and try a different website. If it's your network, your IT provider can act straight away. If it's the vendor, no amount of restarting will help, and the practice should move to its downtime routine while it waits.
What the plan needs to say
Who makes the call. One named person, with a backup, decides the practice is in downtime and tells everyone. Without that, each room waits for someone else to decide.
How you see the schedule. If nobody can see who is booked, the front desk is stuck. Decide in advance how tomorrow's schedule is kept somewhere that survives an outage, whether printed at the end of each day or saved where it can be opened offline.
How care is recorded. Keep a small supply of paper forms for intake and visit notes, and say where they're stored. Your clinical lead should decide ahead of time how orders and prescriptions are handled during an outage, so nobody is working it out with a patient in the room.
Who to call. Put the support numbers for your record vendor, your IT provider, and your internet provider on a printed sheet. A contact list saved inside a system you can't open is no use.
Coming back up
Recovery is where information gets lost. When the system returns, the paper notes need to be entered or scanned, and someone has to confirm that every patient seen during the outage is accounted for. Give that job to a named person.
Write down what happened as well: when it started, how long it lasted, what caused it, and what you'd do differently. That short record is useful to you, and it's the kind of evidence a reviewer likes to see.
Making outages rarer and shorter
You can't prevent a vendor outage, but a lot of downtime is local, and local downtime can be reduced. A second internet connection that takes over automatically means a single line going down no longer stops the clinic. Monitoring catches a failing network device before it fails. Updates scheduled outside clinic hours stop a restart landing in the middle of the morning.
And if the cause is serious, tested backups are what decide whether the outage lasts an hour or a week.
It's also a HIPAA expectation
The Security Rule asks practices to plan for emergencies. That includes a data backup plan, a disaster recovery plan, and a plan for how the practice keeps operating while systems are unavailable. A downtime plan is that third piece. (source: 45 CFR 164.308) Having one written and practiced is good for patients first, and it's also something you can be asked to show.
Practice it once
A plan nobody has tried is a guess. Once a year, take twenty minutes at a staff meeting and walk through it: the system just went down, what do we each do? You'll find the gaps quickly. The forms are out of date, or the phone list has an old number. Better to find that on a calm afternoon.
The takeaway
Decide who calls it, how you'll see the schedule, how you'll record care, and who you'll phone. Put it in a folder. Practice it once. A clinic that has done those things treats an outage as an inconvenience, and its patients barely notice.