Laman

Tampilkan postingan dengan label healthcare IT anecdote. Tampilkan semua postingan
Tampilkan postingan dengan label healthcare IT anecdote. Tampilkan semua postingan

Kamis, 10 Oktober 2013

Drudge Report, Oct. 10, 2013, 9 AM EST: All that needs to be said about government, computing and healthcare

Per Drudge Report. Oct. 10, 2013, 9 AM EST:

From the same people who brought us HITECH, the stimulus bill for rapid rollout of commercial electronic medical records, order entry, results reporting and other components of enterprise clinical "command and control" software for hospitals through which every transaction of care must pass.

More IT malpractice.  The Drudge links, as they appear on the page:

Obamacare website cost more than FACEBOOK, TWITTER, LINKEDIN, INSTAGRAM...
'How can we tax people for not buying a product from a website that doesn't work?'
Major insurers, Dem allies repeatedly warned Obama admin...
REPORT: WH knew site might not be ready...
POLL: Just 1 in 10 report success...
DNC head says site designed for 50,000 max...
Once you get in, you can't get out...
Crazzzzzzzy code...
'It looks like nobody tested it'...
WASHPOST: Not code, but 'outdated, costly, buggy technology'...
CARNEY: 'I Don’t Know' If Obama Has Tried Website...
Hawaii forced to relaunch after zero sign-ups...


I won't comment any further; I don't think I need to.


Drudge Report, Oct. 10, 2013, 9 AM EST.  Click to enlarge.


Of course, the Anecdotalists [1] and Denialists [2] will probably say this is all a "glitch" and that things will be great in ver. 2.0.

Fools all.

Oh, and the cost, via Drudge, per the linked story.  A mere:



-- SS

[1]  See "Health IT: On Anecdotalism and Totalitarianism" at  http://hcrenewal.blogspot.com/2010/09/health-it-on-anecdotalism-and.html)

[2]  See "The Denialists' Deck of Cards: An Illustrated Taxonomy of Rhetoric Used to Frustrate Consumer Protection Efforts" by Chris Jay Hoofnagle, available at http://papers.ssrn.com/sol3/papers.cfm?abstract_id=962462)

Oct. 10, 2013 addendum:

Also see "Analysis: IT experts question architecture of Obamacare website" at http://uk.reuters.com/article/2013/10/05/us-usa-healthcare-technology-analysis-idUKBRE99407T20131005.  If the allegations here are even partially true, every programmer and manager who ever worked on this system should be summarily fired and never permitted to touch another computer involved in healthcare - ever.

-- SS

Sabtu, 09 Februari 2013

A New ECRI Institute Study On Health Information Technology-Related Events

As I wrote here, I was a reviewer of the report in the PA-based, ECRI Institute-conducted study "The Role of the Electronic Health Record in Patient Safety Events."  ECRI studied the Pennsylvania Patient Safety Reporting System database for HIT-related errors.   

The ECRI Institute is an independent organization renowned for its safety testing of medical technologies and reporting on same, and that "researches the best approaches to improving the safety, quality, and cost-effectiveness of patient care."  I've mentioned it and its bylaws in this blog in the past as a model for independent, unbiased testing and reporting of healthcare technologies.

The full report in PDF is at this link.  In the report, the Pennsylvania Patient Safety Authority analyzed reports of EHR-related events from a state database (the Pennsylvania Patient Safety Reporting System or PA-PSRS, pronounced "PAY-sirs") of reported medical errors and identified several major themes.

My review input led to a discrete "limitations" section.  Also, my invited July 2012 presentation to the PA Patient Safety Authority "Asking the Right Questions: Using Known HIT Safety Issues to Improve Risk Reporting and Analysis" with ECRI in attendance (link to PPT here) on the danger of limited datasets due to systematic impediments to information diffusion was apparently taken seriously. 

ECRI decided to do something about the knowledge gap, and they asked the right questions.

They've just released this summary of a new study they conducted.  I have a few comments which follow:
  
ECRI Institute PSO Uncovers Health Information Technology-Related Events in Deep Dive Analysis

Data transfer, data entry, system configurations, and more identified as serious problem areas
 
