Decision support

Compare standards by the job they do

Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.

Working set

Choose profiles

1 of 3 selected

WHODrugTerminology

Add a profile

Decision lens

Compare roles before choosing an implementation.

The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”

Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
Test the boundary
Read what each option leaves unresolved before judging maturity or implementation fit.

Assessment

Review lifecycle coverage and practical fit.

Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.

01 · Lifecycle reach

Where each profile contributes directly

Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.

Readiness-stage coverage for WHODrug Global
Profile	Plan	Acquire	Harmonize	Exchange	Learn + reuse
WHODrugTerminology	WHODrug Global has no direct role recorded in Plan.	WHODrug Global has a direct role in Acquire.	WHODrug Global has a direct role in Harmonize.	WHODrug Global has a direct role in Exchange.	WHODrug Global has a direct role in Learn + reuse.

Direct role recordedNo direct role recorded

02 · Boundaries

What each option does not cover

These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.

WHODrug

Stage boundary: No direct role is recorded for Plan.
Known limitation: 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.

03 · Detailed assessment

Check the fit and source behind the map

Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.

Detailed comparison of WHODrug Global
Assessment	WHODrugWHODrug Global
Purpose & coverage	Medicinal-product names, ingredients, countries, marketing authorization holders, strengths, ATC classifications, and drug groupings for medication coding. Best fitConcomitant medication, prior therapy, exposure, and pharmacovigilance drug coding across global clinical programs.
Readiness stages	AcquireHarmonizeExchangeLearn + reuse
AI-ready contribution	Standardized product identity improves exposure features, but automated coding confidence, country context, dose, route, timing, and indication must remain explicit.
First limitation to test	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.
Maturity	Established Maintained biannual medicinal-product terminology; dictionary access requires a subscription
Sources & links	UMC What’s New in WHODrug · March 2026 (opens in a new tab)Read full profile