Showing posts with label EPIC. Show all posts
Showing posts with label EPIC. Show all posts

Saturday, 9 July 2016

Physicians go flatline on EHR enthusiasm

In a new study, physicians' enthusiasm levels for EHR's seem to resemble this EKG:




Do physicians really experience a satisfaction 'J-curve' with EHRs?
Max Green 
July 6, 2016 
http://www.beckershospitalreview.com/healthcare-information-technology/do-physicians-really-experience-a-satisfaction-j-curve-with-ehrs.html 

There's a school of thought about EHR adoption that suggests physicians experience an initial decrease in their positive perceptions of the technology, but over time those levels creep back up and ultimately surpass their pre-implementation perceptions. But does that J-curve actually exists for EHRs? A new study in the Journal of the American Medical Informatics Association says no. 

That "school of thought" must be from U.B.H. (Univ. of Blind Hyperenthusiasts) and O.U. (Ostrich University).

"[W]e did not find evidence for a J-curve pattern with respect to positive perceptions eventually exceeding baseline measures," the authors concluded. "Some measures followed a U-curve (returned to baseline), or flatlined, while most followed an L-curve (fell and remained below baseline)."

Translation: doctors hate the technology in its present form.

The study is based on a prospective longitudinal survey of Ann Arbor-based University of Michigan Health System physicians over the course of two years, from when they dropped their homegrown CareWeb EHR, for Epic's. Although all physicians received training on the new system and the system "invested substantial resources developing customized content," according to the paper, the only significant increase over baseline perception after two years of the new EHR was for documenting while in the exam room with patients. 

Surely, that accomplishment is worth the investment of hundreds of millions of dollars ...

"Future research is warranted to determine if positive perceptions eventually surpass baseline, and what interventions can help physicians use EHRs more effectively," the authors concluded.

The answer is "likely not."

