Showing posts with label healthcare IT defects. Show all posts
Showing posts with label healthcare IT defects. Show all posts

Wednesday, October 20, 2010

Medical center has more than 6000 "issues" with Cerner CPOE system in four months - has patient harm resulted?

As I have written at Healthcare Renewal before, computerized physician order entry systems (CPOE's) are known to present risks to patients through induction of medical errors.

This technology is held out to be ready for national diffusion, right up to the POTUS. Per ONC director Blumenthal in the July 13, 2010 NEJM:

The widespread use of electronic health records (EHRs) in the United States is inevitable. EHRs will improve caregivers’ decisions and patients’ outcomes. Once patients experience the benefits of this technology, they will demand nothing less from their providers. Hundreds of thousands of physicians have already seen these benefits in their clinical practice.

Vendors deny major problems with their CPOE and other health IT products.

The true story is a bit more complex.

Fortunately, there are some medical centers who are open and honest about HIT problems. These medical centers seem a rarity. However, those that do share are actually conducting themselves in an honorable and mission-true manner, per Joint Commission Safety Standards, the ethics of the medical profession, and the expectations of the public. They should be commended.

One such example is Munson Medical Center in Michigan.

From the October 2010 "News for Physicians affiliated with Munson Medical Center" newsletter, a large medical center in Northern Michigan, about more than six thousand "issues" with their Cerner CPOE:

POE Program Continues to be Improved, Enhanced

The Provider Order Entry (POE) program continues to be improved. Since implementation in June [four months ago - ed.], more than 6,000 issues have been reported. Issues are defined as an aspect of the program not working as intended [does that include medication and treatment errors and 'near-misses'? - ed.], process issues [can these 'issues' kill? - ed.], education needs, or PowerPlan [Cerner - ed.] change requests.

About 600 of these remain open. Issues are prioritized by the POE Team and addressed according to existing standards.

One wonders how many of those 6,000, and how many of the 600 remaining "issues" fall into categories of "likely to cause patient harm in short term if uncorrected" or "may cause in patient harm in medium or long term."

I note that Cerner CPOE is not a new product, nor are similar products from other vendors also afflicted with long lists of "issues." That there could be more than 6,000 "issues" at a new site suggests deep rooted, severe problems with CPOE specifically and health IT design and implementation processes in general.

Did patient harm result here or at other CPOE sites (using products of any vendor, not just this one) that had hundreds or thousands of "issues"? We may never know.

That national rollout is mandated as if this technology were proven, safe, and plug and play is a scandal of UK NPfIT-like proportions.

-- SS

Friday, March 5, 2010

Computers and Prostate Problems in Pennsylvania, East and West

At "Bungled Brachytherapy, Computer Interfaces and Other Mysteries At The Philadelphia Veterans Administration Hospital" at this link I reported on serious problems involving brachytherapy treatment of prostate cancer at the VA Medical Center in Philadelphia.

One of the issues involved computer problems, in the form of failure to network a key computer involved in treatment evaluation.

Now at the other end of the state, Pittsburgh, more prostate-related computer problems have occurred:

Prostate cancer test interpretation flawed
By Walter F. Roche Jr.
PITTSBURGH TRIBUNE-REVIEW
Friday, March 5, 2010

A computer programming error caused West Penn Allegheny Health System's laboratory to send physicians incorrect interpretations of prostate cancer tests for 288 patients over 15 months.

Hospital officials say physicians who ordered the tests were advised about the errors in recent weeks. They were sent revised, corrected interpretations, said Dr. Jan F. Silverman, chairman of the Department of Pathology and Laboratory Medicine.


One wonders how such a "programming error" can occur.

Silverman said actual test results were correct, and most physicians would rely on those and not interpretations. He said hospital officials found no evidence that incorrect test interpretations resulted in delayed or improper care ... The erroneous interpretations were provided on a test physicians use to assess whether patients need biopsies of their prostates. The test provides a comparison of total prostate specific antigen, or PSA, versus free or non-attached PSA.

That there was no apparent delayed or improper care was by happenstance. The purpose of health IT, however, is not to give physicians the opportunity to have a lucky day, or to have placed upon them the additional cognitive burden of deciding which is correct: the test results, or its interpretation.

This episode raises another question: in addition to whatever "programming error" caused this problem, was there no QC of the actual reports to ensure the "interpretation" matched the pathological, serological and other results and findings?

Dr. Ralph Miller, head of the Allegheny Prostate Cancer Center, said it was "theoretically possible, but very, very unlikely" that erroneous interpretations resulted in delayed or improper care.

[That may be true, but is it due to luck and/or the inconvenient fact that most physicians 'did not rely' (i.e., ignored) the computer-generated interpretations? Also, will luck run out the next time a "programming error" occurs, resulting in dead patients? - ed.]

Silverman said those interpretations were sent between Oct. 1, 2008 and January. Of 818 PSA tests the West Penn Allegheny Core Laboratory performed during that period, 412 included comparisons of the two PSA figures. Of those, 288 included incorrect interpretations of that ratio, Silverman said.


That's a very high percentage of error. Should that have occurred in a drug trial, the FDA would likely have been all over the responsible parties. However, health IT is unregulated, therefore all that's required is an "please excuse us, we'll do better the next time" from the involved parties.

The programming error was discovered recently when a physician questioned an interpretation, Silverman said.

I have written before on these electronic pages that physicians and clinical settings should not be the testing labs for IT personnel, with the clinicians using their clinical skills in locating programming bugs.

-- SS

Wednesday, January 20, 2010

Senator Grassley asks hospitals about experiences with federal health information technology program

At a brief Oct. 24, 2009 posting "Washington Post: EMR's No Cure-All; Sen. Grassley Sends Letter of Inquiry to health IT vendors" (link) I mentioned an Oct. 16, 2009 letter to major healthcare IT vendors from Senator Charles E. Grassley (ranking member of the United States Senate Committee on Finance) initiating a Senate investigation of corporate practices. That letter is here (PDF).

A followup investigation has now begun by Sen. Grassley of hospitals themselves. Here is a link to his Senate website and a copy of the new letter dated Jan. 20, 2010.

This followup letter is being sent to:

Banner Health, Brigham & Women's Hospital Case Western Reserve University Hospital Health System, Catholic Healthcare West, Cedars Sinai Children’s National Medical Center, Geisinger Medical Center, Hackensack Hospital, HCA TriStar, Intermountain Healthcare, Indiana University Hospital, Jefferson Regional Medical Center, Kaiser Permanente System, Marshfield Clinic, Massachusetts General Hospital, Mayo Clinics, Memorial Hermann Healthcare System, Methodist Hospital of Indiana, North Shore-Long Island Jewish Health System, Palo Alto Medical Foundation, Rainbow Babies and Children’s Hospital, Saint Mary Mercy Hospital, Seattle Children’s Hospital, Stony Brook University Medical Center, Trinity Hospital System Tufts Medical Center, University of California San Francisco Medical Center, University of Pennsylvania Health System, University of Pittsburgh Medical Center, University of Virginia Medical Center, and Vanderbilt University Hospital.

According to Huffington Post Investigative Fund reporters Fred Schulte and Emma Schwartz in "Electronic Health Records Probe Expands to Hospitals", these organizations were chosen based on both "positive and negative" press reports, complaints, whistleblowers, and Grassley's own research. The Huffington Post quoted Sen. Grassley's spokesperson Jill Gerber in that regard.

The questions are probing:

1. Please describe in detail your facility’s process for identifying HIT products for purchase and choosing an HIT vendor(s).

a. What is the personnel structure of those involved in the purchase?
b. To what extent do physicians and other health care providers within your facility provide input regarding the specific HIT items to be implemented within your facility?
c. Who or what department within your facility is responsible for making HIT purchase decisions?


I have been writing for years on the strategically unsound practice of hospitals leaving these processes up to business IT (MIS) personnel and other non-clinical management, perhaps only then seeking a qualified physician information technology expert - or more typically, appointing a figurehead physician IT amateur - after the acquisition. That person is tasked with "making it all work" and convincing other doctors to use the technology.

(I use the term "figurehead" in that the incumbent Clinician Director of HIT or Chief Medical Information Officer/CMIO usually is an "internal consultant" with no direct control over resources or personnel, a Director of Nothing or Chief of Nothing if you will. I use the term "amateur" in the same sense that I am a telecommunications amateur, fine for an avocation but not for a lead role in a mission-critical setting.)


2. Three of the companies that I wrote to in October 2009 informed me that they do not manufacture HIT software or hardware, but instead assist their health care clients, such as hospitals, with the implementation and management of HIT systems. To what extent do you contract with such entities to assist with the purchase, implementation and/or management of HIT products in your facility?


I have also written on the huge amount of precious healthcare money wasted on management consulting companies for health IT, when a fraction of that money could pay for in-house, permanent expertise.

3. Please describe the training process implemented in your facility to familiarize employees with new technology systems.

a. How does your facility budget for HIT training?
b. What are the vendors’ roles in helping your facility train in the use of their products?


I sincerely hope these hospitals have not "shorted" training. On the other hand, that these systems require extensive training to use properly is part of the problem. Finally, no manner of training can compensate adequately for mission hostile health IT.


4. Does your facility have any policies or processes governing the reporting of problems or concerns by your health care employees related to the HIT products or systems implemented in your facility? If so, please provide a description of the policies or processes. If not, please explain why not.


I would have added "effective policies or procedures" to that question.


5. When patient care and/or safety problems related to HIT systems arise, how are these problems reported within the facility and what is the process or mechanism for addressing them?

a. Are these problems also reported to the HIT vendor, and if so, what is the process for reporting them?
b. If patient care and/or safety problems related to HIT systems are not routinely reported to the HIT vendors, please explain how your facility decides which problems or issues are reported to a vendor and/or addressed by a vendor and which problems are addressed internally by the facility.


These are questions about fundamental processes of quality control of the IT devices themselves. It would perhaps be a criminal affair if pharmaceutical companies and medical device companies did not have such processes in place regarding their products.


6. Please describe in detail any system your facility has in place to document, track, catalogue, and maintain complaints, concerns or issues related to HIT products that may directly or indirectly involve or impact the delivery of care or patient safety.


One would think there would be a robust database or library of such issues at every hospital deploying HIT. Not having such a resource would in my opinion reflect negligence in both the IT and clinical domains. It will be interesting to see the contents, or if they do not exist, the reasons why.


7. Please provide a list of HIT problems or complaints that have been identified by or reported to your facility since January 2008 that directly or indirectly impacted patient safety or the delivery of care, including any complications or adverse events that have occurred as a result of HIT product design and/or usability. Please describe whether and how each of those problems or complaints was resolved and whether these issues have resulted in a change in policy to prevent the problem in the future.


The answers should prove interesting. Hopefully, "near misses" are accounted for in prior questions.


8. Does your facility have policies regarding the discussion of problems in your HIT systems with other health care facilities or with government officials or any individuals or entities outside your facility? If so, please describe those policies. To what extent are these policies driven by contractual agreements with the HIT vendors, and to what extent do they stem from internal processes? Please provide examples of contracts with HIT vendors that include non-disclosure clauses.


Considering the widespread and uncomfortably similar stories people in my field have been hearing for quite awhile (in my case, for the past fifteen+ years), and as I have written before, there seems to be very little cross-institutional knowledge sharing on HIT pitfalls.

It was, in fact, not easy to get a book about HIT problems published for a wide audience - even in a de-identified form - in 2009. Most accounts of health IT consist of what Greenhalgh calls "sanitized accounts of project success."

These accounts are of little didactic value in helping other organizations avoid known deleterious practices (such as talent mismanagement, internal strife, failure to adapt IT to the environment, over-reliance on vendor promises, contract pitfalls, etc.) leading to HIT failure.


9. Some of the HIT vendors stated specifically in their responses to me that they do not include language that would hold them harmless for failures of their products or for the company’s own negligence or recklessness. However, they may include provisions that spell out the vendor’s and the health care client’s respective legal responsibilities and obligations in the use of the product. For example, one vendor stated that it is accountable for the performance of its product as long as the client uses the product appropriately. Another vendor stated that it is not liable when harm or loss results from the client’s use of the product in diagnosing and/or treating patients.

a. Do any of the HIT vendors include language in their contracts with your facility that could be considered “hold harmless” provisions, i.e., the transferring of liability associated with the services or products provided to your facility, or otherwise limit their liability? If so, please provide a copy of sample contracts containing such provisions.


Denial of inclusion of "hold harmless" provisions on the one hand, and statements about being "accountable for the performance of its product as long as the client uses the product appropriately" (whatever that means) and "not [being] liable when harm or loss results from the client’s use of the product in diagnosing and/or treating patients" (what are such systems for, playing Pong?) on the other hand, seem to be at odds.


10. What is the relationship between your facility and any HIT vendors?


a. HIT vendors that manufacture software, hardware and/or other products purchased by health care facilities have stated in their responses to me that they do not offer any financial incentives for purchasing their products, such as shares in the company or financial interests in a particular product. At least one vendor stated, however, that it does offer financial incentives in the form of discounts based on purchase size. Another vendor said that health care clients may receive royalty payments when the clients collaborate with the vendor to develop a product. What financial interest, if any, does your facility have in HIT vendors and/or their products?


b. Do the vendors offer your facility and/or any of your health care providers any financial incentives for purchasing the vendors’ products? If so, please describe the types and value of the incentives.


These are clearly questions about conflict of interest. My best advice to these organizations is "be honest."


11. Did your staff, health care providers and/or facility receive any payments, product discounts, or other items of value from any vendor for discussing and/or promoting that vendor’s HIT products? If so, please list the different types of payments and discounts and their value.


This is a question along the lines of the "Key Opinion Leaders" nurtured by pharmas with a green fertilizer that comes from trees, not cows. One vendor did seem to indicate that this occurs in the "10 secrets the EHR companies don't want you to know" essay here.

While that essay must be taken with a grain of salt, it would not surprise me to find out the HIT industry and the pharma industry share practices in common. Today's B-schools and our current dishonest culture produce the leaders and officers of both, after all.

-- SS

Monday, December 28, 2009

Are Dissmissive Industry and Government Reactions to Physician Concerns about EHR's and other Clinical IT Simply Perverse?

Yes, they are.

At the Nov. 10, 2009 essay "Academic Freedom and ED EHR's Down Under: Another Update and a Welcome Development" and preceding essays linked to it, I wrote about an Australian informatics professor's travails in writing about ED EHR's.

He wrote a mixed-method essay about the mission hostile user experiences ED physicians in NSW reported about the EHR's they were being compelled to use, in addition to similar negative commentary from ED physician experts in other lands. The latest version of the paper "A Critical Essay on the Deployment of an ED Clinical Information System ‐ Systemic Failure or Bad Luck" is here (PDF) or accessible from his department's webpage here.

The government attempted to censor the paper and likely censure the author, and I speculate the HIT industry was not far behind.

Below is an example from my own city on why I found the reactions to the evolving ED EHR paper - reactions that "blamed the doctors" or dismissed what appear to be frequently encountered ED physician concerns - perverse.

I use the term "perverse" in the most formal sense of the word:
Merriam-Webster dictionary:

Perverse (adj).
Etymology: Middle English, from Anglo-French purvers, pervers, from Latin perversus, from past participle of pervertere
Date: 14th century

1 a : turned away from what is right or good : corrupt b : improper, incorrect c : contrary to the evidence or the direction of the judge on a point of law
2 a : obstinate in opposing what is right, reasonable, or accepted : wrongheaded b : arising from or indicative of stubbornness or obstinacy
3 : marked by peevishness or petulance : cranky
4 : marked by perversion : perverted


The very, very last thing patients need is to have ED clinicians slowed down.

Concerns expressed by even a minority of ED physicians that EHR's slow them down or reduce their effectiveness ought to set off alarm bells and rigorous government investigations of the kind that would arise if airline pilots started to complain about lax security allowing passengers on board with bombs:

Dec 24, 2009
Philadelphia Inquirer

Philadelphia ERs seek solutions to crowding

By Marie McCullough

Inquirer Staff Writer

Two of the region's leading medical centers have racked up the city's highest number of "diversions" - periods when ambulances are advised to steer clear because the emergency room is so full.

The Hospital of the University of Pennsylvania and Thomas Jefferson University Hospital are working to reduce such diversions as the number of emergency rooms in the city has continued to fall. This year, Penn has reduced the disruptions by 22 percent and Jefferson by 28 percent.

As they seek solutions, the hospitals are examining their own practices, reflecting a national shift in efforts to address the perennial crisis of ER overcrowding.

Consider Jefferson. This year it reduced diversion hours even though the number of ER patients, the severity of their medical needs, and staffing stayed about the same. Jefferson relieved overcrowding by finding ways to move patients in and out of the ER - and the whole hospital - faster.

"That's where I'm focused, on improving efficiencies," said Rex Mathew, hired by Jefferson two years ago for the new job of vice president of emergency medicine clinical operations.

This is not to suggest that the nation's emergency medical-care system has been slacking. From 1992 to 2002, the number of annual emergency-room visits increased 23 percent, while the number of ERs decreased 15 percent, studies show.

In the Philadelphia region, the contraction has been more dramatic - from 62 ERs in 1993 to 38 now, a 39 percent decrease. The most recent loss was this year's closing of Northeastern Hospital, which had 45,000 emergency visits annually. The impact has been felt at Aria Health-Frankford Campus, where Joaquin Rivera died in the ER while waiting for care on Nov. 28.

While there is no evidence that overcrowding played a role in his death, Frankford had nearly as many diversions in November - 121 hours - as all of last year.

Emergency departments are beset by growing numbers of the uninsured, the chronically ill, and the aged.

Nonetheless, experts say it's time for hospitals to stop blaming ER overcrowding on economic, social, and demographic factors that are beyond their control, and start looking inward. A recent Government Accountability Office report found that even in life-and-death cases, large percentages of ER patients do not see doctors within recommended times.

"Many hospitals have done little to address the patient-flow obstacles that lead to overcrowded" emergency rooms, says a report by Urgent Matters, an ER improvement initiative funded by the Robert Wood Johnson Foundation.

Jefferson and Hahnemann University Hospital are among six U.S. hospitals using grants from Urgent Matters to develop practical strategies for reducing ER crowding. These will be shared nationally through newsletters, the Web, and conferences.

... Most fixes, however, are neither easy nor obvious. Sick patients may lie on gurneys for hours in ERs, uncomfortable and taking up precious space, while they wait for a hospital bed to become available.

... "The problem is not just physical space but effective space," said Robert McNamara, chair of emergency medicine at Temple University Hospital. "With hospital margins tight, there may be beds, but no staff to cover them. And hospitals try to keep staffing tight to keep costs down."

Temple has the city's busiest ER, with 74,000 adult and 20,000 pediatric patients this year - 24 percent of whom were admitted to the hospital, McNamara said. Anticipating a surge in demand following Northeastern's closure, Temple added ER staff and made a concerted effort to speed up testing and discharge procedures, he said.

This year, through November, Temple had 118 hours when ambulances were diverted.

The Hospital of the University of Pennsylvania, with about 60,000 ER patients and a 26 percent admission rate, was by far the city's leading diverter - more than 1,000 hours through November.

... the crowding conundrum continues to evolve. One question is whether health-care reform - which now seems imminent - may increase ER volume rather than reducing it, as millions more Americans become insured.

The situation is actually even worse.

A patient recently died of a heart attack, sitting in the waiting room of a hospital where I once rotated during my internship, Frankford Hospital. He was not found until others in the waiting room stole the dead patient-in-waiting's wristwatch. The man sat unresponsive for nearly an hour in the waiting area of Aria Health Frankford Hospital before a visitor notified security and a doctor arrived.

Dec. 1, 2009

Philadelphia Inquirer

Waiting to be seen at hospital, dying Joaquin Rivera was robbed, police say

... According to Philadelphia police, Rivera walked into Aria Health's Frankford Campus, on Frankford Avenue near Harrison Street, about 10:45 p.m. Saturday.

He was alone, and apparently had walked from his nearby home on Duffield Street near Foulkrod, his son said.

Rivera complained of feeling pain in his left arm and abdomen, and was told to sit in the waiting area, said police spokesman Lt. Frank Vanore. [A middle aged man with left arm and abdominal pain told to 'sit in the waiting room?' One wonders who would qualify for sitting under medical observation - ed.]

At some point during the next hour, Rivera, a longtime bilingual counselor at Olney High School, lost consciousness. He inadvertently became a target, Vanore said, to three other people in the waiting room...

[One of the other people] signed up to be seen by a doctor, while his two cohorts sat near Rivera. "At some point, [one of the people] is observed taking the victim's watch and passing it to the other man," Vanore said.

When a witness ran to notify a security guard of the crime and Rivera's condition, the limping man and his female partner fled, Vanore said. Hospital personnel rushed to Rivera's aid, but it was too late.

He was pronounced dead shortly after midnight Sunday. Vanore said police have not yet learned of Rivera's cause of death.

The family said he was believed to have died of a heart attack.


I reiterate, the very last thing in the world ER clinicians need are ill-conceived and ill-implemented electronic health records systems that slow them down.

Instead of attempted censorship and spin control, such concerns should be addressed throughly, impartially and promptly if not immediately.

What could one call the arrogance or devil-may-care mindset in the government and health IT industry that dismisses such concerns so cavalierly, other than "perverse?"

-- SS

Friday, December 18, 2009

Arguments for Maintaining the Health IT Status Quo on Defects Nondisclosure Clauses

As I wrote at Healthcare Renewal here, I recently posted a web petition "Transparency and Openness in Electronic Patient Records and Other Healthcare Information Technology Systems" at http://www.webpetitions.com/cgi-bin/print_petition.cgi?99504454 , calling for an end to Nondisclosure Clauses [of defects, problems, EHR-related adverse events, etc.] in HIT contracts. The petition reads:

We, the undersigned, believe in transparency, accuracy, and accountability in scientific research, especially in matters related to healthcare.

We believe contractual nondisclosure clauses [1] that prohibit or restrain unfettered disclosure and dissemination of information about healthcare information technology problems related to bugs, design defects, suboptimal user interfaces, other factors that can adversely affect care, and the adverse events and near accidents these problems cause, are unethical.

We believe that patients and clinicians have a right to knowledge of healthcare information technology problems and defects that can distract clinicians and/or reduce clinician effectiveness and productivity. We also believe that hospital governance personnel have the fiduciary responsibility as well as obligation under Joint Commission safety standards to protect patients, clinicians and others working within and for their organizations from the potential consequences of healthcare information technology problems [2].

We believe that only through transparency about healthcare information technology can medical ethics be maintained, the rights of patients to the best possible care be protected and medical science advanced.

Therefore, we call for such clauses to be refused by governance bodies, vendors of healthcare information technology to refrain from including such clauses in their contracts, and the U.S. Congress to prohibit nondisclosure clauses related to medical devices and healthcare information technology.

Furthermore, retaliatory actions against those who in good faith report such matters or incidents should be prohibited.

[1] Koppel R, Kreda D. Health Care Information Technology Vendors' "Hold Harmless" Clause: Implications for Patients and Clinicians, JAMA. 2009;301(12):1276-1278.

[2] Silverstein S. "Health Care Information Technology, Hospital Responsibilities, and Joint Commission Standards." Letter to the Editor, JAMA. 2009; 302: 382.

As I had spelled out many months ago at "Health Care Information Technology Vendors' Hold Harmless and Keep Defects Secret Clauses" here, and in a July 22, 2009 letter to the editor in JAMA entitled "Health Care Information Technology, Hospital Responsibilities, and Joint Commission Standards", I believe these clauses:

  • Are responsible for stagnation in health IT industry thinking that requires an unrelenting focus on the needs of clinicians and patients;
  • Cause hospital executives to violate their fiduciary and Joint Commission safety obligations to patients and staff;
  • Perhaps even put clinicians themselves in a conflict of interest with their own professional ethics (that call for widely sharing information about potential risks to patients).

The Joint Commission nor any other healthcare regulatory body has done anything about such contract clauses since that time, to the best of my knowledge despite being made aware of these issues by direct email to JC leadership.

I've noted few signatures to the petition so far, but have received some feedback and noted other justifications for maintenance of the status quo. The arguments fall into several categories that defend the status quo of HIT defect/problem nondisclosure clauses. The categories of argument include:

  • Legal arguments (or perhaps I should say 'legalistic'): e.g., HIT is not a "medical device", is not regulated, therefore such clauses are nobody's business but the seller and buyer.
  • Semantic arguments (arguing about words): e.g., the Joint Commission safety standards calling for "the organization to communicate information related to safety and quality to those who need it, including staff, licensed independent practitioners, patients, families, and external interested parties" really do not mean communication to other healthcare organizations, regulatory bodies, the press, etc.
  • Corporatist arguments: the clauses are needed to protect the industry and protect "innovation" - however, innovation without adherence to patient's rights and medical ethics is not innovation at all in my mind (cf. the Tuskegee Study of Syphilis).
  • Statist arguments: e.g., we know what's best for medicine, and even if HIT today does have problems and hurt people, it's for the greater future good that their diffusion should be unimpeded by free dissemination of information on downsides.
  • Logically fallacious or irrational arguments: e.g., the circular argument that there's no reason to prohibit nondisclosure clauses about HIT defects and patient incidents, since these problems do not occur in the first place -- or if they occur patient harm is "always" averted by clinicians.

While these type of arguments are interesting and may make for excellent debate, (and medical ethicist George Annas at BU taught his medical students, myself included, well on such issues): none of these arguments are aligned to the ethics, customs and traditions of medicine and the oaths taken by its practitioners.

The oaths taken by healthcare IT companies (i.e., to the speculators investing in this technology) leave much to be desired in that regard.

On the other hand, here is a sentinel reason for supporting their quick abolishment, a strong informatics-based reason to abolish nondisclosure clauses:

As admissions such as "We are unable to share documents [relating to likely problematic EHR's - ed.] as our contract with XXXX includes a confidentiality clause" at http://www.computerweekly.com/blogs/tony_collins/2009/11/claim-of-censorship-over-cerne.html indicate, to the point of rejecting a FOI request for information, there are unknowns in health IT (as Tim the proprietor at Histalk wryly noted, the refusal probably is not on the grounds of having glowing praise to report).

How many other data points have not made it to the literature, either peer reviewed or press? Does anyone know definitively?

Do we really know that Medical Informatics research therefore represents a valid sampling of the events that transpire when HIT is designed and implemented?

A parallel and currently controversial issue in pharma is the deliberate suppression of negative or neutral clinincal trials results, with an emphasis on the positive, to protect a drug candidate or an actual drug in postmarketing surveillance. Does this not potentially taint the science?


-- SS

Tuesday, December 15, 2009

Web Petition: Transparency and Openness in Electronic Patient Records and Other Healthcare Information Technology Systems

I have created a new Web petition "Transparency and Openness in Electronic Patient Records and Other Healthcare Information Technology Systems."

It is at WEBPETITIONS.COM at this link: http://www.webpetitions.com/cgi-bin/print_petition.cgi?99504454

Aimed at clinicians, hospital governance personnel and other healthcare stakeholders including patients, the petition states:

We, the undersigned, believe in transparency, accuracy, and accountability in scientific research, especially in matters related to healthcare.

We believe contractual nondisclosure clauses [1] that prohibit or restrain unfettered disclosure and dissemination of information about healthcare information technology problems related to bugs, design defects, suboptimal user interfaces, other factors that can adversely affect care, and the adverse events and near accidents these problems cause, are unethical.

We believe that patients and clinicians have a right to knowledge of healthcare information technology problems and defects that can distract clinicians and/or reduce clinician effectiveness and productivity. We also believe that hospital governance personnel have the fiduciary responsibility as well as obligation under Joint Commission safety standards to protect patients, clinicians and others working within and for their organizations from the potential consequences of healthcare information technology problems [2].

We believe that only through transparency about healthcare information technology can medical ethics be maintained, the rights of patients to the best possible care be protected and medical science advanced.

Therefore, we call for such clauses to be refused by governance bodies, vendors of healthcare information technology to refrain from including such clauses in their contracts, and the U.S. Congress to prohibit nondisclosure clauses related to medical devices and healthcare information technology.

Furthermore, retaliatory actions against those who in good faith report such matters or incidents should be prohibited.

[1] Koppel R, Kreda D. Health Care Information Technology Vendors' "Hold Harmless" Clause: Implications for Patients and Clinicians, JAMA. 2009;301(12):1276-1278.

[2] Silverstein S. "Health Care Information Technology, Hospital Responsibilities, and Joint Commission Standards." Letter to the Editor, JAMA. 2009; 302: 382.

The signed petition will be sent to the U.S. Senate Finance Committee (currently investigating healthcare IT), the Secretary of HHS, the Director of AHRQ, the Director of the Office of the National Coordinator for Health IT, and the President of the Joint Commission.

Please sign at the WEBPETITIONS.COM link http://www.webpetitions.com/cgi-bin/print_petition.cgi?99504454, and spread the word.

-- SS

Addendum: as an example of the problems these nondisclosure clauses can create, see my post "We are unable to share documents relating to problematic EHR's as our contract with Cerner includes a confidentiality clause."

Sunday, October 25, 2009

Washington Post Article: Electronic medical records not seen as a cure-all

Regarding the very well done Sunday Oct. 25, 2009 story in the Washington Post "Electronic medical records not seen as a cure-all" by staff writer Alexi Mostrous - signup may be required for access - I have several observations.

(Not including the observation that Mr. Mostrous probably deserves an award for being the first major newspaper reporter to broach this topic in a serious and balanced manner.)

First, I believe healthcare IT can live up to all the predictions made about its benefits - but only if done well. There is massive complexity behind those two words "done well", and that is HIT's key stumbling block in 2009. I believe we are only in the adolescent stage of knowing how to "do health IT well."

Second, I should point out that the intended consequences of health IT include, among many other things, the following "hiding in plain sight" (i.e., not often verbalized) intended consequences:

  • The improvement of medicine ... in the context of protection of patient rights established over centuries of development of modern medicine.
  • The improvement of IT itself through cross disciplinary collaboration between IT and medicine, of the science of IT (computer science), the social aspects of computerization ("sociotechnical issues"), and improvement of the our understanding of the intersection of medicine and computers.

Instead, we largely have the opposite. Patients' rights are trampled, and hostility and territoriality has arisen between clinicians (including medical informaticists) and IT, groups that rarely if ever interacted in hospitals ten or twenty years ago.

Of concern, when scientific study sections evaluate NIH grant proposals calling for testing of new IT that involves patients, patient protections and informed consent processes are a paramount concern since such activities are considered research. Yet, in implementing large clinical IT system in a hospital with new features, there are no formal regulations, and I'm not sure there's even IRB involvement in most cases. Patients do not get the chance to give informed consent to the use of these IT devices mediating their care. Why the difference?

The unintended results of computerization efforts have also included suppression of research on sociotechnical issues and on informatics, which must include study of the downsides of HIT, and of the failures in addition to the study of the successes. That is scientific fact - there is no room for debate, no room for spin on the need for careful study of the downsides of any mission critical domain. One would think there to be a vibrant literature on these issues, Yet searches on massive biomedical databases such as PubMed on, say, "cerner electronic health record" (or other vendors as well) are disappointing to say the least. Further, my own website on HIT difficulties remains nearly unique (PPT) after ten years online. That is not bragging; it is a disturbing finding to me - symptomatic of an industry that somehow has managed to avoid serious scrutiny.

In a field with downsides, there are:

1) those who know about the problems but fail to speak,
2) those who see the problems but fail to act, and
3) those who see, know and speak/write/research the problems.

