healthy4u: NHS

This EHR "glitch" killed three-year-old Samuel Starr - but patient safety was not compromised

Actually, safety was compromised. I have written repeatedly that the term "glitch", an often-seen euphemism (usually accompanied with the phrase "but patient care/patient safety was not compromised"), is really a term for life-threatening health IT bugs and malfunctions.  See query link <a href="http://hcrenewal.blogspot.com/search/label/glitch">http://hcrenewal.blogspot.com/search/label/glitch</a> for examples of health IT "glitches" (retrieves multiple posts). <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpyDXrISVqufhC1OX4Qiik6pFNxIueFaUkAZrjyxcKT2cpNF9zcS9pQkHYWyZMp8RxM6gPn8BG3vZAXtqUOUpVbf5Fv4AHrXgzHfB_JoT6Ou4Kup25VRYDSx5S_okwyCWmdy3K5LekH52x/s1600/Main-Samuel-Starr-3204412.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpyDXrISVqufhC1OX4Qiik6pFNxIueFaUkAZrjyxcKT2cpNF9zcS9pQkHYWyZMp8RxM6gPn8BG3vZAXtqUOUpVbf5Fv4AHrXgzHfB_JoT6Ou4Kup25VRYDSx5S_okwyCWmdy3K5LekH52x/s1600/Main-Samuel-Starr-3204412.jpg" width="150" /></a></div> Here's a "glitch" that tragically killed this boy: <blockquote class="tr_bq">Three-year-old boy dies after new NHS computer system delays heart treatment Mar 05, 2014 By James Tute <a href="http://www.mirror.co.uk/news/uk-news/samuel-starr-death-nhs-computer-3209365">http://www.mirror.co.uk/news/uk-news/samuel-starr-death-nhs-computer-3209365 </a> Coroner Maria Voisin rules that new booking system meant he did not receive life-saving treatment A three-year-old boy died in his parents' arms after a new NHS computer system failed to schedule him for a vital heart scan, a coroner has ruled. Samuel Starr was born with a congenital cardiac defect and needed surgery not long after he was born in 2010. Although he made a good recovery doctors said he would need regular tests to check on his progress. But he did not have a scan until 20 months after his first major operation because of a delay following the introduction of a new computer system, Cerner Millennium. When he finally had the appointment doctors found Samuel needed open heart surgery. During the procedure, Samuel had a stroke. A month later, after further complications, he died in the arms of his devastated parents, Catherine Holley and Paul Starr, at Bristol Royal Hospital for Children.</blockquote> There are some in my field who would (and have) called incidents like this "anecdotes" or "bumps in the road." Yet, as I've recently posted, an internationally-renowned healthcare safety tester, ECRI Institute (<a href="http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html">http://hcrenewal.blogspot.com/2013/02/peering-underneath-icebergs-water-level.html</a>), and the medical malpractice insurer of the Harvard medical community, CRICO (<a href="http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html">http://hcrenewal.blogspot.com/2014/02/patient-safety-quality-healthcare.html</a>), have confirmed cases like this are no mere anecdotes.  I estimate from their numbers, and from cases known to me personally and from descriptions of others, that on the order of ten thousand (that's likely low) patients annually are being injured and/or die as a result of bad health IT in the U.S. alone.  Lack of transparency about such incidents impairs knowing the true numbers. <blockquote class="tr_bq">Ms Holley wept as she told the hearing of the moment she kissed her son goodbye, saying: "He was a kind and gentle boy with a great understanding of the world. "As we read Samuel his favourite stories, he died in our arms." Avon Coroner Maria Voisin, recording a narrative conclusion, ruled the booking system meant Samuel was not seen and did not receive treatment.</blockquote> This case somewhat reminds me of the case of a newborn whose x-ray test was done, but never looked at due to a bug in the software that scheduled films to be read, see <a href="http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html">http://hcrenewal.blogspot.com/2011/06/babys-death-spotlights-safety-risks.html</a>, case #2 <blockquote class="tr_bq">Concluding a three-day inquest at Flax Bourton Coroner's Court in North Somerset, Ms Voisin said: "Samuel Starr was born with a complex cardiac disease. "He required surgery and regular check-ups at outpatients to manage his conditions.  "Due to the failure of the hospital outpatients booking system there was a five month delay in Samuel being seen and receiving treatment. "Samuel's heart was disadvantaged and he died following urgent surgery."</blockquote> Just a "glitch." <blockquote class="tr_bq">Doctors diagnosed that Samuel had a restricted pulmonary artery - causing blood to easily flow away from his heart to his lungs - during a 20-week scan in pregnancy ... On March 3, 2010, Samuel underwent open heart surgery at Bristol Royal Hospital for Children. He was discharged six days later and referred to the Paediatric Cardiac Clinic at the Royal United Hospital (RUH) in Bath for check-ups. In October 2010, Samuel had his first check-up, in which an echocardiogram, also known as an "echo", was carried out. Ms Holley said she was told the procedure would be next carried out early in the new year. But it did not happen until April 2011 and an echo was not performed.  Paediatric cardiologist Dr Andrew Tometzki told the inquest he did not "deem it necessary" on that day to carry out the echo scan. Dr Tometzki then ordered a further review - where an echo scan would be carried out - in nine months' time. Samuel's parents did not receive information about the check-up and raised their concerns with community children's nurse Clare Mees. Ms Mees, who works for Sirona Lifetime Services, said she would chase up the matter with Dr Tometzki's secretary. Medical secretary Annabelle Attridge insisted she had taken details and forwarded them on to a dedicated appointments team. However, the inquest heard "glitch problems" with a new booking system meant the appointment was not logged.  </blockquote> Apparently not due to human fault: <blockquote class="tr_bq">Paediatric clinic co-ordinator Donna McMahon said while Samuel's medical records had been created on the new Millennium computer programme, no appointments had been transferred across.</blockquote> Just a "glitch."  Just a "bump in the road." <blockquote class="tr_bq">Ms McMahon said she was first aware of the appointment delay when she received an email from nurse Ms Mees in May 2012. Samuel did not have the vital check-up until June 21. Coroner Ms Voisin added: "This overall failure led to a five month delay in Samuel being seen by his cardiologist. "This meant Samuel had not been seen for five months and had not had an echo for 20 months." His parents were horrified when Dr Tometzki informed them Samuel required heart surgery that spring.</blockquote> Just a "glitch."  Just a "bump in the road." <blockquote class="tr_bq">... "Just hours before his operation Samuel was dancing around the ward and telling the nurses all about Spiderman - we had to remind him to quieten down," Ms Holley said. Samuel's chest was closed on August 8. As he was brought out of sedation on August 9, he suffered a stroke and cardiac arrests. "It is clear that if the surgery had been performed earlier, the procedure would have been the same," Ms Voisin said. But she said expert evidence found that as time went on "the more complicated the surgery is, as the more disadvantaged the heart is and the more difficult it is to get over the operation".</blockquote> Delays in care of fragile patients - in this case a young child, but in many other cases, ED and ICU patients of all ages - is very unwise. <blockquote class="tr_bq">Samuel's condition continued to deteriorate and on September 6 his parents were recommended for treatment to be withdrawn after he had a second cardiac arrest. The coroner said she would not write a report making recommendations to the hospital, as changes had already been implemented.</blockquote> Likely, workarounds to bad health IT, inviting future catastrophe. In my view, many cases such as this never make headlines, as the findings ignore the role of the IT and blame people, cases are settled with gag clauses, patients (who survive) or family are never told of the role of the IT, or lawsuits prove too expensive or too unpleasant to pursue. But patient safety is never compromised by "glitches", and regulation will just stifle innovation. My condolences to the parents.  I've suffered a death in my own family as a result of health IT, and I'm a specialist in the field.  Laypeople have no chance. One should pray the next child affected in this way is not one's own. -- SS Mar. 25, 2014 addendum:   Also see these related posts, the first mentioning "teething problems", another euphemism for potentially-deadly EHR malfunctions: <blockquote class="tr_bq">Cerner's Blitzkrieg on London: Where's the RAF?  <a href="http://hcrenewal.blogspot.com/2010/08/cerners-blitzkrieg-on-london-wheres-raf.html">http://hcrenewal.blogspot.com/2010/08/cerners-blitzkrieg-on-london-wheres-raf.html</a>  North Bristol Hits Appointment Problems: Another "Our Lousy IT Systems Screwed Up, But Patient Safety Was Never Compromised" Story <a href="http://hcrenewal.blogspot.com/2012/01/another-our-crappy-computers-screwed-up.html">http://hcrenewal.blogspot.com/2012/01/another-our-crappy-computers-screwed-up.html</a></blockquote> -- SS

