Model Number 106 |
Device Problem
Under-Sensing (1661)
|
Patient Problem
No Known Impact Or Consequence To Patient (2692)
|
Event Date 07/05/2016 |
Event Type
malfunction
|
Manufacturer Narrative
|
(b)(4).
|
|
Event Description
|
It was reported that the surgeon was unable to detect the patient's heartbeat during the surgical procedure.It was noted that the vns therapy was programmed on while trying to detect the heartbeat.The dhr for m106, sn (b)(4) was reviewed.The dhr was found complete and the m106 passed all testing, including the r-wave verification and the dc leakage-sense delay.Attempts for additional information have been unsuccessful to date.
|
|
Event Description
|
Additional information was received from the surgeon's vns programming system and it was found that the patient's output currents had been programmed on while the surgeon was trying to test the heart beat detection of the device.It should be noted the output currents should be programmed off while trying to test the heart beat detection.Additionally, it can be seen that during a 14 day period, the vns was able to detect 661 times where a stimulation would have been provided, indicating the device was working as expected.
|
|
Manufacturer Narrative
|
Additionally, it can be seen that during a 14 day period, the vns was able to detect 661 times where a stimulation would have been provided, indicating the device was working as expected.This information was inadvertently incorrectly reported on supplemental #01 mfr.Report.This information was inadvertently incorrectly reported on supplemental #01 mfr.Report.
|
|
Event Description
|
It was found during review of the (b)(6) 2016 that two seizures had been detected, but since autostim was programmed to 0ma, not stimulations were delivered.A valid heart ware was detected on (b)(6) 2016 appointment.Attempts for additional relevant information have been unsuccessful to date.
|
|
Search Alerts/Recalls
|