Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The AE domain includes clinical data describing "any untoward medical occurrence in a patient or clinical investigation subject administered a pharmaceutical product and which does not necessarily have to have a causal relationship with this treatment" (ICH E2A). In consultation with regulatory authorities, sponsors may extend or limit the scope of adverse event collection (e.g., collecting pre-treatment events related to trial conduct, not collecting events that are assessed as efficacy endpoints). Events included in the AE domain should be consistent with protocol requirements. Adverse event terms may be captured either as free text or via a prespecified list of terms.

Panel

Outstanding Issues 

  • The standard SDTM uses the term study treatment for several variables ( AEREL, AEACN. Should this be changes to study product (or another term).  

This is an example of a CRF used to collect all adverse experiences that occurred after informed consent is obtained. Adverse experiences were collect using free-text. 

...

This SDTM dataset illustrates data collected on the example AE CRF above,  AEs were coded using MedDRA, and the sponsor’s applicant’s procedures include the possibility of modifying the reported term to aid in coding. The CRF was structured so that seriousness category variables (e.g., AESDTH, AESHOSP) were checked only when AESER is answered “Y.” In this study, the study reference period started at the start of study treatmentproduct exposure. Three AEs were reported for this subject. This SDTM dataset used AEENRF to represent ongoing events. Expected variables (e.g., AELLT, AELLTCD, AEPT, AEPTCD, AEHLT, AEHLTCD, AEHLGT, AEHLCTCD, AEBDSYCD, AESOC, AESOCCD) are not included to save space.  

The applicant also collected information about whether the event was associated with a device. These subjects did not have any device-related issues. See Section 3.3.3.4, Tobacco Product Events and Malfunctions, for an example of device-related events.  

Dataset wrap
Rowcaps
Rows 1-2:

Show examples of modifying the reported term for coding purposes, with the modified term in AEMODIFY. These adverse events were not serious, so the seriousness criteria variables are null. Note that for the event in row 2, AESTDY = "1". Day 1 was the day

treatment

product was started; the AE start and end times, as well as dates, were collected to allow comparison of the AE timing to the start of

treatment

product.

Row 3:Shows an example of the overall seriousness question AESER answered with "Y" and the relevant corresponding seriousness category variables (AESHOSP and AESLIFE) answered "Y". The other seriousness category variables are left blank. This row also shows AEENRF being populated because the AE was marked as “Continuing” as of the end of the study reference period for the subject (see Section 4.4.7, Use of Relative Timing Variables).
Dataset2
RowSTUDYIDDOMAINSPDEVIDUSUBJIDAESEQAETERMAEMODIFYAEDECODAEBODSYSAESEVAESERAEACNAEACNDEVAERELAERLDEVAEOUTAESCONGAESDISABAESDTHAESHOSPAESLIFEAESMIEAECONTRTEPOCHAESTDTCAEENDTCAESTDYAEENDYAEENRF
1ABC123AE123101
ABC123-00011POUNDING HEADACHEHEADACHEHeadacheNervous system disordersSEVERENNOT APPLICABLE
DEFINITELY NOT RELATED
RECOVERED/RESOLVEDSCREENING





YPRODUCT EXPOSURE20062005-10-121420052006-10-1218-12-15
2ABC123AE123101
ABC123-00012BACK PAIN FOR 6 HOURSBACK PAINBack painMusculoskeletal and connective tissue disordersMODERATENDOSE REDUCED
PROBABLY RELATED
RECOVERED/RESOLVED





NTREATMENTPRODUCT EXPOSURE20052006-10-13T13:0520052006-10-13T19:0011
3ABC123AE1231013PULMONARY EMBOLISMPulmonary embolismVascular disordersMODERATEY
ABC123-00021INFLUENZAInfluenzaInfluenzaInfections and infestationsSEVEREYPRODUCT WITHDRAWNDOSE REDUCED
PROBABLY NOT RELATED
RECOVERING/RESOLVING


YY
YTREATMENTPRODUCT EXPOSURE20052006-1002-2126
912
AFTER