healthy4u: Kaiser Family Foundation

Kaiser Health News/Philadelphia Inquirer on InformaticsMD: "The flaws of electronic records"

At my Dec. 2012 post "<a href="http://hcrenewal.blogspot.com/2012/12/upcoming-profile-of-informaticsmd-in.html" target="_blank">How an interview for Kaiser Health News rekindled memories of health IT dysfunction in the 90's that persist in the 10's</a>" I mentioned an interview by a reporter from the Kaiser Health Foundation regarding health IT flaws. His article appeared in both the <a href="http://www.philly.com/philly/entertainment/20130218_The_flaws_of_electronic_records.html" target="_blank">Philadelphia Inquirer</a> and <a href="http://www.kaiserhealthnews.org/Stories/2013/February/18/Scot-Silverstein-health-information-technology.aspx" target="_blank">Kaiser Health News</a> today under the title "The flaws of electronic records": <blockquote class="tr_bq">Philadelphia Inquirer / Kaiser Health News Feb. 18, 2013 <h5 class="byline">Jay Hancock, KAISER HEALTH NEWS</h5><a href="http://www.philly.com/philly/entertainment/20130218_The_flaws_of_electronic_records.html" target="_blank">The flaws of electronic records</a> Drexel University's Scot Silverstein is a leading critic of the rapid switch to computerized medical charts, saying the notion that they prevent more mistakes than they cause is not proven.   <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_8NHZXfqJrMOagNsDryhPIBfqkCL6Fpg0AV_7cXGpvSysrGf5LNS4vuXZ7bHr0FvlxiN9_8QDMVh7JtYnhDxeQ9XkUACF_VE4yC5XetVqe3I7aWif1W7wxpor32l3xF1SPfZxrg-mSG9S/s1600/silverstein_fixing_computer.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="205" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_8NHZXfqJrMOagNsDryhPIBfqkCL6Fpg0AV_7cXGpvSysrGf5LNS4vuXZ7bHr0FvlxiN9_8QDMVh7JtYnhDxeQ9XkUACF_VE4yC5XetVqe3I7aWif1W7wxpor32l3xF1SPfZxrg-mSG9S/s1600/silverstein_fixing_computer.JPG" width="320" /></a></div> Scot Silverstein of Lansdale, one of the most ardent critics of electronic medical records, works on an antique computer. A growing collection of evidence suggests poorly designed medical software can obscure clinical data, generate incorrect treatment orders, and cause other problems. <div class="photo_area" style="width: 600px;"><div class="photocaption"> RON TARVER /Staff Photogapher </div></div> Jay Hancock, KAISER HEALTH NEWS Posted: Monday, February 18, 2013, 3:01 AM Computer mistakes like the one that produced incorrect prescriptions for thousands of Rhode Island patients are probably far more common and dangerous than proponents of electronic medical records believe, says Drexel University's Scot Silverstein. Flawed software at Lifespan hospital group printed orders for low-dose, short-acting pills when patients should have been taking stronger, time-release ones, the Providence-based system disclosed in 2011. Lifespan says nobody was harmed. But Silverstein, a physician and adjunct professor of health-care informatics who is making a name for himself as a strident critic of electronic health records, says the Lifespan breakdown is part of a much larger problem. "We're in the midst of a mania right now" as traditional patient charts are switched to computers, he said in an interview in his Lansdale home. "We know it causes harm, and we don't even know the level of magnitude. That statement alone should be the basis for the greatest of caution and slowing down."</blockquote> In an ethical world, it would be.  Medicine, though, is in the throes of a loss of ethics, as many stories at this site and many others attest to. <blockquote class="tr_bq">Use of electronic medical records is speeding up, thanks to $10 billion and counting in bounties the federal government is paying to caregivers who adopt them. The consensus among government officials and researchers is that computers will cut mistakes and promote efficiency. So 4,000 hospitals have installed or are installing digital records, the Department of Health and Human Services said last month. Seventy percent of doctors surveyed in September by research firm CapSite said they had switched to digital data. But the notion that electronic charts prevent more mistakes than they cause just isn't proven, Silverstein says. Government doesn't require caregivers to report problems, he points out, so many computer-induced mistakes may never surface.</blockquote> The recent ECRI "deep dive" study of "EHR events" (<a href="http://hcrenewal.blogspot.com/2013/02/ecri-institute-pso-uncovers-health.html" target="_blank">link</a>) is just the latest to raise red flags on that point. Even Dr. David Blumenthal, former chair of the Office of the National Health IT Coordinator (ONC) in HHS seems to have <a href="http://hcrenewal.blogspot.com/2010/05/david-blumenthal-on-health-it-safety.html" target="_blank">changed his message</a> about reporting of medical problems. From a Feb. 16, 2013 New York Times article "<a href="http://www.nytimes.com/2013/02/17/sunday-review/the-hip-replacement-case-shows-why-doctors-often-remain-silent.html?_r=0" target="_blank">Doctors Who Don’t Speak Out</a>": <blockquote class="tr_bq">....  TRADITIONALLY, doctors have brought problems to the attention of colleagues by conducting research and publishing their findings in a medical journal. The advantage of that system helps ensure the credibility of study data and protects a researcher from random attack, said Dr. David Blumenthal, the president of the Commonwealth Fund, a group that studies health policy issues. But getting a study published can take a year or two; some Johnson & Johnson consultants did publish studies about the hip’s flaws, but they largely appeared after it had been recalled. Dr. Blumenthal said there was probably a need for more immediate ways for doctors to share their concerns, like forums supported by professional medical organizations. </blockquote> Back to the Inquirer article: <blockquote class="tr_bq">He doesn't discount the potential of digital records to eliminate duplicate scans and alert doctors to drug interactions and unsuspected dangers. But the rush to implementation has produced badly designed products that may be more likely to confound doctors than enlighten them, he says. Electronic health records, Silverstein believes, should be rigorously tested under government supervision before being used in life-and-death situations, much like medical hardware or airplanes.</blockquote> In fact, arguments otherwise are specious.  "Harm to innovation" is the one I've heard most often.  Yet, those proffering such claims cannot point out what aspect of regulation - adherence to GMP's (good manufacturing processes), pre-market safety and quality testing, post-market surveillance, etc. - will "harm innovation."  Indeed, they opine as if innovation in medicine without objective safety and quality checks is a virtue, rather than a potential vice. <blockquote class="tr_bq">Silverstein "is an essential critic of the field," said physician George Lundberg, editor at large for MedPage Today and former editor of the Journal of the American Medical Association. "It's too easy for those of us in medicine to get excessively enthusiastic about things that look like they're going to work out really well. Sometimes we go too far and don't see the downside of things."</blockquote> (Dr. Lundberg mentioned me in Nov. 2011 at MedPage today in a piece entitled "Health IT: Garbage In, Garbage Out" as <a href="http://hcrenewal.blogspot.com/2011/11/george-lundberg-promise-of-health-it.html" target="_blank">here</a>.) The patients - including ourselves and our own family members, I might add - are the ones who pay the price of our hyper-enthusiasm. <blockquote class="tr_bq">... The FDA's Jeffrey Shuren, a neurologist, has said such cases "likely reflect a small percentage of the actual events that do occur."</blockquote> "Tip of the iceberg" were his exact words (<a href="http://hcrenewal.blogspot.com/2010/02/fda-on-health-it-adverse-consequences.html" target="_blank">link</a>). <blockquote class="tr_bq">... At conferences and working from home on the "Health Care Renewal" blog, Silverstein chronicles digital failures and criticizes hospitals in the same dogged way he applied himself to building the 1970s-era Heathkit computers [and amateur radio equipment - ed.] he still keeps in his home, say people who know him. "His message has been consistent": Health IT "provides far less benefit than is claimed by its proponents and opens new, sometimes potent, routes to failure," said Richard I. Cook, a medical error expert at the University of Chicago who sat on a panel examining electronic record safety at the authoritative Institute of Medicine. "No one wants him to be visible. But his message and tone have not wavered."</blockquote> Dr. Cook wrote the lone dissent to milquetoast IOM recommendations on health IT risk - the magnitude of which IOM itself admitted is unknown - in their 2012 report "Health IT and Patient Safety: Building Safer Systems for Better Care" available <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/Patient%20Safety%20and%20Health%20IT%20prepub.pdf" target="_blank">here</a>.  See Appendix E. The last scientific conference at which I chronicled these failures was at the Health Informatics Society of Australia's HIC2012, as a keynote speaker on health IT trust (<a href="http://hcrenewal.blogspot.com/2012/08/my-presentation-to-health-informatics.html" target="_blank">link</a>).  I would have been at HIC2011, to which I had been originally invited, but was helping care for a relative injured by bad health IT at that time.  Her death freed me to travel Down Under in 2012. I have presented at a number of plaintiff attorney's meetings since then, however, such as the American Association for Justice Winter Convention (AAJ, formerly the Trial Lawyer's Association) just last week (<a href="http://www.justicewinterconvention.org/" target="_blank">link</a>).  Trial lawyers don't seem to mind a very direct approach to the issues, unlike many so-called scientists who, as author Michael Crichton once warned (<a href="http://www.goodreads.com/quotes/344539-i-want-to-pause-here-and-talk-about-this-notion" target="_blank">link</a>), seem to believe in "consensus" rather than science. <blockquote class="tr_bq"> The HIMSS Electronic Health Record Association, an industry group, declined to comment on Silverstein. A spokesman for the Office of the National Coordinator for Health Information Technology, the administration's proponent of digital records, said: "It's important to listen to all the voices" in the discussion of the subject.  </blockquote> Some voices, unfortunately, are louder than others and backed by lobbyists and big money.  See, for instance, the May 2009 Washington Post article by Robert O'Harrow Jr. "The Machinery Behind Health-Care Reform: How an Industry Lobby Scored a Swift, Unexpected Victory by Channeling Billions to Electronic Records" (link to the article and my essay about it is <a href="http://hcrenewal.blogspot.com/2009/05/machinery-behind-healthcare-reform-how.html" target="_blank">here</a>). I do point out, however, for the benefit of those at HIMSS and ONC, that knowing of risks, while doing nothing substantive while "listening to all voices in the discussion" can be seen as gross negligence. <blockquote class="tr_bq">Trained as an internist and in medical information technology [Medical Informatics- ed.] as a Yale University postdoc, Silverstein, 55, served as Merck & Co.'s director of scientific information in the early 2000s and then as a full-time Drexel professor, shifting in recent years to part-time teaching and working on medical liability cases for plaintiff attorneys. His insistent warnings about digital health risks over more than a decade have effectively barred him from a lucrative career at a hospital or software vendor.</blockquote> Perverse as that reality may be, it's also the reverse:  I would not want to work for a hospital or software vendor in 2013, where effecting change to protect patients from bad health IT is hard if not impossible, e.g., as at <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=lawsuit" target="_blank">link</a>, <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=clinical%20computing%20problems%20in%20ICU" target="_blank">link</a>, and <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story" target="_blank">link</a>, and at the other case examples at that site.  I find it a far more effective use of my time to help enact change from the outside - and avoiding the pathological individuals who make such scenarios possible. <blockquote class="tr_bq">"I'm sure Scot would be better off by keeping his mouth shut and getting a job with a hospital that's just put in a big . . . system," said Matthew Holt, a Silverstein critic and cochairman of Health 2.0, which organizes health technology conferences.</blockquote> I note that the raison d'être for this blog is the impact of many people doing just that sort of thing - "keeping their mouth shut" and making money, no matter what the ethical implications.  (The patients killed by such behaviors are, unfortunately, unavailable for comment.) <blockquote class="tr_bq"> Many say he comes on too strong. Even admirers cringed when he began blogging about the 2011 death of his mother, which he blames in a lawsuit on a computer error that allegedly caused Abington Memorial Hospital to overlook a key medication. (Both he and the hospital said they couldn't comment on a pending suit.) Personalizing his campaign, some thought, made him seem less objective.</blockquote> I'm at a loss here.  "Too strong" - on matters of life and death that affect everyone?  A proficient writer, who had been writing about health IT problems since 1998, should have kept silent about a first hand story of HIT harm in 2010 of potential great relevance towards public safety?  Writing about the incident 'lessens objectivity'?  That makes little sense, and is perverse.  Those who opined as such have their priorities in serious disarray. Such personalized accounts are common and have caused great change.  <a href="http://en.wikipedia.org/wiki/Libby_Zion_law" target="_blank">Libby Zion's death</a> due to hospital neglect, and her father's making the issues quite public, comes to mind, as do the many laws enacted that are named after people who've gone public after personal tragedy: <blockquote class="tr_bq">... Grieving the loss of their child, Zion's parents became convinced that their daughter's death was due to inadequate staffing at the teaching hospital.  Sidney Zion questioned the staff's competence for two reasons. The first was the administration of meperidine, known to cause fatal interactions with phenelzine, the antidepressant that Libby Zion was taking. The second issue was the use of restraints and emergency psychiatric medication. Sidney's aggrieved words were: "They gave her a drug that was destined to kill her, then ignored her except to tie her down like a dog." To the distress of the doctors, Zion began to refer to his daughter's death as a "murder." Sidney also questioned the long hours that residents worked at the time. In a New York Times op-ed piece he wrote: "You don't need kindergarten to know that a resident working a 36-hour shift is in no condition to make any kind of judgment call—forget about life-and-death." The case eventually became a protracted high-profile legal battle, with multiple abrupt reversals; case reports about it appeared in major medical journals.</blockquote> An alternate explanation is that, lacking other credible means, this is an ad hominem reaction (of those "some") seeking an angle to attack the message ... and the messenger ... or is simply a reaction of, to put it bluntly, castrati who are more at home in a country club than in the world of ideas. For a bona fide example of "coming on too strong", there's this: <div class="PlainText">In the NEJM article "The 'Meaningful Use' Regulation for Electronic Health Records", David Blumenthal, M.D., M.P.P. (ONC Chair) and Marilyn Tavenner, R.N., M.H.A. (10.1056/NEJMp1006114, July 13, 2010) available <a href="http://healthcarereform.nejm.org/?p=3732&query=home">at this link</a>, the opening statement is (emphases mine): </div><blockquote dir="ltr" style="margin-right: 0px;"><div class="PlainText">The widespread use of electronic health records (EHRs) in the United States is inevitable. EHRs will improve caregivers’ decisions and patients’ outcomes. Once patients experience the benefits of this technology, they will demand nothing less from their providers. Hundreds of thousands of physicians have already seen these benefits in their clinical practice.</div></blockquote><div class="PlainText"> I think it fair to say those are grandiose statements and predictions presented with a tone of utmost certainty in one of the world's most respected scientific medical journals.  Even though it is a "perspectives" article, I once long ago learned that in writing in esteemed scientific journals of worldwide impact, statements of certainty were at best avoided, or if made should be exceptionally well referenced. I note the lack of footnotes showing the source(s) of these statements. Another bona fide example of "coming on too strong": <blockquote class="tr_bq">“We have the capacity to transform health with one thunderous click of a mouse after another,” said (former) HHS Secretary Michael Leavitt - <a href="http://www.himss.org/ASP/ContentRedirector.asp?ContentId=65039&type=HIMSSNewsItem">2005 HIMSS Summit</a> </blockquote> <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/AVvXsEi81rMzS-WFiPrb91_Guccc9_kcbOUplIvRl6eAqyOYRwvsQoibE1PA5rhERJ-q54ZC1TCcdeuJH1o7Ecm_5F5wI4yqIzw4j7xvllLz7pS9-fYIc6we-mJokTLmpLZsggAjGOMJS-veYpb3/s1600/lightning.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi81rMzS-WFiPrb91_Guccc9_kcbOUplIvRl6eAqyOYRwvsQoibE1PA5rhERJ-q54ZC1TCcdeuJH1o7Ecm_5F5wI4yqIzw4j7xvllLz7pS9-fYIc6we-mJokTLmpLZsggAjGOMJS-veYpb3/s1600/lightning.jpg" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">We shall transform health (into what, exactly, is not specified) one thunderous mouse click after another!</td></tr></tbody></table></div> It doesn't get any stronger than that, unless, perhaps, the thunderous wrath of God is invoked. Back to the Inquirer once again: <blockquote class="tr_bq">"His refusal to temper his message makes it sometimes difficult to hear," said Ross Koppel, a University of Pennsylvania sociologist and digital health record skeptic.</blockquote> As per a recent article by Joe Conn in Modern Healthcare entitled "Health IT Iconoclasts" (<a href="http://hcrenewal.blogspot.com/2013/02/modern-healthcare-health-it-iconoclasts.html" target="_blank">link</a>), which wrote of Dr. Koppel, Deborah Peel, Lawrence Weed and me, Dr. Koppel has firsthand experience at his message being found "difficult to hear" by the hyper-enthusiasts: <blockquote class="tr_bq">... Researcher Ross Koppel started an uproar in 2005 when he and a colleague coauthored an article in the Journal of the American Medical Association that found a first-generation computerized physician order entry system (CPOE) at the Hospital of the University of Pennsylvania was simultaneously creating new errors even as it reduced others. Koppel’s bombshell—he’s now an adjunct professor of sociology at the University of Pennsylvania— brought down the wrath of information technology boosters. The Healthcare Information and Management Systems Society, a health IT trade group, challenged the study’s “methodology and its subsequent outcomes,” and criticized its authors for their “limited view” and not “looking at the big picture.”  [Others wrote that his work was 'disingenuous', although it had similar findings to my own observation of the very same CPOE system at Yale-New Haven Hospital ... in 1992 - ed.] ... In 2009, he revealed in another JAMA article that health IT vendors’ contracts included “hold harmless” clauses that shielded software developers from legal liability for medical errors their systems caused, even if the developers had been warned about the defects. “That got me major upheaval,” the worst of his career, Koppel recalls.</blockquote> Koppel, a sociologist, has probably done more for health IT transparency and safety than the physicians of the entire academic medical and medical informatics community combined. <blockquote class="tr_bq">... But Silverstein says his position today is the same as it has always been. He believes in the potential power of electronic records for good, he says. But any doctor who feels bound by the Hippocratic oath's injunction to "first, do no harm," he adds, should balk at what's going on. "Patients are being harmed and killed as a result of disruptions to care caused by bad health IT," he said. "I'm skeptical of the manner and pace" of implementation, "not of the technology itself. . . . My only bias is against bad medicine. And my bias is against people with complacent attitudes about bad medicine."</blockquote> The issues are actually relatively simple, using terminology coined by <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGiHKiF08nosKVU7uTAYFAuZg0tzy09D_tVjFrfb2sJmv6LrJlm_Pv-vazJeH5joFN8HbBEAGFJRgS9EIIr5grSxultREvX8Uycje6Tgf0cYzN6BfLqgbHbKFxor9o14guSy_qimQdUwou/s1600/jon_IMG_1038a.jpg" target="_blank">Dr. Jon Patrick of U. Sydney</a> at the aforementioned HIC2012 meeting in Australia during our discussions.  Bad health IT must be removed from the market, and good health IT must replace it. <blockquote class="tr_bq">Good Health IT ("GHIT") is defined as IT that provides a good user experience, enhances cognitive function, puts essential information as effortlessly as possible into the physician’s hands, keeps eHealth information secure, protects patient privacy and facilitates better practice of medicine and better outcomes. Bad Health IT ("BHIT") is defined as IT that is ill-suited to purpose, hard to use, 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>   It is this author's opinion that this change will not happen by "going along to get along" or "listening to all the voices in the discussion of the subject" (especially those with Big Money and Big Lobbyists behind them) while doing nothing. I also note that "complacent attitudes about bad medicine" are not the sole province of IT personnel or healthcare management.  Physicians and nurses who acquiesce to bad health IT are part of the problem. -- SS

