EMR liability needs to go further than just the physician

This example of a disaster waiting to happen, in the form of an error-promoting CPOE, is a poster example of why the net of litigation needs to be cast far wider than just clinicians when EHR-related errors result in injury or death.

This order entry screen, from a production system shows the following.  In all fairness, I do note it’s unclear if the vendor or the customer’s configuration “experts” were responsible for this:

COUMADIN (warfarin) tablet 2 mg Oral daily once.
CAUTION: Potential look-Alike or Sound-Alike medication – this product is COUMADIN

EMR liability needs to go further than just the physician

Below and not indented as is the selection, where the clinician is liable not to look very carefully, is the helpful interpretation:  “warfarin (COUMADIN) Tablet 2 milligram Oral daily for 1 Times.”

“Oral daily for 1 Times?”

This drug needs to be given daily, generally for a very long term.  Its effect on blood clotting varies for numerous reasons in an individual over time, and needs to be checked frequently via a blood test (International Normalized Ratio or INR) to ensure the level of effect is neither too little (which could result in clots) or too much (which could result in serious or fatal bleeding).

In this case, the clinician wanted Coumadin to be administered “daily,” as in “each and every day,” but this was the default – daily, but only once.  “Oral daily for 1 Times.”

Brilliant.

Daily Coumadin (i.e., daily EVERY DAY), the clinician related, could be ordered only with “painstaking difficulty.”

“X mg Oral daily once” is an unimaginably absurd and bizarre dosing selection to have on a CPOE system for such a critical drug – or any drug.  “Daily – once?”

It should not, and does not, take a rocket scientist to realize this selection could quite easily lull the busy clinician into believing they have selected a dose to be continued every day – i.e., “once daily” – as per the standard usage of this drug.

To order this drug for (true) daily administration, a user must find a “repeat” icon and click the number of days the drug is to be administered.  The “repeat” icon is not readily apparent amidst screen clutter.

For other drugs, the order choices are “## mg oral daily” or similar.

This semantic and human-computer interaction ineptitude is truly a disaster waiting to happen, especially with the medical/nursing/trainee staff turnaround that goes on in hospitals, and with the reality that clinicians are working at various hospitals with different CPOE/EHR systems.

Is this some sort scheme to prevent endless-administration Coumadin errors when the drug is actually deliberately discontinued, I ask?  If so, it’s ill-conceived and dangerous at best.

By way of further information, this drug is a common anticoagulant whose use is often protective of injurious or fatal blood clots that can cause strokes or death in people with common conditions such as atrial fibrillation or prosthetic heart valves:

Warfarin is used to decrease the tendency for thrombosis or as secondary prophylaxis (prevention of further episodes) in those individuals that have already formed a blood clot (thrombus). Warfarin treatment can help prevent formation of future blood clots and help reduce the risk of embolism (migration of a thrombus to a spot where it blocks blood supply to a vital organ).

The type of anticoagulation (clot formation inhibition) for which warfarin is best suited, is that in areas of slowly-running blood, such as in veins and the pooled blood behind artificial and natural valves, and pooled in dysfunctional cardiac atria. Thus, common clinical indications for warfarin use are atrial fibrillation, the presence of artificial heart valves, deep venous thrombosis, and pulmonary embolism (where the embolized clots first form in veins).

This is an example of the kinds of mission hostility that results when amateurs attempt to play doctor.

I add that this type of “errorgenicity” is inexcusable.  If patients suffer harm from this type of “feature,” the net of liability needs to go further than just the clinician who was caught in a web of cybernetic clinical toxicity.

Scot Silverstein is a physician and medical informatics professional who blogs at Health Care Renewal.

Submit a guest post and be heard on social media’s leading physician voice.

