ads

,
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
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
    11:29 AM
    At my March 2, 2015 post "Rideout Hospital, California: CEO Pinocchio on quality of patient care during hospital computer crash" (http://hcrenewal.blogspot.com/2015/03/rideout-hospital-california-ceo.html) I highlighted a stunning example of when the light shone through the corporate B.S. about health IT outages, thanks to a letter to the editor by a family member of an affected patient:

    Letter: Re: Rideout Hospital computer problems

    http://www.appeal-democrat.com/opinion/letter-re-rideout-computer-problems/article_4a408cc0-be47-11e4-9b7b-93c22da930d4.html 

    Friday, February 27, 2015 

    I am writing in regard to comments made by the CEO of Rideout Hospital regarding its recent computer crash. 

    He said quality of care for patients had not been compromised during this incident. He is lying.

    My spouse went to Rideout almost two weeks ago and had a Lexiscan of her heart when the computer system went down. The hospital doctor released her and assured her that if anything were wrong, the radiology department would spot it and she would inform us.

    Here it is two weeks later and now they are saying because of the computer problem the entire test didn't get to her cardiologist until today. They think she may have had a minor heart attack and needs further cardiac intervention.

     Is this the new "open and improved" truths we are getting from this hospital? Rideout CEO Robert Chason misinformed us all. 

    I am sure my spouse, who has fallen through the cracks during this inexcusable lapse in Rideout's technical policies, is not the only patient suffering similar situations. 

    Shame on Chason for minimizing the effects of this catastrophe at our local hospital. 

    Edward Ferreira 
    Yuba City

    I am aware of another major EHR outage via Politico.com:

    4/9/15
    http://www.politico.com/morningehealth/0415/morningehealth17818.html

    MEDSTAR EHR GOES DARK FOR DAYS: MedStar’s outpatient clinics in the D.C. and Baltimore area lost access to their EHRs Monday and Tuesday when the GE Centricity EHR system crashed. The system went offline for scheduled maintenance on Friday and had come back on Monday when it suffered a “severe” malfunction, according to an email from Medstar management that was shared with Morning eHealth.

    “All of a sudden the screens lit up with a giant text warning telling us to log off immediately,” a doctor said. “They kept saying it would be back up in an hour, but when I left work Tuesday night it was still down.”

    This doctor told us that the outage was “disruptive and liberating at the same time. I wrote prescriptions on a pad for two days instead of clicking 13 times to send an e-script. And I got to talk to my patients much more than I usually do.

    But of course we didn’t have access to any notes or medication history, and that was problematic.” MedStar notified clinicians in the email that any information entered in the EHR after Friday was lost.

    I do not know if corporate issued the standard "patient safety was not compromised" line, but can almost predict it was uttered somewhere along the line.

    MedStar is a big healthcare system.  An outage for several days at its outpatient clinics is disruptive and will lead to harms in the short term, but also in the long term, that cannot be effectively tallied, due to lost information. 

    That includes information put on backup paper that fails to get entered when an EHR goes back up, as well as outright computer data loss as occurred here.

    Note the doctor's comments about the "liberating" aspect of being freed from health IT.  He/she could actually practice medicine, not computer babysitting.

    How many harms will come of this "major malfunction?"  There is no way to know.  However, hospitals cannot have it both ways.  If these systems are touted as improving safety, then safety is affected when they are down and emergency measures are put into place, resulting in chaos; and certainly when information simply goes to the "bit bucket."

    The answer?  Either far more redundancy, or far less reliance on "paperless" systems.

    There also needs to be mandatory reporting of EHR outages and root cause analysis so the incidence and the reasons can be studied, at the very least.

    -- SS
    8:59 AM
    EHRs and other clinical IT are touted as essential to improving safety, among many other benefits.

    Yet when hospital systems crash, the common refrain by hospital executives to the press, when such stories are reported, is "...but quality of care was not compromised."  

    In fact, I've made an indexing term for this refrain.  The following query link retrieves the posts so indexed, numbering almost 30 at present:  http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised

    One hospital in California 40 minutes north of Sacramento had a crash and its CEO made exactly that claim.  However, a patient's husband disagreed, and called the CEO a liar.  Why?  His wife was affected by the crash in a very unsafe manner.

    The Appeal-Democrat is a local news source for Sutter and Yuba counties, California, serving readers since 1860.  Emphases mine:

    Letter: Re: Rideout Hospital computer problems

    http://www.appeal-democrat.com/opinion/letter-re-rideout-computer-problems/article_4a408cc0-be47-11e4-9b7b-93c22da930d4.html 

    Friday, February 27, 2015 

    I am writing in regard to comments made by the CEO of Rideout Hospital regarding its recent computer crash. 

    He said quality of care for patients had not been compromised during this incident. He is lying.

    My spouse went to Rideout almost two weeks ago and had a Lexiscan of her heart when the computer system went down. The hospital doctor released her and assured her that if anything were wrong, the radiology department would spot it and she would inform us.

    Here it is two weeks later and now they are saying because of the computer problem the entire test didn't get to her cardiologist until today. They think she may have had a minor heart attack and needs further cardiac intervention.

     Is this the new "open and improved" truths we are getting from this hospital? Rideout CEO Robert Chason misinformed us all. 

    I am sure my spouse, who has fallen through the cracks during this inexcusable lapse in Rideout's technical policies, is not the only patient suffering similar situations. 

    Shame on Chason for minimizing the effects of this catastrophe at our local hospital. 

    Edward Ferreira 
    Yuba City

    Claims that hospital paralysis through health IT outages and malfunctions don't compromise patient care insult my intelligence.  Such claims insult the intelligence of patients and their families, too.  Outages and malfunctions nearly always compromise the quality and safety of care.
      
    Patient safety is put at risk because hospitals are not making adequate efforts to keep these systems up 24x7. Many might say they can't afford it.  You don't put in life-critical information systems half-baked, however. Not in medicine, anyway.

    Finally, the press, by accepting these Pinocchio-like statements from hospital administrations without severe challenge, only promote cavalier behavior of hospital executives.

    Hospital executives:  EHRs are so absolutely essential to patient safety, we spend hundreds of millions of dollars on them. When they crash, however, patient care is never compromised.
    -- SS
    1:41 PM
    This story about a  UK hospital that recently "went live"with an American electronic health record/enterprise command-and-control system (EPIC) was not only predictable, but expected considering the sorry state of the health IT industry in terms of clinical leadership and regulation.

    (It appears this was a "big bang" rollout, see http://www.ehi.co.uk/news/EHI/8845/cambridge-goes-for-epic-big-bang, an implementation method better suited for warehouses and widget suppliers than major hospitals.)

    Addenbrooke’s staff blame blood shortage on new eHospital
    By CambridgeNews  |  Posted: November 05, 2014
    http://www.cambridge-news.co.uk/Addenbrooke-8217-s-staff-blame-blood-shortage-new/story-24513716-detail/story.html

    By Freya Leng

    Members of staff at Addenbrooke's [hospital, http://www.cuh.org.uk/addenbrookes-hospital] have voiced their concerns about the new IT system which has been blamed for a blood shortage.

    Cambridge University Hospitals' eHospital went live on October 26 and is designed to improve the quality of care for patients by allowing clinicians and frontline staff to access patient information wherever they are, at the click of a button.

    I must put to rest this lie once again.  The unregulated, generally terrible software being sold by the so-called EHR vendors is NOT simply software to allow clinicians to  "access patient information wherever they are."  

    This is enterprise clinician and clinical resource command-and-control software, through which increasingly each transaction related to care must pass.  In other words, ERP packages to manage patient care, as one might manage inventory and shipping in a merchant enterprise:

    http://en.wikipedia.org/wiki/Enterprise_resource_planning

    Enterprise resource planning (ERP) is a business management software—usually a suite of integrated applications—that a company can use to collect, store, manage and interpret data from many business activities

    Unfortunately, the reductionist assumptions behind the conception, design, authoring and implementation of such ERP software - that hospitals and healthcare are linear, predictable processes - are both deadly wrong, and the beliefs of fools and the recklessly cavalier.

    To wit:

    But since the launch, the News has been contacted by a senior member of staff at Addenbrooke's who said the new IT system was having "serious consequences" on the "operational running of the service".

    In a letter, the staff member who does not want to be named [due to potential for retaliation - ed.], said: "The hospital has very little blood available due to transfusion lab technical failures. Truth - the new IT system is responsible."

    The letter also states the impact the shortage of blood has had on the hospital including the cancellation of all elective surgery until November 8 as well as impacting on any procedure that holds a risk of blood transfusion and organ transplantation.

    "I believe sufficient risk has been placed upon all patients under care of Addenbrooke's," the staff member said. "Someone needs to be responsible for the implementation of the new IT system."

    In my experience, the non-clinical executives who often select this technology, and the IT personnel who then implement the technology (often ignoring clinicians), do need to be held responsible for bad outcomes - in the courtroom.

    The News also understands the whole system went down for six hours at the weekend with staff reverting back to paper and all major trauma cases diverted elsewhere.

    There are numerous cases on this blog of disruptive and patient-endangering EHR system outages.  These are simply inexcusable regarding life-critical computing. The unexpected transitions back and forth between paper endanger patients.

    A doctor, who also did not want to be named, said the wifi system which supports all the ward rounds is "unfit for purpose" and is leading to gross inefficiency.

    If this is true, it once again represents the cavalier nature of those technologists rarely held accountable for mistakes that, of they occurred in other critical industries (e.g., aviation, nuclear energy) might leave smoldering ruins and radioactive clouds that would result in the end of their careers...at the very least.  Unfortunately, individual injured and dead patients are not quite as visible to the public.

    "The general feeling on the ground is that they could not have implemented the system any worse than they have done and without any doubt it has already significantly affected patient care." they said.

    This is consistent with my own personal experience with hospital IT departments in the U.S., where mistakes that I could not even have conceived of making, were regularly made - leaving me to have to point out and clean up the mess, at risk to my own career due to the reactions of the non-clinical IT leaders and staff to being shown their own inadequacy regarding clinical affairs.  (This was, of course, an odd reaction by people who'd never gone to medical school, let alone had doctoral or postdoctoral study, research and development experience in Medical Informatics.)

    A CUH spokesman said: "eHospital gives our staff more time with patients at the bedside, many of whom are frail, elderly and have complex conditions.

    Right, just those patients who are most vulnerable to IT debacles and the cascading errors that can result.

    "However, unlike banks, shops or travel agents, we cannot close our doors or stop our services to the hundreds of thousands of people we treat every year. So it was always going to be a challenge to implement such a massive change.

    That is a very poor excuse for IT malpractice.  It makes the reader believe everything possible in due diligence was done, that others' experience was completely paid attention to, etc.  The results give me great doubt about that...

    "Pathology was affected early last week, which led to a brief reduction in the number of tests, but we are increasingly operating as normal. We did carry out a successful 're-boot' of the system early on Sunday morning.

    There we go once again  the typical bureaucratic spin that "the malfunctions were minor, nothing to see here, move along, patient safety was not compromised"  (a recurrent refrain with its own index term on this blog, see the 25+ posts at http://hcrenewal.blogspot.com/search/label/Patient%20care%20has%20not%20been%20compromised) - while at the same time these systems are represented as revolutionizing medicine - except when they malfunction, at which time they have no meaningful effects on care.

    "The much bigger challenge we face is that the Trust is incredibly busy and we have limited numbers of beds available, and which need to be kept free for emergency cases. Operations will continue to be rescheduled until the community care for those who no longer need a hospital bed is in place. We do sympathise with the frustration that people feel and apologise for the delay they are experiencing."

    In my opinion, patients put at risk, and injured and dead patients need and deserve more than apologies for information technology malpractice.

    Especially at Cambridge University, where in my opinion, this whole affair is truly a world-class embarrassment.

    -- SS
    11:51 AM
    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
    7:40 AM
    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
    5:47 AM
    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
    6:17 AM
    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
    7:40 PM
    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

    11:08 PM
    I would like to pretend these incidents don't occur, but alas, they do. Of course, we only know about the ones that are reported.

    At "Indiana Power Surge" I wrote about the dangers of EHR "glitches" that do, but should not, cause catastrophic failure of clinical IT systems that clinicians are increasingly dependent upon to deliver healthcare.

    At "Another Episode in the Series: HIT Failure" I wrote about yet another hospital whose clinical IT suffered a "glitch" that caused the hospital to struggle for a week with computer failures.

    Here we go again, this seems almost daily now. Wait until hospitals and offices really try to push the envelope to get onboard the ARRA EHR gravy train by 2014:

    Strong winds damage Indian Hospital systems

    Posted: June 8, 2009 05:48 PM

    LAWTON Okla. - The Lawton Indian Hospital is trying to recover from damaging winds that came with a severe storm Sunday night, leaving the hospital without air-conditioning and severely crippled in their computer systems.

    The storm damaged a coil to a $200,000 cooler that provides air conditioning for the hospital. The power went off for a short time around 8:30.

    The power outage affected all their medical records, charts, everything that held patients' information. The only way to overcome the glitch was to resort to an old filing system. A system that used colors to match up what kind of care a patient needed.

    And with 55,000 files to pour through, the hospital has severely slowed down. Rows and rows of thousands of files. Each one containing a patient's history.

    Of course, there is the traditional disclaimer about how such outages NEVER, EVER jeopardize patient safety (see "Health IT Failure Never Puts Patients at Risk"):

    Despite this setback hospital officials remain optimistic.

    "The staff knows a lot of the folks, they know what's going on with them," said hospital Chief Executive Officer Hickory Starr.

    I can attest to memory not being an optimal way to practice medicine ...

    The outage has repercussions beyond inpatients:

    Even if the hospital could call all of the existing patients to let them know the hospital's system is down, he says that would not solve everything.

    "We have a lot of folks that show up here. Some that have appointments and a lot that do not."

    Then there are those who need refills on their prescriptions.

    "And we can not do refills because we can not pull up that electronic chart."

    Finally, the prevailing attitude that safety is an Act of Providence (in reality, safety is not an accident):

    Despite it all, most people remain pretty cheery.

    "Generally they are. There is always some frustration but this is one of those situations that just happens."

    One of those situations that "just happens" is days of EHR failure due to a power outage?

    It'll all be fixed soon:

    Hospital officials expect the computer systems back online late Monday or early Tuesday morning.

    Real soon.

    I repeat my oft-stated observation that IT culture will need to be reformed before IT will be able to "reform medicine."

    -- SS
    8:42 PM
    At "Dangerous Health IT Mismanagement, Spin Control and the World's Longest Teething Pains" I commented that executives always find that "patient safety is not compromised" when health IT malfunctions.

    Here's another hair-raising story from Down Under. Just a wee glitch:

    Power failure lasting 36 hours cripples hospital care

    By Kate Benson
    healthcareitaustralia.blogspot.com

    DOCTORS at more than 100 hospitals in the state could not access patient records or vital test results for up to 36 hours last weekend after a power failure crippled NSW Health's computerised database.

    Some records were lost, X-ray and pathology results could not be accessed and staff were forced to use whiteboards to keep track of emergency patients after the main server shut down at 9am on Saturday because of a faulty circuit-breaker.

    Back-up power from the Cumberland Data Centre, which provides computer access to the Greater Western, Greater Southern and Sydney West area health services also failed, plunging some of the busiest hospitals in the state into chaos.

    Thousands of patients were affected, with doctors and nurses forced to take notes on paper and go to other parts of the hospital to collect hard copies of results, extending treatment times and adding to the confusion.

    Some staff, who did not want to be named, said the weekend was chaotic and a shambles. One surgeon said it was fortunate no lives were lost.

    The chief executive of Sydney West Area Health Service, Steven Boyages, said hospital blackouts that lasted more than 30 to 60 minutes were unacceptable, but the Health Minister, John Della Bosca, insisted patients were not put at risk. "At no time was there any threat to patient care or safety," he said yesterday.

    The Opposition spokeswoman on health, Jillian Skinner, said the blackout was "a serious failure" with great potential for disaster.

    "Hospitals affected not only lost access to patient records, some lost some patient records altogether … and couldn't access X-rays unless they physically went to the X-ray department for a film copy," she said. "John Della Bosca should explain why the patient records system lost power, why back-up systems also failed, and whether patient safety was compromised."

    A spokesman for Mr Della Bosca said workers doing routine maintenance at the data centre had triggered the outage. No patients had reported problems connected to the blackout but a full investigation would be launched. "If necessary changes will be implemented to prevent a recurrence," he said.

    with Louise Hall

    BLACKED OUT
    Hospitals at Westmead, Auburn, Blacktown, Nepean, Lithgow, Mount Druitt, Cumberland, Blue Mountains, Dubbo, Bathurst, Orange, Mudgee, Parkes, Bourke, Albury, Queanbeyan and Goulburn were affected.

    Move along, nothing to see here. Patients were not put at risk. Who needs regulation? It would only stifle innovation.

    -- SS
    9:25 AM
    I've written about a physician who documents the HIT travails Down Under that parallel the ones we have here - and are going to have a lot more of in a mad rush to universal health IT supposedly by 2014.

    Staff in an Australian Hospital's ED basically revolted against a new system that totally failed ... twice in three days. The two accounts of the incident are interesting regarding the incompetence level that hospital IT departments are permitted and that is widely tolerated as if they were a priesthood, and the spin control often used as CYA for events that carry great potential for patient harm.

    Physicians should only have it one hundredth as well as IT personnel.


    Account 1:

    Hospital records system fails twice in one week
    ABC (Australian Broadcasting Company) News
    Posted Fri May 8, 2009 7:37am AEST
    Emergency doctors at Nepean Hospital in Sydney's west are scaling back a new electronic records system because of two failures in the space of four days.
    Hospital management says there was a slowdown in the system for two hours on Tuesday, following a widespread outage on Saturday.
    Staff at the Nepean Hospital have now stopped using some parts of the system, saying they have lost confidence in it. Medics will in some cases go back to using pen and paper to record patients' progress.
    The chief executive of the Sydney West Area Health Service Professor Steven Boyages has apologised to staff, but says the problems could continue for a year and a half, while the technology is being rolled out.
    "Like in every other industry, whether its banking or retail or travel, teething problems do occur," he said.
    "Whenever you experience a computer slowdown it's enormously frustrating. Particularly if you're dealing with patients."
    But Professor Boyages says patient safety has not been compromised. "The important thing to re-assure your listeners is that we have very effective back up systems in place," he said. [That's what's known as "spin control" - ed.]

    This raises several questions:

    • Computer systems that are up 24/7 are fairly common, including health IT systems. Who, exactly, is having "teething pains?" Surely not the entire healthcare or health IT industry, unless one considers the possibility of a baby that has thirty years worth of little teeth coming in. Perhaps it's incompetent IT department leaders who are doing the teething, at patient and physician expense?
    • A year and a half of more problems expected during "rollout?" [That's simply insane -ed.] What in hell is being rolled out?
    • Why, exactly, did the system slow down and then fail? Who was in charge of the project and of system architecture and redundancy? What sanctions do they face as a result of this debacle?
    • In the often chaotic environment of emergency medicine, disruptions to record keeping, even short lived ones, run the risk of irreversible error or catastrophe. Evidence of the concern of staff is their rejection of the system. How can the chief executive state that safety has "not been compromised?"
    • "Very effective backup systems in place?" Since the computer system went down, clearly this exec is not talking about IT. Perhaps the "backup system" is good, old fashioned paper and pencil?

    Others share my concerns, as well as concerns that these systems can be more of a hindrance than a help if designed improperly (the identity of the system is not mentioned, unfortunately).

    Account 2 of same story:

    Electronic medical records putting patients at risk – Nepean Hospital

    Posted 07/05/2009 at 05:12 PM by StreetCorner.AU

    Staff in the Nepean Hospital Emergency Department have banned the use of the new electronic medical records system after it failed for the second time in three days on Tuesday, putting patients at risk, Shadow Minister for Health Jillian Skinner said today.

    According to Jillian Skinner, medical officers have revealed the latest shut down at the Nepean Hospital ED on Tuesday lasted for two hours, leading to staff deciding on Wednesday they no longer had faith in the new system.

    “Staff report the electronic medical records system is so cumbersome that senior medical officers who previously saw 8-10 patients in a shift, are only getting through 5-7 because they spend so much time trying to access or enter information” said Mrs Skinner [a.k.a. a mission hostile user experience, itself potentially deadly in an emergency department - ed.]

    “When the system failed again on Tuesday it meant there were no records of what a patient was there for, no record of treatment so far, no record of tests ordered, no record of test results and no record about what medication may have been given. Skinner reported that emergency staff at Nepean Hospital decided yesterday to pull the pin on using electronic records and are now working with pen and paper because they don’t trust electronic medical records system.

    A situation in an ED where "there are no records of what a patient was there for, no record of treatment so far, no record of tests ordered, no record of test results and no record about what medication(s) may have been given" would seem to my medical mind to reflect a risk to patient safety. Fortunately there are some in the press who report such issues in a credible manner.

    It also seems this system either presented a Mission Hostile User Experience, or a Blue Screen of Death User Experience to clinical users.




    Considering the contractual blackout that exists in the U.S. on information regarding health IT failures, one wonders how many situations of failure "that don't compromise patient safety" occur on a daily basis on this side of the equator.

    At some point, hospital IT departments and leaders will need to be subject to the same rigor as other key hospital employees. Letting them act as an unaccountable priesthood who, when they screw up, are given absolution by executives equally complicit in defending the mediocre, rather than being subjected to Darwinian forces, must end before patients get killed.

    -- SS
    12:03 PM