Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Bibf 1120 adverse event reports that FDA received

Name type
Product name as reported

What a report is

A report is not proof that the drug 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, Drug 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:

There is no certainty that the reported event (adverse event or medication error) was actually due to the product. FDA does not require that a causal relationship between a product and event be proven, and reports do not always contain enough detail to properly evaluate an event. The information in these reports has not been scientifically or otherwise verified as to a cause and effect relationship and cannot be used to estimate the incidence of these events.

Source: openFDA, Drug Adverse Event Overview. 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.

Drug reports received through . Device reports have a separate cutoff, 30 Sep 2026. Why a report count is not a rate.

Reports on file

From January 2007 to March 2021, FDA received 857 adverse event reports that name Bibf 1120. The name is as reporters wrote it. In these reports the drug is a suspect or interacting product.

In the same period, 2 further reports name it only as a concomitant medicine. The counts on this page do not include these reports.

FDA received no report that names Bibf 1120 in the five years to June 2026. The latest report was received in March 2021.

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.

There are many instances of duplicative reports and some reports do not contain all the necessary information.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

Suspect product

FDA records each drug in a report as suspect, concomitant or interacting. This page counts the reports in which Bibf 1120 is suspect or interacting. FDA says:

Any number of the drugs may be marked as suspect if thought to be responsible for one or more of the reactions, but that information is not validated.

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

Data version

openFDA FAERS release of 29 Oct 2026. Reports received through 30 Jun 2026.

Since the last update

FDA says:

Many factors can influence whether or not an event will be reported, such as the time a product has been marketed and publicity about an event.

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

The information in these reports cannot be used to estimate the incidence (occurrence rates) of the events reported.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

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

FDA received no report that names Bibf 1120 in April to June 2026, in January to March 2026 or in April to June 2025.

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)

Reaction lookup

These are the reaction terms that the reports record, with the number of reports for each term. Type a term or a plain word to find its count.

What this list leaves out

The table lists the 75 reaction terms that 5 or more reports record. A term with fewer than 5 reports is not in the table.

The site keeps reaction terms for 842 of the 857 reports (98.2%).

The reports of the other years are not in the counts.

So a count in the table can be lower than the count of FDA.

The table shows the first 50 of 75 terms.

Reaction terms in the reports that name Bibf 1120, most reports first
Reaction term (MedDRA) and plain meaningReportsShare of the 857 reports
Diarrhoealoose or frequent stools18621.7%
Idiopathic pulmonary fibrosis14817.3%
Decreased appetitereduced appetite758.8%
Pneumonialung infection607%
Hepatic function abnormal596.9%
Liver disorder536.2%
Pneumothoraxa collapsed lung465.4%
Pulmonary embolisma blood clot in the lung455.3%
Dyspnoeashortness of breath445.1%
Vomitingbeing sick445.1%
Nauseafeeling sick394.6%
Malignant neoplasm progression354.1%
Neutropenialow neutrophils, a type of white blood cell354.1%
Alanine aminotransferase increasedraised liver enzyme (ALT)344%
Respiratory failurethe lungs could not supply enough oxygen333.9%
Drug-induced liver injury293.4%
Aspartate aminotransferase increasedraised liver enzyme (AST)283.3%
Dehydration283.3%
Constipation273.2%
Pyrexiafever273.2%
Cough232.7%
Drug effect incomplete212.5%
Anaemialow red blood cells202.3%
Gamma-glutamyltransferase increased202.3%
Pneumonia bacterial202.3%
Deaththe patient died; cause not stated by this term192.2%
Interstitial lung diseasescarring or inflammation of lung tissue192.2%
Abdominal painstomach or belly pain172%
Cardiac failureheart failure172%
Platelet count decreasedlow platelet count172%
Acute kidney injurysudden loss of kidney function161.9%
Fatiguetiredness161.9%
Hypertensionhigh blood pressure151.8%
Sepsisa severe body-wide response to infection151.8%
Thrombocytopenialow platelets151.8%
Febrile neutropeniafever with low white blood cells131.5%
Malaisegeneral feeling of being unwell121.4%
Astheniaweakness or lack of energy111.3%
Blood alkaline phosphatase increased111.3%
Chest pain111.3%
Deep vein thrombosisa blood clot in a deep vein111.3%
Rashskin rash111.3%
Urinary tract infectionbladder or urinary infection111.3%
General physical health deteriorationgeneral decline in health101.2%
Haemoptysiscoughing up blood101.2%
Hyponatraemialow blood sodium101.2%
Pulmonary hypertensionhigh pressure in the lung arteries101.2%
Therapeutic product effect incomplete101.2%
Blood bilirubin increased91.1%
Dizzinesslight-headedness or unsteadiness91.1%

Download all 75 terms of Bibf 1120 (CSV)

The counts add to more than 857 reports, because one report can record more than one term. FDA says:

No individual drug is connected to any individual reaction. When a report lists multiple drugs and multiple reactions, there is no way to conclude from the data therein that a given drug is responsible for a given reaction.

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

The CSV file has the same rows and the same limits. Its last row is a note that says so.

