Laman

Tampilkan postingan dengan label healthcare IT usability. Tampilkan semua postingan
Tampilkan postingan dengan label healthcare IT usability. Tampilkan semua postingan

Senin, 04 November 2013

Australian Medical Association on EHR rollout: 'Hard to use, increases workload, hard to find data, we just don't seem to have got the outcome we were looking for.'

Some familiar themes from the Australian Medical Association on their attempt at a National Programme for Health IT:

Electronic health records rollout has not met expectations, Australian Medical Association says
http://www.abc.net.au/news/2013-11-04/ama-says-rollout-of-electronic-health-records-needs-work/5066680
Updated Mon 4 Nov 2013, 8:59am AEDT

The Australian Medical Association says the rollout of electronic health records has not met expectations.

Federal Health Minister Peter Dutton has announced an independent review of the project to see how it can be improved.

AMA national president Dr Steve Hambleton, one of the panel members for the review, says e-health records need to be made easier for doctors to use.

Ease of use seems a constant, unremitting problem.  An independent review (if truly independent) is a wise move - and sorely needed in this country, where the narrative is controlled by the industry and its government sponsors/cheerleaders.

A bit of wisdom comes to mind, from (of all people) weapons inventor Mikhail Kalashnikov:  "All that is too complex is unnecessary, and it is simple that is needed."

