ZANE ProEd
PharmacovigilanceStatus: PUBLISHED // Data_Point_icsr

ICSR Case Processing Steps: Workflow and Worked Example

November 17, 2026 8 min read ZANE ProEd Drug Safety Intelligence Desk
Reviewed by: Dr. Mohammed Anas, Pharm.D
ICSR Case Processing Steps: Workflow and Worked Example

The icsr case processing steps below follow the workflow used by marketing authorisation holders (MAHs) and national competent authorities (NCAs) in the EU. A worked example runs through each stage so you can see which decision is made, by whom, and what it changes downstream. The same logic applies in the US, UK, Canada, the Middle East and India, although local rules on clocks and databases differ.

What are the steps of ICSR case processing?

The process starts when an MAH or NCA receives a report of a suspected adverse reaction. The receipt date matters because it sets the clock: the start point (D0) for a valid ICSR is the date the report was received [1].

Recommended_Programs

Build These Skills Now

Programs from ZANE ProEd Academy that directly address the skill gaps discussed above.

Browse all pharmacovigilance courses →
  1. Receipt. The report arrives from a patient, health professional, literature source or partner. Log the receipt date and source.
  2. Create and record the ICSR. Create the individual case safety report and record it in the pharmacovigilance database [1].
  3. Validity check. Confirm the report meets the minimum criteria. If it does not, it is not processed as an ICSR and the workflow ends at that point [1].
  4. Triage. Determine seriousness, expectedness against the reference safety information, and whether the case is expedited or non-expedited for each region.
  5. Follow-up. If significant information is missing, such as patient age or group, a valid follow-up request is sent to the reporter [1].
  6. Data entry. Enter the case into the safety database and populate the E2B(R3) data elements [2].
  7. Coding. Code reported terms to MedDRA and check that the coded terms match the narrative.
  8. Quality control and submission. A second reviewer checks the case, then the ICSR is submitted to the regulator or partner database within the applicable time frame.
  9. Storage and maintenance. The case remains in the database for signal detection and data quality analysis. Follow-up, amendment or nullification is handled when new information arrives [1].

Worked example: a rash after a new antibiotic

Case W-001: a 58-year-old woman starts drug Y. Nine days later she develops a widespread rash and fever and is admitted to hospital. A pharmacist emails the report to the company on Day 0 and gives the patient's initials, age, drug name, start date, event and hospital admission.

At step 2 the case processor creates the record and assigns a sender's unique case identifier. At step 3 the processor checks that a patient, a suspect drug, an event and a reporter are all identifiable, so the report is a valid ICSR. The clock starts on Day 0.

At step 4 the processor marks the case as serious because of hospitalisation. The processor then compares the term with the reference safety information. If the rash is not listed, the case is unexpected, which affects the expedited reporting category. At step 5 the processor notes that the batch number and the concomitant medicines are missing, and sends a follow-up request. Steps 6 to 8 follow the table below.

What are the four minimum criteria for a valid ICSR?

A report becomes a valid ICSR only when it contains the minimum information needed to be assessed. The four minimum criteria are commonly described as an identifiable patient, an identifiable reporter, a suspect medicinal product and a suspected adverse reaction. These are the elements a processor checks at the validity step.

The consequences of a missing element are shown by the nullification scenarios in EMA guidance. A case is nullified when the patient did not receive the suspect drug, when the reaction did not occur, or when no patient was involved, because the minimum criteria are then no longer met [1]. The same logic applies at intake: if one of the four elements can never be obtained, the report is not a valid ICSR.

If a case passes the check but later loses an element, it is handled as a nullification rather than silently removed. Record the reason in the database so the audit trail shows why the case was closed.

What happens at triage, data entry, coding and QC?

Triage decides how the case will be handled. It records seriousness, expectedness, causality if assessed at intake, and the regional reporting category. Triage is also where duplicates are checked, because a second report about the same patient may need to be linked rather than processed again.

Data entry transfers the information into the safety database and into the E2B(R3) structure. The E2B(R3) data elements include the sender's case safety report unique identifier, the worldwide unique case identification number, the date the report was first received from the source and the date of the most recent information [2]. These fields are what the regulator uses to link versions of the same case.

When an existing ICSR needs correcting, the same sender's unique identifier and worldwide unique case identifier should be reused for an amendment. A report that has been nullified and must be submitted again needs new identifiers [2]. Mixing these up is a common data quality error.

StageMain purposeTypical checks
TriageClassify seriousness, expectedness and reporting categorySeriousness criteria, reference safety information, duplicate search
Data entryPopulate the database and E2B(R3) fieldsDates, identifiers, drug names, mandatory fields
CodingMap reported terms to MedDRAPreferred term matches the narrative, lowest-level term accuracy
Quality controlSecond check before submissionConsistency across fields, narrative and coding, correct timeline

