01
Where it fits—and where it doesn’t
Use these four checks before committing implementation time.
- Use it when
- Best for regulated studies and traceable submission packages; less natural for early discovery or raw instrument output.
- Do not use it as
- Do not treat CDISC as a complete solution on its own. Conformance is detailed and version-sensitive; transformations can preserve structure while losing source context.
- Best for
- Teams working with Clinical and Preclinical data across Plan → Acquire → Harmonize → Exchange.
- 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 Preclinical data, metadata, and the local decisions around them
- CDISCWhat changes
CDISC applies a shared standard across Plan → Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A more consistent, reviewable handoff for the next system or team
03
A concrete example
A phase III study maps EDC collection to CDASH, tabulates SDTM domains, and derives ADaM datasets for analysis and review.
Why it matters: Strong variable conventions and traceability help supervised learning, but harmonization, cohort context, and leakage controls remain separate work.
04
What it fits with
CDASH supports acquisition-to-SDTM traceability; SEND implements SDTM for nonclinical data; ADaM commonly derives from SDTM; Define-XML exchanges dataset metadata.
- Metadata vocabularyDPV
Both support Clinical work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - FrameworkFAIR
Both contribute at Plan, Acquire, Harmonize, Exchange, with different domains or implementation roles.
Explore relationship - Data model / schemaCDISC BCs
Both support Clinical work and meet around Plan, Acquire, Harmonize. Compare their roles before treating them as interchangeable.
Explore relationship - StandardISO IDMP
Both support Clinical work and meet around Plan, Harmonize, Exchange. 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 CDISC must support.
Pin the exact version and companion artifacts: CDASH · SDTM · ADaM · SEND · independently versioned.
Map one representative input to the required standard 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
Conformance is detailed and version-sensitive; transformations can preserve structure while losing source context.
Run one representative end-to-end pilot and record exactly where CDISC 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. Strong variable conventions and traceability help supervised learning, but harmonization, cohort context, and leakage controls remain separate work.
07
Why we believe this
Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.
Evidence notation: E1 + E2. 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.
CDISC foundational standards
The canonical publisher or steward source used to verify this standard profile.
- Publisher
- CDISC
- 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