CDISC SDTM (Study Data Tabulation Model): Domain Classes, FDA Catalog & FHIR Mapping

CDISC SDTM (the Study Data Tabulation Model, maintained by the Clinical Data Interchange Standards Consortium) is the global regulatory metadata and dataset architecture required for organizing and submitting human clinical trial data to the U.S. Food and Drug Administration (FDA), Japan’s Pharmaceuticals and Medical Devices Agency (PMDA), and international health authorities. Sitting downstream of electronic case report form (eCRF) capture in systems such as Castor EDC and OpenClinica, SDTM standardizes raw clinical observations—including Treatment-Emergent Adverse Events (TEAEs), laboratory panels, and vital signs—into predictable two-dimensional domain tables accompanied by machine-readable define.xml provenance metadata.

What Is CDISC SDTM and How Is It Used in Clinical Research and Healthcare?

In the end-to-end CDISC clinical data lifecycle, standards are separated by stage: PRM (Protocol Representation Model) structures the protocol; CDASH (Clinical Data Acquisition Standards Harmonization) standardizes how questions are asked on eCRFs; SDTM standardizes how raw collected subject data are tabulated; and ADaM (Analysis Data Model) structures analysis-ready datasets derived from SDTM for statistical modeling.

Under the SDTM v2.0 model and SDTM Implementation Guide (SDTMIG v3.4), almost all subject-level clinical observations are partitioned into two-character domains assigned to one of three General Observation Classes, alongside Special-Purpose, Trial Design, and Relationship datasets:

SDTM Domain Class	Core Two-Letter Domains	Topic Variable & Variable Naming Rule
Interventions (Treatments and substances administered)	EX (Exposure), EC (Exposure as Collected), CM (Concomitant/Prior Medications), PR (Procedures), SU (Substance Use)	Topic variable is --TRT (e.g., EXTRT, CMTRT, PRTRT); qualifiers include dose (--DOSE), units (--DOSU), route (--ROUTE), and start/end ISO 8601 dates (--STDTC, --ENDTC)
Events (Occurrences or incidents independent of planned evaluations)	AE (Adverse Events), DS (Disposition), MH (Medical History), CE (Clinical Events), DV (Protocol Deviations), HO (Healthcare Encounters)	Topic variable is --TERM (e.g., AETERM coded to MedDRA AEDECOD / AEBODSYS, MHTERM); qualifiers include severity (AESEV), seriousness (AESER), and causality (AEREL)
Findings (Measurements, tests, or questionnaires at discrete times)	LB (Laboratory Test Results), VS (Vital Signs), EG (ECG Test Results), PE (Physical Examination), QS (Questionnaires), FA (Findings About)	Topic variable is --TESTCD / --TEST (e.g., LBTESTCD, VSTESTCD); results captured in original units (--ORRES, --ORRESU) and standardized units (--STRESC, --STRESN, --STRESU)
Special-Purpose & Trial Design Domains	Special-Purpose: DM (Demographics — 1 row per subject), CO (Comments), SE (Subject Elements), SV (Subject Visits) Trial Design: TA (Arms), TE (Elements), TV (Visits), TI (Inclusion/Exclusion), TS (Trial Summary)	USUBJID (Unique Subject Identifier) links every record across all subject-level domains; SUPP-- (Supplemental Qualifiers) and RELREC handle non-standard variables and inter-domain links

What Standards or Regulatory Requirements Govern CDISC SDTM?

Submitting non-conformant clinical trial datasets to the U.S. FDA can trigger a technical rejection or a formal Refuse-to-File (RTF) action under federal law:

