Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Promus PREMIER medical device reports that FDA received

Name type
Device brand name, as written on reports
Generic name
Stent coronary drug-eluting
Device type
Coronary drug-eluting stent (product code NIQ)
Manufacturer given most often on reports
Boston Scientific - Galway

What a report is

A report is not proof that the device was the cause of the event.

FDA says:

Adverse event reports submitted to FDA do not undergo extensive validation or verification. Therefore, a causal relationship cannot be established between product and reactions listed in a report. While a suspected relationship may exist, it is not medically validated and should not be the sole source of information for clinical decision making or other assumptions about the safety or efficacy of a product. Additionally, it is important to remember that adverse event reports represent a small percentage of total usage numbers of a product. Common products may have a higher number of adverse events due to the higher total number of people using the product.

Source: openFDA, Device Adverse Event Overview, section "Responsible use of the data". The site read the page on . The data have the reports that FDA received through .

FDA also says:

Although MDRs are a valuable source of information, this passive surveillance system has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data. In addition, the incidence or prevalence of an event cannot be determined from this reporting system alone due to potential under-reporting of events and lack of information about frequency of device use.

Source: openFDA, Device Adverse Event Overview. The site read the page on .

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.

Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .

Do not rely on openFDA to make decisions regarding medical care. While we make every effort to ensure that data is accurate, you should assume all results are unvalidated.

Source: openFDA, Response of the drug event API (meta.disclaimer). The site read the page on .

Not medical advice. This site counts what was reported to FDA. Questions about a medicine or device belong with a pharmacist or clinician.

Reports on file

From April 2013 to September 2026, FDA received 6,164 medical device reports that name the brand Promus PREMIER. A brand name is as the reporter or the manufacturer wrote it, so one product can have more than one spelling.

FDA received 106 reports in the 12 months to September 2026 and 167 in the 12 months before. FDA releases MAUDE data every month. Reports can arrive months after an event, so the newest months grow in later releases.

Of the 3,444,740 device reports that FDA received in the 12 months to September 2026, 106 (under 0.1%) name the brand Promus PREMIER. Manufacturer reports were 99.7% of the reports that name this brand and 94.9% of all device reports.

The number of people who use the product is not in the data. A count is not a rate. A count of reports is not a count of events or of patients, because one event can have more than one report.

What an MDR is

A medical device report: one submission to FDA about one event. It has the brand name, the generic name, the manufacturer, the product code, the event type and coded problems. Manufacturers and user facilities must send reports.

Data version

openFDA MAUDE release of 23 Oct 2026. Reports received through 30 Sep 2026.

Since the last update

FDA says:

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.

Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .

The latest update of the FDA data, recorded on , changed no count of this page.

  • In April to June 2026, FDA received 20 reports that name the brand Promus PREMIER.
  • In January to March 2026, FDA received 22.
  • In April to June 2025, FDA received 29.

April to June 2026 is the latest closed quarter in the data. A closed quarter is a quarter for which the FDA files have most of the reports.

All updatesFeed of updates (RSS)

Event types by year

The event type is the classification that the reporter gave. The four terms are FDA's.

FDA says:

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.

Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .

Reports that name Promus PREMIER, by event type and by the year in which FDA received them

The table continues to the right.

YearReportsDeathInjuryMalfunctionOtherNot given
2013511282200
20148551827356400
20151,4076340394100
20169376231056500
20175242413236800
20184712911832400
20194663111132400
2020384194831700
2021379245330200
202213925308400
202312227336200
2024227451136900
202513814586600
2026647223500

An event type in a report is not proof that the device was the cause. FDA does not verify the event type.

Malfunction

A malfunction report says that the device did not do what it was made to do. It can be with or without harm to a person.

Reports by month

Reports that name Promus PREMIER, by month, five years to September 2026
0255020222023202420252026

FDA releases MAUDE data every month. Reports can arrive months after an event, so the newest months grow in later releases.

Event type and report source

Event type in all reports that name Promus PREMIER
Event typeReportsShareShare as a bar
Death3896.3%
Injury1,73228.1%
Malfunction4,04365.6%
Other00%
Not given00%
Source of the reports that name Promus PREMIER
Report sourceReportsShareShare as a bar
Manufacturer report6,14699.7%
Voluntary report40.1%
User facility report00%
Distributor report00%
Not given140.2%