Coding and data entry are often done in an Argus or similar safety database. For practical guidance on case entry screens and fields, see the Oracle Argus Safety Database guide.

What are expedited reporting timelines (7/15/90 days)?

Expedited reporting is the fastest category and sets the clock for serious, unexpected reactions. For ICSRs that meet the expedited criteria, the report is due as soon as possible and not later than 15 calendar days after day zero [3]. Day zero is generally the date the MAH receives the information, unless regional rules say otherwise [3].

The 90-day time frame is a separate category. EMA guidance states that the initial valid ICSR is submitted to EudraVigilance within the relevant time frame of 15 or 90 days, as applicable [1]. The passage does not map the 90 days to a single case type, so check the regional rule for each case rather than assuming a category.

Some regions set a shorter clock, commonly 7 calendar days for fatal or life-threatening cases. That requirement is not covered by the sources used for this article, so confirm it against the local regulation before setting a due date.

TimelineWhere it appliesSource
Up to 15 calendar daysExpedited ICSRs meeting regional criteria, measured from day zero[3]
15 or 90 days, as applicableInitial valid ICSR submission to EudraVigilance, depending on case type and region[1]
Shorter clock (commonly 7 days)Certain fatal or life-threatening cases under some local rulesConfirm locally
Non-expeditedReportable non-serious cases that do not meet expedited criteria, subject to regional rules[3]

A follow-up restarts the clock. When additional medically relevant information arrives for a previously reported case, the reporting clock begins again for the follow-up, with day zero set to the date the MAH receives that information [3]. In the worked example, the hospital discharge summary received later starts a new clock for the follow-up report.

Key takeaways

  • The icsr case processing steps run from receipt, through validity, triage, data entry, coding and quality control, to submission and maintenance.
  • Day zero is the receipt date of a valid report, and it sets the reporting clock [1].
  • A valid ICSR needs an identifiable patient, reporter, suspect drug and suspected reaction; losing one of these leads to nullification [1].
  • Reuse identifiers for amendments and issue new identifiers for a re-submitted nullified case [2].
  • Expedited ICSRs are generally due within 15 calendar days of day zero, and follow-up information restarts the clock [3].

How can I practise icsr case processing steps hands-on?

Reading the workflow is different from working a case through it under time pressure. The ZANE ProEd ICSR Case Processing & Triage Certification is a 7-9 day intermediate course that takes you through intake, validity assessment, seriousness and expectedness, MedDRA coding, E2B(R3) entry and 7-day and 15-day expedited workflows in a simulated Argus and ARISg environment.

If you are preparing for a first role, the Pharmacovigilance Case Processing Jobs Freshers: Complete Industry Workflow Roadmap places these steps within the wider career path.

Frequently asked questions

Does a follow-up report need a new case identifier?

No. An amendment or follow-up keeps the same sender's case safety report unique identifier and worldwide unique case identification number so the regulator can link the versions [2]. Only a nullified case that is re-submitted needs new identifiers [2].

What is the difference between a nullification and an amendment?

A nullification declares a previously transmitted ICSR void, for example when the case was found to be erroneous or the minimum criteria are no longer met [1][2]. An amendment corrects items such as seriousness, adverse event terms or causality, while the case remains valid [2].

Should every case be coded before it is triaged?

Triage normally comes first because it decides the reporting category and deadline. Coding follows once the reported terms are confirmed, and the QC step checks that the MedDRA terms still match the narrative.

Are non-serious cases always reported within 15 days?

Not necessarily. Non-serious reactions that are reportable as ICSRs may follow non-expedited timelines that vary by regional or local requirement [3]. Check the rule for each region before setting a due date.

Sources

  1. EMA Good Pharmacovigilance Practices (GVP) Module VI: Collection, management and submission of reports of suspected adverse reactions (Rev 2). EMA.
  2. ICH E2B(R3): Electronic Transmission of Individual Case Safety Reports (ICSRs): Data Elements and Message Specification (R3). ICH.
  3. ICH E2D(R1): Post-Approval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports (R1, Step 4 (2025)). ICH.
Recommended_Programs

Build These Skills Now

Programs from ZANE ProEd Academy that directly address the skill gaps discussed above.

Browse all pharmacovigilance courses →

Follow Zane ProEd on Google

Preferred Source

Add our publication as a preferred source to get the latest clinical research guides, industry updates, and career intel directly in your Google Top Stories & AI Overviews.

Add on Google