AMIA: Enhancing patient safety and quality of care by improving the usability of EHR systems, but ... no sympathy for victims of bad health IT?

A panel of experts from the American Medical Informatics Association have written a paper "Enhancing patient safety and quality of care by improving the usability of electronic health record systems: recommendations from AMIA."

The paper is publicly available at this link in PDF.

The authors are  Blackford Middleton (Harvard Medical School),  Meryl Bloomrosen (AMIA),  Mark A Dente (GE Healthare IT),  Bill Hashmat (CureMD Corp.), Ross Koppel (Dept. of Socology, Univ, of Pennsylvania), J Marc Overhage (Siemens Health Services), Thomas H Payne (U. Washington IT Services),  S Trent Rosenbloom (Vanderbilt Informatics), Charlotte Weaver (Gentiva Health Services) and Jiajie Zhang (University of Texas Health Science Center at Houston).

The paper states what has been obvious to this author - and many others - for many years:

ABSTRACT:  In response to mounting evidence that use of electronic medical record systems may cause unintended consequences, and even patient harm, the AMIA Board of Directors convened a Task Force on Usability to examine evidence from the literature and make recommendations. This task force was composed of representatives from both academic settings and vendors of electronic health record (EHR) systems. After a careful review of the literature and of vendor experiences with EHR design and implementation, the task force developed 10 recommendations in four areas: (1) human factors health information technology (IT) research, (2) health IT policy, (3) industry recommendations, and (4) recommendations for the clinician end-user of EHR software. These AMIA recommendations are intended to stimulate informed debate, provide a plan to increase understanding of the impact of usability on the effective use of health IT, and lead to safer and higher quality care with the adoption of useful and usable EHR systems.

The paper is a respectable start at acknowledgement of the issues ... albeit years late.

That said:

I noted some typical language in the article characteristic of the reluctance of the health IT industry and its friends to directly confront these issues.  I wrote a letter to the authors that, as I indicate below, not unexpectedly went unanswered except for one individual -- not even a physician -- who's gone out on a limb professionally in the interest of patient's rights, and as a health IT "iconoclast" (i.e., patient advocate) suffered for doing so (link).  The lack of a response to the letter is itself representative, in my opinion, of a pathology that renders more rights to the healthcare computer and its makers than patients.   More on this below.

First, I note I am rarely if ever cited by the academics.  They are not prohibited from doing so.  I've probably been writing on these issues -- poorly done health IT, improper leadership, the turmoil created, etc., publicly for longer than anyone else in the domain.

I also note that the paper is somewhat in the form of an analytical debate.  Analytical debates are relatively ineffective in this domain.  They are like popcorn thrust against a battleship.  The paper, also, appearing as it does in a relatively obscure specialty journal (Journal of the American Medical Informatics Association), will probably get more exposure from this blog post than the entire readership of that journal.  The authors need to be relating these issues in forums that are widely read by citizens and government, not in dusty academic journals - that is, assuming they want the messages to widely diffuse.

In my review of the article, I note the following:

... In an Agency for Healthcare Research and Quality (AHRQ) workshop on usability in health IT in July 2010, all eight participating vendors agreed that usability was important and many suggested it was a competitive differentiator, although some considered that usability was in the eye of the beholder and that the discipline of usability evaluation was an imperfect science, with results that were not useful.

A paper like this should have clearly repudiated antiquated viewpoints like that, not merely made note of them.   Not taking a stand is a sign of weakness...or sympathy.

As a matter of fact, if leaders such as this had paid attention to the 'iconoclasts' and their 'anecdotes', my own mother might not have gone through horrible suffering and death, with me as sad witness as I related to them in my letter below.

... End-users of EHR systems are ultimately accountable for their safe and effective use, like any tool in clinical care.

I see a linguistic sleight of hand via use the word "tool" to describe HIT and trying to blend or homogenize this apparatus with other "tools" in clinical care.  The HIT "tool" is unlike any other since no transaction of care can occur without it going through this device, and as such, all care is totally dependent on it.  Further, unlike pharma and medical devices, this "tool" is unvetted and unregulated but its use forced upon many users.

... [AMIA] subcommittees reviewed the literature on usability in health IT, current related activities underway at various US Federal agencies, lessons learned regarding usability and human factors in other industries, and current federally funded research activities.

Did they speak with the source of the most candid information?  The plaintiff's and defendant's Bars?

Need I even ask that question?

... Recent reports describe the safe and effective use of EHR as a property resulting from the careful integration of multiple factors in a broad sociotechnical framework

This is not merely 'recent' news.  The field of Social Informatics (link), that has studied IT in its social contexts for decades now, has offered observations on the importance of considering multiple factors in a broad sociotechnical framework.   The authors all know this - or should know this, or should have made it their business to know this.  The statement sounds somewhat protective of the HIT and hospital industries for their longstanding negligence towards those issues.

