| Model Number |
3000 |
| Medical Device Problem Code |
Computer Software Problem (1112)
|
| Health Effect - Clinical Code |
No Known Impact Or Consequence To Patient (2692)
|
| Date of Event |
03/12/2020
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
It was reported that after programming patient for guided mode and setting the patient on step 2, the set values of the normal stimulation, magnet mode and autostim did not line up with the custom protocol step values for stimulation.No further relevant information has been received to date.
|
| |
|
Additional Manufacturer Narrative
|
|
(b)(4).
|
| |
|
Event or Problem Description
|
|
Further review of data shows that the programmer was successful in creating the protocol and initiating steps 1 and 2 of that protocol which matches the piexport.The values seen on session report and shown in piexport are no backed up by logged files.There was no interrogation or information shown that would transpire between the ipg and programmer that would cause the incorrect normal output current value.If this device were to be interrogated again, the correct values should still be programmed and it was the programmer that caused values to be displayed.Around the time of step 2 of the protocol being implemented there were a lot of communication errors.Incorrectly seen on session report were likely caused by communication errors seen and perhaps some default values seen in the programmer background.
|
| |
|
Additional Manufacturer Narrative
|
|
B5.Event description - correction - inadvertently piexport review was not added in previous supplemental mdr submitted.H6.Results code - correction inadvertently no listed in previous supplemental mdr submitted.
|
| |
|
Search Alerts/Recalls
|