Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Deflect medical device reports that FDA received

Name type
Device brand name, as written on reports
Generic name
Catheter percutaneous
Device type
Catheter, percutaneous (product code DQY)
Manufacturer given most often on reports
Medtronic Ireland

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

FDA received 240 reports in the 12 months to September 2026 and 257 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, 240 (under 0.1%) name the brand Deflect. Manufacturer reports were 100% 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 71 reports that name the brand Deflect.
  • In January to March 2026, FDA received 61.
  • In April to June 2025, FDA received 58.

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

The table continues to the right.

YearReportsDeathInjuryMalfunctionOtherNot given
201519001900
2016500500
2017700700
201841063500
201934033100
202056055100
2021650115400
2022690105900
202312811311400
202416702214500
202525702423300
20261830817500

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 Deflect, 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 Deflect
Event typeReportsShareShare as a bar
Death10.1%
Injury1029.9%
Malfunction92890%
Other00%
Not given00%
Source of the reports that name Deflect
Report sourceReportsShareShare as a bar
Manufacturer report1,031100%
Voluntary report00%
User facility report00%
Distributor report00%
Not given00%

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

Device problems coded

Device problem codes in the reports that name Deflect
Device problem (FDA code)ReportsShare
Material integrity problema problem with the device material23723%
Accessory incompatible21821.1%
Breakthe device broke21320.7%
Leak/splashthe device leaked959.2%
Detachment of device or device componentpart of the device came off949.1%
Deformation due to compressive stress858.2%
Mechanical problema mechanical problem797.7%
Packaging problem313%
Tear, rip or hole in device packaging161.6%
Material deformation151.5%
Defective devicethe device was defective90.9%
Device contamination with body fluid70.7%
Activation, positioning or separation problem60.6%
Device dislodged or dislocated60.6%
Positioning problem50.5%
Device damaged by another device20.2%
Failure to advance20.2%
Inadequacy of device shape and/or size20.2%
Kinkedthe tube or line kinked20.2%
Material fragmentation20.2%

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 Deflect
Patient problem (FDA code)ReportsShare
Cardiac perforation323.1%
Pericardial effusionfluid around the heart181.7%
Cardiac tamponade141.4%
Heart block131.3%
Low blood pressure/ hypotension101%
Discomfortdiscomfort80.8%
Appropriate clinical signs, symptoms and conditions term/code not available60.6%
Bradycardiaslow heart rate60.6%
Perforation60.6%
Chest painchest pain50.5%
Dyspneashortness of breath50.5%
Hemorrhage/blood loss/bleeding50.5%
Asystole40.4%
Non specific ekg/ECG changes40.4%
Arrhythmia30.3%

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

Official pages

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

Cite this page

Reported Reactions. Deflect: medical device reports that FDA received. https://reportedreactions.com/device/deflect/ 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 Deflect 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 (1), injury (102) and malfunction (928). 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 (100%). 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.