01
Where it fits—and where it doesn’t
Use these four checks before committing implementation time.
- Use it when
- Concomitant medication, prior therapy, exposure, and pharmacovigilance drug coding across global clinical programs.
- Do not use it as
- Do not treat WHODrug as a complete solution on its own. Dictionary data require a subscription, ambiguous product names still need expert review, B3/C3 choices affect granularity, and up-versioning can change records and classifications.
- 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
- WHODrugWhat changes
WHODrug 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 study codes verbatim medication names to a frozen WHODrug release and format while retaining the original text, selected record, ATC choice, and reviewer decision.
Why it matters: Standardized product identity improves exposure features, but automated coding confidence, country context, dose, route, timing, and indication must remain explicit.
04
What it fits with
The March 2026 release adds IDMP-linked data and mappings; ATC supports aggregation; B3 and C3 expose different product granularity.
- 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 - 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 WHODrug must support.
Pin the exact version and companion artifacts: March 2026 release · B3 and C3 · 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
Dictionary data require a subscription, ambiguous product names still need expert review, B3/C3 choices affect granularity, and up-versioning can change records and classifications.
Run one representative end-to-end pilot and record exactly where WHODrug 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. Standardized product identity improves exposure features, but automated coding confidence, country context, dose, route, timing, and indication must remain explicit.
07
Why we believe this
Checked against the canonical source plus implementation or adoption evidence reported by the steward or its community.
Evidence notation: E1 + E3. 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.
UMC What’s New in WHODrug · March 2026
The canonical publisher or steward source used to verify this terminology profile.
- Publisher
- Uppsala Monitoring Centre
- 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