... User error may result in untoward outcomes and unintended negative consequences. These may also occur as a result of poor usability, and may also be an emergent property only demonstrated after system implementation or widespread use.

I note the use of the term "user error" and lack of the term "use error" with significant disdain.  As I wrote here regarding the views of a HIT industry exexcutive holding the mystical "American Medical Informatics Certification for Health Information Technology",  NIST itself now defines "use error" (as opposed to "user error") as follows:

“Use error” is a term used very specifically by NIST to refer to user interface designs that will engender users to make errors of commission or omission. It is true that users do make errors, but many errors are due not to user error per se but due to designs that are flawed, e.g., poorly written messaging, misuse of color-coding conventions, omission of information, etc. From "NISTIR 7804: Technical Evaluation, Testing and Validation of the Usability of Electronic Health Records." It is available at http://www.nist.gov/healthcare/usability/upload/Draft_EUP_09_28_11.pdf (PDF).

In the article, indefinites were exchanged with what should have been stronger, declarative statements, and vice versa:

User error ... may also represent a potential health IT-related error yet to happen.

I most decidedly wish they'd stop this "may" verbiage in policy papers like this.

... Anecdotal reports suggest that these application differences [where clinicians use more than one commercial EHR system] result in an increased training burden for EHR users.

"Anecdotal"?  How about "obvious to a third grader?" 

"Anecdotal" in academic papers often is a term of derision for inconvenient truths such as reports of health IT problems.  Its use often reflects a need for authors using the term (per a senior clinician from Victoria, Australia on the 'anecdotes' issue, link) "to attend revision courses in research methodology and risk management."

... Some suggest that the expected gains sought with the adoption of EHR are not yet realized.

"Some"?  How about "credible experts?"  "Suggest?"  They merely hint at it?  How about "opine?"
 

... The design of software applications requires both technical expertise and the ability to completely understand the user’s goal, the user’s workflow, and the socio-technical context of the intent

In the meantime, AMIA has been promoting national rollout of a technology where, most often, the latter does not apply.

To ... transform our healthcare delivery system ... clinicians need to use usable, efficient health IT that enhances patient safety and the quality of care.

This is the typical hyperenthusiast mantra.  Where's the proof?  And, transform into what, exactly?  Vague rhetoric like this in allegedly scientific papers is most unwelcome.

Some experts suggest that improving the usability of EHR may be critical to the continued successful diffusion of the technology.

More weak talk.  Why not come right out and say "Credible experts opine that ...."?

... While some EHR vendors have adopted user-centered design when developing health information technologies, the practice is not universal and may be difficult to apply to legacy systems.

From the patient advocacy perspective, that's their problem...it's a risk of being in this business.  Patients should not be expected to be used as experimental subjects while IT sellers figure out what other industry sectors have long mastered.   Further, they should be held accountable for failures that result in harm.  Another risk of doing business in this sector that clinicians have long learned to live with...

... Some believe it is difficult or impossible to reliably compare one product with another on the basis of usability given the challenges in assessment of products as implemented.

Nothing is "impossible" and again, if it's "difficult", that's the industry's problem.  There is risk of being in the business of medicine or medical facilitation; nobody promised a rose garden, and a rose garden should not be expected.

... Many effects of health IT can be considered to be ‘emergent’ or only discovered after monitoring a system in use

One might ask,  where's the industry and AMIA been regading postmarket surveillance (common in other health sectors) for the past several decades?

... AMIA believes it is now critical to coordinate and accelerate the numerous efforts underway focusing on the issue of EHR usability.

Only "now?"

... Establish an adverse event reporting system for health IT and voluntary health IT event reporting

No, no, no ...voluntary reporting doesn't work.  Even mandatory reporting is flawed, but it's better than voluntary.

I am invariably disappointed by recommendations like this.  I've observed repeatedly, for example, that "volunatary reporting" of EHR problems already exists - in the form of the FDA MAUDE database - and most HIT sellers' reports are absent.  See my posts on MAUDE here, here and here.  (Also, the only one that seems to report may have ulterior motives, i.e., restraint of trade.)

... A voluntary reporting process could leverage the AHRQ patient safety organizations (PSO) ... This work should be sponsored by the AHRQ.

These folks clearly don't want any teeth in this.  AHRQ is a research-oriented government branch, not a regulator, nor does it have regulatory expertise.

AMIA recommends:

Research and promote best practices for safe implementation of EHR

In 2013 this is valuable information in the same sense that advice to use sterile technique during neurosurgery is valuable.

"Promoting best practices" has been done for decades.  Not mentioned is avoiding worst practices.   I've long written these are not the same thing, as toleration of the inappropriate leadership by health IT amateurs (a term I use in the same sense that I am a Radio Amateur, not a telecommunications professional), politics, empire-building and other dysfunction that goes on in health IT endeavors negates laundry lists of "best practices."

