01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Pre- and post-market adverse-event case intake, follow-up, exchange, regulatory reporting, reconciliation, and downstream safety surveillance.
- Limits
- Adoption and business rules remain regional, and some authorities still accept or require E2B(R2) for selected product classes. A valid message does not establish seriousness, expectedness, relatedness, or causality.
- Best for
- Clinical and Regulatory teams working across Acquire → Harmonize → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Clinical and Regulatory source data, metadata, and local mappings
- ICH E2B(R3)What changes
Use ICH E2B(R3) as a pinned standard across Acquire → Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A safety system converts a validated case into an E2B(R3) message, preserves sender and worldwide case identifiers, applies the target regulator's business rules, receives an acknowledgement, and reconciles transmission status.
Why it matters: Structured cases support signal detection and case triage, but duplicate detection, missingness, narrative context, coding quality, exposure denominators, and clinical causality remain separate controls.
04
What it fits with
Uses MedDRA for medical concepts and product-event coding workflows, WHODrug or regional product dictionaries for medicinal-product coding, and the ISO/HL7 ICSR message standard as its technical basis.
- TerminologyMedDRA
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologyWHODrug
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Governance frameworkICH E6(R3)
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata vocabularyDPV
Both support Clinical work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision ICH E2B(R3) must support.
Pin the exact version and companion artifacts: ICSR Implementation Guide 5.03 · 2025-07-18.
Map one representative input to the required standard artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
Adoption and business rules remain regional, and some authorities still accept or require E2B(R2) for selected product classes. A valid message does not establish seriousness, expectedness, relatedness, or causality.
Run one representative end-to-end pilot and record exactly where ICH E2B(R3) loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Structured cases support signal detection and case triage, but duplicate detection, missingness, narrative context, coding quality, exposure denominators, and clinical causality remain separate controls.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
ICH E2B(R3) ICSR specification and files
Official publisher or steward guidance for this standard profile.
- Publisher
- ICH E2B(R3) EWG/IWG