Catalog Number UNKPULSERIDER |
Device Problem
Adverse Event Without Identified Device or Use Problem (2993)
|
Patient Problems
Stroke/CVA (1770); Vasoconstriction (2126); No Patient Involvement (2645)
|
Event Date 06/30/2018 |
Event Type
Injury
|
Manufacturer Narrative
|
Product complaint # (b)(4).Since the product was not returned for analysis, no product failure analysis can be conducted and no determination of possible contributing factors could be made. device history record (dhr) review cannot be conducted because no lot number was provided by the customer. missing information from this report is identified as blank; this information was not provided in the reported event or available at the time of report submission. information regarding patient weight, height, medical history, race, and ethnicity was not reported.
|
|
Event Description
|
This complaint is from a literature source.As reported in the literature publication entitled, ¿use of the pulserider device in the treatment of ruptured intracranial aneurysms: a case series¿ (pmid: (b)(4)).A (b)(6) female patient with a ruptured wide-necked basilar tip aneurysm who underwent pulse rider-assisted coil embolization experienced intraprocedural thrombus resolved with eptifibatide infusion.It was also reported that the patient experienced mild anterior circulation vasospasm seen on dsa, which we treated with intraarterial verapamil on post bleed day 3.This patient¿s spasm resolved by day 15 without further endovascular treatment.The aim of this study was to report a small but promising series of successful use of the pulse rider device in the acute treatment of wide-necked, ruptured basilar artery aneurysms.Methods: between (b)(6) 2018, we treated 4 cases of ruptured wide-necked basilar tip aneurysms at the (b)(6) hospital (b)(6) with pulserider-assisted coil embolization.Imaging and chart.
|
|
Manufacturer Narrative
|
This complaint has been identified as a duplicate of (b)(4).Codes have been updated to no alleged quality issue/, no adverse event, no patient involvement to prevent duplicate coding of the same event.The initial report: mwr-14112019-0000592795 has been detected as a duplicate of mwr-22052019-0000437982.All information and investigation was documented under mwr-22052019-0000438068 ((b)(4)).
|
|
Search Alerts/Recalls
|