Abacavir and lamivudine adverse event reports that FDA received
- Name type
- Generic name
- Class
- Hepatitis B virus nucleoside analog reverse transcriptase inhibitor
- Also reported as
- Abacavir/Lamivudine, Abacavir /Lamivudine, Abacavir And Lamivudine Tablets
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 October 2005 to February 2026, FDA received 297 adverse event reports that name Abacavir and lamivudine. In these reports the drug is a suspect or interacting product.
In the same period, 89 further reports name it only as a concomitant medicine. The counts on this page do not include these reports.
FDA received 4 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, 4 (under 0.1%) name Abacavir and lamivudine. Reports from other health professionals were 66.7% of the reports that name Abacavir and lamivudine 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 Abacavir and lamivudine 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 0 reports that name Abacavir and lamivudine.
- In January to March 2026, FDA received 1.
- In April to June 2025, FDA received 0.
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 12 reaction terms that 5 or more reports record. A term with fewer than 5 reports is not in the table.
This list is partial.
It covers 202 of the 297 reports (68%).
The site keeps reaction terms only for years in which the drug has 12 or more reports.
So a count in the table can be lower than the count of FDA.
The table shows all 12 terms.
| Reaction term (MedDRA) and plain meaning | Reports | Share of the 297 reports |
|---|---|---|
| Virologic failure | 29 | 9.8% |
| Foetal exposure during pregnancythe unborn baby was exposed to the medicine | 23 | 7.7% |
| Treatment failurethe treatment did not work | 11 | 3.7% |
| Exposure during pregnancythe medicine was taken during pregnancy | 10 | 3.4% |
| Drug interactionan interaction between medicines | 8 | 2.7% |
| Deaththe patient died; cause not stated by this term | 7 | 2.4% |
| Nauseafeeling sick | 6 | 2% |
| Treatment noncompliancethe treatment was not taken as directed | 6 | 2% |
| Dizzinesslight-headedness or unsteadiness | 5 | 1.7% |
| Drug resistance | 5 | 1.7% |
| Headachehead pain | 5 | 1.7% |
| Maternal exposure during pregnancythe mother took the medicine during pregnancy | 5 | 1.7% |
The counts add to more than 297 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.
| Name | Name type | Reports |
|---|---|---|
| Abacavir and lamivudine (this page) | Generic name | 297 |
| Abacavir sulfate and lamivudine | Generic name | 501 |
Sum of the separately reported names: 798. 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 Abacavir and lamivudine, 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 |
|---|---|---|---|---|---|---|---|---|---|
| 2005 | 2 | 2 | 0 | 1 | 1 | 0 | 0 | 1 | 0 |
| 2006 | 6 | 6 | 0 | 1 | 2 | 0 | 2 | 1 | 0 |
| 2007 | 7 | 7 | 0 | 1 | 6 | 1 | 0 | 1 | 0 |
| 2014 | 4 | 4 | 0 | 0 | 0 | 0 | 0 | 4 | 0 |
| 2015 | 11 | 10 | 0 | 0 | 0 | 0 | 0 | 10 | 1 |
| 2016 | 33 | 33 | 3 | 0 | 5 | 0 | 0 | 30 | 0 |
| 2017 | 26 | 22 | 1 | 2 | 5 | 0 | 0 | 20 | 4 |
| 2018 | 33 | 30 | 7 | 3 | 7 | 0 | 2 | 27 | 3 |
| 2019 | 28 | 25 | 1 | 1 | 2 | 0 | 11 | 23 | 3 |
| 2020 | 36 | 34 | 3 | 3 | 6 | 0 | 5 | 30 | 2 |
| 2021 | 44 | 35 | 7 | 1 | 5 | 0 | 4 | 31 | 9 |
| 2022 | 41 | 18 | 4 | 0 | 4 | 0 | 4 | 16 | 23 |
| 2023 | 7 | 7 | 3 | 2 | 3 | 0 | 0 | 6 | 0 |
| 2024 | 10 | 10 | 4 | 2 | 2 | 2 | 0 | 10 | 0 |
| 2025 | 4 | 4 | 1 | 0 | 0 | 0 | 1 | 4 | 0 |
| 2026 | 5 | 5 | 1 | 0 | 0 | 0 | 0 | 5 | 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 |
|---|---|
| 2005 | 1 |
| 2006 | 7 |
| 2007 | 7 |
| 2014 | 4 |
| 2015 | 13 |
| 2016 | 36 |
| 2017 | 27 |
| 2018 | 35 |
| 2019 | 31 |
| 2020 | 31 |
| 2021 | 45 |
| 2022 | 36 |
| 2023 | 9 |
| 2024 | 10 |
| 2025 | 4 |
| 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 | 6 | 2% | |
| 2 to 11 | 1 | 0.3% | |
| 12 to 17 | 5 | 1.7% | |
| 18 to 44 | 52 | 17.5% | |
| 45 to 64 | 32 | 10.8% | |
| 65 to 74 | 5 | 1.7% | |
| 75 and over | 2 | 0.7% | |
| Age not given | 194 | 65.3% |
| Sex | Reports | Share | Share as a bar |
|---|---|---|---|
| Female | 82 | 27.6% | |
| Male | 80 | 26.9% | |
| Unknown or not given | 135 | 45.5% |
| Reporter | Reports | Share | Share as a bar |
|---|---|---|---|
| Physician | 29 | 9.8% | |
| Pharmacist | 13 | 4.4% | |
| Other health professional | 198 | 66.7% | |
| Lawyer | 0 | 0% | |
| Consumer or non-health professional | 53 | 17.8% | |
| Not given | 4 | 1.3% |
Age and sex are as the report gives them. The reporter is the primary source in the report. 23.6% of the reports give the United States as the country.
Reason for use
| Indication as recorded (MedDRA) | Reports | Share |
|---|---|---|
| Hiv infection | 145 | 48.8% |
| Antiretroviral therapy | 3 | 1% |
The reporter fills in the indication, and the field is often empty. Each share is of all 297 reports.
Pages near this one
- Abacavir sulfate and lamivudine same ingredient
- Adefovir dipivoxil same class
- Baraclude same class
- Combivir same class
- Abacavir next in the A to Z list
- Abacavir Lamivudine next in the A to Z list
- 6-Mp next in the A to Z list
- Abacavir sulfate next in the A to Z list
- 6-Mercaptopurine Monohydrate next in the A to Z list
- Abacavir Sulfate + Lamivudine next in the A to Z list
- 6-Mercaptopurine next in the A to Z list
- 5-Fu Fluorouracil next in the A to Z list
These links are for navigation. No count selected them. The class page lists each drug of the class.
Official pages
- DailyMed labels for Abacavir and lamivudineThe 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. Abacavir and lamivudine: adverse event reports that FDA received. https://reportedreactions.com/drug/abacavir-and-lamivudine/ 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 Abacavir and lamivudine as a suspect or interacting product. The 89 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 Abacavir and lamivudine 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 Abacavir and lamivudine?
No. It is a count of what people reported to FDA: 297 reports from October 2005 to February 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 (66.7%), consumer or non-health professional (17.8%) and physician (9.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.