Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Sign in
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

FDA Drug Adverse Events Reporting System FAERS 2017

Provided By: John Snow Labs

FDA Drug Adverse Events Reporting System FAERS 2017

Provided By: John Snow Labs

The Food and Drug Administration (FDA) Adverse Event Reporting System (FAERS) data package contains information on medication errors, quality complaints and drug-related adverse events that were submitted to FDA in 2017.

Product offers

The following offers are available for this product. Choose an offer to view the pricing and access duration options for the offer. Select an offer and continue to subscribe. Your subscription begins on the date that you accept the offer. Additional taxes or fees might apply.

Public offer

Payment schedule: Upfront payment | Offer auto-renewal: Supported
$0 for 12 months

Overview

Overview

FAERS data package is designed to support the FDA's post-marketing safety surveillance program for drug and therapeutic biologic products. It is a useful tool for activities such as looking for new safety concerns that might be related to a marketed product, evaluating a manufacturer's compliance with 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. These reports 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 the FDA. The datasets in FAERS data package contain much relevant information such as patient demographics, drug name, dose and route of administration, diagnosis and indication for use, therapy starts and ends date and patient outcome.


License Information

The use of John Snow Labs datasets is free for personal and research purposes. For commercial use please subscribe to the Data Library on AWS. The subscription will allow you to use all John Snow Labs datasets and data packages for commercial purposes.


Metadata

DescriptionValue
Data Package ComplexityMedium
Available EnrichmentsN/A
KeywordsAdverse Reaction, Adverse Events in Healthcare, Adverse Event Reporting Form, FAERS, Serious Adverse Event, Adverse Events Reporting System
Other TitlesFDA Adverse Event Reporting Guidance, Adverse Event Database by FDA 2017, FDA Post-Marketing Surveillance Reports 2017, FDA Drugs Causing Serious Adverse Effects 2017, FDA Reporting System of Adverse Effects 2017

Included Datasets

  1. FDA Adverse Events Reporting System Demographics 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 Demographics dataset contains patient demographic and administrative information, a single record for each event report.

  2. FDA Adverse Events Reporting System Drug 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 Drug file contains drug/biologic information for as many medications as were reported for the event (1 or more per event).

  3. FDA Adverse Events Reporting System Drug Indication 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 Indication file contains all "Medical Dictionary for Regulatory Activities" (MedDRA) terms coded for the indications for use (diagnoses) for the reported drugs (0 or more per drug per event).

  4. FDA Adverse Events Reporting System Drug Reaction 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 "Drug Reaction" file contains all "Medical Dictionary for Regulatory Activities" (MedDRA) terms coded for the adverse event (1 or more).

  5. FDA Adverse Events Reporting System Drug Therapy Dates 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 Drug Therapy Dates file contains drug therapy start dates and end dates for the reported drugs (0 or more per drug per event).

  6. 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).

  7. FDA Adverse Events Reporting System Report Source 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 Report Source file contains report sources for event (0 or more).


Data Engineering Overview

We deliver high-quality data
  • Each dataset goes through 3 levels of quality review
    • 2 Manual reviews are done by domain experts
    • Then, an automated set of 60+ validations enforces every datum matches metadata & defined constraints
  • Data is normalized into one unified type system
    • All dates, unites, codes, currencies look the same
    • All null values are normalized to the same value
    • All dataset and field names are SQL and Hive compliant
  • Data and Metadata
    • Data is available in both CSV and Apache Parquet format, optimized for high read performance on distributed Hadoop, Spark & MPP clusters
    • Metadata is provided in the open Frictionless Data standard, and its every field is normalized & validated
  • Data Updates
    • Data updates support replace-on-update: outdated foreign keys are deprecated, not deleted

Our data is curated and enriched by domain experts

Each dataset is manually curated by our team of doctors, pharmacists, public health & medical billing experts:

  • Field names, descriptions, and normalized values are chosen by people who actually understand their meaning
  • Healthcare & life science experts add categories, search keywords, descriptions and more to each dataset
  • Both manual and automated data enrichment supported for clinical codes, providers, drugs, and geo-locations
  • The data is always kept up to date – even when the source requires manual effort to get updates
  • Support for data subscribers is provided directly by the domain experts who curated the data sets
  • Every data source’s license is manually verified to allow for royalty-free commercial use and redistribution.

Need Help?


About Us

John Snow Labs , an AI and NLP for healthcare company, provides state-of-the-art software, models, and data to help healthcare and life science organizations build, deploy, and operate AI projects.

Provided By
Fulfillment Method
AWS Data Exchange

Data dictionaries

A data dictionary is a visual representation of the contents of a data set. The data represented here is for evaluation purposes only and may not accurately represent the actual content of the product.

Field name
Description
Example
Data type
Primary key
Nullable
Max length
Data set
Table name
Table description
Year

The year in which the data was submitted

2017

date
-
false
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
Quarter

The quarter of the year in which the data was submitted

Q1

string
-
false
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
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
-
false
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
Case_Id

Number for identifying a FAERS case

-
integer
-
false
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
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
-
false
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
Status_of_Report

Initial or follow-up status of report, as reported by manufacturer

-
string
-
false
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
Event_Date

Date the adverse event occurred or began. If a complete date is not available, a partial date is provided

-
date
-
-
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
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
-
-
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
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
-
-
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017
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
-
-
-
FDA Adverse Events Reporting System Demographics 2017
fda_adverse_events_reporting_system_demographics_2017

Data sets (7)

You will receive access to the following data sets

Revision access rules
All historical revisions | All future revisions
Name
Type
Data dictionary
AWS Region
FDA Adverse Events Reporting System Report Source 2017
Included
US East (N. Virginia)
FDA Adverse Events Reporting System Patient Outcome 2017
Included
US East (N. Virginia)
FDA Adverse Events Reporting System Drug Therapy Dates 2017
Included
US East (N. Virginia)
FDA Adverse Events Reporting System Drug Reaction 2017
Included
US East (N. Virginia)
FDA Adverse Events Reporting System Drug Indication 2017
Included
US East (N. Virginia)
FDA Adverse Events Reporting System Drug 2017
Included
US East (N. Virginia)
FDA Adverse Events Reporting System Demographics 2017
Included
US East (N. Virginia)

Data dictionaries and samples

Sample data is for evaluation purposes only and may not accurately represent the actual content of the product.

Name
Resource
File type
File size
Description
FDA Adverse Events Reporting System Demographics 2017
Data set
-
-
-
Data dictionary
Data dictionary
text/csv
-
FDA Adverse Events Reporting System Drug 2017
Data set
-
-
-
FDA Adverse Events Reporting System Drug Indication 2017
Data set
-
-
-
FDA Adverse Events Reporting System Drug Reaction 2017
Data set
-
-
-
FDA Adverse Events Reporting System Drug Therapy Dates 2017
Data set
-
-
-
FDA Adverse Events Reporting System Patient Outcome 2017
Data set
-
-
-
FDA Adverse Events Reporting System Report Source 2017
Data set
-
-
-

Usage information

By subscribing to this product, you agree that your use of this product is subject to the provider's offer terms including pricing information and Data Subscription Agreement . Your use of AWS services remains subject to the AWS Customer Agreement  or other agreement with AWS governing your use of such services.

Support information

Support contact email address
Refund policy
No refunds offered. For any questions email us at info@johnsnowlabs.com
General AWS Data Exchange support