ICSRMedWatchEudraVigilanceSAEPharmacovigilance

ICSR processing: a practical guide for small pharma sponsors

October 22, 2025·9 min read·Nimble PV

A small biotech enrolls its first Phase 1 patient. Three weeks later, the investigator calls: the patient was hospitalised overnight with elevated liver enzymes. What happens next is ICSR processing — and if your sponsor organisation does not have a clear, documented process for it, you are at risk of missing a regulatory deadline that could trigger an FDA clinical hold or EMA suspension of your clinical trial authorisation.

What is an ICSR?

An Individual Case Safety Report is a structured record of a single adverse event or adverse drug reaction. The minimum dataset required for a valid ICSR — per ICH E2B(R3) — is four elements: an identifiable reporter, an identifiable patient, a suspect product, and a suspected adverse event. Without all four, you cannot process it as a valid case, though you should still document the contact.

ICSRs come from multiple sources: investigators and study sites (clinical trial cases), healthcare professionals and patients (spontaneous reports), published literature, and regulatory authority databases. Each source has different handling requirements.

The seriousness and expectedness assessment

Every ICSR must be assessed for seriousness (does it meet ICH E2A seriousness criteria: death, life-threatening, hospitalisation, disability, congenital anomaly, or medically important?) and expectedness (is the reaction listed in the Investigator Brochure or, for marketed products, the Summary of Product Characteristics at the observed specificity and severity?).

These two assessments drive the reporting timeline. An adverse event that is both serious and unexpected — a SUSAR — triggers expedited reporting. A serious expected event does not require expedited reporting but must be collected and included in aggregate reports.

Causality assessment — whether the event is related to the investigational product — is also required and must be assessed by both the investigator and the sponsor independently per ICH E2A.

Reporting timelines

For clinical trial SUSARs:

  • Fatal or life-threatening SUSARs: 7 calendar days from the day of initial receipt (FDA: 21 CFR 312.32; EMA: GVP Module VI)
  • All other SUSARs: 15 calendar days from the day of initial receipt
  • Follow-up reports: 15 calendar days from receipt of follow-up information that changes the seriousness or expectedness assessment

For post-approval spontaneous reports to EudraVigilance: serious reports within 15 calendar days; non-serious within 90 calendar days.

Submission channels

In the US, ICSRs are submitted to FDA via the MedWatch 3500A form electronically through the FDA Safety Reporting Portal (for IND cases) or via E2B(R3) gateway for post-approval ICSRs to FAERS. In the EU, clinical trial SUSARs go to the EudraVigilance Clinical Trials Module (EVCTM) via the CTIS portal under EU CTR 536/2014. Post-approval ICSRs go to EudraVigilance via EVWEB or a compatible E2B(R3) gateway.

A small Phase 1 sponsor with one compound in one country may have fewer than 10 ICSRs per year. But the processing infrastructure — trained staff, documented SOPs, a safety database or structured tracking system, quality review — must be in place before the first case arrives.

Nimble PV handles end-to-end ICSR processing for clinical and post-approval programs. Talk to Vera at nimblepv.com.

Need help with your PV program?

Nimble PV provides fractional VP Drug Safety, ICSR processing, PSMF setup, and full PV system implementation for early-stage pharma and biotech. Onboard in 5–10 days, no setup fee.

Talk to Vera at nimblepv.com →