Jump to content

Epic Transfusion Administration System?


Recommended Posts

Lattice Inc. offers an FDA Cleared Transfusion Administration / Positive Patient Identification system that interfaces to your existing Blood Bank, and documents each transfusion in your EMR.  Please visit www.lattice.com for more information or contact sales@lattice.com

Link to comment
Share on other sites

We are currently working with one of the hospitals implementing the Epic Blood Product Administration System (BPAM). It is matching the scanned blood bag to the patient. The nurse scans the patient, the unit number (DIN) and product code. We are fortunate that we built the E codes one to one in Sunquest when we built the BB module so the E codes go back to Epic. 

Link to comment
Share on other sites

EPIC does have an FDA Approved module for Blood Administration. It is called Blood Product Administraton Module (BPAM) That was cleared in 2014. It can recognize whether or not a unit of blood/component is for the correct patient when the unit is scanned.

Epic Systems Corporation
1979 Milky Way
Verona, WI 53593
Blood Product Administration Module, version 0.9              BK130037               03/06/2014

When transfusing a unit the patient's barcoded arm band is scanned and then the unit is scanned. Epic checks for the unit number in the patient's blood bank results. If the unit is not one that is resulted to the patient it gives an error. Nursing also uses an electronic blood administration flowsheet for recording that all information was checked (just like they do on paper) then they scan their id badges to sign off that everything was checked and correct. The flowsheet is customizable to fit your facilities requirements.

We currently use a Sunquest as our LIS, interfaced with Epic.

Link to comment
Share on other sites

Timely information. We are in the process of an Epic build for our facility. Blood Bank will use Haemonetics and interface with Epic - eventually. I haven't seen anything about transfusion yet from the build team so will make sure our LIS person is aware of this info.

Link to comment
Share on other sites

AMcCord,

If your BB is Haemonetics (or any of the other BB systems), your build team will still need to do some LIS build to get the BB tests from your LIS (we use Beaker) into Haemonetics.  They will also need to decide how they are going to do billing, if that hasn't been disucssed already.

With Epic 2015 the blood products do not go to the LIS, they go directly into the BB system, tests still go through the LIS.

Even though BB is not Epic, if you LIS team would include you on discussions when they do this build it may save some headaches going forward.  Unless you happen to have a Blood Banker on your LIS team.

The BB will also be receiving the "orders to transfuse" from Epic.  If this sounds foreign don't feel bad.  I have been building Epic Beaker and Mediware HCLL for 5 years and it does take a bit to learn the lingo.

 

Link to comment
Share on other sites

18 hours ago, Likewine99 said:

AMcCord,

If your BB is Haemonetics (or any of the other BB systems), your build team will still need to do some LIS build to get the BB tests from your LIS (we use Beaker) into Haemonetics.  They will also need to decide how they are going to do billing, if that hasn't been disucssed already.

With Epic 2015 the blood products do not go to the LIS, they go directly into the BB system, tests still go through the LIS.

Even though BB is not Epic, if you LIS team would include you on discussions when they do this build it may save some headaches going forward.  Unless you happen to have a Blood Banker on your LIS team.

The BB will also be receiving the "orders to transfuse" from Epic.  If this sounds foreign don't feel bad.  I have been building Epic Beaker and Mediware HCLL for 5 years and it does take a bit to learn the lingo.

 

Actually what you are saying does have familiar info in it. Our complication is that we are going into Epic as the 'little brother' of another very large facility even though we and they are not part of a 'system' (but we are part of a collaboration). We are just piggybacking onto their Epic build which means that what we get initially is what they have. The fun part is going to be the fact that we are not going to run the same lab or blood bank information systems as big brother. The folks working on the build on our end (mainly nurses and IT at this point), forget that we have needs that must be met during the build process because they don't understand how the lab works and don't seem to grasp fully how lab must integrate into the build for the HIS. From time to time the lab LIS tech (who is an MT with a generalist background) or our director has to focus them on things that just haven't occurred to them, sometimes after decisions have been made that are going to cause problems for the lab if not fixed.

This transfusion piece is one I want them to be thinking about from the ground up so we don't get stuck with something that doesn't work well. Our LIS build (Orchard) is concurrent with the Epic build and they know they have to fit Haemonetics into the mix down the road - they swear they've done it before and can handle it. I have all my fingers and toes crossed but I'm sure I'll be a totally crazy person by the time it is all up and running.

Edited by AMcCord
Link to comment
Share on other sites

 

On ‎8‎/‎6‎/‎2016 at 2:15 PM, Likewine99 said:

AMcCord,

If your BB is Haemonetics (or any of the other BB systems), your build team will still need to do some LIS build to get the BB tests from your LIS (we use Beaker) into Haemonetics.  They will also need to decide how they are going to do billing, if that hasn't been disucssed already.

With Epic 2015 the blood products do not go to the LIS, they go directly into the BB system, tests still go through the LIS.

Even though BB is not Epic, if you LIS team would include you on discussions when they do this build it may save some headaches going forward.  Unless you happen to have a Blood Banker on your LIS team.

The BB will also be receiving the "orders to transfuse" from Epic.  If this sounds foreign don't feel bad.  I have been building Epic Beaker and Mediware HCLL for 5 years and it does take a bit to learn the lingo.

 

We have been using Epic BPAM since December 2014 with Cerner which required a workaround to get units to go to Epic.  We are moving to Epic Beaker and Mediware HCLL in October 2017.  We do have an experienced Blood Banker on the LIS team but any tips in the build would be appreciated.  The Beaker build has started but the HCLL build starts in October 2016.

Link to comment
Share on other sites

  • 1 month later...
On 8/6/2016 at 8:30 AM, AMcCord said:

Timely information. We are in the process of an Epic build for our facility. Blood Bank will use Haemonetics and interface with Epic - eventually. I haven't seen anything about transfusion yet from the build team so will make sure our LIS person is aware of this info.

We are using Haemonetics and will be interfacing it to Beaker and Epic EMR.  We should start the build by the end of the year.  We may need to stay in touch. :) 

Link to comment
Share on other sites

  • 2 weeks later...

We're also using Epic and struggling with how the doctors place their blood orders. Epic doesn't alert them even if same orders have just been placed. So they could order 8x of 2 units of RBC for example when actually, they only need 2 units. Calls will still be back and forth just because of the duplicate orders which if only the Epic alerted them would not have been placed.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • 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.