Why Science? | ICH E2D(R1) Post-Approval Safety Data and Individual Case Reports

The guidance harmonises definitions and standards for managing and reporting individual safety cases after a medicinal product is approved. It addresses spontaneous reports, solicited reports and contemporary data sources while supporting consistent regional pharmacovigilance.

The core discipline in e2d(r1) governs post-approval case management is to preserve source context while acting on time. The guidance harmonises definitions and standards for managing and reporting individual safety cases after a medicinal product is approved. It addresses spontaneous reports, solicited reports and contemporary data sources while supporting consistent regional pharmacovigilance. Keep this boundary visible: National laws and regional rules determine specific reporting obligations and timelines.

A strong science note separates observation from interpretation. Record product, country, approval status, source and applicable rule before processing. 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.

Contents · Next chapter

FDA lists E2D(R1) as final Level 1 guidance dated March 2026 under docket FDA-2024-D-0803, issued by CDER and CBER. It replaces both the March 2024 draft and the September 2003 final guidance.

For the march 2026 guidance is final level 1, a valid case and a proven causal relationship are different conclusions. FDA lists E2D(R1) as final Level 1 guidance dated March 2026 under docket FDA-2024-D-0803, issued by CDER and CBER. It replaces both the March 2024 draft and the September 2003 final guidance. Preserve this guardrail: Legacy procedures should not be assumed current after a superseding final guidance.

A strong science note separates observation from interpretation. Create a controlled implementation record mapping every revised concept to procedure and training. 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.

Contents · Previous chapter · Next chapter

Case validity generally depends on an identifiable reporter, an identifiable patient, a suspected medicinal product and an adverse event or reaction. Identifiable does not require public disclosure of personal details; it means enough information exists to recognise a real reporter and patient.

A defensible decision about a valid icsr needs minimum information records what was known, when it was known and which rule applied. Case validity generally depends on an identifiable reporter, an identifiable patient, a suspected medicinal product and an adverse event or reaction. Identifiable does not require public disclosure of personal details; it means enough information exists to recognise a real reporter and patient. Remember: A partially described case may still require follow-up even before all criteria are met.

A strong science note separates observation from interpretation. Document which minimum criteria are present, their sources and the follow-up plan for missing elements. 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.

Contents · Previous chapter · Next chapter

An adverse event is an untoward occurrence temporally associated with product use, while an adverse reaction reflects at least a suspected causal relationship in the relevant reporting context. Careful wording prevents observation from being presented as proof.

The core discipline in adverse event and adverse reaction are distinct is to preserve source context while acting on time. An adverse event is an untoward occurrence temporally associated with product use, while an adverse reaction reflects at least a suspected causal relationship in the relevant reporting context. Careful wording prevents observation from being presented as proof. Keep this boundary visible: Reporter attribution and company assessment can differ and both may need preservation.

A strong science note separates observation from interpretation. Separate verbatim facts, reporter causality and company causality in the case record. 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.

Contents · Previous chapter · Next chapter

A spontaneous communication is made voluntarily by a healthcare professional, consumer or other person and is not derived from an organised data-collection system. Reports on company-controlled websites can remain spontaneous when people post them without a structured collection activity.

For spontaneous reports arise without organised solicitation, a valid case and a proven causal relationship are different conclusions. A spontaneous communication is made voluntarily by a healthcare professional, consumer or other person and is not derived from an organised data-collection system. Reports on company-controlled websites can remain spontaneous when people post them without a structured collection activity. Preserve this guardrail: The digital location alone does not determine source classification.

A strong science note separates observation from interpretation. Describe what prompted the report and whether the company asked structured safety questions. 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.

Contents · Previous chapter · Next chapter

Clinical studies, registries, patient support programmes, market research and other organised data collection systems can generate solicited reports. Their handling depends on the system’s design and documented causality approach.

