RSSRecent Articles

I can’t drive – 5?

I recently fielded a question regarding vehicle speed limits on a hospital campus.

I think we can agree that we don’t want folks tearing around our grounds, running into or over people and things, but are there specifics involved? (I think I’m smelling a risk assessment here…)

The situation presented to me revolved around a current practice of posting 5 miles per hour as the campus speed limit, which, as I’m sure you can imagine, can be tough to enforce, regardless of whether you live in NASCAR country. So, the question became: Can the campus speed limit be raised to 10, or even 15, miles per hour?

To my fairly certain knowledge, there is no definitive nationwide regulatory source that would come into play; but, as you can well imagine, there are a number of Authorities Having Jurisdiction who might be willing to offer some assistance in this regard. My immediate thought (and probably the most useful) would be to check with municipal law enforcement to see what they might recommend/require in this regard, and move forward accordingly. I’m thinking that there would be only minor, if any, objection to a raise of the limit to 10 miles per hour, and maybe even 15 miles per hour. But checking with the law enforcement folks is a very fine place to start.

So, how fast can you go?

Random acts of impenetrable prose

Could I have a volunteer from the audience?

Whilst working in the upper part of the Midwest, I found an interesting take on how one might gather volunteers to help out as “victims” when conducting an emergency response exercise that calls for said victims (“paper” patients are OK in a pinch, but isn’t it way more fun/realistic to have some flesh-and-blood types to run through the process?) In this particular area, high school students, in order to fulfill their obligations for graduation, are charged with participating in X number of community service hours during their (hopefully) four-year stint. If I may opine for a moment, I think the community service idea is way cool and with any luck, might bring back the whole “taking care of each other” mindset that seems to have fled screaming into the night. I see way too much trash dumped by roadsides, etc., to think that we are accelerating as a culture toward a positive destination . . . but I digress.

At any rate, a process was set up with the schools that allowed for participation in emergency exercises to count toward the community service requirement. How cool is that? I don’t know if you have such a program in your neck of the woods, but I think it’s definitely worth checking out. And if you’re already doing this, how come you didn’t share it with the group? Shame, shame, shame…

What we have here is a failure to communicate, or is it a water failure? Sewer failure?

Another survey finding that’s been bubbling up to the top lately relates to your utility system disruption/failure response plans. EC.02.05.01, EP #9 requires hospitals to have written procedures for responding to utility system disruptions. I’ve seen a number of folks tagged for not having the full “suite” of response procedures; if you have a utility system, then you need to have a written procedure for responding.

Now I would think that as a function of your incident command structure, (which is, like, totally compliant with the requirements of the National Incident Management System), you should be able to appropriately manage utility disruptions. However, I guess that sort of begs the question: Do you stand up your IC for utility systems issues or is there a reluctance (or something similar to that) to pull the trigger when push comes to a little bigger push? And, once again, it comes down to how (and perhaps more importantly, how well) you educate/communicate/simplify your frontline folks.

My general experience, fortunately, has been that disruptions to single systems tend to be rather more transient than not–something that can be “endured” until we get things back in order. And I think an important consideration when it comes to endurance is having a simple structure, based on what one might consider “normal” operations. This way, staff don’t have to worry so much about getting from Point A to Point Z because they are sufficiently familiar with B, C, D, and so on. They can respond quickly and appropriately, regardless of what’s going on (or isn’t going on, which I guess is a good indicator of a disruption).

So, do you have written plans for each of your utility systems? When’s the last time you had a chance to practice on some of the more esoteric systems? I’d love to hear what folks are doing, and I suspect that I am by no means the only one.

Mac’s Brief on the September TJC Executive Briefings, Part 2

As promised, I continue going the standards The Joint Commission (TJC) unveiled as the top 10 most frequently cited standards for the first six months of survey year 2011 at the annual Executive Briefings meeting. Five (count ‘em) of those standards were in the environment of care (EC)/life safety (LS) world. Here are the last three:

