01
Where it fits—and where it doesn’t
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.
- Do not use it as
- Do not treat MedDRA as a complete solution on its own. MedDRA is licensed, version-sensitive, and multiaxial; a coded term does not establish seriousness, expectedness, relatedness, or causality.
- Best for
- Teams working with Clinical and Regulatory data across Acquire → Harmonize → Exchange → Learn + reuse.
- Maturity
- EstablishedEstablished enough for serious use; still pin the exact release and any implementation profile.
02
See it in the workflow
A standard creates value by changing a handoff, not by existing in a catalog.
- InputWhat starts
Clinical and Regulatory data, metadata, and the local decisions around them
- MedDRAWhat changes
MedDRA applies a shared terminology across Acquire → Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A more consistent, reviewable handoff for the next system or team
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 - Metadata vocabularyDPV
Both support Clinical work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - StandardCDISC ODM
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologyLOINC
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.
Name an 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
Limitation to test first—and the tests that catch it
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.
A structured or machine-readable result can still be unfit for analysis or AI.
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
Why we believe this
Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.
Evidence notation: E1 + E2. The code is shorthand; the plain-language statement above is the claim.
08
Source shelf
Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.
Official MedDRA 29.0 downloads
The canonical publisher or steward source used to verify this terminology profile.
- Publisher
- ICH · MedDRA MSSO
- Rights
- Rights remain with the publisher; this knowledge base links to the source rather than copying it.
- Access
- Opens the publisher's source in a new tab; no external media loads on this page.
- Verified
- 2026-07-13