Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Zavesca (miglustat) adverse event reports that FDA received

Name type
Brand name
Generic name
Miglustat

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 April 2004 to May 2026, FDA received 867 adverse event reports that name Zavesca. In these reports the drug is a suspect or interacting product.

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

FDA received 3 reports in the 12 months to June 2026 and 5 in the 12 months before. FDA releases FAERS data every quarter, so the newest months are not complete. They grow in later releases.

Of the 1,332,454 drug reports that FDA received in the 12 months to June 2026, 3 (under 0.1%) name Zavesca. Reports from physicians were 63.3% of the reports that name Zavesca and 21.9% of all drug 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.

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

  • In April to June 2026, FDA received 3 reports that name Zavesca.
  • In January to March 2026, FDA received 0.
  • In April to June 2025, FDA received 1.

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 81 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 793 of the 867 reports (91.5%).

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 81 terms.

Reaction terms in the reports that name Zavesca, most reports first
Reaction term (MedDRA) and plain meaningReportsShare of the 867 reports
Deaththe patient died; cause not stated by this term14316.5%
Diarrhoealoose or frequent stools13015%
Niemann-Pick disease8910.3%
Seizurea fit or convulsion8810.1%
Weight decreasedweight loss809.2%
Disease progressionthe disease advanced708.1%
Condition aggravatedthe condition being treated got worse637.3%
Pneumonialung infection627.2%
Tremorshaking606.9%
Dysphagiadifficulty swallowing536.1%
Off label useused for a purpose or in a way not on the label495.7%
Pyrexiafever435%
Product use issuea problem in how the product was used384.4%
Convulsion354%
Epilepsy343.9%
Vomitingbeing sick333.8%
Thrombocytopenialow platelets313.6%
Pneumonia aspirationlung infection from breathing in material303.5%
Concomitant disease aggravated293.3%
Astheniaweakness or lack of energy273.1%
General physical health deteriorationgeneral decline in health252.9%
Respiratory failurethe lungs could not supply enough oxygen242.8%
Gastrostomy232.7%
Falla fall212.4%
Ataxia202.3%
Gastrointestinal disorder192.2%
Drug ineffectivethe medicine did not work as expected172%
Fatiguetiredness172%
Gait disturbancedifficulty walking172%
Abdominal painstomach or belly pain161.8%
Dyspnoeashortness of breath161.8%
Sepsisa severe body-wide response to infection151.7%
Constipation141.6%
Dehydration141.6%
Headachehead pain141.6%
Malaisegeneral feeling of being unwell141.6%
Decreased appetitereduced appetite131.5%
Neurological decompensation131.5%
Neuropathy peripheralnerve damage in hands or feet131.5%
Growth retardation121.4%
Urinary tract infectionbladder or urinary infection121.4%
Cough111.3%
Platelet count decreasedlow platelet count111.3%
Abdominal distensiona bloated abdomen101.2%
Drug dose omissiona dose was missed101.2%
Influenzaflu101.2%
Flatulencewind91%
Gastrointestinal tube insertion91%
Product supply issue91%
Respiratory tract infectiona respiratory infection91%

Download all 81 terms of Zavesca (CSV)

The counts add to more than 867 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 Zavesca, 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
20041040020026
20051491132055
2006982024051
20071090150061
2008881021050
2009871041061
201045431611530242
20113937131750202
201273712222040422
201361582401960313
201448471401720311
201586771824140349
201672631502650319
201794882333720476
201877682503610219
20193432100251052
20205047902680243
202110099830600141
2022772030030
20231182051023
2024321010001
2025532120012
2026322000001

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 Zavesca, by the year in which FDA received them
050100200420082012201620202024

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
Reports that name Zavesca, by the year in which FDA received them
YearReports
200410
200513
200610
20079
20089
20096
201051
201151
201282
201365
201451
201585
201672
201779
201870
201938
202039
202199
20227
202311
20244
20253
20263
Reports that name Zavesca, by month, five years to June 2026
05010020222023202420252026

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 of the patient in the reports that name Zavesca
AgeReportsShareShare as a bar
Under 2333.8%
2 to 1121524.8%
12 to 1711813.6%
18 to 4417820.5%
45 to 64647.4%
65 to 74222.5%
75 and over50.6%
Age not given23226.8%
Sex of the patient in the reports that name Zavesca
SexReportsShareShare as a bar
Female38744.6%
Male34139.3%
Unknown or not given13916%
Type of reporter in the reports that name Zavesca
ReporterReportsShareShare as a bar
Physician54963.3%
Pharmacist526%
Other health professional15618%
Lawyer00%
Consumer or non-health professional758.7%
Not given354%

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

Reason for use

Reason for use (indication) that the reports of Zavesca record
Indication as recorded (MedDRA)ReportsShare
Niemann-pick disease40646.8%
Gaucher's disease637.3%
Lipidosis617%
Gaucher's disease435%
Tay-sachs disease192.2%
Gaucher's disease type i182.1%

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

Drugs in the same reports

Other drugs that the reports of Zavesca name, in any role, in order of name
DrugReports that name the two
Cerezyme16
Clonazepam15
Diazepam17
Keppra50
Lamictal15
Levetiracetam16
MiraLAX23
Onfi17
Vimpat15
Vitamin d17

The table has the 10 drug names that these reports name most. Two names in one report says only that the report recorded the two. It says nothing about the part of a product in the event.

FDA says:

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. The site read the page on .

Importantly, the AEMS data by themselves are not an indicator of the safety profile of the drug or biologic.

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

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. Zavesca: adverse event reports that FDA received. https://reportedreactions.com/drug/zavesca/ 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 Zavesca as a suspect or interacting product. The 37 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 Zavesca 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 Zavesca?

No. It is a count of what people reported to FDA: 867 reports from April 2004 to May 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?

Physician (63.3%), other health professional (18%) and consumer or non-health professional (8.7%). 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.