TJC cited 47% of hospitals for LS.02.01.30 (whew, finally under 50%). This is where things went slightly awry for yours truly as it was apparently indicated that the findings (generally under EP #2, which refers to the fire protection features of hazardous areas) have to do with signage. At EB, an example was given of proper labeling of a vent stack from sterile processing that might have hazardous materials (isn’t that why we have EC.02.02.01?) Also mentioned was the concept of the risk assessment (did you really think that was ever going to go away?) to determine what soiled utility rooms should be locked or otherwise secured. Again, my thought was that this was covered under EC.02.02.01 or maybe EC.02.01.01, but in the Life Safety chapter? I didn’t see that one coming!

When it comes to standard EC.02.03.05 (of which 42% of hospitals were cited), I think the safety community has to come together and convince our maintenance and testing vendors that we are sick and tired of having our heads handed to us because they “buried” some deficiency on page 17 of a report only to have the surveyor find the stinking thing and say, “So, what about this?” We need to have a list of deficiencies identified during any maintenance and testing activity provided to us, before the vendors leave the building. We can no longer afford to wait a month or six weeks to get the report of findings; the clock starts ticking the moment these concerns are identified and we need to be jumping on them quickly and assertively, which may entail including the implementation of some sort of interim measure to ensure that we are not placing folks at risk. I absolutely understand that doing so is, in many ways, nothing but a pain in the tuchus; but until such time, as we are proactively managing this stuff, this is going to continue to be among the most frequently cited standards. I say we end it here—who’s with me? FREEDOM! Sorry, got a bit carried away there. Must be ‘cause I’m wearing my (metaphorical) kilt . . .

Finally, LS.02.01.35 (of which 36% of hospitals cited): This standard relates to all things sprinklers—the 18- inch rule, stuff hanging on sprinkler piping, cabling tied to sprinkler supports, all that stuff. Again, this is very much a numbers game. What’s the likelihood that somewhere, above some ceiling, the cable monkeys have run some conduit or other detritus over a sprinkler line or tied it to a support? Very bloody likely, I’d say, very bloody likely.

Getting back to this infection control thingy (as promised in my last post), it was announced that the life safety surveyors are receiving education relative to basic IC issues, including scope cleaning and the separation of clean and dirty scopes. The announcement brought up a thought—for those of you with not-so-generously-proportioned scope cleaning areas, particularly when the soiled and clean processes are separated only by distance and not by a physical barrier, you might want to consider a risk assessment to determine whether your processes are pristine. I know you are doing the best you can, but sometimes you have to take those types of decisions out, dust ‘em off, and look at them again to make sure they are still viable. It may be your only defense during a survey, and I say you can’t have too many of them, only not enough.

For those of you not so executively inclined: Mac’s Brief on the September TJC Executive Briefings

To the surprise of almost no one (as far as I can tell), when The Joint Commission (TJC) unveiled the top 10 most frequently cited standards for the first six months of survey year 2011 at the annual Executive Briefings meeting, five (count ‘em) of those standards were in the environment of care (EC)/life safety (LS) world. Each standard relates directly to the increasing coverage of the life safety surveyors. It also appears that their scope is going to be expanding into the realm of infection control (IC), but more on that in the next blog post (stay tuned).

While the EC/LS world had to settle for second place on the list with LS.02.01.20 (taking third: LS.02.01.10, fourth: LS.02.01.30, fifth: EC.02.03.05, and eighth: LS.02.01.35), it is clear there is a great deal of work yet to be done by hospitals to gain a little control over this deluge of deficiencies.

A whopping 57% of hospitals surveyed between January and June were cited on LS.02.01.20, which has everything to do with maintaining the integrity of egress. Hospitals were caught for a number of deficiencies: doors locked in a means of egress, projections, corridor clutter, and configuration/designation of suites.

My colleague Brad Keyes and I have spoken (some would say approaching ranting) about the importance of your life safety drawings and how they facilitate the survey process if they are accurately maintained. It appears the quality (or lack thereof) of life safety drawings are more frequently put to the test during survey, with not-so-glowing results. (I’m interpreting a 43% success rate as something less than A-level performance.) I suspect that a majority of the findings might still relate to corridor clutter (after all, how difficult is it to find two instances of unattended, unallowed stuff in the corridor, hmm?) Interestingly enough it was revealed that one cannot manage the corridor clutter LS deficiency through the plan for improvement (PFI) process, which is kind of stinky.

My opinion is that if you do your risk assessment for interim life safety measures (ILSM) to compensate for the LS deficiency represented by corridor clutter and actually resolve it in some way, then that is an appropriate use of the process. But, in this case—and so many others, it makes my head spin—my opinion matters not a whit. So egress woes top the list.

Moving on to LS.02.01.10, which also has a 57% rate of findings in hospitals for the first half of 2011. This one’s fairly straightforward: doors (not latching), doors (undercuts), doors (lacking closers), more doors (can anyone say door stops?), and then sealing around ductwork penetrating fire-rated barriers. Again, how difficult is it to find this stuff (and yes, I know that it is our job to make it difficult, but still…) Once again, accurate life safety drawings are the key; if your drawings say door is a fire door, then that’s how it will be surveyed, even if it’s a smoke door now since you’ve sprinkled your building–the drawings never lie!)

