01
Where it fits and where it does not
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.
- Limits
- Conformance is detailed and version-sensitive; transformations can preserve structure while losing source context.
- Best for
- Clinical and Preclinical teams working across Plan → Acquire → Harmonize → Exchange.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Clinical and Preclinical source data, metadata, and local mappings
- CDISCWhat changes
Use CDISC as a pinned standard across Plan → Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
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 - Governance frameworkICH E6(R3)
Both support Clinical work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileTMF Reference Model
Both support Clinical work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileMIABIS
Both support Clinical work and meet around Plan, Acquire, 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.
Define one handoff, its 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
Test the main limitation
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.
Machine-readable output may still be unfit for analysis or ML.
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
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
CDISC foundational standards
Official publisher or steward guidance for this standard profile.
- Publisher
- CDISC