PLYMOUTH MEETING, Pa., Feb. 6, 2013 /PRNewswire-USNewswire/ -- The federal government is spending about $19 billion to encourage hospitals, physician practices, and other healthcare organizations to invest in their health information technology (HIT) infrastructure with the goal of improving patient safety and quality through the Health Information Technology for Economic and Clinical Health (HITECH) Act.

Concerned about the unintended consequences of HIT and the potential for errors to cause patient harm, ECRI Institute Patient Safety Organization (PSO) recently conducted a PSO Deep Dive™ analysis on HIT-related safety events. Their just-released 48-page report identified five potential problem areas, which can be assessed with the accompanying toolkit. The report and toolkit are available for purchase [appx. $350 U.S. - ed.] without membership in ECRI Institute PSO.

"Minimizing the unintended consequences of HIT systems and maximizing the potential of HIT to improve patient safety should be an ongoing focus of every healthcare organization," says Karen P. Zimmer , MD, MPH, FAAP, medical director, ECRI Institute PSO.


Based on [voluntary - ed.] reports submitted to the PSO from participating organizations, ECRI Institute PSO experts identified the following key HIT-related problems:

  • inadequate data transfer from one HIT system to another
  • data entry in the wrong patient record
  • incorrect data entry in the patient record
  • failure of the HIT system to function as intended
  • configuration of the system in a way that can lead to mistakes
To collect enough reports for meaningful evaluation, ECRI Institute PSO asked participating organizations to submit standardized data about HIT events during a nine-week period. This enabled ECRI Institute PSO to identify patterns and trends from the aggregated data and share the findings, as well as its recommendations. The data in the PSO Deep Dive represents only that collected using the Agency for Healthcare Research and Quality (AHRQ) HIT Common Formats.  [Not the improved formats developed by AHRQ in their IT Hazards Manager project, still in development - ed.]  ECRI Institute PSO data encompasses over 800 HIT-related events.

According to the report, HIT must be considered in the context of the environment in which it operates during the three phases of any HIT project: planning for new or replacement systems, system implementation, and ongoing use and evaluation of the system. "Shortsighted approaches to HIT can lead to adverse consequences," caution the authors.

"Healthcare organizations should consider the findings and recommendations in the PSO Deep Dive as part of their effort to achieve those goals," adds Zimmer.

The HIT PSO Deep Dive findings were published in a 48-page report and toolkit with self-assessment questionnaire and action plan form available to all ECRI Institute PSO Members and its partner PSO members. The table of contents of the report is available for free viewing/download. Additional information will be presented in ECRI Institute PSO's Monthly Brief free e-newsletter March edition; go to www.ecri.org/psobrief to sign up. The full report and toolkit are also available for purchase.

For questions about this topic, or for information about purchasing the report, please contact ECRI Institute PSO by telephone at (610) 825-6000, ext. 5558; by e-mail at pso@ecri.org; by fax at (610) 834-1275, or by mail at 5200 Butler Pike, Plymouth Meeting, PA 19462-1298, USA.

From the free linked TOC document:

Key Recommendations
  • Enlist leaders’ commitment and support for the organization’s health IT projects.
  • Involve health IT users in system planning, design, and selection.
  • Conduct a review of workflow and processes to determine how they must be modified.
  • Evaluate the ability of existing IT systems within the organization to reliably exchange data with any health IT system under consideration.
  • Conduct extensive tests before full implementation to ensure that the health IT system operates as expected.
  • Provide user training and ongoing support; educate users about the capabilities and limitations of the system.
  • Closely monitor the system’s ease of use and promptly address problems encountered by users.
  • Introduce alterations to a health IT system in a controlled manner.
  • Monitor the system’s effectiveness with metrics established by the organization.
  • Require reporting of health IT-related events and near misses.
  • Conduct thorough event analysis and investigation to identify corrective measures.

