Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Apollo medical device reports that FDA received

Name type
Device brand name, as written on reports
Generic name
Agent injectable embolic
Device type
Agent, injectable, embolic (product code MFE)
Manufacturer given most often on reports
Micro Therapeutics Ev3

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 January 2005 to September 2026, FDA received 1,215 medical device reports that name the brand Apollo. A brand name is as the reporter or the manufacturer wrote it, so one product can have more than one spelling.

FDA received 132 reports in the 12 months to September 2026 and 135 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, 132 (under 0.1%) name the brand Apollo. Distributor reports were 0.5% of the reports that name this brand and 3.6% 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 40 reports that name the brand Apollo.
  • In January to March 2026, FDA received 24.
  • In April to June 2025, FDA received 30.

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 Apollo, by event type and by the year in which FDA received them

The table continues to the right.

YearReportsDeathInjuryMalfunctionOtherNot given
2005400400
20071330271
2008411002
2010600411
2011700610
20121100803
2013803302
2014603300
201551064500
201682197200
2017972157901
201866185700
201978077100
2020690135600
20211074129100
20221080129600
202314333210800
202412341410500
20251300812200
2026102498900

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 Apollo, 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 Apollo
Event typeReportsShareShare as a bar
Death231.9%
Injury15212.5%
Malfunction1,02184%
Other90.7%
Not given100.8%
Source of the reports that name Apollo
Report sourceReportsShareShare as a bar
Manufacturer report1,16996.2%
Voluntary report60.5%
User facility report00%
Distributor report60.5%
Not given342.8%

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

Device problems coded

Device problem codes in the reports that name Apollo
Device problem (FDA code)ReportsShare
Failure to deliverthe device did not deliver the dose or item27422.6%
Gas output problem20717%
Detachment of device or device componentpart of the device came off19215.8%
Burst container or vessel1129.2%
Leak/splashthe device leaked887.2%
Breakthe device broke806.6%
Physical resistance/sticking806.6%
Intermittent continuity796.5%
Device displays incorrect message776.3%
Device inoperablethe device could not be used604.9%
Difficult to removethe device was hard to remove443.6%
Intermittent communication failure413.4%
Compatibility problem383.1%
Device operates differently than expectedthe device behaved unexpectedly352.9%
Detachment of device component342.8%
No pressure332.7%
Material deformation302.5%
Pressure problem262.1%
Packaging problem252.1%
Protective measures problem231.9%

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 Apollo
Patient problem (FDA code)ReportsShare
Foreign body in patientpart of a device left in the patient12310.1%
Device embedded in tissue or plaque292.4%
Intracranial hemorrhage221.8%
Hemorrhage/blood loss/bleeding151.2%
Vasoconstriction141.2%
Obstruction/occlusion121%
Hematomaa collection of blood under the skin or in tissue90.7%
Deaththe patient died; cause not stated by this term80.7%
Rupturethe device burst80.7%
Headachehead pain70.6%
Ischemia stroke70.6%
Perforation of vessels70.6%
Ischemia60.5%
Muscle weakness/atrophy60.5%
Stroke/cva60.5%

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 MFE.

Official pages

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

Cite this page

Reported Reactions. Apollo: medical device reports that FDA received. https://reportedreactions.com/device/apollo/ 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 Apollo 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 (23), injury (152), malfunction (1,021) and other (9). 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 (96.2%), voluntary reports (0.5%) and distributor reports (0.5%). 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.