---
title: "CDISC standards explained: SDTM, ADaM and more | Quantlix"
description: "CDISC standards define how clinical trial data is collected, tabulated, analyzed and described for regulators. Learn what SDTM, ADaM, CDASH and Define-XML do."
canonical: "https://quantlix.com/en/standards/cdisc/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/cdisc/
Language: en
Description: CDISC standards define how clinical trial data is collected, tabulated, analyzed and described for regulators. Learn what SDTM, ADaM, CDASH and Define-XML do.

**CDISC** [Health and clinical data](https://quantlix.com/en/standards/#health)

# CDISC: the data standards for clinical research

CDISC is a global nonprofit whose clinical research data standards, such as SDTM, ADaM and Define-XML, are required by FDA and Japan's PMDA for study data in drug submissions.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/cdisc/#standard-overview)

## At a glance

**Full name**

Clinical Data Interchange Standards Consortium (CDISC) foundational and data exchange standards

**Published by**

CDISC, a global nonprofit standards organization

**Type**

Data standards (models, implementation guides, controlled terminology and exchange formats)

**Current version**

Each standard is versioned separately, for example SDTM v2.0 with SDTMIG v3.4 (November 2021), with SDTMIG v4.0 in public review; FDA lists accepted versions in its Data Standards Catalog

**Applies to**

Sponsors, contract research organizations and technology vendors that collect, process and submit clinical and nonclinical study data

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- CDASH standardizes how data is collected, SDTM how it is tabulated and ADaM how it is prepared for analysis, with traceability between them.
- SEND applies the SDTM model to nonclinical studies, and Define-XML describes the structure and meaning of every submitted dataset.
- FDA requires standardized study data for NDAs, BLAs and ANDAs for studies that started after December 17, 2016.
- Versions matter: submissions use the versions that FDA or PMDA list as supported at the relevant date, so teams fix a version set early.

### What is CDISC?

CDISC, the Clinical Data Interchange Standards Consortium, is a global nonprofit that publishes **the data standards used to collect, organize, analyze and submit clinical research data**. The name covers both the organization and its family of standards, which follow a study from the case report form to the datasets a regulator reviews.

The standards exist so that nobody has to learn a new data layout for every trial. When adverse events, lab results and vital signs follow the same structure in every submission, reviewers can use the same tools across studies, and sponsors can pool data from many trials.

### What CDISC covers

- **CDASH.** Standard collection fields for case report forms and electronic data capture (EDC), with clear paths into SDTM.
- **SDTM and the SDTMIG.** The Study Data Tabulation Model and its implementation guide organize collected data into domains, such as demographics, adverse events and laboratory results.
- **ADaM.** The Analysis Data Model defines analysis datasets and their metadata, with traceability from each result back to SDTM.
- **SEND.** An implementation of SDTM for nonclinical studies, required by FDA for many applications.
- **Controlled terminology.** Shared code lists, so values such as units and test names mean the same thing everywhere.
- **Define-XML.** Machine-readable metadata describing each dataset, its variables, value lists, origins and derivations.

### What regulators require

**FDA requires standardized study data** for NDAs, BLAs and ANDAs for studies that started after December 17, 2016, and for commercial INDs for studies that started after December 17, 2017. The FDA Data Standards Catalog lists the accepted standards and versions, the Study Data Technical Conformance Guide explains how to apply them, and FDA checks incoming data against published business and validator rules. Technical rejection criteria can stop a submission that is missing required elements, such as the trial summary dataset.

Japan’s PMDA has accepted CDISC study data under its own validation rules since October 2016 and requires CDISC data for new drug applications. In both places, a submission has to use versions that were supported at the relevant date, so teams usually fix a version set at study start and record it.

### How it shows up in software projects

- **Collection design.** EDC forms built on CDASH fields and CDISC controlled terminology, so mapping to SDTM becomes a lookup rather than a rewrite.
- **Traceable transformations.** SDTM and ADaM datasets produced by versioned, reviewed code, with lineage from raw data to every derived variable.
- **Metadata as a product.** Define-XML generated from one governed metadata source instead of being written by hand at the end.
- **Validation in the pipeline.** Conformance rules from FDA, PMDA and CDISC run on every data refresh, so issues surface during the study rather than at submission.
- **Controlled systems.** Platforms that hold trial data meet the electronic record controls of [21 CFR Part 11](https://quantlix.com/en/standards/21-cfr-part-11/) and good clinical practice.

### How we work with CDISC

We help [life sciences](https://quantlix.com/en/industries/life-sciences/) teams build the data side of clinical research: EDC integrations, SDTM and ADaM pipelines, metadata repositories that generate Define-XML and validation dashboards through our [data analytics](https://quantlix.com/en/services/data-analytics/) work. We design with the data governance expectations of [ICH E6](https://quantlix.com/en/standards/ich-e6/) in mind, and where trial data starts in health records, we can map [HL7 FHIR](https://quantlix.com/en/standards/hl7-fhir/) sources into CDISC structures.

We build and test against the published rules, and we document every mapping so your team can review it. The judgment that a submission is acceptable rests with your regulatory team and, finally, with the agency.

## Where it applies

Industries where this standard often shapes the work.

- ### [Pharmaceuticals & Life Sciences](https://quantlix.com/en/industries/life-sciences/)

  Research data, pharmaceutical operations and biotechnology platforms

## Related standards

[All standards](https://quantlix.com/en/standards/)

- ICH E6

  ### [Good clinical practice for trials](https://quantlix.com/en/standards/ich-e6/)

  ICH E6 is the international guideline for good clinical practice (GCP), the ethical and quality standard for designing, running, recording and reporting clinical trials of medicines. E6(R3) is the current revision.
- 21 CFR Part 11

  ### [FDA electronic records and signatures](https://quantlix.com/en/standards/21-cfr-part-11/)

  21 CFR Part 11 is the FDA regulation that sets the conditions under which electronic records and electronic signatures are trusted as equivalent to paper records and handwritten signatures.
- HL7 FHIR

  ### [Health data exchange over web APIs](https://quantlix.com/en/standards/hl7-fhir/)

  HL7 FHIR is the HL7 International standard for exchanging health data as small, linked resources over web APIs, used by EHRs, patient apps, payers and research platforms.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [Data analytics](https://quantlix.com/en/services/data-analytics/)

Quantlix builds analytics pipelines and business intelligence tools that turn operational data into defined metrics, useful reports and decision support.

### [Enterprise applications](https://quantlix.com/en/services/enterprise-applications/)

Quantlix designs and builds enterprise applications for internal workflows, business rules and system integration, with clear access controls and maintainable architecture.

## Questions, answered

What teams usually ask us about this standard.

**Is CDISC mandatory?**

For many submissions, yes. FDA requires study data in the standards listed in its Data Standards Catalog, such as SDTM, SEND, ADaM and Define-XML, for NDAs, BLAs and ANDAs for studies that started after December 17, 2016, and for commercial INDs for studies that started after December 17, 2017. Japan's PMDA also requires CDISC data for new drug applications.

**What is the difference between SDTM and ADaM?**

SDTM organizes collected data into standard domains, such as demographics, adverse events and laboratory results, close to how it was observed. ADaM datasets are derived from SDTM for statistical analysis, with metadata that traces each result back to its source.

**Where does CDASH fit?**

CDASH sets standard collection fields for case report forms and electronic data capture systems, designed so data maps cleanly into SDTM later. Building forms on CDASH reduces transformation work at the end of a study.

**What is Define-XML?**

Define-XML is the CDISC standard for dataset metadata. It describes each submitted dataset, its variables, codes, origins and derivations, and FDA and PMDA require it for each study in electronic submissions. Version 2.1 is the current major version.

**Is SAS transport (XPT) still the submission format?**

Yes, XPT version 5 files remain the expected format for FDA study datasets today. FDA centers are testing CDISC Dataset-JSON as a possible replacement, so check the Data Standards Catalog and Technical Conformance Guide before you change formats.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [CDISC foundational standards](https://www.cdisc.org/standards/foundational)
- [FDA study data standards resources](https://www.fda.gov/industry/fda-data-standards-advisory-board/study-data-standards-resources)
- [PMDA advanced review with electronic data](https://www.pmda.go.jp/english/review-services/reviews/0002.html)
- [CDISC Define-XML](https://www.cdisc.org/standards/data-exchange/define-xml)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
