| Model Number |
560BCS1 |
| Medical Device Problem Code |
Device Alarm System (1012)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
10/09/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Event or Problem Description
|
|
It was reported that during use of a bio-console 560 instrument an error code 27 occurred.The use of the instrument was unspecified.No patient complications have been reported as a result of this event.
|
| |
|
Additional Manufacturer Narrative
|
|
B.5.It was reported that during use of a bio-console 560 instrument an error code 27 (sc mpu fs demodulator hard, error) occurred.The use of the instrument was unspecified. no patient complications have been reported as a result of this event.Medtronic received additional information that restarting the device did not resolve the issue.It was considered that the error was caused by a motherboard failure device evaluation::the reported error code 27 was verified during service.The issue was resolved by replacing the 560 bioconcole flow module.Preventive maintenance was performed per specifications.Correction.B.3.Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Search Alerts/Recalls
|