Standard · v2.0 · published 2023-08-23

CDISC Operational Data Model

Maintained by CDISC

What it helps you do

Use CDISC ODM when you need vendor-neutral exchange and archival of study metadata, subject data, administrative data, reference data, and audit information.

  • Clinical
  • Regulatory
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when
EDC, eClinical, archive, and study-operation transfers where the operational study record—not only submission tables—must remain portable.
Do not use it as
Do not treat CDISC ODM as a complete solution on its own. 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
Teams working with Clinical and Regulatory data across Acquire → Harmonize → Exchange.
Maturity
ScalingUsable today, with adoption or tooling still scaling; pilot the exact stack you plan to run.

02

See it in the workflow

A standard creates value by changing a handoff, not by existing in a catalog.

  1. InputWhat starts

    Clinical and Regulatory data, metadata, and the local decisions around them

  2. CDISC ODMWhat changes

    CDISC ODM applies a shared standard across Acquire → Harmonize → Exchange

  3. OutputWhat becomes possible

    A more consistent, reviewable handoff for the next system or team

Readiness gateBefore scaling: 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.

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.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

  1. Name an accountable owner and the decision CDISC ODM must support.

  2. Pin the exact version and companion artifacts: v2.0 · published 2023-08-23.

  3. Map one representative input to the required standard artifacts.

  4. Test the result against the canonical source and record every exception.

  5. Preserve the source data, mappings, and review evidence before scaling.

06

Limitation to test first—and the tests that catch it

Risk

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.

Test

Run one representative end-to-end pilot and record exactly where CDISC ODM loses context, needs an extension, or depends on another standard.

Risk

A structured or machine-readable result can still be unfit for analysis or AI.

Test

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

Why we believe this

Checked against the canonical source plus implementation or adoption evidence reported by the steward or its community.

Evidence notation: E1 + E3. The code is shorthand; the plain-language statement above is the claim.

Formal status
Published ODM v2.0; current XML schema available
Confidence
High
Review state
Source-checked · watch
Reviewed by
Clinical data-exchange reviewer
Last verified
13 July 2026
Review again when
ODM specification, schema, serialization, certification, or known-issue update
How the evidence method works

08

Source shelf

Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.

  • Primary sourcev2.0 · published 2023-08-23

    CDISC ODM v2.0

    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
    Open at source

Next action

Put this profile in context

Compare its role with adjacent standards or place it inside an end-to-end data pathway before choosing an implementation.