Jump to content

Epic Blood Admistration Module vs Soft TX


Recommended Posts


SoftID Tx is much more comprehensive.  It's been around for awhile, and a lot of effort was put in it to make it really user friendly and foolproof.  You can document much more than Epic currently allows, like blood warmer temperatures.  And you can put "reference ranges" for vital signs which will automatically order a Transfusion Reaction workup if the vitals are out from baseline.

 

Epic is brand new, was just FDA approved early this year, so it needs some improvement.  Hopefully after a few upgrades it will be better.  Since Epic was included in our system, we'll be implementing it soon.  But it will need a lot of testing and workarounds for now.  We're just really looking forward to getting away from paper blood admin records.

Link to comment
Share on other sites

We are attempting to interface the Epic Blood Admin module with Cerner Millennium BB and not working out very well in the interface setup.  Is there another BB system already set up with the Epic Blood Admin out there? Or someone who may have accomplished this already?

Link to comment
Share on other sites

Aubergine,

 

We are a Cerner Millennium site also looking at interfacing blood product info with Epic BPAM. We've just started investigating it, so it sounds like you're further along than we are. There are a few threads about it in uCern. Also, we spoke with folks from St. Elizabeth's Healthcare in Kentucky - they are Millennium and have it up and running with Epic. You may want to contact them.

Good luck!

Link to comment
Share on other sites

We are not live with Epic yet but are implementing the BPAM (we have SoftBank).  From a BB perspective, Soft Tx would be better but we were not allowed the option.  As for interfacing with your BB system, you have to find out if your system can send in discreet OBX segments for the Unit number, Unit Status, ISBT-128 product code and ISBT-128 blood type barcode.  Product expiration date is optional (Soft can not send the expiration).  One thing I learned is that Epic does not want the ISBT-128 data identifiers. For example, if for product code E0382V00 youjr system sends =<E0382V00 you will need your interface engine strip off the =<.  Same for the =% for the blood type and = for the DIN.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Advertisement

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.