It is 8:15 on a Monday morning. Patients are already arriving, the phones are ringing, and the first appointments of the day are underway.
Then someone at the front desk says the system is not working.
At first, everyone assumes it is one computer. A few minutes later, it becomes clear that the problem is larger. Employees cannot get into a critical application. Maybe the server is unavailable. Maybe the internet connection is down. Maybe the EHR cannot be reached.
Whatever the cause, the question quickly changes from "When will IT fix this?" to something much more practical:
What do we do with the patients who are already here?
That is a question every eye care practice should be able to answer.
Technology outages can happen for many reasons, including hardware failures, internet outages, software problems, power events, vendor issues, and cybersecurity incidents. Some may last only a few minutes. Others can take hours or longer to fully resolve.
A strong disaster recovery plan focuses on restoring technology. A strong business continuity plan also considers what happens to the practice while that recovery is taking place.
Start With the Systems Your Practice Depends On Most
One of the first steps in preparing for downtime is understanding which systems are truly critical to patient care.
For many practices, the EHR or practice management system is near the top of the list. But it may not be the only one.
The front desk may depend on scheduling and check-in software. Employees may use cloud-based phone systems. Doctors may rely on imaging or diagnostic applications. Billing information may be stored elsewhere. Staff may communicate through email or a messaging platform.
If multiple systems depend on the same internet connection or server, one problem can affect several areas at once.
That is why it is helpful to think in terms of workflows rather than individual devices.
Instead of asking, "What happens if this computer fails?" ask, "What technology does the practice need in order to check in a patient, complete an exam, access critical information, communicate internally, and check the patient out?"
That produces a much clearer picture of what downtime could actually mean.
Decide What the Practice Can Do Without Technology
A common mistake in emergency planning is focusing entirely on how quickly IT can restore the system.
That matters, but it does not answer the question staff will have during the outage.
What can we still do?
Depending on the type of outage and the systems affected, a practice may be able to continue some operations manually. There may be paper forms available for certain workflows. Staff may have downtime procedures for documenting information that can later be entered into the appropriate system.
Other activities may not be possible without access to specific information or technology.
The answer will vary from practice to practice, which is exactly why the decision should not be improvised during an emergency.
Practice leadership and the clinical team should determine in advance which activities can continue safely during different types of downtime and which situations may require appointments to be delayed or rescheduled.
Your Staff Needs More Than an IT Phone Number
When technology stops working, employees often know one thing: call IT.
That is a good first step, but it is not a complete downtime procedure.
Who actually makes the call? What information should be provided? Who informs the doctors and practice administrator? Who communicates with patients? What happens if the phone system is also affected?
Those responsibilities should be understood before an incident occurs.
An emergency process does not need to be complicated. In fact, simple is usually better. Employees need to know who is responsible for making decisions and where they can find the information they need.
This becomes even more important during a cybersecurity incident, when employees may receive specific instructions not to restart equipment, disconnect devices, or continue using certain systems.
"Everybody do whatever seems helpful" is not an incident response strategy.
Keep Important Contact Information Available Offline
Most practices store important information digitally because that is convenient.
The problem is that your digital information may be exactly what you cannot reach during an outage.
Imagine that email is unavailable and employees need to call the EHR vendor. Does anyone know the support number?
What about the internet provider? Your IT company? The phone vendor? The cyber insurance contact?
Critical contact information should be available somewhere employees can reach even if the network, internet connection, or email system is unavailable.
That does not mean leaving sensitive passwords printed beside the front desk. The goal is simply to make sure basic emergency contact information and instructions are accessible without depending entirely on the technology that may be down.
Backups Matter, but Recovery Time Matters Too
Practices often say, "We have backups," and that is important.
But backups answer only part of the downtime question.
The next issue is how long recovery will take.
If a system fails, can it be restored in 30 minutes? Four hours? A full day?
Those differences matter when patients are scheduled throughout the day.
This is why disaster recovery planning should include conversations about recovery objectives, not simply whether data is being backed up. The practice and IT provider should have a realistic understanding of which systems need to return first and what recovery may look like under different circumstances.
Regular testing matters as well. A backup that has never been restored during a test leaves unanswered questions that you do not want to discover during an actual outage.
Internet Outages Deserve Their Own Plan
Not every outage involves your computers or servers.
Sometimes your technology is working perfectly and the internet connection disappears.
For practices that rely heavily on cloud applications, that can be enough to interrupt a large portion of the day.
If your EHR, phone system, patient communications, or other critical applications require internet access, consider what an internet outage would affect. Does the practice have a secondary connection or another approved option? Which functions would continue locally, and which would not?
The right answer depends on the size of the practice, its technology, and how costly downtime would be.
The important part is understanding the dependency before the internet stops working.
Your Vendors Need to Be Part of the Picture
Eye care practices may rely on several specialized technology vendors, and an outage may require more than one company to solve.
Your IT provider may determine that the network is working correctly but the EHR vendor is experiencing an issue. A diagnostic device may be functioning but unable to communicate with its software. Your phone system may depend on an outside provider experiencing its own outage.
Employees should not have to referee between vendors while patients are waiting.
A good IT partner can often help coordinate troubleshooting and provide the technical information other vendors need. That can be especially valuable when one vendor says, "It's the network," and another says, "It's the software."
Clear documentation of vendors, support contacts, account information, and the technology each company is responsible for can make that process much smoother.
Think About Patient Communication Too
Downtime is not only an internal technology issue. Eventually, it can become a patient communication issue.
If the outage is short, patients may experience nothing more than a slight delay. If it lasts longer, the practice may need to explain that systems are temporarily unavailable, adjust the schedule, or contact upcoming patients.
Who makes that decision?
How will the practice communicate if phones or email are affected?
Does your team know what to say without oversharing details that are still being investigated?
A little planning can prevent mixed messages. Patients do not need a technical explanation. They need clear information about what the outage means for their appointment.
Practice the Plan Before You Need It
A downtime procedure that nobody has looked at in two years may not be much better than having no plan at all.
Practices do not necessarily need elaborate emergency drills every month. Even a periodic tabletop discussion can be useful.
Ask the team: What would we do if the EHR were unavailable for the next four hours? What if the internet went down? What if we could not access email? Who would call whom? Which patients could we continue seeing?
Those conversations often reveal simple gaps.
Maybe the vendor phone numbers are outdated. Maybe nobody knows where the paper downtime forms are stored. Maybe everyone assumes someone else is responsible for contacting IT.
Finding those problems during a meeting is much easier than discovering them while the waiting room is full.
The Goal Is Not Zero Downtime
No IT company can promise that a practice will never experience an outage.
Technology fails. Vendors have problems. Internet connections go down. Unexpected events happen.
The goal is resilience.
A resilient practice understands which technology is most important, has reliable backups and recovery processes, knows what staff should do during downtime, and has clear communication and vendor contacts available.
When something fails, everyone does not need to immediately know how to fix the technical problem.
They need to know how the practice responds while the people responsible for fixing it do their work.
So the question is not only whether your IT provider can recover your systems.
Ask something broader:
Could your practice continue caring for patients while those systems are being recovered?
If nobody is quite sure of the answer, that is a very good place to start.