(Satirically speaking, would it be helpful  if health IT designers, when suffering from, say, acute renal colic, or Bornholm disease a.k.a. devil's grip, http://en.wikipedia.org/wiki/Bornholm_disease, were made to wait for treatment until the doctors and nurses navigated every single tab, menu, pulldown, selection list, etc. to enter all of their data? Perhaps that would be an educational experience for them ... )

"It's certainly timely to actually have a look at the e-health records and just see where it is, where it's going, whether it's actually achieved what it set out to do and what we need to do to actually make it work," he said. 

I think the question of  "whether it's actually achieved what it set out to do" was meant as rhetorical.


"The profession's always supported this, we just don't seem to have got the outcome we were looking for."

That's because the profession - both in Australia and the U.S. - has abdicated leadership of healthcare informatics efforts, instead delegating it to those without domain expertise, and/or the incompetent.

This is a sure path to the results we now are getting both here and Down Under.

From a recent essay at the "Sultan Knish" Blog by writer Daniel Greenfield (http://sultanknish.blogspot.com/2013/10/government-is-magic.html) on competence and the Obamacare insurance website debacle:

... Modernity has to be built. It has to be constructed brick by bit by rivet by cable by people who know what they are doing. Modernity without competence is as worthless as the ObamaCare website which looked pretty enough to give the illusion of technocratic modernity, but didn't actually work.

Competence is the real modernity and it has very little to do with the empty trappings of design that surround it. In some ways the America of a few generations ago was a far more modern place because it was a more competent place. For all our nice toys, we look like primitive savages compared to men who could build skyscrapers and fleets within a year... and build them well.

Unfortunately, there is no easy solution to this problem, since in this industry, failure is an option, and a profitable one at that.

Mr Dutton says a lot of money has been spent on the project, but that the take up rate has been low.

In the U.S., the takeup rate has been artificially accelerated by economic incentives and penalties (via the HITECH Act of 2009).  Australia seems to lack such a plan at present.

Concerns were raised in July that the new system, which was trialled in parts of New South Wales, Queensland and Victoria, makes it difficult for doctors to access updated information

I opine that it takes remarkable incompetence to design software using computers that can store, retrieve and process data at speeds unimaginable just a few years ago, that actually make it difficult for users to access current information.

Doctors also complained that the e-health program, designed to link a patient's medical records between doctors, hospitals and other providers, was increasing their workload.

From the linked article "E-Health Flaws Adding to GP Stress", http://www.abc.net.au/news/2013-07-16/e-health-flaws-adding-to-gp-stress/4822186:

Many Newcastle GPs say the system is adding to stress levels and making their workloads excessive. They are complaining the E-health program unworkable in its present form and is increasing their workload by up to two hours a day.

For little benefit, I add.

... Dr Hambleton says the initial version of the system has several strong aspects and is safe and secure, but that key changes will benefit doctors.

"Clinical utility means that it decreases the search time and that we've got accurate information there. Those are the things that'll make clinicians want to use it and be able to use it."

Translation: major changes might actually make the systems useful, instead of a time-sapping annoyance (at best), and a danger (at worst).

-- SS

Jumat, 17 Mei 2013

American Medical Association finally on board with EHR views expressed on this blog since 2004

- Posted on the Healthcare Renewal Blog May 17, 2013 -

It seems to have taken awhile, but organized medicine seems to finally be recognizing that today's commercial health IT is not quite the revolutionizing, transformative, plug-and-play panacea to healthcare's ills it is often touted as:

AMA Wire
May 15, 2013
AMA board chair: HHS should address EHR usability issues immediately

The government needs to act quickly to remedy the impaired usability of electronic health records (EHR) if the technology's touted benefits are to be realized, AMA Board of Trustees Chair Steven J. Stack, MD (left), told officials during a federal hearing last week.

"The AMA and most physicians believe that, done well, EHRs have the potential to improve patient care," Dr. Stack, an emergency physician in Lexington, Ky., said during his 30-minute testimony. "At present, however, these EHRs present substantial challenges to the physicians and other clinicians now required to use them."

He emphasized that many of today's EHR systems require significant changes before they can deliver the promised outcomes. Referring to Medicare's meaningful use program, he pointed to undesired consequences of pushing EHR systems on physicians before the technology was completely ready for prime time.

"Immediately" is strong language.

I note that the phrase "health IT done well" is a term I've been using since 1998 at my now-Drexel-based health IT teaching website at http://www.ischool.drexel.edu/faculty/ssilverstein/cases, as well as at this blog.

Penned by me at my aforementioned Drexel graduate teaching site, originally housed on AOL, in 1998 and still appearing in its main essay:

... While clinical IT is now potentially capable of achieving many of the benefits long claimed for it such as improved medical quality and efficiency, reduced costs, better medical research and drugs, earlier disease detection, and so forth, there is a major caveat and essential precondition:  the benefits will be realized only if clinical IT is done well.  For if clinical IT is not done well, as often occurs in today’s environment of medical quick fixes and seemingly unquestioning exuberance about IT, the technology can be injurious to medical practice and biomedical R&D, and highly wasteful of scarce healthcare capital and resources. 

Those two short words “done well” mask an underlying, profound, and, as yet, largely unrecognized (or ignored) complexity.  This website is about the meaning of "done well" in the context of clinical computing, a computing subspecialty with issues and required expertise quite distinct from traditional MIS (management information systems, or business-related) computing.

(I have more recently switched to the easier-to-parse terminology of "good health IT" vs. "bad health IT" after discussions with Dr Jon Patrick at U. Sydney during my visit Down Under last summer, http://hcrenewal.blogspot.com/2012/08/my-presentation-to-health-informatics.html.)

I've also heard "not ready for prime time" before.  It is a phrase I used in speaking with a New York Times reporter that then appeared in the Oct. 8, 2012 NYT article "The Ups and Downs of Electronic Medical Records" (http://www.nytimes.com/2012/10/09/health/the-ups-and-downs-of-electronic-medical-records-the-digital-doctor.html?pagewanted=2) by Milt Freudenheim, October 8, 2012, where I am quoted and this blog cited:

... Critics are deeply skeptical that electronic records are ready for prime time. “The technology is being pushed, with no good scientific basis,” said Dr. Scot M. Silverstein, a health I.T. expert at Drexel University who reports on medical records problems on the blog Health Care Renewal. He says testing these systems on patients without their consent “raises ethical questions.”

The AMA Board chair went on to opine:

"Attempting to transform the entire health system in such a rapid and proscriptive manner has compelled providers to purchase tools not yet optimized to the end-user's needs and that often impeded, rather than enable, efficient clinical care," he said.

He noted that physicians are "prolific technology adopters" but that adoption of EHR systems has required federal incentives because the technology still is "at an immature stage of development."

My near-exact terminology has been that the technology is still experimental.

"EHRs have been and largely remain clunky, confusing and complex," he said.

Perhaps he read my ten-part series on the health IT mission hostile user experience at this blog, at http://www.tinyurl.com/hostileuserexper.

According to a recent survey by AmericanEHR Partners, physician dissatisfaction with EHR systems has increased. Nearly one-third of those surveyed in 2012 said they were "very dissatisfied" with their system, and 39 percent said they would not recommend their EHR system to a colleague—up from 24 percent in 2010.

A survey I posted about in Jan. 2010 is here:  "An Honest Physician Survey on EHR's", http://hcrenewal.blogspot.com/2010/01/honest-physician-survey-on-ehrs.html

Dr. Stack spoke at a "listening session" hosted by the Centers for Medicare & Medicaid Services (CMS) and the Office of the National Coordinator for Health Information Technology (ONC), a division of the U.S. Department of Health and Human Services (HHS). The agencies coordinated the session to examine how a marked increase in code levels billed for some Medicare services might be tied to the increased use of EHRs.

Dr. Stack noted that some Medicare carriers have begun denying payment for charts that are too similar to other records.

"In this instance, even when clinicians are appropriately using the EHR, a tool with which they are frustrated and the use of which the federal government has mandated under threat of financial penalty, they are now being accused of inappropriate behavior, being economically penalized, and being instructed ‘de facto' to re‐engineer non‐value‐added variation into their clinical notes," he said. "This is an appalling Catch‐22 for physicians."

"Mandated under threat of financial penalty" has been one of my stated "cart before the horse" issues with HITECH (e.g., http://hcrenewal.blogspot.com/2010/10/cart-before-horse-again-institute-of.html).

Dr. Stack advised officials that three key actions are necessary to rectify these issues with EHR systems:
  • The ONC promptly should address EHR usability concerns raised by physicians and add usability criteria to the EHR certification process.
  • CMS should provide clear and direct guidance to physicians concerning use of EHRs for documentation, coding and billing.
  • Stage 2 of the meaningful use program should allow more flexibility for physicians to meet requirements as EHR systems are improved.
The AMA will continue to work with federal agencies to improve EHR systems and the Medicare meaningful use program.

I've been calling for usability evaluation to be added to the certification process, including in comments during public comment periods to HHS, for some time.

What the AMA Board Chair is apparently missing, though, is health IT safety.  They should perhaps read my post on the recent ECRI Institute Deep Dive Study on health IT risk - itself based on a report in their own AMNews (amednews.com) publication ("Peering Underneath the Iceberg's Water Level: AMNews on the New ECRI Deep Dive Study of Health IT Events", http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html).

I don't think any prudent person would consider a 9-week study of 36 hospitals with volunteered reports of 171 health information technology-related problems, where eight of the incidents reported involved patient harm and three may have contributed to patient deaths, information to ignore.

-- SS

Minggu, 10 Maret 2013

Far more concern about Linux user experience than the EHR user experience, and your life does not depend on the former

I find this ironic and striking:

During my informatics postdoc I used a SparcStation-2 running UNIX and an old X Windows user interface.  Then a few years later, in the Windows 95 days, I installed Linux (an open-source UNIX-like operating system) on a PC and used various X Windows user interfaces on that, too.  There was a lot of debate on which features of which user interface made for the best usability, and more broadly, user experience.

This debate continues as Linux in its multiple versions continues to be extremely popular.

If the health IT sellers put as much time into considering the user experience presented by their products as does the Linux community and were as candid, as, say, the Ubuntu Linux community as here, there might not be physician rebellion groups like Twitter's #EHRbacklash springing up.

-- SS

Rabu, 30 Januari 2013

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 soI'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 decadesNot 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 hereAs 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

Kamis, 02 Februari 2012

Siemens Healthcare on solving EHR usability problems: you can just call up your pal at the next hospital

In my Aug. 2009 post "Why Siemens Healthcare Fails", I wrote:

I note that I used to admire German engineering rigor, but after seeing ill conceived, misguided position ads like the following from Siemens Healthcare, I am having sincere doubts about that country's current prowess in that domain.

My admiration fell another notch. I now see this, in a Feb. 1, 2012 article from HealthData Management entitled "User Unfriendly" on the flaws in commercial health IT that present a poor user interface/user experience (at the expense, ultimately, of you, the patient). The article's browser title bar somewhat subliminally reads "Physicians gripe that EHR's are not easy to use but improvements are coming":

... There's also no mechanism for publicizing problems with EHR interfaces, unlike the FDA's process for issues with medical devices. [User interface expert Prof. Ben] Shneiderman describes a case where a physician found a bug in an EHR that created a danger to patients. "He contacted the supplier because he thought it was something other users should know about, and the response was, 'Oh, we know-we're working on it,'" Shneiderman says. "The physician said, What? You know about it and you haven't notified everyone?' Contrast that with the Federal Aviation Administration, where problems with airplanes are publicized within hours."

The IOM report calls for substantial loosening of those contractual restrictions. "The committee views prohibition of the free exchange of information to be the most critical barrier to patient safety and transparency," the report says. "The committee urges the [HHS] Secretary to take vigorous steps to restrict contractual language that impedes public sharing of patient safety-related details. Contracts should be developed to allow explicitly for sharing of health I.T. issues related to patient safety." The report also says there should be a central place to report and publicize known issues with EHR software.

Siemens apparently has a different idea on taking responsibility for the user interfaces of their products:

Siemens Healthcare Chief Medical Officer Don Rucker, M.D., says the secrecy issue is overblown. "There are trailer loads of information out there on each of these big systems, and there are so many end users that you can just call up your pal at the next hospital."

There are trailer loads of information out there, and it's up to the end user physician to find the information and sort through it?

... Sounds perfectly reasonable to me. /not/

There are so many end users that you can just call up your pal at the next hospital [for guidance on user interface complexities and errors]?

Also sounds perfectly reasonable.
/not/

... Except, I think most EMR vendors and user-organizations sort-of disable Remote Assistance, Remote Desktop and similar programs. Even "print screen" is usually either disabled or forbidden from sharing with that "pal at the other hospital." Might have something to do with security and IP protection.

Ever try to guide someone through a complex computer interface over the phone, blind, with no real-time mutually viewed visuals? It's not easy, but ... physicians and nurses have PLENTY of time for such fritter, what with the little other work they have to do.

I also think saying busy physician, nurse and other clinical customers should "depend on their pals at the next hospital" for information on health IT difficulties is a rather condescending and patronizing statement to make (to be charitable), a backyard-mechanic attitude, but that's just me.

Why does Siemens fail?

This type of statement is a very good clue.

-- SS