marisapete

We have had Epic for approximately 6 years. We are just beginning the build of the new blood administration module that came out with the Spring 08 release. We've had initial discussions with Epic on their bedside barcoding capabilities for blood administration in this module. It is my understanding that they do have the ability to match the barcoded unit number at bedside with the product that is released in the Transfusion Services LIS. However, this functionality is dependent on the LIS/Epic result interface. We will be having our first in depth technical meeting with Epic to explore the dependencies in two weeks. I'll keep you updated on what I find out. Marisa PS for those who want to hear my (extensive) thoughts on Epic implementation: I totally support Teri's comments about inserting yourself into the process early and developing a structure for lab to be involved in decision making in all applicable areas (although I would go one further and suggest a structure that requires outright approval/ownership by lab). This includes order entry and all it entails (order/EAP development, preference lists, order sets, order questions and defaulting answers, stop signs, best practice alerts, programming points, etc.), as well as documentation flowsheets for blood administration. But it also involves result displays, smart text resulting in physician notes/H&Ps/letters, flowsheet result interfaces and enter/edit functionality which all have issues displaying those pesky little lab items like reference ranges, abnormal flags and performing lab. Also make sure you're involved in the upgrade functionality communications, so you learn when they develop new functionality that will address your lab issues. No one will be better at understanding how the functionality can be used to enhance laboratory ordering and resulting and where it may be problematic than those individuals who have the years (and usually decades) of laboratory event management under their belt. All that being said, I think the Epic system is a wonderful tool, and wouldn't go back to the "old way of doing things". However, I keep hearing from other/new Epic users that this continues to be a very painful process for lab, which leads me to believe that Epic hasn't learned the lesson yet either.

Thank you both so much for your feedback! I will definitely keep your comments in mind as we move forward.

Greetings, Our hospital system is performing an RFP for purchase of an automated recall management system. The systems that are out there (like RASMAS and Hazard Track) are mainly aimed at managing medical device and pharmaceutical recalls, but they say they also include automatic notification of blood product and laboratory product recalls and safety alerts. Are any of your hospitals utilizing an automated product recall management system? If yes, what system are you using and how do you use the system in the Transfusion Service/Blood Bank environment? Any help or feedback would be appreciated. Marisa

We recently received Echo's at four of my hospitals. I was searching the site for ideas, as I start to write the validation plans, and came upon this great thread. Is anybody willing to share their validation plan? Marisa Peterson Minneapolis, MN