Each share is of the 6,164 reports that name this brand, not of the devices in use.

Device problems coded

Device problem codes in the reports that name Promus PREMIER
Device problem (FDA code)ReportsShare
Bent1,59625.9%
Failure to advance1,44023.4%
Material deformation77112.5%
Device dislodged or dislocated67310.9%
Breakthe device broke5388.7%
Occlusion within devicethe device blocked3065%
Device damaged prior to usethe device was damaged before use2173.5%
Device damaged by another device2093.4%
Difficult to removethe device was hard to remove2033.3%
Difficult to advance1722.8%
Fracturea broken bone1362.2%
Activation, positioning or separation problem1302.1%
Entrapment of device1181.9%
Material rupture651.1%
Kinkedthe tube or line kinked580.9%
Obstruction of flow460.7%
Migration or expulsion of device380.6%
Inflation problem300.5%
Nonstandard device290.5%
Positioning failure250.4%

These are the device problem codes of FDA, as written on the report. One report can have more than one code. The table leaves out general codes such as "no apparent adverse event".

Patient problems coded

Patient problem codes in the reports that name Promus PREMIER
Patient problem (FDA code)ReportsShare
No patient involvement3645.9%
Deaththe patient died; cause not stated by this term2484%
Thrombosis2303.7%
Chest painchest pain2183.5%
Myocardial infarctionheart attack2173.5%
Vascular dissection1913.1%
Angina1612.6%
Reocclusion1532.5%
Intimal dissection1212%
Dyspneashortness of breath881.4%
Obstruction/occlusion811.3%
Reduced blood flow791.3%
Cardiac arrestthe heart stopped761.2%
Restenosis671.1%
Cardiac enzyme elevation631%

Patient problem codes are mainly in reports sent since 2019, and the field is often empty.

Pages near this one

These links are for navigation. No count selected them. The page of the device type lists each brand name with product code NIQ.

Official pages

The site checked these addresses on . The links open in a new tab.

Cite this page

Embed this card on your site

Copy this code into your page. The card shows the figures above with their source. A line under the card links to this page.

How embedding works. It is free. Keep the link in the card and the link line under it.

Reported Reactions. Promus PREMIER: medical device reports that FDA received. https://reportedreactions.com/device/promus-premier/ Source: U.S. Food and Drug Administration, openFDA Device Adverse Event (MAUDE) files, release of . Reports received through .

Where the data come from

The counts come from the openFDA Device Adverse Event (MAUDE) bulk files, release of 23 Oct 2026. The files have the reports that FDA received through 30 Sep 2026. Brand names, generic names and manufacturer names are as written on the reports. The names of the product codes come from the device classification of FDA.

A report is in the count when a device in it has this brand name, after the site removes differences of punctuation and capital letters. The site does not publish a report narrative, a lot number, a detail of a patient or the identity of a reporter. The record of FDA is the authority. See how the site counts reports, the data sources and the corrections page.

Questions

Do these reports show that Promus PREMIER was at fault?

No. FDA says:

The submission of an MDR itself does not necessarily demonstrate that the device caused or contributed to the adverse outcome or event.

Source: FDA Center for Devices and Radiological Health, About Manufacturer and User Facility Device Experience (MAUDE) Database. Content current as of . The site read the page on .

Confirming whether a device actually caused a specific event can be difficult based solely on information provided in a given report.

Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .

What event types do the reports record?

Death (389), injury (1,732) and malfunction (4,043). The event type is the classification that the reporter gave: death, injury, malfunction or other. FDA does not verify it.

Who sent these reports?

Manufacturer reports (99.7%) and voluntary reports (0.1%). These are the sources of the reports that name this brand.

Some reports come directly from user facilities (like hospitals) or device importers (distributors), while others come directly from manufacturers.

Source: openFDA, Device Adverse Event Overview. The site read the page on .

How does a person report a problem with a medical device?

FDA runs MedWatch, a program that takes voluntary reports about medical devices. The guide on how to report has the links.