healthy4u: healthcare IT regulation

Hypocrisy at the FDA: Let's regulate E-cigarettes ... E-medical records, E-medical ordering and related Bad Health IT? They get a gentleman's pass.

Bad health IT is defined at my Medical Informatics academic site (<a href="http://cci.drexel.edu/faculty/ssilverstein/cases/">http://cci.drexel.edu/faculty/ssilverstein/cases/</a>) as follows: <blockquote class="tr_bq">Bad Health IT ("BHIT") is health IT that is ill-suited to purpose, hard to use, unreliable, loses data or provides incorrect data, is difficult and/or prohibitively expensive to customize to the needs of different medical specialists and subspecialists, causes cognitive overload, slows rather than facilitates users, lacks appropriate alerts, creates the need for hypervigilance (i.e., towards avoiding IT-related mishaps) that increases stress, is lacking in security, compromises patient privacy or otherwise demonstrates suboptimal design and/or implementation. </blockquote> Health IT is unregulated, and Bad Health IT results in patient injuries and deaths.   This is unarguable from the data cited in this post and related posts I've linked to.  The levels of harm are unknown. At my April 9, 2014 post "FDA on health IT risk:  "We don't know the magnitude of the risk, and what we do know is the tip of the iceberg, but health IT is of 'sufficiently low risk' that we don't need to regulate it" (<a href="http://hcrenewal.blogspot.com/2014/04/fda-on-health-it-risk-reckless-or.html">http://hcrenewal.blogspot.com/2014/04/fda-on-health-it-risk-reckless-or.html</a>) I observed how the FDA bent over backwards to avoid regulating Electronic Medical Records systems and other healthcare IT systems: To recap that post: Out of one side of their mouth FDA wrote this: <blockquote class="tr_bq">... products with health management heath IT functions, includes software for health information and data management, medication management, provider order entry, knowledge management, electronic access to clinical results and most clinical decision support software. Products with health management health IT functions are of sufficiently low risk and thus, [even] if they meet the statutory definition of a medical device, FDA does not intend to focus its oversight on them.</blockquote> While out of the side of their mouth that was not intended for public viewing, discovered by investigative reporter Fred Schulte, they wrote this: <div style="margin-left: 40px;">...In summary, the results of this data review suggest significant clinical implications and public safety issues surrounding Health Information Technology. The most commonly reported H-IT safety issues included wrong patient/wrong data, medication administration issues, clinical data loss/miscalculation, and unforeseen software design issues; all of which have varying impact on the patient’s clinical care and outcome, which included 6 death and 43 injuries. The absence of mandatory reporting enforcement of H-IT safety issues limits the number of relevant MDRs [device reports] and impedes a more comprehensive understanding of the actual problems and implications.   </div>FDA is thus claiming "we know what we non-publicly concluded it is not possible to know, and Health IT is not worth regulating ... even in face of dangers we do know" (e.g., see the alarming ECRI Institute data at <a href="http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html">http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html</a>). Note that everyone who needs medical care (which is. essentially, everyone) is increasingly exposed to these electronic products with health management heath IT functions, against their will and without any informed consent processes.  The only people exposed to E-cigarettes are those who willingly buy and consume them. With E-cigarettes, however:  <blockquote class="tr_bq">CBS/AP  April 24, 2014  FDA: Ban sales of electronic cigarettes to minors  <a href="http://www.cbsnews.com/news/fda-ban-sales-of-electronic-cigarettes-to-minors/">http://www.cbsnews.com/news/fda-ban-sales-of-electronic-cigarettes-to-minors/</a> WASHINGTON -- The federal government wants to ban sales of electronic cigarettes to minors and require health warning labels and approval for new products under regulations being proposed by the Food and Drug Administration. </blockquote> Wonderful.  How thoughtful.  (E-cigarettes are plastic or metal tubes, usually the size of a cigarette, that heat a liquid nicotine solution instead of burning tobacco. That creates vapor that users inhale.) <blockquote class="tr_bq"> While the proposal being issued Thursday won't immediately mean changes for the popular devices, the move is aimed at eventually taming the fast-growing e-cigarette industry. The agency said the proposal sets a foundation for regulating the products but the rules don't immediately ban the wide array of flavors of e-cigarettes, curb marketing in places like TV or set product standards. Any further rules "will have to be grounded in our growing body of knowledge and understanding about the use of e-cigarettes and their potential health risks or public health benefits," Commissioner Dr. Margaret Hamburg said.</blockquote><div dir="LTR" id="article-entry"> (Perhaps the E-cigarette industry hasn't figured out who to pay off yet?) <blockquote class="tr_bq">... "By being able to regulate e-cigarettes, we'll get a lot more information about what's in them, how they're made and we're already studying e-cigarettes in terms of how they're being used and what are their implications for health," Hamburg told CBS News. "At the present time, when we can't regulate cigarettes, it's like they wild, wild West" she said. "Companies can do anything they want. They can market in ways that they want. ... Unless they make a therapeutic claim that it is a product for actual cessation of nicotine use, we can't regulate them. If they make a therapeutic claim, we can regulate them as a medical product."</blockquote> The "Wild, wild west" is a perfect descriptor of the health IT market.  And claims of benefits?  How about some 'Words that Work?'  (<a href="http://hcrenewal.blogspot.com/2013/10/words-that-work-singing-only-positive.html">http://hcrenewal.blogspot.com/2013/10/words-that-work-singing-only-positive.html</a>) <blockquote>Hamburg stressed to CBS News that, "Until we have the authority to regulate e-cigarettes, we cannot provide the information that the American public wants about the relative risk and safety of these products. ... We cannot put in place certain restrictions that might be appropriate with respect to how the products are made, the kind of flavorings, the kind of marketing, etc. So we see this as really a crucial first step."</blockquote> The health IT industry has special accommodations in that regard that the E-cigarette company lawyers need to closely examine. <blockquote class="tr_bq">Smokers like e-cigarettes because the nicotine-infused vapor looks like smoke but doesn't contain the thousands of chemicals, tar or odor of regular cigarettes. Some smokers use e-cigarettes as a way to quit smoking tobacco, or to cut down. However, there's not much scientific evidence showing e-cigarettes help smokers quit or smoke less, and it's unclear how safe they are.</blockquote> It's undeniably unclear how safe clinical IT devices are, either.  The ECRI Institute, for instance, found 171 mishaps in 9 weeks at 36 hospitals voluntarily reported, leaving 8 patients harmed and possibly three of them dead.   (A likely far more than serous problem than GM cars with defective ignitions that killed ~13 in a decade...)   The FDA found many injuries and several deaths in their own self-admitted limited dataset as well.  (See FDA Internal Memo on HIT risk at <a href="http://hcrenewal.blogspot.com/2010/08/smoking-gun-internal-fda-memorandum-of.html">http://hcrenewal.blogspot.com/2010/08/smoking-gun-internal-fda-memorandum-of.html</a>). <blockquote class="tr_bq">... Companies also will be required to submit applications for premarket review within two years. As long as an e-cigarette maker has submitted the application, the FDA said it will allow the products to stay on the market while they are being reviewed. That would mean companies would have to submit an application for all e-cigarettes now being sold.</blockquote></div><div style="margin-bottom: 0in;"> </div><div style="margin-bottom: 0in;">There is no premarket review of clinical IT of the types categorized by FDA as "with health management heath IT functions" as above, even if those devices meet the statutory requirements as a medical device that falls under the Food, Drug & Cosmetic Act.  These systems increasingly mediate and regulate every transaction of healthcare.</div><div style="margin-bottom: 0in;"> </div><div style="margin-bottom: 0in;">E-cigarettes, however, are a major concern that are being reviewed in earnest?</div><div style="margin-bottom: 0in;"> </div><div style="margin-bottom: 0in;">Unbelievable.</div><div style="margin-bottom: 0in;"> </div><div style="margin-bottom: 0in;">-- SS DISCLAIMER:  I neither use tobacco products in any form nor E-cigarettes, never did, and have no conflicts of interest of any kind with either the tobacco or E-cigarette industries.</div>

Hypocrisy at the FDA: Let's regulate E-cigarettes ... E-medical records, E-medical ordering and related Bad Health IT? They get a gentleman's pass.

Bad health IT is defined at my Medical Informatics academic site (http://cci.drexel.edu/faculty/ssilverstein/cases/) as follows:Bad Health IT ("BHIT") is health IT that is ill-suited to purpose, hard …

Đọc thêm »

25 Apr 2014

FDA on health IT risk: reckless, or another GM-like political coverup? "We don't know the magnitude of the risk, and what we do know is the tip of the iceberg, but health IT is of 'sufficiently low risk' that we don't need to regulate it."

In my Sept. 16, 2013 post "An Open Letter to David Bates, MD, Chair, ONC FDASIA Health IT Policy Committee on Recommendations Against Premarket Testing and Validation of Health IT" (<a href="http://hcrenewal.blogspot.com/2013/09/an-open-letter-to-david-bates-md-chair.html">http://hcrenewal.blogspot.com/2013/09/an-open-letter-to-david-bates-md-chair.html</a>) I wrote: <blockquote class="tr_bq">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. </blockquote> The resultant April 2014 report is out: "FDASIA Health IT Report: Proposed Strategy and Recommendations for a Risk-Based Framework."  It is available at <a href="http://www.healthit.gov/sites/default/files/fdasiahealthitreport_final.pdf">http://www.healthit.gov/sites/default/files/fdasiahealthitreport_final.pdf</a>. The report is an academic idealist's and industry's dream.  It is a patient's nightmare. Instead of regulation, the report recommends the creation of a nebulous "Health IT Safety Center" (pgs. 16 and 25) as a "public-private entity with broad stakeholder engagement, that includes a governance structure for the creation of a sustainable, integrated health IT learning system that avoids regulatory duplication and leverages and complements existing and ongoing efforts."  In other words, a toothless organization without true regulatory authority. The recommendations of the Health IT Policy Committee have apparently been taken seriously by FDA.  This FDA announcement recently appeared (FDA is part of HHS): <blockquote class="tr_bq"><a href="http://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm390988.htm">http://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm390988.htm</a> HHS News Release For Immediate Release: April 3, 2014 Proposed health IT strategy aims to promote innovation, protect patients, and avoid regulatory duplication HHS today released a draft report that includes a proposed strategy and recommendations for a health information technology (health IT) framework, which promotes product innovation while maintaining appropriate patient protections and avoiding regulatory duplication. The congressionally mandated report was developed in consultation with health IT experts and consumer representatives and proposes to clarify oversight of health IT products based on a product’s function and the potential risk to patients who use it. ... As proposed in the draft report, posted on the ONC, FDA and FCC websites, there would be three health IT categories, based on function and level of risk, that focus on what the product does, not on the platform on which it operates (mobile medical device, PC, or cloud-based, for example). The first category, products with administrative health IT functions, poses little or no risk to patient safety and as such requires no additional oversight. They include software for billing and claims processing, scheduling, and practice and inventory management. The second category, products with health management heath IT functions, includes software for health information and data management, medication management, provider order entry, knowledge management, electronic access to clinical results and most clinical decision support software. Products with health management health IT functions are of sufficiently low risk and thus, if they meet the statutory definition of a medical device, FDA does not intend to focus its oversight on them. Instead, the draft report proposes relying primarily on ONC-coordinated activities and private sector capabilities that highlight quality management principles, industry standards and best practices.</blockquote> The characterization of these admitted medical devices as "sufficiently low risk" is in my opinion grossly negligent (if not criminal). For instance, GM concealed an ignition flaw that resulted in 13 deaths.  Look what's happening now in that sector.  Revelations of corporate wrongdoing and Congressional investigations: <blockquote class="tr_bq"><a href="http://www.nytimes.com/2014/03/31/business/us-regulators-declined-full-inquiry-into-gm-ignition-flaws-memo-shows.html">http://www.nytimes.com/2014/03/31/business/us-regulators-declined-full-inquiry-into-gm-ignition-flaws-memo-shows.html</a> U.S. Agency Knew About G.M. Flaw but Did Not Act By MATTHEW L. WALD MARCH 30, 2014 Federal regulators decided not to open an inquiry on the ignitions of Chevrolet Cobalts and other cars even after their own investigators reported in 2007 that they knew of four fatal crashes, 29 complaints and 14 other reports that showed the problem disabled air bags, according to a memo released by a House subcommittee on Sunday. Then in 2010, the safety agency came to the same decision after receiving more reports that air bags were not deploying. The memo also revealed that General Motors approved the faulty design of the switch in 2002 even though the company that made the part, Delphi, warned the automaker that the switch did not meet specifications. This followed a warning the year before — when the Saturn Ion was being developed — but G.M. said that “a design change had solved the problem,” according to the memo. Continue reading the main story Related Coverage The striking new details in the memo bolster the contention that both G.M. and the National Highway Traffic Safety Administration, more than previously acknowledged, ignored or dismissed warnings for more than a decade about a faulty ignition switch that, if bumped, could turn off, shutting the engine and disabling the air bags. General Motors has recalled nearly 2.6 million cars and has linked 13 deaths to the defect. </blockquote> 13 deaths, and we get this: <blockquote class="tr_bq"><div class="story-body-text story-content" data-para-count="362" data-total-count="2158" itemprop="articleBody">A House subcommittee, which gathered more than 200,000 pages of documents from G.M. and 6,000 pages from the agency, will hold a hearing on Tuesday. Mary T. Barra, General Motors’ chief executive, and David Friedman, the acting administrator of the safety agency, are scheduled to testify. Both are also scheduled to testify before a Senate panel on Wednesday.</div><div class="story-body-text story-content" data-para-count="362" data-total-count="2158" itemprop="articleBody"> </div><div class="story-body-text story-content" data-para-count="241" data-total-count="2399" itemprop="articleBody">“The problems persisted over a decade, the red flags were many, and yet those responsible failed to connect the dots,” Fred Upton, a Republican of Michigan and the chairman of the House Energy and Commerce Committee, said in a statement.</div><div class="story-body-text story-content" data-para-count="241" data-total-count="2399" itemprop="articleBody"> </div><div class="story-body-text story-content" data-para-count="104" data-total-count="2503" itemprop="articleBody">The most damaging finding in the memo concerned the four fatal crashes that went unheeded by regulators.</div><div class="story-body-text story-content" data-para-count="104" data-total-count="2503" itemprop="articleBody"> </div><div class="story-body-text story-content" data-para-count="224" data-total-count="2727" id="story-continues-5" itemprop="articleBody">In a presentation dated Nov. 17, 2007, the safety agency’s investigators reported to its Office of Defects Investigation on the fatal crashes, as well as broad range of complaints and other reports about cars shutting off.</div><div class="story-body-text story-content" data-para-count="224" data-total-count="2727" id="story-continues-5" itemprop="articleBody"> </div><div class="story-body-text story-content" data-para-count="355" data-total-count="3082" itemprop="articleBody">“The panel did not identify any discernible trend and decided not to pursue a more formal investigation,” the House memo said. The findings <a href="http://www.nytimes.com/2014/03/09/business/auto-regulators-dismissed-defect-tied-to-13-deaths.html" title="The report. ">reinforce an analysis</a> by The New York Times published March 8 that found the agency had received more than 260 complaints about Cobalts, Ions and other cars in the recall, citing potentially dangerous shutdowns.</div></blockquote> While GM is being grilled and raked over the coals, the health IT industry is likely going to get the healthcare industry's most generous and unprecedented special regulatory accommodation by FDA due to its products being deemed of "sufficiently low risk" (?) not to merit attention. -------------------------------------------- <div> </div>The FDA statement is particularly reckless, perhaps criminally so, given the following ten points. I add that the following are just highlights off the top of my head, and non-inclusive of all known facts on health IT risk: (1)  FDA's own 2010 "Internal Memo on HIT Risk", "not intended for public use" but exposed by Center for Public Integrity investigative reporter Fred Schulte (<a href="http://www.publicintegrity.org/authors/fred-schulte">http://www.publicintegrity.org/authors/fred-schulte</a>) when he was with the Huffington Post Investigative Fund (as described at <a href="http://hcrenewal.blogspot.com/2010/08/smoking-gun-internal-fda-memorandum-of.html" target="_blank">http://hcrenewal.blogspot.com/2010/08/smoking-gun-internal-fda-memorandum-of.html</a>), stated:   <div style="margin-left: 40px;">...In summary, the results of this data review suggest significant clinical implications and public safety issues surrounding Health Information Technology. The most commonly reported H-IT safety issues included wrong patient/wrong data, medication administration issues, clinical data loss/miscalculation, and unforeseen software design issues; all of which have varying impact on the patient’s clinical care and outcome, which included 6 death and 43 injuries. The absence of mandatory reporting enforcement of H-IT safety issues limits the number of relevant MDRs [device reports] and impedes a more comprehensive understanding of the actual problems and implications. </div><div dir="ltr"></div> They then go on to categorize the known risk factors and the impediments to knowing about their occurrence:  <blockquote class="tr_bq">Limitations of the MAUDE search and final subset of MDRs include the following:  1. Not all H-IT safety issue MDRs can be captured due to limitations of reporting practices including ...(a) Vast number of H-IT systems that interface with multiple medical devices currently assigned to multiple procodes making it difficult to identify specific procodes for H-IT safety issues; ...(b) Procode assignments are also affected by the ability of the reporter/contractor to correctly identify the event as a H-IT safety issue; ...(c) Correct identification by the reporter of the suspect device brand name is challenged by difficulties discerning the actual H-IT system versus the device it supports. 2. Due to incomplete information in the MDRs, it is difficult to unduplicate similar reports, potentially resulting in a higher number of reports than actual events. 3. Reported death and injury events may only be associated with the reported device but not necessarily attributed to the device. 4 Correct identification by the reporter of the manufacturer name is convoluted by the inability to discern the manufacturer of the actual H-IT system versus the device it supports. 5 The volume of MDR reporting to MAUDE may be impacted by a lack of understanding the reportability of H-IT safety issues and enforcement of such reporting.</blockquote> In other words, FDA does not know the level of risk due to systematic impediments to information diffusion. <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiRf0xG1UixoduxWOjXHN0BAMipTO7-63_YQZ4NKtaFyhMvkpdfo7MwpGBU8O0c6XKxBEM4owWvWl0RBV1amw0nVtJlMCMEwEy-o2fovaDZWLYJRc2uY6hS34Kl-lWLwwl9m-iZySg9o4b5/s1600/memo.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiRf0xG1UixoduxWOjXHN0BAMipTO7-63_YQZ4NKtaFyhMvkpdfo7MwpGBU8O0c6XKxBEM4owWvWl0RBV1amw0nVtJlMCMEwEy-o2fovaDZWLYJRc2uY6hS34Kl-lWLwwl9m-iZySg9o4b5/s1600/memo.jpg" width="243" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">Internal FDA Memo ("not intended for public use") on potential dangers of health IT.  Download the full PDF by clicking <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/Internal-FDA-Report-on-Adverse-Events-Involving-Health-Information-IT.pdf">here</a>.</td></tr></tbody></table> I think it axiomatic to state that it is, at best, seriously misleading to now state a technology is of "low risk" while internally having admitted that the risk level is not known due to impediments to that knowledge.  That situation has not changed since this memo's internal FDA dissemination, and its disclosure by Schulte. This is inexplicable on its face on scientific grounds. Further, another HHS agency, the Agency for Healthcare Research and Quality (AHRQ, <a href="http://www.ahrq.gov/">http://www.ahrq.gov/</a>) has also taxonomized in detail a rich tapestry of "how health IT can cause harm."  See "AHRQ Health IT Hazards Manager Report" at <a href="http://healthit.ahrq.gov/sites/default/files/docs/citation/HealthITHazardManagerFinalReport.pdf">http://healthit.ahrq.gov/sites/default/files/docs/citation/HealthITHazardManagerFinalReport.pdf</a> and its contained list of harms on pg. 29, reproduced below. AHRQ has no regulatory authority.  These failure modes are expensive to deal with, thus many will likely only be dealt with by the industry (if at all) after patient harms or near-misses.  Patients, however, are not experimental subjects for the debugging and "improvement" of experimental IT systems. <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGfJvUqIoCXmUuiiiqJvolkT3Ncg9DoM4VResY7HhOBmbfdZj29hKbwxLRTUbMi7gbaSCfQNdqcKqI6SKWi0JKIyOrHFgBfL3D0-rzEHwfVx6Lm37KilOi8LjiEUBdIzyH9oH47wXprM7H/s1600/ahrq.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="257" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGfJvUqIoCXmUuiiiqJvolkT3Ncg9DoM4VResY7HhOBmbfdZj29hKbwxLRTUbMi7gbaSCfQNdqcKqI6SKWi0JKIyOrHFgBfL3D0-rzEHwfVx6Lm37KilOi8LjiEUBdIzyH9oH47wXprM7H/s1600/ahrq.jpg" width="400" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">AHRQ Health IT Hazard Manager Report - Hazard Modes of Health IT (click to enlarge)</td></tr></tbody></table> Surely FDASIA is aware of this. <div>(2)  FDA CDRH Director Jeff Shuren MD, JD's own statement that the known risks are "the tip of an iceberg" at the HIT Policy Committee, Adoption/Certification Workgroup on February 25, 2010, where the topic was "HIT safety" (The text is available <a href="http://web.archive.org/web/20120320111030/http://healthit.hhs.gov/portal/server.pt/gateway/PTARGS_0_11673_910717_0_0_18/3Shuren_Testimony022510.pdf" target="_blank">at this link</a>): <div style="margin-left: 40px;">...... In the past two years, we [FDA] have received 260 reports of HIT-related malfunctions with the potential for patient harm – including 44 reported injuries and 6 reported deaths. Because these reports are purely voluntary, they may represent only the tip of the iceberg in terms of the HIT-related problems that exist.</div></div><div></div><div></div><div></div><div></div><div></div><div> Considering the admitted impediments to information diffusion, it's likely even at this point that FDA knew the number of injuries and deaths was far larger than GM's mere 13 ignition defect-related deaths. </div><div> </div><div><div>(3)   FDA's MAUDE (Manufacturer and User Facility Device Experience) database is a voluntary medical device defects reporting system, but is not specifically purposed for health IT and is almost unknown to typical health IT users as a resource for reporting flaws.  MAUDE reports show health IT devices are literally festooned with an incredible number of flaws, as if they come from dirt-floor-covered software sweatshops with little oversight. These are defects that have made it into live hospital and caregiver devices, and have led to reported harms and death (see <a href="http://hcrenewal.blogspot.com/2011/01/maude-and-hit-risk-mother-mary-what-in.html" target="_blank">http://hcrenewal.blogspot.com/2011/01/maude-and-hit-risk-mother-mary-what-in.html</a>). The voluntary nature of this MAUDE reporting by just a few HIT sellers, and lack of knowledge of it by health IT users as a resource, cannot fail to lead to the conclusion that the problems are far worse than this limited dataset indicates. (4)  The prestigious U.S. Institute of Medicine of the National Academies (<a href="http://www.iom.edu/">http://www.iom.edu/</a>), perhaps the top scientific authority in this country, also admitted the risk levels of health IT were unknown due to systematic impediments to knowing.  IOM noted this in their <a href="http://hcrenewal.blogspot.com/2011/11/iom-report-on-health-it-safety-nix-fda.html">late 2011 study on EHR safety</a>:</div></div><div> <blockquote>... While some studies suggest improvements in patient safety can be made, others have found no effect. Instances of health IT–associated harm have been reported. However, little published evidence could be found quantifying the magnitude of the risk. Several reasons health IT–related safety data are lacking include the absence of measures and a central repository (or linkages among decentralized repositories) to collect, analyze, and act on information related to safety of this technology. Another impediment to gathering safety data is contractual barriers (e.g., nondisclosure, confidentiality clauses) that can prevent users from sharing information about health IT–related adverse events. These barriers limit users’ abilities to share knowledge of risk-prone user interfaces, for instance through screenshots and descriptions of potentially unsafe processes. In addition, some vendors include language in their sales contracts and escape responsibility for errors or defects in their software (i.e., “hold harmless clauses”). The committee believes these types of contractual restrictions limit transparency, which significantly contributes to the gaps in knowledge of health IT–related patient safety risks. </blockquote> The IOM did note, contrary to FDA's current finding that these systems are of "sufficiently low risk", that: <blockquote>These barriers to generating evidence pose unacceptable risks to safety.[IOM (Institute of Medicine). 2012. <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/Patient%20Safety%20and%20Health%20IT%20prepub.pdf">Health IT and Patient Safety: Building Safer Systems for Better Care</a> (PDF). Washington, DC: The National Academies Press, pg. S-2.] </blockquote> Also in the IOM report: <blockquote class="tr_bq">… “For example, the number of patients who receive the correct medication in hospitals increases when these hospitals implement well-planned, robust computerized prescribing mechanisms and use barcoding systems. But even in these instances, the ability to generalize the results across the health care system may be limited. For other products— including electronic health records, which are being employed with more and more frequency— some studies find improvements in patient safety, while other studies find no effect. More worrisome, some case reports suggest that poorly designed health IT can create new hazards in the already complex delivery of care. Although the magnitude of the risk associated with health IT is not known, some examples illustrate the concerns. Dosing errors, failure to detect life-threatening illnesses, and delaying treatment due to poor human–computer interactions or loss of data have led to serious injury and death.”</blockquote></div><div></div><div> IOM could not have stated the reality more explicitly than via their statement "the magnitude of the risk associated with health IT is not known." </div><div> (5)   Surely FDA (and the FDASIA committees responsible for the new Report) are aware of  the ECRI Institute's Deep Dive study results from a study they carried out within their PSO-member hospitals (<a href="http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html" target="_blank">http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html</a>).  I would call 171 voluntarily-reported health IT-related mishaps in 36 hospitals over 9 weeks, with 8 injuries and 3 possible deaths, an alarming study. In fact, in 2014 based on their PSO data, the ECRI Institute identified health IT as #1 of the "Top Ten Technology Risks in Healthcare" (<a href="http://hcrenewal.blogspot.com/2014/04/in-ecri-institutes-new-2014-top-10.html">http://hcrenewal.blogspot.com/2014/04/in-ecri-institutes-new-2014-top-10.html</a>): <blockquote class="tr_bq">CONCERN #1: Data integrity failures with health information technology systems  With the federal government offering financial incentives for hospitals and physician practices to adopt EHR systems, use of these systems more than tripled from 2009 through 2012. “Health IT systems are very complex,” says James P. Keller, M.S., vice president, technology evaluation and safety, ECRI Institute. “They are managing a lot of information, and it’s easy to get something wrong” if the systems are not designed and implemented well. While appropriately designed and implemented systems can provide complete, current, and accurate patient care information so that the clinician can make appropriate treatment decisions, the presence of incorrect data can lead to incorrect treatment, potentially leading to patient harm.</blockquote></div><div></div><div> I certainly would NOT aver that this technology's risk level is of "sufficiently low risk" to not warrant formal regulation by a body skilled in software regulation, as is FDA., e.g., for medical devices and for IT used in pharmaceutical clinical trials data management and drug manufacturing. See for example "General Principles of Software Validation; Final Guidance for Industry and FDA Staff" at <a href="http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/ucm085281.htm">http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/ucm085281.htm</a>. (I would really not enjoy being in a position to have to make such an averment about "sufficiently low risk" under GM ignition investigation-like conditions... )</div><div> </div>(6)  Surely FDA (and the FDASIA committees responsible for the new Report) are aware of the data reported by the medical malpractice insurer CRICO, that insures the Harvard medical community (see <a href="http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html" target="_blank">http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html</a>): <blockquote class="tr_bq">... CRICO recently analyzed a year’s worth of medical malpractice claims in its comparative database [from numerous sources] and found 147 cases in which EHRs were a contributing factor. Computer systems that don’t “talk” to each other, test results that aren’t routed properly, and mistakes caused by faulty data entry or copying and pasting were among the EHR-related problems found in the claims, which represented $61 million in direct payments and legal expenses.  ... Half of the 147 cases resulted in severe injury.  [Death numbers are unstated - ed.] </blockquote> Note that these numbers were an examination of lawsuits filed; most medical malpractice never gets to the point of an actual filed lawsuit due to the unfavorable economics of the medical malpractice industry.  Perhaps 5% of actual events ever get filed, thus CRICO's data is also a "tip of an iceberg." (7)  Surely FDA (and the FDASIA committees responsible for the new Report) are aware of mass risk introduced by faulty systems such as in the incident in Rhode Island, at Lifespan Healthcare (<a href="http://hcrenewal.blogspot.com/2011/11/lifespan-rhode-island-yet-another.html">http://hcrenewal.blogspot.com/2011/11/lifespan-rhode-island-yet-another.html</a>), where thousands of prescriptions were altered by faulty HIT without physician knowledge.  Suffixes for the long acting version of a drug (e.g., "XL" or "XR") were dropped: <blockquote class="tr_bq">PROVIDENCE, R.I. (WPRI) - Rhode Island State Senator Jamie Doyle says he is shocked to hear a <a href="http://www.lifespan.org/">Lifespan</a> computer glitch caused thousands of patients to receive the wrong types of medication. [Appx. 2,000 across five Lifespan hospitals according to the Providence Journal, see below, and the <a href="http://www.washingtonpost.com/business/ri-senator-wants-investigation-after-up-to-2000-hospital-patients-got-wrong-form-of-medicine/2011/11/03/gIQAufcviM_story.html">WaPo</a> - ed.] Doyle is now calling for an independent review of all the hospitals Lifespan runs, and a review of the Rhode Island Department of Health. The DOH is investigating after learning patients who were supposed to receive medications taken once a day instead received medications meant to be taken more than once per day.  [In other words, they were taking short acting drugs on a long-acting once a day schedule, thus being massively under-dosed - ed.]</blockquote> (8)  The FDA (and the FDASIA committees responsible for the new Report) surely cannot be unaware of all of the "glitches" reported on in-situ health IT systems, as cataloged at this blog under the tag "glitch" and as of this writing numbering 25 posts, some including patient deaths.  See the results of the query link: <a href="http://hcrenewal.blogspot.com/search/label/glitch">http://hcrenewal.blogspot.com/search/label/glitch</a>. (9) Surely FDA (and the FDASIA committees responsible for the new Report) cannot be unaware that FDA itself had to recall health IT with flaws "serious enough to cause patient death": <blockquote class="tr_bq">FDA recall.  McKesson Anesthesia Care – Patient Case Data May Not Match Patient Data:  Use of this affected product may cause serious adverse health consequences, including death.  <a href="http://hcrenewal.blogspot.com/2014/03/ehr-recall-use-of-this-affected-product.html">http://hcrenewal.blogspot.com/2014/03/ehr-recall-use-of-this-affected-product.html</a> FDA Recalls Draeger Health IT Device Because "This Product May Cause Serious Adverse Health Consequences, Including Death" <a href="http://hcrenewal.blogspot.com/2011/12/fda-recalls-health-it-software-because.html">http://hcrenewal.blogspot.com/2011/12/fda-recalls-health-it-software-because.html</a> FDA Recall: Philips Xcelera Connect - Incomplete Information Arriving From Other Systems <a href="http://hcrenewal.blogspot.com/2012/07/health-it-fda-recall-philips-xcelera.html">http://hcrenewal.blogspot.com/2012/07/health-it-fda-recall-philips-xcelera.html</a> FDA recall:  An ED EHR "Glitch" That Mangles Prescriptions <a href="http://hcrenewal.blogspot.com/2013/08/a-good-way-to-cynernetically-harm-or.html" target="_blank">http://hcrenewal.blogspot.com/2013/08/a-good-way-to-cynernetically-harm-or.html</a> </blockquote> (10)  FDA (and the FDASIA committees responsible for the new Report) are surely not unaware of my own report to its MAUDE database (because the hospital denied my request to issue the report itself) of a fundamental defect in a widely used health IT system, Eclipsys Sunrise, that nearly caused the death of my mother... AFTER she was seriously injured due to a flaw in an ED's EHR that did lead a year later to her death: <blockquote class="tr_bq"><a href="http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfmaude/detail.cfm?mdrfoi__id=172955">http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfmaude/detail.cfm?mdrfoi__id=172955</a>2 ECLIPSYS SUNRISE CLINICAL MANAGER       Event Date 06/12/2010 Event Type  Injury   Patient Outcome  Hospitalization,Other,Life Threatening,Required Intervention Event Description The eclipsys sunrise clinical manager emr/cpoe is in use at (b) (6) hospital. This system appears to have a serious deficiency: an apparent lack of date constraint validity checking when users are seeking information on prior medication orders and administration. (b) (6), (b) (6) was admitted (b) (6) 2010, for cerebrovascular problems. Famotidine iv was started prophylactically to prevent gastric problems, but was discontinued and changed to protonix a few days later due to suspicion of causing severe agitation and confusion, causing her to pull her lines. Around (b) (6) 2010, patient was transferred to physical therapy floor in the hospital. Hospital considers such a transfer to be a "discharge" and "readmission. " however, patient did poorly, had to be sent back to med-surg floor several days later. Due to having pulled a percutaneous endoscopic gastrostomy tube -peg tube-, she was started on TPN on (b) (6) 2010. In the first bag of tpn solution was 40 mg. Famotidine. Patient's mental status began deteriorating and she began to get very, very agitated and confused once again. Eclipsys sunrise problem/bug was noted when son, a physician informaticist -and author of this report- noted the 40 mg famotidine in the tpn bag, and reported to the floor rn that this was contraindicated. The rn pulled up the medication order and administration records on the eclipsys sunrise clinical manager system to confirm famotidine had been administered previously. Famotidine was shown only as being ordered for tpn on (b) (6), but not prior. The rn selected a date constraint entry box, at which time a calendar widget popped up. The rn set the date constraint back to (b) (6), then (b) (6), then (b) (6) 2010, but the use of the famotidine at that time did not appear. Son of patient demanded the famotidine be stopped anyway, which it was, and that an allergy entry be entered. However, it was fortunate son was a physician and remembered the name of the medicine. In tracing this error today, it was found that the data from admission on (b) (6) to "discharge" to physical therapy floor (b) (6) 2010, was unavailable since it was considered a "prior admission" although the patient had never left the hospital physically. The sunrise system, however, failed to flag the (b) (6) 2010 date constraint entries as 'out of bounds' for the current admission. The validity of the date constraints was not checked, preventing the rn user from realizing he should have called up the prior admissions records. If son of patient had not been a physician, famotidine might have been continued and patient might have suffered more severe consequences than she did after the 40 mg was given in the first tpn bag. As it was, she spent the next three days in a severe delirium and is only slowly recovering. That the eclipsys sunrise ehr did not alert its user that the date constraints they set for seeking medication ordering and administration data were out of bounds -beyond the range of the current "admission" -is a significant and severe oversight and/or bg, and a danger to patients not fortunate enough to have a physician informaticist son closely monitoring their care. </blockquote> Addendum May 4, 2014: (11)   CMS: "we do not have any information that supports or refutes claims that a broader adoption of EHRs can save lives."  (But let's spend hundreds of billions of dollars anyway.) <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgKNTHRZ65twX8W-4VKJyyfOxz-EKIMmIfoipBwryewkc-IKs_JkusXtcujYkfmjqkzRE_1FyX0m7GAS3X-MTb0rq0yeup3rRxjRKLk2xmnWlO6BLlwHE0rJOqULoHziPGyOKQnO3Jkb2La/s1600/CMS_Letter.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgKNTHRZ65twX8W-4VKJyyfOxz-EKIMmIfoipBwryewkc-IKs_JkusXtcujYkfmjqkzRE_1FyX0m7GAS3X-MTb0rq0yeup3rRxjRKLk2xmnWlO6BLlwHE0rJOqULoHziPGyOKQnO3Jkb2La/s1600/CMS_Letter.jpg" width="308" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">CMS: "we do not have any information that supports or refutes claims that a broader adoption of EHRs can save lives."  [But let's spend hundreds of billions of dollars anyway.]  Click to enlarge.</td></tr></tbody></table> -------------------------------------------- Note that these ten points themselves, all I had time to write about this morning, themselves represent a "tip of the iceberg" regarding health IT risks. In my opinion it's immensely reckless for FDA to make a statement that "products with health management heath IT functions, includes software for health information and data management, medication management, provider order entry, knowledge management, electronic access to clinical results and most clinical decision support software ... are of sufficiently low risk" so as to not warrant formal regulation that is already in place for other healthcare software sectors. Fortunately, the public gets to comment via this announcement: Proposed Risk-Based Regulatory Framework and Strategy for Health Information Technology Report; Notice to Public of Availability of the Report and Web Site Location; Request for Comments <a href="http://www.regulations.gov/#!documentDetail;D=FDA_FRDOC_0001-4678">http://www.regulations.gov/#!documentDetail;D=FDA_FRDOC_0001-4678</a> I feel, however, that the decision is a given, and that the health IT industry has such regulatory capture that public comments will be ignored.  (Not that I won't try.) Finally: I ponder what ever happened to the inquiry responses about health IT defects and harm sought by the Senate Finance Committee, as reported in the Washington Post: <blockquote class="tr_bq">Electronic medical records draw frequent criticisms By Alexi Mostrous Washington Post Staff Writer Sunday, October 25, 2009 <a href="http://www.washingtonpost.com/wp-dyn/content/article/2009/10/24/AR2009102400967.html?hpid%3Dtopnews&sub=AR">http://www.washingtonpost.com/wp-dyn/content/article/2009/10/24/AR2009102400967.html?hpid%3Dtopnews&sub=AR</a> ... the Senate Finance Committee has amassed a thick file of testimony alleging serious computer flaws from doctors, patients and engineers unhappy with current systems. On Oct. 16, the panel wrote to 10 major sellers of electronic record systems, demanding to know, for example, what steps they had taken to safeguard patients. "Every accountability measure ought to be used to track the stimulus money invested in health information technology," said <a href="http://projects.washingtonpost.com/congress/members/g000386/" target="">Sen. Charles E. Grassley</a> (Iowa), the panel's ranking Republican. </blockquote> The results of that request seem to have gone to the recycle bin. -- SS

FDA on health IT risk: reckless, or another GM-like political coverup? "We don't know the magnitude of the risk, and what we do know is the tip of the iceberg, but health IT is of 'sufficiently low risk' that we don't need to regulate it."

In my Sept. 16, 2013 post "An Open Letter to David Bates, MD, Chair, ONC FDASIA Health IT Policy Committee on Recommendations Against Premarket Testing and Validation of Health IT" (http://hcrenewal…

Đọc thêm »

09 Apr 2014

Regulation of HIT by federal independent agency vs. federal executive agency / Open criminal probe of GM recall

In the FY2014 HHS budget-in-brief document (PDF at <a href="http://www.hhs.gov/budget/fy2014/fy-2014-budget-in-brief.pdf">http://www.hhs.gov/budget/fy2014/fy-2014-budget-in-brief.pdf</a>) on page 115, there's this: <div class="gmail_extra"> <div style="margin-left: 40px;">Patient Safety and Health IT Usability Patient safety and usability continue to be a focus for ONC. Working with federal partners AHRQ and FDA, ONC will create the foundation for a patient safety program that will be launched in FY 2014called “The Patient Safety Plan”. The Plan seeks to ensure that health IT is safely designed and implemented, medical staff are properly informed and trained to use their health IT systems, and a surveillance system is established to monitor health IT related patient safety events and ensure that unsafe conditions are corrected.</div></div> I believe the health IT industry now realizes some form of regulation is inevitable after, for example, revelations from medical malpractice insurers that a significant number of lawsuits involve the effects of health IT (see for instance my post "Malpractice Claims Analysis Confirms Risks in EHRs" at <a href="http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html">http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html</a>). I also believe that industry and its pundits have pushed for the most favorable regulation possible.  This involves pushing for regulation by agencies with the least agency independence as possible, as I bring out below.  HHS along with its member branches FDA, AHRQ and ONC are executive departments of the US government  The legislation that governs the way such departments and agencies may propose and establish regulations is the Administrative Procedure Act of 1946 (<a href="http://en.wikipedia.org/wiki/Administrative_Procedure_Act">http://en.wikipedia.org/wiki/Administrative_Procedure_Act</a>). First, it seems the executive branch is attempting to concentrate more power within itself over health IT through proposals like in the FY2014 HHS document. I also point out that that HHS (and its offices such as ONC, FDA etc.) are federal executive departments.  <a href="http://en.wikipedia.org/wiki/United_States_federal_executive_departments" target="_blank">http://en.wikipedia.org/wiki/United_States_federal_executive_departments</a>. These are not entirely independent of presidential control: <blockquote>"The heads of the federal executive departments, known as secretaries of their respective department, form the traditional Cabinet of the United States, an executive organ that serves at the disposal of the president and normally act as an advisory body to the presidency."</blockquote> In other words, the leaders serve at the pleasure of the President. This is as opposed to the executive department cousin, the federal independent agency, such as the NRC (Nuclear regulatory commission) and NTSB (national transportation safety board) that are independent agencies (<a href="http://en.wikipedia.org/wiki/Independent_agencies_of_the_United_States_government" target="_blank">http://en.wikipedia.org/wiki/Independent_agencies_of_the_United_States_government</a>): <blockquote>Independent agencies of the United States federal government are those agencies that exist outside of the federal executive departments (those headed by a Cabinet secretary). More specifically, the term may be used to describe agencies that, while constitutionally part of the executive branch, are independent of presidential control, usually because the president's power to dismiss the agency head or a member is limited.</blockquote> It is no secret the administration is determined to push as rapid as possible rollout of health IT, come hell or high water, via HITECH, its coming penalties and other measures.  Its predecessor administration was a bit more genteel and circumspect in this regard. It is clear to me that, in the current political environment, regulation by a federal executive agency is minimalist and will likely be politically ineffective, due to fear of its leadership of being dismissed if they upset the upper echelons.   I note that Jeffrey Shuren, a physician and attorney, director of FDA CDRH already stated in 2010 that "health IT is a political hot potato" as a reason that FDA "has largely refrained from enforcing our regulatory requirements."  See my April 2011 post "FDA Decides Regulating Implantable Defibrillator Medical Devices a 'Political Hot Potato'; Demurs" at <a href="http://hcrenewal.blogspot.com/2011/04/fda-decides-regulating-implantable.html">http://hcrenewal.blogspot.com/2011/04/fda-decides-regulating-implantable.html</a> for links to source. I believe it would be better to place the authority for health IT regulation under the aegis of a federal independent agency, whether an existing one or one created for that purpose, so that its leaders are more independent of executive branch control. ----- I predict that without meaningful regulation, this is where the health IT industry will find itself in a few years. <blockquote class="tr_bq"><a href="http://www.reuters.com/article/2014/03/11/us-autos-gm-recall-probe-idUSBREA2A1RZ20140311" target="_blank">http://www.reuters.com/article/2014/03/11/us-autos-gm-recall-probe-idUSBREA2A1RZ20140311</a> Reuters - Federal prosecutors are examining whether General Motors is criminally liable for failing to properly disclose problems with some of its vehicles that were linked to 13 deaths and led to a recall last month, according to a source familiar with the investigation. The New York-based probe is in its early stages, and the source did not elaborate on the legal theory behind the potential criminal liability. .. Federal investigators are reviewing information about how GM handled reports of problems with ignition switches that first came to light 10 years ago, according to the source. The federal probe by the U.S. attorney in Manhattan adds to a growing list of U.S. authorities examining the recall, which GM announced in February. The National Highway Traffic Safety Administration (NHTSA) previously opened an investigation into whether GM reacted swiftly enough in its recall. Earlier on Tuesday, Reuters reported that a U.S. Senate committee chairman is seeking a hearing on the issue. The U.S. House Energy and Commerce Committee also ordered GM and NHTSA to turn over information about GM's ignition switch problems. The problems in some instances allowed the engine and other components, including front airbags, to turn off while the vehicle was traveling at high speed. More than 1.6 million older vehicles are affected. The failure is believed to be caused when weight on the ignition key, road conditions or some other jarring event causes the ignition switch to move out of the "run" position, turning off the engine and most of the car's electrical components mid-drive, with sometimes catastrophic results. GM has recommended that owners use only the ignition key with nothing else on the key ring. .. The House committee examining the GM issue, led by Michigan Republican Fred Upton, gave the company and NHTSA until March 25 to turn over information about their responses to consumers' complaints about the problem. The committee has asked GM officials to provide a briefing no later than March 18 on how GM has responded to reports of incidents since 2003 and its interaction with NHTSA since then on problems related to the ignition defect. Upton led the 2000 investigation into Firestone tire failures on Ford Motor Co vehicles, resulting in the TREAD Act that requires automakers to report complaints of defects to the NHTSA. That law also makes it a crime to intentionally mislead the agency about defects that lead to serious accidents. ... The person familiar with the criminal probe declined to discuss whether prosecutors were considering liability under the TREAD Act.</blockquote>  In fact, there is no good reason the health IT sector has been excluded from such actions, through an unprecedented regulatory accommodation this single healthcare sector has enjoyed for decades - namely, that of no true regulation at all.   <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjAREJP0qSqoHqaCCq9y3x81HIJTzS6-HLSU3as_BIzCDOfNAHgX2WAaVEFDLHSYhUMaJFX_l6DHv-RxT00pyP3RJcFQfgbCqBsXJG_-xohfHQYOYO1jqYyqUUObqd3ro9ymPy1cI1ivlXh/s1600/dilbert.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="150" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjAREJP0qSqoHqaCCq9y3x81HIJTzS6-HLSU3as_BIzCDOfNAHgX2WAaVEFDLHSYhUMaJFX_l6DHv-RxT00pyP3RJcFQfgbCqBsXJG_-xohfHQYOYO1jqYyqUUObqd3ro9ymPy1cI1ivlXh/s1600/dilbert.jpg" width="200" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"> <div class="MsoNormal">Sure, let's regulate a <s>potentially</s> proven dangerous healthcare technology, health IT (a glamor child of this administration) by a federal executive agency that serves "at the disposal" of the President ... instead of a federal independent agency, with ... uh ...better independence.  Great idea!</div></td></tr></tbody></table> -- SS 3/12/14 Addendum: Note this report of possible delays by the Department of Transportation on disclosure of GM ignition defects, by its National Highway Traffic Safety Administration branch, that caused fatalities and where disclosure could have (and finally now has) resulted in huge legal problems for GM.  GM is a company that was a centerpiece of the administration's economic interventions in recent years: <blockquote class="tr_bq">Did the Obama White House Protect GM? Liz Peek The Fiscal Times March 12, 2014</blockquote><blockquote><a href="http://www.thefiscaltimes.com/Columns/2014/03/12/Did-Obama-White-House-Protect-GM">http://www.thefiscaltimes.com/Columns/2014/03/12/Did-Obama-White-House-Protect-GM</a> Did the Obama administration purposefully hide problems with GM cars? Were they panicked that a massive recall of GM products would undermine one of President Obama’s most self-congratulatory campaign themes – that he “saved” Detroit’s auto industry? This is a tale of two car companies: GM, shining star in President Obama’s reelection galaxy, and Toyota, which became political fodder. The House Energy and Commerce Committee announced two days ago that it would undertake an investigation into why it took GM until quite recently to address a decade of complaints about stalling problems with several car models, and why the National Highway Traffic Safety Administration did not demand a recall of the troubled lines earlier on.  [Because they were afraid to? - ed.]  Reports of unexpected stalling in Chevy Cobalts began to trickle in as early as 2003 when 7 incidents were relayed to NHTSA, according to The New York Times ... </blockquote> Read the whole article. The Department of Transportation is ... you guessed it ... a <a href="http://en.wikipedia.org/wiki/United_States_federal_executive_departments">federal executive agency</a>, not a federal independent agency. -- SS <div id="stcpDiv" style="left: -1988px; position: absolute; top: -1999px;"><div class="field field-name-field-author-ref field-type-entityreference field-label-hidden"><div class="field-items"><div class="field-item odd"><a href="http://www.thefiscaltimes.com/Authors/P/Liz-Peek" rel="author">Liz Peek</a></div></div></div>The Fiscal Times <div class="field field-name-field-release-date field-type-datetime field-label-hidden"><div class="field-items"><div class="field-item odd">March 12, 2014</div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item odd">Did the Obama administration purposefully hide problems with GM cars? Were they panicked that a massive recall of GM products would undermine one of President Obama’s most self-congratulatory campaign themes – that he “saved” Detroit’s auto industry? This is a tale of two car companies: GM, shining star in President Obama’s reelection galaxy, and Toyota, which became political fodder. The House Energy and Commerce Committee announced two days ago that it would undertake an investigation into why it took GM until quite recently to address a decade of complaints about stalling problems with several car models, and why the National Highway Traffic Safety Administration did not demand a recall of the troubled lines earlier on.  Reports of unexpected stalling in Chevy Cobalts began to trickle in as early as 2003 when 7 incidents were relayed to NHTSA, <a href="http://www.nytimes.com/2014/03/09/business/auto-regulators-dismissed-defect-tied-to-13-deaths.html?_r=0">according to The New York Times</a>.</div></div></div>- See more at: http://www.thefiscaltimes.com/Columns/2014/03/12/Did-Obama-White-House-Protect-GM#sthash.Ed9FH0ZD.dpuf</div><div id="stcpDiv" style="left: -1988px; position: absolute; top: -1999px;">National Highway Traffic Safety Administrationsuspected of causing many deaths:  "Did the Obama White House Protect GM?", The Fiscal TimesMarch 12, 2014, <a href="http://www.thefiscaltimes.com/Columns/2014/03/12/Did-Obama-White-House-Protect-GM">http://www.thefiscaltimes.com/Columns/2014/03/12/Did-Obama-White-House-Protect-GM</a>.Note that the Department of Transportation is ... you guessed it ... a <a href="http://en.wikipedia.org/wiki/United_States_federal_executive_departments">federal executive department</a>.</div><div id="stcpDiv" style="left: -1988px; position: absolute; top: -1999px;">Did the Obama White House Protect GM?</div><div id="stcpDiv" style="left: -1988px; position: absolute; top: -1999px;">Did the Obama White House Protect GM?</div>

Regulation of HIT by federal independent agency vs. federal executive agency / Open criminal probe of GM recall

In the FY2014 HHS budget-in-brief document (PDF at http://www.hhs.gov/budget/fy2014/fy-2014-budget-in-brief.pdf) on page 115, there's this:Patient Safety and Health IT UsabilityPatient safety and usab…

Đọc thêm »

12 Mar 2014

Proof positive of government incompetence and recklessness in information technology - H.R.3303 - Bipartisan call for exemption of health IT from the FD&C Act

Here's proof positive of government incompetence and recklessness in information technology. A new proposed bill that would exempt health IT from the Food, Drug & Cosmetic Act and FDA regulation. Rep. Marsha Blackburn (R-TN) calls for exemption of healthcare software from FDA regulation with bipartisan co-sponsorship from Reps. Gene Green (D-TX), Phil Gingrey, M.D. (R-GA), Diana DeGette (D-CO), Greg Walden (R-OR) and G.K. Butterfield (D-NC). H.R.3303 - SOFTWARE Act of 2013 - referred to House Energy & Commerce on 10/22/2013 <a href="http://beta.congress.gov/bill/113th/house-bill/3303/text">http://beta.congress.gov/bill/113th/house-bill/3303/text</a> This remarkable and unprecedented regulatory accommodation is based on nebulous, speculative and largely imaginary grounds that translate to - just because:   <blockquote class="tr_bq">... (c) Sense of Congress.--It is the sense of the Congress that--             (1) clinical software and health software (as defined in         section 201(tt) of the Federal Food, Drug, and Cosmetic Act, as         added by subsection (a)) [can]--                     (A) advance the goals of enhanced patient safety                 and continued innovation;                     (B) hold much promise to lower costs and improve                 the health of patients; and                     (C) can improve the quality and efficacy of health                 care provider services </blockquote> This is despite known defects and harms in-the-now (e.g., ECRI Deep Dive Study with 8 injuries and 3 possible deaths in 9 weeks from 171 health IT 'mishaps', voluntarily reported in just 36 hospitals,<a href="https://www.ecri.org/EmailResources/PSRQ/ECRI_Institute_PSO_Deep%20Dive_HIT_TOC.pdf"> https://www.ecri.org/EmailResources/PSRQ/ECRI_Institute_PSO_Deep%20Dive_HIT_TOC.pdf</a>; Emergency Department EHR dangers as at <a href="http://hcrenewal.blogspot.com/2013/10/quality-and-safety-implications-of.html">http://hcrenewal.blogspot.com/2013/10/quality-and-safety-implications-of.html</a>; innumerable "glitches" that can kill, <a href="http://hcrenewal.blogspot.com/search/label/glitch">http://hcrenewal.blogspot.com/search/label/glitch</a> and <a href="http://hcrenewal.blogspot.com/2011/01/maude-and-hit-risk-mother-mary-what-in.html">http://hcrenewal.blogspot.com/2011/01/maude-and-hit-risk-mother-mary-what-in.html</a>; baby deaths, <a href="http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html">http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html</a> etc.) Instead this group of intrepid Cybernetic Crusaders, to whom your life is valuable (as a guinea pig, it seems) call for -- <blockquote class="tr_bq">"the President and the Congress [to] work together to develop and enact legislation that establishes a risk-based regulatory framework for such clinical software."</blockquote> With the Obamacare/Obamaware debacle still in progress ... (see "Drudge Report, Oct. 10, 2013, 9 AM EST: All that needs to be said about government, computing and healthcare" at <a href="http://hcrenewal.blogspot.com/2013/10/drudge-report-oct-10-2013-9-am-est-all.html">http://hcrenewal.blogspot.com/2013/10/drudge-report-oct-10-2013-9-am-est-all.html</a>) ... All I can say is: REALLY? -- SS p.s. perhaps I should have entitled this post "Look, Ma, No Regulation!" (See <a href="http://hcrenewal.blogspot.com/2011/06/my-mother-passed-away.html">http://hcrenewal.blogspot.com/2011/06/my-mother-passed-away.html</a>.) -- SS

Proof positive of government incompetence and recklessness in information technology - H.R.3303 - Bipartisan call for exemption of health IT from the FD&C Act

Here's proof positive of government incompetence and recklessness in information technology.A new proposed bill that would exempt health IT from the Food, Drug & Cosmetic Act and FDA regulation.Rep. M…

Đọc thêm »

29 Oct 2013

Quality and Safety Implications of Emergency Department Information Systems: ED EHR Systems Pose Serious Concerns, Report Says

A report "Quality and Safety Implications of Emergency Department Information Systems" appeared in the Oct. 2013 issue of "Annals of Emergency Medicine."  It is available fulltext at <a href="http://www.annemergmed.com/article/S0196-0644%2813%2900506-4/fulltext">http://www.annemergmed.com/article/S0196-0644%2813%2900506-4/fulltext</a>, or in PDF via the tab, free as of this writing. First, a preamble:  I once tried to alert a hospital where I'd trained decades before, Abington Memorial Hospital (<a href="http://www.amh.org/">http://www.amh.org/</a>), of impediments to safe care I'd noted in their EHR's, predominantly their ED EHR.  They did not listen.  In fact, their response to my concerns was characterized by an apparent incompetence regarding conduct of safety investigations.  For instance, to my written concern in an April 2010 letter to the CEO and CMO about the ED EHR that: <blockquote class="tr_bq"> ... I've also had to stop administration [to my mother] of an antibiotic (Levaquin) in the recent past in the ED that she has had an adverse reaction to (torn rotator cuff), despite my having told ED intake she was allergic to it. She relates that administration of Levaquin was then almost repeated on the floor until she herself refused it during that past admission.</blockquote> This was the sworn testimony in May 2013 about the "investigation" that resulted, from the hospital's VP of Risk Management, <a href="http://www.corporationwiki.com/Pennsylvania/Abington/regina-sturgis/81813980.aspx">Regina Sturgis</a>: <blockquote class="tr_bq">A:      Deborah [hospital General Counsel] asked me to investigate the Levaquin issue which I did. Q:      Did you do that on your own or did you delegate some of the -- A:      No.  I did it on my own. Q:      Do you know whether any of the IT folks were ever brought in to look at the -- the EMR issues referenced in this letter? A:     No, I do not.  I know that I was asked to look at the Levaquin because of my clinical background. Q:      Okay.  Did you come up with any conclusions? A:      Yes. Q:      What was your conclusion? A:      That she had been ordered Levaquin in the ETC [Emergency Trauma Center a.k.a. ED], that it had been discontinued about a very short period of time later, under a half an hour, and that she never received it. </blockquote> So, the investigation of a complaint that family and then the patient themselves had to stop the administration of a drug whose staff and EHR had been informed of an allergy consisted of confirming that the medication was never given.  No problem, the ED EHR is safe. (I am not joking; that is the testimony given.  Imagine such an investigation and conclusion about, say, reported aircraft flaws, or, in the industry in which I was once a safety officer, public transit vehicle defects and dangers.) However, when competent people investigate similar issues, the findings are concerning.  From Modern Healthcare (<a href="http://www.modernhealthcare.com/">http://www.modernhealthcare.com/</a>), a publication for healthcare executives, on the new Annals of Emergency Medicine article: <blockquote class="tr_bq"><a href="http://www.modernhealthcare.com/article/20130624/NEWS/306249952/">ED EHR systems pose serious concerns, report says</a> By <a href="mailto:jconn@modernhealthcare.com" target="_blank">Joseph Conn</a> Modern Healthcare <div>June 24, 2013</div></blockquote><blockquote>Electronic health-record systems used in <a href="http://www.modernhealthcare.com/section/articles?tagID=5739" target="_blank">emergency</a> departments are beset with poor data displays, loaded with so many alerts warning of potential <a href="http://www.modernhealthcare.com/section/articles?tagID=51" target="_blank">patient-safety issues</a> that they can lead to user alert fatigue, and may be generating incorrect physician orders, according to a report by two emergency physicians' study groups. Meanwhile, providers wanting to address these <a href="http://www.modernhealthcare.com/section/articles?tagID=975" target="_blank">EHR</a> issues are hampered by a lack of research and solid evidence of the extent of the problem with these systems, and by contract provisions with EHR vendors that stymie the free flow of information about system-linked safety concerns, the report authors say. </blockquote> So, ED's across the country are rolling out technology, often taking advantage of ARRA's HITECH incentives ... but there is a lack of research and solid evidence into the risks.  Allow me to opine - that's simply crazy. <blockquote class="tr_bq">The groups found that “poor data display is a serious problem with many of today's EDISs,” while “the sheer volume” of alerts that range from the “completely irrelevant to life threatening” [or lack of appropriate alerts to relevant, simple issues such as data input errors - ed.] can “dull the senses, leading to a failure to react to a truly important warning.” They also found that “an alarming number of clinicians are anecdotally reporting a substantial increase in the incidence of wrong order/wrong patient errors while using the computerized physician order entry component of information systems.”</blockquote> The word "anecdote", as I have written, is being misused.  The reports are not "anecdotes."  They are risk management-relevant incident reports.  (See "From a Senior Clinician Down Under: Anecdotes and Medicine, We are Actually Talking About Two Different Things" at <a href="http://hcrenewal.blogspot.com/2011/08/from-senior-clinician-down-under.html">http://hcrenewal.blogspot.com/2011/08/from-senior-clinician-down-under.html</a>.) <blockquote class="tr_bq">Two study groups from the American College of Emergency Physicians have recommended a program of systemic vigilance over electronic health-record systems used in emergency departments to improve patient safety and enhance quality of care. ACEP workgroups on informatics and on quality improvement and patient safety published their findings in an article, “<a href="http://www.annemergmed.com/article/S0196-0644%2813%2900506-4/abstract" target="_blank">Quality and Safety Implications of Emergency Department Information Systems</a>,” in the current issue of the Annals of Emergency Medicine. </blockquote> Post marketing surveillance, a standard for decades in other healthcare sectors, has been absent from health IT due to a long-obsolete special regulatory accommodation afforded that industry.  This accommodation was initiated when systems were simple and merely advisory - not the comprehensive enterprise clinical resource and clinician command-and-control systems they are today.  Now, clinician investigators of the technology such as the authors of this study are realizing that continuing this accommodation is a mistake. <blockquote class="tr_bq">It follows in the wake of, and references, an Institute of Medicine report from 2011, “Health IT and Patient Safety: Building Safer Systems for Better Care.” That report concluded that “current market forces are not adequately addressing the potential risks associated with the use of health IT.” It also comes eight months after the New England Journal of Medicine published “<a href="http://www.nejm.org/doi/full/10.1056/NEJMsb1205420" target="_blank">Electronic Health Records and National Patient-Safety Goals</a>,” which warned that recent evidence “has highlighted substantial and often unexpected risks resulting from the use of EHRs and other forms of health information technology.”</blockquote> I note that if you frequent this blog, you likely read material similar to the bolded red statements above here first, as authored by me, dating to the founding of this blog in 2004. <blockquote class="tr_bq">... “The rush to capitalize on the huge federal investment of $30 billion for the adoption of electronic medical records led to some unfortunate and unintended consequences, particularly in the unique emergency department environment,” said Dr. Heather L. Farley, the lead author of the report, in a news release. “The irreversible drive toward EDIS implementation should be accompanied by a constant focus on improvement and hazard prevention." Farley is assistant chairwoman of the Department of Emergency Medicine at Christiana Care Health System in Newark, Del.</blockquote> Ironically, I note in Dr. Farley's statement some of my own advice, given to ED staff when I was Chief Medical Informatics Officer at Christiana Care 1996-8.   I had in that time period advised <a href="http://www.christianacare.org/bodymod.cfm?id=169&action=detail&ref=1909">Charles Reese IV, MD</a>, Chair of Emergency Medicine, to not implement EHRs or, at best, implement document imaging systems (since ED charts are not that long or complex), not full field-based EHRs, due to the "unfortunate and unintended consequences" of bad health IT in such an environment I recognized even then.  It was only a few years ago that my advice was finally overturned. <blockquote class="tr_bq">The authors also report “(t)here are few consistent data on how commonly these errors occur, and few studies are actually focused on collecting evidence of these errors.” Meanwhile, “there is currently no mechanism in place to systematically allow, let alone encourage, users to provide feedback about ongoing safety issues or concerns” with EHRs in general, and EDISs specifically.</blockquote> On its face, that is not a safety-conscious environment and the rollout and use of such systems seems a fundamental violation of patient's rights, made worse by the fact that there is no informed consent process whatsoever to ED EHR use. <blockquote class="tr_bq">The workgroups came up with seven recommendations: appointing an emergency department “clinician champion,” creating within healthcare delivery organizations an EDIS performance improvement group and an ongoing review process, paying timely attention to EDIS-related patient-safety issues raised by the review process, disseminating to the public lessons learned from performance improvement efforts, distributing vendors' product updates in a timely manner to all EDIS users and removing the “hold harmless” and “learned intermediary clauses” from vendor contracts. </blockquote> Many of these issues have been discussed on this blog. <blockquote class="tr_bq">“The learned intermediary doctrine implies that the end users (clinicians) are the medical experts and should be able to detect and overcome any fallibility or contributing factor of the product,” the authors said.</blockquote> I have also pointed out the absurdity of such a "doctors are clairvoyant" attitude, e.g., at my 2011 post on basic common sense on IT adverse consequences at <a href="http://hcrenewal.blogspot.com/2011/04/common-sense-on-side-effects-lacking-in.html">http://hcrenewal.blogspot.com/2011/04/common-sense-on-side-effects-lacking-in.html</a>. <blockquote class="tr_bq">They conclude that the “lack of accountability for vendors through hold harmless clauses and the shifting of liability to the clinicians through the learned intermediary doctrine are significant and additional impairments to safety improvement. Electronic health records and EDISs are sufficiently complex that the physician and other users cannot be expected to anticipate unpredictable errors.” </blockquote> That aligns with the work of Dr. Jon Patrick in Sydney, whose treatise "A study of an Enterprise Health information System" on the Cerner FirstNet ED EHR is available here: <a href="http://sydney.edu.au/engineering/it/~hitru/index.php?option=com_content&task=view&id=91&Itemid=146">http://sydney.edu.au/engineering/it/~hitru/index.php?option=com_content&task=view&id=91&Itemid=146</a> <blockquote class="tr_bq">Earlier this month, the Electronic Health Record Association, an EHR developers trade group affiliated with the Chicago-based Healthcare Information and Management Systems Society, announced the launch of a voluntary “<a href="http://www.modernhealthcare.com/article/20130611/NEWS/306119952/ehr-trade-group-issues-code-of-conduct-to-improve-patient-safety" target="_blank">code of conduct</a>” in which adherents would agree to drop “gag clauses” in the contracts with their provider customers. </blockquote> Great.  Per the wonderful 2007 article "The Denialists' Deck of Cards: An Illustrated Taxonomy of Rhetoric Used to Frustrate Consumer Protection Efforts" by Chris Jay Hoofnagle, available at <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=962462">http://papers.ssrn.com/sol3/papers.cfm?abstract_id=962462</a>, as of this writing free: <blockquote class="tr_bq"> ... At this point [of losing the argument], the denialist must propose "self regulation" to deal with the problem that doesn't exist. The cool thing about self regulation is that it cannot be enforced, and once the non-existent problem blows over, the denialist can simply scrap it! [20] [20] In the runup to passage of bank privacy legislation, data brokers created a group called the "Individual Reference Services Group" that promptly disappeared after the legislation passed.</blockquote> ("Denialism" is the use of rhetorical techniques and predictable tactics to erect barriers to debate and consideration of any type of reform, regardless of the facts.) IMO 'self regulation' of healthcare is, on its face, a deception.  There are simply too many conflicts of interest. On use of "integrated" big systems: <blockquote class="tr_bq">“These systems do have glitches [indeed - see <a href="http://hcrenewal.blogspot.com/search/label/glitch">http://hcrenewal.blogspot.com/search/label/glitch</a> - ed], but it can be plain and simple bad design that can lead to clinical errors,” Cozzens said.  But ED physicians, he said, are “having the enterprise systems forced upon them. To think you can take one system and adapt it to those different environments is totally wrong. That's why you see low physician satisfaction and the productivity is going down, all for the sacrifice of having an integrated system.”</blockquote> In fact, so-called "best of breed" systems can be bad health IT as well.  See the aforementioned evaluation by Dr. Patrick in Australia. <blockquote class="tr_bq">Bad Health IT ("BHIT") is defined as IT that is ill-suited to purpose, hard to use, hard to customize, unreliable, loses data or provides incorrect data, causes cognitive overload, slows rather than facilitates users, lacks appropriate alerts, creates the need for hypervigilance (i.e., towards avoiding IT-related mishaps) that increases stress, is lacking in security, compromises patient privacy or otherwise demonstrates suboptimal design and/or implementation.  </blockquote> Through my own work, I've seen bad health IT result in patient harm and death.  It's just unfortunate that I got started in this line of work by being, in effect, shot out of a cannon.  That is, my own mother was a victim. -- SS Addendum 10/8/13: From the article: <blockquote class="tr_bq">End-User Recommendation 4: EDIS-related patient safety concerns identified by the review process should be addressed in a timely manner by ED providers, the EDIS vendors, and hospital administration. Each of these processes should be performed in full transparency, specifically with openness, communication, and accountability. </blockquote> I'm not sure the aforementioned levaquin near-accident "investigation" meets these standards. -- SS

Quality and Safety Implications of Emergency Department Information Systems: ED EHR Systems Pose Serious Concerns, Report Says

A report "Quality and Safety Implications of Emergency Department Information Systems"appeared in the Oct. 2013 issue of "Annals of Emergency Medicine." It is available fulltext at http://www.annemer…

Đọc thêm »

08 Oct 2013

Load more posts