Home » Editorials » Currently Reading:

Maybe Hospital IT Should Embrace a Non-Punitive Culture

February 13, 2008 Editorials 2 Comments

Inside Healthcare Computing has graciously agreed to make previous Mr. HIStalk editorials available from its newsletter as a weekly “Best Of” series for HIStalk. This editorial originally appeared in the newsletter in June 2006. Inside Healthcare Computing subscribers receive a new editorial every week in their Electronic Update.

Hospitals realized several years ago that medication errors are rarely the simple screw-up of a single nurse, pharmacist, or physician. They occur because an organizational system of assumptions, processes, and communication fails, the so-called “Swiss cheese effect” whereby a number of usually self-correcting practices sometime line up unfavorably like the holes in Swiss cheese. That alignment of individually unusual circumstances causes errors.

Knowing that’s the case, it doesn’t make sense to fire someone involved in a medication error. The underlying system is still broken. Disciplinary action also discourages others from reporting their own mistakes and near-misses, thereby depriving the organization and industry of the opportunity to learn from them.

Maybe we should think that way in hospital IT. We’re still stuck in the old “fire everyone involved” mindset when projects fail, which is disturbingly often. Software implementation is simply business change with a technology component. Therefore, when a project deviates from expectations, it doesn’t make sense to have a knee-jerk firing of the IT project manager, the CIO, or even the vendor. Supporting cast changes won’t improve the flawed underlying system that allowed them to fail.

A non-punitive IT culture would acknowledge that all executives, not just those in IT, bear responsibility for the success of business changes involving technology. It’s their job to support process change, contribute resources, and participate in project decisions. The kickoff meeting doesn’t happen until they’re on board and they don’t get to go incognito when the project blows up and the CIO lynch party is being formed.

Some of the worst CIO and vendor behavior involves rationalization and ass-covering once projects have failed spectacularly, much like the nurse who kills a patient through a mistake not entirely under his or her control. We’ve built incentives for people to keep quiet, to dodge blame, to avoid risk, and to criticize others. Eventually everyone gets tired of the finger-pointing, so the only remaining task is to ban mention of the project in polite conversation, at least until the same mistakes doom the next one.

When it comes to IT projects, hospitals are more like surgeons than internists. Cutting is the cure: the vendor, employee, or consultant must be removed and publicly blamed to provide closure. Everyone must believe that lessons have been learned and the chances for future success increased. To admit otherwise would require a lot more self-analysis and work, and after all, Men of Action believe in their keen ability to simplify complex problems and fix them with quick, skilled incisions.

We make a lot of mistakes, many of them eminently preventable if we could just learn collectively. Most of them are quietly buried away, often taking a few careers or contracts with them.

Hospitals are mostly non-profit and non-competitive. Maybe we could improve our odds of IT success by sharing our misses and near-misses just like we do for medication errors.

This editorial is copyright-protected by Algonquin Professional Publishing, LLC., publishers of Inside Healthcare Computing. Please do not copy, forward, or reproduce this material without prior permission. To obtain permission or for more information about Inside Healthcare Computing’s reprint policy, please contact the Customer Service Department at 877-690-1871 or go to http://insidehealth.com/ihcwebsite/reprints.html.

Mr. HIStalk’s editorials appear each Thursday morning in the subscribers-only version of Inside Healthcare Computing’s E-News Update. To subscribe, please go to: https://insidehealth.com/ihcwebsite/subscribe.html or call 877-690-1871.

View/Print Text Only View/Print Text Only

HIStalk Featured Sponsors


Currently there are "2 comments" on this Article:

  1. Typically I don’t comment on this blog site and I know eveyone has there perspective on how to solve an issue regarding Medication Errors, Vendor System Failures, Patient Billing, etc. etc.), however I truly believe once leaders (CXO’s) step up and become servant leaders, become part of the solution vs part of the problem, acknowledge problems vs saying there is no problem then we will finally get somewhere not only in the healthcare industry but the world. CXO’s, Board’s, Wall Street etc. its not about them it’s about doing waht is right no matter if you have to step back and say we made a mistake, what do we need to do to FIX the problem. I am all about due dilegence and risk mitigation, I have been both in high level high-level IT roles, consulting, and the vendor software industry and always been honest with CX’s about situations that I see or have seen in the industry or their facility. The CXO’s that say they don’t have a problem, can’t afford a solution to help mitigate a problem, watch what typically happens over the next 18 months. Humans make mistakes (and always will), however we can and should do what we must do. Be honest and open, don’t point the blame be part of the solution.

  2. Hey, I’m prejudiced by what I sell, but the article underscores the need for robust project and project portfolio management methodology and tools.

    Specifically, supporting tools must be easy to use and easy to roll-out, once you go outside of the core PM group. Traditional ePM tools that are not simple to use for casual users and non-core IT resources will just contribute to project failure.

    Without having some good IT governance structures in place, some balanced scoreing on proposed projects, and some portfolio management methodology in place, you’re going to be going down the wrong path more often than not, and likely not able to tell when you start to go off the rails.


    Software Salesguy 1972

Subscribe to Updates



Text Ads

Report News and Rumors

No title

Anonymous online form
Rumor line: 801.HIT.NEWS



Founding Sponsors


Platinum Sponsors































































Gold Sponsors















Reader Comments

  • Melissa: I have enjoyed your posts every month, and have followed you through your life changes as well as mine. Thank you for a...
  • Edward Marx: That would make for a good post! Let me think on it and look for me on LinkedIn....
  • Rebecca: Thank you, Ed. I always looked forward to your posts - they were a validation to me that you don't have to have to be a...
  • Lee David Milligan: Rob: thanks for the comment. Agree with your point re: unique expectations and complexity....
  • Shelly: Thank you Ed for taking the time to invest in the industry as you have done - with this blog as a sounding board for CIO...
  • Appreciatve: Thanks,, Ed. This was a very nice piece, and telling of what you cherish most. There is one topic that I am not cert...
  • Rob Price: Excellent information and quite consistent with my experiences since 1999 working with three different software companie...
  • Cosmos: Thank you for the interesting article. FYI - the terms "Severe Sepsis" and "Septicemia" are no longer in common use, ...
  • Joel: Thanks for sharing for all of these years. I have appreciated the insight and will miss it!...
  • Ann Farrell: Janet - insightful as always. I remain a fan. Concerned staffing levels "at max" knowing early pt. surveillance syst...

Sponsor Quick Links