More top-cited standards will be discussed in the next blog post–stay tuned!

Cappiello named COO of Healthcare Facilities Accreditation Program

We’d like to report some exciting news: former Joint Commission vice president and long-time advisor to HCPro’s own Briefings on The Joint Commission, Joseph L. Cappiello, has been named the chief operating officer for the Healthcare Facilities Accreditation Program (HFAP). Mr. Cappiello has been a great help to HCPro’s Association for Healthcare Accreditation Professionals (AHAP) and Briefings over the years. You also might know some of the books he’s authored, including The Chapter Leader’s Guide to Emergency Management. We’d like to congratulate Joe on his latest endeavor!

From the official press release:

Joseph L. Cappiello has been appointed new Chief Operating Officer of the Chicago-based Healthcare Facilities Accreditation Program (HFAP). HFAP, the nation’s oldest hospital accreditation organization, has been authorized by the Centers for Medicare and Medicaid Services (CMS) to accredit healthcare facilities for compliance with CMS standards since the beginning of Medicare in 1965.

Cappiello served for 10 years as Vice President of Field Operations at The Joint Commission and brings to HFAP a strong history of accreditation management experience. His role at HFAP will be to direct the nimble and educative approach to facility accreditation that exemplifies the organization, and to lead the continuing evolution of an accreditation process that meets the challenges of the complex healthcare environment. Mr. Cappiello will take his post October 3. He succeeds George A. Reuther, who is stepping down after 25 years of service

“As a smaller organization, HFAP can provide facilities with both a rigorous assessment and a resource for improvement, should they miss the mark,” said Michael J. Zarski, HFAP CEO. “We are thrilled to have Joe join our team, to help us further our personalized approach to the accreditation process. His caliber and experience will provide great value to HFAP and the facilities we work with.”

“HFAP is not just as an evaluator, but an educator,” said Cappiello, “which is what first drew me to the organization. It’s also light on its feet—quickly adaptable to the changing quality environment. And it brings a holistic survey process that creates a true partnership with the facilities it serves. I am pleased to be onboard.”

Cappiello was Vice President for Accreditation Field Operations at The Joint Commission from 1998 to 2008, directing key internal functions as well as the 500-member field surveyor cadre. Known as an innovative and dynamic leader, Cappiello reorganized the operational structure of accreditation operations and made dramatic improvements in the training and operational effectiveness of the surveyor cadre.

Spearheading initiatives on emergency management and disaster response, he led evaluation teams to New York City following the attacks of September 11, testified before Congress after Hurricane Katrina, and advised the governments of Israel and Australia on disaster preparedness. From 2008 to the present, Mr. Cappiello led his own consultancy to help healthcare facilities improve quality and maintain compliance with accreditation standards. He holds a BSN from the University of Rochester and an MA in Heath Facilities Management from Webster University.

