Drug Interaction Data for EHRs and ePrescribers

Hospitals are complex organizations with many different systems used by different departments, and often not well integrated. All kinds of errors can occur -- human errors, data-entry errors, labeling errors. And unfortunately, sometimes those errors have fatal consequences, such as this case of a premature infant that received a lethal dose of sodium due to a parenteral nutrition compounding error.

In this particular case, the death was reported to have led from incorrect data entry into the compounder, insufficient oversight by the pharmacist, incorrect labeling, and an unfulfilled physician request for investigation into abnormally high sodium levels in the infant. Though neither the EMR nor the CPOE were directly implicated in the error this time, it's always worth thinking about whether your system would have been capable of preventing this mistake -- and if not, what you may need to change.

Needed: Dose range checking -- and then some
In order for any system to have detected this error, some form of dose range checking would need to have been in place. This wasn't a result of an adverse drug event or an improperly prescribed medication, so Meaningful Use interaction and allergy checking are of no use. Only knowledge of the correct dosage for this specific patient would help.

In fact, not even all dose range checking would be helpful. This patient belonged to a special class -- a neonate. So the dose checking would need to be differentiated between adult and pediatric (or, in this case, neonatal). Otherwise, a dose that would be appropriate for an adult but fatal to an infant could easily be prescribed.

IV compatibility also an issue
This case also dealt with a solution administered intravenously. In this particular case, there was no adverse reaction between the ingredients being compounded, but with IV administration that's always a possible danger. Therefore, to be 100% safe, your EHR or HIS would also need to contain information about IV Y-site compatibility.
 
And of course, all of this would need to be checked and double-checked at every stage of the process by every clinician: the physician entering the order into the CPOE, the pharmacist compounding the solution, and the nurse administering it to the patient. The systems that each clinician uses should be able to check for each of these factors (and more!), and also should be able to provide the clinicians with more "human readable" information in case something doesn't seem right.

With the state of healthcare IT today, most of us are still a long way off from being able to implement a perfectly integrated system that can eliminate this kind of error entirely. But taking a few steps with the systems we have control over can reduce tragic outcomes like this one. One place to start is to contact a clinical and drug information vendor like Lexicomp to find out what information is available to be integrated into your systems -- both transactionally for automatic clinical decision support and as reference material for clinicians to make use of.