Showing posts with label Patient care has not been compromised. Show all posts
Showing posts with label Patient care has not been compromised. Show all posts

Monday, June 16, 2014

Full Moon Friday the 13th: Computers down at Vermont's largest hospital

A health IT "glitch" hit in Vermont on Full Moon Friday the 13th (have some werewolf with your bad luck!)

Dark Shadows' Quentin Collins (David Selby) in a foul full-moon mood.

Note, however, that "bad luck" has little or nothing to do with mission-critical healthcare IT mass outages.  Mismanagement often does:

http://www.wcax.com/story/25773022/computers-down-at-vermonts-largest-hospital

Computers down at Vermont's largest hospital

Posted: Jun 13, 2014 4:12 PM EST Updated: Jun 13, 2014 4:12 PM EST
BURLINGTON, Vt. -
A major, systemwide computer problem at Fletcher Allen Health Care in Burlington Friday.

The hospital says the computer system went down at 9:45 a.m. The glitch means doctors and nurses could not enter patient information into computers.

"Glitch" is an unfortunate euphemism for potentially harmful or deadly computer malfunctions, often due to mismanagement of that technology. See query link http://hcrenewal.blogspot.com/search/label/glitch.

Hospital spokesperson Mike Noble says information is now being recorded manually [i.e., on paper - ed.] Noble says the staff continues to provide the same care as normal and no surgeries were canceled because of the computer issue.

Noble says the issue appears to be an internal problem and not something from an outside computer provider.

It’s not known when the problem will be corrected.

This is yet another "the systems that revolutionize healthcare against all of paper's ills have all gone down, we don't know when they will be fixed, but patient care has not been compromised because we are resorting to paper" story (more at query link http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised). 

-- SS

Masters of the Obvious at Athens Regional Medical Center: Lack of clinician input, training, common sense created problems with Athens Regional electronic records system - but mostly lack of common sense


My early medical mentor, Dr. Victor P. Satinsky, had disdain for those whom he called "Masters of the Obvious", who proffered profound words of wisdom that were in fact common-sensical or well-accepted, as if they'd invented those words personally.

I think it's fair to say that after countless publications dating back decades, pointing out the essential role of clinical leadership in the development of clinical tools such as healthcare information technology systems, that such involvement is now a standard of care that reasonable hospital leadership would mandate when spending tens of millions of dollars on potentially injurious or lethal systems.

Yet the physician revolt at Athens Regional Medical Center appears to be a result of its most senior leadership not keeping IT leadership on an appropriately short leash (a phenomenon that falls under the topical heading of "severe mismanagement"):

http://onlineathens.com/local-news/2014-06-14/lack-input-training-created-problems-athens-regional-electronic-records-system 

Lack of input, training created problems with Athens Regional electronic records system

By Kelsey Cochran
Athens Banner-Herald
Updated Sunday, June 15, 2014 

More input in the way Athens Regional Health Systems’ electronic health records system was implemented should have come from the clinicians who use it every day, and fewer decisions should have been made by the hospital’s information technology department, a top hospital administrator and two vice presidents of system vendor Cerner Corp. said this week, in the wake of criticism of the system by a number of physicians.

... Although some daily users of the system were involved in the planning and design process from the beginning, Cerner Vice President Michael Robin, who has worked closely with ARMC since the deal was first made, said his team noticed midway through its implementation that the hospital system’s IT team was leading the project, which is "atypical" of Cerner clients like ARMC, he said.

First, I don't think that IT team control of health IT projects is all that unusual.   Clinicians, even medical informaticists with cross-disciplinary expertise, rarely are more than "internal consultants" who may be ignored, as opposed to true leaders with executive presence and authority (e.g., control of budgets, grants of authority, and IT staff performance evaluation, hire and fire authority).

Second, where was the Board of Directors?  They were ultimately responsible for allowing the IT leadership in at a level beyond their collective heads.

Third, it's just a bit odd that the leader of the (failed) $20 billion National Programme for IT in the NHS, Richard Granger, said almost exactly the same thing about listening to end-users ca. 2007 (see http://hcrenewal.blogspot.com/2007/07/clinical-it-mayhem-is-good-for-it.html).  I as well as numerous other authors had similar observations, in some cases dating to the 1960's.  For example,  see my essays, some dating to the late 1990s at http://cci.drexel.edu/faculty/ssilverstein/cases/?loc=cases, and Dr. Donald Lindberg's quotes from 1969 at the page below from Morris Collen's book "A History of Medical Informatics in the United States 1950-1990."


