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.

Choose profiles

1 of 3 selected

CDISCStandard

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?”

  1. Start with the job

    Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.

  2. Map lifecycle reach

    Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.

  3. Test the boundary

    Read what each option leaves unresolved before judging maturity or implementation fit.

Review lifecycle coverage and practical fit.

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

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 Foundational Standards
ProfilePlanAcquireHarmonizeExchangeLearn + reuse
CDISCStandardCDISC Foundational Standards has a direct role in Plan.CDISC Foundational Standards has a direct role in Acquire.CDISC Foundational Standards has a direct role in Harmonize.CDISC Foundational Standards has a direct role in Exchange.CDISC Foundational Standards has no direct role recorded in Learn + reuse.
Direct role recordedNo direct role recorded

What each option does not cover

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

CDISC

Stage boundary
No direct role is recorded for Learn + reuse.
Known limitation
Conformance is detailed and version-sensitive; transformations can preserve structure while losing source context.

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 Foundational Standards
AssessmentCDISCCDISC Foundational Standards
Purpose & coverage

Protocol-to-analysis clinical and nonclinical research data, including acquisition, tabulation, analysis, and submission structures.

Best fitBest for regulated studies and traceable submission packages; less natural for early discovery or raw instrument output.

Readiness stages
PlanAcquireHarmonizeExchange
AI-ready contributionStrong variable conventions and traceability help supervised learning, but harmonization, cohort context, and leakage controls remain separate work.
First limitation to testConformance is detailed and version-sensitive; transformations can preserve structure while losing source context.
Maturity

Established

Regulatory production use

Sources & links