Healthcare structures are not designed merely to protect life and prevent collapse — they are designed to keep an acute-care hospital open for business through and immediately after a design-level earthquake, hurricane, flood, or blast. This Article covers the resilience philosophy, structural redundancy, and the operability targets that distinguish a hospital frame from an ordinary building, and the verification, hardening, and recovery-planning that make "operational after the event" a real, demonstrable outcome rather than an aspiration.
This article is the resilience and post-event-operability home for the structural Part. It assumes the demand-side seismic engineering (response spectra, drift limits, ductile detailing, base isolation, state hospital-seismic regimes) lives in the companion Seismic Design & Drift Control Article, and that the protection of contents, equipment, and distributed systems lives in the Nonstructural & Equipment Seismic Anchorage Article. Here the focus is the system-level question: what does it take for the building — frame, envelope, foundation, lifelines, and the engineered protective systems — to still function as a hospital the morning after.
Most buildings in the United States are designed to a life-safety standard: in a design-level event, occupants can evacuate and the structure will not collapse, but the building may be damaged beyond economical repair and may be unusable. Hospitals reject that bargain. A hospital that closes after a disaster fails at the exact moment its community needs it most — when injuries surge and other facilities are also down.
The governing framework expresses this through Risk Category IV (essential facilities) in ASCE 7 and the IBC, which assigns hospitals the highest Importance Factor and the most stringent design requirements. Risk Category IV pushes the design from "don't collapse" toward "stay functional." The companion essential-facility-loads Article covers how the Importance Factor scales loads; the point here is the intent behind it: a hospital is infrastructure, and its structural performance objective is continued operation, not merely survival.
Resilience as a discipline distinguishes several performance levels along a continuum, which owners and design teams should name explicitly in the basis of design:
Resilience also has a time perspective that pure code compliance does not capture: a building can meet Immediate Occupancy structurally yet still be unusable for weeks because a non-redundant chiller plant, a single feeder, or an unbraced sprinkler main failed. Resilience planning therefore looks at the whole building as a system and at the recovery timeline — how long until full function is restored — not just at the frame.
Although the structural Part's seismic Articles dominate the conversation in high-seismic states, resilience for a hospital is multi-hazard by nature, and the governing hazard varies by region. A complete resilience basis of design names every credible hazard for the site and sets a structural performance target for each.
| Hazard | Primary structural concern | Typical governing reference |
|---|---|---|
| Seismic | Lateral drift, ductility, foundation performance, nonstructural anchorage | ASCE 7, IBC, ASCE 41 (assessment), state hospital-seismic law (e.g., California HCAI/OSHPD) |
| Hurricane / high wind | Wind pressures, wind-borne debris, roof uplift, envelope breach | ASCE 7, IBC, regional wind maps, FEMA guidance for safe-room/shelter design |
| Flood / storm surge | First-floor elevation, buoyancy/scour, critical-equipment elevation | ASCE 24 (flood-resistant design), FEMA flood maps, IBC flood provisions |
| Tornado | Extreme wind, debris impact, designated storm shelters | ICC 500 / FEMA P-361 (storm-shelter standard), ASCE 7 tornado provisions |
| Fire (structural) | Loss of capacity at elevated temperature, compartmentation | IBC fire-resistance ratings, NFPA 101/220 |
| Blast / intentional events | Progressive collapse, member loss, standoff | DoD/GSA progressive-collapse guidance where applicable (typically federal/VA facilities) |
| Snow / ice | Roof load, drifting, ponding | ASCE 7 snow loads |
A critical resilience principle is that the structure must protect the systems that keep patients alive, and those systems are vulnerable to hazards the frame easily survives. A wind-borne-debris breach of the envelope, a flood that submerges a basement electrical room, or a roof failure over an OR can take a hospital offline even though the structural frame is intact. Resilience design therefore integrates the structural Part with the envelope, electrical, mechanical, and fire-protection systems — siting critical equipment above flood elevation, hardening the envelope against debris, and structurally bracing the lifelines so they survive with the frame.
Redundancy — the presence of multiple load paths, so that the loss of one element does not cause disproportionate failure — is a core resilience strategy and is explicitly rewarded in the codes. ASCE 7 applies a redundancy factor (ρ) to the seismic force in the lateral system: a non-redundant lateral system (few resisting elements, so that the loss of one significantly reduces capacity or causes large torsion) is penalized with a higher design force, while a system with many distributed, well-configured resisting elements earns the baseline factor. The code is, in effect, paying owners to design redundancy in.
Structural redundancy for hospitals shows up in several deliberate choices: