iSTAT Scanning Errors

not so far...

We just went live with ACTk two weeks ago. I have had 2 incidence where it looks like the iSTAT is picking up the medical record number instead of the encounter number.

Our Emergency Department just started having issues after the update too... It's scanning the user's badge fine but not the patient armband.

I've seen a random one insert an exclamation point in place of a number but otherwise nothing obvious.   Ivy

I've had scanning errors since the update but it is only with the associates badges.  It will scan some but not all.  Scans MR# fine.

Haven't seen any here.

We have not seen any problem with barcode scanning. 
Check your  barcode printer to make sure it is clean..  
A speck of errant ink  dust can cause this problem. 

We have seen at least 8 instances of scanning errors.  Sometimes it's the first 4 digits of the patient ID ("6100" is replaced by "5853").  Sometimes it's in the middle of the ID ("3516" is replaced by "0215").  This has happened randomly in different locations.
I do not believe it has anything to do with barcode quality.  The same wristband sometimes scans correctly.  We just had a suspect band sent to our lab, and we could not duplicate the failure.
THANK YOU to the POCT community for bringing this to our attention.  We thought it was operator error

We have been seeing issues since Oct 2018 on all our POC devices (Nova, iSTAT, ABL90,etc).  We have tried all avenues of testing to include barcode quality analysis, changing armbands to better quality, reviewing EPIC upgrades and vendor upgrades for clues to any changes made, reviewing DPI printer settings, and printer driver settings.  We see transposition of numbers and replacement of numbers with symbology.  We have pulled IT analysts in throughout the process and find varying amounts of support, depending on IT department, but none have been able to help us.  If anyone out there has solved this issue, I can pay in food and Starbucks!!!