ISMP: Small Effort, Big Payoff… Automated Maximum Dose Alerts with Hard Stops

By The Institute for Safe Medication Practices

Automated alerts can provide an effective means of communicating essential information about drugs and patients to clinicians who prescribe, dispense, and administer medications. Alerts are typically communicated through warning messages that pop up on a screen and can cause either a soft or hard stop. A soft stop provides information to the clinician about a potential drug safety or efficacy problem and may offer alternative suggestions for the clinician to consider. However, minimal or no action or acknowledgement of the alert is required on the part of the user to proceed. A hard stop halts the progress of prescribing, dispensing, or administering a medication that would likely be dangerous to a patient. Further execution of the order is blocked. A nearly hard stop may allow continuation of the process if significant action is taken by the user, such as requiring a prescriber to  call the pharmacy to discuss the order (Strom et al., 2010). Studies have shown that soft stops are often overlooked or quickly overridden without careful consideration of the warning for a variety of reasons, including alert fatigue and poor design of the warning (Strom et al., 2010; Lapane et al., 2008; Shah et al., 2006; Miller et al., 2005). Hard stops and nearly hard stops have been shown to be much more effective in capturing the user’s attention and getting the user to change the prescription, re-enter the drug, or reprogram a device (Strom, 2010; Paterno et al., 2009; Shamliyan et al., 2008; Eslami et al., 2008).

As we describe recent errors with amphotericin B, methotrexate, and fentaNYL, keep in mind that a well-designed alert with a hard stop could have prevented these harmful errors.

Amphotericin B

ISMP has written about confusion between amphotericin B conventional (FUNGIZONE and generics) and lipid-based formulations (AMPHOTEC, ABELCET, AMBISOME) in more than 25 acute care newsletters, along with similar warnings in about 30 more acute care newsletters, regarding confusion between other conventional and lipid-based products (e.g., DOXOrubicin, PACLitaxel). In a recently reported event, amphotericin B conventional was prescribed in a dose reserved for the lipid-based product. A patient with acute myeloblastic leukemia and recent bone marrow transplant developed pulmonary aspergilloma. Using a computerized prescriber order entry (CPOE) system, the patient’s physician entered an order for amphotericin B conventional 375 mg IV every 24 hours. Based on the patient’s weight of 75 kg, the patient received 5 mg per kg of amphotericin B conventional while the maximum safe dose for this product is 1.5 mg per kg per day. This higher dose would have been appropriate for one of the lipid-based products, but it was more than three times higher than the maximum dose recommended for conventional amphotericin B. Within 3 hours of administration, the patient suffered a cardiac arrest and died.

During prescriber order entry of the drug, a warning had popped up on the screen asking the prescriber to verify that the dose did not exceed 1.5 mg per kg. However, the CPOE system did not require acknowledgement of the warning or action by the prescriber. The alert quickly disappeared after the prescriber hit the Enter key and bypassed the alert without consideration. The pharmacist also missed an opportunity to capture the dosing error. Although the screen accessed by the pharmacist when verifying the order revealed that amphotericin B conventional “equivalent to Fungizone” had been prescribed, the pharmacist misunderstood the order as the lipid-based product and even obtained a required approval from an infectious disease prescriber to dispense AmBisome. However, the pharmacy label that printed resulted in preparation of the conventional amphotericin B. The nurse who administered the drug did not notice the error, as she was not aware of the dosing differences between the conventional and lipid-based forms of the drug.

Numerous risk-reduction strategies may have helped to prevent or detect this error, such as including brand names when prescribing the lipid-based forms of the drug. However, a computer alert with a hard stop for doses of conventional amphotericin B greater than 1.5 mg per kg for both the CPOE and pharmacy system is a key strategy the importance of which should not be minimized. While ISMP recommends entry of patient weights in all order entry systems, if this does not occur consistently at your practice site, you may want to establish a catastrophic dose limit for a hard stop alert. Such an alert would not be designed to ensure an appropriate dose but rather to force a time-out and protect against a massive overdose.


In more than 50 acute care newsletters, ISMP has written about the accidental prescribing, dispensing, or administration of methotrexate daily instead of weekly when used for non-oncologic indications. In 2004, we also published a study of methotrexate errors over a 4-year period that resulted in 25 deaths and 48 serious outcomes, many due to daily dosing (Moore et al., 2004). The most recently reported event happened at a compounding pharmacy, but the same type of error has happened in hospitals. In this recent case, the compounding pharmacy received a telephone order to prepare an oral liquid preparation of methotrexate 12 mg per mL, with instructions to administer 6 mg (0.5 mL) once a week for a 19-month-old child with juvenile dermatomyositis. A pharmacist transcribed the order incorrectly and entered it into the pharmacy computer with a dosing frequency of daily. The pharmacy compounded the solution using methotrexate powder, and labeled the medication with instructions to take 0.5 mL daily instead of weekly. The pharmacist handling the order was unfamiliar with methotrexate dosing and did not recognize that a daily dose would be toxic. Also, the pharmacy had never filled a prescription for oral liquid methotrexate before the event. The child received a daily dose for 7 days before the error was noticed by the prescriber. The child was undergoing diagnostic laboratory tests to determine the adverse effects of this overdose when the event was reported to ISMP.  

