Which Life Safety Findings Do You Contest After a State Survey?
A state agency survey conducted on behalf of CMS cited three Life Safety Code deficiencies at a 180-bed hospital. (1) The annual fire alarm test record for the past two years does not document testing of notification appliances in nine storage and mechanical rooms; the vendor's contract states that all devices were tested. (2) Annual inspection of 14 of 60 fire-rated door assemblies cannot be evidenced for the current year. (3) The monthly generator test under load was documented at 30 percent of nameplate for 11 of 12 months, with no annual test at the hospital's actual load. The administrator wants to contest (1) and (2) as 'paperwork only' and accept (3). The plan of correction is due in 10 days, and the survey report notes that the generator finding is at the Condition level.
1. Advise the administrator on which findings to contest and what standard a challenge must meet.
Read the worked answer
I would advise contesting nothing unless we hold factual evidence, and I would say plainly that the 'paperwork only' framing is the weakest position available.
The standard. The Condition of Participation requires the physical environment to meet the Life Safety Code, and compliance is demonstrated by documentation. Missing documentation is the deficiency. A challenge succeeds on a factual error - the wrong room count, a device-level report showing the appliance was in fact tested, a door inspection performed and filed under the wrong asset ID. A challenge fails when it rests on 'we're sure it happened.'
(1) Alarm testing. Before deciding, pull the vendor's device-level test reports and the fire alarm panel event history for the nine rooms. If the reports substantiate testing, we have a factual basis to request correction of the record and a strong argument. If the vendor only provides a summary letter, we accept the finding - and we have a contract problem, not a survey problem.
(2) Door inspections. Same test. If 14 assemblies genuinely went uninspected, we accept. Annual door inspection cannot be reconstructed after the fact.
(3) Generator. Accept without argument. It is Condition-level, and contesting a load-testing deficiency where the record itself shows 30 percent is not credible.
Contesting weak findings burns credibility that we will need on the Condition-level item.
2. What has to be in the plan of correction for these three findings to be accepted, and what must you do before the plan is even written?
Read the worked answer
Before writing: walk the nine rooms and the 60 doors today. Confirm the alarm devices are present, unobstructed, and functional, and confirm the door assemblies close and latch. This is an interim measure and it also tells us whether we have a documentation failure or a hardware failure - very different plans.
Plan of correction, per finding, must state:
- The corrective action - completed, dated, with evidence attached (device-level test reports, door inspection sheets).
- What was done for the patients in the interim, e.g., the sweep above plus any interim life safety measures for spaces with unverified detection coverage.
- The systemic fix - a reconciled device inventory matched to the testing contract; contract language requiring device-level reports, not summary letters; door assemblies loaded into the CMMS with their own PM schedule and asset IDs; generator testing on a written load profile with the actual hospital load measured annually.
- Who is responsible by name and title, and the monitoring and audit frequency - typically a monthly internal audit for a defined period with results reported to the safety committee and the governing body.
- What happens if it recurs - the escalation path.
On the Condition-level item, I would ask CMS/state for the opportunity-to-cure track, present the completed annual load test with a documented load bank or hospital-load measurement, and treat this as the highest-priority item in the plan. A plan that leads with the weakest finding and buries the Condition-level one will not be accepted.
3. The vendor offers a retroactive letter stating all devices were tested. Do you submit it?
Read the worked answer
No - not as support for disputing the finding.
A retroactive attestation is a statement about what someone believes happened, not a record of what happened. It carries little weight on its own, and if the surveyor asks for the original device-level record or panel history and we cannot produce it, we have converted a documentation deficiency into a credibility problem and invited closer scrutiny of every other vendor record in the file.
What I would submit instead: the actual contemporaneous evidence if it exists - the device-level test reports, the panel event log, the technician's daily work tickets. If that evidence substantiates testing, we have a factual argument and we can also show the surveyor why the chart was incomplete. If it does not exist, we accept the finding, submit the systemic correction, and separately manage the vendor performance issue through the contract. The honest answer to the administrator is that the letter protects the vendor, not the hospital.