The Healthcare Facilities Accreditation Program (HFAP) is a non-profit, nationally recognized accreditation organization. It has been accrediting healthcare facilities for over 60 years and under Medicare since its inception. Its mission is to advance high-quality patient care and safety through objective application of recognized standards. More information on the program can be found at

Under Pressure – Positively Clean

In yet another dispatch from the regulatory survey landscape, one item I’ve noticed being cited during surveys are related to the surgical environment–maintenance of temperature and humidity, ensuring appropriate air exchange rates, and making sure that your HVAC systems are appropriately maintaining pressure relationships. The other concern in this realm is making sure that you have a planned response for those instances in which any of the these performance expectations cannot be met. Make sure that the end-users of the environment are clued in to those responses. Depending on where you are, the age of your building systems, etc., you may very well experience (or perhaps have already experienced) performance outside of design/expected parameters (i.e., how’s that climate change working out for your building?)

Minimally, the infection control implications can be far-reaching, and if not appropriately managed, can be devastating to your patients. Likewise, you need to keep a close eye on the pressure relationships between clean and dirty areas; a positively pressured decontamination area can play havoc with the environment in your sterile processing and supply areas. A positively pressured corridor in your surgical area  can have a deleterious effect on your OR procedure rooms.  (Notice I said “area” not “suite”– everyone knows there are no corridors in surgical suites.)

You know how complicated your building systems can be–it’s time to make sure that your end-users understand that when things are not right, we need to collaborate to ensure appropriate protection of our patients. Nobody wants to mess with the OR schedule, but as hospital-acquired infection occurrences venture ever closer to the “never event” it will take a big-time team effort to make sure that our operations (both figuratively and literally) are where they need to be.

This is a public service announcement

This is a public service announcement—with guitars! (Okay, maybe not guitars) or perhaps this will work:

Money well spent…imagine that.

Every once in a while I like to share stuff that folks are developing in other areas of concerns/disciplines, and I think this one is a peach. In fact, I think it’s so useful, I’m just going to thank my good friend and colleague Marge McFarlane for sharing this with me, which helps me to share with you, and then shut the heck up:

The American College of Emergency Physicians is proud to announce the release of its newest training, Hospital Evacuation: Principles and Practices. The training can be found here

We hope that you take the time to view the course and pass the information along. A description of the course can be found below:

“Healthcare facilities must be ready to tackle anything that comes their way. In times of disaster, natural or technological, they must remain open, operational, and continue carrying out their functions. When the situation escalates to a level that endangers the health and/or safety of the facilities patents, staff, and visitors, evacuation of the endangered areas is necessary. Safety and continuity of care among evacuees during a disaster depend on planning, preparedness, and mitigation activities performed before the event occurs. At the completion of the course, hospitals and other healthcare providers with inpatient or resident beds will have basic training and tools to develop an evacuation plan. This one-hour course will take the participant through the stages of preparing for a facility evacuation. It begins by performing an assessment of possible vulnerabilities and the resources available to a facility. Next, the course walks the learner through the development of a functional plan for a healthcare facility, and identification of key personnel positions implemented when a facility evacuates and the roles and responsibilities of each. The course concludes by addressing recovery issues, both plan development and operational.”

Good stuff, and I encourage each one of you with anything more than a passing interest in such things to check it out.

And now for something completely…the same

