Others titles
- FDA Adverse Events Reporting System Demographics Quarterly Report 2018
- FDA Adverse Events Reporting System US Demographics 2018
- FAERS Demographics Report 2018
Keywords
- US Demographics
- FAERS Database
- Adverse Reaction
- Adverse Events of Medication
- Adverse Event Reporting Form
- FAERS
- Serious Adverse Event
- Adverse Events Reporting System
FDA Adverse Events Reporting System Demographics 2018
The FDA Adverse Event Reporting System (FAERS) contains information on medication errors, quality complaints and drug-related adverse events that were submitted to FDA (U.S. Food and Drug Administration) in 2018. The Demographics dataset 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
FAERS (FDA Adverse Event Reporting System) is designed to support the FDA’s post-marketing safety surveillance program for drug and therapeutic biologic products. It is a useful tool for FDA (U.S. Food and Drug Administration) 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.
The reports in FAERS are submitted to FDA by 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 to the products’ manufacturers who then send these reports to FDA.
About this Dataset
Data Info
Date Created | 2018-05-12 |
---|---|
Last Modified | 2019-02-07 |
Version | 2019-02-07 |
Update Frequency |
Quarterly |
Temporal Coverage |
2018-01-01 to 2018-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 | US Demographics, FAERS Database, Adverse Reaction, Adverse Events of Medication, Adverse Event Reporting Form, FAERS, Serious Adverse Event, Adverse Events Reporting System |
Other Titles | FDA Adverse Events Reporting System Demographics Quarterly Report 2018, FDA Adverse Events Reporting System US Demographics 2018, FAERS Demographics Report 2018 |
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 : 1enum : Array ( [0] => Q1 [1] => Q2 [2] => Q3 [3] => Q4 ) |
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 | integer | 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). Abbreviations: "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 |
2018 | Q1 | 100035813 | 10003581 | 3 | Follow-up | 2014-01-10 | 2018-01-16 | 2014-03-12 | 2018-01-23 | Expedited (15-Day) | CN-ELI_LILLY_AND_COMPANY-CN201801014052 | ELI LILLY AND CO | 64.0 | YEAR | Male | True | 2018-01-23 | Consumer | Canada | China | ||||||
2018 | Q1 | 100048965 | 10004896 | 5 | Follow-up | 2018-02-01 | 2014-03-12 | 2018-02-09 | Expedited (15-Day) | PHHY2017AU020915 | NOVARTIS | Male | True | 69.0 | Kilograms | 2018-02-09 | Consumer | COUNTRY NOT SPECIFIED | Australia | |||||||
2018 | Q1 | 100054258 | 10005425 | 8 | Follow-up | 2013-07-01 | 2018-01-05 | 2014-03-12 | 2018-01-11 | Expedited (15-Day) | JP-BAUSCH-BL-2018-004001 | BAUSCH AND LOMB | 65.0 | YEAR | Male | True | 2018-01-11 | Physician | Japan | Japan | ||||||
2018 | Q1 | 100058884 | 10005888 | 4 | Follow-up | 2011 | 2018-03-02 | 2014-03-13 | 2018-03-07 | Periodic (Non-Expedited) | US-ASTRAZENECA-2015SE68374 | ASTRAZENECA | 775.0 | MONTH | Female | True | 61.2 | Kilograms | 2018-03-07 | Consumer | United States of America (the) | United States of America (the) | ||||
2018 | Q1 | 100060834 | 10006083 | 4 | Follow-up | 2014 | 2017-12-04 | 2014-03-13 | 2018-01-26 | Expedited (15-Day) | JP-ASTELLAS-2018JP005660 | ASTELLAS | 60.0 | YEAR | Female | True | 2018-01-26 | Consumer | Japan | Japan | ||||||
2018 | Q1 | 100065478 | 10006547 | 8 | Follow-up | 2012-03-29 | 2018-01-30 | 2014-03-13 | 2018-02-09 | Expedited (15-Day) | JP-ROCHE-2070545 | ROCHE | 82.0 | YEAR | Male | True | 59.0 | Kilograms | 2018-02-09 | Physician | Japan | Japan | ||||
2018 | Q1 | 100066292 | 10006629 | 2 | Follow-up | 2018-02-19 | 2014-03-13 | 2018-02-22 | Periodic (Non-Expedited) | US-MUNDIPHARMA DS AND PHARMACOVIGILANCE-USA-2017-0138515 | PURDUE | Adult | Female | True | 2018-02-22 | Consumer | United States of America (the) | United States of America (the) | ||||||||
2018 | Q1 | 100071964 | 10007196 | 4 | Follow-up | 2013-06-14 | 2018-03-05 | 2014-03-13 | 2018-03-08 | Periodic (Non-Expedited) | US-PFIZER INC-2018064046 | PFIZER | True | 2018-03-08 | Other health-professional | United States of America (the) | United States of America (the) | |||||||||
2018 | Q1 | 100100246 | 10010024 | 6 | Follow-up | 2008-05 | 2018-03-12 | 2014-03-13 | 2018-03-19 | Periodic (Non-Expedited) | US-MYLANLABS-2018M1012089 | MYLAN | Female | True | 2018-03-19 | Consumer | United States of America (the) | United States of America (the) | ||||||||
2018 | Q1 | 100113852 | 10011385 | 2 | Follow-up | 2013-10 | 2018-01-09 | 2014-03-14 | 2018-01-15 | Expedited (15-Day) | CA-ROCHE-2081977 | ROCHE | Female | True | 2018-01-15 | Physician | Canada | Canada |