• FD&C Act Section 745A(a) & FDA Binding Guidance: Under Section 745A(a) of the Federal Food, Drug, and Cosmetic Act, clinical and nonclinical study data in New Drug Applications (NDAs), Abbreviated New Drug Applications (ANDAs), Biologics License Applications (BLAs), and commercial Investigational New Drug (IND) submissions to CDER and CBER must be submitted electronically in the standards specified in the FDA Data Standards Catalog and the FDA Study Data Technical Conformance Guide (with nonclinical toxicology studies using the sister standard CDISC SEND).
• Mandatory Companion Artifacts in eCTD Module 5: An FDA-compliant SDTM package in Electronic Common Technical Document (eCTD) folder m5/datasets/<study-id>/tabulations/sdtm/ requires SAS V5 XPORT (.xpt) or Dataset-JSON/NDA-aligned transport files, a machine-readable define.xml (v2.0 or v2.1) metadata file, a Study Data Reviewer’s Guide (cSDRG), and an annotated case report form (acrf.pdf), validated against FDA business rules and Pinnacle 21 validation checks.
• Controlled Terminology Governance: SDTM variables must be populated using NCI Enterprise Vocabulary Services (EVS) CDISC Controlled Terminology alongside external medical vocabularies: MedDRA for Adverse Events and Medical History, WHO Drug Global for Concomitant Medications, and LOINC for laboratory tests.

How Does CDISC SDTM Integrate with EHR and Health Informatics Workflows?

Historically, clinical research coordinators manually transcribed EHR patient data onto eCRFs before statistical programmers wrote SAS or R scripts to map raw EDC tables into SDTM. Today, EHR-to-EDC integration and real-world data (RWD) pipelines automate this transformation using the HL7 Vulcan / CDISC FHIR-to-CDISC Joint Mapping Implementation Guide:

1. FHIR Resource to SDTM Domain Mapping: Structured EHR data retrieved via HL7 FHIR R4 APIs map deterministically into SDTM domains: FHIR Patient maps to SDTM DM (Demographics); FHIR Observation (vital signs and laboratory panels) maps to SDTM VS and LB; FHIR Condition maps to SDTM MH (Medical History) or CE (Clinical Events); and FHIR MedicationStatement / MedicationAdministration maps to SDTM CM or EX.
2. Provenance & Audit Traceability: Combining W3C PROV and FHIR Provenance records with CDISC Operational Data Model (ODM-XML) and define.xml Origin metadata preserves end-to-end lineage from the hospital EHR source record to the final regulatory submission dataset.

Frequently Asked Questions

What is CDISC SDTM and how is it used in clinical research and healthcare?

The CDISC Study Data Tabulation Model (SDTM) is the international regulatory data standard developed by the Clinical Data Interchange Standards Consortium (CDISC) that defines a uniform structure for organizing, naming, and formatting human clinical trial tabulation datasets (such as Demographics [DM], Adverse Events [AE], Concomitant Medications [CM], and Laboratory Test Results [LB]) for submission to regulatory authorities.

What standards or regulatory requirements govern CDISC SDTM?

Under Section 745A(a) of the Federal Food, Drug, and Cosmetic (FD&C) Act and the FDA Binding Guidance on Standardized Study Data, sponsors submitting NDAs, ANDAs, BLAs, and commercial INDs to FDA CDER or CBER must format clinical trial tabulation datasets according to the versions of CDISC SDTM, SDTM Implementation Guide (SDTMIG), NCI EVS Controlled Terminology, and Define-XML v2.0/v2.1 listed in the FDA Data Standards Catalog.

How does CDISC SDTM integrate with EHR and health informatics workflows?

Clinical trial data captured in electronic data capture (EDC) systems like Castor EDC or OpenClinica (using CDASH and CDISC ODM) or extracted from hospital electronic health records via HL7 FHIR R4 resources are transformed into SDTM domains using the HL7 Vulcan / CDISC FHIR-to-CDISC Joint Mapping Implementation Guide prior to generating ADaM analysis datasets.

Sources

• U.S. Food and Drug Administration (FDA). Study Data Standards Resources: FDA Data Standards Catalog & Study Data Technical Conformance Guide. https://www.fda.gov/industry/fda-data-standards-advisory-board/study-data-standards-resources
• Clinical Data Interchange Standards Consortium (CDISC). Study Data Tabulation Model (SDTM) & SDTM Implementation Guide (SDTMIG). https://www.cdisc.org/standards/foundational/sdtm
• HL7 International & CDISC. FHIR to CDISC Joint Mapping Implementation Guide. https://hl7.org/fhir/uv/cdisc-mapping/