|
Catalog Number 05168589190 |
Device Problems
High Test Results (2457); Non Reproducible Results (4029)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 10/23/2023 |
Event Type
malfunction
|
Event Description
|
The initial reporter received questionable crep2 (creatinine) results from four patient samples tested on the cobas 8000 cobas c 701 module.The initial results were not reported outside of the laboratory.The reporter complained that the creatinine results were high which prompted the rerun of the patient samples.Sample id (b)(6): on (b)(6) 2023, the initial result was 5.86 mg/dl.The repeat result was 1.03 mg/dl.Sample id (b)(6): on (b)(6) 2023, the initial result was 6.77 mg/dl.The repeat result was 4.03 mg/dl.Sample id (b)(6): on (b)(6) 2023, the initial result was 4.74 mg/dl.On (b)(6) 2023, the repeat result was 0.72 mg/dl.Sample id (b)(6): on (b)(6) 2023, the initial result was 2.85 mg/dl.On (b)(6) 2023, the repeat result was 1.00 mg/dl.
|
|
Manufacturer Narrative
|
The serial number of the customer's cobas 8000 cobas c 701 module is 18l0-07.The investigation reviewed the calibration on (b)(6) 2023; the results were within specifications.The investigation reviewed the quality control (qc) recovery; qc level 1 recovery was within +/- 2 standard deviations (sd); the results were within specifications.The investigation reviewed the alarm trace on (b)(6) 2023; the trace had frequent "abnormal sample aspiration" alarms.A precision check was performed with acceptable results.The investigation is ongoing.
|
|
Manufacturer Narrative
|
Medwatch fields d.Device identification, g1 and g4 pma / 510k (premarket numbers) were updated.The field service engineer (fse) checked the gear pump pressure, reagent probe inside and outside rinses, sample probe rinse, and cell rinse.He also checked the correct height of the reagent probes.The investigation determined the event was consistent with a maintenance-related issue.After service, no further issues were reported by the customer.The investigation determined the service actions resolved the issue.
|
|
Search Alerts/Recalls
|
|
|