Interop Support Structure (EHS - smart pump)

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 jrufo@ismp.org. 

2 posts / 0 new
Log in or register to post comments
Last post
Thu, 09/26/2024 - 09:19
#1
Jeff Hurren
Jeff Hurren's picture
Offline
Last seen: 1 week 4 days ago
Joined: 07/05/2019 - 08:29
Interop Support Structure (EHS - smart pump)

Hi Friends, we just received approval to implement interoperability with our smart pump fleet. As we engage in the planning, I'd like to see how other folks are supporting from an org structure standpoint.

For sites live on interop, a few questions:
1. Which department maintains your smart pump library? (e.g. IT, Rx, MedSafety, etc)
2. What is the role of the individual(s) maintaining your library (e.g. RPh, etc)
2. What is the intake/update process for pump library changes?
3. Can you describe your validation process for new or modified entries?
4. What is the role of the individual(s) who validate changes?
5. If you are using a TAWF for compounding (e.g. gravimetrics) has this impacted your smart pump library and/or interop process?

Thanks so much. Historically Med Safety has maintained the smart pumps for us, but we are trying to determine if we should more closely align with our IT team vs. hand it over to them.

Top