What is required is to research and abolish worst practices, including the culture and dynamics of the 'health IT-industrial complex.'  I made this point in my very first website in 1998.  It appears the authors don't get it and/or won't admit to the dysfunction that goes on in health IT projects.
 

... The adoption of useful and usable EHR will lead to safer and higher quality care, and a better return on investment for institutions that adopt them.

"Will?"  With respect to my observation above about the paper's prominent misuse of indefinites vs. stronger declarative terms, the word "may" would have been the appropriate term here.  As I wrote about similar statements from ONC in the NEJM in my 2010 post "Science or Politics? The New England Journal and The 'Meaningful Use' Regulation for Electronic Health Records", I'm quite disappointed seeing speculation and PR presented as fact from alleged scientists and scientific organizations.

Finally, I wrote the following email letter to the authors, to which (except for Ross Koppel) I received no reply.  While Dr. Koppel (a PhD) graciously expressed sympathy for my me and mother, the others (many MD's) were silent.

Perhaps the silence is the best indicator of their concern for the rights of computers and HIT merchants relative to the rights of people:

Mon, Jan 28, 2013 at 1:12 PM

Dear authors,

I've reviewed the new paper "Enhancing patient safety and quality of care by improving the usability of electronic health record systems: recommendations from AMIA" and wanted to express thanks for it.

It's a good start.  Late, but a good start at returning the health IT domain to credibility and evidence-based practice.

It's too bad it didn't come out years earlier.  Perhaps my mother would not have gone through a year of horrible suffering and death, with me as sad witness, due to the toxic effects of bad health IT. 

Perhaps you should hear how horrible it was to hear my mother in an extended agitated delirium; to hear her cry hysterically later on when the rehab people told her that her weight was 95 pounds; to have to make her a "no code" and put her on hospice-care protocols, and then to have watched her aspirate a sleeping pill when she was agitated, and die several days later of aspiration pneumonia and sepsis ... in the living room of my home ... and then watch the Hearse take her away from my driveway...as a result of bad health IT.

I will be writing more thoughts on your article at the Healthcare Renewal blog, of course, but wanted to raise three issues:

1.  The use of "may" and "will" is reversed, and conflating the term "anecdote" with risk management-relevant case reports. 

• They may also represent a potential health IT-related error yet to happen.  --->  They likely represent a potential health IT-related error yet to happen

• Anecdotal reports suggest that these application differences result in an increased training burden for EHR users.  ---> Credible reports indicate...

• Some suggest that the expected gains sought with the adoption of EHR are not yet realized. ---> Credible experts opine ....

• Some experts suggest that improving the usability of EHR may be critical to the continued successful diffusion of the technology. --->  "Credible experts opine that ..."

• The adoption of useful and usable EHR will lead to safer and higher quality care, and a better return on investment for institutions that adopt them. ---> The adoption of useful and usable EHR may lead to safer and higher quality care

You really need to show more clarity ... and guts ... in papers like this, and drop the faux academic weasel words.

2.  You neglected to speak to the best source for information on EHR-related harms, evidence spoliation, etc... med mal attorneys.

3.  You also neglected to speak to, or cite, the writings of a Medical Informaticist on bad health IT now going back 15 years - and whose mother was injured and died as a result of the issues you write about - me.  In fact I am rarely cited or mentioned by anyone with industry interests.

An apparent contempt for 'whistleblowers' such as myself makes me wonder ... what kind of people are the leaders of health IT, exactly? 

Do they value computer's rights over patients'?

It is not at all clear to me which has been the primary motivator of many of the health IT leaders.

I think the rights which I value are quite clear.

Sincerely,

Scot Silverstein

I neglected to mention the horror of seeing my mother put in a Body Bag before being taken to the Hearse in my driveway.

-- SS

ONC's Christmas Confessional on Health IT Safety: "HIT Patient Safety Action & Surveillance Plan for Public Comment"

This time of year is certainly appropriate for a confessional on the health IT industry and hyperenthusiasts' sins.

In the first report I've seen that seems genuinely imbued with a  basic level of recognition of social responsibility incurred by conducting the grand human subjects experiment known as national health IT, ONC has issued a Dec. 21, 2012 report "Health Information Technology Patient Safety Action & Surveillance Plan for Public Comment." It is available at this link in PDF.

Statements are made that have appeared repeatedly since 2004 at this blog, and my health IT difficulties site that went online years before this blog (1998 to be exact); it is possible through my early writing and that of like-minded colleagues that we were the origin of most of these memes.  We wrote them with the result of bringing much scorn upon ourselves. After all, "how could health IT possibly not be a panacea?" was the "you are an apostate" attitude I certainly experienced (e.g., as in my Sept. 2012 post "The Dangers of Critical Thinking in A Politicized, Irrational Culture").

Observations echoed in the new ONC report:

• "Just as health IT can create new opportunities to improve patient care and safety, it can also create new potentials for harm."
• Health IT will only fulfill its enormous potential to improve patient safety if the risks associated with its use are identified, if there is a coordinated effort to mitigate those risks, and if it is used to make care safer.
• Because health IT is so tightly integrated into care delivery today, it is difficult to interpret this initial research [such as the PA Patient Safety Authority study  - ed.], which would seem to suggest that health IT is a modest cause of medical errors. However, it is difficult to say whether a medical error is health IT-related. [Not emphasized, as I wrote here, is the issue of risk when, say, tens of thousands of prescriptions are erroneous due to one software bug, a feat impossible with paper - ed.]
• The proper steps to improve the safety of health IT can only be taken if there is better information regarding health IT’s risks, harms, and impact on patient safety.

Suggested steps to be taken include:

• Make it easier for clinicians to report patient safety events and risks using EHR technology.
• Engage health IT developers to embrace their shared responsibility for patient safety and promote reporting of patient safety events and risks. [I am frankly amazed to see this admission.  In the past, that sector excused itself entirely on the basis of the "learned intermediary" doctrine and "hold harmless" clauses; where the clinician is an all-knowing Deity between computer and patient.  I've been writing for years, however, that the computer is now the intermediary between clinician and patient since all care 'transactions' have to traverse what is now an enterprise clinical resource and clinician control system - ed.]
• Provide support to Patient Safety Organizations (PSOs) to identify, aggregate, and analyze health IT safety event and hazard reports.
• Incorporate health IT safety in post-market surveillance of certified EHR technology
• Align CMS health and safety standards with the safety of health IT, and train surveyors.
• Collect data on health IT safety events through the Quality & Safety Review System (QSRS).
• Monitor health IT adverse event reports to the Manufacturer and User Facility Device Experience (MAUDE) database. [I've been promoting the use of MAUDE for just that purpose, and much more regarding documenting and reporting on mission-hostile health IT; see this post - ed.]

These steps are to be taken in order to "Inspire Confidence and Trust in Health IT and Health Information Exchange."

The title of my keynote address to the Health Informatics Society of Australia this summer was, in fact, "Critical Thinking on Building Trusted, Transformative Medical Information:  Improving Health IT as the First Step".

My thoughts on this report:

• It is at least two decades overdue.
• It was produced largely if not solely due to the pressure of the "HIT apostates", finally overcoming industry memes and control of information flows through great perseverance.
• It is indeed a confessional of the sins committed by the health IT industry over those decades.  Creating, implementing and maintaining mission critical software in a safety-cognizant way is not, and was not, a mystery.  It's been done in numerous industries for decades.
• It is still a bit weak in acknowledging the likely magnitude of under-reporting of medical errors, including HIT-related, in the available data, and the issue of risk vs. 'confirmed body counts' as I wrote at my recent post "A Significant Additional Observation on the PA Patient Safety Authority Report -- Risk".
• It is unfortunate that this report did not come from the informatics academic community in the United States, i.e., the American Medical Informatics Association (AMIA).  AMIA's academics have done well in advancing the theoretical aspects of the technologies, and how to create "good health IT" and not "bad health IT."  However, they have largely abrogated their social responsibilities and obligations, including but not limited to those of physicians, in ensuring the theories were followed in practice by an industry all too eager to ignore academic research (which, in order to follow, utilizes money and resources and reduces margins).

(On the latter point, just last week did the American College of Medical Informatics [ACMI] refuse to permit me to be a speaker at their early 2013 annual retreat despite support from some of its members.)

And this:

• If the industry and the academics had been doing their job responsibly, I might be spending this Christmas and New Years's holiday with my mother, rather than visiting her in the cemetery.

All that said, the report is welcome.

Finally, it is hoped - and expected - that public comments will indeed be "public", and that any irregularities in such comments (such as appeared in the public comments period for MU2 due to industry ghostwriting as in my Aug. 2012 post "Health IT Vendor EPIC Caught Red-Handed: Ghostwriting And Using Customers as Stealth Lobbyists - Did ONC Ignore This?" and Sept. 2012 post "Was EPIC successful in watering down the Meaningful Use Stage 2 Final Rule?") will be reported and acted upon in an aggressive manner.

And finally, from the Healthcare Renewal blog, Merry Christmas.

-- SS

Australian ED EHR Study: An End to the Line "Your Evidence Is Anecdotal, Thus Worthless?"

At my Sept. 2010 post "The Dangers of Critical Thinking in A Politicized, Irrational Culture" I lamented that while my early mentor in biomedicine Victor P. Satinsky MD taught the wise credo "critical thinking always, or your patient's dead" in the 1970's, our culture had become so perverse that this credo had been largely supplanted with:

"Critical thinking anytime, and your career's dead."

That post was in reaction to continued heckling on a professional mailing list, the American Medical Informatics Association (AMIA) Clinical Information Systems Working Group (cis-wg). On this list, Oregon Health Sciences University professor William Hersh expounded on how the evidence of health IT dangers was largely "anecdotal" therefore to be discounted, and how I, specifically, "didn't know the literature on health IT."



In that post I put the lie to the latter figment. On the former prevarication Dr. Jon Patrick, author of the recent thorough dissection of problems with the ED EHR system being rolled out in public hospitals in New South Wales, Australia (see my Mar. 5, 2011 post "On an EMR Forensic Evaluation by Professor Jon Patrick from Down Under: More Thoughts"), hit the ball out of the park:

Prof. Patrick to AMIA cis-wg:



I think such defences are particularly unuseful especially with respect to the dismissal of personal stories and experiences as "anecdotes", hence committing them to the realm of folklore. I offer these notions as a counterpoint.



Discounting Anecdotes:



1. Is a perfidious and specious act.



2. It denies early warning signs of problems.



3. It denies a voice and disempowers the working clinical community who have to operationalise decisions made by others.



4. It denies a route to process improvement within an institution - which is most important for EBM and incremental review of local processes.



5. It defends software manufacturers from fault rectification - cuts off even a need to deliberate on it. Critics of the value of anecdotes are squarely on the side of the faulty and deficient manufacturer.



6. A rule of project management is that projects consist of 3 components, cost, quality and time and if their needs to be a compromise it has to be on quality. Anecdotes are early warning signs of such a compromise.

Prof. Patrick had to once again put the lie to this refrain at a comment on the HISTalk blog yesterday, where the anonymous proprietor had written in a review of Patrick's EHR study:

... On the other hand, I wouldn’t say it’s [Prof. Patrick's Cerner FirstNet study] necessarily unbiased, it focuses on implementation of a single department application that didn’t go well for a variety of reasons (despite many successful FirstNet implementations elsewhere), it uses the unchallenged anecdotal comments of unhappy users who make it clear they liked their previous EDIS better, and it nitpicks (I wasn’t moved to find a pitchfork when I learned that the primary keys in the Millennium database aren’t named consistently).



[Considering the complexity and changeability of healthcare and the corresponding software lifecycle, I duly note that that latter attitude about 'failing to find pitchforks' regarding breaches of sound software engineering practices seems to be a symptom of the larger health IT disease that Prof. Patrick writes about - ed.]

Dr. Patrick then knocked the ball out of the Southern Hemisphere with a comment of his own about anecdotalism and a link to an expansion of the aforementioned ideas he'd shared on "discounting anecdotes":

Prof. Patrick to HISTalk owner:



Your Comment “it uses the unchallenged anecdotal comments of unhappy users ” is not only unfair but unreasonably inaccurate. The comments made by the users are the Directors of 7 EDs and so they have a right to carry authority by virtue of the experience but also the number of 6 out 7 presenting a view of Firstnet as unfit for purpose has numeric validity, which they justify with about 20+ pages of their comments – see Part 2 Appendix 2.



I would also point readers to my editorial about the role of personal experiences being the most useful information to understand the nature of socio-technical failures. http://aci.schattauer.de/en/contents/archive/issue/1124/manuscript/15463/show.html

The essay at that link, "The Validity of Personal Experiences in Evaluating HIT", is an editorial in Johns Hopkins informaticist Chris Lehmann's brilliant new journal "Applied Clinical Informatics."



The editorial is available free, and is a must-read for anyone in a decision-making or managerial role in mission critical domains, including our elected representatives.



In the editorial Dr. Patrick concludes. similarly to his earlier AMIA mailing list opinion:

... the denial of recounted personal experiences in discussion and analysis of HIT is biased and specious and has the effect of:



1. Denying early warning signs of problems.



2. Denying a voice for the working clinical community who have to operationalise decisions made by others and thus disempowers them.



3. Denying process improvement within an institution – which is most important for Evidence Based Medicine and incremental review of local processes.



4. Discourages staff from engaging in any form of process improvement hence worsening the sense of disenchantment.



Every legitimate personal experience of a HIT deserves to be considered on its merits lest we wish to retreat from process and product improvement. Mechanisms of censorship both implicit due to contrived processes of disinformation and disempowerment or explicit due to contractual specifications will lead to more waste, lost productivity, contempt for the providers, and distress among frontline staff rather than increased productivity and improved patient health and safety as we all desire.

In my view, the drivers or motivators for the "anecdotalist" accusation are these, singly or in combination:

• Too much "education" to see the nose on one's face, as in, to think zebras and unicorns instead of horses when hearing hoofbeats outside one's midwest U.S. abode (eggheads);
  
  
• Too little common sense (fools), as in Scott Adams' example: "IGNORING ALL ANECDOTAL EVIDENCE - Example: I always get hives immediately after eating strawberries. But without a scientifically controlled experiment, it’s not reliable data. So I continue to eat strawberries every day, since I can’t tell if they cause hives";
  
  
• Too much concern for the possible interruption of flow of money or power in one's direction (gonifs).
  
  

In conclusion, the anecdotalist refrain of "your evidence is anecdotal" [therefore of little or no value] when used repetitively against competent observers is the refrain of eggheads, fools and gonifs.



In healthcare, the end result is "your patient's dead."



My "anecdotal relative" injured in a mid-2010 HIT mishap is sadly an example.



[June 2011 addendum: my relative, after much suffering, has now died of complications of the "anecdotal HIT mishap" - ed.]



As for myself, I am a Markopolist (see my Sept. 2010 post "Health IT: On Anecdotalism and Totalitarianism").



-- SS

Report of an AMIA special task force on challenges in ethics, safety, best practices, and oversight regarding HIT

I am both surprised and pleased to read the new report of an American Medical Informatics Association (AMIA) task force, in the form of an AMIA Board Position Paper released today entitled:

"Challenges in ethics, safety, best practices, and oversight regarding HIT vendors, their customers, and patients: a report of an AMIA special task force." Goodman, Berner, Dente, Kaplan, Koppel et al. for the AMIA Board of Directors. J Am Med Inform Assoc (2010). doi:10.1136/jamia.2010.008946.

A free PDF is available at this link.

This report may be part of a trend. As I wrote recently at this link:

I was somewhat taken aback by the appearance of the article by Karsh et al. entitled "Health information technology: fallacies and sober realities" (covered at Healthcare Renewal here) in the Oct. 2010 Journal of the American Medical Informatics Association (JAMIA).

I was taken aback since the article rains heavily on the academic memes of healthcare IT as a benign and deterministic solution to healthcare's ills, and of health IT-related adverse outcomes being mere "anecdotes."

It appears that the views on healthcare IT safety, ethics, management practices, etc. appearing on the Healthcare Renewal blog and on my once-controversial academic health IT website "Contemporary Issues in Medical Informatics: Common Examples of Healthcare Information Technology Difficulties" (started in 1999) are now becoming mainstream.

Most of the issues in this new AMIA Position Paper have been written about at this blog since 2004, and at my aforementioned academic HIT website since 1999. I will reproduce the abstract of the paper below, but download and read the entire paper (emphases mine):

ABSTRACT
The current commercial health information technology (HIT) arena encompasses a number of competing firms that provide electronic health applications to hospitals, clinical practices, and other healthcare-related entities. Such applications collect, store, and analyze patient information. Some vendors incorporate contract language whereby purchasers of HIT systems, such as hospitals and clinics, must indemnify vendors for malpractice or personal injury claims, even if those events are not caused or fostered by the purchasers. Some vendors require contract clauses that force HIT system purchasers to adopt vendor-defined policies that prevent the disclosure of errors, bugs, design flaws, and other HIT-software-related hazards. [The "gag clauses." These are exceptionally unethical, in my view, regarding the use of an experimental technology, healthcare IT, on unsuspecting, unconsented patients unaware of health IT risks - ed.] To address this issue, the AMIA Board of Directors appointed a Task Force to provide an analysis and insights. Task Force findings and recommendations include: patient safety should trump all other values [I've been writing and saying this for many years now - ed.]; corporate concerns about liability and intellectual property ownership may be valid but should not over-ride all other considerations; transparency and a commitment to patient safety should govern vendor contracts; institutions are duty-bound to provide ethics education to purchasers and users, and should commit publicly to standards of corporate conduct; and vendors, system purchasers, and users should encourage and assist in each others’ efforts to adopt best practices. Finally, the HIT community should re-examine whether and how regulation of electronic health applications could foster improved care, public health, and patient safety. [Regulation has been another issue I have focused upon, especially after holding a management role in Big Pharma - ed.]

Also notable was this proclamation:

... “Hold harmless” clauses in contracts between Electronic Health Application vendors and purchasers or clinical users, if and when they absolve the vendors of responsibility for errors or defects in their software, are unethical. [I note that, somewhat remarkably, this is not the more typical hedged academic "may be unethical" statement- ed.] Some of these clauses have stated in the past that HIT vendors are not responsible for errors or defects, even after vendors have been informed of problems.

Unethical, indeed, as per my JAMA letter of July 22, 2009 on that issue entitled "Health Care Information Technology, Hospital Responsibilities, and Joint Commission Standards" (link) and per my more detailed essay at my Drexel HIT website (link).

Also remarkable were these statements:

... For-profit manufacturers of healthcare products are bound by values which may at times conflict. For instance, as entities in a marketplace, they are duty-bound to provide a financial return to those investors who have contributed resources in anticipation of their success. Yet, as developers and manufacturers of products that affect the health of people, they are no less obligated to ensure, to the extent possible, that their products are safe and effective, and beneficially support patients [that goes without saying - ed.] and those who treat and care for them. [That is, clinicians, who through their unpaid hard work using oft ill-designed HIT systems are currently used as beta testers and, through 'hold harmless' clauses, as an insurance company and, quite frankly, as cannon fodder - ed.]

... Contracts should require that system defects, software deficiencies, and implementation practices that threaten patient safety should be reported, and information about them be made available to others, as appropriate. Vendors and their customers, including users, should report and make available salient information about threats to patient safety [I've also been writing this for years; it's common sense - ed.] resulting from software deficiencies, implementation errors, and other causes. This should be done in a way easily accessible to customers and to potential customers. This information, when provided to customers, should be coupled with applicable suggested fixes, and should not be used to penalize those making the information available. [There should be as little fear of reporting HIT problems as in reporting medication problems - ed.]

... If appropriate for their size and mission, vendors and client institutions contribute to the growth of biomedical knowledge by conducting HIT research [including research on how to remediate the HIT itself and the IT industry creeds, customs and traditions that cause suboptimal design and implementation in the first place - ed.] … authors of scientific reports should not be prevented from identifying devices, tools, and systems by name in publications.

… There are situations in which HIT vendors pursue joint marketing agreements with institutions that adopt vendors’ products and by which these institutions become a part of the vendors’ marketing program [I believe that hospitals should never allow themselves to become IT marketing and promotion operations - ed.], often in exchange for discounts, payments, stock options, or favorable treatment by the vendor. In at least some cases, these agreements include provisions whereby healthcare institutions that serve as demonstration sites for particular products receive compensation when other institutions adopt products from the same vendor. The Task Force notes that such agreements might place the “referring” institutions in a conflict of interest [a common topic on this blog -ed.], and therefore recommends that:

• Any such conflicts should be eliminated or managed, including disclosure, according to current standards.

• Where such agreements are made, they should include a provision whereby any payment or other compensation contingent on the sale of a system to another party must be disclosed to that other party.

• Payments or gifts to individuals and institutions, including institutional officials, clinicians, etc, should be disclosed. Alternatively, they should be addressed by entities’ internal mechanisms for managing conflicts of interest and commitment, perhaps along the lines of the “rebuttable presumption” standard endorsed by the Association of American Medical Colleges. The goal of the standard is “to ensure that institutions systematically review any financial interest that might give rise to the perception of a conflict of interest, and further, that they limit the conduct of human subjects research by financially interested individuals to those situations in which the circumstances are compelling.

The new AMIA Position Paper and the aforementioned paper on HIT fallacies and realities seem to reflect a welcome transformation or even about-face for AMIA. I am likely considered "radioactive" by some in that organization for espousing similar views dating back to the late 1990's, when expression of such views was uncommon and even frowned upon. Academia has not been highly tolerant of heterodoxy in many domains for quite some time.

One wonders if that stigma will "stick" in view of the increasing realization that such views were not heretical, but forward-thinking along the lines of my early medical mentor, the late Victor P. Satinsky, MD of Hahnemann Medical College and Hospital:

From http://www.upenn.edu/gazette/0298/0298obits.html: Dr. Victor P. Satinsky, C'34, Philadelphia, a cardiovascular surgeon at the old Hahnemann Hospital who helped develop coronary-bypass surgery; September 7 [1997]. He is also credited with 30 major medical innovations and the invention of the Satinsky clamp, now a standard instrument in cardiovascular surgery. He joined Hahnemann (now part of the Allegheny health system [as of 2010 now Drexel College of Medicine - ed.]) in 1946 to do thoracic-surgical research, and from 1961 till his retirement in 1977 he was the research director of its cardiovascular institute. Dr. Satinsky liked to refer to himself on promotional materials as 'the Renaissance Doctor', as he was also a poet, a playwright (some of his plays were produced in London), a painter, a clarinetist, and a fencer; he was known at Hahnemann for practicing his swordsmanship in the halls and classrooms of the hospital. And at the age of 80, he earned a black belt in aikido, and subsequently taught it. Although he had no religious training, during the Second World War he once filled in as a rabbi on a troopship going to Europe when he learned it had chaplains, but no rabbi. He also had taught himself psychiatry and while at Hahnemann developed educational programs for young people; the first, for gifted high-school students, began in 1961. He later added programs for disadvantaged youth, for young people with emotional problems, and one for college dropouts. On retiring, he set up the Satinsky Institute for Human Resource Development to continue this work, which he ran until his death at 84 years.

Dr. Satinsky's short, simple and unyielding credo was:

"Critical thinking always, or your patient's dead."

-- SS

On AMIA's Jan. 2009 Letter to The Office of President Elect Barack Obama: Something is Missing

------------------------------------------
Nov. 11, 2010 note: see the new post on an AMIA Board Position Paper released this day (Nov. 11) entitled "Report of an AMIA special task force on challenges in ethics, safety, best practices, and oversight regarding HIT" at this link.
------------------------------------------

I was somewhat taken aback by the appearance of the article by Karsh et al. entitled "Health information technology: fallacies and sober realities" (covered at Healthcare Renewal here) in the Oct. 2010 Journal of the American Medical Informatics Association (JAMIA).

I was taken aback since the article rains heavily on the academic memes of healthcare IT as a benign and deterministic solution to healthcare's ills, and of health IT-related adverse outcomes being mere "anecdotes."

(It is ironic that my own relative recently fell victim to healthcare IT's supposed beneficence. They were harmed via health IT-related disruptions in care continuity.)

My blog posting on that Karsh article brought a letter to my attention, authored by AMIA's leadership and sent on Jan. 7, 2009 to the Office of President Elect Barack Obama. The full PDF of the letter is here.

Here are relevant excerpts about which I will make only a single comment:

January 7, 2009

Dear Mr. President-Elect,

On behalf of the more than 4,000 physicians, nurses and other members of the American Medical Informatics Association (AMIA) who use health information and communications technology (HIT) to improve the quality, efficiency and safety of healthcare, I am writing to applaud and encourage your commitment to investing in a genuine transformation of our nation’s healthcare system. Properly deployed and supported, HIT can be part of broad health care reform and, importantly in this time of economic challenge, a significant economic multiplier that will encourage the creation of new jobs and real improvements in patient care, public health and life sciences research.

... If we are to develop a national infrastructure for the use of health information to benefit individuals and our entire population, the United States must –

• Develop mechanisms, including grants, loans and financial incentives for physicians, nurses, and healthcare organizations to deploy, implement successfully, and widely disseminate electronic health records (EHRs);
• Develop and support local, regional and national health information exchange to ensure that accurate, secure health information is available whenever and wherever needed by those authorized to access such information;
• Develop and support programs to address the need for a prepared health information technology workforce, with training and continuing education of physicians, nurses, health information managers and others;
• Develop more effective ways to address the health needs of underserved populations, including providing equitable access to health information and communications technology;
• Develop and assure compliance with standards, policies and practices that support effective sharing of health information, while fostering security, confidentiality and transparency, and building trust with the public;
• Develop and maintain health terminologies and classifications that will allow health data to be not only useful, but uniform and consistent, and enable interoperability across myriad information systems;
• Develop proper means to link information related to individuals in order to ensure the validity and integrity of health data used to inform care and research;
• Develop proper means for authentication of the identity of individuals and caregivers and any others authorized to access identifiable health information;
• Support the development of decision-making and other knowledge-management tools in order to permit the delivery of individualized, evidence-based care;
• Develop and support secure web-portals to link individuals to their caregivers and ensure genuinely patient-centered care;
• Develop appropriate and secure linkages between EHRs and the public health system to ensure safety from bioterrorism, rapidly spreading infectious diseases, and other threats;
• And provide appropriate funding for the development of a robust national health information strategy, with support for continued HIT and informatics research and innovation.

During the Presidential campaign, you demonstrated your boldness and vision by pledging to allocate $10 billion annually for five years to promote the adoption and use of health IT. Such an investment will pay dividends not only in improving health care, but in creating jobs...

These are all laudable and interesting goals for an experimental technology, as tacitly admitted in the above goals (although it would have been more ethical, I believe, to have waited for the technology to have "needed" fewer of these goals as a result of research in constrained settings before boldly promoting expensive national rollouts on live patients).

In any case, however, something very, very important is missing...

There is no mention of healthcare IT safety.

At $10 billion annually, surely the AMIA leadership could have specifically and explicitly recommended that some fraction, even a token % (even a small percentage of $10,000,000,000 is not chicken feed), should have been dedicated to help ensure the disruptions and unintended consequences caused by any new/developing/expanding information and communications technology (ICT) didn't kill or maim patients.

Perhaps through the publication of the aforementioned Karsh study on HIT fallacies and sober realities, the AMIA leadership is subconsciously seeking absolution.

-- SS

Addendum: my own Dec. 7, 2008 "Open letter to President Obama" on healthcare IT took a decidedly different approach, namely, I attempted to make the President-elect aware of numerous HIT "fallacies and sober realities":

... 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.

... [If HIT itself is not reformed,] 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.

... healthcare’s defects cannot be effectively changed or reformed via healthcare IT, if that healthcare IT itself is defective.

AMIA leadership and I also differed on the issue of health IT regulation, as I posted in July 2009 at "JAMA letter: Health Care Information Technology, Hospital Responsibilities, and Joint Commission Standards." On that issue, JAMA published my commentary, not theirs.

-- SS