My comments are these:

  • The ECRI study, report and recommendations are quite welcome.
  • The case reports received were apparently voluntary and probably "conservative" and understated as hospitals are not happy to release data on problems and harms that can lead to, or support, litigation.  
  • The study was just 9 weeks long, and with a limited set of healthcare organizations participating.  800 HIT-related events were identified. 
  •  The relevant issues discovered in the events, as summarized in the bullet points above, are capable of causing clinician distraction, incorrect decisions, "use error" (as opposed to "user error", see here), patient harm, and death.  (I am aware of such issues in the press including harms and deaths, as readers here have read at links such as these and these and these and these, and others about which I am providing expert-witness consultation and cannot share.)
  • I believe ECRI has now begun to peer below the water level, through the muck of industry control of the narrative, of what FDA CDRH leader Jeffrey Shuren MD JD referred to as "the tip of the iceberg" - i.e., the current level of knowledge of health IT difficulties, defects and harms. 
  • The report is yet another red flag for a far more robust (and mandatory, in my view) post-marketing surveillance of health IT.  
  • Those who claim these findings are "anecdotes" (as here) are looking increasingly foolish and cavalier.

Finally, readers of this blog have been reading about these issues for years.  You heard it here first.

-- SS 
 

Kamis, 09 Februari 2012

A Critical Review of a Critical Review of e-Prescribing ... Or Is It CPOE?

In PLoS medicine, the following article was recently published by researchers at the University of New South Wales in Australia:

Westbrook JI, Reckmann M, Li L, Runciman WB, Burke R, et al. (2012) Effects of Two Commercial Electronic Prescribing Systems on Prescribing Error Rates in Hospital In-Patients: A Before and After Study. PLoS Med 9(1): e1001164. doi:10.1371/journal.pmed.1001164


The section I find most interesting is this:

We conducted a before and after study involving medication chart audit of 3,291 admissions (1,923 at baseline and 1,368 post e-prescribing system) at two Australian teaching hospitals. In Hospital A, the Cerner Millennium e-prescribing system was implemented on one ward, and three wards, which did not receive the e-prescribing system, acted as controls. In Hospital B, the iSoft MedChart system was implemented on two wards and we compared before and after error rates. Procedural (e.g., unclear and incomplete prescribing orders) and clinical (e.g., wrong dose, wrong drug) errors were identified. Prescribing error rates per admission and per 100 patient days; rates of serious errors (5-point severity scale, those ≥3 were categorised as serious) by hospital and study period; and rates and categories of postintervention “system-related” errors (where system functionality or design contributed to the error) were calculated.

Here is my major issue:

Unless I am misreading, this research took place in hospitals (i.e., "wards" in hospitals) and does not seem to focus (if even refer to) discharge prescriptions.

I think it would be reasonable to say that what are referred to as "e-Prescribing" systems are systems used at discharge, or in outpatient clinic/offices to communicate with a pharmacy selling commercially and not involved in inpatient care.

From the U.S. Centers for Medicare and Medicaid Services (CMS), for example:

E-Prescribing - a prescriber's ability to electronically send an accurate, error-free and understandable prescription [theoretically, that is - ed.] directly to a pharmacy from the point-of-care

I therefore think the terminology used in the article as to the type of system studied is not well chosen. I believe it could mislead readers not experienced with the various 'species' of health IT.

This study appears to be of an inpatient Computerized Practitioner Order Entry (CPOE) system, not e-Prescribing.

Terminology matters. For example, in the U.S. the HHS term "certification" is misleading purchasers about the quality, safety and efficacy of health IT. HIT certification as it exists today (granted via ONC-Authorized Testing and Certification Bodies) is merely a features-and-functionality "certification of presence." It is not like an Underwriter Labs (UL) safety certification of an electrical appliance that the appliance will not electrocute you.

