Fire-protection and life-safety (FLS) systems only protect a defend-in-place occupancy if they keep working during the event that calls on them — through a fire, a utility outage, a flood, or a seismic shock. This article covers what makes a hospital's FLS systems resilient and survivable: the requirement that detection, alarm, suppression, and smoke-control equipment ride through fire and loss-of-normal-power conditions, the way those loads are tied to the essential electrical system, and how survivability is engineered, fed, tested, and maintained across the life of the building.
A hospital is a defend-in-place occupancy. Unlike an office building, where the design intent is total evacuation, a hospital protects most occupants by keeping them where they are and moving them only as far as an adjacent smoke compartment if needed. That strategy is entirely dependent on the FLS systems continuing to operate — and continuing to operate during the very emergency that threatens them, not merely up to its onset.
This creates a design objective that is easy to miss when systems are specified in isolation: survivability. A fire alarm system that detects a fire but loses its notification circuits in the first minutes of that fire has failed. A smoke-control system that activates but loses power to its fans when the utility drops has failed. A generator that starts but cannot pick up the fire pump and the smoke-exhaust fans within their required windows has failed. Resilient FLS design treats the whole chain — sense, decide, act, sustain — as something that must survive the hazard end-to-end, and it does so under the layered code regime that governs U.S. hospitals: NFPA 101 (Life Safety Code) and NFPA 99 (Health Care Facilities Code) as adopted by CMS for Conditions of Participation; NFPA 72 for fire alarm; NFPA 13/14/20 for suppression and fire pumps; NFPA 110 for emergency power supply systems; NFPA 70 (NEC), Article 517 for health-care electrical distribution; and the IBC/IFC for construction-type, occupancy, and high-rise provisions — all enforced through the local Authority Having Jurisdiction (AHJ) and the CMS accreditation regime (Joint Commission, DNV, or another approved accreditor).
Survivability is not one system's responsibility. It is an emergent property of how detection, suppression, smoke control, structure, and the electrical backbone are integrated. It must be owned explicitly — typically by the design team's fire-protection engineer and electrical engineer jointly, with the owner's facilities and life-safety leadership at the table — because no single discipline's code section captures all of it.
Resilient FLS design begins by naming the hazards the systems must ride through. For a U.S. hospital these typically include:
Each hazard maps to specific provisions, but the unifying discipline is the same: identify the FLS functions that must not stop, then engineer their power, their circuits, their supports, and their consumables to outlast the event.
NFPA 72 distinguishes between system survivability (the alarm's ability to continue operating during a fire) and ordinary circuit integrity (the ability to detect and annunciate a fault). For hospitals — and especially for buildings that use the alarm system to drive notification, relocation signaling, or smoke-control activation — survivability of the notification path matters because the system must keep telling people and equipment what to do while the fire grows.
Key articles: