Showing posts with label HIT failure. Show all posts
Showing posts with label HIT failure. Show all posts

Tuesday, December 01, 2009

"We are unable to share documents relating to problematic EHR's as our contract with Cerner includes a confidentiality clause ..."

In my post "Academic Freedom and ED EHR's Down Under: Another Update and a Welcome Development" I reported on the Univ. of Sydney's somewhat belated support for academic freedom, and the reappearance of an essay on ED electronic health records problems in NSW by one of its informatics faculty, Prof. Jon Patrick, after an apparently government-initiated attempt at censorship.

A new update of the paper "A Critical Essay on the Deployment of an ED Clinical Information System - Systemic Failure or Bad Luck" version 6, has now been posted by Dr. Patrick at this link on his department's web pages (a direct link at this time to the PDF is here).

The press has started to take notice. A piece in the Sydney Morning Herald entitled "Health department accused of censorship" appeared on Nov. 28 here.

That piece was noted by Computer Weekly in the U.K. in a piece entitled "Claim of censorship over Cerner system" here. The U.K. suffers a severe EHR epidemic (the UK Public Accounts Committee report on disastrous problems in their £12.7 billion national EMR program is here.)

[12/3/09 update: the piece has disappeared, then reappeared, at Computer Weekly. In case it disappears again, a copy of the article from Google's cache is here.]

From the U.K. Computer Weekly article:

The Sydney Morning Herald and ZDNet in Australia report that the University of Sydney removed from its website - temporarily - a negative essay about a Cerner system which had been installed at hospitals in New South Wales.

The author of the essay is a medical IT professor, Jon Patrick, who is reported to have claimed that NSW Health, which is part of the government of New South Wales, put pressure on the university to take down the paper.

If true, it would tie in with what's been happening in England where mentions of Cerner in a negative context are being officially discouraged.

Cerner is due to be installed at hospitals across London as part of the National Programme for IT [NPfIT] but several trusts that have already gone live - including the Royal Free and Hampstead, Barnet and Chase Farm, and Barts and The London - have run into serious problems, including the losing of patient appointments and patients not being treated.

A showcase Cerner site at Homerton ceased mentioning Cerner in its public board papers after doing a deal with NHS Connecting for Health and the Department of Health. Homerton also rejects FOI requests related to its discussions on Cerner.

Homerton told me: "We are unable to share documents relating to these meetings as our contract with Cerner includes a confidentiality clause and as such disclosure of the information could give rise to an actionable breach of confidence."

I am repeating that last sentence for effect:

We are unable to share documents relating to these meetings as our contract with Cerner includes a confidentiality clause and as such disclosure of the information could give rise to an actionable breach of confidence.


This is solid evidence of such confidentiality clauses in HIT contracts and the chilling effect they have, along with dangers of "hold harmless" clauses. This style of EHR contracting is a practice now under investigation by the U.S. Senate Committee on Finance, as in their Oct. 16, 2009 letter to major healthcare IT vendors and management consultants from Senator Charles E. Grassley (ranking member). A copy of that letter is here (PDF).

I have written on the dangers of such clauses before as in my July 22, 2009 letter in the Journal of the American Medical Association "Health Care Information Technology, Hospital Responsibilities, and Joint Commission Standards" (http://jama.ama-assn.org/cgi/content/extract/302/4/382), as well as my much more thorough posting on these issues in the essay at my Drexel University website here.

In that essay I observed:

Regarding healthcare IT "Hold Harmless" and Defects Gag Clauses, I also question whether hospital executives violated their fiduciary responsibilities by signing such contracts, and violated Joint Commission standards of hospital leadership conduct as well ...


Let's look at the Joint Commission Hospital Accreditation Program Leadership Chapter, and its standards for hospital leadership (link, PDF):


Leadership
LD.01.03.01

Standard LD.01.03.01
The governing body is ultimately accountable for the safety and quality of care, treatment, and services.

Rationale for LD.01.03.01
The governing body’s ultimate responsibility for safety and quality derives from their legal responsibility and operational authority for [organization] performance. In this context, the governing body provides for internal structures and resources, including staff, that support safety and quality.


The governing body has a legal responsibility for safety and quality, not just a moral obligation. One of the "internal structures" is healthcare IT that is safe and effective and that does not expose patients or staff to undue risks.

How does signing "hold harmless" and "defects gag order" clauses with an HIT vendor serve such a purpose, exactly?

Hospital executives know, should know, or should have known that such provisions would remove incentives for health IT vendors to produce the best products and to correct deficiencies rapidly, thus increasing risk to patients and clinicians.

Elements of Performance for LD.01.03.01
5. The governing body provides for the resources needed to maintain safe, quality care, treatment, and services.


One of those resources is health IT.

Standard LD.02.01.01
The mission, vision, and goals of the [organization] support the safety and quality of care, treatment, and services.

Rationale for LD.02.01.01
The primary responsibility of leaders is to provide for the safety and quality of care, treatment, and services. The purpose of the [organization]’s mission, vision, and goals, is to define how the [organization] will achieve safety and quality. The leaders are more likely to be aligned with the mission, vision, and goals when they create them together. The common purpose of the [organization] is most likely achieved when it is understood by all who work in or are served by the [organization].


How is a contract with an HIT vendor that calls for hiding defects in health IT and exposing staff to liability for defects in same serving the above purposes?


Standard LD.02.03.01
The governing body, senior managers and leaders of the organized medical staff regularly communicate with each other on issues of safety and quality.


Does that include communication on health IT defects? Can a medical staff member ask to see a database of such defects when the hospital has signed a nondisclosure of defects agreement with an HIT vendor?

Rationale for LD.02.03.01
Leaders, who provide for safety and quality, must communicate with each other on matters affecting the [organization] and those it serves.


I ask the same question as above.


Standard LD.03.01.01
Leaders create and maintain a culture of safety and quality throughout the [organization].


Safety for whom, exactly? Patients, or patients and staff?

How is exposing professional staff to undeserved liability from defective health IT serving the creation of a culture of safety and quality for them? How is suppressing information on health IT defects and problems helping patient safety and care quality?

How is lack of seeking informed consent on health IT use from patients whose care is mediated by health IT devices with known but undisclosable defects creating a culture of quality?

How is hiding such defects creating a culture of quality in the community's other hospitals, that may be considering purchase of the very same health IT?

Standard LD.03.04.01
The [organization] communicates information related to safety and quality to those who need it, including staff, licensed independent practitioners, [patient]s, families, and external interested parties.

Rationale for LD.03.04.01
Effective communication is essential among individuals and groups within the [organization], and between the [organization] and external parties. Poor communication often contributes to adverse events and can compromise safety and quality of care, treatment, and services. Effective communication is timely, accurate, and usable by the audience.


Are physicians and nurses explicitly informed by administration that clinicians are liable for bad outcomes due to software problems? Are they informed of the gag clause? Are patients informed of unremediated health IT defects existing at time of service?

This standard seems a veritable smoking gun regarding breach of fiduciary responsibility and Joint Commission obligations when hospital leadership signs agreements specifically excluding the sharing information about health IT defects and complaints. It is already known that hospitals maintain lists of health IT defects, some in the thousands of items. A number of the defects rise to the level of creating considerable risk to patients, and nobody is in a hurry to remediate them. (See my proposed although somewhat tongue in cheek "HIT Informed Consent" that describes some of these known defect categories here).

Standard LD.04.04.03
New or modified services or processes are well-designed.

... 3. The hospital's design of new or modified services or processes incorporates: Information about potential risks to patients.

4. The hospital's design of new or modified services or processes incorporates: Evidence-based information in the decision-making process. Note: For example, evidence-based information could include practice guidelines, successful practices, information from current literature, and clinical standards.


How does the contractual inability to communicate about health IT defects, which its executives willingly sign, serve this purpose?

Standard LD.04.04.05
The [organization] has an organization-wide, integrated [patient] safety program.

... 12. The hospital disseminates lessons learned from root cause analyses, system or process failures, and the results of proactive risk assessments to all staff who provide services for the specific situation.


Disseminates lessons learned, except when the HIT contract they've signed with a vendor forbids it, that is.

The practices of the health IT industry, and the dealings of the hospital leadership with that industry, may in fact be a scandal of national (or international) proportions.


International scandal, indeed.

I predict these EHR confidentiality clauses will end up causing great loss of money in failed systems, and/or harming patients, due to the chilling effect they have on revelation of defects and problems by clinicians and executives alike.

Those who signed them will very likely be held liable, at least in the U.S., as the clauses breach the safety standards of the accrediting agency for hospitals here, the Joint Commission. I wish the signers of such contracts good luck in the courtroom.

In Australia and the U.K., I cannot comment, but also wish good luck to those who signed these clauses when lawyers go full court press on EHR-mediated debacles.


-- SS

Tuesday, November 10, 2009

Academic Freedom and ED EHR's Down Under: Another Update and a Welcome Development

In "Academic Freedom and ED EHR's Down Under: An Update" I wrote about the disputed essay on electronic health record (EHR) problems in the Australian state of New South Wales (NSW) by medical informatics professor Dr. Jon Patrick, Health Information Technologies Research Laboratory (HITRL), University of Sydney.

The essay was entitled "A Critical Essay on the Deployment of an ED Clinical Information System ‐ Systemic Failure or Bad Luck?"

I am happy to report that an updated version of the essay, version 5, is now available from Dr. Patrick's university web site at http://www.it.usyd.edu.au/~hitru/index.php?option=com_content&task=view&id=91&Itemid=146 . It can be downloaded from the icon at Item 6.

This is a welcome development.

The essay is now labeled as an Op-Ed (Opinion Editorial).

-- SS

Friday, October 16, 2009

Fuzzy Math Indeed: Rising Costs in Government's Digital Health Stimulus

Seen in the blog of the Huffington Post Investigative Fund:

Fuzzy Math? Rising Costs in Government's Digital Health Stimulus
Spending Could Be Double The Obama Administration's Public Estimate of $19 Billion

By Fred Schulte
Huffington Post Investigative Fund

Creating digital medical records for every American within the next five years – a key provision of President Obama’s stimulus package -- could cost more than twice the $19.5 billion figure that has been cited by federal officials.

Federal budget documents show that actual spending for the plan, which will use stimulus money to help doctors and hospitals defray the cost of installing high-tech records systems, could hit nearly $47 billion.

The discrepancy between the Obama administration’s $19.5 billion public estimate and the entry in the budget of the U.S. Department of Health and Human Services mostly arises from the government’s calculation that it will recoup some of the cost of subsidizing digital systems through billions of dollars in reduced federal health spending. But many health analysts are highly skeptical that such savings can be accurately predicted.

It's worse. Far worse.

I believe the government is underestimating EHR costs by a factor of 5 to 10, due to implementation failure and remediation costs.

I'm a long term optimist on health IT, but a short term realist. I believe we will be having an avalanche of failed/stalled projects such as this one in years to come: "Another Major HIT Project Setback at UCSF".

The incompetence in this industry is worse than I imagined when I started writing about HIT dysfunction a decade ago. Worse are the coverups of problems that occur in implementation and in use.

At least in the U.S. military, there is transparency about health IT problems (e.g., see here). In the private sector, forget about publicity of what actually goes on in the U.S. (The U.K. has increased its own transparency to some extent.)

A spokesman for the department [U.S. Department of Health and Human Services], Nicholas Papas, said that the $47 billion figure is “undergoing revision and we anticipate it will decrease.” He said the agency expects to generate a “firmer figure” by the end of the year, but declined to say how much it would be.

Papas said there was no attempt to lowball the number for public consumption. Calculating both cost and benefits in the government’s estimate is a sound way to explain the price of the plan, he said.


Unfortunately, these calculations do not factor in the cost of dyscompetence, incompetence and failures created by lack of essential cross disciplinary expertise and talent in the HIT industry.

Many health policy experts agree that electronic health records can cut costs by reducing harmful medical errors and wasteful spending.

I would bet these "policy experts" have never tried to implement clinical IT.

The $19 billion figure has appeared in numerous news articles and been widely picked up and repeated by many bloggers covering the fast-growing health information technology industry. Earlier this month President Obama’s chief technology officer, Aneesh Chopra, mentioned the $19 billion figure twice in a live video cast from the White House.

But it’s “totally hypothetical,” said Sharona Hoffman, a professor of law and ethic at Case Western Reserve University School of Law. She said it counts on savings “with no concrete evidence they will occur.”

It's worse than "totally hypothetical." A major confounding variable is simply missing - the cost of HIT failures, false starts, delays, and remediation. More can be read about those risks here. That site has been online for a decade now, and ironically is nearly the only relevant "hit" on a search engine query on "healthcare IT failure" or similar concept.

Has anyone in government been paying attention?

A slide deck I recently presented entitled "Health IT Promises and Threats" provides a dose of reality on supposed cybernetic miracles. It is at this link (PPT).

-- SS

Tuesday, October 13, 2009

Another Major HIT Project Setback at UCSF: Vendor, Client or Both at Fault?

In yet another example of a major health IT project setback, in August I wrote about UCSF's apparent problems with health IT implementation that I learned about through anonymous comments at the HisTALK blog. At "Lessons Unlearned: Health IT Failure, Act 2" I wrote:

I find it remarkable that this resource-wasting scenario (with possible adverse patient care repercussions) can occur:

  • In a state that's in a severe economic crisis,
  • At an organization that failed severely in a HIT and administrative IT merger ten years ago (in the failed, late 1990's attempted merger between UCSF and Stanford's medical centers, see the 2000 stories "UCSF/Stanford: Marriage was rough; divorce is expensive" here and "A thousand MIS personnel cannot merge two healthcare systems" here),
  • With an EHR product, Centricity, that is the descendant of Logician that others have implemented successfully (including myself, speaking from experience),
  • With GE, a major global high technology vendor, presiding over this new failure at a major academic medical center,
  • With ample preventive material available in books, journals on the web about such failures (e.g., at the many pages and links here and here, as just a few examples).

I asked if vendor and hospital executives bother to read such materials.

Here is an update in this poorly-covered mystery:

Friday, October 9, 2009
UCSF halts clinical IT installation
San Francisco Business Times - by Chris Rauber

Dr. Sam Hawgood, newly appointed dean of the University of California, San Francisco's School of Medicine, confirmed that UCSF has put the brakes on installation of a $50 million clinical IT system from General Electric [which had acquired Medicalogic's "Logician" EHR some years ago - ed.]

In late August/early September, the Business Times was unable to reach high-ranking UCSF officials to comment on anonymous reports on the respected HISTalk blog and by sources that UCSF was unhappy with early results of the electronic medical records system installation. An informed insider says GE was “way behind schedule” in writing code, and “UCSF got fed up with the endless GE delays,” and is looking to identify other vendors for a drug order entry system.

“We are taking a pause to evaluate our best options moving forward, and we will be making a decision in the next two to three months, and then moving forward aggressively,” Hawgood said. The delay will not put the IT project behind schedule, he said, because “once we make a decision regarding the vendor, we’ll be back on track for an aggressive installation.” [Unfortunately, that sounds like wishful thinking or spin to me - ed.]

UCSF has brought in consultant Kurt Salmon Associates to help it evaluate the IT project’s woes, which were said to be creating considerable frustration within UCSF Medical Center, and obviously the School of Medicine as well.


This setback is of great concern to me. I believe such scenarios could become commonplace in coming years as healthcare organizations bow to the ARRA-created pressure to computerize "or else" by 2014 - that is, suffer reimbursement penalties for not being "meaningful users" of HIT. (Whatever that somewhat presumptuous term describing a largely experimental technology will ultimately come to mean.)

I have frequently written about the HIT vendors being dominated by those with an MIS (management information systems or "business computing") background, and unshakably and arrogantly deficient in talent management where Medical Informatics expertise is concerned. GE may also suffer from domination by engineers whose primary experience is at the level of capital equipment, PACS etc., much as I wrote about competitor Philips Medical here and here.

Having once worked for a GE competitor myself, Comdisco Healthcare Group, and having asked GE representatives about what a phrase on a banner at an RSNA show stating "GE: Leader in Radiology Informatics" meant -- and getting blank stares and comments that "it has something to do with the computers connected to our xray devices" back in return-- my concern was that the problems are not just UCSF centric but vendor centric as well.

UCSF is a big, complex organization, with a lot of very smart clinicians and lots of politics, and I conjecture that GE bit off more than it could chew regarding development, customization and deployment of major health IT at such an organization. It requires far more than technical excellence.

My concern is that GE, along with many if not most of the other major health IT vendors, lack the Medical Informatics and Social Informatics talent and depth to make our ambitious national EHR plans a reality. The overselling of vaporware and "yes, we can do that, no problem" promises by sales and marketing are also a concern, as I find common in HIT where salespeople promise the world to close a deal. Then, the technical people need to play catch up to the grandiose promises made by their creative sales colleagues.

I fear in a few years we will be in the situation that the UK's National Programme for IT (NPfIT) in the NHS is in now.

If we want to avoid that fate, we as a country must:

  • Increase transparency and information diffusion about HIT difficulties and failures greatly. That my website on HIT failures is still nearly unique on the Web after ten years is symptomatic of a true lack of information sharing on real world HIT problems. My monitoring of access patterns to the site as reported in this 2006 AMIA poster (PDF) strongly suggests the demand for such material far exceeds the supply. The AMIA/AHIMA book of which I am an associate editor entitled "H.I.T. or Miss: Lessons Learned from Health Information Technology Implementations" and the new journal "Applied Clinical Informatics" whose Editor-in-Chief is Dr. Chris Lehmann, informaticist at Johns Hopkins, are a start -- but just a start on candid information diffusion about applied HIT realities.
  • Health IT vendors need to understand that those in MIS and engineering are, in the context of complex clinical settings where clinician-supportive HIT is to be developed and deployed, often dyscompetent (they fail to maintain acceptable standards in one or more areas of professional practice) or even incompetent (lacking the requisite cognitive and non-cognitive abilities and qualities to perform effectively in the scope of professional practice). Lacking an understanding of medical culture and the nature of medical settings is a highly compromising deficit. It leads to mission hostile HIT devices such as shown here. There needs to be much better talent management in that regard.
  • Suboptimal HIT vendor performance, and defective HIT devices, should not be tolerated. Repeat purveyors of such technology should be materially sanctioned for wasting precious healthcare resources. Whether this happens primarily in the courtroom, or in the court of "consumer opinion" by HIT buyers -- based on transparent consumer reports on HIT - remains to be seen.

-- SS

Addendum: a reader familiar with the UCSF situation largely confirms my suspicions as above regarding vendor capabilities and the vendor's biting off more than it could chew, greatly delaying deliverables. They did say, however, that I was not correct (in this case) about the issue of salesperson "promise the moon" behavior, and that this was not a factor in the project stoppage.