Others titles
- Percentage Average FDA Adverse Events Reporting System Demographics 2016
- FDA Adverse Events Reporting System US Demographics 2016
- States Population FDA Adverse Events Reporting System Demographics 2016
Keywords
- Percentage Average
- US Demographics
- States Population
- AERS database
FDA Adverse Events Reporting System Demographics 2016
FAERS database is designed to support the FDA’s post-marketing safety surveillance program for drug and therapeutic biologic products.
The Demographics data file contains patient demographic and administrative information, a single record for each event report.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
Description
The FDA Adverse Event Reporting System (FAERS) is a database that contains information on adverse event and medication error reports submitted to FDA. 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.
About this Dataset
Data Info
Date Created | 2012-09-10 |
---|---|
Last Modified | 2017-02-25 |
Version | 2017-02-25 |
Update Frequency |
Quarterly |
Temporal Coverage |
2016-01-01 to 2016-12-31 |
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 | |
Source License Requirements |
N/A |
Source Citation |
N/A |
Keywords | Percentage Average, US Demographics, States Population, AERS database |
Other Titles | Percentage Average FDA Adverse Events Reporting System Demographics 2016, FDA Adverse Events Reporting System US Demographics 2016, States Population FDA Adverse Events Reporting System Demographics 2016 |
Data Fields
Name | Description | Type | Constraints |
---|---|---|---|
Year | The year in which the data was submitted | date | required : 1 |
Quarter | The quarter of the year in which the data was submitted | string | required : 1 |
Primary_Id | Number 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. It is the Identifier for the case sequence (version) number as reported by the manufacturer | integer | level : Nominalrequired : 1unique : 1 |
Case_Id | Number for identifying a FAERS case | integer | level : Nominalrequired : 1 |
Case_Version_Number | Safety Report Case Version Number. The Initial Case will be version 1. Follow-ups to the case will have sequentially incremented version numbers (for example, 2, 3, 4, etc.) | integer | level : Ordinalrequired : 1 |
Status_of_Report | Initial or follow-up status of report, as reported by manufacturer | string | required : 1 |
Event_Date | Date the adverse event occurred or began. If a complete date is not available, a partial date is provided | date | - |
Manufacturer_Date | Date manufacturer first received initial information. In subsequent versions of a case, the latest manufacturer received date will be provided. FAERS extracts will provide only the exact data submitted in the case. Therefore, if a complete date is not available, a partial date will be provided. | date | - |
Initial_FDA_Date | Date FDA received first version (Initial) of Case. FAERS extracts will provide only the exact data submitted in the case. Therefore, if a complete date is not available, a partial date will be provided. | date | - |
Subsequent_FDA_Date | Date FDA received Case. In subsequent versions of a case, the latest manufacturer received date will be provided (YYYY-MM-DD format). FAERS extracts will provide only the exact data submitted in the case. Therefore, if a complete date is not available, a partial date will be provided. | date | - |
Type_of_Report | Type of report submitted to FDA | string | required : 1 |
Authority_Number | Regulatory Authority’s case report number, when available | string | - |
Manufacturer_Number | Manufacturer's unique report identifier | string | - |
Manufacturer_Sender | Coded name of manufacturer sending report; if not found, then verbatim name of organization sending report is mentioned. | string | - |
Literature_Reference | Literature Reference information, when available | string | - |
Age_of_Patient | Numeric value of patient's age at event | number | level : Ratio |
Age_Code | string | - | |
Age_Group | Patient age group, when available | string | - |
Gender_of_Patient | Patient's gender, when available | string | - |
Is_Electronically_Submitted | Whether or not this report was submitted under the electronic submissions procedure for manufacturers. Abbreviations: "true" means Yes, "false" means No | boolean | required : 1 |
Weight_of_Patient | Numeric value of patient's weight | number | level : Ratio |
Weight_Code | string | - | |
Report_Date | Date report was sent to FDA. If a complete date is not available, a partial date is provided | date | - |
Is_Notified_To_Manufacturer | Whether or not voluntary reporter also notified manufacturer (blank for manufacturer reports). Abbreviatiosn: "true" means Yes, "false" means No | boolean | - |
Occupation_Code | Reporter's type of occupation in the latest version of a case | string | - |
Reporter_Country | Country of the reporter in the latest version of a case | string | - |
Occurrence_Country | Country where the event occurred | string | - |
Data Preview
Year | Quarter | Primary Id | Case Id | Case Version Number | Status of Report | Event Date | Manufacturer Date | Initial FDA Date | Subsequent FDA Date | Type of Report | Authority Number | Manufacturer Number | Manufacturer Sender | Literature Reference | Age of Patient | Age Code | Age Group | Gender of Patient | Is Electronically Submitted | Weight of Patient | Weight Code | Report Date | Is Notified To Manufacturer | Occupation Code | Reporter Country | Occurrence Country |
2016 | Q1 | 100036613 | 10003661 | 3 | F | 2014-05-02 | 2014-03-12 | 2016-02-29 | PER | US-ACORDA-ACO_38996_2013 | ACORDA | F | True | 2016-02-29 | CN | US | US | |||||||||
2016 | Q1 | 100043112 | 10004311 | 2 | F | 2014-03-04 | 2016-02-01 | 2014-03-12 | 2016-02-08 | EXP | CO-B.I. PHARMACEUTICALS,INC./RIDGEFIELD-2014-BI-10571CL | BOEHRINGER INGELHEIM | 73.0 | YR | M | True | 2016-02-09 | MD | CO | CO | ||||||
2016 | Q1 | 100045852 | 10004585 | 2 | F | 2013-07 | 2016-02-05 | 2014-03-12 | 2016-02-10 | EXP | CL-PFIZER INC-2014067801 | PFIZER | 74.0 | YR | M | True | 2016-02-10 | CN | CL | CL | ||||||
2016 | Q1 | 100049985 | 10004998 | 5 | F | 2013-07-03 | 2016-01-28 | 2014-03-12 | 2016-02-05 | EXP | PHEH2013US014590 | NOVARTIS | 2.464 | YR | F | True | 2016-02-03 | CN | COUNTRY NOT SPECIFIED | US | ||||||
2016 | Q1 | 100050132 | 10005013 | 2 | F | 2016-02-05 | 2014-03-12 | 2016-02-11 | EXP | BD-BRISTOL-MYERS SQUIBB COMPANY-20469185 | BRISTOL MYERS SQUIBB | A | F | True | 2016-02-11 | OT | BD | BD | ||||||||
2016 | Q1 | 100050162 | 10005016 | 2 | F | 2016-01-29 | 2014-03-12 | 2016-02-09 | EXP | BD-BRISTOL-MYERS SQUIBB COMPANY-20469409 | BRISTOL MYERS SQUIBB | A | F | True | 2016-02-09 | OT | BD | BD | ||||||||
2016 | Q1 | 100050202 | 10005020 | 2 | F | 2016-02-05 | 2014-03-12 | 2016-02-12 | EXP | BD-BRISTOL-MYERS SQUIBB COMPANY-20469383 | BRISTOL MYERS SQUIBB | A | F | True | 2016-02-12 | OT | BD | BD | ||||||||
2016 | Q1 | 100050242 | 10005024 | 2 | F | 2016-02-05 | 2014-03-12 | 2016-02-11 | EXP | BD-BRISTOL-MYERS SQUIBB COMPANY-20469375 | BRISTOL MYERS SQUIBB | A | F | True | 2016-02-11 | OT | BD | BD | ||||||||
2016 | Q1 | 100050262 | 10005026 | 2 | F | 2016-02-05 | 2014-03-12 | 2016-02-12 | EXP | BD-BRISTOL-MYERS SQUIBB COMPANY-20469391 | BRISTOL MYERS SQUIBB | A | F | True | 2016-02-12 | OT | BD | BD | ||||||||
2016 | Q1 | 100051155 | 10005115 | 5 | F | 2014-02-10 | 2016-02-24 | 2014-03-12 | 2016-03-02 | EXP | US-ABBVIE-14P-163-1209675-00 | ABBVIE | 59.855 | YR | M | True | 86.26 | KG | 2016-03-02 | MD | COUNTRY NOT SPECIFIED | US |