Adverse Event Reporting in Clinical Trials
By Dr. Zubair Khalid, DVM, MS, PhD ·

Quick Answer
- Adverse event reporting in clinical trials requires classifying each event by severity, expectedness, and relatedness before applying FDA or EMA timelines.
- Report serious and unexpected events to regulators within 7 to 15 calendar days depending on the event type and the governing authority.
- The distinction between a serious adverse event and a suspected unexpected serious adverse reaction determines which form and timeline apply, and misclassification is a common compliance failure.
Understanding Adverse Events in Clinical Trials
Clinical trial safety monitoring depends on a shared vocabulary that sponsors, investigators, institutional review boards, and regulators use to describe what happens to participants during a study. An adverse event is any unfavorable medical occurrence in a participant who received a study intervention, regardless of whether the intervention caused it. This definition includes events that occur during the treatment period and those that emerge after treatment has ended if the protocol requires continued observation.
The practical challenge for clinical research professionals is that adverse events exist on a spectrum. Some are mild and self-limiting. Others are life-threatening or fatal. Some are expected based on the known safety profile of the intervention. Others are completely unexpected. The reporting requirements change depending on where an event falls on these dimensions, and the consequences of misclassification range from protocol deviations to regulatory findings during inspection.
Clinical research coordinators and investigators carry the primary responsibility for capturing adverse event information at the site level. The Occupational Outlook Handbook describes the broader medical scientist and clinical research workforce, noting that these professionals typically need advanced education and specialized training to perform their duties. In practice, the person who first learns about an adverse event is often a study coordinator during a participant phone call or a nurse during a scheduled visit. The accuracy of the entire reporting chain depends on how well that first conversation captures the details of the event.
The O*NET OnLine database catalogs the specific tasks and skills associated with clinical research roles, including documenting patient information, coordinating study activities, and ensuring compliance with protocols. These task descriptions reflect the reality that adverse event reporting is not a single administrative step but a continuous process of observation, documentation, classification, and communication that spans the entire trial.
Core Principles of Adverse Event Classification
Severity Grading
Severity describes the intensity of an event, not its medical significance. A headache can be mild, moderate, or severe. A mild heart attack is still a serious adverse event because it meets the seriousness criteria, even though the clinical presentation might be less intense than a severe headache. Severity grading scales vary by therapeutic area, but most protocols use a four-point scale ranging from mild to life-threatening.
The distinction between severity and seriousness is one of the most common sources of confusion in clinical research. Severity is a measure of intensity. Seriousness is a regulatory classification that triggers specific reporting obligations. An event is serious if it results in death, is life-threatening, requires inpatient hospitalization or prolongation of existing hospitalization, results in persistent or significant disability or incapacity, is a congenital anomaly or birth defect, or requires medical or surgical intervention to prevent one of these outcomes.
Causality Assessment
Causality assessment determines whether the study intervention caused the adverse event. Investigators typically use categories such as definitely related, probably related, possibly related, unlikely related, or unrelated. The assessment considers temporal relationship, biological plausibility, response to withdrawal of the intervention, and whether alternative explanations exist.
The causality assessment matters because it determines whether a serious event becomes a suspected unexpected serious adverse reaction. A serious adverse event that is unexpected and judged to have a reasonable possibility of being caused by the study intervention meets the definition of a suspected unexpected serious adverse reaction, which carries the most urgent reporting requirements.
Expectedness Determination
Expectedness refers to whether an event is listed in the investigator's brochure, the protocol, or the informed consent document. An unexpected event is one whose nature, severity, or frequency is not consistent with the available safety information. The determination of expectedness is not based on the individual investigator's clinical experience but on the documented safety profile of the intervention.
The expectedness determination is particularly challenging for new investigational products with limited human exposure. The investigator's brochure is the reference document for this assessment, and it should be updated as new safety information emerges during the trial. Clinical research professionals should verify that they are using the current version of the investigator's brochure when making expectedness determinations.
Regulatory Frameworks for Adverse Event Reporting
FDA Requirements
The U.S. Food and Drug Administration requires investigators to report serious adverse events to the sponsor and to the institutional review board according to specific timelines. The sponsor is responsible for evaluating the event and submitting expedited reports to the FDA when the event meets the criteria for a suspected unexpected serious adverse reaction.
The FDA distinguishes between fatal or life-threatening suspected unexpected serious adverse reactions and other serious suspected unexpected serious adverse reactions. Fatal or life-threatening events require notification to the FDA within 7 calendar days of the sponsor's initial receipt of the information. The sponsor must follow up with a complete report within 8 additional calendar days. Other serious suspected unexpected serious adverse reactions require reporting within 15 calendar days.
The FDA also requires sponsors to submit annual reports that summarize the safety profile of the investigational product, including a list of all adverse events that occurred during the reporting period. These annual reports provide a cumulative safety picture that complements the expedited individual case safety reports.
EMA Requirements
The European Medicines Agency operates under a similar but distinct framework. The Clinical Trials Regulation requires sponsors to report suspected unexpected serious adverse reactions to the European database within 7 days for fatal or life-threatening events and within 15 days for other events. The EMA also requires a development safety update report on an annual basis.
The EMA framework places additional emphasis on the risk-benefit assessment. Sponsors must continuously evaluate whether emerging safety information changes the balance of risks and benefits for trial participants. This ongoing assessment can lead to protocol amendments, informed consent updates, or suspension of the trial if the risks outweigh the benefits.
Comparison of FDA and EMA Approaches
The FDA and EMA frameworks share the same fundamental structure for expedited reporting of serious unexpected events, but important differences exist in forms, timelines, and documentation requirements. The FDA uses the MedWatch form for voluntary reporting and the FDA 3500A form for mandatory reporting by sponsors. The EMA uses the EudraVigilance system for electronic reporting of suspected unexpected serious adverse reactions.
The most significant practical difference is the reporting pathway. The FDA requires sponsors to submit individual case safety reports through the electronic submission gateway, while the EMA requires submission through EudraVigilance with specific electronic data interchange standards. Clinical research professionals working on global trials must understand which regulatory authority has jurisdiction for each site and ensure that reports are submitted through the correct pathway.
Practical Workflow for Adverse Event Reporting
Step 1: Capture the Event
The reporting process begins when a participant reports a symptom or when a clinical finding emerges during a study visit. The clinical research coordinator should document the event using the participant's own words, then clarify the onset date, resolution date, severity, and any concomitant medications or procedures. The documentation should include the event term, start and stop dates, action taken with the study intervention, and outcome.
The initial capture is the point where data quality is most vulnerable. Participants may not spontaneously report symptoms unless asked systematically. Standardized questionnaires and open-ended questions about changes in health status help ensure that adverse events are not missed. The coordinator should also review vital signs, laboratory results, and physical examination findings for abnormalities that meet the definition of an adverse event.
Step 2: Classify the Event
Once the event is documented, the investigator must classify it according to severity, seriousness, expectedness, and causality. This classification determines the reporting pathway. The investigator should document the rationale for each classification decision in the source documents and the case report form.
The classification step requires clinical judgment and familiarity with the protocol and investigator's brochure. The investigator should consider whether the event meets any of the seriousness criteria, whether the event is listed in the investigator's brochure, and whether there is a reasonable possibility that the study intervention caused the event. When the classification is uncertain, the investigator should consult the sponsor's medical monitor.
Step 3: Apply the Reporting Timeline
The timeline for reporting depends on the classification and the governing regulatory authority. The following table summarizes the key reporting requirements for expedited reports.
| Event Type | FDA Timeline | EMA Timeline | Report Destination |
|---|---|---|---|
| Fatal or life-threatening SUSAR | 7 calendar days with follow-up within 8 additional days | 7 calendar days | FDA, EMA, IRB, sponsor |
| Other serious SUSAR | 15 calendar days | 15 calendar days | FDA, EMA, IRB, sponsor |
| Serious adverse event not unexpected | Per protocol, typically within 24 to 72 hours to sponsor | Per protocol, typically within 24 to 72 hours to sponsor | Sponsor, IRB |
| Nonserious adverse event | Per protocol, typically at scheduled intervals | Per protocol, typically at scheduled intervals | Sponsor, case report form |
The sponsor has additional obligations to notify investigators of suspected unexpected serious adverse reactions that occur at other sites. This cross-notification requirement ensures that all investigators have access to the same safety information when making decisions about participant care.
Step 4: Submit the Report
The submission pathway depends on the regulatory authority and the type of report. The FDA requires electronic submission of individual case safety reports through the electronic submission gateway. The EMA requires submission through EudraVigilance. Sponsors typically manage these submissions centrally, but investigators must submit serious adverse event reports to the sponsor within the protocol-specified timeframe.
The investigator also has obligations to the institutional review board. The IRB must be notified of any unanticipated problems involving risks to participants, which includes serious adverse events that are unexpected and related to the study intervention. The IRB notification timeline is typically specified in the IRB's policies and may differ from the FDA and EMA timelines.
At a Glance: Adverse Event Classification and Reporting
| Classification Question | Assessment | Reporting Consequence |
|---|---|---|
| Is the event serious? | Death, life-threatening, hospitalization, disability, congenital anomaly, or intervention required | Triggers expedited reporting pathway |
| Is the event expected? | Compare to investigator's brochure and protocol | Unexpected events require expedited reporting |
| Is the event related to the intervention? | Causality assessment by investigator | Related events may meet SUSAR definition |
| Is the event a SUSAR? | Serious, unexpected, and related | Requires 7 or 15 day reporting to regulators |
| Is the event fatal or life-threatening? | Meets seriousness criteria and is a SUSAR | Requires 7 day reporting with follow-up |
Records and Documentation Requirements
Source Documentation
Source documents are the original records that support the adverse event information entered into the case report form. These include progress notes, nursing notes, laboratory reports, hospitalization records, and participant diaries. The source documents must contain sufficient detail to support the classification decisions made by the investigator.
The principle of source data verification means that the information in the case report form must match the source documents. Discrepancies between the source and the case report form are a common finding during audits and inspections. Clinical research coordinators should ensure that the source documents include the event term, onset and resolution dates, severity, causality assessment, and any action taken with the study intervention.
Case Report Form Completion
The case report form should be completed in a timely manner after the adverse event is documented. The form typically captures the event term, start and stop dates, severity, seriousness criteria, causality assessment, expectedness, action taken with the study intervention, and outcome. The form should be completed using the protocol-specific coding conventions and medical terminology.
Adverse events are typically coded using a standardized medical dictionary to facilitate analysis across the trial. The coding process maps the investigator's verbatim term to a preferred term in the dictionary. Coding errors can lead to inaccurate safety analyses, so the coding should be reviewed by qualified personnel.
Regulatory Reporting Records
Sponsors must maintain records of all adverse event reports submitted to regulatory authorities. These records include the individual case safety reports, the submission dates, and any follow-up information. The records must be retained according to the applicable regulatory requirements, which typically extend for several years after the trial is completed.
Investigators must also maintain records of adverse event reports submitted to the sponsor and the IRB. These records demonstrate compliance with the reporting requirements and provide a complete picture of the safety events that occurred during the trial.
Common Failure Patterns in Adverse Event Reporting
Misclassification of Seriousness
The most common failure pattern is the misclassification of an event as nonserious when it meets the seriousness criteria. This often occurs with events that require hospitalization. An event that requires hospitalization for treatment is serious even if the hospitalization is brief. Similarly, an event that requires medical intervention to prevent permanent impairment is serious even if the intervention is administered in an outpatient setting.
The failure to recognize seriousness leads to delayed reporting and potential regulatory findings. Clinical research professionals should review the seriousness criteria regularly and consult the sponsor when there is any doubt about the classification.
Delayed Reporting
Delays in reporting can occur at any point in the chain. The participant may delay reporting symptoms to the study team. The coordinator may delay documenting the event. The investigator may delay making the classification decision. The sponsor may delay submitting the expedited report to the regulatory authority.
Each step in the chain has its own timeline, and the cumulative delay can result in a missed regulatory deadline. The 7 and 15 day timelines are measured from the sponsor's initial receipt of the information, not from the date the event occurred. However, delays at the site level reduce the time available for the sponsor to complete the evaluation and submit the report.
Incomplete Causality Assessment
Some investigators are reluctant to attribute adverse events to the study intervention, particularly when the event has a plausible alternative explanation. This reluctance can lead to an underreporting of suspected unexpected serious adverse reactions. The causality assessment should consider the totality of the evidence, including the temporal relationship, the biological plausibility, and the response to rechallenge if applicable.
The sponsor's medical monitor can provide guidance on causality assessment, but the final determination is the responsibility of the investigator. The assessment should be documented in the source documents and the case report form.
Failure to Update Expectedness
The expectedness determination is based on the investigator's brochure, which is updated as new safety information emerges. A failure to use the current version of the investigator's brochure can lead to an incorrect expectedness determination. An event that was unexpected at the start of the trial may become expected after the brochure is updated.
Clinical research professionals should verify that they are using the current version of the investigator's brochure and should review the brochure when it is updated to determine whether any previously reported events need to be reclassified.
Quality Controls and Monitoring
Internal Quality Checks
Clinical research sites should implement internal quality checks to verify the accuracy and completeness of adverse event reporting. These checks include a review of source documents against the case report form, a review of the classification decisions, and a verification that all events have been reported within the required timelines.
The quality check should be performed by someone other than the person who completed the original documentation. A second reviewer can identify errors that the original documenter may have missed. The quality check should be documented and retained as part of the trial records.
Sponsor Oversight
The sponsor is responsible for monitoring the safety of the trial and ensuring that adverse event reporting is compliant with regulatory requirements. The sponsor's clinical research associate typically reviews adverse event documentation during site monitoring visits and verifies that the reporting timelines have been met.
The sponsor also has obligations to review the cumulative safety data and to notify regulatory authorities of any new safety information that affects the risk-benefit assessment. This ongoing safety review is separate from the individual case safety report submission and provides a broader picture of the trial's safety profile.
Data Safety Monitoring
Some trials use a data safety monitoring board to review the accumulating safety data at predefined intervals. The board reviews the adverse event data, the serious adverse event reports, and the overall risk-benefit assessment. The board can recommend that the trial continue as planned, be modified, or be stopped based on the safety findings.
The data safety monitoring board is particularly important for trials involving vulnerable populations or interventions with significant known risks. The board's recommendations are advisory, but the sponsor and the investigators typically follow them to ensure participant safety.
Welfare and Safety Context
The adverse event reporting system exists to protect the welfare of trial participants. The system ensures that serious safety signals are identified quickly and that regulatory authorities have the information they need to make decisions about the continuation of the trial. The reporting requirements are not administrative burdens but essential components of the ethical conduct of clinical research.
The National Institutes of Health Office of Intramural Training and Education emphasizes the importance of rigorous training for research professionals, including training in the ethical conduct of research and the protection of human subjects. Adverse event reporting is a core component of this training because it directly affects participant safety.
The American Society for Microbiology Career Services similarly highlights the importance of professional development and adherence to research standards in the life sciences. Clinical research professionals who understand the adverse event reporting requirements are better equipped to protect participants and to maintain the integrity of the research enterprise.
Professional Escalation Criteria
Clinical research professionals should escalate adverse event reporting issues to the appropriate authority when certain conditions are met. The following criteria indicate that escalation is appropriate:
- The investigator is uncertain about the classification of an event as serious or nonserious.
- The event is unexpected and the investigator is uncertain about the causality assessment.
- The sponsor has not acknowledged receipt of a serious adverse event report within the protocol-specified timeframe.
- The sponsor has not submitted an expedited report to the regulatory authority within the required timeline.
- The investigator's brochure has been updated and the expectedness of previously reported events needs to be reassessed.
- A participant experiences an event that requires unblinding of the treatment assignment to manage the event.
The escalation should be documented and should include the reason for the escalation, the person or entity to whom the issue was escalated, and the outcome of the escalation.
Career Pathways in Clinical Research
Clinical Research Coordinator
The clinical research coordinator is responsible for the day-to-day management of the trial at the site level. This role includes participant recruitment, informed consent, data collection, and adverse event documentation. The coordinator is often the first person to learn about an adverse event and plays a critical role in the reporting chain.
The Occupational Outlook Handbook provides information about the education and training requirements for clinical research roles. Most coordinator positions require a bachelor's degree in a health-related field, and certification is available through professional organizations. The coordinator role provides a foundation for advancement to other positions in clinical research.
Clinical Research Associate
The clinical research associate, also known as a monitor, is responsible for overseeing the conduct of the trial at multiple sites. The associate verifies that the sites are following the protocol, that the data are accurate, and that adverse events are being reported appropriately. The associate serves as a liaison between the sponsor and the sites.
The O*NET OnLine database describes the tasks and skills associated with clinical research monitoring roles, including reviewing data for completeness and accuracy and ensuring compliance with regulatory requirements. The associate role requires strong attention to detail and the ability to communicate effectively with site staff.
Regulatory Affairs Specialist
The regulatory affairs specialist is responsible for preparing and submitting regulatory documents, including adverse event reports. This role requires a thorough understanding of the FDA and EMA reporting requirements and the ability to navigate the electronic submission systems. The specialist works closely with the safety team to ensure that reports are submitted within the required timelines.
The National Science Foundation Careers page provides examples of scientific and administrative roles in federal research organizations, which can include regulatory and compliance positions. The regulatory affairs specialist role offers a career path for professionals who are interested in the regulatory side of clinical research.
Data Safety and Monitoring Roles
Data safety and monitoring roles focus on the analysis of safety data across the trial. These roles include biostatisticians who analyze the adverse event data and safety physicians who review the individual case safety reports. These professionals contribute to the ongoing risk-benefit assessment and to the preparation of safety reports for regulatory authorities.
The Association of American Veterinary Medical Colleges provides information about veterinary career pathways, which can include clinical research in veterinary medicine. Veterinary clinical trials have their own adverse event reporting requirements, and professionals in this field must understand the applicable regulations.
Limitations and Considerations
The adverse event reporting requirements described in this article are based on the general principles of clinical trial safety reporting. Specific requirements may vary based on the phase of the trial, the therapeutic area, the investigational product, and the regulatory authority with jurisdiction. Clinical research professionals should always consult the protocol, the investigator's brochure, and the applicable regulations for the specific requirements that apply to their trial.
The FDA and EMA requirements are not identical, and trials conducted in multiple countries must comply with the requirements of each regulatory authority. The sponsor is responsible for coordinating the reporting across jurisdictions and for ensuring that the most stringent requirements are met.
The classification of adverse events requires clinical judgment, and different investigators may reach different conclusions about the same event. The sponsor's medical monitor can provide guidance, but the final responsibility for the classification rests with the investigator. When there is uncertainty, the conservative approach is to report the event as serious and unexpected.
Frequently Asked Questions
What is the difference between an adverse event and a serious adverse event?
An adverse event is any unfavorable medical occurrence in a participant, regardless of whether the study intervention caused it. A serious adverse event is an adverse event that results in death, is life-threatening, requires inpatient hospitalization or prolongation of existing hospitalization, results in persistent or significant disability or incapacity, is a congenital anomaly or birth defect, or requires medical or surgical intervention to prevent one of these outcomes.
What is a suspected unexpected serious adverse reaction?
A suspected unexpected serious adverse reaction is a serious adverse event that is unexpected based on the investigator's brochure and that has a reasonable possibility of being caused by the study intervention. This classification triggers the most urgent expedited reporting requirements to regulatory authorities.
How long does a sponsor have to report a fatal or life-threatening SUSAR to the FDA?
The sponsor must notify the FDA of a fatal or life-threatening suspected unexpected serious adverse reaction within 7 calendar days of the sponsor's initial receipt of the information. The sponsor must submit a complete report within 8 additional calendar days.
How long does a sponsor have to report a nonfatal SUSAR to the FDA?
The sponsor must report a nonfatal suspected unexpected serious adverse reaction to the FDA within 15 calendar days of the sponsor's initial receipt of the information.
What is the difference between the FDA and EMA reporting timelines?
The FDA and EMA both require reporting of fatal or life-threatening suspected unexpected serious adverse reactions within 7 days and other suspected unexpected serious adverse reactions within 15 days. The differences are in the submission systems, the forms, and the documentation requirements.
Who is responsible for reporting adverse events to the institutional review board?
The investigator is responsible for reporting serious adverse events and unanticipated problems involving risks to participants to the institutional review board. The IRB notification timeline is typically specified in the IRB's policies.
What is the investigator's brochure and why is it important for adverse event reporting?
The investigator's brochure is a document that summarizes the available safety and efficacy information about the investigational product. It is the reference document for determining whether an adverse event is expected or unexpected.
What should a clinical research coordinator do if a participant reports a new symptom?
The coordinator should document the symptom using the participant's own words, then clarify the onset date, severity, and any concomitant medications. The coordinator should notify the investigator, who will classify the event and determine the reporting requirements.
Related Articles
- Clinical Trial Safety Monitoring: Adverse Events and Reporting
- How to Become a Clinical Research Nurse: Roles and Requirements
- Clinical Research Coordinator vs. Clinical Trial Coordinator: What's the Difference?
- Clinical Research Associate vs Clinical Research Coordinator: What's the Difference?
- Clinical Research Career Path: From Assistant to Director
References and Further Reading
- Occupational Outlook Handbook. U.S. Bureau of Labor Statistics.
- O*NET OnLine. U.S. Department of Labor.
- Office of Intramural Training and Education. National Institutes of Health.
- Careers at NSF. U.S. National Science Foundation.
- Career Services. American Society for Microbiology.
- AAVMC Career Resources. Association of American Veterinary Medical Colleges.
- NCBI Literature Resources. National Center for Biotechnology Information.
- PubMed. National Library of Medicine.
This article is educational and does not replace institutional policy, professional advice, or applicable safety and regulatory requirements.