Kaiser Health News/Philadelphia Inquirer on InformaticsMD: "The flaws of electronic records"

At my Dec. 2012 post "How an interview for Kaiser Health News rekindled memories of health IT dysfunction in the 90's that persist in the 10's" I mentioned an interview by a reporter from the Kaiser H…

Đọc thêm »

18 Feb 2013

How an interview for Kaiser Health News rekindled memories of health IT dysfunction in the 90's that persist in the 10's

I was interviewed in my home yesterday by Jay Hancock, Senior Correspondent, <a href="http://www.kaiserhealthnews.org/About.aspx" target="_blank">Kaiser Health News</a> about my background, how I got to the current point in my Healthcare Informatics career, my opinions on the state of health IT in 2012, and related matters for a possible article: <blockquote class="tr_bq">Kaiser Health News (KHN) is a nonprofit news organization committed to in-depth coverage of health care policy and politics. KHN’s mission is to provide high-quality coverage of health policy issues and developments at the federal and state levels. In addition, KHN covers trends in the delivery of health care and in the marketplace. KHN is an editorially-independent program of the <a href="http://www.kff.org/" shape="rect" target="_blank">Kaiser Family Foundation</a>, a non-profit private operating foundation, based in Menlo Park, Calif., dedicated to producing and communicating the best possible analysis and information on health issues. </blockquote> Mr. Hancock has quoted me regarding health IT in the past in his current role and when he was a reporter for the Baltimore Sun, for instance in the April 2012 article "<a href="http://www.washingtonpost.com/health-insurance-companies-push-to-diversify-raises-concerns/2012/04/27/gIQAWoSkoT_story.html" target="_blank">Health insurers’ push to diversify raises ethical concerns</a>" that appeared in the Washington Post as well, and the Nov. 2011 article "<a href="http://weblogs.baltimoresun.com/business/hancock/blog/2011/11/advice_to_hospitals_be_careful.html" target="_blank">Advice to hospitals: Be careful what you bill for</a>" in the Baltimore Sun. Mr. Hancock wanted to get an understanding of me, the person.  In doing so, I dug out some of my past technology "toys" to show him at the onset of the interview.  Ironically, doing so reminded me of some irritating occurrences in the past that both inform present views, and served as early experiences in why health IT suffers the problems it does. I will illustrate by showing some of the devices I presented to Mr. Hancock in order for him to better know my interests/knowledge of technology, and then presenting the unpleasant recollections that doing so brought on. Bear with me for a few moments (and pictures). I showed Mr. Hancock devices I'd built and/or used in teaching such as (click to enlarge): <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/AVvXsEhNI2bBd1cOfE5MXq_R7FhoDuqo7tsA0MIEZM-DFZRq2L_RF0nbjYKfMTqCbBLXMf05XS_DIX3LXnmrJC14UHPKHVGxIqkzRF_p0dJtjzyaXY4Ku6kswyTxr4uM62C-SoiTDDjY3RX_XHqE/s1600/monitor.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="184" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhNI2bBd1cOfE5MXq_R7FhoDuqo7tsA0MIEZM-DFZRq2L_RF0nbjYKfMTqCbBLXMf05XS_DIX3LXnmrJC14UHPKHVGxIqkzRF_p0dJtjzyaXY4Ku6kswyTxr4uM62C-SoiTDDjY3RX_XHqE/s1600/monitor.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">An infrared-sensing heart monitor I built in 1980 during a clerkship in biomedical engineering, Boston University Hospital, 1980</td></tr></tbody></table> <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/AVvXsEjLRMslJ-L6uo5Up8v3f8gW6Tpn1DsKPohhPgjvkTPgXFzTIiBvxK4QWY04-9OZAPrwntaxdyaXc3FpVl_eBpxroWG5Pbjs1u0pi9D_3uU0e6N2bsn44mmgGA3GlflHNkoBoRJWSjK3E_ET/s1600/monitor_inside.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="264" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLRMslJ-L6uo5Up8v3f8gW6Tpn1DsKPohhPgjvkTPgXFzTIiBvxK4QWY04-9OZAPrwntaxdyaXc3FpVl_eBpxroWG5Pbjs1u0pi9D_3uU0e6N2bsn44mmgGA3GlflHNkoBoRJWSjK3E_ET/s1600/monitor_inside.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">Inside the heart monitor.  I etched and drilled the printed circuit boards myself.</td><td class="tr-caption" style="text-align: center;"></td><td class="tr-caption" style="text-align: center;"></td></tr></tbody></table> <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/AVvXsEjfaQ4LIqHZqETVHyBYLKV7nBObQVnYUWtTMyFPyCPsLa0TFUf7OPEyf3-MsobysGudPtzn-AikRxWl0IQF8mB_TPCoCWMEmHpu_WNA-6MKmEy2HZhMrPq1Ws_5mAQkjl5Vhi5uM9RwHF3N/s1600/pbox.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="264" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfaQ4LIqHZqETVHyBYLKV7nBObQVnYUWtTMyFPyCPsLa0TFUf7OPEyf3-MsobysGudPtzn-AikRxWl0IQF8mB_TPCoCWMEmHpu_WNA-6MKmEy2HZhMrPq1Ws_5mAQkjl5Vhi5uM9RwHF3N/s320/pbox.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">A 3-transistor breadboard shortwave radio I built as a kid.</td></tr></tbody></table> <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/AVvXsEhRBkW3a2lwQrI8Z1iqGOfk9HVmZYLs3atqSj2DqdhEAzgtbr11HcMJQ0UkAQuradR-gr4UeEQk1GcJDAnwyAxgC9PbIwQknRZtk7mnjajZDhoS7AnABcvRkc-EzIfRrIeVxrv0ereDyMJx/s1600/hw101.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="201" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRBkW3a2lwQrI8Z1iqGOfk9HVmZYLs3atqSj2DqdhEAzgtbr11HcMJQ0UkAQuradR-gr4UeEQk1GcJDAnwyAxgC9PbIwQknRZtk7mnjajZDhoS7AnABcvRkc-EzIfRrIeVxrv0ereDyMJx/s1600/hw101.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">A somewhat more sophisticated radio kit.  My Heathkit HW-101 ham radio transceiver, built myself over several months when I was a medical trainee.  Also built its matching power supply box, not shown.</td></tr></tbody></table> <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/AVvXsEioHh-zMYfMv-DtCyWAxE4DsLkBTmP_l0mLMs4LSgcj90n_y6IplsjDBkyE5fFqKU7VaFeMbqzJf9r1R_TLMwZoUbeDVh-5PogmI3F1rJugTWpJcDwqRi_bzsz37ZnkqPL4sp6xJSA9sjxc/s1600/hw101_inside.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="275" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEioHh-zMYfMv-DtCyWAxE4DsLkBTmP_l0mLMs4LSgcj90n_y6IplsjDBkyE5fFqKU7VaFeMbqzJf9r1R_TLMwZoUbeDVh-5PogmI3F1rJugTWpJcDwqRi_bzsz37ZnkqPL4sp6xJSA9sjxc/s1600/hw101_inside.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">HW-101 innards, top view.  Not exactly a simple device.</td></tr></tbody></table> <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/AVvXsEjMqX4MYZmY9Ir7PY_5ldAliBxLTsZaW_yERtsdfCgBKjFsTz04ptod_hZCir8n3L_GUh8EohaUfULwL7KGBc-PHpXtCFqlmDQHDvHnupKdFuvctFnTx0_2Ue6kktj9iodAFpu42cdWhvpY/s1600/hw101_under.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMqX4MYZmY9Ir7PY_5ldAliBxLTsZaW_yERtsdfCgBKjFsTz04ptod_hZCir8n3L_GUh8EohaUfULwL7KGBc-PHpXtCFqlmDQHDvHnupKdFuvctFnTx0_2Ue6kktj9iodAFpu42cdWhvpY/s1600/hw101_under.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">HW-101 underside of chassis.  Each and every one of those solder connections was done by me.  In bulding it, I learned how each circuit worked (and had to debug it when, on initial powerup, smoke rose due to a defective ceramic capacitor and two bad tubes, one of which glowed a delightful cherry-red.)</td></tr></tbody></table> <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/AVvXsEhxcE0GYwocATWczjbtZGBlKniF-7aPALWsis0MBi5u__4pa_VHxmCing_cd6seWbzIamDdbGL2CiAb957sOGYa2nPSKlt1COjY6apzsvGBinI_W8_jq3deMH0X-mlX_LisIeDZlwzOMtBm/s1600/h8.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="194" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxcE0GYwocATWczjbtZGBlKniF-7aPALWsis0MBi5u__4pa_VHxmCing_cd6seWbzIamDdbGL2CiAb957sOGYa2nPSKlt1COjY6apzsvGBinI_W8_jq3deMH0X-mlX_LisIeDZlwzOMtBm/s1600/h8.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">My Heathkit H8 computer, introduced 1977.  Intel 8080 processor. One of the first personal computers.  In true minicomputer style, the 8080 general registers, accumulator/flags register, program counter, stack pointer, and memory addresses were directly accessible via the front panel pushbuttons and the split-octal display.</td></tr></tbody></table> <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/AVvXsEjHGHE5EygfpJBKVtX14fYUUJfIBoAfLSl2qS0MnTelvSda98KbpWW7dgdhroNFhb12xExI1UQssJ9La2gOfpse1R4TrbQSAPkOCfLdcmzZdrMkQgnbzLH5xn0v7R0O1F3ZUqFeDd_KR7yN/s1600/h8_inside.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="251" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjHGHE5EygfpJBKVtX14fYUUJfIBoAfLSl2qS0MnTelvSda98KbpWW7dgdhroNFhb12xExI1UQssJ9La2gOfpse1R4TrbQSAPkOCfLdcmzZdrMkQgnbzLH5xn0v7R0O1F3ZUqFeDd_KR7yN/s1600/h8_inside.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">Inside the H8.  I used this to teach computer and CPU architecture to Medical Informatics  postdoctoral fellows at Yale School of Medicine.  I did not, and do not believe healthcare IT leaders should be mere “appliance operators.” </td></tr></tbody></table> <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/AVvXsEiaQg4SB7pJYQ5Qdi4e4ld8PE41FFf2XnL-l8kA0woZYT5-WCgiS7yayoTWkekfcNI91YlDZDecsp2FTk6sWrQ030m7RDX8CVoNVLS9EOgHCgZO0X3Z6eEOXpm4t93HVe7HUstW4GhetGce/s1600/vtos.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="249" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaQg4SB7pJYQ5Qdi4e4ld8PE41FFf2XnL-l8kA0woZYT5-WCgiS7yayoTWkekfcNI91YlDZDecsp2FTk6sWrQ030m7RDX8CVoNVLS9EOgHCgZO0X3Z6eEOXpm4t93HVe7HUstW4GhetGce/s1600/vtos.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">My TRS-80 Model I running VTOS 4.0, a pre-IBM PC precursor to LDOS 5 and TRSDOS 6.  All were far superior to MS-DOS of any flavor in my opinion.</td></tr></tbody></table> <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/AVvXsEhm2GpffAVXmQfo1n78BVq860ijo7GEmRcNpAb9ZX4p80_nuN3399P32r8UOg40-BBBGcwLMZbLsVb79GUGLdApiKm1vSN_zkt8rWuzBN0L7xjmJhLK2hYSnqmsbKu3gbCQL-PI96d60zY1/s1600/trs80_fix.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="244" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhm2GpffAVXmQfo1n78BVq860ijo7GEmRcNpAb9ZX4p80_nuN3399P32r8UOg40-BBBGcwLMZbLsVb79GUGLdApiKm1vSN_zkt8rWuzBN0L7xjmJhLK2hYSnqmsbKu3gbCQL-PI96d60zY1/s1600/trs80_fix.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">TRS-80 Model I about to undergo repair by me.</td></tr></tbody></table> As I mentioned before the pictures, unpacking from their storage boxes and showing this personal technology brought out numerous formative memories, and not always good ones, from my CMIO (Chief Medical Informatics Officer) days. Seeing all this, it may be easier to imagine why, as a CMIO in the mid 1990's I was offended when patronized by hospital IT personnel about how an information system  in an invasive cardiology cathlab, a critical care area, could not be moved from unstable Windows 3.1 to Windows NT to prevent frequent crashes and data loss because “Windows NT needed RAID disk arrays” and other B.S., and also by similar personnel patronizing me on my serious concerns about ICU patients put at risk of infection by improper hardware for a biohazard-prone environment.  (See <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story">http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story</a> and <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=clinical%20computing%20problems%20in%20ICU">http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=clinical%20computing%20problems%20in%20ICU</a>.) I was further reminded about how I was alarmed by the selfsame hospital IT "experts", lacking healthcare and medical informatics knowledge and experience, simply ignoring my counsel, as if medicine was a harmless parlor game to be played, winner take all.  And likewise regarding hospital senior management who's hired me in the first place - at least one of whom expressed to me more concern for the career advancement of the IT staff than for patient safety. The latter ICU incident, in fact, directly led to my starting to write about health IT issues on the Web in 1998.  Sadly, my colleagues, as well as former students and mentees, tell me little has changed. That type of territorial, political behavior might perhaps be more appropriate (or at least hardly harmful) in a nail salon or pizza parlor, but not in an ICU or cardiac cath lab. Yet today's health IT domain is rife with leadership by health IT amateurs** [see note below] who patronize, bully and play nasty politics with healthcare informatics-educated clinicians and specialists, and accuse clinicians of being "Luddites" for resisting <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/" target="_blank">bad health IT</a> pushed on them by hyperenthusiasts (<a href="http://hcrenewal.blogspot.com/2012/03/doctors-and-ehrs-reframing-modernists-v.html" target="_blank">Ddulites</a>) who ignore the downsides.   <blockquote class="tr_bq">Good Health IT ("GHIT") is defined as IT that provides a good user experience, enhances cognitive function, puts essential information as effortlessly as possible into the physician’s hands, keeps eHealthinformation secure, protects patient privacy and facilitates better practice of medicine and better outcomes.  Bad Health IT ("BHIT") is defined as IT that is ill-suited to purpose, hard to use, 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> What is lost in these dysfunctional dynamics is that the true "customer" who suffers is the patient.  Patients come to the hospital sick and with expectations that the personnel there will put the patients' interests first.  If they are injured or leave in a pine box, they care little about whose political empires were threatened by internecine and/or industry battles over IT. Mr. Hancock's Kaiser Health News profile of me, if published, should prove interesting.   It will probably mention my own relative's injury and death related to health IT, and may cite the Complaint itself, a public document.   I will link to it when it if and when it appears. -- SS ** (Amateur, used in the same sense that I am a <a href="http://www.arrl.org/" target="_blank">radio amateur</a> licensed by the government after a series of written exams, but not a professional telecommunications engineer, knowing I would not want to, nor should be allowed to, lead a mission critical telecommunications project.) ----------------------- Feb. 18, 2013 Addendum: The article was published as <a href="http://hcrenewal.blogspot.com/2013/02/kaiser-health-newsphiladelphia-inquirer.html" target="_blank">here</a>. -- SS

How an interview for Kaiser Health News rekindled memories of health IT dysfunction in the 90's that persist in the 10's

I was interviewed in my home yesterday by Jay Hancock, Senior Correspondent, Kaiser Health News about my background, how I got to the current point in my Healthcare Informatics career, my opinions on …

Đọc thêm »

06 Dec 2012

Load more posts