Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Tafamidis meglumine adverse event reports that FDA received

Name type
Generic name

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

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

FDA received 8 reports in the 12 months to June 2026 and 30 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 Tafamidis meglumine 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 2 reports that name Tafamidis meglumine.
  • In January to March 2026, FDA received 0.
  • In April to June 2025, FDA received 4.

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 41 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 401 of the 426 reports (94.1%).

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 all 41 terms.

Reaction terms in the reports that name Tafamidis meglumine, most reports first
Reaction term (MedDRA) and plain meaningReportsShare of the 426 reports
Cardiac failureheart failure6114.3%
Deaththe patient died; cause not stated by this term5813.6%
Off label useused for a purpose or in a way not on the label296.8%
Acute kidney injurysudden loss of kidney function286.6%
Atrial fibrillationan irregular heart rhythm266.1%
Dyspnoeashortness of breath235.4%
Product use in unapproved indicationused for a purpose not on the label194.5%
Syncopefainting163.8%
Fatiguetiredness153.5%
Falla fall143.3%
Pyrexiafever143.3%
Sepsisa severe body-wide response to infection133.1%
Spinal stenosis133.1%
Cardiac failure congestivecongestive heart failure112.6%
Hypotensionlow blood pressure112.6%
Atrial flutter102.3%
Blood culture positive102.3%
Cardiac failure chronic92.1%
Hyperlipidaemiaraised blood fats92.1%
Hypokalaemialow blood potassium92.1%
Insomniadifficulty sleeping92.1%
Intervertebral disc protrusiona bulging spinal disc92.1%
Neuropathy peripheralnerve damage in hands or feet92.1%
Cardiac amyloidosis81.9%
Sudden deatha sudden death81.9%
Condition aggravatedthe condition being treated got worse71.6%
Dizzinesslight-headedness or unsteadiness71.6%
Gait disturbancedifficulty walking71.6%
Tachycardiafast heart rate71.6%
Cutaneous vasculitis61.4%
Disease progressionthe disease advanced61.4%
Drug interactionan interaction between medicines61.4%
Hypersensitivity vasculitis61.4%
Cardiac failure acute51.2%
Chest discomfort51.2%
Cough51.2%
Endocarditis51.2%
Nauseafeeling sick51.2%
Pyelonephritis acute51.2%
Rhabdomyolysismuscle breakdown51.2%
Staphylococcal sepsis51.2%

Download all 41 terms of Tafamidis meglumine (CSV)

The counts add to more than 426 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.

Same ingredient, other names

Reporters write a brand name or a generic name. Each name has its own page and its own count.

Names of Tafamidis meglumine with a page, in the order generic names, brand names, names as reported
NameName typeReports
Tafamidis meglumine (this page)Generic name426
VyndaqelBrand name4,124

Sum of the separately reported names: 4,550. A report that names two of these names is in the sum two times. The sum is not the number of reports for the ingredient.

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 .

Outcomes by year

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

Outcomes in the reports that name Tafamidis meglumine, 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
2012330210020
2013330111010
201510100090020
2016443340000
201831315112900140
2019916011534103331
202077761933710371
202148461901920252
202255532402310262
202339391811700200
202446431612000263
2025141421110080
2026542010031

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 Tafamidis meglumine, by the year in which FDA received them
05010020122015201820212024

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 Tafamidis meglumine, by the year in which FDA received them
YearReports
20124
20134
20141
201517
20166
20172
201827
201995
202080
202151
202253
202330
202442
202512
20262
Reports that name Tafamidis meglumine, by month, five years to June 2026
0102020222023202420252026

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 Tafamidis meglumine
AgeReportsShareShare as a bar
Under 200%
2 to 1110.2%
12 to 1700%
18 to 44163.8%
45 to 64419.6%
65 to 747918.5%
75 and over19144.8%
Age not given9823%
Sex of the patient in the reports that name Tafamidis meglumine
SexReportsShareShare as a bar
Female7718.1%
Male28065.7%
Unknown or not given6916.2%
Type of reporter in the reports that name Tafamidis meglumine
ReporterReportsShareShare as a bar
Physician22151.9%
Pharmacist20.5%
Other health professional12128.4%
Lawyer00%
Consumer or non-health professional8018.8%
Not given20.5%

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

Reason for use

Reason for use (indication) that the reports of Tafamidis meglumine record
Indication as recorded (MedDRA)ReportsShare
Cardiac amyloidosis13631.9%
Hereditary neuropathic amyloidosis5312.4%
Amyloidosis4711%
Familial amyloidosis122.8%
Cardiomyopathy102.3%
Amyloidosis senile92.1%

The reporter fills in the indication, and the field is often empty. Each share is of all 426 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. Tafamidis meglumine: adverse event reports that FDA received. https://reportedreactions.com/drug/tafamidis-meglumine/ 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 Tafamidis meglumine as a suspect or interacting product. The 44 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 Tafamidis meglumine 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 Tafamidis meglumine?

No. It is a count of what people reported to FDA: 426 reports from May 2012 to April 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 (51.9%), other health professional (28.4%) and consumer or non-health professional (18.8%). 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.