That said, now on to the Washington Post article:

... bipartisan enthusiasm has obscured questions about the effectiveness of health information technology products, critics say. Interviews with more than two dozen doctors, academics, patients and computer programmers suggest that computer systems can increase errors, add hours to doctors' workloads and compromise patient care.

I would include the bipartisan enthusiasm under the subject header of "irrational exuberance", which itself falls under the header of "lack of domain knowledge." That itself is a consequence of both failure to study the issues, and suppression of those issues by those with an interest in doing so.

health IT's effectiveness is unclear.

The literature is indeed conflicting, and the need for rigorous scientific study has never been more essential considering the commitment of tens of billions of dollars towards health IT. The time for story telling, marketing based on opinion, name calling, leap-of-faith extrapolations of light year dimensions, and other forms of pseudoscience and non-science are over. The time for objective study is now.

The Senate Finance Committee has amassed a thick file of testimony alleging serious computer flaws from doctors, patients and engineers unhappy with current systems.

Being the ranking member of that committee, Sen. Grassley has a fiduciary responsibility to protect Medicare and Medicaid patients (and one might argue, to protect all patients since those programs often serve as models for private insurers). In that regard, the investigation he has initiated is part of his responsibility as a ranking member of Congress. Politics aside (and there are those who will resort to ad hominem "political witch hunt" arguments), he would have been negligent if he had not initiated an inquiry.

