01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- EDC, eClinical, archive, and study-operation transfers where the full operational study record must remain portable alongside submission tables.
- Limits
- ODM v2 is not backward-compatible in several areas, XML is the currently supplied schema serialization, and schema validity does not prove semantic or regulatory fitness.
- Best for
- Clinical and Regulatory teams working across Acquire → Harmonize → Exchange.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Clinical and Regulatory source data, metadata, and local mappings
- CDISC ODMWhat changes
Use CDISC ODM as a pinned standard across Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
An EDC exports protocol metadata, forms, clinical data, users, signatures, and audit history in a validated ODM v2 package for transfer or archive.
Why it matters: Its metadata and audit trail help reconstruct collection context, but analysis features and labels still require CDISC or domain transformations and leakage controls.
04
What it fits with
Provides the base structure extended by Define-XML, Dataset-XML, Dataset-JSON, SDM-XML, CTR-XML, and other CDISC exchange artifacts.
- TerminologyMedDRA
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologyWHODrug
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - StandardICH E2B(R3)
Both support Clinical and Regulatory work and meet around Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Governance frameworkICH E6(R3)
Both support Clinical and Regulatory work and meet around 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 ODM must support.
Pin the exact version and companion artifacts: v2.0 · published 2023-08-23.
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
ODM v2 is not backward-compatible in several areas, XML is the currently supplied schema serialization, and schema validity does not prove semantic or regulatory fitness.
Run one representative end-to-end pilot and record exactly where CDISC ODM 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. Its metadata and audit trail help reconstruct collection context, but analysis features and labels still require CDISC or domain transformations and leakage controls.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
CDISC ODM v2.0
Official publisher or steward guidance for this standard profile.
- Publisher
- CDISC