MedDRA term

The person who codes a report selects the preferred term that agrees best with the description of the reporter. The words under a term are the plain meaning that this site gives.

Not the label

The FDA-approved label of a product lists its adverse reactions. See the official pages at the end of this page.

Outcomes by year

The table gives the outcomes that the reporters gave, in the terms of FDA.

Outcomes in the reports that name Bibf 1120, by the year of the openFDA file that holds the report

The table continues to the right.

Year of the openFDA fileReportsSeriousDeathLife-threateningHospitalization (initial or prolonged)Disability or Permanent DamageCongenital Anomaly/Birth DefectOther Serious (Important Medical Events)Not serious
2007331030010
2011330110010
2013220020000
2014171741110050
2015999723106940242
20161351354779560360
20171891806217143100449
20182192026915145708017
2019138134502010470384
202045451643710140
2021774060070

An outcome in a report is not proof that the drug was the cause. The reporter gives the outcome, and FDA does not verify it. FDA says:

The information in these reports has not been scientifically or otherwise verified as to a cause and effect relationship and cannot be used to estimate the incidence of these events.

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

The six headings with the names of FDA are the outcome terms of FDA. A report can have more than one outcome. The columns Serious and Not serious are the two values of the openFDA field serious. For the value serious, openFDA gives this description:

The adverse event resulted in death, a life threatening condition, hospitalization, disability, congenital anomaly, or other serious condition

Source: openFDA, Drug adverse event fields (YAML reference). The site read the page on .

The year is the year of the openFDA file that holds the latest version of the report. It is not always the year in which FDA first received the report. The chart of the next section uses the year of first receipt. The latest year is not complete.

Reports by year and month

Reports that name Bibf 1120, by the year in which FDA received them
0250500200720132015201720192021
Show the figures of the chart as a table
Reports that name Bibf 1120, by the year in which FDA received them
YearReports
20073
20113
20132
201430
2015108
2016222
2017233
2018161
201984
20209
20212

FDA received no report that names Bibf 1120 in the five years to June 2026. FDA received the latest report in March 2021.

Why a count moves

A count moves for many reasons. The guide gives FDA's words about them.

Patients and reporters

Age of the patient in the reports that name Bibf 1120
AgeReportsShareShare as a bar
Under 200%
2 to 1100%
12 to 1700%
18 to 44242.8%
45 to 6420323.7%
65 to 7436542.6%
75 and over24128.1%
Age not given242.8%
Sex of the patient in the reports that name Bibf 1120
SexReportsShareShare as a bar
Female27432%
Male58067.7%
Unknown or not given30.4%
Type of reporter in the reports that name Bibf 1120
ReporterReportsShareShare as a bar
Physician81695.2%
Pharmacist70.8%
Other health professional202.3%
Lawyer00%
Consumer or non-health professional101.2%
Not given40.5%

Age and sex are as the report gives them. The reporter is the primary source in the report. 5.7% of the reports give the United States as the country.

Reason for use

Reason for use (indication) that the reports of Bibf 1120 record
Indication as recorded (MedDRA)ReportsShare
Idiopathic pulmonary fibrosis41448.3%
Non-small cell lung cancer799.2%
Pleural mesothelioma malignant586.8%
Ovarian cancer222.6%
Colorectal cancer161.9%
Bladder cancer141.6%

The reporter fills in the indication, and the field is often empty. Each share is of all 857 reports.

Pages near this one

These links are for navigation. No count selected them.

Official pages

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

Cite this page

Reported Reactions. Bibf 1120: adverse event reports that FDA received. https://reportedreactions.com/drug/bibf-1120/ Source: U.S. Food and Drug Administration, openFDA Drug Adverse Event (FAERS) files, release of . Reports received through .

Where the data come from

The counts come from the openFDA Drug Adverse Event (FAERS) bulk files, release of 29 Oct 2026. The files have the reports that FDA received through 30 Jun 2026. A drug name is the name on the report. The site matches it to a brand name or a generic name of the National Drug Code Directory of 2 Nov 2026. A class is the pharmacologic class (EPC) of the FDA label.

A report is in the count when it names Bibf 1120 as a suspect or interacting product. The 2 reports that name it only as a concomitant medicine are not in the count. 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 Bibf 1120 was responsible for the reactions?

No. FDA says:

For any given report, there is no certainty that a suspected drug caused the event.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

A reaction can relate to the condition that the drug treats, to other medicines, or to something else.

Is this the list of reactions on the label of Bibf 1120?

No. It is a count of what people reported to FDA: 857 reports from January 2007 to March 2021. The FDA-approved label of a product lists its adverse reactions. The official pages at the end of this page link to the labels.

Who sent these reports?

Physician (95.2%), other health professional (2.3%) and consumer or non-health professional (1.2%). These are the types of reporter for the reports that name this drug.

If a manufacturer receives an adverse event report, it is normally required to send the report to FDA.

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

How does a person report an adverse event?

FDA runs MedWatch, a program that takes voluntary reports from health professionals, patients and consumers. The guide on how to report has the links.