Sen. Grassley has taken on the pharma industry and the government's Food and Drug Administration itself, such as in this recent article "FDA fails to follow up on unproven drugs" where he concluded from a GAO study he ordered that "FDA has fallen far short of where it should be for patient safety." He seems quite serious about medical safety.

If only others in Congress had done their job similarly regarding national finance, we might now not be in the worst economic crisis since '29 with many major industries failing.

David Blumenthal, the head of health technology at the Department of Health and Human Services, acknowledged that the systems had flaws. "But the critical question is whether, on balance, care is better than before," he said. "I think the answer is yes."

This sounds uncomfortably like how a pharmaceutical company might respond to doubts about drug effectiveness and safety. In reality it's really irrelevant what he "thinks." Where's the data? Is this a political statement, a personal belief, or a statement backed up by scientific fact that is not cast into doubt by other research results? Our own National Research Council, Joint Commission, and other international organizations have written about their doubts and concerns about HIT [as that IT is designed and implemented in 2009]. If there is rigorous, systematic research weighing pro's and con's to back this assertion, I wish it would be published.

For his statement is really saying "we don't really know how many systems have flaws, we know some do, and we don't really know the full extent of the impact of those flaws, but because there can be some benefits, let's spend $50+ billion before we know the extent of the problems and fix them." I point out research from Harvard forty years ago, when Harvard informatics pioneer Dr. Octo Barnett published the "Ten Commandments of HIT." Two of those commandments were:

