_dta: 1. by Jean Roth , jroth@nber.org , 26 Mar 2015 2. DRUGyyQq.TXT contains drug/biologic information for as many medications 3. as were reported for the event (1 or more per event). primaryid: 1. Unique number for identifying a FAERS report. 2. This is the primary link field (primary key) between data files (example: 31234561). 3. This is a concatenated key of Case ID and Case Version Number. 4. It is the Identifier for the case sequence (version) number as reported by the manufacturer. drug_seq: 1. Unique number for identifying a drug for a Case 2. To link to the THERyyQq.TXT data file, both the Case number (primary key) 3. and the DRUG_SEQ number (secondary key) are needed. 4. (For an explanation of the DRUG_SEQ number, including an example, please see Section E, End Note 2, below.) 5. DRUG_SEQ (Drug file, Therapy file, and Indications file). 6. The best way to explain the DRUG_SEQ (drug sequence number) is with an example. 7. This will also clarify the relationship between a Case, the drug(s) reported for that Case, 8. and the therapy date(s) reported for the drug(s). 9. Consider Case 3078140 version 1, received by the FDA on 12/31/97. 10. The PRIMARYID for this case is 30781401. 11. Like any Case, it appears once (and only once) in the Demographic file: 12. PRIMARYID 13. --- 14. 30781401 15. Four drugs were reported for this Case: Aricept was reported as suspect, and Estrogens, Prozac, and Synthroid as concomitant. 16. Primaryid 30781401 appears four times in the Drug file, with a different DRUG_SEQ for each drug: 17. PRIMARYID DRUG_SEQ DRUGNAME 18. --- -------- -------- 19. 30781401 1 Aricept 20. 30781401 2 Estrogens 21. 30781401 3 Prozac( Fluoxetine Hydrochloride 22. 30781401 4 Synthroid (Levothyroxine Sodium) 23. Dates of therapy for Aricept were reported as "4/97 to 6/13/97", and "6/20/97 (ongoing)." 24. Since the drug was started, stopped, then restarted, there are two entries in the Drug Therapy file. 25. In such a circumstance, the two entries will have the same PRIMARYID and the same DRUG_SEQ # 26. (or DSG_DRUG_SEQ # as it is called in the Therapy file - see below). 27. No therapy dates were reported for the concomitants; therefore, 28. they do not appear in the Drug Therapy file, which is excerpted as follows: 29. PRIMARYID DSG_DRUG_SEQ # START_DT END_DT 30. --- ---------- -------- ------ 31. 30781401 1 199704 19970613 32. 30781401 1 19970620 33. NOTE: The Drug Seq # is no longer a unique key as was the case in LAERS QDE. 34. The Drug Seq # simply shows the order of the DRUGNAME within a unique case. 35. Additionally, the fields labeled DRUG_SEQ, INDI_DRUG_SEQ, and DSG_DRUG_SEQ in the Drug, 36. Indication, and Therapy files, respectively, all serve the same purpose 37. of linking the data elements in each individual file together 38. with the appropriate drug listed in the case using the PRIMARYID. role_cod: 1. Code for drug's reported role in event.(See table below.) 2. CODE MEANING_TEXT 3. ---- ------------ 4. PS Primary Suspect Drug 5. SS Secondary Suspect Drug 6. C Concomitant 7. I Interacting drugname: 1. Name of medicinal product. 2. If a "Valid Trade Name" is populated for this Case, then DRUGNAME = Valid Trade Name; 3. if not, then DRUGNAME = "Verbatim" name, exactly as entered on the report. 4. For the great majority of reports, there is a "Valid Trade Name." val_vbm: 1. Code for source of DRUGNAME.(See table below.) 2. CODE MEANING_TEXT 3. ---- ------------ 4. 1 Validated trade name used 5. 2 Verbatim name used route: 1. The route of drug administration. dose_vbm: 1. Verbatim text for dose, frequency, and route, exactly as entered on report dechal: 1. Dechallenge code, indicating if reaction abated when drug therapy was stopped. (See table below.) 2. CODE MEANING_TEXT 3. ---- ------------ 4. Y Positive dechallenge 5. N Negative dechallenge 6. U Unknown 7. D Does not apply rechal: 1. Rechallenge code, indicating if reaction recurred when drug therapy was restarted. (See table below.) 2. CODE MEANING_TEXT 3. ---- ------------ 4. Y Positive rechallenge 5. N Negative rechallenge 6. U Unknown 7. D Does not apply lot_num: 1. Lot number of the drug. exp_dt: 1. Expiration date of the drug. (YYYYMMDD format) 2. If a complete date is not available, a partial date is provided, 3. See the NOTE on dates at the end of this section. exp_dt_num: 1. Expiration date of the drug. (YYYYMMDD) 2. YYYY-onlys are converted to midpoint of year: YYYY0702 3. YYYYMM-onlys are converted to midpoint of month: YYYYMM15 nda_num: 1. NDA number (numeric only) obs: 235,878 vars: 13 26 Mar 2015 16:20 size: 60,856,524 (_dta has notes) ------------------------------------------------------------------------------------------------------------------------------------- storage display value variable name type format label variable label ------------------------------------------------------------------------------------------------------------------------------------- primaryid long %12.0g * Unique number for identifying a FAERS report drug_seq long %12.0g * Unique number for identifying a drug for a Case role_cod str2 %9s * Code for drug's reported role in event drugname str70 %70s * Name of medicinal product val_vbm byte %8.0g * Code for source of DRUGNAME route str28 %28s * The route of drug administration dose_vbm str100 %100s * Verbatim text for dose, frequency, and route, exactly as entered on report dechal str1 %9s * Dechallenge code, indicating if reaction abated when drug therapy was stopped rechal str1 %9s * Rechallenge code, indicating if reaction recurred when drug therapy restarted lot_num str35 %35s * Lot number of the drug exp_dt long %12.0g * Expiration date of the drug. (YYYYMMDD format) exp_dt_num float %td * Expiration date of the drug. (YYYYMMDD) nda_num long %12.0g * NDA number (numeric only) * indicated variables have notes ------------------------------------------------------------------------------------------------------------------------------------- Sorted by: primaryid drug_seq