FDA Adverse Events Reporting System Drug 2017

$395 / year

FAERS (FDA Adverse Events Reporting System) database is designed to support the FDA’s post-marketing safety surveillance program for drug and therapeutic biologic products. The Drug file contains drug/biologic information for as many medications as were reported for the event (1 or more per event).

Complexity

The FDA Adverse Event Reporting System (FAERS) is a database that contains information on adverse event and medication error reports submitted to FDA (U.S. Food and Drug Administration). The informatic structure of the FAERS database adheres to the international safety reporting guidance issued by the International Conference on Harmonisation (ICH E2B). Adverse events and medication errors are coded to terms in the Medical Dictionary for Regulatory Activities (MedDRA) terminology.

FAERS is used for the spontaneous reporting of adverse events and medication errors involving human drugs and therapeutic biological products. FAERS began on September 10, 2012, and replaced the Adverse Event Reporting System (also known as Legacy AERS), which was decommissioned on August 27, 2012.

FAERS is a useful tool for FDA for activities such as looking for new safety concerns that might be related to a marketed product, evaluating a manufacturer’s compliance to reporting regulations and responding to outside requests for information. The reports in FAERS are evaluated by clinical reviewers in the Center for Drug Evaluation and Research (CDER) and the Center for Biologics Evaluation and Research (CBER) to monitor the safety of products after they are approved by FDA. If a potential safety concern is identified in FAERS, further evaluation is performed. Further evaluation might include conducting studies using other large databases, such as those available in the Sentinel System. Based on an evaluation of the potential safety concern, FDA may take regulatory action(s) to improve product safety and protect the public health, such as updating a product’s labeling information, restricting the use of the drug, communicating new safety information to the public, or, in rare cases, removing a product from the market.

Reporting of adverse events and medication errors by healthcare professionals and consumers is voluntary in the United States. FDA receives some adverse event and medication error reports directly from healthcare professionals (such as physicians, pharmacists, nurses and others) and consumers (such as patients, family members, lawyers and others). Healthcare professionals and consumers may also report adverse events and/or medication errors to the products’ manufacturers. If a manufacturer receives an adverse event report, it is required to send the report to FDA as specified by regulations. The reports received directly and the reports from manufacturers are entered into FAERS.

Date Created

2017-01-01

Last Modified

2017-12-02

Version

2017-12-02

Update Frequency

Quarterly

Temporal Coverage

2017-01-01 to 2017-09-30

Spatial Coverage

United States

Source

John Snow Labs => U.S. Food and Drug Administration (FDA), Center for Drug Evaluation and Research (CDER), Office of Surveillance and Epidemiology (OSE)

Source License URL

John Snow Labs Standard License

Source License Requirements

N/A

Source Citation

N/A

Keywords

Percentage Average, US Demographics, States Population, AERS database, FAERS Database, FDA Adverse Events

Other Titles

FDA Adverse Events Reporting System Drugs Quarterly Report 2017, FDA Adverse Events Reporting System US Drugs 2017, FAERS Drugs Report 2017

Name Description Type Constraints
YearThe year in which the data was submitteddaterequired : 1
QuarterThe quarter of the year in which the data was submittedstringrequired : 1
Primary_IdNumber for identifying a FAERS report. This is the primary link field (primary key) between data files. This is a concatenated key of Case_Id and Case_Version_Number. It is the Identifier for the case sequence (version) number as reported by the manufacturerintegerrequired : 1 level : Nominal
Case_IdCase number for identifying a FAERS case.integerrequired : 1 level : Nominal
Drug_Sequence_NumberSequence number for identifying a drug for a Case. To link to the "Drug Therapy Dates" file, both the Primary_Id (primary key) and the Drug_Sequence_Number (secondary key) are needed.integerrequired : 1 level : Ordinal
Role_of_Drug_in_EventCode for drug's reported role in event.string-
Drug_NameName of medicinal product. If a "Valid Trade Name" is populated for this ISR (Individual Safety Report), then Drug_Name = Valid Trade Name; if not, then Drug_Name = "Verbatim" name, exactly as entered on the report. For the great majority of reports, there is a "Valid Trade Name."string-
Product_Active_IngredientActive Ingredient of the product, when availablestring-
Source_of_Drug_NameCode for source of Drug_Name, either validated trade name or verbatim name.string-
Route_of_AdministrationThe route of drug administrationstring-
Dose_Verbatim_TextVerbatim text for dose, frequency, and route, exactly as entered on report.string-
Cumulative_Dose_to_First_ReactionCumulative dose to first reaction of the drugnumberlevel : Ratio
Unit_of_Cumulative_Dose_to_First_ReactionCumulative dose to first reaction unitstring-
Dechallenge_CodeDechallenge code, indicating if reaction abated when drug therapy was stoppedstring-
Rechallenge_CodeRechallenge code, indicating if reaction recurred when drug therapy was restartedstring-
Drug_Lot_NumberLot number of the drugstring-
Drug_Expiration_DateExpiration date of the drug. If a complete date is not available, a partial date is provideddate-
NDA_NumberNDA (New Drug Application) number of the drugstring-
Dose_AmountAmount of drug dose reportednumberlevel : Ratio
Dose_Unitstring-
Drug_Dosage_FormForm of drug dosage reportedstring-
Dose_FrequencyFrequency of dose reportedstring-
YearQuarterPrimary_IdCase_IdDrug_Sequence_NumberRole_of_Drug_in_EventDrug_NameProduct_Active_IngredientSource_of_Drug_NameRoute_of_AdministrationDose_Verbatim_TextCumulative_Dose_to_First_ReactionUnit_of_Cumulative_Dose_to_First_ReactionDechallenge_CodeRechallenge_CodeDrug_Lot_NumberDrug_Expiration_DateNDA_NumberDose_AmountDose_UnitDrug_Dosage_FormDose_Frequency
2017Q1130889161130889168ConcomitantEVerbatim name used
2017Q1131087171131087174ConcomitantCVerbatim name used
2017Q1131087171131087176ConcomitantDVerbatim name used
2017Q1131091411131091417ConcomitantCVerbatim name used
2017Q1131091471131091477ConcomitantCVerbatim name used
2017Q1131622961131622969ConcomitantDVerbatim name used
2017Q1131633401131633404ConcomitantDVerbatim name used
2017Q1131664161131664164ConcomitantEVerbatim name used
2017Q1131664161131664166ConcomitantAVerbatim name used
2017Q1131785311131785315ConcomitantCVerbatim name used