Devices › Catheter, coronary, atherectomy
Device brand name · Catheter coronary atherectomy
Rotablator Rotational Atherectomy System: medical device reports filed with FDA
1,917 reports name it, 2009–2026. Manufacturer given most often on reports: Boston Scientific - Costa Rica Coyol. Product code MCX.
- 1,917
- device reports naming the brand
- 0% of all MAUDE reports · about 111 a year
- 88
- reports, 12 months to August 2026
- 32 in the 12 months before
- 63.8%
- classified as malfunction
- 55.3% across the product code
- 7%
- classified as death, as reported
- 135 reports · not verified by FDA
FDA's MAUDE database holds 1,917 reports that name the brand "Rotablator Rotational Atherectomy System" (catheter coronary atherectomy), received between March 2009 and August 2026; the manufacturer given most often on reports is Boston Scientific - Costa Rica Coyol. Spellings of one product vary from report to report.
88 reports arrived in the 12 months to August 2026, up 175% from 32 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 (63.8%), injury (29.2%) and death (7%); across all catheter, coronary, atherectomy reports (product code MCX) death is recorded in 7.4% and malfunction in 55.3%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are fracture (17.3%), entrapment of device (16.7%) and no display/image (11.5%). The patient problems coded most often are no patient involvement, device embedded in tissue or plaque and perforation of vessels. 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 11,889 reports carrying product code MCX. 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 |
|---|---|---|---|
| Fracturea broken bone | 331 | 17.3% | 7% |
| Entrapment of device | 320 | 16.7% | 22.4% |
| No display/image | 220 | 11.5% | 2.2% |
| Device damaged by another device | 114 | 5.9% | 5.9% |
| Device operates differently than expectedthe device behaved unexpectedly | 112 | 5.8% | 2.4% |
| Detachment of device or device componentpart of the device came off | 79 | 4.1% | 6.1% |
| Difficult to removethe device was hard to remove | 76 | 4% | 5.6% |
| Breakthe device broke | 55 | 2.9% | 2.3% |
| Output problem | 45 | 2.3% | 4.8% |
| Detachment of device component | 43 | 2.2% | 2.3% |
| Device contamination with chemical or other material | 33 | 1.7% | 1.3% |
| Failure to advance | 32 | 1.7% | 2.6% |
| Kinkedthe tube or line kinked | 30 | 1.6% | 0.8% |
| Gas/air leak | 23 | 1.2% | 0.5% |
| Insufficient device problem information | 21 | 1.1% | 0.5% |
| Intermittent loss of power | 19 | 1% | 2% |
| Material separation | 19 | 1% | 7.9% |
| Difficult to advance | 15 | 0.8% | 1.3% |
| Material integrity problema problem with the device material | 15 | 0.8% | 1.6% |
| Device damaged prior to usethe device was damaged before use | 14 | 0.7% | 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 | 261 | 13.6% |
| Device embedded in tissue or plaque | 145 | 7.6% |
| Perforation of vessels | 131 | 6.8% |
| Deaththe patient died; cause not stated by this term | 113 | 5.9% |
| Vascular dissection | 41 | 2.1% |
| Low blood pressure/ hypotension | 39 | 2% |
| Intimal dissection | 36 | 1.9% |
| Cardiac tamponade | 30 | 1.6% |
| Myocardial infarctionheart attack | 30 | 1.6% |
| Obstruction/occlusion | 26 | 1.4% |
| Perforation | 26 | 1.4% |
| Chest painchest pain | 23 | 1.2% |
| Cardiac arrestthe heart stopped | 22 | 1.1% |
| St segment elevation | 20 | 1% |
| Reduced blood flow | 18 | 0.9% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Rotablator Rotational Atherectomy System | Product code MCX | All MAUDE reports |
|---|---|---|---|
| Reports | 1,917 | 11,889 | 26,136,888 |
| Share of that pool | — | 16.1% | 0% |
| Classified as death, per 1,000 reports | 70 | 74 | 9 |
| Classified as injury | 29.2% | 36.9% | 36.2% |
| Classified as malfunction | 63.8% | 55.3% | 62.3% |
| Filed by the manufacturer | 99.7% | 96.4% | 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 MCX
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| RotaLink? Plus | 1,957 | 42 | 4.4% |
| Rotapro | 1,565 | 313 | 4.7% |
| Diamondback 360 Coronary Orbital Atherectomy System | 1,512 | 0 | 15.7% |
| RotaWire and wireClip Torquer | 1,462 | 84 | 3.8% |
| RotaLink Burr | 627 | 39 | 8.1% |
| Diamondback Coronary | 492 | 222 | 15.9% |
| ROTAWIRE Drive | 369 | 85 | 3.5% |
| AngioJet Ultra System Console | 162 | 11 | 1.2% |
| Rotalink Catheter | 154 | 0 | 13% |
| Rotablator Guide Wire | 352 | 0 | 3.7% |
| Diamondback 360 Peripheral Orbital Atherectomy System | 676 | 0 | 0.9% |
| AngioJet SOLENT omni | 671 | 26 | 1.3% |
| Diamondback 360 Orbital Atherectomy System | 241 | 0 | 3.3% |
| Selox JT 53 | 150 | 5 | 0% |
| Synergy | 14,271 | 84 | 3.5% |
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 Rotablator Rotational Atherectomy System reports
How many FDA reports name Rotablator Rotational Atherectomy System?
1,917 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 88 in the latest 12 months.
What kinds of events are reported?
malfunction (63.8%), injury (29.2%) and death (7%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
fracture (17.3%), entrapment of device (16.7%), no display/image (11.5%), device damaged by another device (5.9%) and device operates differently than expected (5.8%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.7%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Rotablator Rotational Atherectomy System 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.