Demos
Others titles
- FDA Adverse Events Reporting System Outcome Report 2017
- FDA Adverse Events Reporting System patent Outcome Reports 2017
- FAERS Outcome Report 2017
Keywords
- US Demographics
- FDA Data
- AERS database
- FAERS Database
- FDA Adverse Events
FDA Adverse Events Reporting System Patient Outcome 2017
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 “Patient Outcome” file contains information on patient outcomes for the event (0 or more).
Get The Data
- Research
Non-Commercial, 
Share-Alike, 
Attribution Free Forever - Commercial
Commercial 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 (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.
About this Dataset
Data Info
| 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 | |
| Source License Requirements |
N/A |
| Source Citation |
N/A |
| Keywords | US Demographics, FDA Data, AERS database, FAERS Database, FDA Adverse Events |
| Other Titles | FDA Adverse Events Reporting System Outcome Report 2017, FDA Adverse Events Reporting System patent Outcome Reports 2017, FAERS Outcome Report 2017 |
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_Number. It is the Identifier for the case sequence (version) number as reported by the manufacturer | integer | level : Nominalrequired : 1 |
| Case_Id | Case number for identifying a FAERS case. | integer | level : Nominalrequired : 1 |
| Patient_Outcome | Description of patient outcome. The outcome from the latest version of a case is provided | string | required : 1 |
Data Preview
| Year | Quarter | Primary Id | Case Id | Patient Outcome |
| 2017 | Q1 | 100039237 | 10003923 | Other Serious (Important Medical Event) |
| 2017 | Q1 | 1000588614 | 10005886 | Hospitalization - Initial or Prolonged |
| 2017 | Q1 | 100063033 | 10006303 | Hospitalization - Initial or Prolonged |
| 2017 | Q1 | 100063033 | 10006303 | Other Serious (Important Medical Event) |
| 2017 | Q1 | 100065923 | 10006592 | Death |
| 2017 | Q1 | 100065923 | 10006592 | Hospitalization - Initial or Prolonged |
| 2017 | Q1 | 100085064 | 10008506 | Hospitalization - Initial or Prolonged |
| 2017 | Q1 | 1001058224 | 10010582 | Hospitalization - Initial or Prolonged |
| 2017 | Q1 | 1001058224 | 10010582 | Life-Threatening |
| 2017 | Q1 | 1001163912 | 10011639 | Other Serious (Important Medical Event) |
