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
01
USDMReference architecture
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?”
01
Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
02
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
03
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 CDISC Unified Study Definitions Model
No direct role is recorded for Acquire, Harmonize, Learn + reuse.
Known limitation
USDM is a model and reference architecture. It is not an EDC, submission dataset, or proof that generated documents comply with every regulator. Every linked terminology and API version must be pinned.
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 CDISC Unified Study Definitions Model
A computable study definition spanning objectives, endpoints, eligibility, interventions, schedule of activities, amendments, estimands, and protocol content.
Best fitUpstream protocol facts that must flow consistently into study-build, registry, document, and downstream data systems.
Readiness stages
PlanExchange
AI-ready contribution
Structured protocol intent is valuable for agents and automation, but generated study assets still require conformance checks and accountable clinical review.
First limitation to test
USDM is a model and reference architecture. It is not an EDC, submission dataset, or proof that generated documents comply with every regulator. Every linked terminology and API version must be pinned.
Maturity
Scaling
Released model, implementation guide, APIs, terminology, and conformance-rule specifications; adoption is still scaling