Home » Time Capsule » Currently Reading:

Time Capsule: Doctors Mostly Ignore Primitive Clinical Decision Support: Help Them Do Right Instead of Warning Them They Might Be Wrong

February 15, 2013 Time Capsule 4 Comments

I wrote weekly editorials for a boutique industry newsletter for several years, anxious for both audience and income. I learned a lot about coming up with ideas for the weekly grind, trying to be simultaneously opinionated and entertaining in a few hundred words, and not sleeping much because I was working all the time. They’re fun to read as a look back at what was important then (and often still important now).

I wrote this piece in June 2008.

Doctors Mostly Ignore Primitive Clinical Decision Support: Help Them Do Right Instead of Warning Them They Might Be Wrong
By Mr. HIStalk

125x125_2nd_Circle

Anyone who has worked with hospital clinical systems knows that so-called “clinical decision support” for physicians has been a bust in many (most?) cases. You turn on all those high-falutin’ warnings that were the primary reason you bought CPOE. The doctors scream bloody murder at the interruptions. You dial it back, they still gripe. C’mon, Doc, we bought this to help you practice good medicine.

Finally, you learn an expensive lesson. From the doctor’s perspective, the optimal decision support setting for your CPOE system is to shut off everything except (a) dose range alerts at the “you’re about to kill this patient” level, and (b) allergy warnings, which they will still ignore 95 percent of the time. (The docs would have told you that upfront, but clinical systems arousal means not asking questions whose answers reflect imperfect reality).

Your shiny new system might (if you’re lucky) save a patient once or twice a year who would have been in big trouble pre-CPOE. Otherwise, the average patient isn’t getting much benefit. Check your stats – an ignored warning is a useless one.

Today’s clinical decision support is mostly old-school, mainframe stuff, simple lookups and algorithms like “do these two drugs interact” and “this test is not recommended, please use this one instead.” It was designed from the paradigm of finding something the physician might have missed and providing a pesky error message, no different from crude screen edits that catch keystroke errors.

In other words, the computer just tells doctors when they might be wrong instead of helping them be right in the first place. May I repeat? The computer just tells doctors when they might be wrong instead of helping them be right in the first place.

The more useful paradigm might have been, “Let me give you some carefully and intelligently mined information that might help you diagnose or treat, not scold you afterward.”

Today’s hospital systems contain a heck of a lot more useful information than they did back in the 1980s when allergy alerts were hot stuff. The challenge now is separating the good stuff from the noise. What subtle trends are occurring with this patient? What correlations exist that humans might miss? What information from the patient’s longitudinal record could help make the right decision now? Can anything be gleaned from the hospital’s vast database of past therapies and outcomes that would improve this particular patient’s care?

If you’re a vendor looking to gain an edge in next generation’s sales wars, look no further. This is stuff that doctors would actually use. This is information that would decrease clinical variation and help apply cutting edge knowledge to individual cases. Information saves money and lives, so hospitals would pay for that result.

This is not simple programming work or a subscription to some expensive third-party drug database. In fact, making something like this work with yesterday’s architectures would be a big pain. It would require a lot of information about a particular patient, including some not readily available today (like an easy way to specify, “What do you think’s wrong with this guy, doc?”)

That level of guidance would also require customization capability since doctors aren’t interchangeable. Urologists don’t focus on the same information as cardiologists. Doctor A might pay a lot of attention to respiratory data points, while Doctor B might be a blood sugar man. Let each flag suggestions as “helpful” or “not helpful” so the system can learn what to offer next time (yes, computers can learn.)

Once vendors figure all that out, the next logical step would be to tie literature to practice. Journal knowledge shouldn’t be hidden away in libraries and online subscriptions. Specialty content vendors are already evaluating and grading that new information into decision support applications for immediate, routine patient use. That’s pretty cool and would be even cooler if undertaken under the open source banner to encourage broad participation and to minimize financial barriers to adoption.

The industry’s efforts to create electronic clinical decision support have largely misfired, as evidenced by its half-hearted use and unimpressive impact on outcomes. Surely some smart folks out there can come up with a better plan that will help make all these systems worth their cost.

View/Print Text Only View/Print Text Only


HIStalk Featured Sponsors

     

Currently there are "4 comments" on this Article:

  1. There are 2 primitive CDS in emergency medicine that are very simple and effective: 1. Let the user know if there are any pending labs at the time of ED discharge, and 2. Alert the user if vital signs are abnormal at discharge. Beyond these, better to wait for Watson.

  2. You are right. Every day, for the past week, the EHR CDS device covering the care of my team’s patient with a massive gastrointestinal bleed in shock pops up a warning about anti coagulant DVT prophylaxis. It must be clicked off each time and can not be deactivated.

    I think to my self, what in the world is going on here? Why is the computer so stupid? But it tries to be smart by yielding 2 pages of information on DVT prohylaxis. Hmmm.

  3. My doctors blow through the decision support and nonsense screens always. They have yet to find anything of value there. These screens waste time, distract cognition, and further disrupt the already disrupted workflows caused by CPOE devices.

    I like the CDS needs reported by the first commenter. That is useful and life saving information.

    I would add that there should be a decision alert when new test results arrive otherwise silently at the EMR, and a pop-up screen showing lab values whenever anyone is ordering a medication that could have an impact of blood test results, eg potassium.

    The same could be said for a pop-up allowing a scroll through on medications and med-admin.

    Those needs are well known but not met, for over a decade.

  4. Stupid is as stupid does… we can’t blame the EMRs per se – but CDS was just set up so poorly by the vendors!
    While there will always be a small need for “alerts which STOP workflow so you don’t kill someone”… the real value of CDS will be in providing information which MAKES WORKFLOW EASIER! Unfortunately, most EMR vendors didn’t add in sophisticated CDS abilities, so we will be seeing the rise of Cloud-based CDS which allow for much more sophisticated analysis, and ideally will be integrated so intimately with the EMRs that they can actually support workflows in a variety of ways. And yes, I am working on this type of software with healthfinch.com – and I hope we see more and more from the industry at large!







Subscribe to Updates

Search


Loading

Text Ads


Report News and Rumors

No title

Anonymous online form
E-mail
Rumor line: 801.HIT.NEWS

Tweets

Archives

Founding Sponsors


 

Platinum Sponsors


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Gold Sponsors


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reader Comments

  • Really???: Getting very Alice-In-Wonderland-y in Trumpville methinks....
  • Epic Employee: Self-scheduling is definitly out there. I personally schedule all my primary care visits through MyChart either on the w...
  • ex-HHC: re:GIFT trial and Coumadin dosing. Medicare wouldn't pay for warfarin-based genotyping and this trial doesnt really seem...
  • dysF(n): Also on blockchain in healthcare - video might be even better... I don't have time to go through to narrow down to best ...
  • dysF(n): Pretty good blockchain explanation here http://money.howstuffworks.com/bitcoin2.htm...

Sponsor Quick Links