Pharmacovigilance Reference Tool · ICSR · E2B(R3)
ICSR Case Processing Guide
A practical workflow reference and interactive checklist for validating, processing, quality-checking, and preparing individual case safety reports for E2B(R3) submission readiness.
Quick Answer
ICSR case processing moves an individual case safety report from intake through regulatory submission. A valid case requires four minimum criteria: identifiable patient, identifiable reporter, suspect product, and adverse event. Workflow steps include triage, duplicate check, MedDRA coding to PT level, seriousness and causality assessment, narrative drafting, QC, and E2B(R3) transmission. Serious cases may trigger 7- or 15-day expedited clocks depending on jurisdiction. This interactive checklist supports workflow review—not a substitute for sponsor SOPs.
Interactive workflow check
ICSR completeness checklist
Mark the minimum validity criteria and workflow stages that have been completed. The summary updates with missing items and overall readiness.
Checklist summary
Workflow completeness
0 of 12 items complete
Missing items
- Identifiable patient
- Identifiable reporter
- Suspect product
- Adverse event
- Intake logged
- Triage completed
- Duplicate check completed
- MedDRA coding reviewed
- Seriousness, expectedness, and causality assessed
- Case narrative drafted
- Quality control completed
- Submission readiness confirmed
Workflow map
From intake to submission
ICSR case processing turns source information into a validated, coded, medically reviewed, and submission-ready safety report.
- Intake Capture the first awareness date, receipt channel, source documents, reporter information, patient descriptors, suspect product, adverse event terms, and local-country context.
- Triage Confirm validity, seriousness indicators, special situations, expedited reporting potential, and whether the clock has started.
- Duplicate check Compare patient, reporter, product, event, dates, and country against prior cases before case creation or submission.
- MedDRA coding Code verbatim event terms accurately to current MedDRA terminology, preserving clinical meaning and documenting coding rationale where needed.
- Assessment Document seriousness, expectedness or listedness, causality, dechallenge/rechallenge, outcome, and medically significant considerations.
- Narrative Write a concise chronological account that reconciles key dates, product exposure, event course, treatment, outcome, and assessment rationale.
- Quality control Verify source consistency, coding, dates, seriousness criteria, expectedness source, causality, narrative alignment, and submission clock.
- Submission Prepare the E2B(R3) message or partner package, confirm routing and regional requirements, and retain the audit trail.
E2B(R3) context
Why structured case data matters
ICH E2B(R3) defines the electronic structure used to transmit ICSRs between companies, regulators, and partners. Case processors should think beyond narrative completion: each key fact must be represented in the correct structured field, with controlled terminology and traceable source support.
A submission-ready case usually needs clean receipt dates, patient age or age group where known, reporter qualification, product role, dose and therapy dates when available, coded reactions, seriousness criteria, outcome, causality, and sender/receiver identifiers.
Narrative and QC
Narrative review tips
Strong narratives are factual, chronological, and proportionate. They should not over-interpret limited reports, omit contradictory source details, or hide uncertainty. When information is unknown, say so plainly if it matters to medical interpretation or reporting obligations.
- Open with patient context, suspect product exposure, event onset, and reporting source.
- Keep dates internally consistent with structured fields and source documents.
- Separate reporter opinion, investigator causality, and company medical assessment where they differ.
- Include dechallenge, rechallenge, treatment, outcome, relevant labs, and diagnostic findings when available.
Common pitfalls
Errors that slow submission
- Invalid case creation: one of the four minimum ICSR criteria is missing or not actually identifiable.
- Clock confusion: receipt date, awareness date, and follow-up date are mixed without rationale.
- Coding drift: MedDRA terms imply diagnosis, severity, or causality not present in the source.
- Assessment mismatch: seriousness criteria, expectedness source, or causality is inconsistent between fields and narrative.
- QC late discovery: duplicate or follow-up data issues are found only after submission preparation.
Primary references
Public guidance sources
Use current primary guidance for regulatory decisions. This page summarizes workflow concepts and does not replace regional reporting rules or sponsor SOPs.
Competitive landscape: CCRPS case processing guide and PharmaRegulatory.in ICSR workflow describe intake-to-submission stages in article format without an interactive 12-step checklist or integrated seriousness, causality, MedDRA, and signal-detection hub links. Enterprise safety databases (Argus, ArisGlobal) embed workflows behind commercial licenses. NovaPharmaNews provides a free interactive completeness checklist with E2B(R3) context and pharmacovigilance tool cross-links—not a replacement for sponsor SOPs or database validation.
FAQ
ICSR case processing questions
What are the four minimum criteria for a valid ICSR?
The usual minimum criteria are an identifiable patient, an identifiable reporter, a suspect product, and an adverse event or suspected adverse reaction. Local rules and company procedures may add extra intake or validation requirements.
Where does E2B(R3) fit into case processing?
E2B(R3) is the ICH electronic message standard used to structure and transmit individual case safety reports. Case processing teams map validated case data into E2B fields before regulatory or partner submission.
When should duplicate checks happen in an ICSR workflow?
Duplicate checks should happen early during intake or triage and again before submission if meaningful follow-up information arrives. Checks usually compare patient, reporter, product, event, country, and date details.
What should a pharmacovigilance case narrative include?
A case narrative should summarize the relevant facts in chronological order: patient background, product exposure, event onset and course, treatment, outcome, lab or diagnostic support, dechallenge or rechallenge, and the assessment rationale.
What are common ICSR quality control errors?
Common errors include missing minimum criteria, mismatched dates, unsupported seriousness criteria, inconsistent MedDRA coding, narrative contradictions, unclear expectedness source, and submission-clock errors.
What is Day 0 for expedited reporting clocks?
Day 0 is typically the date the sponsor or marketing authorization holder first becomes aware of the case meeting minimum criteria—not necessarily the event onset date. Follow-up that changes seriousness or causality may restart or adjust clocks per local rules and SOPs.
How does MedDRA coding fit in case processing?
Verbatim reporter terms are coded to Lowest Level Terms (LLTs) in licensed MedDRA tools, rolling up to Preferred Terms (PTs) for analysis and E2B transmission. Coding should preserve clinical meaning without upgrading or downgrading the source. See the MedDRA Lookup Guide for hierarchy context.
What safety databases are used for ICSR processing?
Enterprise PV systems such as Argus, ArisGlobal LifeSphere, Veeva Vault Safety, and Oracle Safety are common for case intake, workflow, MedDRA coding, and E2B generation. This public guide describes workflow concepts independent of any single vendor platform.
When is follow-up required during case processing?
Follow-up is needed when minimum criteria are incomplete, seriousness is unclear, product or dose details are missing, or medical review requires additional clinical information. Document follow-up attempts and responses in the case audit trail.
How do seriousness and expectedness differ from causality?
Seriousness applies ICH E2A criteria at the event level. Expectedness compares the event to the reference safety information (RSI) for clinical trials or labeling for marketed products. Causality is the relatedness judgment for the suspect product—often using WHO-UMC categories at case level.
What E2B(R3) fields require special QC attention?
Receipt dates, sender case identifiers, patient age or age group, reporter qualification, product role and therapy dates, coded reactions, seriousness flags, outcomes, and causality assessments must reconcile between structured fields, narrative, and source documents before XML validation.
How does case processing connect to signal detection and aggregate reporting?
Clean, consistently coded ICSRs feed disproportionality screening and PSUR/PBRER/DSUR tables. Cases after the aggregate data lock point roll to the next reporting interval. Link case-level work to Signal Detection, Aggregate Reporting, and SUSAR Assessment tools in the pharmacovigilance hub.