Catalog Number MK06000 |
Device Problems
Circuit Failure (1089); Gas Output Problem (1266); Failure to Deliver (2338)
|
Patient Problem
Insufficient Information (4580)
|
Event Date 10/26/2022 |
Event Type
malfunction
|
Manufacturer Narrative
|
The investigation has just started; results will be provided in a follow-up report.
|
|
Event Description
|
It was reported that during use, a ¿turbovent2 failure" was displayed and ventilation stopped.After restarting the device, it recovered.There was no patient injury reported.Same failure for identical device has been reported before (date of emdr on 2022-12-14 under mdr report no.9611500-2022-00340) for date of event on (b)(6) 2022.However, it was found that the same issue occurred on (b)(6) 2022 as well.It could not be excluded that a patient was involved during that case leading to this separate report for the issue on (b)(6) 2022.
|
|
Manufacturer Narrative
|
The device log file analysis revealed that on the reported date of event a signal failure of the control responsible for the motor speed and motor direction occurred.The signal was not transmitted correctly leading to the reported turbo vent 2 failure.The device has reacted on the detected deviation as specified by posting a corresponding alarm.In this case automatic ventilation is no longer possible.Fresh gas and manual ventilation remain available.The sporadic failure could be traced back to a faulty component onboard the pcb a500 blower.The field-failure-rate of the pcb a500 blower is accepted by the responsible product quality board.The number of similar cases, related to the same root cause, is within the expected range of the respective risk assessment and thus accepted.
|
|
Event Description
|
It was reported that during use, a ¿turbovent2 failure" was displayed and ventilation stopped.After restarting the device, it recovered.There was no patient injury reported.Same failure for identical device has been reported before (date of emdr on (b)(6) 2022 under mdr report no.9611500-2022-00340) for date of event 2022-11-14.However, it was found that the same issue occurred on (b)(6) 2022 as well.It could not be excluded that a patient was involved during that case leading to this separate report for the issue on (b)(6) 2022.
|
|
Search Alerts/Recalls
|