| Model Number |
CND1040 |
| Medical Device Problem Code |
Insufficient Device Problem Information (3190)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
11/17/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
It was reported the following: physician was able to complete the procedure.Patient is doing well; however, the nose of the stent post deployment wa getting stuck prior ro post dilation.He used a 3.5 balloon free in a moderately calcified lesion, followed with a 5.5 balloon.During the deployment process the stent did jump but did not mis the (stenosis) lesion, however it did not deploy at the desired location and had to expand the stent.The physician used a ompetitor stent to cover the proximal common carotid.The physician did not expereince resistance.The nose cone is bulky per physician.
|
| |
|
Additional Manufacturer Narrative
|
|
Device analysis and investigation is in-process.
|
| |
|
Event or Problem Description
|
|
It was reported the following: physician was able to complete the procedure.Patient is doing well; however, the nose of the stent post deployment wa getting stuck prior ro post dilation.He used a 3.5 balloon free in a moderately calcified lesion, followed with a 5.5 balloon.During the deployment process the stent did jump but did not mis the (stenosis) lesion; however, it did not deploy at the desired location and had to expand the stent.The physician used a competitor stent to cover the proximal common carotid.The physician did not experience resistance.The nose cone is bulky per physician.
|
| |
|
Additional Manufacturer Narrative
|
|
Device analysis and investigation is in-process.Supplemental follow up report: a root cause investigation was conducted for this event.The device was not returned for analysis.An internal lot record review was performed.A root cause for the difficult deployed stent could not be found and either it was not confirmed that there was a problem with the device, or it was confirmed that there was no problem with the device fda code 67.
|
| |
|
Search Alerts/Recalls
|