Showing posts with label healthcare IT deaths. Show all posts
Showing posts with label healthcare IT deaths. Show all posts

Wednesday, September 18, 2013

Updates on Three Medical Malpractice Cases Involving EHR's

Scorecard:

Case 1 - dead adult due to failure to intubate when in respiratory distress, causing anoxia and brain death; allegations of EHR alteration; case delayed six months due to newspaper publicity.
Case 2- adult renal failure patient infected with hepatitis C from transplant; lawsuit just filed.
Case 3 - dead baby due to x-ray never being read; hospital filed a Motion to Compel Settlement Conference.

The details:

Case 1:

Trial to begin in wrongful death claim
Monday, September 19, 2011
By Sean D. Hamill, Pittsburgh Post-Gazette

As far as Samuel Sweet was concerned, he only had a headache. It was a bad one, but nothing more, maybe something his chiropractor could fix with a little adjustment.

But three days after being admitted to UPMC Presbyterian for what his family was told was a treatable amount of bleeding on the brain, and six hours after his family saw him laughing and chatting about the Penguins' playoff chances, early in the morning of May 16, 2009, Mr. Sweet died unexpectedly.

Why he died is the subject of a civil case his family filed a few months later that is set to be heard by a jury as early as today in Allegheny County Common Pleas Court. [Read the whole story at link above - ed.]

Set to be heard by a jury as early as today (i.e., Sept. 19, 2011)? Well, no, actually. As a result of this newspaper story, the defendants filed a complaint with the judge, who ordered a six month delay in further proceedings. The complaint and decision is at this link (PDF).

Apparently, sanctions sought by the defendants against the plaintiff's attorney for "leaking" public information to the public about matters affecting their own health and safety were denied.

I find the allegations of EHR alteration of interest:

... [Plaintiff attorney] Ms. Maliver said UPMC's timeline came into question in early August 2011, when UPMC finally turned over -- after two years of discovery [i.e, they turned them over at the last minute, a few weeks before trial was scheduled to begin - ed.] -- 1,200 pages of "results detail sheets" which show not only when something was written in Mr. Sweet's electronic chart, but who wrote it and how.

[They possibly never expected someone to actually go through the 1,200 pages in detail on such a short time frame, but, apparently, the plaintiff's attorney took on the challenge - ed.]


So, for example, Ms. Maliver alleges that the results detail sheets show that during the 21 minutes before Mr. Sweet was said to stop breathing, none of the information in his chart is straight from the computer monitors that would tell what his vital signs were during that period.

But the results detail sheets also show something more troubling, Ms. Maliver said.

She said she found evidence that three days after Mr. Sweet died, Dr. Richard Simmons, UPMC Presbyterian's head of quality assurance, tried to put a "Diff Intub" [difficult to intubate, due to anatomy - ed.] red-letter warning on Mr. Sweet's electronic medical record. That effort showed up on the results details sheets, according to Ms. Maliver.

Such a warning would tell anyone who opened the record that Mr. Sweet was difficult to intubate.

Dr. Simmons wasn't trying to alter the record, [attorney for the defendants] Mr. Conti said
; instead he was in Mr. Sweet's medical record as part of the "peer review" process, assessing what happened in Mr. Sweet's case.

As part of that, he was in the medical record three days after Mr. Sweet died trying to figure out how one would create a warning about a patient's difficult intubation [in effect, altering the record, at the very least through creation of a confusing audit trail - ed.], Mr. Conti said.

Moreover, Mr. Conti said, such a warning was irrelevant because "Dr. Kaura said he understood Mr. Sweet was a difficult airway just by looking at him." [In the picture of the patient in the newspaper article, I cannot tell that; perhaps Dr. Kaura could get a new career as a clairvoyant. In any case, the clairvoyance seemed insufficient for expert help to be called in a timely fashion, i.e., STAT - ed.]

I have problems with this explanation of EHR fiddling, coming from a defense attorney regarding someone who, as head of quality assurance, must have been extremely well-versed in 1) peer review, 2) the code of conduct regarding medical record alteration e.g., in the Pennsylvania Medical Care Availability and Reduction of Error (MCARE) Act of 2002 (PDF, see Section 511, "Preservation and accuracy of medical records", pg. 18-19), and 3) electronic health records systems, metadata, audit trails (and the difficulties in deciphering them), etc.

I suggest several possibilities.

The head of quality assurance was:

  • Merely experimenting with the EHR during Peer Review for his own education, using the chart of a dead man who died under conditions suspicious for malpractice, rather than a dummy chart or test environment created for the purpose;
  • Experimenting with the EHR using the chart of said dead man to educate the staff on how to place the appropriate warning about difficult intubations;
  • Trying to discover if Windows was superior to Mac OS X by comparing to a MacBook Air in his lap;
  • Seeing if he could generate Windows protection faults through aggressive fiddling;
  • Looking for the "Super Mario" game on the computer;
  • Attempting to spoliate crucial medical information that could put the physicians and medical center at risk of liability.

I leave it to the reader to decide which possibilities are most likely.

My comments are that:

  • I feel sorry for the family, who must now endure six more months of suspense and suffering absent their loved one, and
  • I am concerned about public health issues, the public being potentially exposed to six more months of risk that will not be investigated until the case resumes.

Additionally, in an April 2009 post "UPMC as 'Proving Ground' for IT Tests On Children: Pioneers in Health IT, or Pioneers in Ignoring the Past?" I noted that as in a May 2006 article in the Pittsburgh Tribune entitled "UPMC partners with technology provider":

... The University of Pittsburgh Medical Center is taking another step in a quest to commercialize new medical technology.

UPMC on Monday signed a three-year deal with health care information technology provider Cerner Corp. to develop and market medicine-related technological advances. Both parties will contribute $10 million in cash, services and intellectual property to the effort.

The deal is a smaller version of an April 2005 deal between UPMC and information technology behemoth IBM.

As is the case in the IBM deal, UPMC will serve as a built-in proving ground for jointly developed technologies and products, with Cerner marketing the products and UPMC awarded a share of profits.

I wrote, somewhat incredulously:

"Proving ground?"I cannot believe I am reading such a claim. A hospital and patients, as I have written before, are not a learning lab for HIT vendors. The appropriate "proving ground" for new medical technology is the controlled clinical trial where participants (in this case, patients and healthcare professionals alike) have freedom of choice whether or not to participate, and a chance to give (or deny) consent after being fully informed of potential risk.

Were patients or their parents asked to give consent to the use of HIT (such as here)? Were they even aware they were serving as subjects of a "proving ground?" Likewise for clinicians?

... Using a hospital as a "proving ground" for unproven HIT on unconsented or coerced subjects (e.g., children, their parents, and the doctors themselves) [or adults themselves - ed.] probably amounts to battery at the very least, is consistent with violations of fiduciary and Joint Commission safety standards, and I am concerned about it representing human rights violations as well.

In view of the recent Koppel and Kreda paper in JAMA on "hold HIT vendors harmless" and "defects gag" clauses, this entire arrangement seems incredibly disturbing at the very least.I also believe the conflict of interest represented by a healthcare organization partnering with a vendor to "commercialize new medical technology" on unconsented subjects while sharing profits is a horrendous development, for as I stated, the appropriate settings for such practices are properly conducted, impartial clinical trials. The potential for abuses in the current arrangement seems uncomfortably high.

My sentiments seem aligned with IOM's recommendation 4.1 and others on Conflict of Interest as pointed out by fellow HC Renewal blogger Bernard Carroll at this post:


Academic medical centers and other research institutions should establish a policy that individuals generally may not conduct research with human participants if they have a significant financial interest in an existing or potential product or a company that could be affected by the outcome of the research. Exceptions to the policy should be made public and should be permitted only if the conflict of interest committee (a) determines that an individual’s participation is essential for the conduct of the research and (b) establishes an effective mechanism for managing the conflict and protecting the integrity of the research…” (page S-14).

One might reasonably ask if there was a motive to "protect" the health IT when it was suspected of contributing to a patient death. (There was, apparently, the means and opportunity.)

Case 2:


Also from Pittsburgh, and is in followup to my May 2011 postings on a kidney transplant from a hepatitis-C donor entitled "Transplant Team at UPMC Missed Hepatitis Result - Suspicious for Health IT Failure?" and "Healthcare Renewal Cited in Pittsburgh Post Gazette on Health IT Issues."

The affected patients have now sued:

UPMC sued over botched kidney transplant
Tuesday, September 20, 2011
By Sean D. Hamill, Pittsburgh Post-Gazette

A Greene County couple involved in a botched kidney transplant that led to a two-month shutdown of UPMC's living donor kidney and liver transplant programs -- and to state and federal investigations -- filed two malpractice lawsuits this morning in Allegheny County Common Pleas Court.

Christina Mecannic and Michael Yocabet sued UPMC, University of Pittsburgh Physicians, four doctors and one nurse after federal investigators determined that an entire transplant team missed a test result that showed Ms. Mecannic was infected with hepatitis C when her kidney was transplanted into Mr. Yocabet on April 6

A Greene County couple involved in a botched kidney transplant that led to a two-month shutdown of UPMC's living donor kidney and liver transplant programs -- and to state and federal investigations -- filed two malpractice lawsuits this morning in Allegheny County Common Pleas Court.

Christina Mecannic and Michael Yocabet sued UPMC, University of Pittsburgh Physicians, four doctors and one nurse after federal investigators determined that an entire transplant team missed a test result that showed Ms. Mecannic was infected with hepatitis C when her kidney was transplanted into Mr. Yocabet on April 6

The complaints can be retrieved from these links: Yocabet, Mecannic (PDF).

Of interest, there are allegations of intimidation by doctors of the donor once they discovered that the donor was Hep-C positive, with questions about cocaine use, infidelity, etc.

Further, computers are featured relatively prominently in the actual complaint points, e.g., Count 96, emphases mine:

96. Defendant UPP was negligent and showed reckless indifference to Plaintiff in the following particlulars:
  • Creating an environment that jeopardized patient safety;
  • Allowing an environment that jeopardized patient safety;
  • Creating an environment that encouraged volume at the expense of patient safety;
  • Allowing an environment that encouraged volume at the expense of patient safety;
  • In failing to promulgate and/or enforce rules, regulations, procedures and standards to ensure that kidney transplants are only performed with suitable patients;
  • By placing financial gain over the safety of its patients;
  • In failing to provide adequate safeguards to ensure that kidney transplant recipients do not receive kidneys from a donor that is positive for Hepatitis C;
  • In having a medical records system in place that fails to properly alert its transplant team of an unsuitable donor;
  • In having a medical records system in place that fails to properly alert its transplant team of abnormal test results;
  • In failing to ensure that medical personnel are properly trained to recognize patients that are not proper candidates to be kidney donors;
  • In failing to properly supervise their staff that provided care to Plaintiff during his admission; and
  • In failing to assure that staff are properly trained and/or supervised in interpreting test results.

My comment here is that, if the doctors and nurses were compelled to use the electronic medical record system and had no other means of being informed of the hepatitis-C result, they should consider counter-suits against the hospital system and/or vendor for forced use of FDA-unapproved, defective (e.g., mission hostile) medical devices known to cause error and injury.


Case 3:

This is in followup to my report of the death of a premature infant in Pennsylvania, as in my June 2011 post "Babies' deaths spotlight safety risks linked to computerized systems."

The news here is that on Sept. 1, 2011 the hospital filed a "Motion to Compel Settlement."

Of interest, a plaintiff's amended complaint still includes issues related to computers, e.g., Count 42:

42. Upon information and belief, the incorrect date on the image caused the xray not to be read by a radiologist on the night the image was taken, and that if the image had been correctly dated February 27, 2010, it would have been reviewed by a radiologist immediately, who would have alerted Defendants that the PICC line was improperly positioned and had to be moved back to a safe position. However, since the film was incorrectly dated February 23, 2010, the film was classified as “old” [i.e., cybernetically, by the PACS system - ed.] and was not put in line for immediate review [in effect, the computer determined the clinicians' work flow - ed.], and was not reviewed in time to prevent injury to Plaintiff’s Decedent.

And count 57:

57. The death of Destinee and the losses directly related to her death, were the direct and proximate result of the negligence and carelessness of Defendant, Lindsay Davison, either individually and/or by and through her respective agents, and/or servants, and/or employees, and/or ostensible agents acting through and within the course and scope of their employment, consisting of, but not limited to one or more of the following;

a. failing to obtain an x-ray image of sufficient quality to adequately confirm that the PICC line was safely and properly inserted;
b. failing to recognize that the x-ray image referred to above was of an inferior quality such that it could not be used to confirm that the PICC line was safely and properly inserted;
c. failing to properly associate the correct identifying information about the patient with the x-ray that was taken to confirm the proper placement of the PICC line;
d. failing to put the right date on the x-ray that was taken to confirm the proper placement of the PICC line;
e. causing the x-ray of February 27, 2010 to be mislabeled and/or misdated and/or to not be read in a timely fashion [apparently due in part to computer decision-making about "old" films - ed.]; and
f. failure to prevent harm to Destinee and causing her death.
And:

Count 65, part o: "failing to have in place and enforce policies and procedures in the use of x-ray information and data systems."

I am surprised there is no component of the lawsuit against the PACS vendor for selling defective products.

As I mentioned previously, a computer programmed to consider an "old" but unread x-ray as unimportant (instead of critical to read, due to the effects it might have on the interpretation of later films) and that did not trigger an alarm to wake the dead (no pun intended) is, on first principles, defective.

My overall comment is that these lawsuits demonstrate hospitals had better get their acts together regarding clinical information technology, fast, or they will find their ROI's on the equipment turning sharply and ominously negative.

-- SS

Monday, September 16, 2013

An Open Letter to David Bates, MD, Chair, ONC FDASIA Health IT Policy Committee on Recommendations Against Premarket Testing and Validation of Health IT

From http://www.healthit.gov/policy-researchers-implementers/federal-advisory-committees-facas/fdasia:

The Food and Drug Administration Safety Innovation Act (FDASIA) Health IT Policy Committee Workgroup is charged with providing expert input on issues and concepts identified by the Food and Drug Administration (FDA), Office of the National Coordinator for Health IT (ONC), and the Federal Communications Commission (FCC) to inform the development of a report on an appropriate, risk-based regulatory framework pertaining to health information technology including mobile medical applications that promotes innovation, protects patient safety, and avoids regulatory duplication.

My Open Letter to the Committee's chair speaks for itself:

From: Scot Silverstein
Date: Mon, Sep 16, 2013 at 9:39 AM
Subject: ONC FDASIA Health IT Policy Committee's recommendations on Premarket Surveillance
To: David Bates

Sept. 16, 2013

David Bates, Chair, ONC FDASIA Health IT Policy Committee
via email
   
Dear David,

I am disappointed (and in fact appalled) at the ONC FDASIA Health IT Policy Committee's recommendations that health IT including typical commercial EHR/CPOE systems not be subjected to a premarket testing and validation process.  I believe this recommendation is, quite frankly, negligent. [1]

As you know, my own mother was injured and then died as a result of EHR deficiencies, and nearly injured or killed again in the recuperation period from her initial injuries by more health IT problems in a second EHR used in her care.  In my legal consulting and from my colleagues, as well as from the literature, I hear about other injuries/deaths and many "near misses" as well.  That your recommendations came in the face of the recent ECRI Deep Dive study is even more appalling, with the latter's finding of 171 health IT-related incidents in 9 weeks from 36 member PSO hospitals, resulting in 8 injuries and 3 possible deaths, all reported voluntarily. [2]

It is my expert opinion the issues that cause these outcomes would never have made it into production systems, had a reasonable, competent, unbiased premarket testing and validation process been in place.

Consequently, I have shared the FDASIA HIT Policy Committee's recommendations with the Plaintiff's Bar, and will use its recommendations in my presentations to various chapters of the American Association for Justice (the trial lawyer's association) - as well as to interested Defense attorneys so they may advise their clients accordingly.

I am also making recommendations that in any torts, individual or class, regarding EHR problems that would likely have been averted with competent premarket testing and validation, that the FDASIA HIT Policy Committee members who agreed with the recommendation be considered possible defendants.

I am sorry it has come to this.

Please note I am also posting this message for public viewing at the Healthcare Renewal weblog of the Foundation for Integrity and Responsibility in Medicine (FIRM).

Sincerely,

Scot Silverstein, MD
Consultant/Independent Expert Witness in Healthcare Informatics
Adjunct Faculty, Drexel University, College of Computing and Informatics

Notes:


[1] FDA Law Blog, Recommendations of FDASIA Health IT Workgroup Accepted, September 11, 2013, available at http://www.fdalawblog.net/fda_law_blog_hyman_phelps/2013/09/recommendations-of-fdasia-health-it-workgroup-accepted.html: "Of particular interest is the recommendation that health IT should generally not be subject to FDA premarket requirements, with a few exceptions:  medical device accessories, high-risk clinical decision support, and higher risk software use cases."

[2] "Peering Underneath the Iceberg's Water Level: AMNews on the New ECRI 'Deep Dive' Study of Health IT Events" , Feb. 28. 2013, available at http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html.

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

Note: the following are listed on the linked site above as members of the committee:

Member List
  • David Bates, Chair, Brigham and Women’s Hospital
  • Patricia Brennan, University of Wisconsin-Madison
  • Geoff Clapp, Better
  • Todd Cooper, Breakthrough Solutions Foundry, Inc.
  • Meghan Dierks, Harvard Medical Faculty, Division of Clinical Informatics
  • Esther Dyson, EDventure Holdings
  • Richard Eaton, Medical Imaging & Technology Alliance
  • Anura Fernando, Underwriters Laboratories
  • Lauren Fifield, Practice Fusion, Inc.
  • Michael Flis, Roche Diagnostics
  • Elisabeth George, Philips Healthcare
  • Julian Goldman, Massachusetts General Hospital/ Partners Healthcare
  • T. Drew Hickerson, Happtique, Inc.
  • Jeffrey Jacques, Aetna
  • Robert Jarrin, Qualcomm Incorporated
  • Mo Kaushal, Aberdare Ventures/National Venture Capital Association
  • Keith Larsen, Intermountain Health
  • Mary Anne Leach, Children’s Hospital Colorado
  • Meg Marshall, Cerner Corporation
  • Mary Mastenbrook, Consumer
  • Jackie McCarthy, CTIA - The Wireless Association
  • Anna McCollister-Slipp, Galileo Analytics
  • Jonathan Potter, Application Developers Alliance
  • Jared Quoyeser, Intel Corporation
  • Martin Sepulveda, IBM
  • Joseph Smith, West Health
  • Paul Tang, Palo Alto Medical Foundation
  • Bradley Thompson, Epstein Becker Green, P.C
  • Michael Swiernik, MobileHealthRx, Inc.
Federal Ex Officios
  • Jodi Daniel, ONC
  • Bakul Patel, FDA
  • Matthew Quinn, FCC

 -- SS

Friday, July 13, 2012

Did Toxic Effects of an EHR Kill Rory Staunton?

A stunning story about the death of a young man from sepsis (blood poisoning by infection), missed in an ED, appeared in the New York Times:

An Infection, Unnoticed, Turns Unstoppable

By JIM DWYER
New York Times
Published: July 11, 2012

For a moment, an emergency room doctor stepped away from the scrum of people working on Rory Staunton, 12, and spoke to his parents.

“Your son is seriously ill,” the doctor said.

“How seriously?” Rory’s mother, Orlaith Staunton, asked.

The doctor paused.

“Gravely ill,” he said.

How could that be?

Two days earlier, diving for a basketball at his school gym, Rory had cut his arm. He arrived at his pediatrician’s office the next day, Thursday, March 29, vomiting, feverish and with pain in his leg. He was sent to the emergency room at NYU Langone Medical Center. The doctors agreed: He was suffering from an upset stomach and dehydration. He was given fluids, told to take Tylenol, and sent home.

Partially camouflaged by ordinary childhood woes, Rory’s condition was, in fact, already dire. Bacteria had gotten into his blood, probably through the cut on his arm. He was sliding into a septic crisis, an avalanche of immune responses to infection from which he would not escape. On April 1, three nights after he was sent home from the emergency room, he died in the intensive care unit. The cause was severe septic shock brought on by the infection, hospital records say. 

Rory Staunton, age 12, 5 feet 9 inches tall and 169 pounds, had suffered a cut on his arm.  He presented with a marked fever of 102 F (39 C), pulse markedly elevated at 131, respiratory rate elevated at 22; reported to have hit as high as 36 breaths per minute (in essence, panting).  It was reported by the NYT that before the ED visit his parents said his temperature had reached 104 F (40 C).

That alone should have set off some level of concern.  (It is possible narrative details of his history never made it into the ED chart; ED EHR's are often templated point-and-click affairs that can impair or discourage capture of narrative.)

Per the NYT, the bacteria Streptococcus pyogenes normally dwells in the throat or on the skin, areas where the body is well defended.  Also known as Group A streptococcus, the strain typically causes strep throat or impetigo.  However, if it gets into the blood stream (e.g., via a cut in the skin, as this patient suffered playing ball), the results can be devastating.

The lab results from the first ED visit are particularly stunning:


(From NYT article; click to enlarge)


The white blood cell count is markedly elevated at 14.7, meaning 14,700 cells per microliter of blood (cubic millimeter or 1 mm3).  Further, there is a plain evidence of greatly accelerated new white cell production, in the form of "bands", at 53% of the total (normally 5-15%).  Bands are immature white blood cells that are seen in the blood, being produced as part of the body's response to infection.

Herein is a significant issue.  The NYT noted that:

"Three hours later [i.e., after the ED visit, which reportedly only lasted 2 hours - ed.], Rory’s blood tests came back. High levels of neutrophils and “bands” – immature white blood cells – are evidence of infection. But nobody called the Stauntons, and by the time Rory returned to the hospital the next day, his infection was unstoppable. He died two days later."

Not getting into the issue regarding the patient apparently being discharged before the labs got back (itself an invitation to disaster), and the other abnormalities such as low sodium, low platelets, elevated glucose all pointing to a very sick patient... nobody called the Stantons with white cell results like these?   Nobody entertained the thought of ... antibiotics as a precaution?

It is possible - dare I say likely - that no clinical person in the ED ever saw these results.

EHR's that are poorly designed or implemented can have a toxic effect on care.  For instance, EHR's can cause user confusion if the user interface is complex, data can be lost due to poor relational design.  Data from the wrong patient's data can be presented (misidentification), or data from a lab can come back to the system after a patient has left, and despite being abnormal, just sit there in a silo without being looked at ("out of sight, out of mind"; a "silent silo" syndrome).

It is usually difficult to ascertain exactly which EHR product is being used at a particular hospital.  I note this medical center actively promoted its EPIC EHR in a June 2011 press release "NYU Langone Medical Center Launches Next Phase of Its Electronic Health Record System", although another system "ICIS"  (for Integrated Clinical Information System, "a state-of-the-art healthcare information management system that connects all NYULMC caregivers involved in patient care") is mentioned here.  The ICIS may also contain the Eclipsys Sunrise Clinical Manager, per this link. (I'd noted some clinically relevant problems with the latter in an FDA report here.)

In any case, magical powers are attributed to the technology that are not strongly or uniformly supported by the literature (link), but strongly pushed by industry marketing memes of deterministic health IT benefits and absolute beneficence:

“... Our electronic health record system is an integral part of our ongoing efforts to leverage technology and enhance our ability to provide patient-centered care and enable the highest level of quality care management,” said Bernard A. Birnbaum, MD, senior vice president and vice dean, chief of hospital operations at NYU Langone. “These front-end and back-end services are an important step in assuring our patient’s experience from beginning to end is a seamless one.”

I've documented examples of situations where EHR's and other IT components of clinical ERP systems (enterprise resource planning and management systems, a term that more accurately describes what exists in many hospitals now than the misleading, file cabinet-evoking term "EHR") contributed to or caused patient harm, such as at "Babies' deaths spotlight safety risks linked to computerized systems" - a computer error caused a central line placement x-ray to have gone unread, leading to death; "The Sweet death that wasn't very sweet" - a missing "difficult intubation" EHR flag led to a middle-aged man suffocating during an intubation attempt; and others.  An Australian researcher thoroughly studied the potential risks of an EHR meant specifically for ED's ("A Study of an Enterprise Health information System", PDF executive summary at this link).

The following passage in the NYT article also offers another clue:

... Two hours later, though, he had three [signs of sepsis]: his temperature had risen to 102, his pulse was 131 and his respiration rate was 22. But by the time those vital signs were recorded, at 9:26 p.m., they had no bearing on his treatment. In fact, the doctor had already decided that Rory was going home. Rory’s “ExitCare” instructions, signed by his father, were printed 12 minutes before those readings. 

Did those readings escape notice due to delayed charting (data entry), a common problem with EHRs in busy clinical environments?

The Institute of Medicine in its 2011 IOM report on health IT safety admitted harms are reported but the magnitude of harms is unknown due to multiple reporting impediments, as did the FDA in its 2010 internal memo on "H-IT Safety Issues" divulged by the Huffington Post Investigative Fund (see here and here).  The National Institute of Standards and Technology (NIST) admits in its 2011 report on HIT usability that EHR usability is often poor and may lead to "use error" (error caused or promoted by poor design, as distinguished from simple user error, see here), magnitude of problem also unknown.

In a startling medical situation such as Rory Stanton's, where crucial labs seem to have evaporated causing or contributing to delayed treatment of a devastating and obvious illness, I believe EHR-related factors need to be examined and ruled out first.

For, quite simply, if the EHR caused or contributed to this tragic debacle, the public could be at risk.


-- SS

Additional thought:  could this be the "cybernetic Libby Zion case" I've written of?

-- SS

July 18, 2012 Addendum:

The Stauntons, who appeared on the NBC Today Show are seeking to create a “Rory’s Law” in New York to ensure that parents have full access to blood and lab tests done on their children as soon as results are available, and that a doctor will be present to assess the findings. Story here.

-- SS

Wednesday, September 28, 2011

Propofol and Other Drug Questions: Was Michael Jackson a UPMC Patient at the Same Time as Samuel Sweet?

At my Sept. 24, 2011 post "UPMC and the Sweet death that wasn't very sweet: How EMRs can detract from a clear narrative, and facilitate spoliation and obfuscation of evidence" I wrote a detailed summary of a civil medical malpractice Complaint regarding possible electronic chart alteration. As I pointed out, that Complaint made EMR metadata visible to laypeople for the first time that I am aware.

A new docket has appeared in that case entitled "Interrogatories to Defendant" from Attorney/physician Deborah Maliver dated Sept. 27, 2011.

This document is publicly downloadable from the Pittsburgh Prothonotary Office Civil Docket site at this link, case #GD-09-019407, document #55, or at my cached version at this link (PDF).

It brings up questions of even greater concern to me as a physician, those of mysterious drug orders for powerful sedatives such as propofol, fentanyl and etomidate. Apparently the metadata makes it difficult to account for what could be questioned as "over-generous" dispensing of those drugs.

(This is ironic, since the trial of the doctor who administered this drug to deceased singer Michael Jackson has itself just gotten underway.)

Here is the first interrogatory request listing numerous drugs:


Question 1. Request for full metadata on these drugs (click to enlarge)


See Exhibit "A" from the new Interrogatory docket below, as produced in discovery earlier, and download the new Interrogatory in its entirety to see the questions asked about the other metadata:

Exhibit "A". McKesson drug cabinet dispenser audit trail. Five 100-ml vials of propofol in a row from May 14-May 15? Lorazepam (ativan), propofol and etomidate on May 15-16 at a time when a patient had a deteriorating respiratory status? (These drugs suppress the respiratory drive.) Click to enlarge.


Question 4 is particularly disturbing:

(click to enlarge)


Apparently none of these drugs appeared in the eMAR system, the electronic medication administration record. Where did they go? I hope the full audit trails will show a definitive final disposition of these drugs.

One would hope a highly computerized medical center could keep track of its inventory of drugs of powerful potential for abuse with 100% certainty, chain-of-custody style (that means, 0% guesswork):

Chain of custody (CoC) refers to the chronological documentation or paper trail, showing the seizure, custody, control, transfer, analysis, and disposition of evidence, physical or electronic.

This is of concern to me as a former Occupational Medicine physician (in the transit industry) and a physician in general. I've seen drug abuse result in train wrecks - literally. Drug abuse/failure to be able to track disposition in a hospital would represent a prima facie public health menace.

There are also questions about whether users of the EMR signed in or used the accounts of other individuals, which is another weakness of the EMR. No handwriting to evaluate...

-- SS

10/24/11 Addendum:

Here is a horrible example of what can go wrong when drugs of abuse potential are not tracked with the utmost of rigor:

Star Tribune/Minneapolis

Abbott Northwestern patient left 'writhing in pain' sues

"Hi, love," Sarah May Casareto greeted Larry V. King as he lay on a gurney before surgery. As they wheeled down the hall, he recalled in court records, she told him that he'd have to "man up" because they couldn't give him a lot of medication.

The next 57 minutes of surgery were excruciating, according to a lawsuit filed Tuesday in Hennepin County District Court that accuses the drug-addicted former nurse of skimming his narcotics, which left him "writhing in pain" during a medical procedure for kidney stones last year at a Minneapolis hospital.

Casareto, of Forest Lake, entered an Alford plea of guilty Sept. 1 to a fifth-degree controlled substance crime for possessing Fentanyl, a high-powered painkiller, and was sentenced to probation in connection with the Nov. 8 incident at Abbott Northwestern Hospital. The plea enabled Casareto to maintain her innocence while acknowledging ample evidence to convict her.

The suit, which seeks at least $50,000 in damages, alleges that she was "negligent and careless" in her care for King, 57, of Bloomington. The suit also names Abbott as a defendant.

It contends that Abbott "knew or should have known [before the procedure] that Casareto was exhibiting drug-seeking behavior and that she had become dependent upon narcotic pain medications." It also notes that Abbott officials knew that she had failed "on at least six different occasions" to properly handle patients' pain medication obtained from the hospital pharmacy.

King's attorney, Tony Nemo, called the lawsuit reflective of "a growing problem" that should draw closer scrutiny to drug diversion, or the theft of medications intended for patients.

"One of the things I know Mr. King is hoping is that this case may cause Twin Cities hospitals to reveal procedures and protocols to, if not prevent, at least minimize this problem in the future," he said.

I wonder if information technology problems regarding tracking of drugs with abuse potential existed.

Read the whole article at the above link.

-- SS

Saturday, September 24, 2011

UPMC and the Sweet death that wasn't very sweet: How EMRs can detract from a clear narrative, and facilitate spoliation and obfuscation of evidence

The world of electronic medical records is very secretive.

Vendors will not allow their programs or data structures to be examined, even by the academic community. Their products, medical devices, are not vetted by regulatory agencies such as the FDA for quality.

Patients and clinical personnel are supposed to take the word of the seller that these systems are fit for purpose and of high quality.

A window into the internal working of EMR's was initiated Down Under just this year, in the form of a detailed internal analysis of an ED EMR product from America slated for roll-out in public hospitals in one of Australia's most populous states. Dr. Jon Patrick of the University of Sydney performed this work. He was not happy with what he found, in terms of software engineering, human computer interaction, and other issues related to fitness for purpose. See here and here.

(For more on healthcare IT difficulties, see "Contemporary Issues in Medical Informatics: Common Examples of Healthcare Information Technology Difficulties" at this link: http://www.ischool.drexel.edu/faculty/ssilverstein/cases/.)

One component of the healthcare IT "ecosystem" many have been unable to see, which is perhaps even more carefully guarded than the program code and data structures, is the metadata on EMR use.

A remarkable development has now changed that metadata secrecy - a public civil lawsuit court docket.

Metadata is "data about data." In this context, that means data about who accessed the EMR, what they did, when they did it, from where they did it, etc. Perhaps it should be deliberately misspelled as "meatdata."

It allows the "legible gibberish" (see my Feb. 2011 post "Electronic Medical Records: Two Weeks, Two Reams" for more on that term) produced by the clinical side of EMR to be better weaved into meat, that is, a medical narrative that is essential to truly understanding a case.

I noted the unfortunate case of Samuel Sweet at the University of Pittsburgh Medical Center (UMPC), as reported by Sean Hamill in the Pittsburgh Post-Gazette:


Trial to begin in wrongful death claim
Monday, September 19, 2011
By Sean D. Hamill, Pittsburgh Post-Gazette

As far as Samuel Sweet was concerned, he only had a headache. It was a bad one, but nothing more, maybe something his chiropractor could fix with a little adjustment.

But three days after being admitted to UPMC Presbyterian for what his family was told was a treatable amount of bleeding on the brain, and six hours after his family saw him laughing and chatting about the Penguins' playoff chances, early in the morning of May 16, 2009, Mr. Sweet died unexpectedly.

Why he died is the subject of a civil case his family filed a few months later ... [Plaintiff's attorney] Ms. Maliver [actually Dr. Maliver, as she holds both the JD and MD degrees - ed.] said UPMC's timeline came into question in early August 2011, when UPMC finally turned over -- after two years of discovery [i.e, they turned them over at the last minute, a few weeks before trial was scheduled to begin - ed.] -- 1,200 pages of "results detail sheets" which show not only when something was written in Mr. Sweet's electronic chart, but who wrote it and how.

[The patient died when there was a delay in treatment due to marked difficulty in putting a breathing tube into his lungs (a difficult intubation) when he developed respiratory failure. The defendants possibly never expected someone to actually comb through the 1,200 pages of "results detail sheets" on such a short time frame, but, apparently, the plaintiff's attorney took on the challenge - ed.]


So, for example, Ms. Maliver alleges that the results detail sheets show that during the 21 minutes before Mr. Sweet was said to stop breathing, none of the information in his chart is straight from the computer monitors that would tell what his vital signs were during that period.

But the results detail sheets also show something more troubling, Ms. Maliver said.

She said she found evidence that three days after Mr. Sweet died, Dr. Richard Simmons, UPMC Presbyterian's head of quality assurance, tried to put a "Diff Intub" [difficult to intubate, due to anatomy - ed.] red-letter warning on Mr. Sweet's electronic medical record. That effort showed up on the results details sheets, according to Ms. Maliver.

Such a warning would tell ["alert" would be a more precise term - ed] anyone who opened the record that Mr. Sweet was difficult to intubate.
As a result of this newspaper story, the defendants filed a complaint with the judge, who ordered a six month delay in further proceedings. The complaint and decision is at this link (PDF).

In further investigating what I considered a remarkable story, I came across a public docket Dr. Maliver filed on behalf of her clients in the case, "PLAINTIFF'S MOTION AND SUPPORTING BRIEF TO AMEND COMPLAINT TO SEEK PUNITIVE DAMAGES".

As I mentioned previously, this is a remarkable development that has opened a window on metadata secrecy.

This is freely and publicly downloadable from the Pittsburgh Prothonotary Office Civil Docket site at this link, case #GD-09-019407 , document #40 of 09/02/2011. (I have also cached the document at this link: http://www.ischool.drexel.edu/faculty/ssilverstein/cases/lawsuits/complaint_punitive_damages_vol101400000177.pdf .)

As I mentioned in the aforementioned post, I found the hospital attorney's explanation of apparent tampering somewhat troubling:

Dr. Simmons wasn't trying to alter the record, [attorney for the defendants] Mr. Conti said; instead he was in Mr. Sweet's medical record as part of the "peer review" process, assessing what happened in Mr. Sweet's case.

As part of that, he was in the medical record three days after Mr. Sweet died trying to figure out how one would create a warning about a patient's difficult intubation [in effect, altering the record, at the very least through creation of a confusing audit trail - ed.], Mr. Conti said.

The public nature of the "PLAINTIFF'S MOTION AND SUPPORTING BRIEF TO AMEND COMPLAINT TO SEEK PUNITIVE DAMAGES" document makes it possible for the public to look at some of the actual metadata to see for themselves what might have occurred.

Again, this is remarkable and is the first time I am aware of when the public (and the academic Medical Informatics community, of which I am a part) gets to "peek behind the curtain" of an EMR's metadata.

Let's take a look.

I will summarize relevant part of the Motion and intersperse testimony and metadata from the actual record of Mr. Sweet (again, from a now-public court document).

The purpose of the Motion was to seek punitive damages:

A. SEEKING PUNITIVE DAMAGES

(1) This is a civil action for medical malpractice in which the Plaintiff alleges in essence that Samuel Sweet, a relatively healthy man of only 62 years of age, needlessly suffocated to death in the intensive care unit at UPMC after undergoing a routine cerebral angiogram when, the following day, physicians recklessly and prematurely pulled out his breathing tube and then could not get it back in when it became obvious Mr. Sweet would die without it.

(2) This case is listed for trial on September 19, 2011, and discovery has just concluded.

(3) In light of the evidence adduced in discovery, the Plaintiff seeks to amend the Complaint to re-characterize Defendant Murugan's and Defendant actions and inactions as willful, wanton, reckless and not merely negligent. The Plaintiff similarly seeks to amend the ad damnum clause against these defendants to include a request for punitive damages because of their shocking and reckless disregard for Mr. Sweet's welfare and their attempts to alter the appearance of the medical records, in full awareness of Mr. Sweet's brain death, so as to obscure what really happened.

It is the last part of count A.(3) I will address here, a quite serious charge involving medical record evidence spoliation, which is specifically forbidden in Pennsylvania by the Medical Care Availability and Reduction of Error (MCARE) Act of 2002 (PDF, see Section 511, "Preservation and accuracy of medical records", pg. 18-19) and other regulations.

Of importance, the Motion continues:

... (15) UPMC has a special warning system that is intended to serve the very purpose of alerting all medical providers of a patient with a difficult airway. The way it works [as UMPC defendants testified under oath - ed.] is the attending physician, writes up the problem list for the patient and need only put difficult airway in the list, and this will trigger a special yellow banner to pop up on the patient's computer files for all to see every time the chart is opened and every time any page is viewed.

Not only that, but then the words "difficult airway"appear in red text within the yellow banner, and this puts the viewers on notice to check the anesthesia record as to how intubation was done successfully in the past, so they can replicate the successful technique.

This patient was extubated after a procedure to check for brain bleeding, but by late at night it became obvious he could not breathe adequately on his own, and needed to be re-intubated.

Let's see how a chart appears with, and without the banner about a patient being difficult to intubate (due to their mouth and air-passage anatomy):


Real Electronic Medical Record screen of Mr. Sweet lacking warning banner, above; fictitious chart showing banner, below. [Why wasn't it the fictitious patient chart that was fiddled with? - ed.] Click to enlarge.


Such a warning apparently did not appear in Mr. Sweet's EMR chart, and that along with other failed communication (which can be read in the Motion) led to the re-intubation difficulties, and ultimately death. (I should note that it's possible the clinicians did flag the "difficult intubation" condition, but that the EHR lost the data through relational integrity problems, i.e., the information became "orphaned" from the patient's records, although still existing in the system somewhere.)

(27) ... not one person knew that there was a note from anesthesiology containing a road map for success, that included the use of a "Fast-Track LMA device", neither of which was ever brought in for Mr. Sweet that night when he needed the tube to be put back in.


Exhibit E. Under Oath. "A designation of difficult intubation automatically appears on a patient's banner bar if it is entered as a problem on the Problem List by the user selecting it from a drop-down menu list." (I tend to have doubts the problem list is that intelligent, but this is what was testified.) Click to enlarge.


Sworn testimony indicates nobody took the appropriate actions to enable the alert to appear on the EMR screens:


Admitted under oath. Nobody did what it would take to make a "difficult intubation" alert appear on Mr. Sweet's chart. Click to enlarge.

As a result of this missing data, the "syndrome of overconfidence in computers", and the toxic effect of poorly done health IT impairing clinician-clinician communications, physicians seeing this patient when he was under duress admit under oath they did not know of this intubation problem:


Dr. Kaura didn't know. Click to enlarge.


Dr. Sappington didn't know. Click to enlarge.

This is bad enough. The post-mortem chart fiddling issues I am addressing here begin with this:

C. (39) In the present case, after rounds of complex discovery battles, it became apparent that UPMC altered the records ... in this case, much of the record alteration was conducted by quality assurance officer, one Dr. Richard Simmons.

(40) Once the brain death of Mr. Sweet was known, a wave of record alteration and supplementation occurred, largely though not exclusively at the behest of Dr. Simmons ...

(41) For example, after Mr. Sweet was dead, when it could obviously not benefit his medical care, Dr. Simmons entered Mr. Sweet's computerized medical record, clearly looking into whether there had been a proper yellow-banner warning created through a problem list (which, of course, there was not).

Again, these are serious charges. Why would the plaintiff attorney raise these charges? Let's look at some metadata:


Exhibit K, showing quality assurance officer Dr. Simmons fiddling with Mr. Sweet's chart on May 19th several times during the day, as well as on the 22nd. Note circled entries. Note the gap (labeled) and the time of the last entry on the 19th, 15:23. Also note all these dates are post mortem by several days; death was on the 16th. Also note the times of entry, and the part of the chart accessed in the second round of accesses on May 19th - including "problem list" at 15:02. Click to enlarge.

I note that we are left to wonder what happened between access round two by the QA Officer on May 19 beginning 15:01 PM, and round three on May 22 at 14:03 PM. (Where are data for May 19th after 15:23 and May 20th and 21st, I wonder as well? This was not a weekend but midweek ...)

The Motion continues:

(42) Thereafter, even though Mr. Sweet was now long dead and such action could do him no good, Dr. Simmons tried to create a problem list that had originally been omitted by Defendant. He listed a difficult airway as the problem (even though obviously Mr. Sweet's problem list would have included many things, such as having undergone an angiogram and a minor cerebral bleed). In other words, Dr. Simmons tried to take the action necessary to make the computer show the yellow banner warning that was missing.

Here's more metadata seemingly supporting this statement. It's clear that nobody, including especially someone in Dr. Simmons' role should have been doing ANYTHING to the data that would or could raise suspicion of alterations via the metadata, such as times. Surely a presumably competent senior physician in a peer review role would have known this.

(I also note, shouldn't the record have been electronically "locked" by several days after death, thus causing any changes after the lock to appear in the normal "give us the legal medical record" outputs, not just in metadata?):


Exhibit L. Metadata showing Dr. Simmons on May 19th in the drop-down menu to make a problem list - then retracting it ("active --> cancelled") shortly afterwards. (I note the apparent cancellation time of 3:24 PM, i.e., 15:24, is just after the final May 19th entry of 15:23 on Exhibit K, when the several-day "gap" begins. I also note the patient died on May 16th. Curious... ) Click to enlarge.

But problems apparently occurred:

(43) It did not work. The yellow banner would not appear retroactively onto the otherwise completed record although he did succeed in altering the original record to look like there had always been a problem list. Further, during review of the "detail sheets," the Plaintiff discovered that Dr. Simmons, having failed to create a banner warning, tried to then delete or undo what he had attempted, but could not get it out of the computer tracking system. See Exhibit L hereof.

Let's look at the next part of Exhibit L:


Note the postmortem date of 5/19/2009 on this "problem list", and the attempted cancellation, presented as evidence. Note the time of the Problem list addition - 3:02 PM (i.e., 15:02 as in exhibit K above). Canceled as above at 3:24. Someone in Dr. Simmons' position should not have been fiddling with the problem list, knowing (or should have known, or should have made it his business to know) that footprints of fiddling in the metadata would, at the very least, raise eyebrows. Click to enlarge.

This does not look like the metadata that would be generated by peer review that I myself would perform ...

In summary, this unique Motion containing actual EMR metadata is, in my personal view, suspect for 1) imprudent post-death fiddling with the EMR records at best, and/or 2) attempts to alter the EMR to unjustly protect those who caused harm to come to this patient at worst.

I do not know which occurred, but hospital attorney Conti's excuse that "Dr. Simmons was in the medical record three days after Mr. Sweet died trying to figure out how one would create a warning about a patient's difficult intubation" [that is, entering new data not present before - ed.] could be either:

  • A sign of lack of computer and legal savvy of a senior clinician/UPMC Presbyterian's head of quality assurance, but whose intentions were pure, as explained above; or
  • The confabulations of an attorney caught with his pants down.

My personal opinion?

Want to buy a bridge in Brooklyn, members of the jury and Your Honor?


NY bridge for sale. Cheap.


The following also does not favorably influence my interpretation of the metadata:

(44) It is noteworthy that, prior to producing these results detail sheets that indicated such changes, UPMC attempted to file a motion for a protective order to bring all further discovery to a halt (a motion which was denied) even though the discovery deadline had not yet arrived.

Obviously, this is not for me to decide and will need to await court adjudication, but as a Medical Informatics specialist and someone with some investigative experience regarding computers and medicine, I am not happy with the looks of this.

I report, you decide.

There were other allegations in this plaintiff's Motion, again based on clinical IT metadata, regarding: unaccounted-for drugs of potential abuse (e.g., sedative propofol, the drug that killed Michael Jackson), the entry of fictitious data (such as vital signs, timing and medication administration by others including nurses), dictations coerced out of junior staff by senior personnel that might have been "spun" favorably to the medical center, etc., but those are the subject of later posts.

I again repeat the six-month delay in this case could potentially leave various problems with this EMR system unexposed and unremediated. This could unnecessarily expose the public to six more months of risk.

Addendum: if UPMC or the vendor take issue with posting of this material due to IP or other issues such as health IT gag clauses (which by the way are signed by hospital executives in violation of Joint Commission Safety Standards per my 2009 JAMA letter here and longer essay here), contact the Prothonotary Office in Pittsburgh, not me.

-- SS

Addendum:

What type of person was Mr. Sweet? This type:


Samuel E. Sweet Jr.
Cheswick

Samuel E. Sweet Jr., 62, of Cheswick, died Saturday, May 16, 2009, at UPMC Presbyterian Hospital. He was born Dec. 9, 1946, in New Kensington, son of the late Samuel E. Sweet Sr. and Marjorie (Secrist) Sweet. He was a resident of Cheswick for 33 years. He worked for the Army Corps of Engineers at Lock No. 2 of the Allegheny River and served in the Marine Corps during the Vietnam Era. He was a member of Hoboken Presbyterian Church, Blawnox Sportsmen Club, Blawnox "A" Club and the Springdale VFW. He enjoyed gardening and cutting grass. Survivors include his wife, Janet A. Sweet; sons, Samuel E. "Chip" (Michele) Sweet III, of Natrona, and William E. (Tracy) Sweet, of Edgewood; granddaughters, Kristin Ruff, of South Carolina, and Virginia Sweet, of Natrona; brother, John Thomas (Debbie) Sweet, of Warren; and nieces and nephews. Friends received from 2 to 6 p.m. Monday only, at the THOMAS M. SMITH FUNERAL HOME AND CREMATORY LTD., 930 Center Ave., Blawnox, followed by a funeral service at 7 p.m. in Hoboken Presbyterian Church, 921 North Ave., Blawnox, PA 15238. In lieu of flowers, the family respectfully suggests memorial contributions to Hoboken Presbyterian Church.
-- SS

Addendum:

This case was settled before going to trial for $1,375,000.

-- SS

Wednesday, July 06, 2011

Law firms as enablers of HIT experiments? Familiar law firm now regular reader of Healthare Renewal

It continues to amaze me that unregulated, unvetted healthcare information technology of unproven benefit and proven harm continues to spread like wildfire. This occurs even when people are killed, such as the infant deaths I outlined at this post being defended by obstructionist law firms.

This phenomenon has enablers. Among those, which include HIT vendors, their marketing arm HIMSS, large consultant companies, HIT pundits, the government, etc., law firms seem to have become enablers of hospitals' experiments with unproven, unqualified, unregulated healthcare information technology - in part by defending the medical mistakes that result.

Lawyers defending blatant IT-related errors impede correction of the defects and impaired "HIT ecosystem" that causes the problems. After all, they can simply tell a hospital a case is not defensible (and, for example, advise them to settle). Accepting cases is entirely voluntary.

For example, take the law firm of MARSHALL,DENNEHEY,WARNER,COLEMAN defending the hospital that caused my mother's IT-related year-long suffering starting May 2010, and then death exactly one month ago on June 6, 2011. They have become a regular reader of Healthcare Renewal, and I can believe it's not to help the hospital improve its HIT.

It's not as if lawyers are not writing on these issues, such as Case Western School of Law's Sharona Hoffman in "E-Health Hazards: Provider Liability and Electronic Health Record Systems". That work is a comprehensive analysis of the liability risks associated with use of clinical IT.


The real-world result of health IT interfering in simple care processes. Law firms that defend HIT-caused medical errors are enablers in use of these experimental technologies.

Perhaps they should have advised their clients of the risks of health IT before my mother was maimed? Or did they not know of these risks, something any law firm advising healthcare clients in 2010-2011 knew, should have known, or should have made it their business to know?

Some tracking examples among a larger set:

Today:

Domain Name (Unknown)
IP Address 12.104.41.# (MARSHALL,DENNEHEY,WARNER,COLEMAN)
ISP AT&T WorldNet Services
Location
Continent : North America
Country : United States (Facts)
Language English (U.S.)
en-us
Operating System Macintosh WinNT
Browser Safari 1.3
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.41 Safari/535.1
Javascript version 1.5
Monitor
Resolution : 1280 x 1024
Color Depth : 32 bits
Time of Visit Jul 6 2011 10:08:54 am
Last Page View Jul 6 2011 10:30:45 am
Visit Length 21 minutes 51 seconds
Page Views 5
Referring URL http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=there%27s%20also%20been%20a%20baby%20death%20locally%20to%20me%20that%20is%20allegedly%20due%20to%20HIT%20PACS%20interference%20in%20otherwise%20simple%20care
Search Engine google.com
Search Words there's also been a baby death locally to me that is allegedly due to hit pacs interference in otherwise simple care
Visit Entry Page http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html
Visit Exit Page http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html
Out Click
Time Zone UTC-5:00
Visitor's Time Jul 6 2011 10:08:54 am
Visit Number 902,836

Yesterday:

Domain Name (Unknown)
IP Address 12.104.41.# (MARSHALL,DENNEHEY,WARNER,COLEMAN)
ISP AT&T WorldNet Services
Location
Continent : North America
Country : United States (Facts)
Language English (U.S.)
en-us
Operating System Macintosh WinNT
Browser Safari 1.3
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.41 Safari/535.1
Javascript version 1.5
Monitor Resolution : 1280 x 1024
Color Depth : 32 bits
Time of Visit Jul 5 2011 9:07:13 am
Last Page View Jul 5 2011 9:08:46 am
Visit Length 1 minute 33 seconds
Page Views 4
Referring URL http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=health%20care%20renewal
Search Engine google.com
Search Words health care renewal
Visit Entry Page http://hcrenewal.blogspot.com/
Visit Exit Page http://hcrenewal.blogspot.com/2011/06/electronic-medication-prescribing-magic.html
Out Click
Time Zone UTC-5:00
Visitor's Time Jul 5 2011 9:07:13 am
Visit Number 902,285


and an older one:

Domain Name (Unknown)
IP Address 12.104.41.# (MARSHALL,DENNEHEY,WARNER,COLEMAN)
ISP AT&T WorldNet Services
Location Continent : North America
Country : United States (Facts)
Language English (U.S.)
en-us
Operating System Macintosh WinNT
Browser Safari 1.3
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.28 Safari/534.24
Javascript version 1.5
Monitor Resolution : 1280 x 1024
Color Depth : 32 bits
Time of Visit Apr 4 2011 12:12:05 pm
Last Page View Apr 4 2011 12:33:44 pm
Visit Length 21 minutes 39 seconds
Page Views 30
Referring URL
Visit Entry Page http://hcrenewal.blogspot.com/
Visit Exit Page http://hcrenewal.blogspot.com/2009/03/malpractices-of-multitudes-mission.html
Out Click
Time Zone UTC-5:00
Visitor's Time Apr 4 2011 12:12:05 pm
Visit Number 860,621

Note 30 page views in the latter data.

-- SS

Monday, June 27, 2011

Babies' deaths spotlight safety risks linked to computerized systems

A new tragic case. (A second, earlier case of infant death was posted in March 2011 here).

See Baby's death spotlights safety risks linked to computerized systems by Judith Graham and Cynthia Dizikes in the Chicago Tribune.

A baby died at Advocate Lutheran General Hospital due to an intravenous solution containing a massive overdose of sodium chloride — more than 60 times the amount ordered by the physician. The authors write:

Although a series of other errors contributed to the tragedy, its origin — a piece of data entered inaccurately into a computer program — throws a spotlight on safety risks associated with medicine's advance into the information age, a trend being pushed aggressively under health reform.

One wonders if any type of alert was generated, and if not, why not.

What are hospitals getting for their tens to hundreds of millions of dollars they are throwing at clinical IT?

Technology can be a great blessing in medicine. I am alive and healthy in 2011 thanks to it. The medical condition referred to in the aforementioned letter was in fact cured as a result of advances in cardiac electrophysiology science, as here and here, pgs. 1 and 2).

However, technology cannot be applied cavalierly, lawlessly (per attorney Sharona Hoffman), experimentally, without regulation, and without informed patient consent as is often done in the world of HIT.

-- SS

Also see another case at my aforementioned March 2011 post "Thanks to the wonders of EHR, this premature baby went to the grave, prematurely" at this link, from an Oct. 2010 story in Virginia Lawyers Weekly ("Failures in care alleged after premature birth - $1,000,000 Settlement"). A PICC line was also involved.

-- SS

Tuesday, June 07, 2011

My mother passed away

My mother, affected catastrophically by an EHR-related medical error last year, passed away yesterday evening.

In her memory, a photo of her and me from 1957 I found in her possessions.

Betty Silverstein, 1925-2011

Her children were always Number One.

May she rest in peace, and may my efforts result in others not having to suffer similar mistakes at the hands of IT.

-- SS

Nov. 2011 addendum:

Here is a memorial bench I had erected for my parents at their grave last month, near where they ran a small community pharmacy for almost four decades.
My father, a pharmacist, was a go-to source for health information in the once-bucolic community of Somerton, in far Northeast Philadelphia, long before chain drugstores appeared in the region.
The inscription atop the bench reads "Owners of Lumar Pharmacy. Served This Community 1954 -1991."

They, like I, also toiled to safeguard and improve the health of the public.

Click to enlarge

May they rest in peace.

-- SS

Friday, July 16, 2010

FDA MAUDE Database: Patient Outcome - Death

I present another health IT problem case from the FDA's voluntary MAUDE (Manufacturer and User Facility Device Experience) database below.

From FDA's description of MAUDE:

  • MAUDE data represents reports of adverse events involving medical devices. The data consists of voluntary reports since June 1993, user facility reports since 1991, distributor reports since 1993, and manufacturer reports since August 1996. MAUDE may not include reports made according to exemptions, variances, or alternative reporting requirements granted under 21 CFR 803.19.
  • The on-line search allows you to search CDRH database information on medical devices which may have malfunctioned or caused a death or serious injury. MAUDE is scheduled to be updated monthly and the search page reflects the date of the most recent update. FDA seeks to include all reports received prior to the update. However, the inclusion of some reports may be delayed by technical or clerical difficulties.
  • MAUDE data is not intended to be used either to evaluate rates of adverse events or to compare adverse event occurrence rates across devices. Please be aware that reports regarding device trade names may have been submitted under different manufacturer names. Searches only retrieve records that contain the search term(s) provided by the requester.

I somehow missed the following case when I wrote the Oct. 2009 post 'Our Policy Is To Always Have Unabashed Faith In The Computer ... Except When It Screws Up, And Then It's The Doctor's Fault' but I have added it there as well:

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfmaude/detail.cfm?mdrfoi__id=1656460
CERNER MILLENIUM POWERCHART CPOE
Event Date 11/19/2006
Event Type: Death
Patient Outcome: Death

The medication review screen of the subject device does not specify the exact dose in milligrams of combination medications. For example, narcotics are combined with tylenol in at least two strengths. Liquid narcotic tylenol-oxycodone combination is reported in ml, not mg. The exact dose of tylenol is not specified and requires knowledge of the combination medication dose in the volume specified.

Certain fields of the grid do not specify the volume, but rather state "date/time" requiring another click or pop up screen. The immediate knowledge of tylenol dosage in mg is directly related to understanding and preventing excessive doses. In the subject, 10 ml of acetaminophen-oxycodone is indicated as having been given 3 times over 4 hours. That means that 1950 mg of tylenol was administered in 4 hours while the patient was in a state of starvation and receiving other medication that increase the effects of tylenol.

This dose would equate to 11,700 mg of tylenol over 24 hours, nearly 3 times the maximum daily dose in otherwise health people. In the ensuing days, the patient developed acute renal failure, presumably acute tubular necrosis, and died. In the absence of other etiology, the excess tylenol was the culprit. This was not considered as etiology ante-mortem. The counterintuitive screen impaired the professionals. The pharmacist did not recognize and stop the medication, the nurses administered it, and the excessive dose, clinically meaninglessly listed as a volume of 10 ml -given 3 times in 4 hours- of acetaminophen-oxycodone, was missed by the physicians. Adverse events have been ascribed to "user error" by vendors.

The device offers a potent propensity to life endangering oversights. There are other screens on this device which present information that interfere with clinically useful visualization of data.
[Who designed these screens, I ask? Clinicians, or business IT personnel used to designing inventory systems for widget control? - ed.] The data does not flow to the professionals. It is not represented in a meaningfully useful manner.

The professionals need to hunt for it. As such, the user unfriendly screens [see this link on mission hostile HIT - ed.] impair safe medical care consistent with the impediment to expedient professional understanding of what, exactly, is the dose of medication and how much was administered to the patient. This sentinel case of death is directly attributed to user unfriendly screens on this device.

How many cases like this, as well as "near misses" related to health IT go unreported, nationwide and worldwide?

As in my paper "Remediating an Unintended Consequence of Healthcare IT: A Dearth of Data on Unintended Consequences of Healthcare IT",
nobody really knows; these devices are unregulated with no requirements for reporting.

However, let's roll it out nationally anyway, because HIT will deterministically "revolutionize" medicine. Just ignore those spoil-the-party, man-behind-the-curtain prattle from writers like these.

We can safely ignore all contrarian research and literature, of course, as we all know HIT will revolutionize medicine from the definitive certainty of HHS in "The 'Meaningful Use' Regulation for Electronic Health Records", NEJM, Blumenthal and Tavenner (10.1056/NEJMp1006114, July 13, 2010):

The widespread use of electronic health records (EHRs) in the United States is inevitable. EHRs will improve caregivers’ decisions and patients’ outcomes. Once patients experience the benefits of this technology, they will demand nothing less from their providers. Hundreds of thousands of physicians have already seen these benefits in their clinical practice.

[Except for those who
haven't - ed.]


And our government's called BP Energy Company cavalier?

I offer no additional comments.

-- SS