... 8. Thou shall be concerned with realities of the cost and projected benefit of the computer system [i.e., ROI - ed.]

10. Be optimistic about the future, supportive of good work that is being done, passionate in your commitment, but always guided by a fundamental skepticism.

The full set is in this post. Somewhere in the past 40 years, the rigorous ROI evaluations (which also must include systematic evaluations of risk, as any businessperson knows) and the fundamental skepticism seem to have gotten lost.

Over the next two months, Blumenthal will finalize the definition of "meaningful use," the standard that hospitals and physicians will have to reach before qualifying for health IT stimulus funds.

This is an example of putting the cart before the horse, and is a semantically-based, self contained logical fallacy of sorts. If a health IT system is harmful, the term "meaningful use" is itself Orwellian. If we don't know if HIT is beneficial, or have doubts, then such as term presupposes that health IT is inherently beneficial. A better term would have been "good faith use" - use based on the faith or hope that health IT will have an overall positive effect. The term "meaningful use" jumps the gun and is more a political slogan than a "meaningful term."

"If you look at other high-risk industries, like drug regulation or aviation, there's a requirement to report problems," said David C. Classen, an associate professor of medicine at the University of Utah who recently completed a study on health IT installations.

This is obvious, the reasons for it are obvious, and the reasons why health IT needs a requirement for problems reporting (one aspect of post-marketing surveillance, the "Phase IV" study as it is known in pharma) is obvious. Yet in 2009, no such requirement exists (see my post "Our Policy Is To Always Have Unabashed Faith In The Computer" for more on why we need reporting requirements.) Why do these requirements simply not exist in HIT?

