Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

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

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

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

FDA received 19 reports in the 12 months to June 2026 and 22 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, 19 (under 0.1%) name Lopinavir. Reports from other health professionals were 71.7% of the reports that name Lopinavir and 19.7% 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 Lopinavir 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 15 reports that name Lopinavir.
  • In January to March 2026, FDA received 0.
  • In April to June 2025, FDA received 10.

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 178 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,619 of the 1,626 reports (99.6%).

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

Reaction terms in the reports that name Lopinavir, most reports first
Reaction term (MedDRA) and plain meaningReportsShare of the 1,626 reports
Foetal exposure during pregnancythe unborn baby was exposed to the medicine24615.1%
Exposure during pregnancythe medicine was taken during pregnancy19111.7%
Virologic failure17310.6%
Off label useused for a purpose or in a way not on the label1579.7%
Lipodystrophy acquiredchanges in body fat distribution1499.2%
Drug resistance1489.1%
Premature babya baby born early1066.5%
Diplopiadouble vision1006.2%
Eyelid ptosis1006.2%
Drug interactionan interaction between medicines965.9%
Treatment failurethe treatment did not work965.9%
Mitochondrial toxicity925.7%
Premature delivery865.3%
Progressive external ophthalmoplegia855.2%
Viral mutation identified754.6%
Aspartate aminotransferase increasedraised liver enzyme (AST)643.9%
Intentional product use issuedeliberate use not as intended633.9%
Alanine aminotransferase increasedraised liver enzyme (ALT)593.6%
Pathogen resistance533.3%
Portal hypertension523.2%
Maternal exposure during pregnancythe mother took the medicine during pregnancy513.1%
Treatment noncompliancethe treatment was not taken as directed513.1%
Abortion spontaneousmiscarriage472.9%
Ultrasound antenatal screen472.9%
Hepatic cytolysis452.8%
Diarrhoealoose or frequent stools402.5%
Deaththe patient died; cause not stated by this term382.3%
Hydrops foetalis342.1%
Drug abusemisuse of a medicine332%
Cleft lip and palate322%
Trisomy 18322%
Product use in unapproved indicationused for a purpose not on the label301.8%
Vomitingbeing sick291.8%
Nauseafeeling sick281.7%
Ophthalmoplegia281.7%
Immune reconstitution syndrome271.7%
Viral load increased271.7%
Caesarean section261.6%
Depressionlow mood261.6%
Product use issuea problem in how the product was used261.6%
Low birth weight baby231.4%
Immune reconstitution inflammatory syndrome221.4%
Stillbirth211.3%
Anaemialow red blood cells201.2%
Hypokalaemialow blood potassium191.2%
Acute kidney injurysudden loss of kidney function181.1%
Drug ineffectivethe medicine did not work as expected181.1%
Pyrexiafever181.1%
Somnolencedrowsiness171%
Fatiguetiredness161%

Download all 178 terms of Lopinavir (CSV)

The counts add to more than 1,626 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 Lopinavir, 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
2004151441310131
2005242450920120
2006771040020
20074140701201311
2008222220302180
20098686321904670
20104343501701320
2011313110505300
2012171790300110
20133332611111201
2014222230801170
20157372130507641
2016284282542158112352
201725825820112062330
20189996201131923
2019443930614385
202017314711113031611726
20219992372418837
2022686711118112621
2023808022131219770
20243737601508330
20253939601411390
2026313122124022310

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

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 Lopinavir, by the year in which FDA received them
YearReports
200411
200522
200615
200743
200822
200979
201060
201132
201221
201333
201420
201570
2016297
2017262
2018118
201964
2020167
2021100
202279
202361
202414
202521
202615
Reports that name Lopinavir, by month, five years to June 2026
0255020222023202420252026

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 Lopinavir
AgeReportsShareShare as a bar
Under 2553.4%
2 to 11332%
12 to 17251.5%
18 to 4426016%
45 to 6430818.9%
65 to 74452.8%
75 and over241.5%
Age not given87653.9%
Sex of the patient in the reports that name Lopinavir
SexReportsShareShare as a bar
Female28117.3%
Male59236.4%
Unknown or not given75346.3%
Type of reporter in the reports that name Lopinavir
ReporterReportsShareShare as a bar
Physician22914.1%
Pharmacist120.7%
Other health professional1,16671.7%
Lawyer00%
Consumer or non-health professional784.8%
Not given1418.7%

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

Reason for use

Reason for use (indication) that the reports of Lopinavir record
Indication as recorded (MedDRA)ReportsShare
Hiv infection90555.7%
Covid-191167.1%
Antiretroviral therapy744.6%
Prophylaxis against HIV infection664.1%
Antiviral treatment271.7%
Foetal exposure during pregnancy130.8%

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

Drugs in the same reports

Other drugs that the reports of Lopinavir name, in any role, in order of name
DrugReports that name the two
Abacavir311
Didanosine362
Efavirenz466
Emtricitabine379
Lamivudine945
Nevirapine501
Ritonavir1,340
Stavudine370
Tenofovir414
Zidovudine748

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

No. It is a count of what people reported to FDA: 1,626 reports from February 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?

Other health professional (71.7%), physician (14.1%) and consumer or non-health professional (4.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.