MICRO THERAPEUTICS, INC. DBA EV3 PIPELINE FLEX W/SHIELD TECHNOLOGY; INTRACRANIAL ANEURYSM FLOW DIVERTER
|
Back to Search Results |
|
Model Number PED2-350-12 |
Device Problems
Unintended Movement (3026); Physical Resistance/Sticking (4012)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 08/02/2021 |
Event Type
malfunction
|
Manufacturer Narrative
|
If information is provided in the future, a supplemental report will be issued.
|
|
Event Description
|
Medtronic received a report that two pipeline devices moved during deployment and could not be resheathed into the phenom 27 microcatheter.The patient was undergoing treatment for an unruptured, saccular aneurysm located in the left posterior communicating artery.The max diameter was 4mm, and the neck diameter was 2mm.The patient's vessel tortuosity was normal.The landing zone was 2.91mm distal and 3.50mm proximal. dual antiplatelet treatment was administered, and the pru level was 161.It was reported that the phenom 27 catheter was advanced into distal m1.During deployment the pipeline device fell back proximal to desired landing zone.The doctor attempted to resheath the device, and it got stuck in microcatheter and she was unable to resheathed.Multiple attempts were made.The guide catheter was advanced and the phenom catheter was manipulated.The doctor was still unable to resheath the pipeline.The pipeline was not deployed and removed from the patient.Another pipeline was used, and during deployment the same issue occurred with the second device.The pipeline was partially open but not deployed and the system fell back proximal to aneurysm neck.The doctor attempted to resheath the device and it was stuck in the phenom catheter.Multiple attempts were made to resheath the device again, and all attempts were unsuccessful.This device was also removed from the patient.Finally, a third pipeline was deployed without incident.There was no injury to the patient and a good angiographic result was achieved post procedure.There was no damage to the pipeline pushwire. the devices were prepared according to the instructions for use (ifu).Ancillary devices include a benchmark 105 guide catheter.
|
|
Manufacturer Narrative
|
Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.A good faith effort will be made to obtain the applicable information relevant to the report.If information is provided in the future, a supplemental report will be issued.
|
|
Event Description
|
Additional information was received on 2021-aug-11.It was reported that there was not any difficulty or friction during the initial attempt to deliver the device. the distal end of the device opened appropriately. it was only after the device fell back past the intended landing zone and the attempted resheathing that the device got stuck in the phenom 027. the device did jump during deployment. it was believed this was due to patient anatomy and guide catheter position. because the device jumped back below the intended landing zone the resheathing attempt was made. the catheter tip moved during the attempted deployment. however, the catheter tip must move in order to deploy the device.
|
|
Manufacturer Narrative
|
H3: no damages were found with the pipeline flex w/ shield proximal pusher.The hypotube was intact and unstretched and ptfe shrink tubing was found undamaged.No damages were found with the distal marker, re-sheathing marker or with the proximal bumper.The resheathing pad was found undamaged.The distal and proximal dps restraints and dps sleeves were found undamaged.The tip coil was found stretched.The braid was already deployed and not returned for analysis.Based on the analysis findings, the customer report of ¿movement during deployment¿ could not be confirmed based on device analysis.Possible causes are vasospasm, patient vessel tortuosity, high force delivery, catheter kickback, insufficient distal anchoring of braid or incorrect braid sizing.The customer report of ¿resistance during re-sheathing/failure to resheath¿ was confirmed as the pipeline flex w/ shield device had resistance within the phenom-27.Possible causes for failure to resheath are patient vessel tortuosity, resistance during delivery/retrieval, ped/delivery system damage, catheter damage, user does not maintain continuous flush, user resheaths more than two times, introducer sheath damaged or introducer sheath not fully seated into the hub.The dried blood could have also contributed towards the resistance.The micro c atheter was found accordioned, braid was found damaged, the resheathing marker/distal marker/resheathing pad were found loose on the distal wire and the tip coil were found stretched indicative of retracting the device against resistance.There is no indication that the event is related to a potential manufacturing issue.Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.A good faith effort will be made to obtain the applicable information relevant to the report.If information is provided in the future, a supplemental report will be issued.
|
|
Search Alerts/Recalls
|
|
|