Time for a quick roundup of some recent survey trends:

  • We’ve talked about the overarching issues with weekly testing of plumbed eyewash stations any number of times over the years and I am always happy to respond to direct questions. The key element here is that if your organization is not conducting an at least weekly testing regimen for your plumbed eyewash stations and has not documented a risk assessment indicating that a lesser frequency is appropriate, it will likely be cited. My consultative advice: If you’re not testing at least weekly, please do so, or do the risk assessment homework.
  • With the extra life safety surveyor time during survey, the likelihood of encounters with frontline staff is on the rise. And apparently, it is not enough for folks to know what they are doing, but there is also an expectation that they will understand why they do what they do, primarily in the context of supporting patient care (which we all do—everything that happens in a hospital can trace back to the patient). I guess it won’t be enough for folks to be able to respond appropriately when asked how they would respond to a fire. They also need to understand how their response fits into the grand scheme of things. I really believe that folks understand why their jobs are important; we just need to prepare them for the question. Probably more on this as it develops.
  • 96 bottles of beer on the wall, 96 bottles of beer—but will that be enough beer to last 96 hours (I guess it depends on how thirsty you are)? So the question becomes this: If a surveyor asks to see your 96-hour capability assessment, what would you do, and perhaps most importantly, can you account for it in your Emergency Operations Plan? My general thought in this regard is that the 96-hour benchmark would be something that one would re-visit periodically, just as you would your hazard vulnerability assessment, in response to changing conditions, both internal and external.
  • As a final thought for this installment, please make sure that you (that would be the royal “you) are conducting annual fire drills in all those lovely little off-site locations listed as business occupancies on your Statement of Conditions. And make very sure that staff is aware that you are conducting those fire drills. There’s been a wee bit of an upsurge in fire drill findings based on the on-site staff not being able to “remember” any fire drills, in some instances, for several years. The requirement is annual and I don’t think any of us wishes to get tagged for something as incidental as this one.

Your mother should know…but what if she doesn’t?

I’ve noticed a little word popping up in recent survey reports, a word that strikes fear in my heart. I don’t know how widespread this might be, so if you folks have an opportunity to weigh in on this conversation, I’d be really interested in what you all are seeing out there. And so, today’s word of the day is “should.” Now scream real loud!

I think we are all pretty familiar with those things that are legitimately (perhaps specifically is a better descriptor) required by the standards. I like to refer to those requirements as “have to’s” – we have to test certain fire alarm components at certain frequencies, we have to conduct quarterly fire drills, etc. Now I’m certainly not someone who is going to complain when a regulator (of any stripe) provides us with concrete strategies (this is where we move from the “have to’s” to the “how’s,” inching ever closer to “should”) for achieving or maintaining compliance.

But the question I keep coming back to is how are we supposed to know about these unwritten requirements (we used to call them ghost standards—boo!) if they are, as noted, unwritten. And the reason I keep coming back to this question is because I’ve been seeing a number of findings lately that revolve around what an organization “should” do. And please, I am not necessarily disagreeing with the wisdom engendered in many, if not most of these findings (we’ll mention a couple of examples in a moment), but there is a point at which the line between what is consultative advice and what is actually required blurs so completely that any tipping point, compliance-wise, is almost completely subjective.

As an example (and remember, I’m not disagreeing with the concept), a recent survey report included a finding because the “clean” side of central sterile was negative to the adjacent corridor, with the qualifier “air flow should always be positive from clean areas to less clean areas”. Concept-wise, I’m down with that (I’m not loving the use of “always” in this type of context—how long is always, or maybe it should be how frequently is always, but I digress), but where in the Joint Commission standard does it say that, apart from the all-encompassing appropriate provision of pressure relationships, etc. That “should” really undercuts the whole statement. Is this something we “must” do within the context of the standard or are we trying to leverage behaviors by acting like something is deficient when it is not necessarily the case?

Another “should” that came up recently involved the results of a vendor’s testing of the medical gas system. Now you and I both know that our vendors are not always the most efficient when it comes to providing written documentation of their activities. In this particular instance, the testing had been done in June, and the report had been delivered in August, mere moments before the survey started. Within the report, there were some issues with master alarms that required repair work—repair work that had not yet been completed. Now, as near as I can tell, each organization still gets to prioritize the expenditure of resources, etc., presumably based on some sort of risk assessment (that’s a “should” for all you folks keeping track), but the finding in question ends with a resounding statement that the facility “should” have required the vendor to provide a deficiency report at the time of the inspection. Conceptually, you’ll get no argument from me, and as consultative advice I will tell you that it is a positively stupendous idea to know what problems are out there before your testing vendors leave the premises. Remember, you “own” the fixes as soon as they are identified, and if there are delays, you’d best have a pretty gosh-darn good reason for it. In fact, I would have to consider that strategy as a best practice in managing maintenance and testing activities, but where does it say that in the standards?