In fact, the results of the new study are not surprising considering the not-so-glowing reviews of EHRs forwarded on to HHS in Jan. 2015 by the list of medical societies below (see link to the letter at my Jan. 28, 2015 post "Meaningful Use Not So Meaningful: Multiple medical specialty societies now go on record about hazards of EHR misdirection, mismanagement and sloppy hospital computing" at http://hcrenewal.blogspot.com/2015/01/meaningful-use-not-so-meaningul.html):


American Medical Association
AMDA – The Society for Post-Acute and Long-Term Care Medicine
American Academy of Allergy, Asthma and Immunology
American Academy of Dermatology Association
American Academy of Facial Plastic
American Academy of Family Physicians
American Academy of Home Care Medicine American Academy of Neurology
American Academy of Ophthalmology
American Academy of Otolaryngology—Head and Neck Surgery
American Academy of Physical Medicine and Rehabilitation
American Association of Clinical Endocrinologists
American Association of Neurological Surgeons
American Association of Orthopaedic Surgeons
American College of Allergy, Asthma and Immunology
American College of Emergency Physicians
American College of Osteopathic Surgeons
American College of Physicians
American College of Surgeons
American Congress of Obstetricians and Gynecologists
American Osteopathic Association
American Society for Radiology and Oncology
American Society of Anesthesiologists
American Society of Cataract and Refractive Surgery and Reconstructive Surgery
American Society of Clinical Oncology
American Society of Nephrology
College of Healthcare Information Management Executives
Congress of Neurological Surgeons
Heart Rhythm Society
Joint Council on Allergy, Asthma and Immunology
Medical Group Management Association
National Association of Spine Specialists
Renal Physicians Association
Society for Cardiovascular Angiography and Interventions
Society for Vascular Surgery

But, as the EHR pollyannas say, it'll all be better in ver. 2.0.

-- SS
Baca selengkapnya

Saturday, 30 April 2016

Back to Paper After U.S. Coast Guard EHR Debacle:  Proof of Hegel's Adage "We Learn From History That We Do Not Learn From History"?

Back to Paper After U.S. Coast Guard EHR Debacle: Proof of Hegel's Adage "We Learn From History That We Do Not Learn From History"?

I have become blue in the face writing about healthcare information technology mismanagement over the years.  In fact, the original focus of my 1998 website on health IT (its descendant now at http://cci.drexel.edu/faculty/ssilverstein/cases) was on HIT project mismanagement.

If this industry actually had learned anything from history, I would not be reading nor writing about brutally mismanaged HIT endeavors in 2016.  Sadly, that is not the case.

The Coast Guard, founded by Alexander Hamilton, has this as its motto and mission:

http://www.gocoastguard.com/about-the-coast-guard
Semper Paratus - Always Ready.

The Coast Guard is one of our nation's five military services. We exist to defend and preserve the United States. We protect the personal safety and security of our people; the marine transportation system and infrastructure; our natural and economic resources; and the territorial integrity of our nation–from both internal and external threats, natural and man-made. We protect these interests in U.S. ports and inland waterways, along the coasts, on international waters.

We are a military, multi-mission, maritime force offering a unique blend of military, law enforcement, humanitarian, regulatory, and diplomatic capabilities. These capabilities underpin our three broad roles: maritime safety, maritime security, and maritime stewardship. There are 11 missions that are interwoven within these roles.

It seems the Coast Guard personnel need personal protection from the HIT industry, for the motto of that industry, sadly appears to be something like "Stupra Acetabulus" (Screw the Suckers).

From Politico, one of only a few publications that in recent years has taken a critical approach to this industry and pulls no punches:

http://www.politico.com/story/2016/04/ehr-debacle-leads-to-paper-based-care-for-coast-guard-servicemembers-222412
EHR debacle leads to paper-based care for Coast Guard servicemembers
By Darius Tahir
04/25/16

The botched implementation of an electronic health records system sent Coast Guard doctors scurrying to copy digital records onto paper last fall and has disrupted health care for 50,000 active troops and civilian members and their families.

Five years after signing a $14 million contract with industry leader Epic Systems, the Coast Guard ended its relationship with the Wisconsin vendor, while recovering just more than $2.2 million from the company. But it couldn’t revert back to its old system, leaving its doctors reliant on paper.

This state of affairs is simple inexcusable.  It represents gross negligence and severe multi-axial incompetence at best - but likely primarily not by the Coast Guard, whose core competency does not include HIT.

There’s no clear evidence the EHR disaster has harmed patients, and a Coast Guard spokesman said the use of paper records hasn’t affected “the quality of health care provided to our people.”

Proof by lack of evidence is not reassuring in a debacle of this kind.  However, the Coast Guard admits that paper records aren't the clear and present danger the IT pundits make them out to be.

Politico is skeptical of the claim:

That seems unlikely. Without digital records, if a patient goes outside a Coast Guard clinic, it can take weeks for the paper record to follow him or her back to the Coast Guard, says Michael Little of the Association of the United States Navy. And since the Coast Guard primarily provides outpatient, rather than hospital, services, many of its patients seek outside care.

“It’s one thing if you’re doing paper-based [care] in Ohio, but what about if you’re on paper records in [an] icebreaker or cutter in Alaska, and you need your gall bladder removed?” said Little, the organization’s director of legislative affairs.

In this case, I disagree that the lack of records is so dangerous.  There's the telephone, FAX machines, the patient himself or herself, and the hand-carried note.  Used with care, those serve care reasonably well. 

With the Department of Veterans Affairs weighing whether to buy a top-of-the-line commercial electronic health record and the Pentagon beginning a multibillion-dollar EHR implementation, the Coast Guard case displays how poorly the process can go for the government, even when the biggest names in health IT are involved.

Not just the government.  I'd also argue that this shows that the "biggest names" are, at best, overextended, and at worst, badly needing external investigation as to their software development, customization, implementation and support practices, as well as hiring practices (e.g., see my August 15, 2010 post "EPIC's outrageous recommendations on healthcare IT project staffing"
at http://hcrenewal.blogspot.com/2010/08/epics-outrageous-recommendations-on.html) and contracting.

Reversion to a purely paper-based system is a rare event in the recent annals of electronic records, said Thomas Payne, a health IT expert at the University of Washington. “I can think of examples where that has happened, but in the last decade that is much less common.”

I believe that is because of the general invisibility of, and immunity from, the risks and harms that occur from "making do" with bad health IT due to financial pressures.  Hence one sees hair-raising examples like I wrote of at my Nov. 17, 2013 post "Another 'Survey' on EHRs - Affinity Medical Center (Ohio) Nurses Warn That Serious Patient Complications 'Only a Matter of Time' in Open Letter"at http://hcrenewal.blogspot.com/2013/11/another-survey-on-ehrs-affinity-medical.html where going back to paper to allow a complete rethinking of the EHR implementation would likely have been the safe response.

See also, for example, my July 2013 post "RNs Say Sutter’s New Electronic System Causing Serious Disruptions to Safe Patient Care at East Bay Hospitals" at http://hcrenewal.blogspot.com/2013/07/rns-say-sutters-new-electronic-system.html (there are links there to still more examples).

The Coast Guard is tight-lipped about the causes, timeline and responsibility for the debacle. “Various irregularities were uncovered, which are currently being reviewed,” a spokesman said.

The causes are all covered at http://cci.drexel.edu/faculty/ssilverstein/cases/, and have been since the late 1990s.  In the alternative, the book "Managing Technological Change: Organizational Aspects of Health Informatics" (http://www.amazon.com/Managing-Technological-Change-Organizational-Informatics/dp/0387985484) by Lorenzi & Riley does likewise for an even longer period, since the mid 1990s - for those willing or able to learn from history and from the pioneers

There’s no shortage of candidates: the service relied on five separate vendors to build the new system, and its own planning seems to have been at fault.

Lawmakers are looking into the matter, said a spokesman for the Senate Appropriations Committee, which is “monitoring the situation."

This is symptomatic, in my view, of the fact that there are a lot of "Beltway Bandit" IT consultant companies doing business, few of them very good.

Bungled implementation, followed by chaos

In September 2010, the Coast Guard bid out the contract to Epic Systems, then added an array of other contracts to software vendors and consultants to help implement it. Since 2010, the agency spent, on net, just more than $34 million on health IT.

In a January 2011 speech, Coast Guard Chief Medical Officer Mark Tedesco cited the success of Epic installations at Kaiser Permanente and Cleveland Clinic. He predicted that the Epic implementation would improve the health of its population and save money.

Overall it’s a cheaper system for us to run than to upgrade to [the next generation military EHR], because of what that would’ve meant to us infrastructure-wise and support-personnel wise,” he said.

It's stunning to think what this says about the next-generation military EHR.  The previous one was not very good, either (see my June 4, 2009 post "If The Military Can't Get Electronic Health Records Right, Why Would We Think Conflicted EHR Companies And IT-Backwater Hospitals Can?" at http://hcrenewal.blogspot.com/2009/06/if-military-cant-get-electronic-health.html). 

Trouble, apparently, struck quickly. The solicitation for the EHR contract envisioned rolling out the software within six months at two to three pilot sites, before deploying it to a total of 43 clinics and the sickbays aboard the Coast Guard’s fleet.

That didn’t occur; the system never deployed to any clinic or cutter, said Eric Helsher, an executive with Epic. The next missed deadline was March 2012, which Trent Janda — the Coast Guard doctor serving as project leader — announced in a summer 2011 newsletter of the Uniformed Services Academy of Family Physicians.

One can only wonder what penalties the contract called for if the goals and timelines were not met.  That software was not deployed even to any pilot sites is nearly unimaginable to me.

As Janda set the new goal, he acknowledged there had been “multiple hurdles and delays,” and explained that the service had expanded its ambitions.

“Immediately upon award of the contract, we began a comprehensive analysis of the clinical workflows and existing information systems,” Janda wrote. “Many of the weaknesses became apparent as we compared ourselves to industry standards and best practices. Frequently, a weakness would lead to others, ultimately leading to the need for an additional system. The work-flow analysis quickly grew into a system wide re-engineering project like a snowball rolling down the mountainside.”

This sounds like a groundbreaking level of project mayhem and chaos, even for HIT.

The comment reveals that the agency failed to do necessary advance planning, says Theresa Cullen, an informatics executive with the Regenstrief Institute who formerly worked with Veterans Health Affairs and the Indian Health Service.

“They should have done a full needs assessment,” she said. “One would have normally done the workflow evaluation prior to the release of the RFP.”

If true, I believe it was an obligation of EPIC and the multiple contractors to have pointed that out to their future customer, and adjusted their bids accordingly, taking into account the time and resources needed for this type of work - or not placed a bid at all.  Such deficiencies and what they mean towards project progress and failure are obvious - to anyone who's learned from history.

... Cullen also found it odd that the Coast Guard didn’t hire consultants to implement the new system until September 2012. The service ended up hiring Leidos, which also maintained its old EHR.

The Coast Guard further complicated the process by deciding to team up with the State Department. Its original request was complicated enough, with installations spanning six time zones. The partnership with State meant implementing across 170 countries. (A spokeswoman for State said the agency was investigating its options, but refused additional comment).

The sheer number of sites led Cullen to question whether Coast Guard and State had devoted enough resources to the project. Between Epic and Leidos, the project was budgeted for roughly $31 million. That was “an inadequate amount of funding for what you’re asking to do,” she said. Consultants receive roughly $100 an hour, and Epic’s work with clinicians is time-consuming.

Again, those hired knew, should have known, or should have made it their business to know that under such conditions, if true, project failure was the predictable outcome.  They are supposed to be the HIT experts, after all, not the Coast Guard.

While a very efficient health care system could implement the EHR, she said, the Coast Guard lacks that reputation. She speculated that Epic intentionally underbid the contract. (Epic’s Helsher said that “the contract was viable and we were fully motivated to lead a successful install.”)

Someone is right, and someone is wrong.  I leave it to the reader to decide who was correct and who wasn't.

Anecdotes of further delays pepper various newsletters and reports from 2012 through 2015. Server failures scuttled a pilot rollout in 2014, then developed into deeper problems, and last July the systems started failing on a more regular basis.

Perhaps the "anecdotes" need to be turned into "teachable moments" through legal discovery by federal law enforcement.

The Coast Guard advised retirees and dependents that month that, due to incompatibility between its EHR and the Department of Defense’s new medication reconciliation system, they couldn’t get their prescriptions filled at Coast Guard clinics.

Around Labor Day, Coast Guard health care personnel were directed to copy information from electronic files onto paper, for fear of losing their data.

That is just about the most pathetic sentence I've ever had to read in my 24 years in Medical Informatics.

... doctors are frustrated. One complained in the Uniformed Services Academy of Family Physicians newsletter of “unique challenges which seemed to revolve around many electronic record keeping changes.” “The question we pose is, how is this affecting shipboard life?” Little said. “This is the most important thing that’s happening right now in the Coast Guard.”

My advice to the Coast Guard is to treat the IT invaders and consultants as it would a invading maritime fleet from a hostile nation.

The vendors who worked with the Coast Guard either don’t know what went wrong, or aren’t telling. Leidos — also the lead company implementing the Pentagon’s EHR project — declined comment, as did Lockheed Martin, which was contracted to implement access to the EHR through mobile devices, and Apprio, which was to provide credentialing services.

I believe they have a very good idea of "what went wrong", and aren't telling (per the Fifth Amendment)?  If they have "no idea" what went wrong, what, I ask, are they doing in the IT consulting business?

... The EHR giant [EPIC] says it’s not entirely clear why the Coast Guard pulled the plug. But the situation wasn’t Epic’s fault, company executive Eric Helsher said.

They pulled the plug out of fear for their members' well-being, hopefully.

It seems everyone seeks to escape culpability, with the blame placed on the customer.

The Coast Guard spokesman said the decision was “driven by concerns about the project's ability to deliver a viable product in a reasonable period of time and at a reasonable cost.”

It seems there's still some who don't continue down the sunk-cost fallacy road (https://www.logicallyfallacious.com/tools/lp/Bo/LogicalFallacies/173/Sunk_Cost_Fallacy) and are willing to walk away from bad HIT.

... In general, software contracts deserve more scrutiny, said Kingston, who served on the House Appropriations Committee. “These things don’t get the scrutiny a weapons system does.”

Considering the reputation of military costs, that's saying quite a lot.  The lesson that should have been learned from history is that HIT is both exploratory, and a relative free-for-all.

Caveat emptor.

One last piece of (free!) advice for the Coast Guard leadership.

Read this paper:

Pessimism, Computer Failure, and Information Systems Development in the Public Sector.  (Public Administration Review 67;5:917-929, Sept/Oct. 2007, Shaun Goldfinch, University of Otago, New Zealand).  Cautionary article on IT that should be read by every healthcare executive documenting the widespread nature of IT difficulties and failure, the lack of attention to the issues responsible, and recommending much more critical attitudes towards IT.  linkto pdf

That may be the most valuable learning experience of all for their next attempt to implement EHRs.

-- SS
Baca selengkapnya

Wednesday, 6 April 2016

What is more important in healthcare, computers, or nurses and other human beings?  Southcoast Health cutting dozens of jobs on heels of expensive IT upgrade

What is more important in healthcare, computers, or nurses and other human beings? Southcoast Health cutting dozens of jobs on heels of expensive IT upgrade

That I even have to ask the question on the title of this post is a tragedy and a scandal.

I've written a number of posts on this blog about hospitals laying off staff and even put in financial jeopardy due to EHR implementation, e.g., my June 2, 2014 post "In Fixing Those 9,553 EHR "Issues", Southern Arizona’s Largest Health Network is $28.5 Million In The Red" at http://hcrenewal.blogspot.com/2014/06/in-fixing-those-9553-ehr-issues.html and numerous others indexed under "healthcare IT costs" at query link http://hcrenewal.blogspot.com/search/label/healthcare%20IT%20cost

This often occurs due to poor project planning, overconfidence, underestimation of complexity and even incompetence, that drives up electronic records system costs way over estimates. 

It's happened again:


Southcoast Health cutting dozens of jobs on heels of expensive IT upgrade
Mar 30, 2016, 11:25am EDT
Updated Mar 30, 2016, 11:31am EDT
http://www.bizjournals.com/boston/blog/health-care/2016/03/southcoast-health-cutting-dozens-of-jobs-on-heels.html

Stung by losses linked to costly technology upgrades, Southcoast Health is laying off 95 employees just a year after finalizing a similar staffing cut.

The cuts represent 1 percent of Southcoast’s 7,251 workforce, and will happen across the care provider's three hospitals in Fall River, Wareham and New Bedford. All levels of hospital staff will be affected, officials said.

Southcoast employees were notified of the cut Wednesday morning. The cuts come as the hospital negotiates a merger with Care New England, a four-hospital system in Rhode Island.

The care provider said the cuts stemmed from training costs associated with the installation of a $100 million records system, known as Epic. Similar operating challenges have been reported by other Massachusetts care providers in the midst of Epic upgrades and installations.

I note that $100 million can purchase an entire new hospital wing or facility.

Training costs, of all things, should have been factored into the original project plans.  It's not as if this issue is an unknown in an industry and product extant for several decades now.

Also, IMO the word "challenges" should be altered to "challenged" to describe the institutional geniuses responsible for debacles like this.

Training costs for the system, which went live in October, contributed to a $9.9 million operating loss in the first quarter of fiscal 2016, which ended Dec. 31. Hospital executives said similar expenses have impacted the bottom line in the current quarter, which ends Thursday.

So, training costs for the EHR devoured profits from an increasing revenue stream as below, plus consumed enough to leave a near $10 million loss. Stunning.

“These financial challenges are attributable to higher-than-budgeted operating expenses, largely a result of our Epic implementation,” said Southcoast president and CEO Keith Hovan, in a letter to employees. “During the first two quarters of this fiscal year, revenue has grown positively at a rate of 4 percent – a significant accomplishment, particularly given the lack of a flu season. However, expenses have grown at 6 percent during that time, which is an untenable variance that must be corrected.”

I note that the hospital system might have realized their cost underestimations via reading the literature a bit, including but not limited to my completely free academic site at http://cci.drexel.edu/faculty/ssilverstein/cases (in existence in various flavors since 1998), and this very blog.

Hovan went on to ask employees for recommendations to reduce costs, going so far as to tell employees to reach out to him directly.

How about reducing IT expenditure and laying off IT personnel responsible for the cost underestimates?  Costing is supposed to be a core competence of management information systems (MIS) personnel in those IT departments.

... Approximately 70 people were let go in October 2014, and another 35 were let go in January 2015.

The hospital still has 339 job openings for a number of clinical roles. Cohenno wouldn’t detail what kinds of jobs the hospital was eliminating, but said employees affected by today’s layoffs will be encouraged to apply to open positions.

Some consolation for being fired to maintain the good health of a computer.

The solution to this problem is for hospital executives to actually learn more about what they're getting into in HIT acquisition, implementation and operation, instead of simply believing the marketing hype coming from the HIT industry and its cybernetic hyper-enthusiasts.

That means reading far more than typical industry marketing BS, a.k.a. performing robust due diligence.

-- SS
Baca selengkapnya

Thursday, 17 March 2016

Criminal matter for the Attorney General of NY?  Hail the gods of medical computing, and the need for human sacrifice.  NYC’s $764M medical records system will lead to ‘patient death’: insiders

Criminal matter for the Attorney General of NY? Hail the gods of medical computing, and the need for human sacrifice. NYC’s $764M medical records system will lead to ‘patient death’: insiders

I believe the suffering and death of my mother in 2010-2011 due to EHR flaws - including but not limited to lack of essential confirmation dialogs on medication deletion at triage, lack of notification messages informing down-line staff of such action by unqualified personnel (inadequate support of teamwork), and other issues - lends me some moral standing to comment on the following as a horrifying and potentially criminal matter.  (See http://khn.org/news/scot-silverstein-health-information-technology/).


Two back-to-back articles appeared in the New York Post:


NYC’s $764M medical records system will lead to ‘patient death’: insiders
By Michael Gartland
March 15, 2016
http://nypost.com/2016/03/15/nycs-764m-medical-records-system-will-lead-to-patient-death-insiders/

and

Hospital exec [CMIO] quits, compares $764M upgrade to Challenger disaster
By Michael Gartland
March 16, 2016
http://nypost.com/2016/03/16/hospital-exec-quits-compares-764m-upgrade-to-challenger-disaster/ 


It is well-known and indisputable that this technology can and does injure and kill, especially when poorly designed, defective, poorly implemented, or all of the above.  See for instance the ECRI EHR risk Deep Dive study results at http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html.

Any official in leadership of health IT who denies this - or sidesteps it - or makes excuses for compromises on health IT safety, especially in view of dire warnings from clinician experts - in 2016 is guilty of conduct of the type below:

http://www.legalmatch.com/law-library/article/criminal-negligence-laws.html
What is Criminal Negligence?

Under some criminal law statutes, criminal negligence is defined as any type of conduct that “grossly deviates” from normal, reasonable standards of an ordinary person.  It generally involves an indifference or disregard for human life or for the safety of people.  Sometimes the definition for criminal negligence also requires a failure to recognize unjustifiable risks associated with the conduct.

Examples of criminally negligent behavior may include knowingly allowing a child to be in very dangerous conditions, or driving in an extremely irresponsible way.  Criminal negligence is less serious than intentional or reckless conduct.  Generally, reckless conduct involves a knowing disregard of risks, while negligence involves an unawareness of the risks.

The two articles reflect a good possibility that the politics of what I'd once termed "cybernetics über alles" has trumped patient safety concerns in NYC.

Here's details from the first article:

A new $764 million medical records system is launching at the municipal hospital system on April 2 — even though insiders warn it isn’t ready and patients will suffer.

The soft launch of the electronic system Epic is scheduled at Elmhurst and Queens hospitals.

“Sooner or later, it will crash,” said one source involved in the project. “There will be patient harm — patient harm and patient death.”

That sounds like insiders warning of far more problems than mere crashes causing patient harm and death, a brave act considering possible retaliation.

I wonder if the users of this EPIC system are having imposed on them the speech and though controls imposed on users at University of Arizona (see my Oct. 3, 2013 post "Words that Work: Singing Only Positive - And Often Unsubstantiated - EHR Praise As 'Advised' At The University Of Arizona Health Network" at http://hcrenewal.blogspot.com/2013/10/words-that-work-singing-only-positive.html).

Sources say Dr. Ramanathan Raju, who runs the municipal network, NYC Health + Hospitals, is under the gun from City Hall to meet the deadline and fears he’ll be fired if he doesn’t.

“Raju has said too many times to count that the Mayor’s Office has told him if April 1st doesn’t happen, then Ram will lose his job,” one source said.

The source added that Raju has threatened to fire top executives if the project doesn’t launch on time.

If this is true, than the "gun" from City Hall is aimed straight at patients, and if patients indeed are mortally affected, the responsible officials might be deemed accessories to murder.

I add that this type of situation represents fundamental and severe mismanagement, as I'd been writing about since the late 1990's at my academic site "Contemporary Issues in Medical Informatics: Good Health IT, Bad Health IT, and Common Examples of Healthcare IT Difficulties" at http://cci.drexel.edu/faculty/ssilverstein/cases/.

The hospital system is already on City Hall’s watch list, having required a $337 million bailout in January to stay afloat. 

Money for EHR's grows on trees.

Note other hospitals where EHR implementations led to financial disaster (e.g., http://hcrenewal.blogspot.com/2014/06/in-fixing-those-9553-ehr-issues.html, http://hcrenewal.blogspot.com/2013/05/clouded-visionary-leadership-wake.html, http://hcrenewal.blogspot.com/2013/06/want-to-help-hospital-go-bankrupt-get.html, http://hcrenewal.blogspot.com/2014/06/100-million-epic-install-dampens.html as examples).

Insiders contend that the only safe way to roll out Epic is to take more time — about three months — to address several key issues.

One is planning for a crash, which some consider almost inevitable because the new setup hasn’t been configured to work with systems at other hospitals or with some of its own internal billing and tracking software.

Existing patient data also has to be transferred from the old system — a process that would normally take six months, but which was shoehorned into less than one.

Going "live" with a half-baked EHR under such circumstances for political reasons, if these facts are true, would be, in my professional opinion, an act worthy of prison time if harm results.

“There are supposed to be all these dry runs,” a source said. “They haven’t been done.”

Again, if true, this reflects expediency at the expense of patient well-being, by rows of political hacks, fools and incompetents calling the shots in an area in which they have no business being involved.

City officials contend Epic remains “on-time and within budget.”

I have a feeling this will be revisited at some time in the future - in court.

A mayoral spokeswoman said there would be a round-the-clock effort to ensure there are no glitches. 

"No glitches?" 

That is a hollow promise that cannot be kept even under the best of circumstances.  Under the hellish circumstances described, such a statement is outright frightening. The Mayor truly has no clue about EHR "glitches", but I offer the many posts at query link http://hcrenewal.blogspot.com/search/label/glitch for his education.

Mr. Mayor, here's an example of EPIC and other EHR implementations under the best of circumstances.  These systems are so immensely complex, trying to be pressure-fit into a vastly complex, varying and changing environment, that to not heed CMIO and other expert warnings is the height of recklessness:


Of course, we are reassured that the crack team assigned the implementation duties will produce stellar results:

“NYC Health + Hospitals and its Epic implementation experts are prepared to implement the new system in Queens facilities beginning April 2, and have assembled a team of about 900 technicians and Epic experts who will work around-the-clock that week both in Queens and at remote data centers to ensure the transition to the new system goes as smoothly as possible,” said spokeswoman Ishanee Parikh.

EPIC experts like these?  From this link at the "Histalk" site on staffing of health IT projects, Aug. 16, 2010. Emphases mine:

Epic Staffing Guide 

A reader sent over a copy of the staffing guide that Epic provides to its customers. I thought it was interesting, first and foremost in that Epic is so specific in its implementation plan that it sends customers an 18-page document on how staff their part of the project. 

Epic emphasizes that many hospitals can staff their projects internally, choosing people who know the organization. However, they emphasize choosing the best and brightest, not those with time to spare. Epic advocates the same approach it takes in its own hiring: don’t worry about relevant experience, choose people with the right traits, qualities, and skills, they say. 

The guide suggests hiring recent college graduates for analyst roles. Ability is more important than experience, it says. That includes reviewing a candidate’s college GPA and standardized test scores. 

I bet many readers were taught by their HR departments to do behavioral interviewing, i.e. “Tell me about a time when you …” Epic says that’s crap, suggesting instead that candidates be given scenarios and asked how they would respond. They also say that interviews are not predictive of work quality since some people just interview well. 

Don’t just hire the agreeable candidate, the guide says, since it may take someone annoying to push a project along or to ask the hard but important questions that all the suck-ups will avoid. 

Epic likes giving candidates tests, particularly those of the logic variety.

The part about "not worrying about relevant experience" and about "hiring recent college graduates as HIT project analysts" is bizarre if true, and downright frightening.

Medical environments and clinical affairs are not playgrounds for novices, no matter how "smart" their grades and test scores show them to be. These practices as described, in my view, represent faulty and dangerous advice on first principles.  The advice also is at odds with the taxonomy of skills published by the Office of the National Coordinator I outlined at the post "ONC Defines a Taxonomy of Robust Healthcare IT Leadership."

The second NY Post article cited above is even more dire:

A senior official was so worried a new $764 million medical records system for the municipal hospital system was launching too early that he resigned, comparing it to the disastrous space shuttle Challenger launch in 1986.

In a “resignation and thank-you” email last week, Dr. Charles Perry urged colleagues at NYC Health + Hospitals — formerly the Health and Hospitals Corp. — to sound the alarm and press for an “external review” to stop the system from going live next month.

Perry was chief medical information officer of Queens and Elmhurst Hospital Centers, the first scheduled to get the new electronic medical data system.

When a CMIO - a role I held in the mid 1990s -  resigns under such circumstances, a project should be halted in its tracks and external examination begun.  Instead, it appears we have spin control.

In his email, Perry offered a comparison to the launch of the Challenger — aboard which seven crew members died when it exploded 73 seconds after liftoff on Jan. 28, 1986 — and cited a presidential panel’s report examining how the disaster occurred.

That is as dire and direct a warning as they come.  Unqualified individuals who second guess such a warning should be held legally accountable for adverse outcomes.

(Such a warning letter about EHRs now sits as "Exhibit A" in the lawsuit complaint regarding my dead mother.  It had not been heeded.)

“For a successful technology, ­reality must take precedence over public relations, for nature cannot be fooled,” Perry wrote in his ­email, quoting from the report.

But fools in leadership roles in health IT think they can fool Mother Nature.

Perry went on to urge a short delay despite “vehement entreaties to make the April 1st date by officials and consultants with jobs and paydays on the line.”

This is exactly how patients end up maimed and dead.

Agency president Dr. Ramanathan Raju has repeatedly told colleagues his job is on the line if the deadline isn’t met, sources said.

Perry, a medical doctor with an MBA, declined to comment.

Maybe Raju should quit, too.  He should know that Discovery over such matters would not be very pleasant, especially if I am assisting attorneys in such matters - which could very well occur.

“He [Perry] took a stand,” said one insider. “He wasn’t going to take part in something that was going to compromise patient safety.”

It's good to know someone in Medical Informatics still has balls.

The idea that we’d jeopardize patients to meet a deadline is simply wrong,” said Karen Hinton, Mayor Bill de Blasio’s spokeswoman.

“If a patient safety issue is identified, the project will stop until it is addressed.

“NYC Health + Hospitals and its Epic implementation experts have assembled a team of about 900 technicians and Epic experts who will work around the clock through the week surrounding the transition in both Queens and at remote data centers to ensure we shift to the new system as smoothly as possible.”

It's been said that one expert who truly know what they're doing will always outperform 1,000 (or 900) generalists following the finest of "process" who are in over their heads (to wit, 900 generic musicians could never exceed the work of Beethoven or Brahms).

In this matter, I take the CMIO's word over the 900 techies and "experts", once having voiced such concerns myself.

-- SS

What is Criminal Negligence?

Under some criminal law statutes, criminal negligence is defined as any type of conduct that “grossly deviates” from normal, reasonable standards of an ordinary person.  It generally involves an indifference or disregard for human life or for the safety of people.  Sometimes the definition for criminal negligence also requires a failure to recognize unjustifiable risks associated with the conduct.
Examples of criminally negligent behavior may include knowingly allowing a child to be in very dangerous conditions, or driving in an extremely irresponsible way.  Criminal negligence is less serious than intentional or reckless conduct.  Generally, reckless conduct involves a knowing disregard of risks, while negligence involves an unawareness of the risks.
- See more at: http://www.legalmatch.com/law-library/article/criminal-negligence-laws.html#sthash.3YLT7ahF.dpuf

What is Criminal Negligence?

Under some criminal law statutes, criminal negligence is defined as any type of conduct that “grossly deviates” from normal, reasonable standards of an ordinary person.  It generally involves an indifference or disregard for human life or for the safety of people.  Sometimes the definition for criminal negligence also requires a failure to recognize unjustifiable risks associated with the conduct.
Examples of criminally negligent behavior may include knowingly allowing a child to be in very dangerous conditions, or driving in an extremely irresponsible way.  Criminal negligence is less serious than intentional or reckless conduct.  Generally, reckless conduct involves a knowing disregard of risks, while negligence involves an unawareness of the risks.
- See more at: http://www.legalmatch.com/law-library/article/criminal-negligence-laws.html#sthash.3YLT7ahF.dpuf

What is Criminal Negligence?

Under some criminal law statutes, criminal negligence is defined as any type of conduct that “grossly deviates” from normal, reasonable standards of an ordinary person.  It generally involves an indifference or disregard for human life or for the safety of people.  Sometimes the definition for criminal negligence also requires a failure to recognize unjustifiable risks associated with the conduct.
Examples of criminally negligent behavior may include knowingly allowing a child to be in very dangerous conditions, or driving in an extremely irresponsible way.  Criminal negligence is less serious than intentional or reckless conduct.  Generally, reckless conduct involves a knowing disregard of risks, while negligence involves an unawareness of the risks.
- See more at: http://www.legalmatch.com/law-library/article/criminal-negligence-laws.html#sthash.3YLT7ahF.dpuf

What is Criminal Negligence?

Under some criminal law statutes, criminal negligence is defined as any type of conduct that “grossly deviates” from normal, reasonable standards of an ordinary person.  It generally involves an indifference or disregard for human life or for the safety of people.  Sometimes the definition for criminal negligence also requires a failure to recognize unjustifiable risks associated with the conduct.
Examples of criminally negligent behavior may include knowingly allowing a child to be in very dangerous conditions, or driving in an extremely irresponsible way.  Criminal negligence is less serious than intentional or reckless conduct.  Generally, reckless conduct involves a knowing disregard of risks, while negligence involves an unawareness of the risks.
- See more at: http://www.legalmatch.com/law-library/article/criminal-negligence-laws.html#sthash.3YLT7ahF.dpuf

What is Criminal Negligence?

Under some criminal law statutes, criminal negligence is defined as any type of conduct that “grossly deviates” from normal, reasonable standards of an ordinary person.  It generally involves an indifference or disregard for human life or for the safety of people.  Sometimes the definition for criminal negligence also requires a failure to recognize unjustifiable risks associated with the conduct.
Examples of criminally negligent behavior may include knowingly allowing a child to be in very dangerous conditions, or driving in an extremely irresponsible way.  Criminal negligence is less serious than intentional or reckless conduct.  Generally, reckless conduct involves a knowing disregard of risks, while negligence involves an unawareness of the risks.
- See more at: http://www.legalmatch.com/law-library/article/criminal-negligence-laws.html#sthash.3YLT7ahF.dpuf
Baca selengkapnya

Friday, 25 September 2015

Cambridge University Hospitals Trust IT Failures:  An Open Letter to Queen Elizabeth II on Repeated EHR Failures, Even After £12.7bn Wasted in Failed NHS National IT Programme

Cambridge University Hospitals Trust IT Failures: An Open Letter to Queen Elizabeth II on Repeated EHR Failures, Even After £12.7bn Wasted in Failed NHS National IT Programme

Dear Queen Elizabeth,

I am an American citizen who has written for years about healthcare information technology mismanagement (IT malpractice), dangers to patients of this technology when faulty in healthcare, and the huge mania or bubble that has surrounded this technology in a layer of fairy tales that has cost your Kingdom's treasury, as well as that of the U.S., dearly.

Your subjects seem unable to learn from their mistakes, or learn even from free material at sites such as this, or at my academic site at Drexel University at http://cci.drexel.edu/faculty/ssilverstein/cases/.

Instead of being appropriately skeptical, they spend your citizen's money extravagantly and with abandon on grossly faulty computing.  This results in serious health care meltdowns such as I observed at my September 22, 2011 post on your now-defunct National Programme for IT in the National Health Service (NPfIT).  That post was entitled "NPfIT Programme goes 'PfffT'" and is at http://hcrenewal.blogspot.com/2011/09/npfit-programme-going-pffft.html.

In that post I observed:

... [NPfIT] also failed because of collective ignorance of these domains [e.g., healthcare informatics, social informatics, etc. - ed.] among its leaders, and among those who chose the leaders. For instance, as I wrote here:


The Department of Health has announced the two long-awaited senior management appointments for the National Programme for IT ... The Department announced in February that it was recruiting the two positions as part of a revised governance structure for handling informatics in the Department of Health.

Christine Connelly will be the first Chief Information Officer for Health and will focus on developing and delivering the Department's overall information strategy and integrating leadership across the NHS and associated bodies including NHS Connecting for Health and the NHS Information Centre for Health and Social Care.
Christine Connelly was previously Chief Information Officer at Cadbury Schweppes with direct control of all IT operations and projects. She also spent over 20 years at BP where her roles included Chief of Staff for Gas, Power and Renewables, and Head of IT for both the upstream and downstream business.

Martin Bellamy will be the Director of Programme and System Delivery. He will lead NHS Connecting for Health and focus on enhancing partnerships with and within the NHS. Martin Bellamy has worked for the Department for Work and Pensions since 2003. His main role has been as CIO of the Pension Service.

Excuse me. Cadbury Schweppes (candy and drink?) The Pension Service? As national leaders for healthcare IT?

Also see my August 2010 post "Cerner's Blitzkrieg on London: Where's the RAF?" at http://hcrenewal.blogspot.com/2010/08/cerners-blitzkrieg-on-london-wheres-raf.html.

It's clear medical leaders in the UK learned little from the £12.7bn NPfIT debacle.  Now we have this:

Addenbrooke's Hospital consultants concerned over online records
BBC News
31 July 2015
http://www.bbc.com/news/uk-england-cambridgeshire-30393575

A £200m online patient-record system has been "fraught with problems" and medics' concerns "seemingly overlooked", senior hospital consultants have claimed.

A letter seen by the BBC reveals management at Addenbrooke's and Rosie hospitals in Cambridge were told of "serious" issues last month.  It came after the hospitals transferred 2.1 million records in October.

The trust said "unanticipated" issues led to "more than teething problems". 

The hospital is the first in the UK to use Epic's eHospital system, which is used in hospitals in the US.

To the CEO, these problems are just "hiccups":

... Chief executive Dr Keith McNeil admitted there had been "more than teething problems" and "some of it was anticipated and some of it was unanticipated". The "unanticipated" problems included problems with blood tests and "one of the busiest periods in the hospital's history", he said. He added: "We're profoundly sorry about that... people will understand that you can't do an information technology implementation of this size without some hiccups.

"Hiccups" are a euphemism for incompetence in system design, implementation and testing before it is used on live patients, Your Majesty.  I also note that a close relative of mine, and numerous other patients I know of are severely injured or dead due to these "hiccups."  

And now this:

Addenbrooke's and Rosie hospitals' patients 'put at risk'
BBC News
22 September 2015
http://www.bbc.com/news/uk-england-cambridgeshire-34317265

One of the UK's biggest NHS trusts has been placed in special measures after inspectors found it was "inadequate".

Cambridge University Hospitals Trust, which runs Addenbrooke's and the Rosie Birth Centre, was inspected by the Care Quality Commission in April and May.

Inspectors expressed concerns about staffing levels, delays in outpatient treatment and governance failings.

... Prof Sir Mike Richards, the Care Quality Commission's (CQC) chief inspector of hospitals, said while hospital staff were "extremely caring and extremely skilled", senior management had "lost their grip on some of the basics".

"[Patients] are being put at risk," he said. "It is not that we necessarily saw actual unsafe practice but we did see they would be put at risk if you don't, for example, have sufficient numbers of midwives for women in labour."

The trust, which is said to be predicting a £64m deficit this year, has apologised to patients.

I note that these hospitals had been the beta site for the first implementation of U.S. EHR maker EPIC company's product of the same name.  That £64m deficit looks a bit suspicious for IT overspend; for example see this U.S. hospital's experience of going in the red over fixing 10,000 "issues" (problems) with EPIC, in my post of June 2, 2014:  "In Fixing Those 9,553 EHR "Issues", Southern Arizona’s Largest Health Network is $28.5 Million In The Red" at http://hcrenewal.blogspot.com/2014/06/in-fixing-those-9553-ehr-issues.html.

... Perhaps the most worrying aspect of the Addenbrooke's story is not that such a world-renowned hospital has ended up in a predicament like this, but rather that it happened so quickly.

A year ago the trust which runs the hospital - Cambridge University Hospitals NHS Foundation Trust - wasn't even on the Care Quality Commission's radar in terms of being a failing centre.

I suggest a deep connection between this rapid fall, and the rapid rise of an EHR - an antiquated term for what is now an enterprise command-and-control system for hospitals.

... In fact, two years ago - as the regulator was embarking on its new inspection regime - it was among the band of hospitals considered to be the safest, according to the risk-rating system at the time.

But now a hospital which can boast to being a centre of excellence for major trauma, transplants, cancer, neurosurgery, genetics and paediatrics, has been judged to be a basket case and will join the 12 other failing hospitals already placed in special measures.

In my view, a major disruptive technology such as a new EHR is the Number One suspect in such a fall.

... Certainly it seems to have made mistakes - as the troubles with its £200m computerised patient records programme illustrates - but it's hard to escape the feeling that this is just the tip of the iceberg.

The "troubles with its £200m computerised patient records programme" is likely the iceberg, not just its tip.

The Care Quality Commission ("The independent regulator of health and social care in England", http://www.cqc.org.uk/) investigated these hospitals and issued a report, located at http://www.cqc.org.uk/location/RGT01/reports.

Among their key findings were:

Introducing the new EPIC IT system for clinical records had affected the trust’s ability to report, highlight and take action on data collected on the system. 

Excuse me?   Spend £200m on a computer system, and the result is impaired ability to report, highlight and take action on data collected?  Something is very wrong here.

 ... Although it was beginning to be embedded into practice, it was still having an impact on patient care and relationships with external professionals.

Clearly, the CQC does not mean a positive impact.

... Medicines were not always prescribed correctly due to limitations of EPIC, although we were assured this was being remedied.

Spend £200m on a computer system and the result is medicine prescription impairment (with the risks to patients that entails)?  Excuse me?

If those "limitations" affect these British hospitals, what "limitations" on getting prescriptions correct exist in all the U.S.-based hospitals that use this EHR, I ask?

... There was a significant shortfall of staff in a number of areas, including critical care services and those caring for unwell patients. This often resulted in staff being moved from one area of a service to another to make up staff numbers. Although gaps left by staff moving were back-filled with bank or agency staff, this meant that services often had staff with an inappropriate skills mix and patients were being cared for by staff without training relating to their health needs.

I suspect many staff were so unhappy with the EHR that they left, and recommended others not come.

Despite this patients received excellent care.

Odd how patient care and safety is never affected by bad health IT, as in the myriad stories at this site under the indexing key "patient care has not been compromised" (http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised).

... Clinical staff were not always able to access the information they required – for example, diagnostic tests such as electrocardiographs (ECGs) to assess and provide care for patients. This was because ECGs had to be sent to a central scanning service to be scanned into the electronic recording system [a.k.a. EHR] once the patient had been discharged. This meant their ECGs would not be available for comparison purposes if a patient was re-admitted soon after discharge.

Very, very bad IT planning, potentially putting unstable patients at risk.  Cybernetic miracles always have "fine print" that needs be read by skeptical managers BEFORE implementation.

Where agency staff were used, they were not always able to access information about patients they were supporting. 

 Ditto.

... Some staff told us there were no care plans on the new IT system.  Some staff told us the doctors’ orders had replaced care plans on the new EPIC IT system. These orders were task-orientated and did not always reflect the holistic needs of the patients.

This defective arrangement sounds like it was designed by non-clinicians.   The hubris and arrogance of non-clinicians sticking their heads into clinical issues - especially those of an IT-management background - must be witnessed to be fully comprehended.  It is my belief that such individuals should be subject to the liability as are the clinicians whose work increasingly depends on these IT systems.   If you dare to stick your neck into clinical affairs regarding systems upon which clinicians depend, you should be subject to the same liabilities as a clinician.  Unfortunately, this rarely if ever occurs.

 ... Whilst there were up-to-date evidence-based guidelines in place, we were concerned that these were not always being followed in maternity. This included FHR monitoring, VTE and early warning score guidelines. Staff were competent and understood the guidelines they were required to follow, however, lack of staffing and familiarity with the computer system (EPIC) made this difficult.

The point being missed here is that paper records required no massive multi-hundred page training manual in order to to perform basic functions such as the above.  The complexity of EHRs is costly, unnecessary, impairs clinicians and the solution is a massive scale back and simplification of these systems' complexity and scope.  Unfortunately, that, too is unlike to happen until the negative impacts become increasingly visible and intolerable - a meltdown I predict will occur, eventually.

... Since the introduction of EPIC, outcomes of people’s care and treatment was not robustly collected or monitored. For example, there was no maternity dashboard available since December 2014.

Again, spend £200m and have this result?  Something is seriously wrong here.  I suspect it is that personnel no longer had the time to perform monitoring, as they were likely distracted and struggling to keep afloat with more fundamental medical issues (like keeping major mishaps from occurring) using a complex and buggy EHR system.

That theory is likely confirmed by the following:

... At unit level we observed examples of excellent leadership principles; however, leadership of the directorate overall required improvement. This was because senior managers had not responded appropriately or in a timely way to known and serious safety risks, there was a general lack of service planning, and because key performance data was not being collected robustly and therefore not being analysed. We recognised that EPIC was the root cause of the problems with data collection, and that prior to its introduction in October 2014 many of the data collection issues were not apparent, however, improving this issue was not seen as a priority.

Management, I suspect, became complacent due to their infatuation with cybernetics and a belief that with a big-name EHR in place, operational ills were accounted for and they could relax.  (I've written of this phenomenon as the "syndrome of inappropriate overconfidence in computing.")  Management complacency, bad health IT and struggling clinicians is a very, very bad combination.

... Staff understood their responsibilities for safeguarding children, and acted to protect them from the risk of avoidable harm or abuse. There were enough medical staff but there were nursing shortages in some areas, such as in the day unit and in the neonatal unit. The new ‘EPIC’ (a records management system) computer system added to pressures on staff but effective temporary solutions helped to protect patients.

In other words, workarounds were used to get around the work-impeding EHR.  Workarounds introduce yet more risk.

... the electronic records system (EPIC) created significant numbers of delayed discharges that impacted on patients receiving end-of-life care.  ... Many staff said they had struggled with EPIC and it was time consuming. The specialist palliative care team found patients dropped off the system, so kept two lists to avoid losing patients.

One does not struggle with paper records.  (My current colleagues tell me the EHR struggle is non-ending.)  I further note that a computer system's rights, it appears, took precedence over patients' dying with dignity.

... While introducing EPIC, processes to deal with remaining paper records were unclear. For example, staff documented follow-up appointment requests on notepads. Paper records which were not stored in EPIC were inconsistently stored within the outpatients department. Inaccurate discharge summaries led to a risk that patients would not receive appropriate follow up care.

A fetish to totally eliminate paper, even where paper is the best medium for a purpose (e.g., as here:  http://cci.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story), creates major chaos and increases risk.

In conclusion, Your Highness, it might benefit your citizens (and those of the U.S.) if a national re-education programme were instituted to de-condition your leaders from unfettered belief in cybernetic miracles in medicine, a mental state they attain in large part due to mass EHR vendor and pundit propaganda.

A more sober mindset is recommended by your subject Shaun Goldfinch in "Pessimism, Computer Failure, and Information Systems Development in the Public Sector" (Public Administration Review 67;5:917-929, Sept/Oct. 2007, then at the University of Otago, New Zealand): 

The majority of information systems developments are unsuccessful. The larger the development, the more likely it will be unsuccessful. Despite the persistence of this problem for decades and the expenditure of vast sums of money, computer failure has received surprisingly little attention in the public administration literature. This article outlines the problems of enthusiasm and the problems of control, as well as the overwhelming complexity, that make the failure of large developments almost inevitable. Rather than the positive view found in much of the public administration literature, the author suggests a pessimism when it comes to information systems development. Aims for information technology should be modest ones, and in many cases, the risks, uncertainties, and probability of failure mean that new investments in technology are not justified. The author argues for a public official as a recalcitrant, suspicious, and skeptical adopter of IT.

Such a mindset would be helpful in preventing massive wastes of healthcare Pounds, Euros and Dollars better spent on patient care than on cybernetic pipe dreams.

Sincerely,

S. Silverstein, MD
Drexel University
Philadelphia, PA

------------------

Addendum:

I would like to hear from those in the know if my suspicions are correct.  Please leave comments.

-- SS
    Baca selengkapnya