MAUDE MDR 6523576

MDR report key
6523576
Report number
1000515253-2017-00011
Event key
0
Event type
3
Date of event
2017-02-06
Date received
2017-04-26
Adverse event
3
Product problem
3
Patients in event
0
Reporter occupation
403
Health professional
3
Initial report to FDA
3
Event location
3

Manufacturer Contact#

Report source
D
Manufacturer link flag
N

Devices#

Seq, Brand, Generic table
SeqBrandGenericManufacturerProduct codeModelCatalogLotPMA510(k)ImplantEvaluatedAvailability
1DI-60AUTOMATED CELL-LOCATING DEVICE, PRODUCT CODE: JOYCELLAVISION ABJOYDI-60 COMPLETECC286297* Y

Patients#

Sequence, Received, Treatment table
SequenceReceivedTreatmentOutcome
12017-04-260

Event Narratives#

N

Patient 1

THIS EVENT ONLY OCCURS IF THE USER INCORRECTLY PLACES A SP-10 BARCODE READ ERROR SLIDE, ON THE DI-60. WHEN THE SP-10 CREATES THIS TYPE OF SLIDE, THE ORDER ID BEGINS WITH THE PREFIX 'ERR.' THE DI-60 INSTRUCTIONS FOR USE, SECTION A3 - MATERIALS SPECIFICATION, SECTION A.3.4 - BARCODES, INSTRUCTS THE OPERATOR: "ALL SLIDES MUST BE LABELED WITH AN ORDER ID IN THE FORM OF A BARCODE. THE BARCODE MUST CONTAIN ONLY THE ORDER ID AND NO OTHER ORDER DATA. THE ORDER ID MAY BE UP TO 24 CHARACTERS (ASCII), INCLUDING SPACES. IT MUST NOT BEGIN WITH: PB, BFS, ERR, QC (RESERVED FOR CELL LOCATION TEST SLIDES), A SPACE." IF THE SLIDE IS PLACED ON THE DI-60, IT WILL ALERT THE OPERATOR TO A BARCODE READ ERROR. THE OPERATOR HAS THE ABILITY TO REASSIGN THE ORDER ID TO IDENTIFY ANY BARCODE READ ERRORS GENERATED BY THE DI-60. THE DI-60 INSTRUCTIONS FOR USE, SECTION 4 - VERIFYING PROCESSED SLIDES, SECTION 4.1.7 - EDIT ORDER ID STATES "THE ORDER ID CAN ONLY BE EDITED IF IT STARTS WITH "ER". IF A BARCODE CANNOT BE READ, AN IMAGE OF THE BARCODE WILL BE SAVED INTO THE DATABASE RECORD. THE SLIDE WILL BE GIVEN AN ORDER ID STARTING WITH "ERR" FOLLOWED BY THE CURRENT DATE AND TIME (ERRYYYYMMDDHHMMSS) AND PROCESSED USING DEFAULT SETTINGS." THE ERR BARCODE LABELS GENERATED BY THE SP-10 HAVE A COMPLETELY DIFFERENT RANGE OF NUMBERS (E.G. ERR000000001) THAN THE ERR ORDER-IDS CREATED BY THE DI-60 (E.G. ERR20170323101925). THIS IS AN INDICATION TO THE OPERATOR THAT THE INCORRECT SLIDE WAS PLACED ON THE DI-60. THERE HAVE BEEN NO REPORTED CASES OF SAMPLE MISMATCH, HOWEVER THE POSSIBILITY EXISTS. THE EVENT WAS RECREATED BY A (B)(6) CAS DURING INSTALLATION OF THE DI-60 DEVICE LOCATED AT CUSTOMER SITE: (B)(4).

D

Patient 1

A (B)(6) CLINICAL APPLICATIONS SPECIALIST (CAS) WAS ONSITE PERFORMING INSTALLATION OF THE DI-60 DEVICE. THE CAS RECREATED AN ISSUE WHERE THE DI-60 STORED AN IMAGE OF A PREVIOUS BARCODE READ ERROR. WHEN AN ERROR SLIDE FROM THE AUTOMATED SLIDE PREPARATION UNIT (SP-10) IS ANALYZED, THE DI-60 DISPLAYS THE IMAGE OF A PREVIOUS DI-60 BARCODE READ ERROR. THE OBSERVED EVENT IS AS FOLLOWS: THE SP-10, WHICH CREATES AND LABELS BLOOD SMEAR SLIDES, CREATES SLIDE 1 WITH NO ISSUES. SLIDE 2 HAS A BARCODE READ ERROR AND IS ASSIGNED A SEQUENTIAL ERROR NUMBER BY THE SP-10 (I.E. ERR000000001). THE SP-10 ALERTS THE OPERATOR OF THE ERROR WITH AN AUDIBLE ALARM AND THE ASSIGNED ERROR ID# APPEARS ON THE WORK LIST HIGHLIGHTED IN RED. THE OPERATOR MUST FOLLOW THE ONSCREEN INSTRUCTIONS TO RESOLVE THE ERROR. THE SLIDE IS HELD BY THE SP-10 FOR FURTHER VERIFICATION BY THE OPERATOR. THE OPERATOR DOES NOT PERFORM FURTHER VERIFICATION AND INCORRECTLY PLACES SLIDE 2 ON THE DI-60. SLIDE 1 IS PROCESSED BY THE DI-60 AND GENERATES A BARCODE READ ERROR (I.E. THE BARCODE PRINT IS TOO FAINT, BLURRY, MARKINGS THROUGH BARCODE, ETC.). THE DI-60 ASSIGNS THE SLIDE AN ERROR ID# USING THE FORMAT OF 'ERRYYYYMMDDHHMMSS' AND STORES A DIGITAL IMAGE OF SLIDE 1'S ID LABEL. SLIDE 2 IS PROCESSED BY THE DI-60, WHICH READS THE SP-10 ERROR NUMBER 'ERR000000001' AND INCORRECTLY ATTACHES AN IMAGE TAKEN FROM AN ERROR GENERATED PREVIOUSLY; IN THIS CASE, THE IMAGE OF SLIDE 1 ID LABEL IS DISPLAYED. THERE IS A POSSIBILITY THAT THE OPERATOR MAY REVIEW THE ERROR SLIDE 'ERR000000001' (SLIDE 2) WITH THE IMAGE OF SLIDE 1 ID LABEL DISPLAYED AND MANUALLY IDENTIFY THE SLIDE INCORRECTLY. THIS MAY RESULT IN A SAMPLE MISMATCH. NO ERRONEOUS RESULTS WERE REPORTED AS THE ANALYZER WAS BEING IMPLEMENTED AND WAS NOT YET RELEASED TO THE OPERATOR. THE ISSUE WAS ESCALATED TO CELLAVISION, MANUFACTURER OF THE DI-60. A PRELIMINARY INVESTIGATION REPORT FROM CELLAVISION DATED MARCH 10, 2017 IDENTIFIED A DI-60 SOFTWARE ANOMALY.