"It's been a complete nightmare," said Steve Chabala, an emergency room physician at St. Mary Mercy Hospital in Livonia, Mich., which switched to electronic records three years ago. "I can't see my patients because I'm at a screen entering data." Last year, his department found that physicians spent nearly five of every 10 hours on a computer, he said. "I sit down and log on to a computer 60 times every shift. Physician productivity and satisfaction have fallen off a cliff."

The industry in the past has called such physicians "luddites", "resistant to change", "stubborn" etc. However, argumentum ad hominem is a fallacious mode of argument that has no place in a scientific field such as biomedicine. There also seems to be quite a lot of such concerns expressed by a large number of physicians, nurses, etc., and dismissing their concerns with a wave of the hand is cavalier in the extreme - again, these are first principles, without room for argument or debate. Let's study the issues rigorously and scientifically before resorting to ad hominem.

Other doctors spoke of cluttered screens, unresponsive vendors and illogical displays. "It's a huge safety issue," said Christine Sinsky, an internist in Dubuque, Iowa, whose practice implemented electronic records six years ago.

See my eight part series on mission hostile clinical IT here for examples of what Dr. Sinsky is referring to.

She emphasized that electronic records have improved her practice. "We wouldn't want to go back," she said. "But EHRs are still in need of significant improvement."

