Model Number 37800 |
Device Problem
Adverse Event Without Identified Device or Use Problem (2993)
|
Patient Problems
Nausea (1970); Pain (1994); Complaint, Ill-Defined (2331); Abdominal Distention (2601)
|
Event Type
Injury
|
Manufacturer Narrative
|
Concomitant medical products: product id: 4351-35.Implanted: (b)(6) 2018, product type: lead; product id: 4351-35, implanted: (b)(6) 2018, product type: lead.If information is provided in the future, a supplemental report will be issued.
|
|
Event Description
|
The patient¿s healthcare provider reported via manufacture representative that the patient presented at the clinic on (b)(6) 2018 for a routine checkup.The nurse made step changes from 5 ma to 7.5 ma as per pathway as the patient still experienced nausea although there was improvement.The patient reported a distended tummy and pain after one-hour post programming change.It was noted that at the patient¿s previous appointment only a nominal change had occurred.No environmental/external/patient factors were noted that may have led or contributed to the issue.The patient was scheduled to see their healthcare provider on (b)(6) 2018 to change the settings back to 5 ma.No further complications were reported.Additional information reported that had volvulus, ischaemic bowel and had a right side hemicolectomy.It was unknown if the event was resolved.No further complications were reported.Additional information reported that the patient was discharged (b)(6) 2018 and had a follow up in the clinic (b)(6) 2019.The patient¿s healthcare provider did not feel that the volvulous was connected to the device programming.
|
|
Manufacturer Narrative
|
Continuation of concomitant medical products: product id: 4351-35, serial# unknown, implanted: (b)(6) 2018, product type: lead; product id: 4351-35, serial# unknown, implanted:
(b)(6) 2018, product type: lead.If information is provided in the future, a supplemental report will be issued.
|
|
Event Description
|
Additional information reported that the patient is well, the issue resolved and there appeared to be no connection to enterra.No further complications were reported.
|
|
Search Alerts/Recalls
|
|