(This is not to mention the irony that one major aspect of Medical Informatics research is to remove ambiguity from medical terminology, e.g., via the decades-old Unified Medical Language System project or UMLS. However, as I've often written, the HIT domain lacks the rigor of medical science itself.)

I note that if this were a grant proposal for studying e-Prescribing, I would return it with a low ranking and a reviewer comment that the study proposed is actually of CPOE.

That said, looking at the nature of this study:

The conclusion of this paper was as follows. I am omitting some of the actual numbers such as confidence intervals for clarity; see the full article available freely at above link for that data:

Use of an e-prescribing system was associated with a statistically significant reduction in error rates in all three intervention wards. The use of the system resulted in a decline in errors at Hospital A from 6.25 per admission to 2.12 and at Hospital B from 3.62 to 1.46. This decrease was driven by a large reduction in unclear, illegal, and incomplete orders. The Hospital A control wards experienced no significant change. There was limited change in clinical error rates, but serious errors decreased by 44% across the intervention wards compared to the control wards.

Both hospitals experienced system-related errors (0.73 and 0.51 per admission), which accounted for 35% of postsystem errors in the intervention wards; each system was associated with different types of system-related errors.

I note that "system related errors" were defined as errors "where system functionality or design contributed to the error." In other words, these were unintended adverse events as a result of the technology itself.

The authors conclude:

Implementation of these commercial e-prescribing systems resulted in statistically significant reductions in prescribing error rates. Reductions in clinical errors were limited in the absence of substantial decision support, but a statistically significant decline in serious errors was observed.

The authors do acknowledge some limitations of their (CPOE) study:

Limitations included a lack of control wards at Hospital B and an inability to randomize wards to the intervention.

Thus, this was mainly a pre-post observational study, certainly not a randomized controlled clinical trial.

Not apparently accounted for, either, were potential confounding variables related to the CPOE implementation process (as in this comment thread).

In that thread I wrote to a commenter [a heckler, actually, apparently an employee of HIT company Meditech] with a stated absolute faith in pre-post studies that:

... A common scenario in HIT implementation is to first do a process improvement analysis to improve processes prior to IT implementation, on the simple calculus that "bad processes will only run faster under automation." There are many other changes that occur pre- and during implementation, such as training, raising the awareness of medical errors, hiring of new support staff, etc.

There can easily be scenarios (I've seen them) where poorly done HIT's distracting effects on clinicians is moderated to some extent by process and other improvements. Such factors need to be analyzed quite carefully, datasets and endpoints developed, and data carefully collected; the study design and preparation needs to occur before the study even begins. Larger sample sizes will not eliminate the possible confounding effects of these factors and many more not listed here.

The belief that simple A/B pre-post test that look at error rate comparisons are adequate is seductive, but it is wrong.

Stated simply, in pre-post trials the results may be affected by changes that occur other than the intervention. HIT implementation does not involve just putting computers on desks, as I point out above.

In other words, the study was essentially anecdotal.

The lack of RCT's in health IT are, in general, one violation of traditional medical research methodologies for studying medical devices. That issue is not limited to this article, of course.

Next, on ethics:

CPOE has already been demonstrated in situ to create all sorts of new potential complications, such in at Koppel et al.'s "Role of Computerized Physician Order Entry Systems in Facilitating Medication Errors", JAMA. 2005;293(10):1197-1203. doi: 10.1001/jama.293.10.1197 that concluded:

In this study, we found that a leading CPOE system often facilitated medication error risks, with many reported to occur frequently. As CPOE systems are implemented, clinicians and hospitals must attend to errors that these systems cause in addition to errors that they prevent.

CPOE technology, at best, should be considered experimental in 2012.

In regards to e-Prescribing proper, there's this: Errors Occur in 12% of Electronic Drug Prescriptions, Matching Handwritten and this: Upgrading e-prescribing system can bump up error risk to consider; in other words, the literature is conflicting, confirming the technology remains experimental.

This current study confirmed some (CPOE) errors that would not have occurred with paper did occur with cybernetics, amounting to "35% of postsystem errors in the intervention wards."

In other words, patient Jones was now subjected to a cybernetic error that would not have occurred with paper, in the hopes that patients Smith and Silverstein would be spared errors that might have occurred without cybernetic aid.

Even though the authors observe that "human research ethics approval was received from both hospitals and the University of Sydney", since patient Jones did not provide informed consent to the experimentation with what really are experimental medical devices as I've written often on this blog [see note 1], I'm not certain the full set of ethical issues have been well-addressed. It's not limited to this occasion, however. This phenomenon represents a pervasive, continual world-wide oversight with regard to clinical IT.

Furthermore, and finally: of considerable concern is another common limitation of all health IT studies, which I believe is often willful.

What really should be studied before justifications are given to spend tens of millions of dollars/Euros/whatever on CPOE or other clinical IT is this:

The impact of possible non-cybernetic interventions (e.g., additional humans and processes) to improve "medication ordering" (either CPOE, or ePrescribing) that might be FAR LESS EXPENSIVE, and that might have far less IT-caused unintended adverse consequences, than cybernetic "solutions."

Instead, pre-post studies are used to justify expenditures of millions (locally) and tens or hundreds of billions (nationally), with results sometimes like this affecting an entire country.

There is something very wrong with this, both scientifically and ethically.

-- SS

Note:

[1] If these devices are not experimental, why are so many studying them to see if they actually work, to see if they pose unknown dangers, and to try to understand the conflicting results in the literature? More at this query link: http://hcrenewal.blogspot.com/search/label/Healthcare%20IT%20experiment


Addendum Feb. 10, 2012:

An anonymous commenter points out an interesting issue. They wrote:

The study was flawed due to its failure to consider delays in care and medication administration as an error caused by these experimental devices.

Delays are widespread with CPOE devices. One emergency room resorted to paper file cards and vacuum tubes to communicate urgency with the pharmacy. Delays were for hours.

I agree that lack of consideration of a temporal component, i.e., delays due to technology issues, is potentially significant.

I, for example, remember a more than five-minute delay in getting sublingual nitroglycerin to a relative with apparent chest pain due to IT-related causes. The problem turned out to be gastrointestinal, not cardiac; however, in another patient, the hospital might not be so lucky.

Addendum Feb. 12, 2012:

A key issue in technology evaluation studies is to separate the effects of the technology intervention from other, potentially confounding variables which always exist in a complex sociotechnical system, especially in a domain such as medicine. This seems uncommonly done in HIT evaluation studies. Not doing so will likely inflate the apparent contribution of the technology.

A "control ward" where the same education and training, process re-engineering, procedural improvements, etc. were performed as compared to the "intervention ward" (but without actual IT use) would probably be better suited to pre-post studies such as this.

A "comparison ward" where human interventions were implemented, as opposed to cybernetic, would be a mechanism to determine how efficacious and cost-effective the IT was compared to less expensive non-cybernetic alternatives.

-- SS

Rabu, 04 Januari 2012

Just Say "No" to the Term "Anecdotes"; and HIT as a Medical Metadevice

A New Year's thought: there needs to be a push in healthcare for dropping of the word "anecdote" to describe case reports of health IT-related errors.

This word even appears in the late 2011 IOM report on HIT safety (PDF), e.g., the preface:


... We found that specific types of health IT can improve patient safety under the right conditions, but those conditions cannot be replicated easily and require continual effort to achieve. We tried to balance the findings in the literature with anecdotes from the field but came to the realization that the information needed for an objective analysis and assessment of the safety of health IT and its use was not available.


The "A" word needs to be dropped from the healthcare IT lexicon, since such reports from reliable sources are in fact incident reports purposed for risk management activities.

Incident reports do not need peer review for consideration for that purpose.

Of note, I do not believe the incident reports filed in hospitals when something awry occurs are labelled "anecdotes", either.

See the Aug. 2011 post "From a Senior Clinician Down Under: Anecdotes and Medicine, We are Actually Talking About Two Different Things" for more on this topic.

And on another vein, the issue of HIT being a medical device:

As the good State Rep. Marino of my home state of Pennsylvania and others oddly proffer - that 'certification' of health IT, having nothing to do with safety or usability, relieves HIT from being a device [1] - and as the IOM itself debates exactly what to call HIT and under what guidelines to regulate it, another term/category for HIT devices is needed.

In the spirit of the naming of the UMLS Metathesaurus, and in consideration of HIT's informational governance/orchestration of other medical devices and personnel (including the 'carbon units' known as clinicians and patients) -- I suggest the term "metadevice" for HIT.

Healthcare metadevices need their own specific regulation, apart from traditional medical devices.

-- SS

Note:

[1] As in line 21- 24 on page 6 of the "Safeguarding Access For Every Medicare Patient Act" Bill (PDF) that I wrote about here. The Bill states: "CLARIFICATION OF AUTHORITY. Certified EHR’s shall not be considered a device for purposes of the Federal Food, Drug, and Cosmetic Act."

(This proposal, of course, raises the question of whether Rep. Marino believes non-certified HIT shall be considered a medical device, a topic for another time.)