Model Number 1000 |
Device Problems
Failure to Interrogate (1332); Defective Component (2292)
|
Patient Problem
Seizures (2063)
|
Event Date 12/08/2020 |
Event Type
malfunction
|
Event Description
|
Patient presented with an increase in seizures and their device was not able to be interrogated despite using three different programming systems.It was indicated that the patient's generator could be palpated, but the generator could not be found when trying to interrogate.The patient was referred to surgery and underwent a generator replacement.The explanted device has not been received by the manufacturer to date.A review of device history records revealed that the generator passed all functional specifications and quality tests prior to distribution.No other relevant information has been received to date.
|
|
Manufacturer Narrative
|
H6 adverse event problem codes , corrected data: follow-up report #1 inadvertently left blank.
|
|
Event Description
|
The explanted generator was received but product analysis is still underway.
|
|
Event Description
|
Product analysis was completed on the returned generator.The allegations of ftp and no stimulation were duplicated in the pa lab.The electrical tests performed in the pa lab found that the generator was at an eos = yes condition.The battery voltage was measured at 1.854 volts, and the memory locations on the generator indicated that 100.649% of the battery had been consumed.The pulse generator as received felt swollen and did not meet the thickness specifications.The microprocessor (a1) was found to be the contributing factor for the reported allegations but the failure mechanism for the microprocessor (a1) was not established.
|
|
Event Description
|
Internal data was received and reviewed from the suspect generator.
|
|
Event Description
|
Additional product analysis was completed on the returned generator.Additional testing revealed multiple resets occurred but the cause of the resets could not be determined.Running the microcontroller on the breadboard failed (reset) between 5 and 10 days after starting.Additionally, attempts at jtag communication and communication with wandcomm were very inconsistent and seldomly successful.The cause of the reset could not be determined.
|
|
Search Alerts/Recalls
|