|
|
| Model Number |
10049998 |
| Medical Device Problem Code |
No Flow (2991)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
09/19/2022
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Device evaluation summary: medtronic conducted an investigation based upon all information received.It was reported that the 840 ventilator continued to ventilate the patient when the unit generated a breath delivery (bd) electrically erasable programmable read-only memory (eeprom) background check breath delivery unit (bdu) alarm.Although the customer reported that the device continued to deliver breaths, the ventilator would go into an inoperative condition and the diagnostic code generated would lead to loss of ventilation.The device was available for evaluation.The service personnel (sp) inspected the ventilator, confirmed that the unit had a loss of ventilation in memory with generated bd eeprom background check bdu alarm, and replaced the bd central processing unit (cpu) printed circuit board assembly (pcba).The device passed all required tests and calibrations as per the manufacturer's specifications and was in working condition.The likely cause of the event was isolated in the field to a potential fault in the bd cpu pcba.The manufacturing records for each device are thoroughly reviewed prior to release to ensure that it has met all medtronic quality specifications.Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided 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.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.A good faith effort will be made to obtain the applicable information relevant to the report.If information is provided in the future, a supplemental report will be issued.
|
| |
|
Event or Problem Description
|
|
It was reported that the 840 ventilator continued to ventilate the patient when the unit generated a breath delivery (bd) electrically erasable programmable read-only memory (eeprom) background check breath delivery unit (bdu) alarm.The patient was bagged before transferring to an alternate ventilator without injury.Although the customer reported that the device continued to deliver breaths, the ventilator would go into an inoperative condition and the diagnostic code generated would lead to loss of ventilation.
|
| |
|
Additional Manufacturer Narrative
|
|
Correction section g 510k# section d9 was updated due to part return section h6 evaluation code result - additional code added h3 device evaluation summary: updated due to part return medtronic conducted an investigation based upon all information received.It was reported that the 840 ventilator continued to ventilate the patient when the unit generated a breath delivery (bd) electrically erasable programmable read-only memory (eeprom) background check breath delivery unit (bdu) alarm.Although the customer reported that the device continued to deliver breaths, the ventilator would go into an inoperative condition and the diagnostic code generated would lead to loss of ventilation.The device was available for evaluation.The service personnel (sp) inspected the ventilator, confirmed that the unit had a loss of ventilation in memory with generated bd eeprom background check bdu alarm, and replaced the bd central processing unit (cpu) printed circuit board assembly (pcba).The device passed all required tests and calibrations as per the manufacturer's specifications and was in working condition.One bd cpu pcba was retuned to medtronic for further analysis.Visual inspection of the returned bd cpu pcba found no anomalies.The returned pcba was installed to the test unit and powered up.Analysis found the bd operating software was corrupted.The cause of the event was isolated to a fault in bd cpu pcba.The manufacturing records for each device are thoroughly reviewed prior to release to ensure that it has met all medtronic quality s pecifications.The event is included in a trending and monitoring plan.Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided 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.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.A good faith effort will be made to obtain the applicable information relevant to the report.If information is provided in the future, a supplemental report will be issued.
|
| |
|
Search Alerts/Recalls
|
|
|