This EHR "glitch" killed three-year-old Samuel Starr - but patient safety was not compromised

Actually, safety was compromised. I have written repeatedly that the term "glitch", an often-seen euphemism (usually accompanied w...

Đọc thêm »

UK: Another Example of IT Malpractice With Bad Health IT (BHIT) Affecting Thousands of Patients, But, As Always, Patient Care Was "Not Compromised"

<div class="post-title entry-title" itemprop="name">At my Dec. 2011 post "<a href="http://hcrenewal.blogspot.com/2011/12/yet-another-glitch-affecting-thousands.html" target="_blank">IT Malpractice? Yet Another "Glitch" Affecting Thousands of Patients. Of Course, As Always, Patient Care Was "Not Compromised</a>" and others, I noted:</div><div class="post-title entry-title" itemprop="name"> </div><blockquote class="tr_bq">... claims [in stories regarding health IT failure] that "no patients were harmed" ... are both misleading and irrelevant: Such claims of 'massive EHR outage benevolence' are misleading, in that medical errors due to electronic outages might not appear for days or weeks after the outage ... Claims of 'massive EHR outage benevolence' are also irrelevant in that, even if there was no catastrophe directly coincident with the outage, their was greatly elevated risk. Sooner or later, such outages will maim and kill.</blockquote> Here is a prime example of why I've opined at my Sept. 2012 post "<a href="http://hcrenewal.blogspot.com/2012/09/good-health-it-v-bad-health-it-paper-is.html" target="_blank">Good Health IT (GHIT) v. Bad Health IT (BHIT): Paper is Better Than The Latter</a>" that a good or even average paper-based medical record keeping system can facilitate safer and better provision of care than a system based on bad health IT (BHIT). Try this with paper: <blockquote class="tr_bq"><a href="http://www.independent.co.uk/life-style/health-and-families/health-news/nhs-coverup-over-lost-cancer-patient-records-8191066.html" target="_blank">NHS 'cover-up' over lost cancer patient records</a> Thousands awaiting treatment were kept in the dark for five months when data disappeared Sanchez Manning The Independent Sunday 30 September 2012 Britain's largest NHS trust took five months to tell patients it had mislaid medical records for thousands of people waiting for cancer tests and other urgent treatments. Imperial College Healthcare NHS Trust discovered in January that a serious computer problem and staff mistakes had played havoc with patient waiting lists.</blockquote> It's quite likely the "serious computer problem" far outweighed the impact of "staff mistakes", as disappearing computer data does so in a "silent" manner.  One does not realize it's missing as there's not generally a trail of evidence that it's gone. <blockquote class="tr_bq"> About 2,500 patients were forced to wait longer on the waiting lists than the NHS's targets, and the trust had no idea whether another 3,000 suspected cancer patients on the waiting list had been given potentially life-saving tests. Despite the fact that the trust discovered discrepancies in January and was forced to launch an internal review into the mess, including 74 cases where patients died, it did not tell GPs about the lost records until May.</blockquote> That is, quite frankly, outrageous if true and (at least in the U.S.) might be considered <a href="http://legal-dictionary.thefreedictionary.com/Criminal+Negligence" target="_blank">criminally negligent</a> (failure to use reasonable care to avoid consequences that threaten or harm the safety of the public and that are the foreseeable outcome of acting in a particular manner). <blockquote class="tr_bq">Revelations about the delay prompted a furious response yesterday from GPs, local authorities and patients' groups. Dr Tony Grewal, one of the GPs who had made referrals to Imperial, said doctors should have been told sooner to allow them to trace patients whose records were missing. "The trust should have contacted us as soon as it was recognised that patients with potentially serious illnesses had been failed by a system," he said. "GPs hold the ultimate responsibility for their patient care."</blockquote> That is axiomatic. <blockquote class="tr_bq">The chief executive of the Patients Association, Katherine Murphy, added: "This is unacceptable for any patient who has had any investigation, but especially patients awaiting cancer results, where every day counts. The trust has a duty to contact GPs who referred the patients. It's unfair on the patients to have this stress and worry, and the trust should not have tried to hide the fact that they had lost these records. They should have let the GPs know at the outset."</blockquote> Unfair to the patients is an understatement,  However, if one's attitude is that computers have more rights than patients, as many on the health IT sector seem to with their ignoring of patient rights such as informed consent, lack of safety regulation, and lack of accountability, then it's quite acceptable. <blockquote class="tr_bq">The trust defended the delay in alerting GPs, arguing that it needed to check accurately how much data it had lost before making the matter public. It said a clinical review had now concluded that no one died as a result of patients waiting longer for tests or care.</blockquote> That would be perhaps OK if the subjects whose "data had been lost" through IT malpractice were lab rats. <blockquote class="tr_bq">Despite this, three London councils – Westminster, Kensington and Chelsea, and Hammersmith and Fulham – are deeply critical of the way the trust handled the data loss. Sarah Richardson, a Westminster councillor who heads the council's health scrutiny committee, said that trust bosses had attempted to "cover up" the extent of the debacle. "Yes, they've done what they can but, in doing so, [they] put the reputation of the trust first," she said. "Rather than share it with the GPs, patients and us, they thought how can we manage this information internally. They chose to consider their reputation over patient care."</blockquote> As at my Oct. 2011 post "<a href="http://hcrenewal.blogspot.com/2011/10/cybernetik-uber-alles-computers-have.html" target="_blank">Cybernetik Über Alles: Computers Have More Rights Than Patients?</a>", to be more specific, they may have put the reputation of the Trust's computers first.  <blockquote class="tr_bq">Last week, it was revealed that Imperial has been fined £1m by NHS North West London for the failures that led to patient data going missing. On Wednesday, an external review into the lost records said a "serious management failure" was to blame for the blunder.</blockquote> Management of what, one might ask? <blockquote class="tr_bq">Imperial's chief financial officer, Bill Shields, admitted at a meeting with the councils that the letter could have been produced more quickly. He said that, at the time, the trust had operated with "antiquated computer systems" and had a "light-touch regime" on elective waiting times.</blockquote> Version 2.0A will, as again is a typical refrain, fix all the problems. <blockquote class="tr_bq">Terry Hanafin, the leading management consultant who wrote the report, said the data problems went back to 2008 and had built up over almost four years until mid-2011. Mr Hanafin said the priorities of senior managers at that time were the casualty department and finance.</blockquote> Clinical computing is not business computing, I state for the thousandth time.  When medical data is discovered "lost", the only response should be ... find it, or inform patients and clinicians - immediately. <blockquote class="tr_bq">He further concluded that while the delays in care turned out to be non-life threatening, they had the potential to cause pain, distress and, in the case of cancer patients, "more serious consequences" ... The trust said it had found no evidence of clinical harm and stressed that new systems have now been implemented to record patient data. It denied trying to cover up its mistakes or put its reputation before concerns for patients. "Patient safety is always our top priority," said a spokesman.</blockquote> "More serious consequences" is a euphemism for horrible metastatic cancer and death, I might add.  The leaders simply cannot claim they "found no evidence of clinical harm" regarding delays in cancer diagnosis and treatment until time has passed, and followup studies performed on this group of patients. This refrain is evidence these folks are either lying, CYA-style, or have no understanding of clinical medicine whatsoever - in which case their responsibilities over the clinic need to be ended in my opinion. I, for one, would like to know the exact nature of the "computer problem", who was responsible, and if it was a software bug, how such software was validated and how it got into production. -- SS Oct. 1, 2012 Addendum: What was behind the problems, according to another source?    Bad Health IT (BHIT): <blockquote class="tr_bq"><a href="http://www.ehi.co.uk/news/EHI/8094/poor-it-behind-imperial-cancer-problems" target="_blank">Poor IT behind Imperial cancer problems</a> e-Health Insider 28 September 2012 Rebecca Todd An independent review of data quality issues affecting cancer patient referrals to Imperial College Healthcare NHS Trust has identified “poor computer systems” as a key cause of the problem. The review’s report highlights the trust’s use of up to 17 different IT systems as causing problems for patient tracking. However, it says the trust should be aware of the risks of [replacing the BHIT and] moving to a single system, Cerner Millennium, because of reported problems in providing performance data after similar moves at other London trusts. In January 2012, the report says the NHS Intensive Support Team was reviewing the way reports on cancer waiting times were created from Imperial’s cancer IT system, Excelicare. The team discovered that almost 3,000 patients were still on open pathways who should have been seen within two weeks. In May, letters were sent to GPs to try and ascertain the clinical status of around 1,000 patients.</blockquote> BHIT must be forbidden from real-world deployments, and fixed rapidly or dismantled (as Imperial College Healthcare NHS Trust appears to be doing), although the "solution" might be just as bad, or worse, than the disease. -- SS

UK: Another Example of IT Malpractice With Bad Health IT (BHIT) Affecting Thousands of Patients, But, As Always, Patient Care Was "Not Compromised"

At my Dec. 2011 post " IT Malpractice? Yet Another "Glitch" Affecting Thousands of Patients. Of Course, As Always, Patient C...

Đọc thêm »

Key lesson from the NPfIT - The Tony Collins Blog

ComputerWorldUK.com <a href="http://blogs.computerworlduk.com/the-tony-collins-blog/2011/05/the-national-programme-of-failed-it-in-the-nhs/"></a><blockquote><a href="http://blogs.computerworlduk.com/the-tony-collins-blog/2011/05/the-national-programme-of-failed-it-in-the-nhs/">Key lesson from the NPfIT - The Tony Collins Blog</a> Listening to critics is critical to the success of big projects. But has this lesson been learnt? Published 07:56, 20 May 11 A US doctor Scot Silverstein, who has an expertise in clinical IT design, says of the NAO report on the NPfIT that the initials should stand for: "National Programme of Failed IT.”He says on the blog <a href="http://hcrenewal.blogspot.com/2011/05/national-programme-of-failed-it-in-uk.html">Health Care Renewal</a>:"Perhaps the NPfIT (National Programme for IT in the NHS) should be renamed the "National Programme of Failed IT in the NHS." No new acronym will be needed.</blockquote>Read the entire ComputerWorldUK piece by Tony Collins. Some of the excuses and rationalizations described during this programme are simply stunning.This idea, though, I find fascinating:<blockquote>One of the lessons that emerges from disastrous business decisions, as recorded on the excellent BBC2 series "<a href="http://www3.open.ac.uk/media/fullstory.aspx?id=21194">Business Nightmares"</a> with Evan Davis, is that expensive new ideas should be tested, and repeatedly tested, by the harshest critics of those ideas. </blockquote>-- SS

Key lesson from the NPfIT - The Tony Collins Blog

ComputerWorldUK .com Key lesson from the NPfIT - The Tony Collins Blog Listening to critics is critical to the success of big projects. But ...

Đọc thêm »

UK: ISO draft standards for the development, manufacture and deployment of healthcare IT focus on SAFETY

The UK's NHS has not had the best of success to date implementing national health IT, as indicated by reports <a href="http://www.publications.parliament.uk/pa/cm200809/cmselect/cmpubacc/153/15304.htm">here</a> and <a href="http://www.connectingforhealth.nhs.uk/about/foi">here</a>, for example. However, they have appeared to have learned from their mistakes and in fact are on the way to being far ahead of the U.S. in terms of understanding what it truly takes for HIT to be efficacious - and perhaps even more importantly, as safe as possible. From an informatics colleague who informed me of these developments: <blockquote>The UK has recently adopted the ISO draft standards for the development and deployment of HIT. They don't go as far as premarket approval, but do require vendors to develop and deliver to healthcare organizations a formal hazard assessment for their products, require both to continually update their risk assessments, and require care delivery organizations to have an explicit process for identifying & mitigating risks, and formally accepting (or not) the residual risks that remain. The thinking is these standards will be adopted across the EU once the ISO approval process is completed.</blockquote> These two remarkable documents are available from the UK's NHS: <div class="PlainText"><blockquote><a href="http://www.isb.nhs.uk/documents/isb-0160/dscn-18-2009">http://www.isb.nhs.uk/documents/isb-0160/dscn-18-2009</a> "Health informatics — Guidance on the management of clinical risk relating to the deployment and use of health software" Formerly ISO/TR 29322:2008(E) DSCN18/2009 and <a href="http://www.isb.nhs.uk/documents/isb-0129/dscn-14-2009">http://www.isb.nhs.uk/documents/isb-0129/dscn-14-2009</a> "Health Informatics — Application of clinical risk management to the manufacture of health software" Formerly ISO/TS 29321:2008(E) DSCN14/2009 </blockquote> From the first of these, the overall intro: <blockquote>ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.</blockquote> Then on to matters at hand: <blockquote>Introduction The threat to patient safety There is mounting concern around the world about the substantial number of avoidable clinical incidents which have an adverse effect on patients, of which a significant proportion result in avoidable death or serious disability, see references [1], [2], [3], [4], [5] and [6]. A number of such avoidable incidents involved poor or "wrong" diagnoses or other decisions. A contributing factor is often missing or incomplete information, or simply ignorance, e.g. of clinical options in difficult circumstances or of the cross-reaction of treatments (a substantial percentage of clinical incidents are related to missing or incomplete information). It is increasingly claimed that information systems such as decision support, protocols, guidelines and pathways could markedly reduce such adverse effects. [As I have written in many places such as <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=2009">here</a> and <a href="http://hcrenewal.blogspot.com/2010/07/new-england-journal-on-meaningful-use.html">here</a>, this may or may not be true regarding today's commercial healthcare IT as it is currently designed and deployed. Evidence supporting the assertion, especially robust studies such as randomized controlled clinical trials, is scarce, and evidence contradicting it is growing. The technology remains experimental - ed.] If for no other reason – and there are others – this is leading to increasing deployment and use of increasingly complex health software systems, such as for decision support and disease management. It can also be anticipated that, due to pressures on time and to medico-legal aspects, clinicians will increasingly rely on such systems, with less questioning of their "output", as a "foreground" part of care delivery rather than as a "background" adjunct to it. Indeed, as such systems become integrated with medical care, any failure by clinicians to use standard support facilities may be criticised on legal grounds. Increased use of such systems is not only in clinical treatment but also in areas just as important to patient safety, such as referral decision-making. Failure to make a "correct" referral, or to make one "in time", can have serious consequences. Economic pressures are also leading to more decision support systems. The area of generic and/or economic prescribing is the most obvious, but achieving economy in the number and costs of clinical investigative tests is another. Thus the use of health software and medical devices in increasingly integrated systems, e.g. networks, can bring substantial benefit to patients. However unless they are proven to be safe and fit for purpose they may also present potential for harm or at least deter clinical and other health delivery staff from making use of them, to the ultimate detriment of patients. Annex A provides some examples of the potential for harm. Harm can of course result from unquestioning and/or non-professional use, although the manufacturers of health software products, and those in health organizations deploying and using such products within systems, can mitigate such circumstances through, for example, instructions for use, training and on-screen presentation techniques, guidance, warnings or instructions. Some of these system deficiencies are insidious, may be invisible to the end user [an obviously perilous situation - ed.] and are typically out of the sole control of either the manufacturer or the deploying health organization.</blockquote> The reports note the obvious, something that the health IT vendors' <a href="http://www.ischool.drexel.edu/faculty/ssilverstein/cases/?loc=cases&sloc=koppel_kreda">contractual gag clauses</a> and secrecy in the health IT industry make difficult to rigorously evaluate: <blockquote>A necessary pre-cursor for determining and implementing controls to minimize risks to patients, from a health software systems that is manufactured and then deployed and used within a health organization, is a clear understanding of the risks which the deployed system might present to patients if malfunction or an unintended event were to occur, and the likelihood of such a malfunction or event causing harm to the patient.</blockquote> These risks cannot be properly evaluated in an industry where the flows of information are dominated by the vendors. Some examples of potential for harm, from annex (appendix) A, will likely sound quite familiar to readers of Healthcare Renewal: <ul><li>Patient (mis)identification</li><li>Inadvertent accidental prescribing of dangerous drugs (such as methotrexate)</li><li>Incorrect patient details retrieved from radiology information system</li><li>CT and MRI images could not be seen after being moved to PACS</li><li>Drug mapping error</li><li>Pre-natal screening risk computation errors</li><li>Radiotherapy errors</li><li>Slack security</li></ul> I especially note the following in the first document (on deployment): <blockquote>5.3 Competencies of personnel Persons performing risk management tasks will need to have the knowledge, experience and competencies appropriate to the tasks assigned to them. This will need to include, where appropriate, knowledge and experience of the particular health software systems (or similar health software products) and applications, the technologies involved and risk management techniques. This should include appropriate registered clinical input throughout the process. Appropriate competency and experience records will need to be maintained. Clinical risk management tasks can, and should, be performed by a project team that contains representatives of each of the functions that are involved in deploying and subsequently using the health software systems or system, with each contributing their specialist knowledge to build both awareness and consensus. Of particular importance will be clinical input from clinicians who are familiar with the practical realities of the environments within which the software system will be used and the clinical processes to which the software system is directed. </blockquote> Emphasis on the last sentence is mine. At a time when U.S. CIOs and health IT "talking heads" still find the need to write touchy-feely "Master of the Obvious" articles extolling the virtues of permitting clinicians 'input' into health IT projects, usually under the aegis of unempowered "Directors of Informatics" or "Chief Medical Information Officers" (a.k.a. Directors of Nothing and Chiefs of Nothing, with no true executive presence or authority), the latter direct, definitive sentence is refreshing. Miracle of miracles, even postmarketing surveillance is covered (the pharma and medical device industries have been mandated by regulators to conduct such studies on their products for decades): <blockquote>11 Post-deployment monitoring Both manufacturers and organizations deploying and using health software and other products within systems, have a business need to establish, document and maintain a process to collect and review information about the clinical safety performance of the products and system in the post-deployment phase, at least to help manage their liabilities but also to enable them to optimize their products and systems.</blockquote> There is much more in these documents. Download and read the PDF's. I will have more to say in future posts, but thank god someone is considering the risks to patients of this technology, touted as universally beneficent by health IT exceptionalists, in a serious manner. Now if only we can import this thinking into the United States. -- SS </div>

UK: ISO draft standards for the development, manufacture and deployment of healthcare IT focus on SAFETY

The UK's NHS has not had the best of success to date implementing national health IT, as indicated by reports here and here , for examp...

Đọc thêm »