Glifage 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.
Reports on file
From August 2012 to March 2026, FDA received 484 adverse event reports that name Glifage. The name is as reporters wrote it. In these reports the drug is a suspect or interacting product.
In the same period, 2,172 further reports name it only as a concomitant medicine. The counts on this page do not include these reports.
FDA received 6 reports in the 12 months to June 2026 and 12 in the 12 months before. FDA releases FAERS data every quarter, so the newest months are not complete. They grow in later releases.
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 Glifage 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 1 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 .
No update is on record for this page. The record starts when FDA adds the reports of July to September 2026.
- In April to June 2026, FDA received 0 reports that name Glifage.
- In January to March 2026, FDA received 1.
- In April to June 2025, FDA received 3.
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.
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 72 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 468 of the 484 reports (96.7%).
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 72 terms.
| Reaction term (MedDRA) and plain meaning | Reports | Share of the 484 reports |
|---|---|---|
| Blood glucose increasedraised blood sugar reading | 64 | 13.2% |
| Drug ineffectivethe medicine did not work as expected | 52 | 10.7% |
| Diarrhoealoose or frequent stools | 51 | 10.5% |
| Malaisegeneral feeling of being unwell | 42 | 8.7% |
| Nauseafeeling sick | 36 | 7.4% |
| Hyperglycaemiahigh blood sugar | 35 | 7.2% |
| Weight decreasedweight loss | 34 | 7% |
| Diabetes mellitus inadequate controldiabetes not well controlled | 31 | 6.4% |
| Off label useused for a purpose or in a way not on the label | 31 | 6.4% |
| Diabetes mellitusdiabetes | 30 | 6.2% |
| Hypertensionhigh blood pressure | 30 | 6.2% |
| Dizzinesslight-headedness or unsteadiness | 29 | 6% |
| Abdominal painstomach or belly pain | 22 | 4.5% |
| Intentional product misusedeliberate use not as intended | 21 | 4.3% |
| Myocardial infarctionheart attack | 21 | 4.3% |
| Blood pressure increaseda raised blood pressure reading | 19 | 3.9% |
| Vomitingbeing sick | 19 | 3.9% |
| Headachehead pain | 18 | 3.7% |
| Fatiguetiredness | 17 | 3.5% |
| Weight increasedweight gain | 16 | 3.3% |
| Astheniaweakness or lack of energy | 15 | 3.1% |
| Choking | 15 | 3.1% |
| Arterial occlusive disease | 14 | 2.9% |
| Abdominal discomfortstomach discomfort | 13 | 2.7% |
| Coronary artery occlusion | 13 | 2.7% |
| Pain in extremitypain in an arm or leg | 13 | 2.7% |
| Product use complaint | 13 | 2.7% |
| Gastritisinflamed stomach lining | 12 | 2.5% |
| Treatment noncompliancethe treatment was not taken as directed | 12 | 2.5% |
| Dysentery | 11 | 2.3% |
| Blood cholesterol increasedraised cholesterol | 10 | 2.1% |
| Cerebrovascular accidentstroke | 10 | 2.1% |
| Memory impairmentmemory problems | 10 | 2.1% |
| Syncopefainting | 10 | 2.1% |
| Visual impairmentreduced vision | 10 | 2.1% |
| Wrong technique in product usage processthe product was used in the wrong way | 10 | 2.1% |
| Abdominal pain upperupper stomach pain | 9 | 1.9% |
| Covid-19COVID-19 infection | 9 | 1.9% |
| Dyspnoeashortness of breath | 9 | 1.9% |
| Hypoglycaemialow blood sugar | 9 | 1.9% |
| Influenzaflu | 9 | 1.9% |
| Pruritusitching | 9 | 1.9% |
| Type 2 diabetes mellitustype 2 diabetes | 9 | 1.9% |
| Anaemialow red blood cells | 8 | 1.7% |
| Gait disturbancedifficulty walking | 8 | 1.7% |
| Intentional product use issuedeliberate use not as intended | 8 | 1.7% |
| Blood pressure inadequately controlled | 7 | 1.4% |
| Decreased appetitereduced appetite | 7 | 1.4% |
| Depressionlow mood | 7 | 1.4% |
| Hypersensitivityan allergic-type reaction | 7 | 1.4% |
The counts add to more than 484 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 Glifage, by the year of the openFDA file that holds the report
The table continues to the right.
| Year of the openFDA file | Reports | Serious | Death | Life-threatening | Hospitalization (initial or prolonged) | Disability or Permanent Damage | Congenital Anomaly/Birth Defect | Other Serious (Important Medical Events) | Not serious |
|---|---|---|---|---|---|---|---|---|---|
| 2007 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2008 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2009 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2010 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| 2012 | 3 | 3 | 0 | 0 | 2 | 0 | 0 | 1 | 0 |
| 2013 | 20 | 18 | 0 | 2 | 7 | 0 | 0 | 13 | 2 |
| 2014 | 86 | 86 | 0 | 1 | 49 | 4 | 0 | 62 | 0 |
| 2015 | 82 | 82 | 2 | 1 | 37 | 4 | 0 | 79 | 0 |
| 2016 | 19 | 19 | 1 | 1 | 8 | 0 | 0 | 17 | 0 |
| 2017 | 16 | 16 | 0 | 0 | 6 | 0 | 0 | 15 | 0 |
| 2018 | 11 | 11 | 1 | 0 | 4 | 2 | 0 | 9 | 0 |
| 2019 | 65 | 65 | 1 | 0 | 5 | 0 | 0 | 62 | 0 |
| 2020 | 51 | 51 | 0 | 1 | 11 | 0 | 0 | 46 | 0 |
| 2021 | 49 | 48 | 0 | 0 | 15 | 0 | 0 | 35 | 1 |
| 2022 | 28 | 28 | 2 | 0 | 9 | 0 | 0 | 22 | 0 |
| 2023 | 23 | 23 | 2 | 1 | 7 | 0 | 0 | 17 | 0 |
| 2024 | 17 | 17 | 1 | 1 | 6 | 1 | 0 | 11 | 0 |
| 2025 | 12 | 12 | 1 | 1 | 1 | 2 | 0 | 10 | 0 |
| 2026 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 2 | 0 |
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
The column of 2026 has an outline, because the year is not complete. It has the reports that FDA received through June 2026 only.
Show the figures of the chart as a table
| Year | Reports |
|---|---|
| 2012 | 7 |
| 2013 | 18 |
| 2014 | 96 |
| 2015 | 72 |
| 2016 | 20 |
| 2017 | 13 |
| 2018 | 12 |
| 2019 | 68 |
| 2020 | 54 |
| 2021 | 46 |
| 2022 | 27 |
| 2023 | 23 |
| 2024 | 16 |
| 2025 | 11 |
| 2026 | 1 |
FDA releases FAERS data every quarter, so the newest months are not complete. They grow in later releases.
Why a count moves
A count moves for many reasons. The guide gives FDA's words about them.
Patients and reporters
| Age | Reports | Share | Share as a bar |
|---|---|---|---|
| Under 2 | 4 | 0.8% | |
| 2 to 11 | 0 | 0% | |
| 12 to 17 | 0 | 0% | |
| 18 to 44 | 22 | 4.5% | |
| 45 to 64 | 131 | 27.1% | |
| 65 to 74 | 84 | 17.4% | |
| 75 and over | 51 | 10.5% | |
| Age not given | 192 | 39.7% |
| Sex | Reports | Share | Share as a bar |
|---|---|---|---|
| Female | 317 | 65.5% | |
| Male | 159 | 32.9% | |
| Unknown or not given | 8 | 1.7% |
| Reporter | Reports | Share | Share as a bar |
|---|---|---|---|
| Physician | 16 | 3.3% | |
| Pharmacist | 12 | 2.5% | |
| Other health professional | 14 | 2.9% | |
| Lawyer | 0 | 0% | |
| Consumer or non-health professional | 434 | 89.7% | |
| Not given | 8 | 1.7% |
Age and sex are as the report gives them. The reporter is the primary source in the report. 0% of the reports give the United States as the country.
Reason for use
| Indication as recorded (MedDRA) | Reports | Share |
|---|---|---|
| Diabetes mellitus | 196 | 40.5% |
| Type 2 diabetes mellitus | 70 | 14.5% |
| Glucose tolerance impaired | 30 | 6.2% |
| Blood glucose abnormal | 9 | 1.9% |
| Blood glucose increased | 9 | 1.9% |
| Gestational diabetes | 2 | 0.4% |
The reporter fills in the indication, and the field is often empty. Each share is of all 484 reports.
Pages near this one
- Gliclazide next in the A to Z list
- Glifage Xr next in the A to Z list
- Glibenclamide next in the A to Z list
- Glimepiride next in the A to Z list
- Gliadel next in the A to Z list
- Glipizide next in the A to Z list
- Gleostine next in the A to Z list
- Glivec next in the A to Z list
- Gleevec Unknown next in the A to Z list
- Glofitamab next in the A to Z list
- Gleevec next in the A to Z list
- Glucagon next in the A to Z list
These links are for navigation. No count selected them.
Official pages
- DailyMed labels for GlifageThe labels (prescribing information) that have this name, at the National Library of Medicine.
- MedWatch Online Voluntary Reporting FormThe online form of FDA for a voluntary report.
- MedWatch: The FDA Safety Information and Adverse Event Reporting ProgramThe page of the FDA program that receives reports about drugs and devices.
- FDA Adverse Event Monitoring System (AEMS) Public DashboardThe public dashboard of FDA for adverse event reports on drugs and biologics.
The site checked these addresses on . The links open in a new tab.
Cite this page
Reported Reactions. Glifage: adverse event reports that FDA received. https://reportedreactions.com/drug/glifage/ 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 1 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 Oct 2026. A class is the pharmacologic class (EPC) of the FDA label.
A report is in the count when it names Glifage as a suspect or interacting product. The 2,172 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 Glifage 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 Glifage?
No. It is a count of what people reported to FDA: 484 reports from August 2012 to March 2026. 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?
Consumer or non-health professional (89.7%), physician (3.3%) and other health professional (2.9%). 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.