Data Readiness
Knowledge BaseLife-sciences R&D
93 profiles ·
practical standards guide

Reference architecture · v4.0 · released 2025-06-03

CDISC Unified Study Definitions Model

Maintained by CDISC · developed with TransCelerate

What it helps you do

Define a clinical study once, then reuse the same structured facts across the protocol, registry, and study systems.

  • Clinical
  • Regulatory
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits and where it does not

Use these four checks before committing implementation time.

Use it when
Objectives, endpoints, eligibility, interventions, schedules, and other protocol facts must stay consistent across authoring, registry, study-build, and downstream systems.
Limits
Do not use USDM as an electronic data-capture system, a submission dataset, or proof that generated documents satisfy every regulator. It supports those outputs; it does not replace them.
Best for
Study designers, clinical data standards teams, protocol authors, digital-protocol product owners, and integration architects.
Maturity
ScalingUSDM v4.0 is released with an implementation guide, API, terminology, and conformance rules; adoption and end-to-end tooling are still scaling.

02

See it in the workflow

This view shows the input, the change the standard introduces, and the resulting output.

  1. InputWhat starts

    Protocol intent: objectives, endpoints, eligibility, interventions, schedule of activities, estimands, amendments, and controlled terms

  2. USDMWhat changes

    USDM v4.0 organizes that intent as a versioned, computable study definition

  3. OutputWhat becomes possible

    Consistent protocol content, registry fields, CTMS/EDC setup inputs, and SDTM Trial Design metadata

Readiness gateValidate conformance and have accountable clinical and regulatory reviewers confirm that every generated output preserves the intended meaning.

03

A concrete example

A sponsor authors one versioned study definition, then reuses it to initialize protocol text, registry fields, clinical trial management and electronic data-capture configuration, and SDTM Trial Design metadata.

Why it matters: Structured protocol intent is valuable for agents and automation, but generated study assets still require conformance checks and accountable clinical review.

04

What it fits with

Aligns with ICH M11 and CDISC Biomedical Concepts, controlled terminology, and SDTM Trial Design; its API can bridge to FHIR-facing systems.

05

Implementation starter

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

  1. Choose one study and name the downstream outputs that will consume the definition.

  2. Pin USDM v4.0 together with the implementation guide, API schema, controlled terminology, conformance rules, and tracked errata.

  3. Map the current protocol-authoring concepts and identifiers into USDM without discarding the source representation.

  4. Generate one representative protocol section, registry extract, and study-system handoff from the same versioned definition.

  5. Validate the model and each downstream artifact, then reconcile changes back to the authoritative definition.

  6. Assign clinical, standards, regulatory, and technical owners for review, release, and amendment handling.

06

Test the main limitation

Risk

The model, API, terminology, conformance rules, or downstream mappings drift onto incompatible versions.

Test

Record every dependency in a release manifest and run the pinned conformance suite plus representative downstream transformations before each promotion.

Risk

Generated protocol or system artifacts look plausible but alter clinical intent or omit regulator-specific requirements.

Test

Diff each generated artifact against the authoritative definition and require accountable clinical and regulatory sign-off on meaning, completeness, and jurisdictional requirements.

07

Official resources

Specifications, diagrams, examples, and guides from the organizations that maintain them.

  • Primary sourceUSDM v4.0

    Digital Data Flow and USDM versions

    CDISC's canonical overview of USDM, its releases, implementation guidance, and related Digital Data Flow work.

    Publisher
    CDISC
    Open official source
  • Diagramv4.0.0

    DDF-RA timeline UML view

    A version-pinned model view showing how study timeline concepts relate inside the DDF reference architecture.

    USDM timeline model view showing study epochs, elements, activities, and scheduled instances across a study design.
    CDISC DDF-RA v4.0.0, Timeline UML view, CC BY 4.0Preview · open the original at the publisher
    Publisher
    CDISC DDF-RA project
    Open official source
  • Specificationv4.0.0

    USDM OpenAPI specification

    The version-pinned API contract for exploring resources, operations, and implementation details.

    Publisher
    CDISC DDF-RA project
    Open official source
  • Examplesv4.0.0

    Official USDM examples

    Version-pinned example artifacts for seeing how the reference architecture is represented in practice.

    Publisher
    CDISC DDF-RA project
    Open official source
  • Video

    Advancing the Schedule of Activities using USDM

    A CDISC-hosted webinar page explaining the Schedule of Activities work and its relationship to USDM.

    Publisher
    CDISC
    Open official 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.