Again, this is an ongoing error that could easily be prevented by a hard stop in the pharmacy computer for daily dosing of oral methotrexate (or if filling frequent oncology orders, for daily doses without a stop date after 5 days or less).


ISMP has written about errors with fentaNYL in more than 100 acute care newsletters—about a quarter of them are related to IV dosing errors. The most recent dosing error occurred with a 2-month-old infant who had been admitted to the hospital for a pyeloplasty. The anesthesia team started a fentaNYL infusion (200 mcg in 20 mL of 5% dextrose) to be delivered at 1 mcg/kg/hour during the surgical procedure. However, the infant received the entire 200 mcg of fentaNYL in less than an hour because the smart infusion pump had been misprogrammed to deliver 1 mcg/kg/minute instead of 1 mcg/kg/hour. The infant became hypotensive for a short interval but tolerated the procedure and was breathing spontaneously after surgery.

As with the other events, numerous risk-reduction strategies could help prevent infusion pump programming errors, but one key intervention in this case includes a hard stop during pump programming that would not allow the programming of such a catastrophic dose to continue. A hard stop in this case would have required reprogramming of the pump in accordance with preapproved dosing guidelines.


The errors described above demonstrate specific situations with amphotericin B, methotrexate, and fentaNYL in which hard stops would have protected patients from harmful medication errors. While some clinicians may complain that hard stops potentially delay order completion or slow the dispensing and administration process, the intent is to allow for a brief period of investigation to ensure safety. Clearly for drugs like amphotericin B, methotrexate, and fentaNYL, the risk of a potentially fatal dosing error far outweighs any risk of a slight delay in therapy. Another barrier may be that some clinicians find hard stops objectionable, noting that decision support should not replace the clinician’s responsibility for patients (Strom et al., 2010; van der Sijs et al., 2006). However, when relatively simple actions like thoughtfully placed hard stops could prevent harmful events and clinicians do not implement them, they are clearly not upholding their responsibility to keep patients safe from unreasonable risk. While organizations need to address any clinicians’ concerns with hard stops and make every effort to minimize any unintended effects, we suggest that all organizations place the issue of hard stops for certain drugs, including the three described above, and other preventable clinical situations on the top of their safety agendas.

This column was prepared by the Institute for Safe Medication Practices (ISMP), an independent, nonprofit charitable organization dedicated entirely to medication error prevention and safe medication use. Any reports described in this column were received through the ISMP Medication Errors Reporting Program. Errors, close calls, or hazardous conditions may be reported online at or by calling 800-FAIL-SAFE (800-324-5723). ISMP is a federally certified patient safety organization (PSO), providing legal protection and confidentiality for patient safety data and error reports it receives. Visit for more information on ISMP’s medication safety newsletters and other risk reduction tools. This article appeared originally in the September 19, 2013, issue of the ISMP Medication Safety Alert!


Eslami, S., de Keizer, N. F., Abu-Hanna, A. (2008). The impact of computerized physician medication order entry in hospitalized patients—A systematic review. International Journal of Medical Informatics, 77(6), 365-376.

Lapane, K. L., Waring, M. E., Schneider, K. L., et al. (2008). A mixed method study of the merits of e-prescribing drug alerts in primary care. Journal of General Internal Medicine, 23(4), 442-446.

Miller, R. A., Waitman, L. R., Chen, S., et al. (2005). The anatomy of decision support during inpatient care provider order entry (CPOE): Empirical observations from a decade of CPOE experience at Vanderbilt. Journal of Biomedical Informatics, 38(6), 469-485.

Moore. T. J., Walsh, C. S., & Cohen, M. R. (2004). Reported medication errors associated with methotrexate. American Journal of Health System Pharmacists, 61, 1380-1384.

Paterno, M. D., Maviglia, S. M., Gorman, P. N., et al. (2009). Tiering drug-drug interaction alerts by severity increases compliance rates. Journal of the American Medical Informatics Association, 16(1), 40-46.

Shah, N. R., Seger, A. C., Seger, D. L., et al. (2006). Improving acceptance of computerized prescribing alerts in ambulatory care. Journal of the American Medical Informatics Association, 13(1), 5-11.

Shamliyan, T. A., Duval, S., Du, J., et al. (2008). Just what the doctor ordered. Review of the evidence of the impact of computerized physician order entry system on medication errors. Health Services Research, 43(1, Pt 1), 32-53.

Strom, B. L., Schinnar, R., Aberra, F., et al. (2010). Unintended effects of a computerized physician order entry nearly hard-stop alert to prevent a drug interaction. Archives of Internal Medicine, 170(17), 1578-1583.

van der Sijs, H., Aarts, J., Vulto, A., et al. (2006). Overriding of drug safety alerts in computerized physician order entry, Journal of the American Medical Informatics Association, 3(2), 138-147.