[MT-L] Magic 5.64 BBK ISBT128 multiple unit/same donor scanning issue in TAR
Paul Goedicke
I could use some help figuring out what we need to do with a recent change we have noticed from our blood supplier for FFP.
We had been getting units with the E5730 product code, which scans as =<E5730V00 . Recently, we have been receiving apheresis units that have been multiple collections from the same donor (the unit numbers are the same) with product codes of E5730 that scan with an A or B (i.e. scans as =<E5730VA0 or =<E5730VB0). When scanned into inventory, the letter A (or B) is appended to the unit number. On a unit inquiry, that letter populates the 1st Level Division field. We’re not having an issue in BBK making a component or even issuing the units, but when Nursing scans through TAR, it’s erroring out as a mismatch for the patient – the unit number scans, but when the product code is scanned (maybe TAR waits to have both unit and product code before checking the BBK module?), we get the error. We can’t be the first site to have this issue. Does it require creating a custom I128.BT Bar Code Term and editing the Input Rule? I verified through Batch Entry of units that Meditech recognizes these product labels as FFP (because it’s looking for the E5730 code).
Meditech KB article 27257 explains what the system is doing, and KB 30636 addresses an error when scanning concatenated bar codes in the issue units routine (where we aren’t having a problem). Our Input Rule for .I128.PR appears to be identical to the rule in that article.
Any help is appreciated.
Thanks,
Paul
Paul Goedicke
Clinical Analyst III
Jackson County Memorial Hospital
1200 East Pecan
Altus, OK 73521
I hope to be the kind of person my dog thinks I am.
- anonymous
The documents accompanying this transmission contain confidential information, belonging to the sender, that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information after its stated need has been fulfilled.
If you are not the intended recipient, you are hereby notified that any reading, disclosure, copying, distribution, or action taken in reliance on the contents of these documents is strictly prohibited. Violators may be prosecuted. If you have received this email in error, please notify the sender immediately and destroy the transmitted information.
Nancy Stucky
We are C/S 5.64 (going to 5.66). We have run into this same issue with blood units and TAR. Because of that and some other things we could not accomplish we are not using TAR. Instead we have developed quite an extensive set of CDS’s for documentation in the LAB system (giving nursing limited access to the LAB application for documentation). The trade off is that the vitals are not incorporated into the same area in the EMR. But we have developed a pretty sophisticated paperless blood bank process with many safety features and work arounds in the LAB application. If you want more specific information I can put you in touch with our blood banker who did the setup.
Are these kinds of issues with the multiple units from the same donor, and FFP changed to FFP-thawed, fixed in 6.0?
Nancy Stucky, LIS Coordinator
Newton Medical Center Lab
Newton, KS
The information in this e-mail and any attachments is confidential and
intended solely for the attention and use of the named addressee(s).
It must not be disclosed to any person without proper authority.
If you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, you are not authorized to and
must not disclose, copy, distribute, or retain this message or any part of it.
Nancy Stucky
Yes, we are set up to use the specimen barcode rather than by account number.
Nancy Stucky
From: Freeman, Gale
[mailto:gfre...@shsny.com]
Sent: Thursday, March 14, 2013
10:34 AM
To: 'Nancy Stucky'; 'Paul
Goedicke'; medit...@MTUsers.com
Subject: RE: [MT-L] Magic 5.64 BBK
ISBT128 multiple unit/same donor scanning issue in TAR
Do you use the barcoding at bedside when the unit is being given ?
Linda Frederick
When you thaw E5730 are you just editing the expiration date/time in the BBK system or are you making a ‘new’ (Thawed) product using the Make Components routine?
We don’t get divided/split apheresis FFP with code E5730 (= Apheresis FRESH FROZEN PLASMA| NaCitrate/ XX/ <=-18C| Open). Each of our apheresis FFP has a different product code (such as E4689, E4693) but each is a different “container” [1st container, 2nd container]. When we thaw them, we create a new product(s) (Thawed apheresis plasma) with a unique product code derived from the original. [But we make 5 day plasma, so we must re-label using our Hematrax printer, -- you can’t make 5 day plasma from apheresis FFP from an open system.]
We are still working on TAR, but it seems we tested RBC units that were aliquoted in-house (xxxxA0) and did not encounter any problems, but I will need to confirm that.
Linda Frederick, MT(ASCP)
Blood Bank Section Chief
Phelps County Regional Medical Center
From: meditech-...@mtusers.com [mailto:meditech-...@mtusers.com]
On Behalf Of Paul Goedicke
Sent: Wednesday, March 13, 2013 3:52 PM
To: medit...@MTUsers.com
Subject: [MT-L] Magic 5.64 BBK ISBT128 multiple unit/same donor scanning issue in TAR
I could use some help figuring out what we need to do with a recent change we have noticed from our blood supplier for FFP.
CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain
confidential and privileged information for the use of the designated recipients
names above. If you are not the intended recipient, you are hereby notified that
you have received this communication in error and that any review, disclosure,
dissemination, distribution or copying of it or its contents is disallowed.
If you have received this communication in error; please notify Phelps County
Regional Medical Center immediately by telephone at (573) 458-8899 extension
4357 and destroy all copies of this communication and any attachments.
Paul Goedicke
We create a new thawed product labeled with code E2702.
Paul Goedicke
Clinical Analyst III
Jackson County Memorial Hospital
1200 East Pecan
Altus, OK 73521
I hope to be the kind of person my dog thinks I am.
- anonymous
---------------------------------------------------------------------------------------------
This email has been scanned by the JCMH IronPort appliance and has been cleared for delivery.
If you have any concerns or questions, call the IT Helpdesk at x5550.
---------------------------------------------------------------------------------------------
Nancy Stucky
I may have misunderstood something. The patient wristband has the BBK specimen label.
Nancy Stucky
From: Freeman, Gale
[mailto:gfre...@shsny.com]
Sent: Thursday, March 14, 2013
12:04 PM
To: 'Nancy
Stucky'; 'Paul Goedicke';
medit...@MTUsers.com
Subject: RE: [MT-L] Magic 5.64 BBK
ISBT128 multiple unit/same donor scanning issue in TAR
Interesting, You have the specimen barcode on the blood product, and it matches that to the patient wristband ?
We are not live yet, havent even really started it in TEST either.
Freeman, Gale
Sent: Thursday, March 14, 2013 11:28 AM
To: 'Paul Goedicke'; medit...@MTUsers.com
Freeman, Gale
Cohen, Julie - CRH
We have found in the past that when TAR gets the error message it is because the BBK techs didn’t pay attention to the “A” & “B” and when they issued they would select the “A” unit in Meditech but then they actually gave the nurse the “B” unit. Is it possible this is what happened?
From: meditech-...@mtusers.com [mailto:meditech-...@mtusers.com] On Behalf Of Paul Goedicke
Sent: Wednesday, March 13, 2013 1:50 PM
To: medit...@MTUsers.com
Subject: [MT-L] Magic 5.64 BBK ISBT128 multiple unit/same donor scanning issue in TAR
I could use some help figuring out what we need to do with a recent change we have noticed from our blood supplier for FFP.