A defensible decision about solicited reports come from organised systems records what was known, when it was known and which rule applied. Clinical studies, registries, patient support programmes, market research and other organised data collection systems can generate solicited reports. Their handling depends on the system’s design and documented causality approach. Remember: A programme label is insufficient; the actual collection method determines classification.

A strong science note separates observation from interpretation. Attach the programme protocol or data-collection description to the case-source decision. 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.

Contents · Previous chapter · Next chapter

Companies need procedures for safety information on digital platforms under their responsibility. E2D(R1) distinguishes unsolicited posts from organised digital data collection and ties review and reporting to access, minimum criteria and source context.

The core discipline in digital platforms require defined responsibilities is to preserve source context while acting on time. Companies need procedures for safety information on digital platforms under their responsibility. E2D(R1) distinguishes unsolicited posts from organised digital data collection and ties review and reporting to access, minimum criteria and source context. Keep this boundary visible: Teams are not expected to treat the entire internet as a company-controlled safety inbox.

A strong science note separates observation from interpretation. Create an inventory of owned, sponsored and monitored platforms with review frequency and escalation paths. 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.

Contents · Previous chapter · Next chapter

The regulatory clock begins when the marketing authorisation holder or a third party acting for it has sufficient information to determine that minimum reporting criteria are met. For accessed digital data, day zero may differ from the date the content was created or first accessed.

For day zero starts when reportability can be recognised, a valid case and a proven causal relationship are different conclusions. The regulatory clock begins when the marketing authorisation holder or a third party acting for it has sufficient information to determine that minimum reporting criteria are met. For accessed digital data, day zero may differ from the date the content was created or first accessed. Preserve this guardrail: Delaying internal routing does not reset the clock.

A strong science note separates observation from interpretation. Capture receipt, access, recognition and escalation timestamps with responsible persons. 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.

Contents · Previous chapter · Next chapter

Death, immediate life threat, hospitalisation or prolongation, significant disability, congenital anomaly and other medically important conditions can make a case serious. Severity describes intensity and should not be confused with seriousness.

A defensible decision about seriousness follows outcomes and medical importance records what was known, when it was known and which rule applied. Death, immediate life threat, hospitalisation or prolongation, significant disability, congenital anomaly and other medically important conditions can make a case serious. Severity describes intensity and should not be confused with seriousness. Remember: A severe symptom may be non-serious, and a modest symptom may be serious because of its outcome.

A strong science note separates observation from interpretation. Map each case independently to seriousness criteria and intensity. 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.

Contents · Previous chapter · Next chapter

Expectedness compares the reported reaction with the appropriate product information under the applicable regional framework. Greater specificity or severity can make known information meaningfully different.

The core discipline in expectedness uses the relevant reference is to preserve source context while acting on time. Expectedness compares the reported reaction with the appropriate product information under the applicable regional framework. Greater specificity or severity can make known information meaningfully different. Keep this boundary visible: Expectedness is a regulatory comparison, not a prediction about what clinicians should have anticipated.

A strong science note separates observation from interpretation. Record the reference document, version, effective date and exact comparison. 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.

Contents · Previous chapter · Next chapter

Pregnancy, breastfeeding, overdose, misuse, abuse, medication error, occupational exposure and lack of efficacy can require collection and evaluation even when no adverse event is initially described. Follow-up should be proportionate to possible clinical importance.

For special situations may carry safety information, a valid case and a proven causal relationship are different conclusions. Pregnancy, breastfeeding, overdose, misuse, abuse, medication error, occupational exposure and lack of efficacy can require collection and evaluation even when no adverse event is initially described. Follow-up should be proportionate to possible clinical importance. Preserve this guardrail: A special situation is not automatically an adverse reaction or reportable case in every region.

A strong science note separates observation from interpretation. Use a decision tree that preserves the situation while checking regional reporting rules. 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.

Contents · Previous chapter · Next chapter

Published scientific and medical literature can contain reportable cases or relevant safety information. Search strategy, frequency, product attribution, duplicate checking and article access determine whether cases are recognised consistently.

