Life Safety Code Q&A

In a recent Q&A on the FacilityCare website, consultant Brad Keyes answered a question about the process CMS uses to adopt a new edition of the Life Safety Code


In a recent Q&A on the FacilityCare website, consultant Brad Keyes answered a question about the process CMS uses to adopt a new edition of the Life Safety Code. 

Q: How often does the Center for Medicare & Medicaid Services (CMS) adopt newer versions of the NFPA 101 Life Safety Code (LSC)? It seems to me that modifications made in more recent versions of code are meant to either clarify questionable data, improve or expand safety requirements, or add items that have not been previously addressed (invention, innovation, materials, etc.). I would think the most recent version of any code is the most relevant. Fifteen years between adopted versions seems a little out of whack.

A: CMS first adopted the 1967 edition of the LSC in 1970. Then it adopted the 1985 edition in 1988. Then it adopted the 2000 edition in 2003. Now it is on the cusp of adopting the 2012 edition. So that means there have been the following numbers of years between adopting a newer edition of the LSC: 18 years, 15 years and 12 years.

Read the full answer. 

 

 

 



February 20, 2015


Topic Area: Safety


Recent Posts

UF Health Hospitals Rely on Green Globes to Realize Their Full Potential

Case study: The process encouraged the team to push themselves in several areas.


How Healthcare Facilities Can Be Truly Disaster-Resilient

Real resilience looks different than what’s written down in plans


TriasMD Breaks Ground on DISC Surgery Center for San Fernando Valley

It is set to open in Q3 2025


Bigfork Valley Hospital Falls Victim to Data Breach

The incident occurred in November 2024


AI-Driven Facilities: Strategic Planning and Cost Management 

6 factors to ensure infrastructure, operations and financial management support AI’s integration


 
 


FREE Newsletter Signup Form

News & Updates | Webcast Alerts
Building Technologies | & More!

 
 
 


All fields are required. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.