Devices › Temporary coronary saphenous vein bypass graft for embolic protection
Device brand name · Temporary coronary saphenous vein bypass graft for embolic protection
FilterWire EZ: medical device reports filed with FDA
507 reports name it, 2012–2026. Manufacturer given most often on reports: Boston Scientific. Product code NFA.
- 507
- device reports naming the brand
- 0% of all MAUDE reports · about 35 a year
- 71
- reports, 12 months to August 2026
- 80 in the 12 months before
- 82.1%
- classified as malfunction
- 58.5% across the product code
- 0.4%
- classified as death, as reported
- 2 reports · not verified by FDA
507 medical device reports received by FDA name the brand "FilterWire EZ" (temporary coronary saphenous vein bypass graft for embolic protection); the manufacturer given most often on reports is Boston Scientific; received from February 2012 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
71 reports arrived in the 12 months to August 2026, down 11% from 80 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are malfunction (82.1%), injury (17.6%) and death (0.4%); across all temporary coronary saphenous vein bypass graft for embolic protection reports (product code NFA) death is recorded in 1.9% and malfunction in 58.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are difficult to remove (39.6%), material integrity problem (28.4%) and difficult or delayed positioning (5.9%). The patient problems coded most often are no patient involvement, device embedded in tissue or plaque and vasoconstriction. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 2,035 reports carrying product code NFA. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| Difficult to removethe device was hard to remove | 201 | 39.6% | 18.8% |
| Material integrity problema problem with the device material | 144 | 28.4% | 5.5% |
| Difficult or delayed positioning | 30 | 5.9% | 1.9% |
| Breakthe device broke | 21 | 4.1% | 4.4% |
| Fracturea broken bone | 20 | 3.9% | 1.3% |
| Difficult to advance | 17 | 3.4% | 0.7% |
| Detachment of device or device componentpart of the device came off | 16 | 3.2% | 3.8% |
| Failure to advance | 16 | 3.2% | 4% |
| Nonstandard device | 15 | 3% | 0.7% |
| Entrapment of device | 12 | 2.4% | 1.3% |
| Device contamination with chemical or other material | 11 | 2.2% | 0.2% |
| Torn material | 11 | 2.2% | 0.2% |
| Failure to capture | 9 | 1.8% | 0.5% |
| Detachment of device component | 8 | 1.6% | 2.5% |
| Device damaged prior to usethe device was damaged before use | 8 | 1.6% | 1% |
| Device difficult to setup or prepare | 8 | 1.6% | 0.3% |
| Device-device incompatibility | 8 | 1.6% | 0.2% |
| Difficult or delayed activation | 8 | 1.6% | 0.3% |
| Mechanical jam | 8 | 1.6% | 0.4% |
| Positioning failure | 8 | 1.6% | 0.6% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| No patient involvement | 23 | 4.5% |
| Device embedded in tissue or plaque | 14 | 2.8% |
| Vasoconstriction | 9 | 1.8% |
| Foreign body in patientpart of a device left in the patient | 8 | 1.6% |
| Stroke/cva | 6 | 1.2% |
| Obstruction/occlusion | 5 | 1% |
| Paralysis | 5 | 1% |
| Embolism/embolus | 3 | 0.6% |
| St segment elevation | 3 | 0.6% |
| Coma | 2 | 0.4% |
| Embolism | 2 | 0.4% |
| Infarction, cerebral | 2 | 0.4% |
| Intimal dissection | 2 | 0.4% |
| Low blood pressure/ hypotension | 2 | 0.4% |
| Chest painchest pain | 1 | 0.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | FilterWire EZ | Product code NFA | All MAUDE reports |
|---|---|---|---|
| Reports | 507 | 2,035 | 26,136,888 |
| Share of that pool | — | 24.9% | 0% |
| Classified as death, per 1,000 reports | 4 | 19 | 9 |
| Classified as injury | 17.6% | 38.3% | 36.2% |
| Classified as malfunction | 82.1% | 58.5% | 62.3% |
| Filed by the manufacturer | 98% | 96.6% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code NFA
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Rx Accunet Embolic Protection System | 429 | 0 | 2.1% |
| Filterwire Ez Emoblic Protection System | 164 | 0 | 1.8% |
| Spider Fx | 649 | 65 | 2% |
| Spiderfx Embolic Protection Device | 232 | 0 | 6% |
| Angioguard Xp Emboli Capture Guidewire System | 275 | 0 | 0% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about FilterWire EZ reports
How many FDA reports name FilterWire EZ?
507 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 71 in the latest 12 months.
What kinds of events are reported?
malfunction (82.1%), injury (17.6%) and death (0.4%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
difficult to remove (39.6%), material integrity problem (28.4%), difficult or delayed positioning (5.9%), break (4.1%) and fracture (3.9%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (98%) and voluntary reports (0.2%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that FilterWire EZ was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.