You have just called for a significant expansion of use of healthcare information technology (HIT) by hospitals and physicians as part of your economic rescue plan. I strongly applaud such an incentive.
As in other industries using information technology, HIT such as electronic medical records, physician order entry, and clinical decision support systems will play a leading role in healthcare transformation. Without such technology, the healthcare system is far too complex to be managed well.
And managed well it must become. However, there is a major caveat regarding such a national initiative.
Mr. Obama, I offer the following suggestions from the perspective of my medical specialty area, Biomedical Informatics, the formal study of computer applications in biomedicine [1]:
HIT is an experiment. It is, as yet, unproven on a large scale. There have been many warning signs that it is an experiment that could go awry. HIT can be used to assist in healthcare transformation, but not if the HIT itself is defective or mismanaged.
Unfortunately, the problems with HIT are indeed considerable.
Use of HIT after 30-plus years of effort and billions of dollars spent remains limited. As per the 2008 statistics in the New England Journal of Medicine, just four percent of physicians in the U.S. reported having an extensive, fully functional electronic-records system, and just thirteen percent reported having a basic system. Most hospitals are also lacking the technology to any meaningful extent [2].
Clinicians (physicians, nurses and others) are struggling to use awkwardly designed HIT, designed as if for quiet, solitary business offices yet costing millions of dollars per hospital. Hospital boards, executives and department heads are often frustrated by the pushback and resentment they get from their clinicians regarding such HIT.
Too few in the HIT industry, however, ask why this situation exists and what might be done to eradicate these problems.
The healthcare industry and the HIT sector have been reliably tone deaf on these issues, which results in the very low diffusion of HIT. Platitudes, excuses, and blame placed solely on endusers (i.e., the clinicians) are the norm.
Why is this so?
Mr. Obama, I believe that there are two major ideological camps in what I call the “HIT Ecosystem” [3].
On one side are the “HIT industrialists" - the "We're Right" Wing.
The HIT industrialists, including developers, vendors, consultants, and IT personnel in hospitals view HIT simply as another variety of business computing technology, such as finance and accounting systems meant for use in calm, solitary office environments.
They cling to their “religion” of management information systems approaches and methods for design, implementation and evolution of business IT, believing these approaches as valid for the back office as for the pediatric clinic, emergency department or intensive care unit.
Nothing could be further from the truth. This is a leap of logic of absurdist proportions that would be comical if its implications were not so serious.
It is as if the industrialists believe one should be able to travel to the moon in a hot air balloon. The moon is "up" and balloons go "up", therefore, why not? All that's required are the right "processes" -- with which the Acme Hot Air Balloon Co. executives can accomplish anything -- and ignoring those pessimistic scientists, engineers and other experts who speak of vacuum of space and radiation and all those esoteric "gotchas" that are bad for business! (See my Powerpoint presentation to the IEEE Medical Technology Policy Committee on this issue at this link.)
To the Moon in a Hot Air Balloon!The industrialists forget -- or never knew -- that a thousand generic workers following the finest of process will always be outperformed by a few people who actually know what they're doing.
The HIT industrialists usually refuse to accept more progressive, “activist” approaches to these issues that recognize that clinical computing and business computing are not different sides of the same coin, but are in fact distinct subspecialty areas of computing requiring distinct and specialized approaches.
The industrialists would also have us believe that the HIT “economy” is fundamentally sound and that we should proceed with business as usual.
I shall refer to the industrialists as the “We’re Right” Wing of the HIT Ecosystem.
I use this title based on their often reactionary and procrustean views towards HIT. The adjective “procrustean”, derived from certain practices of Procrustes, a figure from Greek mythology, is defined as “designed to produce strict conformity by ruthless or arbitrary means” [4]. These views, that the “old” ways of designing and implementing IT are the “right” and in fact the only way to proceed, are strongly held. I believe they are, however, being made obsolete in an age of unparalleled IT innovation.
Largely as a result of the “We’re Right” wing’s views, costly, morale damaging (especially to clinicians) HIT difficulties and failures are commonplace, and the benefits of which this technology is capable are not being realized.
Clinicians must toil with ill conceived or badly designed IT in their already harried ten to fifteen minute patient visits, and the industry is largely deaf to their misery. It’s bad for the IT business.
On the other hand, knowledgeable clinician-informaticists in the aforementioned field of Biomedical Informatics, true computer scientists (as distinguished from management information systems or MIS personnel), sociologists studying IT, and other related specialists, some working for more than thirty years, have found better ways to develop and manage HIT than has the traditional IT industry, which itself has a dismal record of project cost overruns, failures, and system abandonment in fields far less complex than clinical medicine.
Sadly, the specialists are often pushed to the margins of the HIT Ecosystem. I will call this “we actually know what we’re doing” group of specialists the “Left Out” Wing.
It is particularly ironic that the Biomedical Informatics group is marginalized, in that it was that group of pioneers who experimented in the early days of computing and essentially invented the foundational elements for today's health IT. Even then, the pioneers noted issues in HIT that are unchanged many decades later. For example, as I note at my academic website on HIT difficulties:
As far back as 1969, EMR and Medical Informatics pioneer Donald A. B. Lindberg, M.D., now Director of the U.S. National Library of Medicine at NIH, made the following observation.
He wrote that "computer engineering experts per se have virtually no idea of the real problems of medical or even hospital practice, and furthermore have consistently underestimated the complexity of the problems…in no cases can [building appropriate clinical information systems] be done, simply because they have not been defined with the physician as the continuing major contributor and user of the information" (Lindberg DAB: Computer Failures and Successes, Southern Medical Bulletin 1969;57:18-21).
With regard to Biomedical Informatics specifically, the U.S. National Institutes of Health (NIH) has spent hundreds of millions of dollars over the past twenty years to expand Biomedical Informatics through funding of rigorous training at many of this nation’s major universities, as have many other educational organizations on their own funds.
Yet, the lessons of Biomedical Informatics and the other specialist areas have yet to diffuse into the HIT industry and effect needed “change” in that sector. When informatics experts bring their activism into the equation, they are often not taken seriously or placed into “advisory roles” (that is, away from true leadership roles) in most healthcare organizations.
Experts in the Left Out wing offer sage advice. “It is unwise spending millions on Electronic Medical Records without investing thousands in Biomedical Informatics expertise”, these specialized personnel say [5].
Yet there are many “unwise” organizations within healthcare. Examples abound of healthcare organizations not just passively but actively and almost absurdly rejecting the presence or counsel of the specialists as if the organizations are run by intellectually challenged leadership (does this sound familiar regarding other industries in the news recently? See example here), and I believe there is great value in studying the results of this lack of insight [6]. However, others do not.
The following is meant not to be humorous but to reflect a dangerous reality:
The Industrialist "We're Right" Wing's Simplistic and Overoptimistic View of Healthcare Environments
The Informaticist "Left Out" Wing's Reality-Based View of Healthcare EnvironmentsIf you think the above is exaggerated, Mr. Obama, read my account "Serious Clinical Computing Problems in the Worst of Places: An ICU" at this link regarding an actual situation some years ago in an ICU at the largest healthcare provider in Mr. Biden's home state, and the cavalier attitudes taken by its executive administration over endangerment of ICU patients via computer.
Imagine for a moment the horror of being unable to intervene due to administration's priorities of "everyone getting along" rather than the absolute protection of patients. Yet this is not an uncommon scenario in the IT backwater of hospitals.
This state of affairs has significant real world implications.
Even now I hear of ill conceived and poorly implemented ICU systems that endanger premature infants, EMR's that interfere with adult patient care and clinician mental focus in offices and clinics, order entry systems that encourage rather than prevent medication errors, and systems that impair hospital operations to the point of putting seriouly ill patients at risk of being misdiagnosed and intermittently losing patient information.
First and foremost among the “We’re Right” wing is an aversion to detailed investigation of IT failure, as should be performed, NTSB style. However, doing so might be bad for business. In the industrialist culture of IT, it’s bad to air the dirty laundry.
As a result, our government has been seduced by the promise, the potential, the Siren Song if you will of HIT, and shielded from information on its true challenges, difficulties, downsides and failures. An "irrational exuberance", a Syndrome of Inappropriate and Uninformed Overconfidence in Computers prevails in healthcare (my webcast on irrational exuberance in HIT can be heard at online journal "Government Health IT" here).
As a result of this seduction and censorship of the unpleasant realities, seasoned legislators such as Sen. Max Baucus are led to make claims such as:
“Everybody talks about health IT. We all know we need it. It hasn't happened. Why? Partly because we're America. We're not a single-payer system like the UK, which can say, you hospitals, you have to put this in because we're paying your bills” [7].
This implies that Sen. Baucus believes the UK should have an easy time of it in their multi-billion dollar national HIT program, NHS Connecting for Health.
Yet this has proven to be profoundly untrue:
The future of the NHS's £12.7bn computer programme was in doubt last night after its managers acknowledged further delays in introducing a system for the electronic storage and transmission of patients' records.
Connecting for Health, the NHS agency responsible for the world's biggest civil IT project, said it was no longer possible to give a date when hospitals in England will start using the sophisticated software that is required to keep track of patients' medical files.
Christine Connelly, the Department of Health's recently appointed head of informatics, is understood to be reviewing whether the programme is a cost-effective way of improving the quality and safety of patient care [8].
I should add that the “appointed head of informatics” has no apparent formal Biomedical Informatics background, but had been CIO of candy/beverage company Cadbury Schweppes, a puzzling background to lead a national HIT initiative.
If health IT is easier in the UK due to their single payer system, then God help us here in the United States.
Lessons from HIT difficulties and failures are rarely spoken of and often hidden. Detailed investigations down to fine grained causes that are routinely performed in other areas of technology failure – airlines, trains, etc. – are not done when health IT fails. This is due to the industrialist biases.
Yet, as per the European Federation for Medical Informatics (EFMI) Working Group for Assessment of Health Information Systems, you should be aware that bad HIT can kill [9].
Further, the repeated advice of the “We’re Right” wing of the HIT Ecosystem is that the cause of failure, besides those darn clinicians, is neglecting to adhere to obvious and simplistic “best practices” typical for business IT. These practices largely involve common sense, such as involving end users at all stages of development, focusing on the value added rather than the technology, and other “sterile technique is needed in surgery” advice.
Unfortunately, even in non-healthcare IT, technology projects have a bad reputation for going over budget and schedule, not realizing expectations, for providing poor return on investment, or in failing outright and being de-installed. Surveys and reports on the acceptability of new IT systems seem to highlight constantly the same problems and probable causes of failure yet businesses, large and small, continue to make mistakes when attempting to improve information systems and often invest in inappropriate or unworkable changes without proper consideration of the likely risks [10].
In HIT, these problems are perhaps worse, with the added complexity of the unpredictable, poorly bounded environment of healthcare.
Enter Biomedical Informatics, computer science, social science and the other true experts. Advice often heard from this “Left Out” wing, but largely dismissed by the industrialists, include:
- Simplistic “best practices” of business IT are often inadequate for the complexities of IT in clinical settings, and even these are often not followed in healthcare IT.
- CIO’s are not unaware of, nor do they go out of their way to pass up, best practices. The reasons that commonsense best practices, e.g., strong clinician involvement and empowerment in health IT projects are not universally employed is a sociological issue, and requires investigation.
- The most important "best practice" of all is often not followed: the practice of knowing what you do not know, identifying those who do know, becoming familiar with their work, and utilizing them and their knowledge maximally. Most hospital CIO's are unaware or have a very narrow and faulty view of Biomedical Informatics. Considering the impact of the CIO role in healthcare, and the ease of obtaining such information via the web, this amounts to fundamental negligence.
- There are highly specialized and nuanced “best practices” arising from decades of Biomedical Informatics, IT-sociology and other research of which traditional IT personnel are generally unaware, and therefore do not use. This is harmful to the healthcare enterprise.
- The reasons for “worst practices” seen of many stakeholders – such as active and passive aggressive behaviors that occurs for many reasons and negate any “best practices” - need to also become deeply understood, not treated in a cavalier manner or ignored. These behaviors reflect hidden, critical human issues of which nobody speaks, and it is these unspoken issues that can cause HIT to fail.
- Continued inattention to HIT ease of use to maximize vendor profits, and issues such as pay for performance formulas based on electronic medical records data, but prepared in a typical corporatized manner unfair to clinicians and harmful to medicine’s core values, will be recognized as such by clinicians. This will lead to increased active and passive aggression against HIT that will cause HIT (even otherwise well designed HIT) to fail.
There are many other points of wisdom contained in a huge body of literature that, in fact, could have helped avoid the major problems within the UK’s national HIT initiative, and that can prevent the same from happening here.
Mr. President, I implore you and your advisers and staff to become personally familiar with these issues. Seek out the advice of Biomedical Informatics experts, computer scientists, those who study social issues in computing, and others. Have your advisers read books such as “Medical Informatics 20/20: Quality and Electronic Health Records through Collaboration, Open Solutions, and Innovation” by the VHA pioneers [11], “Managing Technological Change: Organizational Aspects of Health Informatics” by informatics researchers Lorenzi and Riley [12], and “Understanding And Communicating Social Informatics” by IT social issues innovators Kling, Rosenbaum and Sawyer [13].
Push as strongly for HIT reform as for healthcare reform itself, lest our HIT initiatives suffer the same delays – and the same costly failures – as the UK’s national electronic medical records program.
If this is not done, Mr. President, billions of precious healthcare dollars that might be spent on “IT misadventure” in a time of unprecedented national financial challenges and hardships might simply be better spent on delivery of needed medical services, health insurance and other "safety net" interventions.
HIT in 2009 and beyond, as healthcare itself, is at a crossroads. If we do HIT right, we get rewarded. If we do HIT wrong, then the results shall be deserved.
My takeaway lesson is simply stated: healthcare’s defects cannot be effectively changed or reformed via healthcare IT, if that healthcare IT itself is defective.
Both require change.
Sincerely,
Scot Silverstein, M.D.
References:
[1] “Training the Next Generation of Informaticians - A Report from the American College of Medical Informatics.” J Am Med Inform Assoc. 2004 May–Jun; 11(3):167–172. PDF at this link.
[2] “Electronic Health Records in Ambulatory Care - A National Survey of Physicians.” NEJM 359:50-60.
[3] “Introduction to the Complex Ecosystem of Healthcare IT.” Essay at website “Sociotechnologic Issues in Clinical Computing: Common Examples of Healthcare IT Difficulties.” Scot Silverstein MD, Drexel University, Philadelphia, PA, http://www.ischool.drexel.edu/faculty/ssilverstein/failurecases/?loc=cases&sloc=ecosystem (accessed Nov. 26, 2008).
[4] The American Heritage® Dictionary of the English Language: Fourth Edition, 2000. http://www.bartleby.com/61/85/P0578500.html
[5] Paraphrasing William Hersh, M.D., Professor and Chair, Department of Medical Informatics & Clinical Epidemiology, Oregon Health & Science University, http://www.billhersh.info
[6] “Medical Informatics, Information Technology Leadership, and Clinical IT Success”, Scot Silverstein MD, Drexel University, Philadelphia, PA, http://www.ischool.drexel.edu/faculty/ssilverstein/medinfo.htm (accessed Nov. 26, 2008).
[7] “Health” supplement, Wall Street Journal, Nov. 24, 2008, p. R10
[8] “Bank bailout puts £12.7bn NHS computer project in jeopardy”, John Carvel, The Guardian, Oct. 29, 2008, http://www.guardian.co.uk/society/2008/oct/29/nhs-health (accessed Nov. 26, 2008).
[9] “Bad Health Informatics Can Kill.” European Federation for Medical Informatics (EFMI) Working Group for Assessment of Health Information Systems, http://iig.umit.at/efmi/badinformatics.htm (accessed Nov. 26, 2008).
[10] “Developing a risk estimation model from IT project failure research.” M Bronte-Stewart, Computing and Information Systems, University of Paisley, 2005, 9(3): 8-31. http://cis.paisley.ac.uk/research/journal/V9/V9N3/failure.doc (accessed Nov. 26, 2008).
[11] Medical Informatics 20/20: Quality and Electronic Health Records through Collaboration, Open Solutions, and Innovation. First edition. Goldstein, Groen, Ponkshe & Wine, Jones & Bartlett Publishers, 2007, ISBN-13: 9780763739256
[12] Managing Technological Change: Organizational Aspects of Health Informatics. Second edition. Lorenzi & Riley, Springer-Verlag Publishers, 2004, ISBN: 0387985484
[13] Understanding And Communicating Social Informatics: A Framework For Studying And Teaching The Human Contexts Of Information And Communication Technologies. Information Today Publishers, 2005, ISBN 1573872288.
RSS Feed (xml)