Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Muse 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 April 2004 to January 2024, FDA received 1,352 adverse event reports that name Muse. The name is as reporters wrote it. In these reports the drug is a suspect or interacting product.

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

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

Reports for male patients were 97.8% of the reports that name Muse and 34.6% 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 Muse 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 Muse 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 44 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 1,327 of the 1,352 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 all 44 terms.

Reaction terms in the reports that name Muse, most reports first
Reaction term (MedDRA) and plain meaningReportsShare of the 1,352 reports
Drug ineffectivethe medicine did not work as expected98472.8%
Wrong technique in product usage processthe product was used in the wrong way47335%
Product quality issuea problem with the product itself15411.4%
Penile pain1249.2%
Penile burning sensation805.9%
No adverse eventno adverse event was reported493.6%
Penile haemorrhage453.3%
Expired product administeredthe product was used past its expiry date362.7%
Urethral haemorrhage292.1%
Erection increased241.8%
Wrong technique in drug usage processthe medicine was used in the wrong way201.5%
Administration site pain191.4%
Genital discomfort181.3%
Burning sensationa burning feeling171.3%
Therapeutic product effect incomplete161.2%
Product label issuea problem with the label151.1%
Exposure via partner131%
Painpain, site not specified131%
Extra dose administered110.8%
Off label useused for a purpose or in a way not on the label110.8%
Product storage errorthe product was stored wrongly110.8%
Incorrect product storagethe product was stored wrongly100.7%
Penile erythema100.7%
Product packaging quantity issue100.7%
Application site pain90.7%
Groin pain90.7%
Application site discomfort80.6%
Product use issuea problem in how the product was used80.6%
Urethral injury80.6%
Painful erection70.5%
Penis disorder70.5%
Product physical issuea physical defect in the product70.5%
Therapeutic product effect decreased70.5%
Urethral pain70.5%
Drug effect decreasedthe medicine had less effect60.4%
Dysgeusiaaltered taste60.4%
Erectile dysfunctiondifficulty getting or keeping an erection60.4%
Pain in extremitypain in an arm or leg60.4%
Testicular pain60.4%
Administration site haemorrhage50.4%
Discomfort50.4%
Genital burning sensation50.4%
Hyperaesthesia50.4%
Incorrect dose administeredthe wrong dose was given50.4%

Download all 44 terms of Muse (CSV)

The counts add to more than 1,352 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 Muse, 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
2004110001010
2007210001001
2009222000000
2012770000070
2013870111041
201518410002009174
201636810103009358
20172454001003241
2018126110000011115
2019162190000019143
20208344000004439
202112264000006458
202237500000432
2023310000012
2024220000020

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 Muse, by the year in which FDA received them
0250500200420092015201820212024
Show the figures of the chart as a table
Reports that name Muse, by the year in which FDA received them
YearReports
20041
20071
20081
20092
20127
20138
2015185
2016371
2017256
2018160
2019122
202078
2021121
202237
20231
20241
Reports that name Muse, 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 Muse
AgeReportsShareShare as a bar
Under 210.1%
2 to 1100%
12 to 1700%
18 to 4480.6%
45 to 6421115.6%
65 to 7429521.8%
75 and over21716.1%
Age not given62045.9%
Sex of the patient in the reports that name Muse
SexReportsShareShare as a bar
Female231.7%
Male1,32297.8%
Unknown or not given70.5%
Type of reporter in the reports that name Muse
ReporterReportsShareShare as a bar
Physician201.5%
Pharmacist171.3%
Other health professional100.7%
Lawyer00%
Consumer or non-health professional1,30196.2%
Not given40.3%

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

Reason for use

Reason for use (indication) that the reports of Muse record
Indication as recorded (MedDRA)ReportsShare
Erectile dysfunction1,10281.5%
Prostate cancer50.4%
Sexual dysfunction40.3%

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

Drugs in the same reports

Other drugs that the reports of Muse name, in any role, in order of name
DrugReports that name the two
Amlodipine65
Aspirin62
Atorvastatin41
Cialis50
Lisinopril87
Losartan47
Metformin115
Metoprolol59
Simvastatin40
Viagra102

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

No. It is a count of what people reported to FDA: 1,352 reports from April 2004 to January 2024. 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 (96.2%), physician (1.5%) and pharmacist (1.3%). 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.