Skip to content
Healthcare IT & HIPAA

Not If, But When: The Outage Preparedness Plan Every Medical Practice Needs

November 17, 2026

By the Galleon IT Solutions team

Healthcare-first managed IT engineers serving DFW and Houston since 2017.

Last reviewed: November 17, 2026

November gave every business owner a reminder they did not ask for. On November 12, a Microsoft 365 outage left Outlook, Teams, and other services failing for users worldwide for roughly a day. The next afternoon, the FAA halted departures nationwide for more than four hours after problems with aging, overloaded air traffic control equipment, and thousands of flights were cancelled. Afterward, the Secretary of Transportation warned that more of these will happen unless the system is upgraded.

That warning applies well beyond air travel. Every medical practice depends on systems it does not own and cannot fix: a cloud EMR, Microsoft 365, an internet circuit, a phone carrier, an e-prescribing network, a clearinghouse. Each of them will fail at some point. The useful question is not whether your practice will face an outage, but whether the plan for it exists before it starts.

This is the preparation checklist we work through with practices across Dallas-Fort Worth and Houston. Our companion article, When the Cloud Goes Down, covers what to do in the moment.

1. Know which outside services your practice cannot run without

Start with an honest inventory. List every system the practice uses on a normal day, and for each one write down who provides it, what stops working if it fails, and how long you could manage without it. Most practices find their list is longer than they expected:

  • The EMR and practice management system, cloud or hosted
  • Email, calendars, and Teams, usually Microsoft 365
  • The internet connection at each location
  • Phones, especially cloud VoIP that rides on the internet
  • Fax, whether an analog line or a cloud service that delivers to email
  • E-prescribing, EPCS tokens, and the Texas PDMP
  • Labs, imaging, and clearinghouse connections
  • The patient portal, online scheduling, and payment processing

The point is not to eliminate these dependencies. It is to know them, so an outage does not reveal one for the first time.

2. Remove the single points of failure you do control

You cannot fix Microsoft's network or the FAA's radar. You can make sure your own building is not the weakest link.

  • A second internet path. A business-grade primary circuit with automatic cellular failover means a cut cable or a carrier outage does not take your cloud EMR, phones, and email down together.
  • Phones that survive the internet. If your phones are cloud VoIP, confirm calls can be forwarded to mobile phones from the provider's portal, and that someone knows how to do it.
  • A fax path that does not depend on email. If faxes normally arrive in Outlook, know how to read them directly in the fax service's web portal when email is down.
  • Workstations and power. Battery backups on network equipment and key workstations keep a brief power flicker from becoming an hour of rebooting.

3. Write the downtime procedure before you need it

A downtime procedure is a short document that tells staff exactly how to keep working when a system is unavailable. It should fit on a few pages and cover check-in, charting, prescriptions, referrals, results, and how everything gets entered back into the system afterward. HIPAA expects practices to have contingency procedures, and the practical value is greater than the compliance value. Our EHR downtime plan template walks through what to include.

Keep printed copies at every front desk and nursing station. A downtime plan saved only in SharePoint or Outlook is no help when Microsoft 365 is the thing that is down.

4. Set up communication channels that do not depend on the system that failed

During the Microsoft outage, many organizations discovered that their emergency communication plan was an email. Build a backup that works when email and Teams do not.

  • A staff text group or calling tree, with current mobile numbers, kept outside Microsoft 365
  • A printed list of phone and fax numbers for your top referral sources, labs, pharmacies, and hospitals
  • Your IT partner's support number posted where every staff member can see it
  • A short template message for patients if appointments or the portal are affected

5. Decide who is in charge

When something breaks, someone has to make the call to switch to downtime procedures, communicate with staff, and decide when to switch back. Name that person and a backup for each location. Without a named decision-maker, practices lose the first hour to discussion.

6. Make sure backups cover the cloud, too

Many practices assume that because data lives in Microsoft 365 or a cloud EMR, it is automatically backed up. Providers protect their own infrastructure, but recovering your specific data after deletion, corruption, or ransomware is often your responsibility under the service agreement. A separate backup of Microsoft 365 mail and files, tested regularly, means a provider problem or a bad day does not become permanent loss. Our article on what makes a backup HIPAA compliant covers the details.

7. Prepare staff for outage-themed scams

Every major outage is followed by phishing that uses it as cover. Train staff before the next one: no vendor asks for passwords during an outage, nobody installs software or grants remote access because of an unexpected call, and anything suspicious goes to your IT partner. Five minutes of this at a staff meeting is cheap insurance.

8. Rehearse it once a year

A plan nobody has practiced is a plan that fails on first use. Once a year, run a short drill: announce that email and the EMR are down for one hour, and have the front desk and clinical staff work the downtime procedure. Note where people got stuck and fix the plan. Many cyber insurers and HIPAA reviewers also look for evidence that contingency plans are tested, not just written.

9. Review the plan after every real outage

The Microsoft outage and the FAA ground stop are free lessons. After any outage that touches your practice, spend fifteen minutes with your IT partner on three questions: what worked, what did not, and what changes before the next one. Update the plan and the printed copies.

What a good IT partner contributes

Preparation is shared work. The practice owns the procedures and the decisions. A healthcare-focused IT partner should own the technical side: mapping dependencies, building redundant internet and phone paths, backing up cloud data, monitoring provider status, warning you about outage-themed phishing, and helping run the annual drill. At Galleon, this is part of how we support practices across DFW and Houston, not a separate project.

If November's outages showed gaps in your practice's plan, our free IT risk assessment is a good place to start, or call us at (972) 776-6366.

Frequently asked questions

It is a written plan for how the practice keeps seeing patients when key systems or services are unavailable. It covers downtime procedures, backup communication, who makes decisions, and how normal operations are restored afterward.

Yes. The HIPAA Security Rule includes contingency planning requirements, including data backup, disaster recovery, and emergency mode operation procedures. Testing and revising the plan is also part of the standard.

Keep a staff communication channel outside Microsoft 365, print your downtime procedure and key contact numbers, make sure fax can be read without email, back up your Microsoft 365 data separately, and know how to confirm an outage quickly with your IT partner.

Yes. When the EMR, phones, and email all run over the internet, a single circuit becomes a single point of failure for the entire practice. Automatic failover to a second connection is one of the most cost-effective protections a cloud-based practice can have.

At least once a year, and after any real outage that affects the practice. A short tabletop or one-hour drill is enough to find the gaps.

Get Started

Ready for a straight answer about your IT?

Schedule a 20-minute discovery call. We will tell you what is working, what is not, and what the gaps would cost.