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 case for PAA

PAA stands for Patient Admission App. In a nutshell it is a platform in which the hospital can communicate with its patients and their relatives before, during and after their stay in  the hospital. A patient's encounter with a hospital is often a traumatic event to both the patient and his family. A lack of  proper communication between the parties can have major implications on the hospital efficiency and the patient's experience which research shows has a critical impact on the quality of care. From red tape to red carpet  A PAA should accompany the patient throughout his journey by keeping him informed and engaged. This starts prior to the actual admission when the patient feels scared, anxious and confused. A PAA should provide the patient with all the information related to his upcoming treatment. This can include treatment reminders such as not to eat x hours before a planned anesthesia, orientation map, etc. It should also handle in...

Hospital CXO - A new well deserve seat at the executive table

I once asked the CEO of a large hospital what will be the main KPI to measure how well the hospital is doing. The CEO immediate response was that the best indicator would be how satisfy the patients are. In a stressful and overloaded environment such as a hospital, it is easy to focus on the disease and forget about the patient. A chief experience officers (CXO), or other similar titled leaders, is a new member in a hospital C-suite. The role of a CXOs have gained scope and respect in the C-suite as studies show how experience affects all aspects of care. There is a growing body of evidence supporting that the association between better patient experience and health care quality. For example, a study found that a higher CMS star rating was associated with lower patient mortality and readmission's.  One of the drivers accelerating the adoption was the US government decision to start mandate measuring patient’s perception of their care and tied reimbursement to those scores. Beyond t...