email

  • Birgit Houston

    Error generation is promoted when there are too many steps to complete a process, or when the process is not presented in an intuitive manner, which adds to the complexity of the process.  This is human nature.  It’s also one of the biggest beefs I have with the primitive and multiform nature of the current selection of EHR’s.

    I repeat myself daily about this, but I don’t get the impression anyone who makes these decisions listens or cares.

    • http://profile.yahoo.com/HSIMVPNZYT67UBE42HDLN2EHHA Joyce

       I would put this comment in 20 point font and put it in front of every EMR script monkey. When CPOE systems require a six hour training class to learn to use, you should be seriously reconsidering the software interface. I’m an RN who uses (and hates) Seimens’ Soarian. 

      • http://profile.yahoo.com/XX6KDRX23DEZJSMFLWM4Q6CCHM Aten

        These devices are not fit for purpose. It is more economical for a small practice to take the penalty than use these flawed and defective devices.  As for hospital CPOE, the med mal lawyers must name the vendors and the hospital administrators in their lawsuits when screwups occur from the flawed ordering devices.

  • SaraJMD

    Someone probably did make a one time dose the default in this case.  The Joint Commission at some point started requiring a specific anticoagulant safety program, and the inpatient institutions I’ve been at have come down on the side of making providers reorder coumadin every day, basically to avoid ODs. That said, this is a perfect example of why that isn’t necessarily the answer either! Unless warnings are tripped with this order, its expiration and what the provider wants to do about it the next day (and if there are enough of these warnings, these become easy to click through without really reading), these one time orders are the most easily lost. I’ve seen better iterations of this problem, but I agree that even if the dose itself is effectively for one day at a time, the system needs to somehow tag the patient as being on coumadin chronically. Admittedly, hospitalized patients, who are sick, stressed, having procedures and eating an atypical diet need frequent coumadin dose adjustments, even the ones who are very stable at home and admitted for irrelevant issues, but as you point out, a missed dose can be a major problem, as well. Ultimately, I agree, I can’t understand how we hope to avoid medication errors by making the ordering process increasingly complicated!

    • S Silverstein

      It’s not just the default issue – it’s the grammar..  “COUMADIN (warfarin) tablet 2 mg Oral daily once.”

      “Daily once?” “Oral daily for 1 Times?” How did such phrases make it to a production system in a real hospital?

      Ironically, one of the key aspects of Medical Informatics — as a discipline — is to study medical terminology and semantics to reduce ambiguity and “blur”  cf.:  UMLS project.

      Illiterates have no business working in proximity to EHRs. “Daily once” is just a tad more clear than “daily sometimes.”

      • SaraJMD

         It’s true, I guess I do react less to that than someone outside the healthcare system might. On some level, I’ve accepted that “daily” in hospitalese actually means “at about 10 am” or something, but as a rule, plain old English is clearer for most of us, and that order does not make sense in English.

        • S Silverstein

          It can also be too easily confused, especially by busy residents, nurses and attendings, as “once daily.”

          Why should hospitals go looking for trouble?

    • http://profile.yahoo.com/XX6KDRX23DEZJSMFLWM4Q6CCHM Aten

      Regardless, this is prima facie evidence of the devices’ errorgenicity. There are innumerable patients who become underanticoagulated due to the gibberish featured in this reprot.

  • Happydaysdoc

    I couldn’t agree more but good luck with finding someone that actually cares about this issue AND can do anything about it — it really scares me with what junk the EMR can generate.

    I had to share my favorite EMRism of the week: if I have the diagnosis “fatigue” on a patient’s problem list, and enter a drug that is to be used with caution in pregnancy, even if my patient is 96 years old, I get a warning that the patient could be pregnant. Worse is that I have wait 20 seconds to read this warning while my patient also waits. It blows me away that this lunacy is present at the same time a Coumadin dosing script that could cause some patient to have a stroke is status quo.

  • Ryro

    In many hospitals information systems analysts who configure/ customize CPOE and not licensed clinicians. They have no oversight from P&T committees or other clinical governance structures and dictate solutions based on technical feasibility not best practices or patient safety.
    The most common excuse you will hear when reporting the risks of such confguration is either:
    1. Its working as designed, or
    2. Its never been done that way on this software or,
    3. Its not technically feasible to do it otherwise, or
    4. You have to LEARN to work with the software
    Its amazing how many times user (physician/ nurse) lack of applcation “education” is cited as the reason for raising the safety concerns of the example illustrated. Information Systems Departments need clinical oversight and software solution vendors need to be held accountable when medical misadventures are introduced by CPOE.

Trending