eduKateSG · Why Science?
Use shared definitions and fast reporting so an important new safety signal reaches decision-makers in time
Read FDA’s final March 1995 ICH E2A guidance through adverse events, adverse reactions, seriousness, severity, expectedness, causality, minimum case criteria, seven- and fifteen-day reports and follow-up.
When something harmful happens during a clinical trial, the first scientific task is careful language. Was it simply observed after treatment, is there a reasonable possibility the medicine contributed, is the outcome serious, and was it already expected?
FDA’s final March 1995 ICH E2A guidance harmonises core safety definitions and standards for expedited reporting during clinical development. Shared terms help sponsors, investigators and regulators recognise important new information without treating every symptom as the same kind of evidence.
Did you know? “Serious” and “severe” are not synonyms. Severe describes intensity; serious is based on outcomes or actions such as death, danger to life, hospitalisation, disability, congenital anomaly or another medically important event.
For students, E2A is classification with consequences. A precise definition changes the reporting route and clock, while a disciplined case record lets another reviewer understand the evidence without guessing.
Chapter index
Chapters 1–9: AE, ADR, unexpectedness, seriousness, severity and medical importance
- 1. An adverse event does not require causality
- 2. The March 1995 E2A guidance is final
- 3. An adverse drug reaction includes suspected causality
- 4. Unexpectedness is judged against reference information
- 5. Seriousness follows outcomes and medical significance
- 6. Severity describes intensity, not reporting category
- 7. Life-threatening refers to actual immediate risk
- 8. Medical importance can make an event serious
- 9. Expedited reporting focuses on serious unexpected ADRs
Chapters 10–17: causality, minimum criteria, reporting timelines, follow-up and safety action
- 10. Causality should reflect evidence and alternatives
- 11. Fatal or life-threatening cases use a seven-day clock
- 12. Other qualifying serious unexpected ADRs use fifteen days
- 13. Minimum information supports an initial report
- 14. Follow-up turns an alert into a useful case
- 15. Blinding needs a safety-aware procedure
- 16. Other observations may require rapid communication
- 17. A complete E2A receipt makes the decision traceable
E2A defines an adverse event as an untoward medical occurrence in someone given a pharmaceutical product, whether or not it is considered related. It can be a sign, symptom, disease or abnormal laboratory finding temporally associated with treatment.
The strength of an adverse event does not require causality begins with naming the observation accurately. E2A defines an adverse event as an untoward medical occurrence in someone given a pharmaceutical product, whether or not it is considered related. It can be a sign, symptom, disease or abnormal laboratory finding temporally associated with treatment. Keep this boundary visible: Timing after treatment is not proof that the medicine caused the event.
Try this
Classify a case for an adverse event does not require causality. Write an observation-only description before adding any causal interpretation. Separate observation, seriousness, expectedness and causality. Keep this limit: Timing after treatment is not proof that the medicine caused the event.
A strong science note separates observation from interpretation. Write an observation-only description before adding any causal interpretation. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Write an observation-only description before adding any causal interpretation. Keep this boundary visible: Timing after treatment is not proof that the medicine caused the event.
FDA identifies E2A as final guidance dated March 1995 under docket FDA-1993-D-0128 and issued by CDER. It harmonises collection, evaluation and rapid communication of important clinical-development safety information.
For the march 1995 e2a guidance is final, classification is a route to action rather than paperwork. FDA identifies E2A as final guidance dated March 1995 under docket FDA-1993-D-0128 and issued by CDER. It harmonises collection, evaluation and rapid communication of important clinical-development safety information. Preserve this guardrail: Current national or regional reporting rules may add requirements beyond the harmonised principles.
Try this
Build the reporting clock for the march 1995 e2a guidance is final. Create a source receipt with title, status, date, docket, office, purpose and applicable jurisdiction. Mark day zero, deadline and follow-up. Respect this boundary: Current national or regional reporting rules may add requirements beyond the harmonised principles.
A strong science note separates observation from interpretation. Create a source receipt with title, status, date, docket, office, purpose and applicable jurisdiction. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Create a source receipt with title, status, date, docket, office, purpose and applicable jurisdiction. Keep this boundary visible: Current national or regional reporting rules may add requirements beyond the harmonised principles.
CHAPTER 3 OF 17 · Name the event
3. An adverse drug reaction includes suspected causality
In preapproval development, an adverse drug reaction is a noxious and unintended response for which a causal relationship is at least a reasonable possibility and cannot be ruled out. This separates observed events from suspected medicine-related responses.
A fast safety report about an adverse drug reaction includes suspected causality can be preliminary and still be scientifically honest. In preapproval development, an adverse drug reaction is a noxious and unintended response for which a causal relationship is at least a reasonable possibility and cannot be ruled out. This separates observed events from suspected medicine-related responses. Remember: A suspicion threshold supports reporting; it does not establish proven causation.
Try this
Create a case receipt for an adverse drug reaction includes suspected causality. List evidence for and against a causal relationship without collapsing uncertainty into yes or no. Ask a second reviewer to reproduce the decision. Preserve this caution: A suspicion threshold supports reporting; it does not establish proven causation.
A strong science note separates observation from interpretation. List evidence for and against a causal relationship without collapsing uncertainty into yes or no. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
List evidence for and against a causal relationship without collapsing uncertainty into yes or no. Keep this boundary visible: A suspicion threshold supports reporting; it does not establish proven causation.
CHAPTER 4 OF 17 · Name the event
4. Unexpectedness is judged against reference information
An unexpected adverse reaction has a nature or severity not consistent with applicable product information, such as the Investigator’s Brochure for an unapproved medicine. Known reactions that are substantially more specific or severe can also add unexpected information.
The strength of unexpectedness is judged against reference information begins with naming the observation accurately. An unexpected adverse reaction has a nature or severity not consistent with applicable product information, such as the Investigator’s Brochure for an unapproved medicine. Known reactions that are substantially more specific or severe can also add unexpected information. Keep this boundary visible: Unexpected does not mean unforeseeable in ordinary language; it is a comparison with the designated reference.
Try this
Classify a case for unexpectedness is judged against reference information. Quote the relevant reference concept, then show exactly how the case differs. Separate observation, seriousness, expectedness and causality. Keep this limit: Unexpected does not mean unforeseeable in ordinary language; it is a comparison with the designated reference.
A strong science note separates observation from interpretation. Quote the relevant reference concept, then show exactly how the case differs. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Quote the relevant reference concept, then show exactly how the case differs. Keep this boundary visible: Unexpected does not mean unforeseeable in ordinary language; it is a comparison with the designated reference.
CHAPTER 5 OF 17 · Classify the case
5. Seriousness follows outcomes and medical significance
A serious event or reaction results in death, is life-threatening at the time, requires or prolongs inpatient hospitalisation, causes persistent or significant disability or incapacity, or is a congenital anomaly or birth defect. Medical judgment also identifies other important events that may require intervention to prevent such outcomes.
For seriousness follows outcomes and medical significance, classification is a route to action rather than paperwork. A serious event or reaction results in death, is life-threatening at the time, requires or prolongs inpatient hospitalisation, causes persistent or significant disability or incapacity, or is a congenital anomaly or birth defect. Medical judgment also identifies other important events that may require intervention to prevent such outcomes. Preserve this guardrail: A serious classification depends on the actual case and relevant judgment, not merely an alarming diagnosis label.
Try this
Build the reporting clock for seriousness follows outcomes and medical significance. Map the case to each seriousness criterion and document the evidence supporting the selected one. Mark day zero, deadline and follow-up. Respect this boundary: A serious classification depends on the actual case and relevant judgment, not merely an alarming diagnosis label.
A strong science note separates observation from interpretation. Map the case to each seriousness criterion and document the evidence supporting the selected one. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Map the case to each seriousness criterion and document the evidence supporting the selected one. Keep this boundary visible: A serious classification depends on the actual case and relevant judgment, not merely an alarming diagnosis label.
CHAPTER 6 OF 17 · Classify the case
6. Severity describes intensity, not reporting category
An event may be mild, moderate or severe in intensity without meeting a serious outcome criterion. A severe headache can be non-serious; a modest symptom can prompt hospitalisation and be serious. Keeping the concepts separate prevents over- and under-reporting.
A fast safety report about severity describes intensity, not reporting category can be preliminary and still be scientifically honest. An event may be mild, moderate or severe in intensity without meeting a serious outcome criterion. A severe headache can be non-serious; a modest symptom can prompt hospitalisation and be serious. Keeping the concepts separate prevents over- and under-reporting. Remember: Intensity scales do not replace the seriousness assessment.
Try this
Create a case receipt for severity describes intensity, not reporting category. Classify three example events independently for severity and seriousness. Ask a second reviewer to reproduce the decision. Preserve this caution: Intensity scales do not replace the seriousness assessment.
A strong science note separates observation from interpretation. Classify three example events independently for severity and seriousness. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Classify three example events independently for severity and seriousness. Keep this boundary visible: Intensity scales do not replace the seriousness assessment.
CHAPTER 7 OF 17 · Classify the case
7. Life-threatening refers to actual immediate risk
E2A clarifies that life-threatening means the patient was at risk of death at the time of the event. It does not mean an event that could hypothetically have caused death if it had been more severe.
The strength of life-threatening refers to actual immediate risk begins with naming the observation accurately. E2A clarifies that life-threatening means the patient was at risk of death at the time of the event. It does not mean an event that could hypothetically have caused death if it had been more severe. Keep this boundary visible: Speculation about a worse counterfactual should not substitute for the documented clinical state.
Try this
Classify a case for life-threatening refers to actual immediate risk. Record vital signs, interventions and clinician judgment supporting or rejecting immediate risk. Separate observation, seriousness, expectedness and causality. Keep this limit: Speculation about a worse counterfactual should not substitute for the documented clinical state.
A strong science note separates observation from interpretation. Record vital signs, interventions and clinician judgment supporting or rejecting immediate risk. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Record vital signs, interventions and clinician judgment supporting or rejecting immediate risk. Keep this boundary visible: Speculation about a worse counterfactual should not substitute for the documented clinical state.
Some events may not initially cause death, hospitalisation or disability but can jeopardise the patient or require intervention to prevent a serious outcome. Examples depend on medical judgment and context, including certain laboratory abnormalities, dependency or urgent treatment.
For medical importance can make an event serious, classification is a route to action rather than paperwork. Some events may not initially cause death, hospitalisation or disability but can jeopardise the patient or require intervention to prevent a serious outcome. Examples depend on medical judgment and context, including certain laboratory abnormalities, dependency or urgent treatment. Preserve this guardrail: Medical importance should be reasoned and documented rather than used as an automatic catch-all.
Try this
Build the reporting clock for medical importance can make an event serious. Write the plausible prevented outcome and the intervention that made the event medically important. Mark day zero, deadline and follow-up. Respect this boundary: Medical importance should be reasoned and documented rather than used as an automatic catch-all.
A strong science note separates observation from interpretation. Write the plausible prevented outcome and the intervention that made the event medically important. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Write the plausible prevented outcome and the intervention that made the event medically important. Keep this boundary visible: Medical importance should be reasoned and documented rather than used as an automatic catch-all.
CHAPTER 9 OF 17 · Meet the clock
9. Expedited reporting focuses on serious unexpected ADRs
Single cases that are both serious and unexpected and have a reasonable suspected causal relationship generally qualify for expedited reporting during development. These dimensions should be assessed separately before the reporting decision.
A fast safety report about expedited reporting focuses on serious unexpected adrs can be preliminary and still be scientifically honest. Single cases that are both serious and unexpected and have a reasonable suspected causal relationship generally qualify for expedited reporting during development. These dimensions should be assessed separately before the reporting decision. Remember: An expedited case report is an alert for prompt evaluation, not a final proof of the medicine’s risk.
Try this
Create a case receipt for expedited reporting focuses on serious unexpected adrs. Use a three-column serious-unexpected-related decision card for each case. Ask a second reviewer to reproduce the decision. Preserve this caution: An expedited case report is an alert for prompt evaluation, not a final proof of the medicine’s risk.
A strong science note separates observation from interpretation. Use a three-column serious-unexpected-related decision card for each case. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Use a three-column serious-unexpected-related decision card for each case. Keep this boundary visible: An expedited case report is an alert for prompt evaluation, not a final proof of the medicine’s risk.
CHAPTER 10 OF 17 · Meet the clock
10. Causality should reflect evidence and alternatives
Temporal relationship, dechallenge, rechallenge, biological plausibility, dose response, concomitant treatment and competing illness can inform whether a reasonable causal relationship exists. Investigators and sponsors may differ, and both assessments can be relevant.
The strength of causality should reflect evidence and alternatives begins with naming the observation accurately. Temporal relationship, dechallenge, rechallenge, biological plausibility, dose response, concomitant treatment and competing illness can inform whether a reasonable causal relationship exists. Investigators and sponsors may differ, and both assessments can be relevant. Keep this boundary visible: A missing alternative explanation does not by itself prove causation.
Try this
Classify a case for causality should reflect evidence and alternatives. Build a causality timeline and list the strongest drug and non-drug explanations. Separate observation, seriousness, expectedness and causality. Keep this limit: A missing alternative explanation does not by itself prove causation.
A strong science note separates observation from interpretation. Build a causality timeline and list the strongest drug and non-drug explanations. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Build a causality timeline and list the strongest drug and non-drug explanations. Keep this boundary visible: A missing alternative explanation does not by itself prove causation.
CHAPTER 11 OF 17 · Meet the clock
11. Fatal or life-threatening cases use a seven-day clock
Qualifying fatal or life-threatening serious unexpected adverse reactions should be reported as soon as possible and no later than seven calendar days after the sponsor first knows the case qualifies. A report as complete as possible follows within eight additional calendar days.
For fatal or life-threatening cases use a seven-day clock, classification is a route to action rather than paperwork. Qualifying fatal or life-threatening serious unexpected adverse reactions should be reported as soon as possible and no later than seven calendar days after the sponsor first knows the case qualifies. A report as complete as possible follows within eight additional calendar days. Preserve this guardrail: The clock does not wait for perfect information or final causality certainty.
Try this
Build the reporting clock for fatal or life-threatening cases use a seven-day clock. Mark awareness, qualification, initial report and follow-up deadlines on a calendar. Mark day zero, deadline and follow-up. Respect this boundary: The clock does not wait for perfect information or final causality certainty.
A strong science note separates observation from interpretation. Mark awareness, qualification, initial report and follow-up deadlines on a calendar. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Mark awareness, qualification, initial report and follow-up deadlines on a calendar. Keep this boundary visible: The clock does not wait for perfect information or final causality certainty.
CHAPTER 12 OF 17 · Meet the clock
12. Other qualifying serious unexpected ADRs use fifteen days
Serious unexpected adverse reactions that are not fatal or life-threatening should be filed as soon as possible and no later than fifteen calendar days after first knowledge that the minimum reporting criteria are met.
A fast safety report about other qualifying serious unexpected adrs use fifteen days can be preliminary and still be scientifically honest. Serious unexpected adverse reactions that are not fatal or life-threatening should be filed as soon as possible and no later than fifteen calendar days after first knowledge that the minimum reporting criteria are met. Remember: Fifteen days is an outer limit, not a reason to delay a ready report.
Try this
Create a case receipt for other qualifying serious unexpected adrs use fifteen days. Create an intake workflow that identifies day zero and escalates approaching deadlines. Ask a second reviewer to reproduce the decision. Preserve this caution: Fifteen days is an outer limit, not a reason to delay a ready report.
A strong science note separates observation from interpretation. Create an intake workflow that identifies day zero and escalates approaching deadlines. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Create an intake workflow that identifies day zero and escalates approaching deadlines. Keep this boundary visible: Fifteen days is an outer limit, not a reason to delay a ready report.
CHAPTER 13 OF 17 · Improve the evidence
13. Minimum information supports an initial report
E2A lists an identifiable patient, identifiable reporting source, suspect medicinal product and identifiable serious unexpected event or outcome with a reasonable suspected causal relationship for clinical-investigation cases as minimum information. Missing details should be actively pursued.
The strength of minimum information supports an initial report begins with naming the observation accurately. E2A lists an identifiable patient, identifiable reporting source, suspect medicinal product and identifiable serious unexpected event or outcome with a reasonable suspected causal relationship for clinical-investigation cases as minimum information. Missing details should be actively pursued. Keep this boundary visible: Anonymous rumours or cases without an identifiable event cannot be evaluated as valid expedited reports.
Try this
Classify a case for minimum information supports an initial report. Check each minimum field and open a dated follow-up request for every missing detail. Separate observation, seriousness, expectedness and causality. Keep this limit: Anonymous rumours or cases without an identifiable event cannot be evaluated as valid expedited reports.
A strong science note separates observation from interpretation. Check each minimum field and open a dated follow-up request for every missing detail. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Check each minimum field and open a dated follow-up request for every missing detail. Keep this boundary visible: Anonymous rumours or cases without an identifiable event cannot be evaluated as valid expedited reports.
CHAPTER 14 OF 17 · Improve the evidence
14. Follow-up turns an alert into a useful case
Initial reports may lack hospital records, laboratory values, diagnoses, outcome or exposure detail. Sponsors should seek relevant information and submit significant follow-up promptly. Version control should connect updates so reviewers do not count one person as several cases.
For follow-up turns an alert into a useful case, classification is a route to action rather than paperwork. Initial reports may lack hospital records, laboratory values, diagnoses, outcome or exposure detail. Sponsors should seek relevant information and submit significant follow-up promptly. Version control should connect updates so reviewers do not count one person as several cases. Preserve this guardrail: A rapid initial report does not remove the duty to investigate and correct the record.
Try this
Build the reporting clock for follow-up turns an alert into a useful case. Build a follow-up checklist and record source, request date, receipt date and change to interpretation. Mark day zero, deadline and follow-up. Respect this boundary: A rapid initial report does not remove the duty to investigate and correct the record.
A strong science note separates observation from interpretation. Build a follow-up checklist and record source, request date, receipt date and change to interpretation. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Build a follow-up checklist and record source, request date, receipt date and change to interpretation. Keep this boundary visible: A rapid initial report does not remove the duty to investigate and correct the record.
When treatment assignment affects whether a case qualifies or how it is evaluated, unblinding may be needed for safety reporting. The process should protect trial integrity as far as possible while ensuring regulators and investigators receive necessary information.
A fast safety report about blinding needs a safety-aware procedure can be preliminary and still be scientifically honest. When treatment assignment affects whether a case qualifies or how it is evaluated, unblinding may be needed for safety reporting. The process should protect trial integrity as far as possible while ensuring regulators and investigators receive necessary information. Remember: Preserving blinding never overrides urgent participant protection or required reporting.
Try this
Create a case receipt for blinding needs a safety-aware procedure. Define who may unblind, for what trigger, how access is limited and how the action is documented. Ask a second reviewer to reproduce the decision. Preserve this caution: Preserving blinding never overrides urgent participant protection or required reporting.
A strong science note separates observation from interpretation. Define who may unblind, for what trigger, how access is limited and how the action is documented. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Define who may unblind, for what trigger, how access is limited and how the action is documented. Keep this boundary visible: Preserving blinding never overrides urgent participant protection or required reporting.
CHAPTER 16 OF 17 · Improve the evidence
16. Other observations may require rapid communication
E2A recognises that findings beyond a single qualifying case can demand prompt attention, such as a clinically important increase in a known serious reaction, a major hazard from animal data or a lack of efficacy in a life-threatening disease.
The strength of other observations may require rapid communication begins with naming the observation accurately. E2A recognises that findings beyond a single qualifying case can demand prompt attention, such as a clinically important increase in a known serious reaction, a major hazard from animal data or a lack of efficacy in a life-threatening disease. Keep this boundary visible: A formal case category should not become a barrier to communicating an urgent emerging risk.
Try this
Classify a case for other observations may require rapid communication. Create escalation criteria for patterns and non-case findings that could change trial conduct. Separate observation, seriousness, expectedness and causality. Keep this limit: A formal case category should not become a barrier to communicating an urgent emerging risk.
A strong science note separates observation from interpretation. Create escalation criteria for patterns and non-case findings that could change trial conduct. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Create escalation criteria for patterns and non-case findings that could change trial conduct. Keep this boundary visible: A formal case category should not become a barrier to communicating an urgent emerging risk.
CHAPTER 17 OF 17 · Improve the evidence
17. A complete E2A receipt makes the decision traceable
The receipt records patient and reporter identifiers, suspect product, event narrative, dates, dose, seriousness criterion, severity, expectedness reference, causality evidence, concomitant factors, outcome, reporting clock, recipients, unblinding, follow-up and version history. It reveals why and when the case moved.
For a complete e2a receipt makes the decision traceable, classification is a route to action rather than paperwork. The receipt records patient and reporter identifiers, suspect product, event narrative, dates, dose, seriousness criterion, severity, expectedness reference, causality evidence, concomitant factors, outcome, reporting clock, recipients, unblinding, follow-up and version history. It reveals why and when the case moved. Preserve this guardrail: A complete report improves evaluation but cannot by itself establish population-level incidence or causation.
Try this
Build the reporting clock for a complete e2a receipt makes the decision traceable. Give the receipt to an independent reviewer and ask them to reproduce the classification and deadline. Mark day zero, deadline and follow-up. Respect this boundary: A complete report improves evaluation but cannot by itself establish population-level incidence or causation.
A strong science note separates observation from interpretation. Give the receipt to an independent reviewer and ask them to reproduce the classification and deadline. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Give the receipt to an independent reviewer and ask them to reproduce the classification and deadline. Keep this boundary visible: A complete report improves evaluation but cannot by itself establish population-level incidence or causation.
E2A expedited safety-report map
| Question | Evidence to capture | Boundary to retain |
|---|---|---|
| What happened? | Event, dates, clinical course and outcome | Observation does not prove causality |
| Does it qualify? | Seriousness, expectedness and reasonable causal relationship | Serious is different from severe |
| When must it move? | Seven- or fifteen-day clock and initial report | Do not wait for a perfect file |
| How does it improve? | Follow-up, unblinding, versioning and action | One case does not estimate incidence |
Science learning becomes useful when a student can show where a claim came from, why it applies and where it stops. Continue with the eduKate Science Learning Hub, compare choices in the Education Hub, and connect these habits to career pathways built from subject capabilities.
E2A makes speed and precision partners. Shared definitions help teams send the most important new safety information quickly, while careful follow-up turns an early alert into evidence that can protect participants and improve the whole development programme.
Primary sources and verification date
Source status checked 26 October 2026. FDA guidance describes the agency’s current thinking and does not replace applicable statutes, regulations or product-specific communication with FDA.
- FDA: ICH E2A Clinical Safety Data Management — Final guidance, March 1995; docket FDA-1993-D-0128.
- FDA: Full ICH E2A guidance PDF — Official definitions, minimum criteria and expedited reporting timelines.
- FDA: Sponsor Responsibilities — Safety Reporting Requirements — Final guidance, December 2025; current U.S. IND and BA/BE reporting context.
