Showing posts with label Mismanagement. Show all posts
Showing posts with label Mismanagement. Show all posts

Thursday, 17 March 2016

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

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

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


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


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

and

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


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

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

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

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

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

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

Here's details from the first article:

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

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

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

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

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

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

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

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

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

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

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

Money for EHR's grows on trees.

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

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

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

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

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

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

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

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

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

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

"No glitches?" 

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

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


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

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

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

Epic Staffing Guide 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This is exactly how patients end up maimed and dead.

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

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

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

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

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

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

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

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

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

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

-- SS

What is Criminal Negligence?

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

What is Criminal Negligence?

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

What is Criminal Negligence?

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

What is Criminal Negligence?

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

What is Criminal Negligence?

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

Friday, 25 September 2015

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

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

Dear Queen Elizabeth,

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

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

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

In that post I observed:

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

And now this:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Among their key findings were:

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

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

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

Clearly, the CQC does not mean a positive impact.

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

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

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

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

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

Despite this patients received excellent care.

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

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

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

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

 Ditto.

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

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

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

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

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

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

That theory is likely confirmed by the following:

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

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

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

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

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

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

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

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

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

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

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

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

Sincerely,

S. Silverstein, MD
Drexel University
Philadelphia, PA

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

Addendum:

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

-- SS
    Baca selengkapnya