Decision support

Compare standards by the job they do

Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.

Working set

Choose profiles

1 of 3 selected

USDMReference architecture

Add a profile

Decision lens

Compare roles before you compare maturity.

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, confidence, or implementation fit.

Three-part assessment

See the reach, the gaps, and the evidence.

Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.

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
Profile	Plan	Acquire	Harmonize	Exchange	Learn + reuse
USDMReference architecture	CDISC Unified Study Definitions Model has a direct role in Plan.	CDISC Unified Study Definitions Model has no direct role recorded in Acquire.	CDISC Unified Study Definitions Model has no direct role recorded in Harmonize.	CDISC Unified Study Definitions Model has a direct role in Exchange.	CDISC Unified Study Definitions Model has no direct role recorded 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.

USDM

Stage boundary: No direct role is recorded for Acquire, Harmonize, Learn + reuse.
Known limitation: USDM is a model and reference architecture—not an EDC, submission dataset, or proof that generated documents comply with every regulator—and every linked terminology and API version must be pinned.

03 · Detailed assessment

Check the fit and evidence behind the map

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

Detailed comparison of CDISC Unified Study Definitions Model
Assessment	USDMCDISC Unified Study Definitions Model
Purpose & coverage	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—not an EDC, submission dataset, or proof that generated documents comply with every regulator—and every linked terminology and API version must be pinned.
Evidence	E1 + E3 High confidence Formal statusReleased USDM v4.0 with tracked errata and conformance-rule specifications ReviewSource-checked · watch
Maturity	Scaling Released model, implementation guide, APIs, terminology, and conformance-rule specifications; adoption is still scaling
Sources & links	CDISC Digital Data Flow and USDM versions (opens in a new tab)Read full profile