Catalog Number 256082 |
Device Problem
Incorrect, Inadequate or Imprecise Result or Readings (1535)
|
Patient Problem
No Information (3190)
|
Event Date 10/14/2020 |
Event Type
malfunction
|
Manufacturer Narrative
|
Medical device expiration date: unknown.Device manufacture date: unknown.A device evaluation and/or device history review is anticipated, but is not complete.Upon completion, a supplemental report will be filed.(b)(4).
|
|
Event Description
|
It was reported while testing for sars cov-2 a false positive result was obtained.It is unknown what type of confirmatory testing was performed.Multiple attempts have been made to obtain additional information, with no response from the customer at this time.Eua#: (b)(4).
|
|
Event Description
|
It was reported while testing for sars cov-2 a false positive result was obtained.It is unknown what type of confirmatory testing was performed.Multiple attempts have been made to obtain additional information, with no response from the customer at this time.Eua#: (b)(4).
|
|
Manufacturer Narrative
|
Eua#: (b)(4).H6: investigation summary: bd has received several customer complaints for false positive results, when using bd sars-cov-2 reagents for bd veritor¿ system.The current investigation concerns multiple lots of bd sars-cov-2 reagents for bd veritor¿ system.Bd takes a systematic approach to investigating false positive complaints that are received.This approach involves review of manufacturing batch history records, testing of retention samples, and testing of customer returned samples if applicable.Due to unknown lot# a dhr could not be performed.The investigation did not find a root cause for the false positive results that were observed.It is recommended that each customer review their workflow carefully to ensure that the package insert is being followed as written.The root cause is under investigation and will be documented in our quality system.Bd cannot confirm the complaint based on the investigation that was performed.A corrective and preventive action (capa#1878253) is already initiated to investigate the root cause and some mitigation actions are already being addressed.H3 other text : see h10.
|
|
Search Alerts/Recalls
|