IV compatibility checking in Epic ?

PLEASE NOTE:   Posts made to this forum should not be considered as the expressed opinions of, nor should be considered endorsed by, the Medication Safety Officer’s Society (MSOS) or the Institute for Safe Medication Practices (ISMP). 

Make sure your email is up-to-date
In order to continue to receive updates from MSOS, as well as forum posts and other valuable information as a member of MSOS, please be sure to update your email address with us, whenever it changes. If you need assistance doing so, please send an email to cmichalek@ismp.org

1 post / 0 new
Katie Cassidy
Katie Cassidy's picture
Offline
Last seen: 3 days 6 hours ago
Joined: 10/06/2017 - 09:34
IV compatibility checking in Epic ?

Hi everyone,

Wondering if anyone has successfully implemented IV incompatibility warnings/checks in Epic ? We have Medispan as our data vendor and recently learned about the IV CHEK module, we are not currently using it but looking into implementing it.

1. Have you implemented these warnings for pharmacy to check in solution compatibility? Likes and dislikes of these warnings? Alert fatigue concerns?
(We would mostly be interested in using this warning type for custom fluids and "iv builder" custom type orders.)

2. Can this warning type be used for y-site incompatibility warnings for nursing on med admin? I think the answer is no from what I have read from Epic, but hoping someone may have a good workflow for this.
(Our current process is for nursing to check Lexidrug/Trissels which we provide links on the MAR to, but this is a manual process and is sometimes missed. We also have some compatibility warnings in Alaris for common ones (calcium + phos; pip/tazo + LR), but those are manually maintained and not necessarily specific to the combo of giving the 2 drugs together. It would be great if there was a way to leverage the Medispan data for warnings in Epic instead.)

Thank for any info you have on this topic!
Katie