healthy4u

On an EMR Forensic Evaluation by Professor Jon Patrick from Down Under: More Thoughts.

<div style="text-align: center;">Note: the reports to which this post refers are available as a set of PDF's from the University of Sydney, NSW, Australia <a style="font-style: italic;" href="http://www.it.usyd.edu.au/%7Ehitru/essays/Study%20of%20Enterprise%20Health%20IS%20-%20Parts%200-9%20PDF-ARCHIVE.zip">at this link</a> (12 Mb, .zip folder), or at "A study of an Enterprise Health information System" at <a href="http://sydney.edu.au/engineering/it/%7Ehitru/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>. <div style="text-align: center;">March 6, 2011 addendum. Also see my new post "<a style="font-style: italic;" href="http://hcrenewal.blogspot.com/2011/03/what-to-do-about-state-of-ed-ehr-in-nsw.html">What to do about the state of the ED EHR in NSW?</a>" </div></div> Over ten years ago now, 1999 in fact, I started my healthcare IT difficulties website. That site, "Contemporary Issues in Medical Informatics: Common Examples of Healthcare Information Technology Difficulties" now resides on a Drexel University server in Philadelphia, Pennsylvania USA <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/">at this link</a>, and used as a teaching resource. I started the site after observing, for lack of a better description, "crazy stuff" in the commercial healthcare information technology sector. Crazy stuff such as EMR systems for ICU's that <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=clinical%20computing%20problems%20in%20ICU">crashed regularly and spread pathogens around</a>, EMR's for invasive cardiology cath labs <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story">that were an informational jumble and abyss and that also issued regular General Protection Faults and died</a>, lack of Medical Informatics expertise (and actual disdain for it) in healthcare IT projects, grossly incompetent IT leaders, and hospitals uncritically and enthusiastically buying these products as if they were a plug and play, proven technology. To make matters worse, I also observed executives expressing a hostile indifference to glaring deficiencies. My observations about health IT and about responses to my counsel brought to mind the biblical passage: <blockquote>"Give not that which is holy unto the dogs, neither cast ye your pearls before swine, lest they trample them under their feet, and turn again and rend you." - Matthew 7:6 </blockquote> I was never afforded the opportunity to perform a forensic analysis of the internals of these systems, being that I was not allowed to obtain the software or "schematics" of the data structures. In fact, to make the cardiology system usable, I ordered the IT staff to simply discard the internal data dictionary, relational data structures, input screens, and analytic routines, and rebuild them - from scratch - using a proper Medical Informatics-based, cardiology domain expert-driven, iterative and incremental (agile) approach. The result was a resounding success, and was described in a written report as "exceptional" by national specialty association reviewers invited to evaluate the effort. (A success for which, I might add, I and my enlightened executive sponsor <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story">were paradoxically demonized by the IT department and hospital executives</a>; cf. Matthew 7:6.) Now, an Australian researcher of considerable computer and database expertise, <a href="http://sydney.edu.au/engineering/it/%7Ejonpat/">Professor Jon Patrick</a> at the University of Sydney, has put considerable ink to a forensic evaluation of the internals and external reactions to an EMR system "built in America", Cerner Firstnet. Professor Patrick holds a Ph.D. from Monash University. He came to the University of Sydney from Massey University, New Zealand, where he held the foundation Chair of Information Systems. Professor Patrick won Australia's national Eureka science prize in 2005 for developing a natural language processing system that detected financial scams in web pages at the behest of the Australian Government. FirstNet is an ED EHR that government officials decided must be installed in ED's of public hospitals throughout the Australian state of New South Wales. Promo material below, click to enlarge: <div style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWv3btAUsn_Umf2ZFMjq6HXIZ6BgHxlc835DJCPhyBPJzoY8PVpBuM_w6id8ohYVEfHWPPvBvQWjowc_kQWlqenx4WezZU_6sWBRcil-j5bO9RUr-N9MOP3r3X0GgM2qAiR_vQu73S2rl5/s1600/p1.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5580655476444502130" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWv3btAUsn_Umf2ZFMjq6HXIZ6BgHxlc835DJCPhyBPJzoY8PVpBuM_w6id8ohYVEfHWPPvBvQWjowc_kQWlqenx4WezZU_6sWBRcil-j5bO9RUr-N9MOP3r3X0GgM2qAiR_vQu73S2rl5/s320/p1.png" style="display: block; margin: 0px auto 10px; width: 247px; cursor: pointer; height: 320px; text-align: center;" /></a>FirstNet promo material, page 1. Click to enlarge. (Hmm ... Is there a subliminal message in the picture of the doctor and nurse?) </div><div style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtd0yVxqvX4M2SebLq7XUMfF-4lum_lGcfgEsmXc75o6s4INr4HJfRIFh7YZPdlj1RqedKjnVVNjIbTvFIZCbybSvpWGIYDV8dqMZf8NqC1c3vDe14bEjjvq-oZeN3R3SOoGA2mTH7ZC1N/s1600/p2.png"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5580655538113430082" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtd0yVxqvX4M2SebLq7XUMfF-4lum_lGcfgEsmXc75o6s4INr4HJfRIFh7YZPdlj1RqedKjnVVNjIbTvFIZCbybSvpWGIYDV8dqMZf8NqC1c3vDe14bEjjvq-oZeN3R3SOoGA2mTH7ZC1N/s320/p2.png" style="display: block; margin: 0px auto 10px; width: 247px; cursor: pointer; height: 320px; text-align: center;" /></a>FirstNet Promo material, page 2. Click to enlarge. </div> The initiative's been underway for several years, and the result is a group of apparently very unhappy Wal-Mart shoppers. (I guess the correct line would be "unhappy <a href="http://en.wikipedia.org/wiki/Big_W">Big W</a> shoppers" for those Down Under.) Prof. Patrick had written a preliminary essay on the issue entitled, in rhetorical question-style, "The Story of the Deployment of an ED Clinical Information System: Systemic Failure or Bad Luck?" back in 2009. He apparently found himself in considerable hot water for doing so due to 'pushback' as I described at "<a href="http://hcrenewal.blogspot.com/2009/11/academic-freedom-and-ed-ehrs-down-under.html">Academic Freedom and ED EHR's Down Under: An Update</a>". However, his university stood by him in defense of academic freedom (and of the sanctity of those in the healing arts, I might add). He's spent the intervening time expanding the analysis of the ED clinical system and its deployment considerably, right down to the fine nuances of relational database design in complex domains (such as biomedicine). As I wrote in an initial post "<a href="http://hcrenewal.blogspot.com/2011/03/study-of-enterprise-health-information.html">A Study of an Enterprise Health information System - Finally, an Informatics Scientist Does A Rigorous Review of a Commercial EHR System, by Cerner</a>", the TOC of his new analysis are these (the files are available as a .zip archive <a href="http://www.it.usyd.edu.au/%7Ehitru/essays/Study%20of%20Enterprise%20Health%20IS%20-%20Parts%200-9%20PDF-ARCHIVE.zip">at this link</a>): <blockquote>3.0 Part 0 - Executive Summary 3.1 Part 1 - A Critical Essay on the Deployment of an ED Clinical Information System ‐ Systemic Failure or Bad Luck? First published here in Oct 2009, revised Dec 2009. 3.2 Part 2 - Discussions with ED Directors: Are we on the right track? 3.3 Part 3 - Discussions with Software Performance Experts. 3.4 Part 4 - Conceptual Data Modelling. 3.5 Part 5 - Database Relational Schema and Data Tables. 3.6 Part 6 - Coalescing the Analyses of the ER Diagrams, Relational Schemata and Data Tables. 3.7 Part 7 - The Integrated Assessment. 3.8 Part 8 - Future HIT Regulation Proposals. 3.9 Part 9 - Ockham's Razor of Design. Published at the IHI conference, Nov 2010 Washington.</blockquote> I have been reading these sections, and have found the technical sections (parts 4-6) highly informative about a major suspicion I've held for many years. I suspected chaos in the health care IT software engineering process, with inadequate attention to quality, rigor, fine detail, resilience engineering, talent management and other practices essential in development of mission critical products of any type. Prof. Patrick's forensic analysis, while not proof of my concerns, certainly supports them. If Boeing produced aircraft with malfunctioning engines, broken seats, defective flaps, tires that blew on landing, and rust right out of the factory (like the Chevy Vega of old?), one might suspect the development and manufacturing environment could be substantially problematic. The theme of apparent violations of fundamental precepts of relational database design run consistently through his analysis of the FirstNet product. Without getting too technical (which I can, having written successful <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/medinformatic1/saudi.htm">r</a><a href="http://www.ischool.drexel.edu/faculty/ssilverstein/medinformatic1/saudi.htm">elational database-based clinical information systems</a> of considerable complexity for challenging environments, with novel user interaction design besides), I see evidence of developmental chaos. Examples: primary key-foreign key inconsistencies and problematic usages ("keys" are flags used to link sets of information about some object or entity, such as a patient to their diagnoses or meds), internal field nomenclature faux pas (there are best practices on how to do this to enhance software quality and maintenance), cryptic documentation , "stale bits" (old code and data) from past iterations remaining to create "glitches", unreliabilities and new problems, and other technical sins apparently abound. These can be read about in sections 4-6 of Prof. Patrick's analysis. The issues can be summarized as he did in the part 6 Abstract: <blockquote> Consistent weaknesses in sections of the Millenium clinical information System (CIS) are revealed in the combined study of the ERD (entity-relationship diagram), logical schema and the data tables. PK (primary key, i.e., unique identifier) values are not always defined unambiguously at the design level and data tables reveal inconsistencies in declarations and data validation. There is evidence that keys are managed by software within the application rather than by the in-built functions available in the database management system leading to less confidence in data integrity. </blockquote>He goes on to relate: <blockquote> The [technical design] weaknesses in terms of clinical work practices, that have been identified are only likely to show up in occasional circumstances with a combination of processing and data values separated in time. [In other words, the resulting errors are unpredictable, and depend on variable factors about the patient's data and user's attempted actions that cannot be predicted ahead of time - ed.] Staff are not likely to associate one instance of missing or mis-processed data with another. This spasmodic nature tends to lull staff into a false sense of security that the mis-processing is either inconsequential or an accident of their own making. We recommend that each and every mis-processing experience be recorded as accurately as possible so that appropriate computational forensic analysis can correctly identify if weaknesses in the underlying technology have been the source. </blockquote> These are dead-serious matters, literally. One's well being in an ED should not depend on random chance. If you are the "lucky patient" who Wins the Lottery or Hits the Jackpot on health IT mis-processing, or whose clinicians are distracted by user experience flaws, "workarounds", demoralization or other issues, you might end up maimed - or in the grave. <div style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZ20IJBLu5ePEUKL0bwFA8RSyWPjKFQDm5YHVAcwwbU_9imWz6YVp8pp8QbDpSEoZ1F4TNzVfWia13tgGqFCynsMZviaTQuc2D5QfIgw7u_KsQnbWrPUU3qzkI-r72Grz7kp4Fm32KkBqA/s1600/winner.jpg"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5580994204237950722" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZ20IJBLu5ePEUKL0bwFA8RSyWPjKFQDm5YHVAcwwbU_9imWz6YVp8pp8QbDpSEoZ1F4TNzVfWia13tgGqFCynsMZviaTQuc2D5QfIgw7u_KsQnbWrPUU3qzkI-r72Grz7kp4Fm32KkBqA/s320/winner.jpg" style="display: block; margin: 0px auto 10px; text-align: center; cursor: pointer; width: 360px; height: 270px;" /></a>The ED EHR Slot Machine. Click to enlarge. You've hit the ED EHR mis-processing jackpot! Perhaps today is a good day to die... </div> I do not believe mission critical software for, say, avionics, or for implantable medical devices, suffers such sloppiness. (In part due to regulation, which health IT lacks entirely in the U.S.). The UK, having their own HIT issues (see my Aug. 2010 "Battle of Britain" post <a href="http://hcrenewal.blogspot.com/2010/08/cerners-blitzkrieg-on-london-wheres-raf.html">at this link</a>), apparently learned something, as evidenced in: <a href="http://www.connectingforhealth.nhs.uk/engagement/clinical/occo/safety/dscn18.pdf"></a><blockquote><a href="http://www.connectingforhealth.nhs.uk/engagement/clinical/occo/safety/dscn18.pdf">Health informatics — Guidance on the management of clinical risk relating to the deployment and use of health software</a>. UK National Health Service, DSCN18 (2009), formerly ISO/TR 29322:2008(E). and <a href="http://www.connectingforhealth.nhs.uk/engagement/clinical/occo/safety/dscn14.pdf">Health Informatics — Application of clinical risk management to the manufacture of health software</a>. UK National Health Service, DSCN14 (2009), formerly ISO/TS 29321:2008(E).</blockquote> That said, I will now comment in more detail on a part of the analysis readily understandable by 'database laypeople': part 2, "Discussions with ED Directors: Are we on the right track?" (again, probably a rhetorical question). In this section, candid discussions were held with the Directors of seven Emergency Departments in New South Wales public hospitals assessing the impact of the introduction of the FirstNet information system into their ED's. The effort has been ongoing for approximately the last 5 years. Numerous themes remind me of my own observations as in my aforementioned <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/">Drexel health IT difficulties site</a>: <blockquote>The implementation processes of the HSS [governmental Health IT support, a.k.a. Health Support Services - ed.] were criticised for refusing to acknowledge the validity of complaints, failing to fulfil promises, creating an ineffective change process, refusing to consult clinicians, using strategies to disenfranchise participation by clinical staff, and introducing a technology that doesnʼt fit their needs. </blockquote>All of these themes are familiar to me, and are representative of the phenomena of non-clinician, IT-centric arrogant ignorance, paternalism, leadership-pyramid inversion (i.e., the facilitators thinking and acting as if they are the enablers of healthcare), playing nasty politics with clinicians to avoid work, and minimizing job and results-evaluation discomfort for those lucky enough to secure cushy IT jobs in health IT support. <blockquote>In determining the clinical documentation needs of staff, the Directors claim that the HSS ignores the needs of staff. Directors report over-supply of irrelevant information and under-supply of needed information in the clinical interfaces. ["Legible gibberish" - ed.] The environment consists of counter-intuitive interfaces where data is entered by one person in one part of the system so that it is not discoverable by another person. The interfaces have inappropriate sizing of objects, confusing functions, redundant steps, unused functions and cluttered interfaces. These difficulties have resulted in increased time usage on the system resulting in decreased time with patients for no gain in administrative or clinical outcomes. Staff minimise their use of the system to as little as possible with work arounds being constantly developed and improved. Staff morale has been clearly degraded with accompanying loss of respect for the HSS and more generally NSWHealth’s authority. </blockquote> These concepts are described and illustrated in my multi-part essay on the healthcare IT mission hostile user experience <a href="http://www.tinyurl.com/hostileuserexper">at this link</a>. They represent major deviations from good information science, information presentation and human-computer interaction (HCI) precepts. <blockquote>... Workarounds in using the system are the most obvious tangible response of staff to the functions of the system they consider unsatisfactory. The key aspect of workarounds is that they constitute a subversion of the policy processes created by the software that the staff are not prepared to collaborate with. Some of these strategies may even compromise the legal status of the records in the system: such as not signing documents, unrecorded alterations to documents, and test results not attached to patient records. ... Another form of staff protest workaround is the strategy by staff to avoid using the system by either having other people [presumably underlings - ed.] do the work on the system, inserting minimal amounts of information thereby reducing the value of the information and passing information to other staff verbally. </blockquote> Workarounds to IT obstacle courses and booby traps, as noted by Koppel, Wetterneck, Telles & Karsh in "<a style="font-weight: bold;" href="http://jamia.bmj.com/content/15/4/408.abstract">Workarounds to Barcode Medication Administration Systems: Their Occurrences, Causes and Threats to Patient Safety</a>", J Am Med Inform Assoc. 2008 Jul-Aug;15(4):408-23, increase, not reduce, the risk of EHR-mediated medical errors. I wrote about their findings at "Business v. clinical computing: Workarounds to Barcode Medication Administration Systems" <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=barcoding">at this link</a>. It should be kept in mind that these are mission-critical systems for use in a fast-paced ED, not tracking systems for widgets - or for lab rats. <blockquote>The lack of appropriate reporting functionality of the system has had a serious impact on the critical work of the Directors on process improvement ... It was evident in talking to the Directors that they have antennae highly tuned to the processes happening in their departments and the public health issues that emerge from their patients. On a daily, weekly and monthly basis they review single cases, collections of common cases, and variations in established disease profiles to understand the success of their work and to detect emerging new trends or potential new disease outbreaks. At an administrative level they are asked to review cases either because of the return of new test results or due to complaints or reviews from other bodies. The FirstNet installation has removed all the reporting functionality the directors had in their previous system EDIS while destroying their information sources for process improvement, and their mechanisms for creating and collaborating in research projects. This, in turn, has led to a loss of motivation to enter data further degrading the value of the data held within the system.</blockquote> Reducing the value of a tool to people, and decreasing their ability to perform their jobs (especially when they take great professional responsibility and pride in those jobs) predictably leads to demoralization, demotivation and a cascading path down a whirlpool of failure. <blockquote> The disadvantages of the system for day to day operations is well demonstrated by the issues around the ordering system. It is stated to be overly complex and requires a large deal of repetitive information to be input for multiple orders on one sample, plus specialist data entry knowledge that requires every joint order to have exactly the same timestamp. Ordering was the first accession where staff recognised that information is sometimes sent to the wrong staff, both arriving where it shouldn’t and not arriving where it should. ... Further mis-processing is seen with the cancellation of orders when a patient is transferred to a hospital ward from the ED. The results of orders, particularly radiology, often need to be checked by senior staff, but the system has no functionality to enable efficient processing of orders that have normal results, and thereby require no further attention.</blockquote> I do recall another EHR system, by the same vendor I believe, where an "upgrade" in the recent past led to orders ending up in the wrong places (<a href="http://hcrenewal.blogspot.com/2010/08/huffington-post-investigative-fund-fda.html">link</a>): <blockquote>... Computers at a major Midwest hospital chain went awry on June 29, posting some doctors’ orders to the wrong medical charts in a few cases and possibly putting patients in harm’s way. The digital records system “would switch to another patient record without the user directing it to do so,” said Stephen Shivinsky, vice-president for corporate communications at Trinity Health System. Trinity operates 46 hospitals, most in Michigan, Iowa and Ohio. [In other words, data entered by clinicians was going into the wrong charts. How many charts were involved? Does the hospital system even know, I wonder? - ed.] Less than two weeks later, an unrelated glitch caused Trinity to shut down its $400 million system for four hours at 10 hospitals in the network because electronic pharmacy orders weren’t being delivered to nurses for dispensing to patients, he said.</blockquote> Not to pick on this vendor; these "glitches" seem to be occurring in many HIT vendor's products. All this, dear readers, is simply madness. <blockquote> ... Patient record retrieval is an important aspect of the staff work with patients, therefore its efficiency and accuracy is of vital importance to the activities of the ED. Staff were particularly pointed about the deterioration of this functionality in FirstNet compared to the previous system EDIS. [ED information system - ed.] There were cases where records could not be found, confusion about where data was stored in the patient record with different staff writing the same information into different parts of the record, and the [manual] rewriting of records [requiring a large amount of additional labor and time, not exactly a commodity in an ED -ed.] due to insertion of content into the wrong record.</blockquote> These are critical issues. If you can't get information out of a computer in a timely fashion, what you have is a very expensive doorstop. I also note that a document imaging system that images hand written charts would not have these problems... Prof. Patrick addresses the oft-heard canard that such complaints are the complaints of "Luddite doctors", old dogs who simply don't want to learn new tricks: <blockquote>The staff in the ED are now generally experienced at using some form of clinical information system, many for over 10 years. This experience gives them a keen sense of what is possible with technology as well as the deficiencies in the existing systems. Combining this experience and knowledge with a sense of professional responsibility for process improvement enables them to judge quite acutely when a system is well designed or not. Hence their observations about elements of systems that are not parsimonious enough for optimal clinical efficiency deserve to be respected. </blockquote> That it even needs to be written that the opinions of experienced medical professionals on the tools they are coerced to use by non-medical outsiders "deserve to be respected" gives testimony to my observation of a cross-disciplinary invasion of healthcare by the IT profession (among others). <blockquote> Workflow and dataflow and the continuity of these processes are vital to the smooth running of a complex socio-technical process. ED staff have shaped these flows over a period of years and socialised all staff into the streaming. The directors have found that with the workflow of staff needing to use both clinical and nursing notes at the same time, their separation in FirstNet is deleterious. One department considered that the many nursing and medical notes accumulated over a day had to be kept in a single continuous sequence in the clinical record. Their workaround was to keep the one note page open for 24 hours to maintain the needed continuity in the patient record and avoid staff using a significant amount of time at the computer searching for needed information. </blockquote>Nemeth and Cook explain how an ED EHR can be developed and marketed that interferes with, not supports, the workflows common in ED"s worldwide, in "<a href="http://www.ctlab.org/documents/Hiding%20in%20plain%20sight.pdf">Hiding in plain sight: What Koppel et al. tell us about healthcare IT</a>", J Biomed Inform. 2005 Aug;38(4):262-3: <blockquote> ... On the surface, healthcare work seems to flow smoothly. That is because the clinicians who provide healthcare service make it so. Just beneath the apparently smooth-running operations is a complex, poorly bounded, conflicted, highly variable, uncertain, and high-tempo work domain. The technical work that clinicians perform resolves these complex and conflicting elements into a productive work domain. Occasional visitors to this setting [i.e., IT personnel, non-medical bureaucrats, etc. - ed.] see the smooth surface that clinicians have created and remain unaware of the conflicts that lie beneath it. The technical work that clinicians perform is hiding in plain sight. [Hiding from the uninformed, that is - ed.] Those who know how to do research in this domain can see through the smooth surface and understand its complex and challenging reality. Occasional visitors cannot fathom this demanding work, much less create IT systems to support it. Progress in healthcare IT systems relies on scientific data on the actual, not the perceived, nature of day-today operations.</blockquote> It increasingly seems the only place the faux-expert, healthcare-facilitor, cybernetic snake oil salespeople are going ot learn this simple lesson is in the courtroom... <blockquote>A recent article in the press has presented evidence that access block times in EDs across the state of NSW are worsening. </blockquote> As regards causality, it perhaps takes being an IS dept. director in a hospital - or holding elected office - to be unable to recognize the nose at the front of one's face. Prof. Patrick wraps up this section of his forensic analysis as follows: <blockquote>A number of conclusions can be drawn from the study: 1. Staff are entirely dissatisfied with the SBB and they feel that the deliverables have significantly failed to match the promises. 2. The Directors see that the HSS have failed in their support of the frontline of emergency care across the Sydney basin and their practices are decidedly lacking in proper engagement with the user community which should be their primary concern. 3. Some of the consequences of the HSS decision not to provide the reports needed by the Directors have lead to them being seriously hampered in being able to monitor the quality of their own department’s practices and wider changes and trends in community health. 4. The inefficiencies introduced by this technology have lead to a litany of complaints about its behaviour that have gone unheeded over the past three years. 5. It has lead to major strategies to work around the system by staff at all levels, to the point of complete avoidance by some staff. The major consequences of these failings in the eyes of the ED directors are: <ul><li>Lost productivity and inefficiencies,</li><li>Increased risks to patients,</li><li>Disillusionment of staff and loss of morale.</li></ul></blockquote>Considering my own relative's injuries originating in an ED EHR mishap, I think I can safely add to Prof. Patrick's final tally an additional item: <blockquote><ul><li>Patients have been harmed. </li></ul></blockquote>This is not a pretty picture. I'm confident the Australian legal system abhors negligence as much as our own here in the U.S. If patients are injured and/or die as a result, considering that the Programme leadership and IT vendors knew - or should have known - of these deficits, it would not surprise me if criminal negligence charges begin to appear. These issues are not exactly rocket science, and an expanding literature base has been appearing in recent years. See, for example, my recent post "An Updated Reading List on Health IT" <a href="http://hcrenewal.blogspot.com/2011/02/updated-reading-list-on-health-it.html">at this link</a>. I can only add that my own relative was nearly killed as a result of a number of the phenomena described in Prof. Patrick's analysis. More on other sections of his report at another time. -- SS March 6, 2011 addendum: Also see my new post "<a href="http://hcrenewal.blogspot.com/2011/03/what-to-do-about-state-of-ed-ehr-in-nsw.html">What to do about the state of the ED EHR in NSW?</a>" -- SS Mar. 8, 2011 addendum: Prof. Patrick has added a new section to his report, entitled "The Future Pathways for e-Health in NSW." It is available <a href="http://sydney.edu.au/engineering/it/%7Ehitru/essays/Things%20we%20should%20change%20in%20NSW-v4.pdf">at this link</a> (PDF). It inoculates against most of the 'Ten Plagues' that bedevil health IT projects (such as the IT-clinical leadership inversion, magical thinking about the technology, and lack of accountability): More on the Pathways at my post <a href="http://hcrenewal.blogspot.com/2011/03/future-pathways-for-e-health-in-nsw.html">here</a>. The de facto "National Program for IT in the HHS" here in the United States needs a similar inoculation. --SS

On an EMR Forensic Evaluation by Professor Jon Patrick from Down Under: More Thoughts.

Note: the reports to which this post refers are available as a set of PDF's from the University of Sydney, NSW, Australia at this link ...

Đọc thêm »

Here Comes the Judge! A Quick Thought on Cybernetic Medicine: Why Can't Computers Also Do Law?

At my Jan. 2011 post "<a href="http://hcrenewal.blogspot.com/2011/01/ibms-watson-jeopardy-and-revolutioning.html">IBM's Watson, Jeopardy, and Revolutionizing Medicine</a>" I lamented that with every new computer advance since the 1950's, soon to follow was a prediction of cybernetic advancements in medicine, such as this: <blockquote>... A Watson-like system can take that information and co-relate it against all the medical journals and relevant information, and say, "Here's what I think and why," while showing its evidence for how it came up with the conclusion, according to Frase [vice president of industry solutions and emerging business at IBM Research].</blockquote> The following recently occurred to me in the early morning hours as I watched the sun rise: I wonder why there are no suggestions of replacing lawyers with computers. After all, a Watson-like system can take lawsuit information and co-relate it against all the legal journals and relevant information, and say, "Here's what I think and why," while showing its evidence for how it came up with the conclusion. No need for lawyers and their cognitive processes and judgment! Right? The judge could be replaced by a cyber-judge. <a href="http://www.judgealex.com/">Judge Alex</a> and <a href="http://www.judgejudy.com/">Judge Judy</a>, you've met your match. Here comes the cybernetic judge... <div style="text-align: center;"><a href="http://www.youtube.com/watch?v=3hIcKkKID8k"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5580606684680627346" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfUsQtELFbFI5kw9SqfSKmNrJBUR0u1MGAWPvsOZ2Vn5hWX1mVOhAd-itrZltd3LuFv9rlFV_Kv6Qp9M594b4dpzKt9_amMGKdU9nRBpA5w7CL5_P3_pgRQl3DRGWRxgE45dgQ3SSqyZzG/s320/here_come_the_judge.jpg" style="display: block; margin: 0px auto 10px; text-align: center; cursor: pointer; width: 254px; height: 122px;" /></a>Order in the Court, Cause Here Comes the Judge! Click to play video. </div> A set of Watson-like systems could even serve as a jury, being capable, as we know, of flawless human judgment. ... The jury findings, your honor Judge Watson are: <blockquote>Bob Watson: defendant is guilty by algorithm. Mary Watson: defendant is guilty by algorithm. Judy Watson : defendant is guilty by algorithm. Frank Watson: defendant is guilty by algorithm. Tom Watson: defendant is ... xoxooxo1011001%$&#@# </blockquote> (Oops, sorry, your cybernetic Honor, Tom's primary CPU crashed.) Think of the possibilities... Perhaps Watson could even be programmed to, say, determine if a proposed law is constitutional or not? No more Supreme Court! Like medicine, cybernetic practice of law should be <a href="http://www.thefreedictionary.com/reductio+ad+absurdum">child's play</a>, no? -- SS

Here Comes the Judge! A Quick Thought on Cybernetic Medicine: Why Can't Computers Also Do Law?

At my Jan. 2011 post " IBM's Watson, Jeopardy, and Revolutionizing Medicine " I lamented that with every new computer advance ...

Đọc thêm »

Thanks to the wonders of EHR, this premature baby went to the grave, prematurely

Thanks to the distractions of EHR and the wonders of EHR auto entry, cut and paste etc., this premature baby went to the grave, prematurely: <blockquote>Failures in care alleged after premature birth - $1,000,000 Settlement By Virginia Lawyers Weekly Published: October 18, 2010 Tags: Fairfax County Circuit Court, Medical Malpractice, Million-Dollar Settlements Decedent and his twin sister were born healthy at 27 weeks gestation. Decedent was placed in the neonatal intensive care unit. Six days after birth, a peripherally inserted central catheter (PICC) was inserted into the right axilla and used to infuse nutrition, medication, blood products and lipids. Within 48 hours, the PICC insertion site began to show evidence of compromise. The attending physician gave a verbal order to monitor the arm, but the order was never reduced to writing and no monitoring of the site was thereafter documented in the chart. Indeed, a comparison of the IV site care notes with the nursing notes revealed the use of an automated entry feature, confirmed by the defendants in discovery, which permitted the nursing staff to simply re-enter prior descriptions of a patient’s condition. [Transforming medicine, one thunderous mouse click at a time, as expressed by the former HHS secretary. As at <a href="http://www.physicianspractice.com/risk-management/content/article/1462168/1800351?pageNumber=2">this link on EHR risks</a> re: copy and paste, "Another pitfall seen in litigation is the situation of an incorrect history or physical finding that is documented repeatedly in the medical record. This frequently occurs in the in-patient setting but can occur in the outpatient setting as well." - ed.] As a result, the nursing notes continued to describe the condition of the affected arm as normal when in fact it was continuing to visibly deteriorate. Thereafter, despite swelling and seepage at the PICC insertion site and discoloration of the hand, the PICC was not removed for an additional 48 hours. The decedent was flown to another facility where the right arm was amputated after becoming necrotic and gangrenous. The infant died after 36 days of life. Plaintiffs sued the nurses, hospital and neonatal specialists charged with the decedent’s care. Plaintiffs’ experts were prepared to testify that it was a departure from the standard of care for the physicians and nurses to fail to monitor the PICC insertion site and promptly remove the line when evidence of compromise and vascular damage developed. [That's a no-brainer. Were these clinicians distracted by EHR clerical data entry duties, I wonder? - ed.] They would have further testified that these departures caused a cascade of events leading to necrosis of the arm, the onset of gangrene and eventually staph sepsis, which killed the decedent. The plaintiffs’ wrongful death claim was primarily for loss of solace. The decedent was survived by his parents and three siblings, including his fraternal twin. The decedent’s twin is now a healthy 2-year old who is meeting all normal developmental milestones. [10-T-153] Type of Action: Medical malpractice Injuries Alleged: Name of case: Court: Fairfax County Circuit Court Tried before: Name of judge/mediator: Special Damages: Verdict or Settlement: Amount: $1,000,000 Date: Sept. 17, 2010 Plaintiffs’ attorneys: Infant death Confidential Mediation Johanna L. Fitzpatrick $584,000 in medical expenses (contested by defendants) Settlement H. Jan Roltsch-Anoll, Woodbridge; Tracy C. Hudson, Manassas</blockquote> What a tragedy. -- SS

Thanks to the wonders of EHR, this premature baby went to the grave, prematurely

Thanks to the distractions of EHR and the wonders of EHR auto entry, cut and paste etc., this premature baby went to the grave, prematurely:...

Đọc thêm »

"A Study of an Enterprise Health information System" - Finally, an Informatics Scientist Does A Rigorous Review of a Commercial EHR System, by Cerner

Australian professor Jon Patrick, who I wrote about at this blog in the past such as at my Nov. 2009 post "<a href="http://hcrenewal.blogspot.com/2009/11/academic-freedom-and-ed-ehrs-down-under.html">Academic Freedom and ED EHR's Down Under: An Update</a>", has written what I consider the first truly serious, rigorous evaluation of a commercial EHR system. He has evaluated the Cerner FirstNet ED EHR, being 'forced' on hospitals in the Australian state of New South Wales by their government. His evaluation is entitled "A study of an Enterprise Health information System" and was released on March 4, 2011. In my view, all current EHR's should undergo this level of scrutiny and critique. His multi-part analysis, down the the level of the data schema, speaks for itself. The report is at: <a href="http://sydney.edu.au/engineering/it/%7Ehitru/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> or download directly from: <a href="http://www.it.usyd.edu.au/%7Ehitru/essays/Study%20of%20Enterprise%20Health%20IS%20-%20Parts%200-9%20PDF-ARCHIVE.zip">http://www.it.usyd.edu.au/~hitru/essays/Study%20of%20Enterprise%20Health%20IS%20-%20Parts%200-9%20PDF-ARCHIVE.zip</a> [Note: this is a 12 Mb .zip file]. Summary: <blockquote>This is a study into the roll-out of Cerner FirstNet into EDs in NSW. The original study was issued in Dec 2009 (Part 3.1). This has been added to with a new study in 2010 consisting of discussions with 7 ED Directors (Part 3.2), discussions with software experts who do performance evaluations on Cerner sites (Part 3.3), and reviews of Entity-Relationship Diagrams (Part 3.4), Schema descriptions and data tables from customer installations (Part 3.5 & 3.6). All this information is coalesced to establish a much more detailed picture of a Cerner installation (Part 3.7). A number of weaknesses are identified in the design and implementation and risk assessments are recommended for organisations using this software or intending to use it. Regulations that might minimise the risks to users of health software are recommended (Part 3.8). An alternative architecture and method for constructing clinical information systems is presented (Part 3.9).</blockquote> The .zip file contains the following files: <blockquote>3.0 Part 0 - Executive Summary 3.1 Part 1 - A Critical Essay on the Deployment of an ED Clinical Information System ‐ Systemic Failure or Bad Luck? First published here in Oct 2009, revised Dec 2009. 3.2 Part 2 - Discussions with ED Directors: Are we on the right track? 3.3 Part 3 - Discussions with Software Performance Experts. 3.4 Part 4 - Conceptual Data Modelling. 3.5 Part 5 - Database Relational Schema and Data Tables. 3.6 Part 6 - Coalescing the Analyses of the ER Diagrams, Relational Schemata and Data Tables. 3.7 Part 7 - The Integrated Assessment. 3.8 Part 8 - Future HIT Regulation Proposals. 3.9 Part 9 - Ockham's Razor of Design. Published at the IHI conference, Nov 2010 Washington.</blockquote> A non-technical but revealing summary from Part 2: <blockquote> Discussions were held with the Directors of 7 Emergency Departments in New South Wales (NSW) public hospitals assessing the impact of the introduction of the FirstNet information system into their Departments. All but one of the Directors has found that the system has had a deleterious impact on their department’s clinical work. The range of problems reported indicate that whilst the software is not fit-for-purpose, many of the problems are created or exacerbated by attitudes of the NSW Health IT support, Health Support Services (HSS). In most departments it was reported that staff have developed significant strategies for minimising and circumventing the use of the system. The Directors are frustrated by the lack of a reporting functionality that disables their ability to monitor their own department’s performance. Most Directors report an increase in the time required to deal with patients and therefore a deterioration in access block times. This has been masked by changes in the way this time has been redefined by NSW Health. Overall, most perceive that in moving from their previous information system EDIS to FirstNet they and their patients have suffered. Most Directors are resigned to the fact that no improvements will be made to the current performance of the system due to its inherent inadequacies and the attitude of HSS. A consequence of the ED Directors critique leads inevitably to the debate on the merits of enterprise wide systems versus best-of-breed systems. Emerging from these issues are criteria for a new technology for creating clinical information systems.</blockquote> I will have more to say on this study later. I have to take an injured relative to the doctor. (Note - the culpable system was not by this vendor). -- SS

"A Study of an Enterprise Health information System" - Finally, an Informatics Scientist Does A Rigorous Review of a Commercial EHR System, by Cerner

Australian professor Jon Patrick, who I wrote about at this blog in the past such as at my Nov. 2009 post " Academic Freedom and ED EHR...

Đọc thêm »

HIMSS and Healthcare IT: We Don't Need A "Usability Maturity Model." We Need - USABILITY - and Less of Cold-Blooded Calculus

Health IT industry consortium HIMSS has followed up its Master of the Obvious, 50-years-too-late paper "Defining and Testing EMR Usability: Principles and Proposed Methods of EMR Usability Evaluation and Rating" (June 2009) that I wrote about in a Dec. 2010 post "<a href="http://hcrenewal.blogspot.com/2010/12/unintended-errors-with-ehr-based-result.html">Unintended errors with EHR-based result management: a case series, and a special pleading for health IT</a>" with a new report: <a href="http://www.himss.org/ASP/ContentRedirector.asp?ContentID=76349"></a><blockquote><a style="font-weight: bold;" href="http://www.himss.org/ASP/ContentRedirector.asp?ContentID=76349">Promoting Usability in Health Organizations: Usability Maturity Model</a> (PDF, Feb. 2011)</blockquote> I knew I was in for a heaping helping of gobbledygook after reading the title itself: “Promoting Usability in Health Organizations: Initial Steps and Progress Toward a Healthcare Usability Maturity Model” A “Healthcare Usability Maturity Model” is a clue that what follows will take simplicity, and expend considerable ink to tangle it into a mess of process mysticism, buzzwords, paradigms, very pretty charts, and other Master-of-the-Obvious-made-to-look-sophisticated, destined-for-the-dusty-shelf consultant report. That is largely what follows. See for yourself.This passage in the Executive Summary is pathognomonic of the amoral, money-over-blood, patients-as-guinea-pigs mentality that inhabits the commercial health IT sector. I find it particularly revealing and revolting: <blockquote> ... Leaders may be reluctant to incorporate usability principles and practices [in a safety-critical technology increasingly mediating all aspects of medical care delivery - ed.] because of perceptions that these methods may slow development and product fielding. However, data exist on usability return on investment (ROI), outlining the value of adopting usability in health organizations. </blockquote> Excuse me? It takes proof of "ROI" to convince these companies to produce usable (which subsumes the concept of "safe") health IT? This is as cold-blooded a calculus as it gets. This is <a href="http://en.wikipedia.org/wiki/Ford_Pinto">Ford Pinto</a> material:<blockquote>... Critics alleged that the vehicle's lack of reinforcing structure between the rear panel and the tank meant the tank would be pushed forward and punctured by the protruding bolts of the <a href="http://en.wikipedia.org/wiki/Differential_%28mechanics%29" title="Differential (mechanics)" class="mw-redirect">differential</a><a href="http://en.wikipedia.org/wiki/Ford_Pinto#cite_note-fordpintocase-14">[15]</a> [by a rear end collision of only 20 mph/32 km/h, causing a fire - ed.]— making the car less safe than its contemporaries.According to a 1977 <a href="http://en.wikipedia.org/wiki/Mother_Jones_%28magazine%29" title="Mother Jones (magazine)">Mother Jones</a> article, Ford allegedly was aware of the design flaw, refused to pay for a redesign, and decided it would be cheaper to pay off possible lawsuits for resulting deaths. The magazine obtained a <a href="http://en.wikipedia.org/wiki/Cost-benefit_analysis">cost-benefit analysis</a> that it said Ford had used to compare the cost of an $11 repair against the monetary value of a human life—what became known as the Ford Pinto Memo.<a href="http://en.wikipedia.org/wiki/Ford_Pinto#cite_note-50worst-12">[13]</a><a href="http://en.wikipedia.org/wiki/Ford_Pinto#cite_note-mother-15">[16]</a><a href="http://en.wikipedia.org/wiki/Ford_Pinto#cite_note-16">[17]</a> An example of a Pinto rear-end accident that led to a lawsuit was the 1972 accident that killed Lilly Gray and severely burned 13-year old Richard Grimshaw. The accident resulted in the court case <a href="http://en.wikipedia.org/wiki/Grimshaw_v._Ford_Motor_Co.">Grimshaw v. Ford Motor Co.</a>,<a href="http://en.wikipedia.org/wiki/Ford_Pinto#cite_note-17">[18]</a> in which the California Court of Appeal for the Fourth Appellate District upheld compensatory <a href="http://en.wikipedia.org/wiki/Damages">damages</a> of $2.5 million and <a href="http://en.wikipedia.org/wiki/Punitive_damages">punitive damages</a> of $3.5 million against Ford, partially because Ford had been aware of the design defects before production but had decided against changing the design. [In more recent years, others said the Ford Pinto scandal was not clear-cut, but health IT unusability increasing odds for medical errors is clear-cut - ed.] </blockquote> <blockquote> </blockquote> Why are these companies and their leadership getting to play God - in a field such as Medicine? <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtYbO9i2jbJhyyQoyesX24vy99i7HmbRi1kxfdWEEBWLpTmLP96_JrM5JI86qwUPQj1Ty9do51aSnNSRNA8dohgaxoRq-xqmtV_BNVjW4U6Bq42Yw3K2gnwf5tK7_mxnnVqOj9KN9r1y6W/s1600/cp.jpg"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5579924020893002882" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtYbO9i2jbJhyyQoyesX24vy99i7HmbRi1kxfdWEEBWLpTmLP96_JrM5JI86qwUPQj1Ty9do51aSnNSRNA8dohgaxoRq-xqmtV_BNVjW4U6Bq42Yw3K2gnwf5tK7_mxnnVqOj9KN9r1y6W/s320/cp.jpg" style="display: block; margin: 0px auto 10px; text-align: center; cursor: pointer; width: 128px; height: 181px;" /></a>Usability? Those Luddite doctors and crummy patients will get usability over my - er, their - dead bodies, if I don't profit handsomely from it. Finally, I have several meta-observations about this new report: <ul><li>We don't need a "usability maturity model." We need USABILITY. We need the common and longstanding knowledge of software usability in other mission critical sectors to be applied on the development whiteboard and usability testing labs (if any!) at HIT vendors. </li></ul><ul><li>Why is it that health IT usability has to be written about, basically as if from the grade school level, in 2011 - some sixty years into the “computer revolution?” Do we still write treatises on why it’s wise to use sterile technique and good lighting in operating rooms? What is the major malfunction in this industry? </li></ul><ul><li>Why is this treatise not entitled “Promoting Usability in Health IT Vendor Development Shops: A Vendor Responsibility Model”?</li></ul><ul><li>The frequent use of the terminology "user experience" as applied to healthcare IT in this report struck my eye. It has been adopted in this report, but was uncommon regarding health IT until recently, as in my posts about the health IT <a href="http://www.tinyurl.com/hostileuserexper">mission hostile user experience.</a> </li></ul>The terminology is conspicuously absent in the aforementioned earlier 2009 HIMSS report. It would not take Sherlock Holmes to theorize that I might be an <a href="http://www.google.com/search?client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&channel=s&hl=en&source=hp&biw=1024&bih=578&q=healthcare+IT+user+experience&btnG=Google+Search#sclient=psy&hl=en&client=firefox-a&hs=q9q&rls=org.mozilla:en-US%3Aofficial&channel=s&biw=1024&bih=578&tbs=ww:1&q=%22mission+hostile+user+experience%22&aq=f&aqi=&aql=&oq=&pbx=1&bav=on.2,or.&fp=6c13b9433fbb516b">unattributed contributor</a> to the new 2011 HIMSS report. If anyone knows differently, I'd be interested to hear about it.-- SS <blockquote> </blockquote>

HIMSS and Healthcare IT: We Don't Need A "Usability Maturity Model." We Need - USABILITY - and Less of Cold-Blooded Calculus

Health IT industry consortium HIMSS has followed up its Master of the Obvious, 50-years-too-late paper " Defining and Testing EMR Usabi...

Đọc thêm »

Vladimir Putin and Common Sense on IT

Vladimir Putin may be known for showing off his pectorals riding horses bare chested, but he also seems to have a substantial amount of gray matter between the ears. Our country, including the healthcare IT sector, could probably learn something from him: <blockquote><a href="http://online.wsj.com/article/SB10001424052748704415104576065641376054226.html"> A Walled Wide Web for Nervous Autocrats </a> Wall Street Journal Jan. 8, 2011 By EVGENY MOROZOV At the end of 2010, the "open-source" software movement, whose activists tend to be fringe academics and ponytailed computer geeks, found an unusual ally: the Russian government. Vladimir Putin signed a 20-page executive order requiring all public institutions in Russia to replace proprietary software, developed by companies like Microsoft and Adobe, with free open-source alternatives by 2015. The move will save billions of dollars in licensing fees, but Mr. Putin's motives are not strictly economic. In all likelihood, his real fear is that Russia's growing dependence on proprietary software, especially programs sold by foreign vendors, has immense implications for the country's national security. Free open-source software, by its nature, is unlikely to feature secret back doors that lead directly to Langley, Va. </blockquote>It's also less likely to feature a backdoor to a hacker's basement, or a lot of bugs ("glitches") that some health IT vendors and customer organizations allow to accumulate into the thousands before lifting a finger. This brings to mind the adage that "if you want something done right, do it yourself." <blockquote> ... For ordinary Internet users, there is one silver lining: The embrace of open-source technology by governments may result in more intuitive software applications, written by a more diverse set of developers. [Read the whole article at the link above - ed.] </blockquote>More intuitive IT applications could solve a lot of the current health IT problems, such as the <a href="http://www.tinyurl.com/hostileuserexper">mission hostile user experience</a> of many closed-source products from major vendors. Afrer major IT debacles including the <a href="http://www.huffingtonpost.com/stephen-soumerai/dont-repeat-the-uks-elect_b_790470.html">£13 billion abyss</a> of the National Programme for IT in the NHS (NPfIT), the UK also seems to be learning: <blockquote><a href="http://www.ehi.co.uk/news/EHI/6687/new_approach_urged_for_government_it">New approach urged for government IT</a> E-Health Insider <div style="padding-bottom: 10px;font-size:0.9em;">2 March 2011 Lyn Whitfield </div> <div style="margin-top: 3px; margin-bottom: 10px; float: right; margin-left: 15px;"> </div> A new report into government IT failures has warned that previous inquiries may have embedded problems by focusing on inappropriate ‘best practice’ instead of looking for alternative approaches. The report, from the Institute for Government, says “existing ‘best practice’ project models do not deal with the fundamental issues at the heart of government IT.”[As I've stated <a style="font-style: italic;" href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/">here</a>, one has to consider the "worst practices" as well, the "thou shall not's." Typical Milquetoast, touchy-feely "best practices" models and their "sanitized accounts of successful projects" (cf. <a href="http://hcrenewal.blogspot.com/2009/12/healthcare-it-as-cybernetic-miracle.html">Greenhalgh</a><a href="http://hcrenewal.blogspot.com/2009/12/healthcare-it-as-cybernetic-miracle.html"> et al.</a>) avoid such inconvenient realities like the plague - ed.] It also argues that: “By implementing these same, flawed project techniques in an increasingly rigid fashion, these traditional solutions can act to exacerbate the problems further.” [This sounds familiar, typical of the inflexible, dogmatic business IT culture, descended from the punched-card programmable tabulator culture of the 1920's - see <a href="http://hcrenewal.blogspot.com/2008/05/seedie-society-for-exorbitantly.html">this link</a> - ed.] Instead, it calls for a new that focuses on using government’s huge buying power to get better deals for what it calls ‘platform' technologies – such as server capacity and PCs – while encouraging departments to adopt ‘agile’ methodologies to deliver systems to meet the particular challenges they face.... Andrew Adonis, Director of the Institute for Government said: “The billions spent on cancelled IT projects, such as ID cards and National Programme for IT in the NHS, demonstrate precisely why we need a much more flexible approach to government IT. ... The report cites the national programme as one ‘symptom of failure’ in government IT; the tendency for projects to run late and for departments to struggle to keep suppliers on board or hold them to their original delivery requirements as a result. </blockquote> <a href="http://en.wikipedia.org/wiki/Agile_software_development">Agile software development methodologies</a> have traditionally been anathema to the culture of IS departments involved in mercantile, manufacturing and management varieties of business computing. As I've written many times, however, those methodologies are essential in healthcare IT, such as <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=Cardiology%20story">here</a> and <a href="http://hcrenewal.blogspot.com/2010/09/health-it-danger.html">here</a>. At the latter link I observed: <blockquote>... In fact, in my observations IT personnel are the true Luddites [as opposed to clinicians who are often accused of that reactionary characteristic- ed.], clinging to inappropriate, rigid business-IT views on the healthcare IT development and implementation process (vs. more appropriate and modern <a href="http://en.wikipedia.org/wiki/Extreme_Programming">agile methodologies</a>), holding unshakable, stereotypical views about physicians, and remaining unreasonably obstinate on clinician complaints about "clunky" health IT user experiences.</blockquote> Perhaps Mr. Putin and Mr. Adonis deserve a copy of the book "<a href="http://www.amazon.com/Medical-Informatics-Electronic-Collaboration-Innovation/dp/0763739251">Medical Informatics 20/20: Quality And Electronic Health Records Through Collaboration, Open Solutions, And Innovation</a>", Jan. 2007, by the <a href="http://www.ehealth.va.gov/EHEALTH/CPRS_Demo.asp">VistA</a> (open-source EMR) pioneers. The "Open Solutions" part of that title says it all. -- SS

Vladimir Putin and Common Sense on IT

Vladimir Putin may be known for showing off his pectorals riding horses bare chested, but he also seems to have a substantial amount of gray...

Đọc thêm »

IOM Committee on Patient Safety and Health IT, Meeting Two: Institute of Medicine, or of Mediocrity?

In my Jan. 2011 post "<a href="http://hcrenewal.blogspot.com/2011/01/institute-of-medicine-committee-on.html">Institute of Medicine Committee on Patient Safety and Health Information Technology, and Thoughts on Social Aspects of Health IT Evaluation</a>" I wrote that: <blockquote>The U.S. National Research Council of the <a href="http://www.nationalacademies.org/">National Academy of Sciences</a> issued a report in early 2009 on the state of health IT. That study's report, led in part by pioneers in Medical Informatics G. Octo Barnett and William Stead, was entitled "Computational Technology for Effective Health Care: Immediate Steps and Strategic Directions" (pre-publication PDF available free at <a href="http://www.nlm.nih.gov/pubs/reports/comptech_prepub.pdf">this link</a>). The report was announced under the following header: <a href="http://www8.nationalacademies.org/onpinews/newsitem.aspx?RecordID=12572"> </a><blockquote><a href="http://www8.nationalacademies.org/onpinews/newsitem.aspx?RecordID=12572">CURRENT APPROACHES TO U.S. HEALTH CARE INFORMATION TECHNOLOGY ARE INSUFFICIENT </a></blockquote> The insufficiencies were largely in the areas of difficulties with data sharing and integration, deployment of new IT capabilities, large-scale data management, and lack of cognitive support by health IT for busy clinicians. One might reasonably conclude such deficits could affect patient safety. Recently the <a href="http://www.iom.edu/About-IOM.aspx">Institute of Medicine</a> (the health arm of the National Academy of Sciences) formed a Committee to study health IT safety. It held its first meeting on Dec. 14, 2010 (quite a few years late in my opinion, and only after tens of billions of dollars have been earmarked for health IT, but better late than never): <blockquote> The <a style="font-weight: bold;" href="http://www.iom.edu/Activities/Quality/PatientSafetyHIT.aspx">Institute of Medicine Committee on Patient Safety and Health Information Technology</a> is holding its first meeting on December 14-15, 2010. The first day, December 14, 2010 beginning at 10:30 am, is open to the public to observe the committee proceedings. The committee will hear presentations by the Office of the National Coordinator and other invited guests. There will also be an opportunity for members of the public and representatives of interested organizations to make a brief statement before the committee. Prior registration is requested for attendees and required for those wishing to make a statement.</blockquote></blockquote><blockquote></blockquote> Here are links to the PPT presentations from Meeting 2 of the Committee on Patient Safety and Health IT that took place Feb. 24, 2011: <blockquote> <a href="http://www.iom.edu/%7E/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Dwork.pdf">http://www.iom.edu/~/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Dwork.pdf</a> <a href="http://www.iom.edu/%7E/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/WoodsNormanFeb2011.pdf">http://www.iom.edu/~/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/WoodsNormanFeb2011.pdf</a> <a href="http://www.iom.edu/%7E/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Harper%20IOM%20HIT%20Patient%20Safety.pdf">http://www.iom.edu/~/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Harper%20IOM%20HIT%20Patient%20Safety.pdf</a> <a href="http://www.iom.edu/%7E/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Chrisman-.pdf">http://www.iom.edu/~/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Chrisman-.pdf</a> <a href="http://www.iom.edu/%7E/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Palmer.pdf"> http://www.iom.edu/~/media/Files/Activity%20Files/Quality/Patient%20Safety%20and%20HIT/Meeting%202/Palmer.pdf</a></blockquote> The PPT's can be downloaded directly from these links. <a href="http://www.blogger.com/redir.aspx?C=6a066a21e02c4884bce66800e5d0abb6&URL=http%3a%2f%2fwww.iom.edu%2f%7e%2fmedia%2fFiles%2fActivity%2520Files%2fQuality%2fPatient%2520Safety%2520and%2520HIT%2fMeeting%25202%2fPalmer.pdf" target="_blank"></a> I note several observations: <ul><li>The overall quality of these presentations appears mediocre; </li></ul><ul><li>Issues of healthcare IT risks - as they exist on the ground in 2011 - are addressed poorly if at all; </li></ul><ul><li>Proposed "solutions" are really nothing novel or new compared to existing literature or recommendations made in earlier studies, including that of the US NRC;</li></ul><ul><li>That these presentations come from the highest scientific body in the United States is, in my opinion, a disappointment and, indeed, an embarrassment.</li></ul> The IOM's rules of engagement, according to the Study Director, preclude my testifying, as a Medical Informatics specialist and former CMIO, about a relative's nearly being killed by poorly designed and implemented health IT. Instead, the linked presentations above are presented. Here's an example of what I consider a somewhat rigorous and critical thinking-based presentation on health IT risks: <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/Clinical_IT_benefits_risks.ppt"></a><blockquote><a href="http://www.ischool.drexel.edu/faculty/ssilverstein/Clinical_IT_benefits_risks.ppt">http://www.ischool.drexel.edu/faculty/ssilverstein/Clinical_IT_benefits_risks.ppt</a></blockquote> I think the IOM should be able to do better than a mere small-university medical informatics adjunct professor. -- SS

IOM Committee on Patient Safety and Health IT, Meeting Two: Institute of Medicine, or of Mediocrity?

In my Jan. 2011 post " Institute of Medicine Committee on Patient Safety and Health Information Technology, and Thoughts on Social As...

Đọc thêm »