Yes, not cancellation, but improvement. And, quite importantly, before tens of billions of dollars are spent. Hospitals and physician offices are not an IT development laboratory, since the users of these facilities (patients) have very special rights and the clinicians, very special obligations and responsibilities.

Legal experts say it is impossible to know how often health IT mishaps occur. Electronic medical records are not classified as medical devices, so hospitals are not required to report problems.

That after decades of HIT development, sales and implementation we cannot know with certainty how often mishaps occur is, quite simply, a scandal of major proportions. Quoting an old House of God law, #10: "if you don't take a temperature, you can't find a fever." Another applicable aphorism seen on another discussion board: "you can only be so negligent or craven before the only remaining rationale is that you intended the result."

"Doctors who report problems can lose their jobs," Hoffman said.

I've taken risks with my own career in criticizing health IT, as have my colleagues. Hoffman is not exaggerating.

"Hospitals don't have any incentive to do so [speak out about problems with HIT] and may be in breach of contract if they do."

Imagine the outcry if the same prevailed regarding drugs or medical devices. The cemeteries would be lined with people whose epitaph could read "we bury our mistakes."

While orange-shirted vendor employees "ran around with no idea how to work their own equipment," the internist said, doctors struggled to keep chronically ill patients alive. "I didn't go through all my training to have my ability to take care of patients destroyed by devices that are an impediment to medical care."

