Controlled Terminology




Supplemental Files

Controlled Terminology consists of question (e.g., Variables, TESTs and PARMs) and answer(e.g., response codelists, qualifier variable codelists), which are commonly referred to as codelists and are published alphabetically in the Controlled Terminology publication.

The terms within these codelists may have relationships to other terms within other codelists. For instance, a single TEST in the EGTEST codelist may have a finite set of responses located in the EGSTRESC codelist that constitutes a subset of the EGSTRESC codelist. Another instance, a single VSTEST value may have a constrained set of units of measure that are valid for the numeric responses to that VSTEST. These relationships are not readily apparent in the Controlled Terminology publication files.

To address this issue, the Controlled Terminology Teams have created Codetable Mapping Files based on published Terminology, which show relationships between terms in different_Controlled Terminology codelists. These supplemental files provide human and machine-readable linkages between published terms across multiple codelists and may be helpful for data QA/QC, CRF building, and data mapping. These files are for clinical use only.

The Controlled Terminology teams will continue to update these files as new Terminology is published, as well as develop new domain Codetable Mapping Files. If you are interested in seeing specific content developed, please submit the request through the New Term Request Site. CDISC is concurrently working on the development of electronically consumable formats of this content to be published out of CDISC Library.

Note: 2020-09-25: The SEND Leadership Team has decided to remove the SEND codetable mapping files from this page in December 2020, coincident to the CT P44 publication. It is unclear at this time how the files are to be used to support a SEND submission, which is causing some confusion among the user community. These files will no longer be updated beginning with CT Package 43.

DD Codetable

DS Codetable

CV Codetable

ECG Codetable

GI Codetable

MK Codetable

Oncology Codetable

Race Ethnicity Codetable

RP Codetable

SC Codetable

SEND Codetable

SR Codetable

SS Codetable

TS Codetable

UR Codetable

VS Codetable

The Unified Code for Units of Measure (UCUM) contains a blueprint for the creation of compliant units of measure from more than 300 terminal unit symbols. UCUM is used in healthcare to populate electronic health records, such as laboratory records in LOINC, and in the ISO IDMP standard.

CDISC must specify a single, preferred unit of measure for the pharmaceutical industry to use in data submissions to regulators. Since UCUM does not control mathematical synonymy nor cover all units of measure required by the pharmaceutical industry, CDISC  publishes submission values for units of measure  across multiple codelists that support variables within CDISC findings, interventions, and trial design domains.

To seamlessly toggle between UCUM and CDISC Units, a mapping has been built and is updated quarterly with the CDISC Controlled Terminology publication. For each published CDISC submission value across all UNIT-based codelists in SDTM terminology, the mapping provides valid UCUM expressions associated with that unit concept. This allows a collected UCUM-compliant unit of measure to be easily matched to the appropriate CDISC submission value associated with that concept.

Unit-UCUM Codetable

FDA requires the submission of Logical Observation Identifiers Names and Codes (LOINC®) within clinical LB domain datasets in new drug applications (NDAs), abbreviated new drug applications (ANDAs), and biologics license applications (BLAs) for studies starting after 15 March 2020 and for certain investigational new drugs (INDs) for studies starting after 15 March 2021. A recommendations document produced by a LOINC working group, composed of representatives from FDA, NIH, CDISC, and Regenstrief Institute, called for the development of a mapping file to map the most commonly submitted LOINCs in clinical research to the associated CDISC Controlled Terminology components associated with each LOINC part.

LOINC to LB Mapping File

This mapping file is intended to show examples of LOINC code mappings to CDISC variables and terminology to aid researchers’ adoption of the FDA requirement. The file is composed of LOINCs from the 2005 CDISC-LOINC mapping project, the LOINC Top 2000 SI, the LOINC Top 2000 US, as well as CDISC LB domain datasets submitted to FDA from 2014 - 2016. It includes more than 1400 LOINCs across the Chemistry, Hematology, Coagulation, Toxicology, Urinalysis, Serology, and other classes that would be mapped to the CDISC LB domain. The mapping file does not include LOINCs relevant to data that would be mapped to other CDISC domains such as microbiology, pathology, genomics, vital signs, fetal/neonatal screening, or administrative questions. For more information, please refer to the published ReadMe associated with the mapping.

LOINC to LB Mapping Files

CDISC Conformance Rules dictate that an <=8 character TESTCD/PARMCD and <=40 character TEST/PARM value be available for data submission to regulators. Two distinct codelists are created to support two distinct, paired submission values, however the underlying semantic meaning remains the same. It is not easy to tell which paired submission value goes with which, as the paired submission values exist on different rows of the CDISC Terminology publications, sometimes quite far apart. The CDISC Synonym column is not helpful to ascertain the paired 'decode' value when there are multiple synonyms. Currently, NCI C-codes can be used to pair TEST/TESTCD or PARM/PARMCD submission values but this requires manual manipulation of the spreadsheets. Currently users must manipulate the existing formats produced by NCI-EVS to generate a more integrated view of these paired values.

NCI-EVS has produced a prototype view of these paired codelists that show the paired submission values (TEST/TESTCD or PARM/PARMCD) for each terminology subset (SDTM, SEND, and ADaM) on the same row of data. Only SDTM, SEND, and ADaM files have been produced because these are the only CDISC Terminology subsets that contain paired codelists. These files contain only paired codelist values; they do not contain all terminology values for SDTM, SEND, and ADaM. The SDTM and SEND files correspond to Controlled Terminology version 2021-06-25. The ADaM file correspond to Controlled Terminology version 2020-12-18.

The content in these files should be considered for experimental use only and may be subject to content and structural changes over time, based on user feedback during this review and commenting period.

We invite you to test the utility of these files and share your feedback. You will need to log in or register for the CDISC Wiki to provide comments via JIRA.
Register for the Wiki. If you already have an account on Wiki or JIRA, our issue-tracking system, simply log in to your account; Wiki and JIRA use the same login credentials. CDISC Wiki is a different login from cdisc.org.

View the Paired Codelist Page


ADaM Paired View

SDTM Paired View

SEND Paired View