Wednesday, May 25, 2011

Managing the Impact and Costs of Emergency Power Testing on Hospital Operations: A Case Study

By David L. Stymiest, PE CHFM FASHE; Jack W Dean, PE; and Anand K. Seth, PE CEM 
(This white paper was first presented at ASHE's 35th Annual Conference, July 1998.  It has not been updated for 2011 and is provided here as an historical reference only.)

Introduction
Hospitals are required to have an emergency power testing program in place to meet the requirements of NFPA 70, NFPA 99 and NFPA 110, as well as standards established by accreditation organizations such as JCAHO. The goal of the emergency power testing program should be to comply with regulatory requirements without adversely affecting the operation of the hospital or the well-being of the patients. The specific requirements to be met are referenced by the forerunner to this paper. That technical document addresses the importance of simulating actual loading conditions during the testing period and the necessity of following up on the test results to identify problems and take corrective action. This paper builds upon that publication by detailing a case study of emergency power testing occurring over a significant period of time at the Massachusetts General Hospital (MGH), issues uncovered (which might be described as second order consequences of the emergency power testing effort) and the steps taken to eliminate problematic issues.

Emergency power testing programs involve transferring the power sources of operating systems from utility power to the emergency generators and back. This action can cause disruption to increasingly more complex clinical and building equipment, building automation systems, and hospital operations. When managed properly and proactively followed through, these disruptions are valuable learning experiences and provide opportunities to improve the hospital infrastructure, improve hospital operations and reduce the hidden costs of testing. This case study presents a number of lessons learned and offers proactive strategies for managing the process. The lessons learned also illustrate areas where future system designs should be improved.

No comments:

Post a Comment