openFDA Device Enforcement
Report-date coverage
June 20, 2012–July 08, 2026
Known gap: openFDA describes 2004-present coverage, but the current export has no report-date records in this interval.
openFDA Device Recall
event_date_initiated coverage
June 01, 1997–June 30, 2026
Enforcement coverage uses report dates; product initiation dates can precede those bounds. Device-enrichment coverage uses FDA event_date_initiated.
Product dates, classifications, firms, and source wording remain attached to their individual rows.
Opening this dossier never hides products that did not match a prior timeline filter.
device · product 1 of 5
VITROS 3600 Immunodiagnostic System Product Code 6802783 and Refurbished Product Code 6802914 Running Software Version 3.8.0
During planned monitoring of data post-release of Software Version 3.8.0 an increased occurrence of software issues relating to unresponsive subsystems, unresponsive user interface (sometimes referred to as a screen freeze), and/or printer disconnections was identified. The consequence of these issues would be a delay in reporting results due to the required system shutdowns to recover the system. This delay in reporting results could occur during any assay, including which the speed of the result is deemed critical or STAT and could result in a delay of treatment in a patient. Due to the release strategy of this software version, the user could not update the system but a field engineer had to manually install each affected system.
During planned monitoring of data post-release of Software Version 3.8.0 an increased occurrence of software issues relating to unresponsive subsystems, unresponsive user interface (sometimes referred to as a screen freeze), and/or printer disconnections was identified. The consequence of these issues would be a delay in reporting results due to the required system shutdowns to recover the system. This delay in reporting results could occur during any assay, including which the speed of the result is deemed critical or STAT and could result in a delay of treatment in a patient. Due to the release strategy of this software version, the user could not update the system but a field engineer had to manually install each affected system.
During planned monitoring of data post-release of Software Version 3.8.0 an increased occurrence of software issues relating to unresponsive subsystems, unresponsive user interface (sometimes referred to as a screen freeze), and/or printer disconnections was identified. The consequence of these issues would be a delay in reporting results due to the required system shutdowns to recover the system. This delay in reporting results could occur during any assay, including which the speed of the result is deemed critical or STAT and could result in a delay of treatment in a patient. Due to the release strategy of this software version, the user could not update the system but a field engineer had to manually install each affected system.
During planned monitoring of data post-release of Software Version 3.8.0 an increased occurrence of software issues relating to unresponsive subsystems, unresponsive user interface (sometimes referred to as a screen freeze), and/or printer disconnections was identified. The consequence of these issues would be a delay in reporting results due to the required system shutdowns to recover the system. This delay in reporting results could occur during any assay, including which the speed of the result is deemed critical or STAT and could result in a delay of treatment in a patient. Due to the release strategy of this software version, the user could not update the system but a field engineer had to manually install each affected system.
During planned monitoring of data post-release of Software Version 3.8.0 an increased occurrence of software issues relating to unresponsive subsystems, unresponsive user interface (sometimes referred to as a screen freeze), and/or printer disconnections was identified. The consequence of these issues would be a delay in reporting results due to the required system shutdowns to recover the system. This delay in reporting results could occur during any assay, including which the speed of the result is deemed critical or STAT and could result in a delay of treatment in a patient. Due to the release strategy of this software version, the user could not update the system but a field engineer had to manually install each affected system.