This gets to issues I first raised in my website on HIT difficulties: who are these IT personnel, and what are their qualifications, exactly, to be working in mission critical medical environments? How is their competence evaluated?

I think these are questions that need to be answered.

-- SS

Saturday, October 24, 2009

Washington Post: EMR's No Cure-All; Sen. Grassley Sends Letter of Inquiry to health IT vendors

Senator Grassley has sent a letter out to ten major health IT vendors seeking information on health IT problems and flaws. The letter can be retrieved from this link (PDF) at the Washington Post. Read the whole thing.

It is linked via a Washington Post story "Electronic medical records not a cure-all", Sunday Oct. 25, 2009, by staff writer Alexi Mostrous. The WaPo article itself seems to require registration. I will comment on the article in future posts.

Addendum 10/25: I have now commented on the article here.

-- SS

Sunday, October 18, 2009

Our Policy Is To Always Have Unabashed Faith In The Computer ... Except When It Screws Up, And Then It's The Doctor's Fault

Healthcare IT such as electronic medical records (EMR/EHR) and computerized physician order entry (CPOE) systems are a perfected, safe technology, one might think, from the almost hagiographic and entirely uncritical P.R. about HIT, all the way up to the President of the United States. (Not bad for an entirely unregulated industry. Pharma IT should only have it so well.)

Paraphrasing Capt. Chesley Sullenberger in a recent WSJ article, however, I'm a long term optimist about HIT, but a short term realist. Healthcare cannot be 'transformed' by a technology that itself has major problems and needs transformation. These issues should have been substantially remediated before forced national rollouts, I feel.

That's especially true given the inherent dangers in medicine. You can't be a wishful thinker. You have to know what you know, and perhaps more importantly in medicine, what you don't know (this is especially true both for those in IT who lack formal clinical or biomedical backgrounds, and for those in medicine who lack formal biomedical informatics or computer science backgrounds). You also need to know what your tools can and can't do. Sticking one's head in the sand is no way to approach HIT.




That said, here are some sample voluntary reports on HIT malfunctions from just one vendor, taken from the FDA Medical Devices database, the Manufacturer and User Facility Device Experience (MAUDE) database, links included. These are production systems used on real, live patients, not prototypes:

MAUDE data represents reports of adverse events involving medical devices. The data consists of voluntary reports since June 1993, user facility reports since 1991, distributor reports since 1993, and manufacturer reports since August 1996. MAUDE may not include reports made according to exemptions, variances, or alternative reporting requirements granted under 21 CFR 803.19.

Emphases below are mine. My comments are in [red italic].

Case 1: (note - added to this post 7/2010)
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfmaude/detail.cfm?mdrfoi__id=1656460
CERNER MILLENIUM POWERCHART CPOE
Event Date 11/19/2006
Event Type: Death
Patient Outcome: Death
The medication review screen of the subject device does not specify the exact dose in milligrams of combination medications. For example, narcotics are combined with tylenol in at least two strengths. Liquid narcotic tylenol-oxycodone combination is reported in ml, not mg. The exact dose of tylenol is not specified and requires knowledge of the combination medication dose in the volume specified. Certain fields of the grid do not specify the volume, but rather state "date/time" requiring another click or pop up screen. The immediate knowledge of tylenol dosage in mg is directly related to understanding and preventing excessive doses. In the subject, 10 ml of acetaminophen-oxycodone is indicated as having been given 3 times over 4 hours. That means that 1950 mg of tylenol was administered in 4 hours while the patient was in a state of starvation and receiving other medication that increase the effects of tylenol. This dose would equate to 11,700 mg of tylenol over 24 hours, nearly 3 times the maximum daily dose in otherwise health people. In the ensuing days, the patient developed acute renal failure, presumably acute tubular necrosis, and died. In the absence of other etiology, the excess tylenol was the culprit. This was not considered as etiology ante-mortem. The counterintuitive screen impaired the professionals. The pharmacist did not recognize and stop the medication, the nurses administered it, and the excessive dose, clinically meaninglessly listed as a volume of 10 ml -given 3 times in 4 hours- of acetaminophen-oxycodone, was missed by the physicians. Adverse events have been ascribed to "user error" by vendors. The device offers a potent propensity to life endangering oversights. There are other screens on this device which present information that interfere with clinically useful visualization of data. [Who designed these screens, I ask? Clinicians, or business IT personnel used to designing inventory systems for widget control? - ed.] The data does not flow to the professionals. It is not represented in a meaningfully useful manner. The professionals need to hunt for it. As such, the user unfriendly screens [see this link on mission hostile HIT - ed.] impair safe medical care consistent with the impediment to expedient professional understanding of what, exactly, is the dose of medication and how much was administered to the patient. This sentinel case of death is directly attributed to user unfriendly screens on this device.

Case 2:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfRES/res.cfm?id=64345
Cerner Millennium RadNet Auto Launch Study and Auto Launch Report software functionalities. Defects in the Auto Launch functionality make it possible for a mismatch of patient data. [That is, in radiology reports. The dangers of transpositions is obvious.]

Case 3:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=722614
The issue involves powerchart local access medication administration task, used when certain cerner millennium solutions are not available. At powerchart local access sites that utilize coordinated universal time (utc) functionality, medication administration tasks might be displayed with incorrect times. When a pt download occurs from cerner millennium servers to powerchart local access, and there is no cerner millennium application session active, powerchart local access adds or subtracts the number of hours equal to the time zone difference from greenwich mean time. Scheduled medication administration tasks may show an incorrect administration time and the possibility exists for a pt to receive medications earlier or later than intended. [As just one example of the dangers with this type of defect, an elderly patient with sepsis might get an early dose of aminoglycoside, causing peak levels to rise to nephrotoxic and ototoxic levels - ed.]

