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

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

Saturday, March 31, 2012

An Expensive Healthcare Computing Mistake: $1.5 Million

At my June 2011 post "Babies' deaths spotlight safety risks linked to computerized systems" I reported on a case (case #2) of an infant death in part attributed to HIT (PACS) interference in otherwise simple care processes.

In "Allen-Blake vs. Abington Memorial Hospital", a critical x-ray of a PICC (peripherally inserted central catheter) line placement allegedly was never read due to misdating.

The Allen-Blake case was settled 2/29/12 for $1.5 million, according to the public docket count 78 (link):

2/29/2012OrderOF 2/28/12 OTT, J PROPOSED SETTLEMENT OF $1,500,000.00 APPROVED CC

That $1.5 million might have paid for a lot of other things, such as provision of better medical care through hiring/retention of more staff. The legal fees for defense incurred must also have been substantial, representing yet more precious healthcare capital down the proverbial drain.

Add cases like this to the "total cost of ownership" of health IT.

-- 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