Skip to main content

Why hospital IT managers are a block for innovation




We all have this image in our head of an IT guy who surrounds himself with technology, obsessively try out every new gadget, and keep mentioning all kinds of weird acronyms that distance him from society.

When I sat the other day in front of the IT manager of a big hospital while he was chewing a gum, I can't help thinking how far is that image of the IT guy from the person who was sitting in front of me. 

In contrast to that image in our head the IT manager main concern is keeping the lights on. An IT manager who experienced an unscheduled downtime in one of the hospital mission critical systems, like many of them did, surely got his priorities straight after that event. The worst nightmare of an IT manager is to stand first thing in the morning in front of the CEO and to explain why the hospital network was hacked during the night. With such heavy responsibility laying on their heads innovation does not even get into the top three in their priority list.

That is all completely fine and understood. What is problematic however is that often the IT department get to be in charge of innovation just because innovative products tend to deal with technology, and the IT manager is the first stop to "pass" for introducing new technology to the hospital.

For the IT manager an innovative product is another product that he will have to maintain. His incentive plan does not include rewards for introducing new technologies and so as most people he will not be keen on taking additional work without a reward. Innovative products tend to use cutting edge infrastructure which requires the IT to get their heads around and learn how to maintain, in paradox the less innovative the product is the better it is for the IT department.

That misconception between the two images is what leads all hospital workers, from clinicians to executives, to turn to the IT manager when being introduced to an innovative product. Hospital IT managers usually do not have the skills to fully grasp the value of the systems they are asked to evaluate, and so as a result they tend to shift the discussion to subjects from their domain, like security, privacy, redundancy, authentication, interoperability, compliance, and other boring stuff that the hi-tech industry has found many ways to solve.
Too often the voice of the IT manager is too vocal in the conversation and clinicians and even C-level executives are reluctant to confront his or her opinion. 

A healthy organization must know to balance all voices and reward the individuals who prompt innovation and progress. Skepticism should be challenged and lack of motivation to take additional responsibilities is not a quality to be proud of.

But if you want a more practical advice it is this: instead of being the first, keep the IT manager the last person you consult with about introducing innovation. After all, you can't let the zoo keeper lead a herd of running horses...

Comments

Popular posts from this blog

Clinical data warehouses: Sometimes it's worth being lazy

If you are a health organization you probably have or thinking of having a clinical data warehouse. A Clinical Data Warehouse (CDW), sometimes called Clinical Data Repository (CDR), is a database that consolidates data from a variety of clinical sources to form a unified view of a the data for various purposes. Typical data types which are often found within a CDW include: clinical laboratory test results, vital signs, patient demographics, administered meds, hospital admissions, ICD-9 codes and more. Developing and sustaining an effective CDW operations unit is a substantial effort and long-term commitment. The main challenge in designing a CDW is defining its scope and the use cases it should support. In theory a CDW can serve as a basis for reporting, studying and planning. The use case that is often mentioned in relate to CDW is supporting clinical trials. This would allow for researchers to have all the information from a study in one place as well as let other researchers benefit

The big battle: Best of breed vs One stop shop

The world of economics has decided on this debate a long time ago: monopolies are bad, diversity is good. No matter what a monopoly promises, you can rest assure that over time the lack of competition will cause prices to go up and quality to go down. When it comes to healthcare IT, however, there is one unique factor that flips the coin – interoperability. Despite various attempts the healthcare industry has yet to solve the interoperability challenge in a satisfactory manner which will enable a full continuum of care across different health information systems within a health delivery organization. Taking a common scenario of prescribing a medication order in theatres using a surgical system to be later administered in a ward requires significant investment to achieve, even using the modern Fast Health Interoperability Resource (FHIR) protocol. The investment required to streamline the data flow across systems raise in an exponential order with every new system that is thrown to t

Are we ready for a Cloud First hospital?

I will start this article by defining what I mean by the term a Cloud First hospital. The term cloud has been a buzz word in the past decade which led many organizations to declare their support for the cloud, sometime without understanding its true meaning. For the purpose of this article I am proposing a simple test to decide whether an organization is a cloud first or not. If you are software vendor you must have an IT department which directly in charge of the system up-time at your clients sites. If you are a health organization then you should never have visited the data center where your data resides. A Cloud First hospital is one which more than 50% of its systems reside in data center that none of its staff members ever visited or not even sure where they are. According to a recent survey by Datica, in the US only 17.7 percent of the respondents say they work with healthcare organizations that have more than 50% of the existing software infrastructure remotely hosted or