The Ascension Health Outage Was a Communications Continuity Failure

The Ascension incident this month has been covered primarily as a clinical-systems event, with attention on diverted ambulances and paper charting. Less attention has gone to what happened to the communications layer. Patients trying to reach their care teams encountered overwhelmed phone lines, broken portal messaging, and call-center staff who could not access the records needed to answer basic questions.

When core systems go down, the contact center becomes the entire institution to the people calling it. If the contact center has no degraded-mode playbook, the outage compounds. Wait times spike, fraudulent callers exploit the confusion to extract information, and legitimate urgent calls get lost in the queue.

Resilience here is a design problem, not a staffing problem. It includes pre-authorized scripts for known outage scenarios, fallback routing that does not depend on the primary identity systems, and intake workflows that can verify a caller using attributes that survive a database being offline. None of this is glamorous, and most organizations only build it after an incident forces them to.

Ascension will recover. The lesson worth carrying forward is that communications continuity needs to be planned with the same rigor as clinical continuity, and tested under conditions that resemble a real outage rather than a tabletop exercise.