01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Clinical-trial safety coding, individual case safety reports, aggregate safety analyses, and regulatory pharmacovigilance exchange.
- Limits
- MedDRA is licensed, version-sensitive, and multiaxial; a coded term 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
- MedDRAWhat changes
Use MedDRA as a pinned terminology 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 coding team preserves the verbatim event, assigns an LLT under a frozen MedDRA version, derives higher levels, and documents coding review and up-version impact.
Why it matters: The hierarchy supports safety aggregation and signal features, but automated coding requires human validation and cannot substitute for clinical causality assessment.
04
What it fits with
Used with ICH E2B(R3), CDISC adverse-event data, Standardised MedDRA Queries, and the separately released SNOMED CT–MedDRA map package.
- 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 - StandardICH E2B(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 - 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 MedDRA must support.
Pin the exact version and companion artifacts: 29.0 · Production release 2026-03-01.
Map one representative input to the required terminology 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
MedDRA is licensed, version-sensitive, and multiaxial; a coded term does not establish seriousness, expectedness, relatedness, or causality.
Run one representative end-to-end pilot and record exactly where MedDRA 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. The hierarchy supports safety aggregation and signal features, but automated coding requires human validation and cannot substitute for clinical causality assessment.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
Official MedDRA 29.0 downloads
Official publisher or steward guidance for this terminology profile.
- Publisher
- ICH · MedDRA MSSO