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.
Indicate if the subject experienced any adverse events. If Yes, include the appropriate details where indicated on the CRF. | Were any adverse events experienced? AEYN Not Submitted | <NY codelist> | |
---|---|---|---|
If collected on the CRF, the sponsor may insert instructions to ensure each record has a unique identifier. | AESPID | _______ | |
Record only 1 diagnosis, sign, or symptom per line (e.g., nausea and vomiting should not be recorded in the same entry, but as 2 separate entries). Using accepted medical terminology, enter the diagnosis (if known); otherwise, enter a sign or symptom. | AETERM | _________________ | |
Record the start date of the AE using this format (DD-MON-YYYY). | AESTDAT AESTDTC | _ _ / _ _ _ / _ _ _ _ | |
Indicate if the adverse event has not resolved at the time of data collection; leave the End Date blank. | Is the adverse event ongoing? AEONGO AEENRTPT AEENRF | <NY codelist> | |
Record the date that the AE resolved using this format (DD-MON-YYYY). If the AE is ongoing, leave the field blank. | AEENDAT AEENDTC | _ _ / _ _ _ / _ _ _ _ | |
The reporting physician/healthcare professional will assess the severity of the event using sponsor-defined categories. This assessment is subjective and the reporting physician/ healthcare professional should use medical judgment to compare the reported AE to similar type events observed in clinical practice. Severity is not equivalent to seriousness. | Severity AESEV | <AESEV codelist> | |
Assess if an adverse event should be classified as serious based on the criteria defined in the protocol. | Was the adverse event serious? AESER | <NY codelist> | |
Record whether the serious adverse event resulted in death. | Did the adverse event result in death? AESDTH | <NY codelist> | |
Record the date of death. | DTHDAT DM.DTHDTC | _ _ / _ _ _ / _ _ _ _ | |
Record whether the serious adverse event is life-threatening. | Life Threatening AESLIFE | <NY codelist> | |
Record whether the serious adverse event resulted in an initial or prolonged hospitalization. | Hospitalization (initial or prolonged) AESHOSP | <NY codelist> | |
Record whether the serious adverse event resulted in a persistent or significant disability or incapacity. | Disability or Permanent Damage AESDISAB | <NY codelist> | |
Record whether the serious adverse event was associated with congenital anomaly or birth defect. | Congenital Anomaly or Birth Defect AESCONG | <NY codelist> | |
Record whether the serious adverse event required intervention to prevent permanent impairment or damage due to the use of a medical product. | Needs Intervention to Prevent Impairment AESINTV SUPPAE.QVAL | <NY codelist> | |
Record whether the serious adverse event is an important medical event, which may be defined in the protocol or in the investigator brochure. | Other Serious (Important Medical Events) AESMIE | <NY codelist> | |
Indicate if the cause of the adverse event was related to the study treatment and cannot be reasonably explained by other factors (e.g., subject's clinical state, concomitant therapy, other interventions). | Relationship to Study Treatment AEREL | ||
Record changes made to the study treatment resulting from the adverse event. | Action Taken with Study Treatment AEACN | <ACN codelist> | |
Record the appropriate outcome of the event in relation to the subject's status. | Outcome AEOUT | <OUT codelist> |
Dataset Wrapper Debug Message
Please add a row column to your dataset.
Overview
Content Tools