Healthcare cyberattack planning has to cover patient portal downtime, not just the servers behind it. Cleveland’s University Hospitals offers a concrete example: keeping clinical sites open did not preserve every digital route patients used to reach them. When the portal disappears, a technical isolation decision becomes a scheduling, medication, communications and payment problem. Restoring a login page is only one part of restoring the service.
What University Hospitals Actually Said
In its cybersecurity incident notice, UH says it detected “unusual activity” on October 22, 2026, activated response protocols and disconnected systems from the internet “out of an abundance of caution.” That is the supported description. It does not establish ransomware, patient-data theft or a confirmed breach.
The notice’s November 2 update said hospitals, emergency departments and physician offices remained open. It also described the operational split: most applications on UH-owned servers were functioning, but could not exchange information outside UH. An application can be running while the service its users need is unavailable. Infrastructure monitoring and patient experience are not the same dashboard.
On November 7, UH announced MyChart was accessible again, according to WKYC’s report quoting UH’s restoration statement. October 22 to November 7 is 16 calendar days: more than two weeks, not three. Those dates do not establish an exact outage duration to the hour.
The statement warned that some features might remain limited and new results or other information could be delayed while data was reconciled. WKYC explicitly noted that the announcement did not update electronic prescribing. Portal access was a recovery milestone, not confirmation that every connected workflow had recovered.
Healthcare Cyberattack Planning Starts With Patient Portal Downtime
UH’s downtime notice described working alternatives rather than simply asking patients to wait. Its phones remained operational, but very high call volumes produced long holds. Patients with urgent care, result or medication questions were directed to their doctor’s office, rather than a main number that could only transfer them. UH asked patients not to call merely to confirm existing appointments unless their care team had contacted them about a change.
Video visits moved to phone, Zoom or in-person appointments with instructions from the care team. Outpatient pharmacies remained open. When electronic prescribing was unavailable, UH said providers could print, fax or call in prescriptions when needed. That describes UH’s fallback; another organization must have its clinical, pharmacy and compliance teams approve alternatives appropriate to its own requirements.
UH also directed patients with Quest Diagnostics testing to Quest’s results service. That was not a universal replacement: UH Specialty Lab and inpatient results still required MyChart or the doctor. Payment at the time of service was unavailable at its cashless facilities, although the notice offered separate automated-phone and online payment routes. These were different dependencies, with different workarounds.
A Working Telephone Is Not a Capacity Plan
My practical starting point would be a workflow inventory owned jointly by IT and operations. For each patient-facing function, record what the patient needs, which outside connection it depends on, the approved alternative and who owns the resulting queue. “Call the office” needs staffing, routing and a way to track completion. Otherwise, the fallback is a hold queue with a reassuring name.
- Appointments: distinguish existing bookings from changes, cancellations and new requests. Keep patient instructions consistent with what scheduling teams can actually deliver.
- Medications and results: name the clinical escalation owner and the approved handoff. Track receipt and follow-up rather than treating a fax transmission as a completed patient task.
- Payments: separate an unavailable collection channel from the underlying balance. Have finance explain permitted alternatives without implying every patient must use a portal.
This is operator analysis drawn from UH’s documented workarounds, not a claim that UH used this exact inventory. I would exercise the alternatives under sustained demand, including shift changes and unavailable staff. A plan that works for a quiet afternoon may not remain workable after repeated days of diverted requests.
Status Updates Are Part of the Recovery System
The public messages also need reconciliation. On November 10, UH’s incident page still displayed its November 2 update and wording that MyChart was offline, despite the later restoration announcement. The dated announcement is evidence of restored access; the older page is not evidence of a fresh outage.
There was still a narrower limitation afterward. In its November 8 update, cleveland.com reported a UH spokesperson’s statement that bill pay was the only remaining out-of-service portion of the portal. That does not establish that electronic prescribing, a separate workflow, had recovered. Neither an expected billing fix nor portal availability supplies a verified e-prescribing restoration date.
I would give every status update an effective date, a named owner and a service-by-service description. When a newer notice supersedes an older one, link them and remove contradictory instructions. Patients should not have to debug the organization’s communications history to find a working route to care.
Keep the Downtime Team Through Reconciliation
HHS’s ASPR TRACIE Healthcare System Cybersecurity: Readiness & Response Considerations treats recovery as a continuation of downtime. It recommends planning the paper-document lifecycle, maintaining consistent communications and supporting the migration of manual documentation back into electronic systems. It also warns that partial functionality can hinder workflows or increase risk. These are planning considerations to adapt, not one configuration for every provider.
My recovery checklist would therefore test complete workflows: request received, routed, acted on, documented and visible to the appropriate patient or team. Clinical leaders would decide how to reconcile medication requests and results safely; operations would retain staff for the backlog. The finish line is not merely an available portal. It is knowing what happened while the portal was unavailable, what remains unfinished and who is responsible for closing the loop.
