USDM vs SDTM, ICH M11, ODM and FHIR

USDM sits among standards that sound alike and do different jobs. The short version: USDM describes the plan for a study, ICH M11 describes the protocol document, CDASH and ODM describe how data is collected, and SDTM describes the data once it has been. They are stages of one flow, not competitors.

At a glance

StandardPublished byWhat it describesWhen it applies
USDMCDISC, with TransCelerateThe study definition: design, schedule, objectives, eligibility, interventions and the protocol's text.Before the study starts, and again at each amendment.
ICH M11ICHThe protocol document: a harmonised template and a technical specification for exchanging its content.When the protocol is written and submitted.
CDASHCDISCHow data is collected: the fields on case report forms.When data collection is designed.
ODMCDISCCase report form metadata and collected data, as an exchange format.When an EDC system is built and when data moves between systems.
SDTMCDISCCollected data, organised into standard datasets for regulatory submission.After data is collected.
HL7 FHIRHL7Healthcare data in general, including research studies and care schedules.Wherever a study has to meet healthcare systems such as the EHR.

USDM vs ICH M11

This is the pairing people mix up most, because both are called a digital protocol.

ICH M11 is a regulatory guideline. It defines the Clinical electronic Structured Harmonised Protocol, CeSHarP: a common template for what a protocol contains and in what order, and a technical specification of the data elements for exchanging that content electronically. ICH adopted it at Step 4 on 19 November 2025, and FDA published it as final guidance in May 2026.

USDM is a data model. It holds the whole study definition, including parts no protocol template spells out as data, such as every scheduled activity and every timing. CDISC aligned USDM to M11 so that the sections of the M11 template can be filled from a study held in USDM. Version 3.0 covered the draft template, version 4.0 was aligned to the March 2025 review draft, and a 4.1 release is planned to align with the adopted specification.

USDM vs SDTM

SDTM, the Study Data Tabulation Model, organises the data collected from participants into standard datasets for submission to regulators. It is about what happened. USDM is about what is planned, and exists before a single participant is enrolled.

They meet at the SDTM trial design datasets, which describe the plan inside a submission: Trial Arms (TA), Trial Elements (TE), Trial Visits (TV), Trial Inclusion/Exclusion Criteria (TI) and Trial Summary (TS). USDM was built so that these can be generated from a study design: its arms, epochs, elements, cells, encounters and criteria carry the same concepts and use the same controlled terminology. The mapping is published with the standard.

USDM vs CDASH and ODM

CDASH standardises the fields on case report forms. ODM is the format for exchanging form definitions and collected data, and is how most EDC builds are described. Both are about data collection.

USDM stops one step earlier. It says that vital signs are taken at Week 2. Through biomedical concepts it can also say that vital signs means systolic and diastolic blood pressure and pulse, with their units. It does not define the form. The intended flow is that an EDC system reads the schedule and the biomedical concepts from USDM and uses them to select or build forms, which are then expressed in ODM. USDM is described by CDISC as a reference model and ODM as a transport model.

USDM vs HL7 FHIR

FHIR is the healthcare interoperability standard. It is how a study reaches an electronic health record: a research study, the participants in it, and the schedule of care they follow can all be FHIR resources.

Two HL7 Vulcan projects connect it to USDM. One defines how a schedule of activities is represented in FHIR. The other, Utilizing the Digital Protocol, is a joint effort of TransCelerate, CDISC and HL7 Vulcan to keep ICH M11, the FHIR representation of a protocol and USDM aligned, so the same study can be expressed in each.

Older CDISC protocol standards

  • PRM, the Protocol Representation Model of 2012, covered much of the same ground at a higher level. CDISC expects USDM to supersede it.
  • SDM-XML, the Study Design Model of 2011, described designs as an extension of ODM. It was folded into ODM v2.0 and was one of the inputs to USDM.
  • CTR-XML targets one use, generating clinical trial registry submissions from a single file. USDM covers registry content as one of several uses.

Where a site-side digital protocol fits

Every standard above is written from the sponsor’s side of the study or the regulator’s. None of them describes how a particular research site will carry the study out, because that is not theirs to standardise. That is the gap Concordare’s Clinical Trial Protocol Model (CTPM) is built for. Concordare has built a USDM 4.0 connector for the CTPM that works in both directions: a USDM file from a sponsor can seed a CTPM, and an approved CTPM can be exported as USDM 4.0. It covers the core of the study design, is still expanding, and is being demonstrated ahead of general release. The CTPM also carries the operational detail a research site needs that USDM does not define. USDM at the research site goes into what that operational detail is for.

Keep going