EHR pioneer Dr. Donald A.B. Lindberg (http://www.nlm.nih.gov/od/roster/lindberg.html), 1969:  "Computer engineering experts per se have virtually no idea of the real problems of medical or even of hospital practice, and furthermore have consistently underestimated the complexity of the problems ... in no cases can these jobs be done, simply because they have not been defined with a physician as the continuing major contributor and user of the information." (Click to enlarge)

The essential nature of clinicians actually having input (and at a leadership level) into the design and implementation of clinical tools such as health IT is patently obvious.  Only in the perverse control-mentality of business information technology (a.k.a. MIS or management information systems, see http://hcrenewal.blogspot.com/2008/05/seedie-society-for-exorbitantly.html for the possible pre-electronic computer, tabulator-based roots of that culture) could such a precept even be questioned, let alone ignored.

... Moore, who took over as administrative lead on the electronic health record system after Thaw resigned, said some of the issues outlined in the physicians’ letter were real, and some were “theoretical.”

Translation: some of the complaints were accidents waiting to happen.

..."To the best of our knowledge, there was not patient harm or patient death.”

In other words, this is yet another story where the common, feel-good and ignorant refrain "but patient care has not been compromised" has reared its ugly head.  (I've made this type of claim a topical header at this blog.  See query link http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised for others.)

Assuming that's true - note that the impact of bad health IT can be delayed due to delayed effects of bad or missing information - this statement is, let me be impolite, vacuous on its face.

vac·u·ous (http://www.merriam-webster.com/dictionary/vacuous)

adjective \ˈva-kyə-wəs\
: having or showing a lack of intelligence or serious thought : lacking meaning, importance, or substance

It seems some simple facts apparently need to be explained to these geniuses.   I'll put it in caps just to make sure they understand some basic issues:

  • A HOSPITAL IS NOT A PLACE FOR RISKY INFORMATION TECHNOLOGY EXPERIMENTATION.   UNNECESSARY RISK IN HEALTHCARE IS A VERY, VERY BAD THING.
  • THE GOAL OF HOSPITALS IS NOT TO SUBJECT PATIENTS TO RISK VIA MISMANAGEMENT OF HEALTHCARE IT, AND THEN PROCLAIM "NOBODY WAS INJURED OR KILLED" AFTER THE PERPETRATORS OF THE MISMANAGEMENT ARE UPROOTED.
  • CLINICIANS DO NOT TOIL IN HOSPITALS TAKING CARE OF SICK PATIENTS SO THAT INFORMATION TECHNOLOGY PERSONNEL CAN HAVE COMFY JOBS AND COOL COMPUTERS.

One wonders if these points might be above the intellectual pay grade of those running hospitals - including boards - in 2014.

If nobody was injured or killed, it was due to happenstance, not due to appropriate due diligence and adherence to the standards of care essential in this healthcare sector - that is, healthcare information technology.

Depending on happenstance is not a good healthcare management strategy.

-- SS

Tuesday, March 25, 2014

This EHR "glitch" killed three-year-old Samuel Starr - but patient safety was not compromised

Actually, safety was compromised.

I have written repeatedly that the term "glitch", an often-seen euphemism (usually accompanied with the phrase "but patient care/patient safety was not compromised"), is really a term for life-threatening health IT bugs and malfunctions.  See query link http://hcrenewal.blogspot.com/search/label/glitch for examples of health IT "glitches" (retrieves multiple posts).




Here's a "glitch" that tragically killed this boy:

Three-year-old boy dies after new NHS computer system delays heart treatment

Mar 05, 2014
By James Tute

http://www.mirror.co.uk/news/uk-news/samuel-starr-death-nhs-computer-3209365

Coroner Maria Voisin rules that new booking system meant he did not receive life-saving treatment

A three-year-old boy died in his parents' arms after a new NHS computer system failed to schedule him for a vital heart scan, a coroner has ruled.

Samuel Starr was born with a congenital cardiac defect and needed surgery not long after he was born in 2010.

Although he made a good recovery doctors said he would need regular tests to check on his progress.

But he did not have a scan until 20 months after his first major operation because of a delay following the introduction of a new computer system, Cerner Millennium.

When he finally had the appointment doctors found Samuel needed open heart surgery. During the procedure, Samuel had a stroke.

A month later, after further complications, he died in the arms of his devastated parents, Catherine Holley and Paul Starr, at Bristol Royal Hospital for Children.

There are some in my field who would (and have) called incidents like this "anecdotes" or "bumps in the road."

Yet, as I've recently posted, an internationally-renowned healthcare safety tester, ECRI Institute (http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html), and the medical malpractice insurer of the Harvard medical community, CRICO (http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html), have confirmed cases like this are no mere anecdotes.  I estimate from their numbers, and from cases known to me personally and from descriptions of others, that on the order of ten thousand (that's likely low) patients annually are being injured and/or die as a result of bad health IT in the U.S. alone.  Lack of transparency about such incidents impairs knowing the true numbers.

Ms Holley wept as she told the hearing of the moment she kissed her son goodbye, saying: "He was a kind and gentle boy with a great understanding of the world.

"As we read Samuel his favourite stories, he died in our arms."

Avon Coroner Maria Voisin, recording a narrative conclusion, ruled the booking system meant Samuel was not seen and did not receive treatment.

This case somewhat reminds me of the case of a newborn whose x-ray test was done, but never looked at due to a bug in the software that scheduled films to be read, see http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html, case #2

Concluding a three-day inquest at Flax Bourton Coroner's Court in North Somerset, Ms Voisin said: "Samuel Starr was born with a complex cardiac disease. "He required surgery and regular check-ups at outpatients to manage his conditions.  "Due to the failure of the hospital outpatients booking system there was a five month delay in Samuel being seen and receiving treatment. "Samuel's heart was disadvantaged and he died following urgent surgery."

Just a "glitch."

Doctors diagnosed that Samuel had a restricted pulmonary artery - causing blood to easily flow away from his heart to his lungs - during a 20-week scan in pregnancy ... On March 3, 2010, Samuel underwent open heart surgery at Bristol Royal Hospital for Children. He was discharged six days later and referred to the Paediatric Cardiac Clinic at the Royal United Hospital (RUH) in Bath for check-ups.

In October 2010, Samuel had his first check-up, in which an echocardiogram, also known as an "echo", was carried out. Ms Holley said she was told the procedure would be next carried out early in the new year.

But it did not happen until April 2011 and an echo was not performed.  Paediatric cardiologist Dr Andrew Tometzki told the inquest he did not "deem it necessary" on that day to carry out the echo scan. Dr Tometzki then ordered a further review - where an echo scan would be carried out - in nine months' time.

Samuel's parents did not receive information about the check-up and raised their concerns with community children's nurse Clare Mees.

Ms Mees, who works for Sirona Lifetime Services, said she would chase up the matter with Dr Tometzki's secretary.

Medical secretary Annabelle Attridge insisted she had taken details and forwarded them on to a dedicated appointments team.

However, the inquest heard "glitch problems" with a new booking system meant the appointment was not logged. 

Apparently not due to human fault:

Paediatric clinic co-ordinator Donna McMahon said while Samuel's medical records had been created on the new Millennium computer programme, no appointments had been transferred across.

Just a "glitch."  Just a "bump in the road."

Ms McMahon said she was first aware of the appointment delay when she received an email from nurse Ms Mees in May 2012.

Samuel did not have the vital check-up until June 21.

Coroner Ms Voisin added: "This overall failure led to a five month delay in Samuel being seen by his cardiologist.

"This meant Samuel had not been seen for five months and had not had an echo for 20 months."

His parents were horrified when Dr Tometzki informed them Samuel required heart surgery that spring.

Just a "glitch."  Just a "bump in the road."

... "Just hours before his operation Samuel was dancing around the ward and telling the nurses all about Spiderman - we had to remind him to quieten down," Ms Holley said.

Samuel's chest was closed on August 8. As he was brought out of sedation on August 9, he suffered a stroke and cardiac arrests.

"It is clear that if the surgery had been performed earlier, the procedure would have been the same," Ms Voisin said.

But she said expert evidence found that as time went on "the more complicated the surgery is, as the more disadvantaged the heart is and the more difficult it is to get over the operation".

Delays in care of fragile patients - in this case a young child, but in many other cases, ED and ICU patients of all ages - is very unwise.

Samuel's condition continued to deteriorate and on September 6 his parents were recommended for treatment to be withdrawn after he had a second cardiac arrest.

The coroner said she would not write a report making recommendations to the hospital, as changes had already been implemented.

Likely, workarounds to bad health IT, inviting future catastrophe.

In my view, many cases such as this never make headlines, as the findings ignore the role of the IT and blame people, cases are settled with gag clauses, patients (who survive) or family are never told of the role of the IT, or lawsuits prove too expensive or too unpleasant to pursue.

But patient safety is never compromised by "glitches", and regulation will just stifle innovation.

My condolences to the parents.  I've suffered a death in my own family as a result of health IT, and I'm a specialist in the field.  Laypeople have no chance.

One should pray the next child affected in this way is not one's own.

-- SS

Mar. 25, 2014 addendum:  

Also see these related posts, the first mentioning "teething problems", another euphemism for potentially-deadly EHR malfunctions:

Cerner's Blitzkrieg on London: Where's the RAF?
 http://hcrenewal.blogspot.com/2010/08/cerners-blitzkrieg-on-london-wheres-raf.html 

North Bristol Hits Appointment Problems: Another "Our Lousy IT Systems Screwed Up, But Patient Safety Was Never Compromised" Story
http://hcrenewal.blogspot.com/2012/01/another-our-crappy-computers-screwed-up.html

-- SS

Sunday, February 23, 2014

We're Sorry ... Our New EMR May Screw Up Your Care, But Don't Worry ... Patient Safety Has Not Been Compromised

A sign seen at a hospital system recently (name redacted):


We're Sorry for any "Delays" as we start using our new EMR system ... But as a patient, you'll notice many benefits.   As to risks, nothing to see here ... move along.   (Click to enlarge)




FirstNet is an EMR system for Emergency Departments.

What's missing here is this:

  • Potentially deadly EHR startup "issues" can number in the many thousands (as at this link);
  • If you don't want to subject yourself to these delays and/or glitches, you are free to select another hospital for your care. 
  • (If you are injured or die as a result of the "Delays", then ... we're Extra-Special With Sugar On Top Sorry?)

In other words, this glib, nonchalant signage is incomplete, and misleading on its face.

While I understand its purpose, it ignores patient rights to informed consent and knowledge of a potentially unsafe environment for care, which hospitals have to prevent as an ethical and legal obligation.

Of course, "please feel free to ask your caregiver if you have any questions" ... who may in fact be limited by contract or edict to only use "Words That Work" to further soothe unsuspecting patients (as at this link).

-- SS

Thursday, February 20, 2014

Computer woes hit Banner hospital system: Another large EHR outage ... but patient safety was not compromised

Here is yet another story in the genre of "EHRs go out, but patient care has not been compromised." (See query link at http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised; there are more than 20 posts there now):

Computer woes hit Banner hospital system
Ken Alltucker, The Arizona Republic 12:30 a.m. EST February 20, 2014
http://www.usatoday.com/story/news/nation/2014/02/19/computer-woes-slam-banner-hospital-system/5630829/

The Phoenix-based health system used backup paper records to help provide patient care.

PHOENIX -- Banner Health grappled with a widespread computer outage Wednesday as hospitals and doctors resorted to backup paper systems to provide care for patients.

The Phoenix-based health system did not immediately know what triggered the computer troubles that started just before 10 a.m. PST. An official described the computer troubles as a rolling outage of computer systems at hospitals and other health care facilities in Phoenix, Colorado and Nevada.

"Not knowing" means that you are not in control of your life-critical information systems; rather, they are in control of you.

By late Wednesday, a spokesman said, technicians had identified the problem and were fixing it. They expect to investigate the root cause of the problem Thursday.

It took from 10 AM to "late Wednesday" to identify a problem causing a mass outage.  That should give anyone pause about dependency on fragile information systems in the hands of hospital IT departments (whose personnel undergo an ocean's less qualification-vetting than the medical personnel who depend on their work product) for one's medical care.

Banner Health, the Phoenix area's largest health care system, activated "downtime procedures" that included using paper-based systems to track medications and other care provided to patients, officials said.

Banner's emergency departments still provided care to patients and accepted new patients.

Some non-emergency surgeries and appointments were delayed because of the computer troubles.

"There have been some delays and inconveniences, but we are still providing care," said Bill Byron, Banner Health's senior vice president of public relations.

In other words, what they are saying is "we really don't need these systems, that cost hundreds of millions of dollars, to provide care with the same degree of safety as with our 'downtime procedures' (a.k.a. paper)" ... and that patient safety was not compromised by this mass outage.

Banner Health, which operates 24 hospitals and several primary-care offices and outpatient centers in more than a half-dozen states, was working to "reboot" the computer systems Wednesday evening through a series of sequential fixes, Byron said.

In the meantime, Banner officials were able to retrieve computer-based records that detailed patients' medical histories, including any medications, laboratory results and procedures that were previously performed.

Officials?  What about line clinicians?  And when did this capability start if the systems needed to be "rebooted?"

Nurses and doctors shifted to writing on paper records after the computer systems experienced trouble Wednesday morning.

Information from those paper charts will be keyed into the patients' computer-based health records after the problem is fixed.

Sure, and nothing will be lost that could adversely affect patients in the future....

Banner Health has been among the most advanced health systems in the nation in converting to computer-based health records.

Banner Estrella Medical Center was among the first hospitals to open as an "all-digital" facility in the past decade. Banner's other hospitals have largely completed the final stages of installing computerized record-keeping in areas such as physician order and entry and electronic documentation.

If they are the most advanced, what does this event say about those less advanced?

Arizona law does not require hospitals to notify state health regulators in the event of such a widespread outage.

Health IT, as usual, enjoys widespread and extraordinary regulatory accommodation.

However, some hospitals have internal policies requiring that they notify health accrediting organizations or federal regulatory agencies, such as the Centers for Medicare and Medicaid Services, an Arizona Department of Health Services spokeswoman said.

And how many do?  Not many, I predict.

-- SS

Saturday, January 25, 2014

Martin Health System, Florida: Our EHRs were out for two days, but patient care has not been compromised, sayeth Pinocchio

This is yet another post in my ever-growing "our EHRs went out due to IT incompetence, and chaos ensued, but patient care has not been compromised" series (see query link: http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised):

Martin Health System looking into network outage that slowed hospital operations
Posted: 01/24/2014
By: Meghan McRoberts
http://www.wptv.com/dpp/news/region_martin_county/martin-health-system-looking-into-network-outage-that-slowed-hospital-operations

MARTIN COUNTY, Fla.-- Martin Health System is looking into what caused some computer hardware to fail Wednesday, leading to network outage in all of the Martin Health System hospitals.

Things were back to normal Friday morning, according to hospital spokesperson, Scott Samples.

Translation: for two days there was a complete network outage, with no EHRs, email, CPOE etc.

But since Wednesday night patients say the atmosphere around the hospital was chaotic.

Patients likely noted doctors and nurses running like headless chickens.  I note that chaos and safe medical care are not good bedfellows.

Hospital staff, doctors and nurses access the computer system to read patient charts and medical information. Without it, they were left digging into paper documents.

The paper documents left laying around would have best had scanty, sparse patient information, since the computer in computerized hospitals has become the primary source of truth.  (One might think such a system, including the network, would be hardened against failure, but a two-day outage, as per other outages at the query link above, show this is often not the case.)

Samples says this led to some minor inconveniences around the hospitals, where some patients received their meals later than normal. Some outpatient appointments could not be scheduled, and extra nurses and administrative staff were brought in to help with the increased work load.

No medication or treatment was jeopardized.

There we have it.  In Pinocchio-like fashion we hear the obligatory "we lost all our information systems, which are our central nervous system for patient care, but patient care has not been compromised" statement from hospital PR.  This statement is questionable on its face. 

The risk of accident was significantly increased on its face.

New patients information was taken down on paper, and put into the system on Friday. Samples says there was a back up computer for data from former patients.

The future will be in question depending on the quality, or lack thereof, of this "backload" of patient information that was collected during what patients themselves described as "chaos."

Of course, according to the IT pundits paper itself, even under ideal circumstances, is so risky that tens or hundreds of millions of dollars per hospital has been spent to replace it.  Someone is not being truthful.

The hospitals that experienced the outage were Martin Medical Center, Martin Hospital South, and Tradition Medical Center.

But patient safety risk was not compromised at any of them, so sayeth the figure below.


All our EHRs and other clinical IT were unavailable for two days ... patients reported chaos ... we had to delay or cancel appointments and bring in extra clinical staff to maintain order ... but patient safety was not compromised, except for some late lunches!

Pinocchio must be working at a lot of hospitals. When EHRs are out, patient safety is compromised. This is not open for debate, it is an "on its face" issue. These systems need hardening so as to be up and available 100%. Period. People responsible for outages need to be held accountable, including in a court of law if patients are injured or die as a result. Period.

Finally I note that, with the corporatization of healthcare and with population of executive offices by lightweights with unquestioning faith in "cybernetic miracles", the credo of my early 1970's medical mentor, cardiothoracic surgery pioneer and educator Victor P. Satinsky, MD (link) - "Critical thinking, always, or your patient's dead" - is more valuable than ever.

-- SS

Wednesday, October 2, 2013

Another in the "Health IT Crashed, But Patient Care Was Not Compromised" Series - NHS Greater Glasgow and Clyde

We must have health IT to prevent stupid doctors and nurses from making mistakes.  Without it, patients are at the mercy of dreaded Paper Records, which by definition cannot ever be used to provide quality care.

But when the IT goes down, Patient Care Has Not Been Compromised.  This line should be trademarked, as it's seen so often.  (I even have an indexing tag for it, see this query link: http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised.)

Care is never, never compromised when the IT goes belly up en masse due to information technology malpractice.  Care is only compromised by paper, no matter how good the paper records and its human stewards are.

Here's the latest example that made it to the news, in Scotland:

1 October 2013
BBC News
Appointments postponed after major IT failure at NHSGGC (NHS Greater Glasgow and Clyde)

Hundreds of outpatient appointments and a number of operations had to be postponed after computer systems failed at Scotland's biggest health board.

NHS Greater Glasgow and Clyde said technicians were working through the night to fix a "major IT problem" which occurred on Tuesday morning.

It affected staff access to clinical and administrative systems.

Delaying hundreds of appointments and delaying surgeries at up to 10 major hospitals seems on its face to represent "compromised care."

The health board apologised to patients and said all appointments would be rescheduled.

In total, 288 outpatient appointments, four planned inpatient procedures, 23 day surgery cases and 40 chemotherapy sessions were postponed.

There was also some delay in calls to the switchboard being answered.

The problem may have affected up to 10 major hospitals across the health board area.

One wonders how these appointments and surgeries were triaged for delay.  Clearly the downed computer was of no help.

Here's that wonderful line:

But emergency operations were not compromised - neither were community services.

So when does computer failure actually compromise patient care?  I'd like to see some hospital executive with a spine for once admit that IT malpractice does disrupt patient care, create distractions, and thus create safety risk.  Considering the domain, however, I doubt I'll ever see that.

A spokeswoman said: "Our technical staff are working flat out to resolve this.

It should never have happened in the first place.

"The problem relates to our networks and the way staff can connect to some of our clinical and administrative systems.

Well, sick patients really appreciate that explanation.

It was not clear how long the disruption would last.

NHSGGC said if it did continue, people who were scheduled for treatment would be contacted directly.

Per a computer guru from my past:  "Either you're in control of your information systems, or they're in control of you."

In this instance, the latter clearly applies.

In healthcare, having your information systems in control of you is, sooner or later, going to be deadly.

-- SS


Wednesday, August 28, 2013

Setback for Sutter after $1B EHR crashes (in followup to post "RNs Say Sutter’s New Electronic System Causing Serious Disruptions to Safe Patient Care at East Bay Hospitals")

At my July 12, 2013 post "RNs Say Sutter’s New Electronic System Causing Serious Disruptions to Safe Patient Care at East Bay Hospitals" (http://hcrenewal.blogspot.com/2013/07/rns-say-sutters-new-electronic-system.html) I reproduced a California Nurses Association warning about rollout of an EHR at Sutter:

RNs Say Sutter’s New Electronic System Causing Serious Disruptions to Safe Patient Care at East Bay Hospitals

Introduction of a new electronic medical records system at Sutter corporation East Bay hospitals has produced multiple problems with safe care delivery that has put patients at risk, charged the California Nurses Association today.

Problems with technology are not unique to health care ...  [What is unique to healthcare IT is the complete lack of regulation - ed.]

In over 100 reports submitted by RNs at Alta Bates Summit Medical Center facilities in Berkeley and Oakland, nurses cited a variety of serious problems with the new system, known as Epic. The reports are in union forms RNs submit to management documenting assignments they believe to be unsafe.

Patient care concerns included computerized delays in timely administration of medications and contact with physicians, ability to properly monitor patients, and other delays in treatment.  Many noted that the excessive amount of time required to interact with the computer system, inputting and accessing data, sharply cuts down on time they can spend with patients with frequent complaints from patients about not seeing their RN.  [Note: patients are not given the opportunity for informed consent about the risks, nor opt-out of EHR use in their care - ed.]

In related posts I'd observed such concerns being ignored by hospital management.  See header of the aforementioned post.

Now we have this:  a major system crash.

Healthcare IT News
Setback for Sutter after $1B EHR crashes
'No access to medication orders, patient allergies and other information puts patients at serious risk'
 
Worse, clinicians must now serve their Cybernetic Master to perfection, or be whipped (apparently to improve morale):

... "We have been on Epic for 5 months now, and we can no longer have incorrect orders, missing information or incorrect or missing charges. Starting on September 1st, errors made in any of the above will result in progressive discipline," according to another hospital memo sent to staff.

In the setting of dire warnings by the nurses of EHR dangers several months back that were likely largely ignored, if any patient was harmed or killed as a result of this latest fiasco, the corporate leadership has literally begged to be sued for negligence, in my view.

However I'm sure a press release soon will claim that "patient care has not been compromised."

Of course this includes now and moving forward, even with informational gaps all over the place.

-- SS

Aug. 29, 2013 additional thought:

The punishment for not being a 'perfect' user of this EHR is the ultimate "blame the user" (blame the victim?) game, considering the pressures of patient care in hospitals in lean times - partly due to EHR expense! - and EHRs that have not been formally studied for usability and are poorly designed causing "use error" (that is, a poor user experience promotes even careful users to make errors).  Cf. definition of bad health IT:

Bad Health IT ("BHIT") is defined as IT that is ill-suited to purpose, hard to use, unreliable, loses data or provides incorrect data, causes cognitive overload, slows rather than facilitates users, lacks appropriate alerts, creates the need for hypervigilance (i.e., towards avoiding IT-related mishaps) that increases stress, is lacking in security, compromises patient privacy or otherwise demonstrates suboptimal design and/or implementation.

The study of usability is getting underway only now via NIST but will likely be done in an industry-friendly way due to health IT politics.

-- SS

Aug. 29, 2013 addendum

There have been numerous comments over at HisTalk (at http://histalk2.com/2013/08/27/news-82813/) defending the outage as not EPIC's fault.   From the point of view of clinicians - and more importantly, patients - it doesn't matter what component of the hospital's entire "EHR" (an anachronistic term used for what is now a complex enterprise clinical resource and clinician command-and-control system) went down. 

Aside from all the EPIC issues the nurses have been complaining about (see earlier July 12, 2013 post linked above), the larger problem is that IT malpractice occurred.  The term "malpractice" is used in medical mishaps; I see no reason why it does not apply to major outages of mission critical healthcare information technology systems.

IT malpractice in healthcare kills.

These are the types of nurses I'd want caring for me and mine.  Letting this kind of snafu go "anechoic" does not promote proper management remedial education on Safety 101 and on health IT risk, two areas of education that management appears to desperately need in hospitals.

-- SS

Friday, July 12, 2013

RNs Say Sutter’s New Electronic System Causing Serious Disruptions to Safe Patient Care at East Bay Hospitals

Add the following from Sutter East Bay Hospitals to nurses' and physicians' complaints at Marin General Hospital (http://hcrenewal.blogspot.com/2013/05/marin-general-hospitals-nurses-are.html), Affinity Medical Center (http://hcrenewal.blogspot.com/2013/06/affinity-rns-call-for-halt-to-flawed.html), Contra Costa County (http://hcrenewal.blogspot.com/2012/08/contra-costas-45-million-computer.html), San Francisco Department of Public Health (http://hcrenewal.blogspot.com/2010/11/avatar-fails-no-not-cameron-movie-but.html), and others:

For Immediate Release 
July 11, 2013
Contact-  Charles Idelson, 510-273-2246

RNs Say Sutter’s New Electronic System Causing Serious Disruptions to Safe Patient Care at East Bay Hospitals

Introduction of a new electronic medical records system at Sutter corporation East Bay hospitals has produced multiple problems with safe care delivery that has put patients at risk, charged the California Nurses Association today.

Problems with technology are not unique to health care – pilots of the ill fated Asiana airline that tragically crashed at San Francisco International Airport July 6 told federal investigators that an automatic throttle failed to keep the jetliner at the proper speed for landing, the Los Angeles Times reported July 9.  [What is unique to healthcare IT is the complete lack of regulation - ed.]

In over 100 reports submitted by RNs at Alta Bates Summit Medical Center facilities in Berkeley and Oakland, nurses cited a variety of serious problems with the new system, known as Epic. The reports are in union forms RNs submit to management documenting assignments they believe to be unsafe.

Patient care concerns included computerized delays in timely administration of medications and contact with physicians, ability to properly monitor patients, and other delays in treatment.  Many noted that the excessive amount of time required to interact with the computer system, inputting and accessing data, sharply cuts down on time they can spend with patients with frequent complaints from patients about not seeing their RN.  [Note: patients are not given the opportunity for informed consent about the risks, nor opt-out of EHR use in their care - ed.]

"EPIC is a system that is so cumbersome to use for nurses and physicians, that we often feel as though we are caring for a computer, not a patient,” said Thorild Urdal, an RN at Alta Bates Summit’s hospital in Berkeley. “It delays care and treatment, the program is naturally counter-intuitive and it was clearly not designed in concert with nurses and physicians." [Clinicians end up caring for an "iPatient", as others have noted - ed.]

"The Epic program developed and implemented by Sutter is neither nurse or patient friendly,” said Alta Bates Summit Oakland RN Mike Hill. “Epic does not enhance my ability to chart instead it takes time away from the bedside and my patients and preventing me from providing the absolute best care that they and I expect from me as a nurse."

Sutter CEO Pat Fry last year told the San Francisco Business Times that Sutter will spend $1 billion on Epic, a system that has sparked controversy at several other hospitals, including a Contra Costa facility where several RNs cited serious medical errors in testimony to county supervisors last August.

At Alta Bates Summit specific incidents directly related to Epic problems included:

• A patient who had to be transferred to the intensive care unit due to delays in care caused by the computer.  [It's happenstance they did not have to be transferred to the morgue - ed.]
• A nurse who was not able to obtain needed blood for an emergent medical emergency.
• Insulin orders set erroneously by the software.
• Missed orders for lab tests for newborn babies and an inability for RNs to spend time teaching new mothers how to properly breast feed babies before patient discharge.
• Lab tests not done in a timely manner.
• Frequent short staffing caused by time RNs have to spend with the computers.
• Orders incorrectly entered by physicians requiring the RNs to track down the physician before tests can be done or medication ordered.
• Discrepancies between the Epic computers and the computers that dispense medications causing errors with medication labels and delays in administering medications.
• Patient information, including vital signs, missing in the computer software.
• An inability to accurately chart specific patient needs or conditions because of pre-determined responses by the computer software.
• Multiple problems with RN fatigue because of time required by the computers and an inability to take rest breaks as a result.
• Inadequate RN training and orientation.

These "incidents" are certainly capable of causing harms or fatalities.  One wonders if hospital executives are providing the usual refrain that these are just "glitches" (http://hcrenewal.blogspot.com/search/label/glitch) and that patient care has not been compromised (http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised).

A bit more background follows:

... Hospitals nationally are spending tens of billions of dollars on technology systems, especially on electronic health records (EHR) programs for which they also receive federal financial incentives.

EHR programs are paraded as a panacea for reducing medical errors and cutting costs, but in life the promise is falling short in both areas.

A RAND corporation analysis earlier this year said visions of savings and improved efficiency in patient care have had what the New York Times called “mixed results, at best.”

The U.S. Food and Drug Administration has acknowledged getting hundreds of reports of problems involving health information technology including numerous patient injuries and deaths.

Some examples seen at hospitals across the country:

• At Marin General Hospital in Northern California, RNs called on the Marin Healthcare District board to delay implementation of their EHR system. "Orders are being inadvertently passed to the wrong patients. People have gotten meds when they've been allergic to them. This is dangerous," Marin RN Barbara Ryan said in comments reported by the Marin Independent Journal.
• In Chicago, the Chicago Tribune in 2011 reported on a patient death at Advocate Lutheran General hospital after an automated machine prepared an intravenous solution containing a massive overdose of sodium chloride — more than 60 times the amount ordered by a physician.
• At Affinity Medical Center RNs in Massillon, Oh. RNs in June raised multiple objections to the hurried introduction of an EHR system. Subsequently, they have cited medication errors, delays in care, problems with documentation, computers crashing, and other concerns.

I am simply the reporter here.

-- SS

Friday, May 17, 2013

Marin General Hospital nurses warn that new computer system is causing errors, call for time out

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

Of course, the ever-present euphemism for life-threatening EHR malfunctions and defects, i.e., "glitches" are the cause (http://hcrenewal.blogspot.com/search/label/glitch):


Marin General Hospital nurses warn that new computer system is causing errors, call for time out

By Richard Halstead
Marin Independent Journal
Posted:   05/15/2013 04:07:49 PM PDT

Nurses at Marin General Hospital have asked administrators to put implementation of a new computerized physician order entry system on hold until glitches can be worked out and more training provided to nurses and doctors who use it.

Nearly a dozen nurses attended the regularly scheduled meeting of the Marin Healthcare District board Tuesday night at Marin General to voice their concerns. The district board oversees Marin General, but it does not involve itself in the hospital's day-to-day operations.

"Orders are being inadvertently passed to the wrong patients
. People have gotten meds when they've been allergic to them. This is dangerous," said Barbara Ryan, a Marin General registered nurse, who works in pediatrics and the intensive care nursery. "We're not asking you to get rid of it. We're asking you to place it on hold."


Orders passed to wrong patients?  No problem, just a glitch!  Meds people are allergic to?  Just a glitch.  Dangerous?  No way.  It's just a glitch!

But Lee Domanico, who serves as the CEO of both Marin General and the Marin Healthcare District, said, "I'm confident that in spite of the implementation issues, we have a system today that is safer for patients than our old paper system, and it will get even safer as we gain experience with it and work to fix some of the glitches we've experienced."

Where's the data backing up that assertion, I ask?  The actual risks of paper records don't seem to be robustly documented anywhere.

Ryan, who serves as the California Nurses Association/National Nurses United representative, was one of four Marin General nurses who spoke during the public comment portion of the meeting. Ryan said the nurses warned in advance of the system's roll-out on May 7 that nurses and doctors had insufficient knowledge of the system. Ryan said due to problems with the software nurses had been unable to open the program at home to practice using it.

And yet the rollout happened anyway?  That seems to me to be reckless indifference to the concerns of clinicians.

"Lo and behold the problems that we were worried about have happened," Ryan said. "We're looking at two-hour preps for surgery and two- to three-hour discharges; skilled nursing facilities calling back saying, this really doesn't make sense; the wrong meds ordered on the wrong patients and then given to the wrong patients; the inability for nurses to be able to see what the doctor ordered and double-check it."

Of course, I might add, patient safety was not compromised, the other common refrain of EHR glitch-excusers ... see below.

Ryan said nurses have and will continue to file "assignment despite objection" forms due to the system. Nurses file the forms to document formal objections to what they consider an unsafe, or potentially unsafe, patient care assignment.

"We will take patients but we will object to the assignment because it is unsafe," Ryan said. "This system is making it unsafe."

These will be exceptionally helpful in court to any patients injured or killed as a result of these "glitches" and EHR rollout that occurred despite direct warnings from clinical experts.

Marin General nurse Susan Degan said, "This is not about resistance to change. It's about accountability. My most important role is that of patient advocate. I am held accountable when errors are made."

Domanico acknowledged there have been some technical problems with the Paragon system, including making it possible for nurses to open from home. And he said the software is not faster than the old paper system.  [Considering it's acknowledged all the way up to the highest levels of HHS that current EHR's slow physicians down, one wonders if anyone in this organization thought an EHR would actually increase speed? - ed.]

About the "resistance to change" canard, see my essay "Doctors and EHRs: Reframing the 'Modernists v. Luddites' Canard to The Accurate 'Ardent Technophiles vs. Pragmatists' Reality" at http://hcrenewal.blogspot.com/2012/03/doctors-and-ehrs-reframing-modernists-v.html .

"So yes," Domanico said, "it is causing stress for nurses who have heavy workloads, who are learning how to use it, particularly in areas where we need to speed up the computer."

What?  "Speed up the computer?"  They've spent tens if not hundreds of millions for an EHR, and the computer's too slow?

Actually, I think what this CEO in an obvious display of health IT ignorance is trying to say is that we have to do something about the system's poor usability, which sort of mimics what the Board Chair of the American Medical Assocation just said (http://hcrenewal.blogspot.com/2013/05/ama-finally-on-board-with-ehr-views.html).

Also - clinician stress promotes error.

But Domanico challenged the suggestion that patient safety at Marin General had been compromised.

In fact, there is no way the issues described above cannot be compromising patient safety, on its face. (http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised).

"I would have no hesitation about entering this hospital tonight," he said.

As a VIP, of course, this CEO would get special treatment.  Thanks a lot.

I would NOT want to be a patient there under these conditions, unless perhaps I had a 24x7 medically-skilled advocate/bodyguard.

Board member Ann Sparkman, who previously served as in-house counsel at Kaiser Permanente, said nurses at Kaiser struggled at first when a new computer system was introduced there.

Sparkman said, "It's just to be expected."

This seems a rather bizarre appeal to common practice (http://www.nizkor.org/features/fallacies/appeal-to-common-practice.html).

The stunning ignorance of this board member about proper mission-critical IT safety testing and implementation, such as performed in pharma, aerospace, etc. is, quite frankly, shocking.

Further, an attitude that life-threatening "glitches" are "just to be expected" by a member of the Board of Directors, with fiduciary responsibilities regarding hospital operations, is grossly negligent in my opinion, and completely ignores patient's rights.

Unbelievable.

One wonders if any formally-trained medical informatics experts were in leadership roles in this project.

-- SS

Monday, March 11, 2013

When "Human Error" Causes EHR Downtime, Who is Liable For Patient Injuries That Result?

In the Pittsburgh Post-Gazette was this story of yet another EHR "glitch":

March 9, 2013 12:17 am 

Human error the cause of UPMC electronic issue

A systemwide problem with UPMC's information systems Wednesday left electronic patient records and other data inaccessible for about three hours. A UPMC spokeswoman said the hospitals "immediately went to manual backup systems, and we quickly identified and fixed the problem." She said there was no indication that patient care was compromised by the incident, which was due to human error.

I will presume the "human error" was not a physician or nurse pressing the wrong button, but a "human error" involving the servers or IT infrastructure such as a botched system upgrade, action that caused a server room power fault, etc.

UMPC is a very large system as their webpage shows, showing approximately fifteen major facilities.

The now-expected "patient care has not been compromised" line was provided to the Gazette, a line so commonly heard after EHR outages that I  use it as a Healthcare Renewal indexing tag (see this query link).

The following questions arise:

  • What, exactly, was the "human error" and why was there no fault tolerance built into these mission-critical systems to account and compensate for it, such as via redundancy?
  • If paper is so bad as a record-keeping medium that hundreds of billions of dollars are being spent to replace it, then how can patient care not be compromised, especially when multiple hospitals unexpectedly and without warning have to return to its use? 
  • How can a very large hospital system rapidly declare that "patient care was not compromised" without a thorough and comprehensive patient review, accounting for possible delayed negative outcomes (by way of just a few simple examples, due to medication or imaging delays?)
  •  Who is liable for any adverse patient outcomes that occurred related to the sudden unavailability of past records:  the clinicians?  The "human" who committed the computer-related error?  The corporation, either for direct negligence in implementing and mandating use of a system prone to mass outage by human error, or vicariously for the negligence and/or misconduct of its information technology employees and/or agents?
  •  How many "outages" will it take before some patient is outright, no-doubt-about-it harmed or killed?  Do we want to find out, or is a priority to have redundancies so these systems don't crash?
I, for one, would not want to have a family member be "crashing" at the time of a sudden, unexpected system-wide EHR outage.

-- SS

Wednesday, October 3, 2012

Allegheny Health System Computer Crash (Again) and Paper Backups

I reported on a health IT crash in my May 2011 post "Twelve Hour Health IT Glitch at Allegheny General Hospital - But Patients Unaffected, Of Course..."

Now, there's this at the same healthcare system:

Computer system at West Penn Allegheny restored after crash 
Liz Navratil
Pittsburgh Post-Gazette
October 2, 2012


The computer system at West Penn Allegheny Health System crashed about noon today, temporarily leaving doctors and nurses to work off of paper records instead.

Kelly Sorice, vice president of public relations for the health system, said all systems have since been restored. She said the servers crashed about noon today when the system experienced a power surge.

Doctors in the health system keep paper copies of almost all of their records so they can reference them during power outages or scheduled maintenance times, Ms. Sorice said.

Some systems were up eight hours later and others were expected to come online overnight, according to a report at HisTalk.

Assuming the statement about "doctors keep paper copies of almost all their records" was not spin control regarding skeletal paper records, a question arises.

Why, exactly, spend hundreds of millions of dollars on computing if paper records are kept, and are perfectly sufficient to accomplish the following, the usual refrain in health IT crash scenarios?

Ms. Sorice said she did not know of any procedures that had been rescheduled and added that, "Patient care has not been compromised."

As a physician/ham radio enthusiast who did an elective in Biomedical Engineering in medical school, I also want to know:

1)  What caused the “power surge?”
2)  Why were the systems not protected against a “power surge?”
3)  Exactly how did the “power surge” affect the IT?

Note: I've created a new, searchable indexing term for HIT outage stories with the usual refrain along the lines that "patient care has not been compromised." 

See this query link using the new indexing term.

-- SS

Addendum Oct. 3:

Australian EHR reseacher and professor Dr. Jon Patrick opines:

Even if [the paper records are] skeletal they suggest an endemic lack of confidence. I think the hospital spokesperson hasn't seen the implication of their statement.

-- SS

Sunday, September 30, 2012

UK: Another Example of IT Malpractice With Bad Health IT (BHIT) Affecting Thousands of Patients, But, As Always, Patient Care Was "Not Compromised"

At my Dec. 2011 post "IT Malpractice? Yet Another "Glitch" Affecting Thousands of Patients. Of Course, As Always, Patient Care Was "Not Compromised" and others, I noted:

... claims [in stories regarding health IT failure] that "no patients were harmed" ... are both misleading and irrelevant:

Such claims of 'massive EHR outage benevolence' are misleading, in that medical errors due to electronic outages might not appear for days or weeks after the outage ... Claims of 'massive EHR outage benevolence' are also irrelevant in that, even if there was no catastrophe directly coincident with the outage, their was greatly elevated risk. Sooner or later, such outages will maim and kill.

Here is a prime example of why I've opined at my Sept. 2012 post "Good Health IT (GHIT) v. Bad Health IT (BHIT): Paper is Better Than The Latter" that a good or even average paper-based medical record keeping system can facilitate safer and better provision of care than a system based on bad health IT (BHIT).

Try this with paper:

NHS 'cover-up' over lost cancer patient records

Thousands awaiting treatment were kept in the dark for five months when data disappeared

Sanchez Manning
The Independent
Sunday 30 September 2012

Britain's largest NHS trust took five months to tell patients it had mislaid medical records for thousands of people waiting for cancer tests and other urgent treatments. Imperial College Healthcare NHS Trust discovered in January that a serious computer problem and staff mistakes had played havoc with patient waiting lists.

It's quite likely the "serious computer problem" far outweighed the impact of "staff mistakes", as disappearing computer data does so in a "silent" manner.  One does not realize it's missing as there's not generally a trail of evidence that it's gone.

About 2,500 patients were forced to wait longer on the waiting lists than the NHS's targets, and the trust had no idea whether another 3,000 suspected cancer patients on the waiting list had been given potentially life-saving tests. Despite the fact that the trust discovered discrepancies in January and was forced to launch an internal review into the mess, including 74 cases where patients died, it did not tell GPs about the lost records until May.

That is, quite frankly, outrageous if true and (at least in the U.S.) might be considered criminally negligent (failure to use reasonable care to avoid consequences that threaten or harm the safety of the public and that are the foreseeable outcome of acting in a particular manner).

Revelations about the delay prompted a furious response yesterday from GPs, local authorities and patients' groups. Dr Tony Grewal, one of the GPs who had made referrals to Imperial, said doctors should have been told sooner to allow them to trace patients whose records were missing. "The trust should have contacted us as soon as it was recognised that patients with potentially serious illnesses had been failed by a system," he said. "GPs hold the ultimate responsibility for their patient care."

That is axiomatic.

The chief executive of the Patients Association, Katherine Murphy, added: "This is unacceptable for any patient who has had any investigation, but especially patients awaiting cancer results, where every day counts. The trust has a duty to contact GPs who referred the patients. It's unfair on the patients to have this stress and worry, and the trust should not have tried to hide the fact that they had lost these records. They should have let the GPs know at the outset."

Unfair to the patients is an understatement,  However, if one's attitude is that computers have more rights than patients, as many on the health IT sector seem to with their ignoring of patient rights such as informed consent, lack of safety regulation, and lack of accountability, then it's quite acceptable.

The trust defended the delay in alerting GPs, arguing that it needed to check accurately how much data it had lost before making the matter public. It said a clinical review had now concluded that no one died as a result of patients waiting longer for tests or care.

That would be perhaps OK if the subjects whose "data had been lost" through IT malpractice were lab rats.

Despite this, three London councils – Westminster, Kensington and Chelsea, and Hammersmith and Fulham – are deeply critical of the way the trust handled the data loss. Sarah Richardson, a Westminster councillor who heads the council's health scrutiny committee, said that trust bosses had attempted to "cover up" the extent of the debacle. "Yes, they've done what they can but, in doing so, [they] put the reputation of the trust first," she said. "Rather than share it with the GPs, patients and us, they thought how can we manage this information internally. They chose to consider their reputation over patient care."

As at my Oct. 2011 post "Cybernetik Über Alles: Computers Have More Rights Than Patients?", to be more specific, they may have put the reputation of the Trust's computers first. 

Last week, it was revealed that Imperial has been fined £1m by NHS North West London for the failures that led to patient data going missing. On Wednesday, an external review into the lost records said a "serious management failure" was to blame for the blunder.

Management of what, one might ask?

Imperial's chief financial officer, Bill Shields, admitted at a meeting with the councils that the letter could have been produced more quickly. He said that, at the time, the trust had operated with "antiquated computer systems" and had a "light-touch regime" on elective waiting times.

Version 2.0A will, as again is a typical refrain, fix all the problems.

Terry Hanafin, the leading management consultant who wrote the report, said the data problems went back to 2008 and had built up over almost four years until mid-2011. Mr Hanafin said the priorities of senior managers at that time were the casualty department and finance.

Clinical computing is not business computing, I state for the thousandth time.  When medical data is discovered "lost", the only response should be ... find it, or inform patients and clinicians - immediately.

He further concluded that while the delays in care turned out to be non-life threatening, they had the potential to cause pain, distress and, in the case of cancer patients, "more serious consequences" ... The trust said it had found no evidence of clinical harm and stressed that new systems have now been implemented to record patient data. It denied trying to cover up its mistakes or put its reputation before concerns for patients. "Patient safety is always our top priority," said a spokesman.

"More serious consequences" is a euphemism for horrible metastatic cancer and death, I might add.  The leaders simply cannot claim they "found no evidence of clinical harm" regarding delays in cancer diagnosis and treatment until time has passed, and followup studies performed on this group of patients.

This refrain is evidence these folks are either lying, CYA-style, or have no understanding of clinical medicine whatsoever - in which case their responsibilities over the clinic need to be ended in my opinion.

I, for one, would like to know the exact nature of the "computer problem", who was responsible, and if it was a software bug, how such software was validated and how it got into production.

-- SS

Oct. 1, 2012 Addendum:

What was behind the problems, according to another source?   

Bad Health IT (BHIT):

Poor IT behind Imperial cancer problems
e-Health Insider
28 September 2012
Rebecca Todd

An independent review of data quality issues affecting cancer patient referrals to Imperial College Healthcare NHS Trust has identified “poor computer systems” as a key cause of the problem.

The review’s report highlights the trust’s use of up to 17 different IT systems as causing problems for patient tracking.

However, it says the trust should be aware of the risks of [replacing the BHIT and] moving to a single system, Cerner Millennium, because of reported problems in providing performance data after similar moves at other London trusts.

In January 2012, the report says the NHS Intensive Support Team was reviewing the way reports on cancer waiting times were created from Imperial’s cancer IT system, Excelicare.

The team discovered that almost 3,000 patients were still on open pathways who should have been seen within two weeks. In May, letters were sent to GPs to try and ascertain the clinical status of around 1,000 patients.

BHIT must be forbidden from real-world deployments, and fixed rapidly or dismantled (as Imperial College Healthcare NHS Trust appears to be doing), although the "solution" might be just as bad, or worse, than the disease.

-- SS

Thursday, August 23, 2012

From the University of Chicago EHR Helpdesk Call Line

I was alerted this morning (Aug. 23rd) to this message currently in the telephone message of the CBIS [Chicago Biomedicine Information Services] Service Desk at University of Chicago Medical Center:

"Thanks for calling the CBIS Service Desk.  Your call is very important to us. We are currently experiencing troubles with our Citrix logon.  It may log you on under a different profile.  Please check before you go any further when you're logging in to Citrix."

Citrix is a computer program that allows remote access to information systems.

I imagine the meaning of "log you on under a different profile" means "logging you on as a different user."

The chances of a security breach (ability of unauthorized user to peer into patient's charts they have no business seeing), unauthorized history/order manipulation, or even misidentification error (e.g., a clinician inadvertently acting upon a patient of some other clinician who has a similar name to their own patient) and other distracting work disruptions due to the inconveniences this "trouble" creates are worrisome.

One wonders how every user is being informed of this problem, as not everyone makes it a habit to call the service desk before logging in to clinical systems...

But, alas, this is just a "glitch" (the euphemism used by technophiles for malignant software defects), and, of course, patient safety is never compromised by "glitches."


Patient Safety Will Not Be Compromised, We Predict ... So Say Us All.


-- SS

8/29/12 Addendum:

Apparently the problem was finally solved between 5:30 PM and 9 PM CST on August 27.   I first became aware of it at around 8 AM EST August 23.  Brings to life the line "either you are in control of your information systems, or they are in control of you."

Also, see the comment thread to this post here, specifically the comments starting at August 28, 2012 12:16:00 PM EDT, to see yet another demonstration of the illogic, unserious attitudes and feelings of entitlement towards patient risk and transparency characteristic of the health IT industry.  The anonymous commenter also alleges to have firsthand knowledge of the problem, suggesting they are from U. Chicago, but this cannot be confirmed.

-- SS

Wednesday, August 8, 2012

ONC and Misdirection Regarding Mass Healthcare IT Failure

In my keynote address to the Health Informatics Society of Australia in Sydney recently, I cautioned attendees including those in government to be wary of healthcare IT hyper-enthusiast misdirection and logical fallacy (a.k.a. public relations).

In the LA Times story "Patient data outage exposes risks of electronic medical records" on the Cerner EHR outage I wrote of in my post "Massive Health IT Outage: But, Of Course, Patient Safety Was Not Compromised" (the title, of course, being satirical), Jacob Reider, acting chief medical officer at the federal Office of the National Coordinator for Health Information Technology is quoted.  He said:

"These types of outages are quite rare and there's no way to completely eliminate human error."

This is precisely the type of political spin and hyper-enthusiast misdirection I cautioned the Australian health authorities to evaluate critically.

As comedian Scott Adams humorously noted regarding irrelevancy, a hundred dollars is a good price for a toaster, compared to buying a Ferrari.

Further, when you're the patient harmed or killed, or the victim is a family member, you really don't care how "rare" the outages are.

Airline crashes are "rare", too.   So, shall they just be tolerated as a "cost of doing business" and spun away?

(As I once wrote, the asteroid colliding with Earth that caused the extinction of the dinosaurs was a truly "rare" event.)

It seems absurd for me to have to point out that paper, unless there is a mass outbreak of use of disappearing ink, or locally hosted clinical IT, do not go blank en masse across multiple states and countries for any length of time, raising risk across multiple hospitals greatly, acutely and simultaneously.   Yet, I have to point out this obvious fact in the face of misdirection.

Locally hosted health IT, of course, can only cause "local" chart disappearances.  "Local" is a relative term, however, depending on HC organization size, as in the example of a Dec. 2011 regional University of Pittsburgh Medical Center (UPMC) 14-hour outage affecting thousands here.

Further, EHR's and other clinical IT, whether hosted locally or afar, had better offer truly major advantages, without major risks and disadvantages, over older medical records technologies before exposing large numbers of patients to an invasive IT industry and the largest unconsented human subjects experiment in history.

Unfortunately, those basic criteria are not yet apparent with today's systems (see for instance this reading list).

EHR's and other clinical IT, forming in reality an enterprise clinical resource management and clinician workflow control apparatus, have introduced new risk modes including mass chart theft (sometimes tens of thousands in the blink of an eye); also, mass chart disappearances as in this case - all not possible with paper.

At the very least, if hospitals want enterprise clinical resource management and clinician workflow control systems, these should not be relegated to a distant third party.  Patients are not guinea pigs upon whom to test the ASP software model ("software as a service") that, upon failure for any reason, threatens their lives.

Finally, these complications are a further example why this industry cannot go on without meaningful oversight.  The unprecedented special medical device regulatory accommodations must end.

-- SS

Tuesday, August 7, 2012

Massive Health IT Outage: But, Of Course, Patient Safety Was Not Compromised

Having been 'Down Under' in Sydney addressing the Health Informatics Society of Australia on the need to slow down their national health IT program - and on the need to think critically about HIT seller public relations exaggerations and hubris - and being very busy, I missed this quite stunning story of a major health IT outage.

Just a typical "glitch":

Some lessons from a major outage
Posted on July 31, 2012
By Tony Collins

Last week Cerner had a major outage across the US. Its international customers might also have been affected.

InformationWeek Healthcare reported that Cerner’s remote hosting service went down for about six hours on Monday, 23 July. It hit “hospital and physician practice clients all over the country”. Information Week said the unusual outage “reportedly took down the vendor’s entire network” and raised “new questions about the reliability of cloud-based hosting services”.

A Cerner spokesperson Kelli Christman told Information Week,

“Cerner’s remote-hosted clients experienced unscheduled downtime this week. Our clients all have downtime procedures in place to ensure patient safety.  [Meaning, for the most part, blank paper - ed.] The issue has been resolved and clients are back up and running. A human error caused the outage.  [I don't think they mean human error as in poor disaster recovery and business continuity engineering - ed.]  As a result, we are reviewing our training protocol and documented work instructions for any improvements that can be made.”

Christman did not respond to a question about how many Cerner clients were affected. HIStalk, a popular health IT blog, reported that hospital staff resorted to paper [if that was true, that paper was OK in an unplanned workflow disruption of major proportions, then why do we need to spend billions on health IT, one might ask? - ed.] but it is unclear whether they would have had access to the most recent information on patients.

One Tweet by @UhVeeNesh said “Thank you Cerner for being down all day. Just how I like to start my week…with the computer system crashing for all of NorCal [Northern California].”

Tony Collins is a commentator for ComputerWorldUK.com.  He's quoted me, as I wrote in my May 2011 post Key lesson from the NPfIT - The Tony Collins Blog.

This incident brings to life longstanding concerns about hospitals outsourcing their crucial functions to IT companies.  

Quite simply, I think it's insane, at least in the foreseeable future, as this example shows.

It also brings to mind the concerns that health IT, as an unregulated technology, causes dangers in hospitals with inadequate internal disaster and business continuity functions aside from fresh sheets of paper.  Such capabilities would likely be mandatory if health IT were meaningfully regulated.

The Joint Commission, for example, likely issued its stamp of approval for the affected hospitals, hospitals who had outsourced their crucial medical records functions to an outside party that sometimes went mute.  If someone was injured or died due to this outage, they would not care very much about the supposed advantages.

There's this in the article:

... “Issue appears to have something to do with DNS entries being deleted across RHO network and possible Active Directory corruption. Outage was across all North America clients as well as some international clients.”

Of course, patient safety was not compromised.

Finally:

Imagine being a patient, perhaps with a complex history, in extremis at the time of this outage.  

I, for one, do not want my own medical care nor that of my relatives and friends subject to cybernetic recordkeeping unreliability and incompetence like this, and the risk it creates.

-- SS

Aug. 8, 2012 addendum:

The Los Angeles Times covered this outage in a story aptly entitled "Patient data outage exposes risks of electronic medical records."

They write:

Dozens of hospitals across the country lost access to crucial electronic medical records for about five hours during a major computer outage last week, raising fresh concerns about whether poorly designed technology can compromise patient care.

My only comment is that the answer to this question is rather axiomatic.

They also quote Jacob Reider, acting chief medical officer at the federal Office of the National Coordinator for Health Information Technology, who said:

"These types of outages are quite rare and there's no way to completely eliminate human error"

This is precisely the type of political spin and misdirection I cautioned the Australian health authorities to evaluate critically.

Paper, unless there is a mass outbreak of use of disappearing ink, or locally hosted clinical IT, do not go blank en masse across multiple states and countries for any length of time, raising risk across multiple hospitals greatly, acutely and simultaneously.  (Locally hosted IT outages only cause "local" mayhem; see my further thoughts on this issue here).

-- SS