A defensible decision about literature surveillance needs reproducible methods records what was known, when it was known and which rule applied. Published scientific and medical literature can contain reportable cases or relevant safety information. Search strategy, frequency, product attribution, duplicate checking and article access determine whether cases are recognised consistently. Remember: A citation alone may not provide the minimum information needed for a valid ICSR.

A strong science note separates observation from interpretation. Keep search strings, dates, review decisions, full-text status and case links. 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.

Contents · Previous chapter · Next chapter

The same event may be reported by a patient, clinician, programme and regulator. Demographics, dates, product, event and narrative clues support duplicate detection while privacy protections constrain matching.

The core discipline in duplicates can distort the safety picture is to preserve source context while acting on time. The same event may be reported by a patient, clinician, programme and regulator. Demographics, dates, product, event and narrative clues support duplicate detection while privacy protections constrain matching. Keep this boundary visible: Over-aggressive merging can combine different people; missed duplicates can inflate apparent frequency.

A strong science note separates observation from interpretation. Document match variables, uncertainty and the retained case hierarchy. 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.

Contents · Previous chapter · Next chapter

Reasonable follow-up seeks outcome, diagnosis, timing, exposure, tests, treatment and confounders. Priority should reflect seriousness, novelty, preventability and the value of missing information rather than a mechanical request for every field.

For follow-up should improve clinically important gaps, a valid case and a proven causal relationship are different conclusions. Reasonable follow-up seeks outcome, diagnosis, timing, exposure, tests, treatment and confounders. Priority should reflect seriousness, novelty, preventability and the value of missing information rather than a mechanical request for every field. Preserve this guardrail: Repeated contact can burden reporters and should respect consent and local requirements.

A strong science note separates observation from interpretation. Rank questions by decision value and record each attempt and response. 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.

Contents · Previous chapter · Next chapter

Case processing needs enough traceability to validate information and manage duplicates while limiting personal data to what is necessary. Access controls, secure transfer and retention rules protect reporters and patients.

A defensible decision about privacy and verification must work together records what was known, when it was known and which rule applied. Case processing needs enough traceability to validate information and manage duplicates while limiting personal data to what is necessary. Access controls, secure transfer and retention rules protect reporters and patients. Remember: De-identification should not erase information needed for legitimate safety obligations without a reasoned process.

A strong science note separates observation from interpretation. Map every personal-data element to purpose, access, retention and protection. 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.

Contents · Previous chapter · Next chapter

Patient-support providers, market-research agencies and digital service vendors may receive safety information on behalf of a company. Agreements, training, intake channels, clock-start rules, reconciliation and oversight should make responsibilities clear.

The core discipline in quality systems keep vendors and programmes aligned is to preserve source context while acting on time. Patient-support providers, market-research agencies and digital service vendors may receive safety information on behalf of a company. Agreements, training, intake channels, clock-start rules, reconciliation and oversight should make responsibilities clear. Keep this boundary visible: Contracting work out does not remove the authorisation holder’s accountability.

A strong science note separates observation from interpretation. Test each partner with a sample case from receipt through submission and reconciliation. 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.

Contents · Previous chapter · Next chapter

The receipt records source type, minimum criteria, dates, clock start, seriousness, expectedness, causality views, special situations, duplicates, follow-up, privacy controls, reporting decision and acknowledgement. It shows how raw contact became a managed case.

For a complete e2d(r1) receipt makes the decision reproducible, a valid case and a proven causal relationship are different conclusions. The receipt records source type, minimum criteria, dates, clock start, seriousness, expectedness, causality views, special situations, duplicates, follow-up, privacy controls, reporting decision and acknowledgement. It shows how raw contact became a managed case. Preserve this guardrail: Documentation supports consistent judgment but does not turn uncertain causality into fact.

A strong science note separates observation from interpretation. Give the receipt to a second reviewer and ask whether they reach the same 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.

Contents · Previous chapter