Case 4:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=946706
Patient care delay. The issue involves functionality in cerner millennium powerchart office and powerchart core and affects users that utilize the powerchart inbox and message center inbox. In results to endorse or sign and review, if the user clicks ok and next multiple times in quick succession [e.g., a busy clinician with sick patients, waiting for the computer to respond - ed.] while attempting to sign a result or a document, the display could lag behind the system's processing of the action [that is to say, the human-programmed and supposedly tested and validated computer "system" -ed.], and multiple results or documents could be signed without the user's review. In message center, when clicking ok and next or accept and next, or when deleting or completing messages and moving to the next task, a document could be signed or a message could be deleted without the user's review. Results could be endorsed or documents could be signed without physician review, which could impact patient care. Cerner received communication that a patient's follow-up care was delayed as a result of this issue. [Luck prevailed that no injury occurred - in this reported case. One wonders if that is true of all the users who experienced this problem. Also, I do not recall such errors happening on paper order forms due to, say, a busy clinician tapping his pen on the paper - ed.]

Case 5:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=888215
The issue involves the pharmacy medmanager functionality. If the user performs a modify action on an order with an existing duration and duration unit, the order's stop date might not be recalculated. Specifically, this occurs when only the duration value is changed prior to entering the original duration unit. Pt care could be adversely affected, as medication therapy could be concluded prematurely or could last longer than intended based on the order details prior to the modification. This issue can be avoided if the user performs a renew action instead of a modify action to change an order's duration. If performing a modify action is required, users can manually set the stop date and time during the modify action. Cerner received communication that a pt's surgery required rescheduling as a result of this issue. [Again, was the lack of patient harm due to careful clinicians who at that moment just happened to not be distracted or cognitively overloaded or overworked or exhausted from on-call, or an act of Providence? Were other non-reported users at other organizations less lucky? - ed.]

Case 6:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=920819
The issue involves the results to endorse (rte) inbox functionality in powerchart, powerchart office and firstnet and affects users that use the rte inbox to view radiology reports that have been created in radnet. Radiology results might fail to be displayed in the ordering provider's results to endorse folder in the inbox. Treatment or diagnosis decisions could be delayed if the clinician is relying on the display of a result in the inbox results to endorse folder to initiate patient follow-up. Note: the final results are posted to the flowsheet and are available on the patient's chart. Cerner received communication that a patient's follow-up care was delayed as a result of this issue. [Were any diagnoses of, say, cancer missed by other organizations affected? -ed.]

Case 7:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=700117
The issue involves the direct charting flowsheet and icu flowsheet, used within the powerchart system. When the result details box is accessed for a negative result value in either the icu flowsheet or the direct charting flowsheet in powerchart, either by right-clicking a negative, unsigned result value and selecting chart details from the context menu, or by right-clicking a negative signed result value and selecting modify, the dialog box displays a blank result value. When the user clicks ok in the result details dialog box, the value is changed to zero in the result cell in the flowsheet. [Of all places, health IT in ICU's should be extensively validated before going into production - ed.]

Case 8:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=715963
The issue involves the careadmin medication administration wizard used within the carenet system. When scanning a medication in careadmin, the system fails to recognize mckesson identifiers or other miscelaneous identifiers and properly identify the scanned product, which could result in the documentation of an incorrect dose in the careadmini window. In such situations, the system does not display overdose or underdose or route/form compatibility warnings as it should. Patients could receive an inappropriate dose of medication. Cerner has not been made aware of any adverse patient care events that resulted from this issue. [Thank god for that - but were any unreported by other organizations? - ed.]

Case 9:
http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=753029
Microbiology set up a program within the cerner computer system to automate the reporting system for hsv (herpes simplex virus)testing. The system was tested with the assistance of cerner and found to be working appropriately. The new system was operational for approximately 3 weeks when it was determined that the first word of the sentence, "no" was inappropriately dropping off of the following sentence: "no herpes simplex virus type 1 or herpes simplex virus type 2 detected by dna amplification. " as such, two of five patients were incorrectly informed that they had hsv before the error was detected. One had started an antiviral creme treatment. The other three did not have follow-up visits until after the correct results were determined. Cerner has looked at the program and has not provided an answer for the system issue. In the interim, the previous manual review and entry process is being used. [How does the word "no", an essential descriptor in a medical test, simply get "dropped?" Does NORAD's ballistic missile warning system ever do that, i.e., "no ICBM's incoming" reported as "ICBM's incoming"?- ed.]

---------------------------------

Additional reported errors can be seen in a file downloadable by clicking on this link (PDF). Some of these are a bit startling.

---------------------------------

Still others can be seen at:

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=695436

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=688925

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=996685

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=1075747

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=574578

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=1288623

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=1370640

http://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/Detail.CFM?MDRFOI__ID=834678


Again, these are reports about just one HIT vendor but this piece is not just about them. Other HIT vendor products have similar issues. Health IT remains an experimental technology.

The MAUDE reports are voluntary, however, so the absence of a report does not mean an absence of a problem. (I note MAUDE queries on a number of major HIT vendors produce no results, or results limited to HIT that is closely associated with physical "medical devices" -- as opposed to virtual ones -- such as radiology systems.) For example, while a query on mfg. "Cerner" brings up hits, a query on another vendor shows this result:

No records were found with Manufacturer: Allscripts Report Date From: 10/01/1998 Report Date To: 09/30/2009

... and this:

No records were found with Manufacturer: Nextgen Report Date From: 10/01/1997 Report Date To: 09/30/2009

... while a broader FDA search on "Nextgen" brings up exactly one relevant hit on "Nextgen EMR - Medical Device" -- without specifics as to the "malfunction" noted under product code "HGM" - which on lookup is a perinatal monitoring system.

A broader search on Allscripts only brings up drug related issues such as
this curious 2002 warning letter about the marketing of guaifenesin, a cough medicine, from FDA's Center for Drug Evaluation and Research.

Either these vendors are not reporting HIT problems, or are listed under another name. Rather unlikely is that they have no problems to report (latter hyperlink is PDF). As another example, a search on brand name "Centricity" brings up "hits" mostly on specialized GE products such as PACS.

So, is HIT safe, or can "glitches" affect patient care? Should this industry be entirely unregulated, or its products "certified" by groups with conflicts of interest such as those affiliated with industry trade groups? Should vendors be held harmless for HIT defects that harm patients?

I report, you decide.

-- SS