News and updates
- 2021-06-28: New contents, new endpoints, new features
- 2021-05-04: Added diff functionality
- 2021-03-30: New contents, editorial updates
- 2020-11-11: Next Generation CDISC Library
- 2020-07-07: New contents, new endpoint, metadata adjustments for ADaM
- 2020-02-14: New contents, new endpoints, editorial updates
- History Prior to 2020...
2019-11-18: New contents, bug fixes, minor browser patch
2019-09-13: Data standards browser as a new functionality
2019-07-18: Search API, CSV & Excel exports, new and updated contents, and documentation updates
2019-04-10: New contents, XML media type (beta functionality), and document revision with new and updated information
2019-02-15: Initial version
The base URL for the API is:
The URL for Data Standards Browser is:
The REST API uses API key authentication.
Note, support for Basic Auth is deprecated as of the 2020-11-11 release. For an interactive walk-through, refer to the video posted on https://www.cdisc.org/cdisc-library/getting-started, starting at 00:44:38.
Content for CDISC Controlled Terminology P43 is available as a patch release dated 2020-11-06. It consists of contents published on 2020-09-25 plus transactional updates from the version dated 2020-11-06.
The following standards have been loaded:
- CDISC Controlled Terminology P19 (2014-09-26) to P46 (2021-06-28)*, a total of 28 quarters with 115 parts
- CDASH v1.1.1/CDASHUG v1.0, CDASH Model v1.0 to v1.1, CDASHIG v2.0 to v2.1
- SDTM v1.2 to v1.8, SDTMIG v3.1.2 to v3.3, SDTMIG-AP v1.0, SDTMIG-PGx v1.0, SDTMIG-MD v1.0, SDTMIG-MD v1.1
- SENDIG v3.0, SENDIG v3.1.1, SENDIG-DART v1.1, SENDIG-AR v1.0
- ADaM v2.1, ADaMIG v1.0 to ADaMIG v1.1 to v1.2, ADaM ADAE v1.0, ADaM TTE for BDS v1.0, ADaM OCCDS v1.0
* denotes new contents added as of the 2021-06-28 release
UPDATED Included in the 2021-06-28 release are:
- QRS*, accessible via:
- API endpoint.
- Data Standards Browser.
- ODM-XML support.
- CDISC Controlled Terminology Q2 2021 publication (P46).
- List of draft contents:
- ADaM OCCDS v1.1 (new).
- SDTM v2.0 (updated).
- SDTMIG v3.4 (updated).
Data Standards Browser
- Added a text search in the left navigation pane.
- Updated to display multi-line text properly, e.g., CDISC Notes.
- Applied word wrapping behavior to columns, e.g., Label.
- Updated to show an error message when a Diff report can't be generated when there is nothing to compare with, i.e., no predecessor.
* For details, go to QRS Supplements to SDTMIG.
Corrections & Patches
- "dataset" was incorrectly indexed as "datasetStructure". Fixed the indexer so that dataset names such as AE are searchable using the correct scope.
- Excel and CSV export requests for ADaM v2.1 no longer creates an error. It is now showing 0 variables, which is the expected result.
- SDTMIG-MD v1.1's predecessor was missing. It now has predecessor relationship to SDTMIG-MD v1.0.
- N/A for this release
- API endpoint
- Report as an export from Data Standards Browser
* For details, go to Diff
Corrections & Patches
- N/A for this release
- N/A for this release
For system maintenance status, use this endpoint to obtain a flag indicating whether CDISC Library is under maintenance and a related system message:
For a machine-readable method to obtain a full listing of products loaded into the metadata repository use:
Or, by product group:
where product-group is one of these values:
* denotes new parameter added as of the 2021-03-30 release
Included in the 2020-02-14 release are two new endpoints, designed to provide high-level information about CDISC Library. These endpoints support both JSON and XML media types.
First, /mdr/about returns the URL for on-line API Documentation and Release Notes. It also includes a hypermedia link to a list of the product groups with their most recent update dates, as described below.
/mdr/lastupdated returns dates of last updated, organized by CDISC product group.
UPDATED Added to the 2021-06-28 release is the support for ODM-XML, as a beta functionality. The media type for ODM-XML is application/odm+xml. For CDASHIG, users will receive an ODM v1.3.2 document as the response payload. For ADaMIG, SDTMIG, and SENDIG, user will receive a Define-XML v2.1 document.
ODM-XML, CSV and Excel Workbook media types are only available at the top-level of a foundational standard. When requesting them at levels in any lower hierarchy, the API will return an HTTP 406 Not Acceptable status code.
CDISC Controlled Terminology in ODM-XML format is not yet supported. This is currently accessible through NCI EVS FTP site, here: https://evs.nci.nih.gov/ftp1/CDISC.
For example, a cURL snippet to obtain ADaM OCCDS v1.0 (lines #1-3), SDTMIG v3.3 (lines #5-7) in ODM format. The outputs are in Define-XML v2.1:
Another cURL snippet to obtain CDASHIG v2.1 in ODM format. The output is in ODM v1.3.2:
Below is a cURL snippet to obtain ADaM OCCDS v1.0 (lines #1-3), SDTMIG v3.3 (lines #5-7), and Controlled Terminology P38 (lines #9-11) in CSV format:
Similarly, a cURL snippet to obtain ADaM OCCDS v1.0 (lines #1-3) , SDTMIG v3.3 (lines #5-7), and Controlled Terminology P38 (lines #9-11) in Excel Workbook format:
Starting 2021-03-30, users can access draft contents through CDISC Library. Draft contents are point-in-time snapshots, before they become official publication. Although may not be suitable for production use, draft contents are helpful toward evaluation and public reviews.
Whenever mid-cycle revision to CDISC Controlled Terminology publication is necessary, only the latest corrected information will appear in the metadata repository.
The earliest CDISC Controlled Terminology publication loaded into the metadata repository is P19 (2014-09-26). With that, _links/priorVersion will not be part of the API response when querying P19 packages. CDISC will evaluate loading prior publications based on demand and requests.
For CDISC Controlled Terminology, NCI EVS publishes synonyms in a semi-colon separated list. In the metadata repository, they are decoded into individual entries. In rare cases where synonyms are non-unique for any given term, only distinct synonyms will appear in the metadata repository.
When querying using the API, lexicographic order is applied to synonyms listing in the response. For example, this is a response excerpt when querying the term Left Ventricular Maximum Positive dP/dt (C120916):
In the CDISC Controlled Terminology Protocol package, where the Codelist Extensible (Yes/No) attribute reads "NA", they are treated as null in the metadata repository.
All instances of "N/A" in CDASH publications are treated as null in the metadata repository.
An exception is the "Controlled Terminology Codelist Name" column exported in the CSV and Excel formats to preserve original sequence of codelist values as shown in the published document.
In the CDASH Model v1.0 and the CDASHIG v2.0, the CDASH team applied the class concept to all domains. Identifier and timing variables were assigned class Identifier and Timing respectively as an attribute. In order to offer one common API design for all CDASH products, it was necessary to apply this class concept to CDASHIG v1.1 domains. In consequence, "Common variables" (identifier and visit timing variables in Sections 5.1, 5.2) were also instantiated to all CDASHIG v1.1 domains.
These changes were presented to and approved by the CDISC Global Governance Committee. For these changes, a new version indicator, 1.1.1, is given in the metadata repository.
The CDASH products include different types of mappings:
- CDASH model class variables to SDTM class variables
- CDASH model class variables to SDTM dataset variables
- CDASH model domain variables to SDTM dataset variables
- CDASH model domain variables to SDTMIG dataset variables
- CDASHIG domain fields to SDTMIG dataset variables
- CDASHIG domain fields to SDTM class variables
- CDASHIG scenario fields to SDTMIG dataset variables
To accommodate the different types of mapping targets, three JSON array attributes had to be defined:
Variables in the SDTM occasionally have expanded text to describe a variable's role. This text is stored in "roleDescription" in the metadata repository. Otherwise, "roleDescription" matches "role", where "role" has a set of controlled values. Below is an example for the SDTM v1.5 variable SVUPDES:
Some Implementation Guide variables have multiple CDISC Controlled Terminology codelists. Therefore, an array object is used to output codelist metadata in an API response. For example, this is an excerpt when querying the SENDIG v3.1 variable MISTRESC:
To promote consistency, the label "ISO 3166-1 Alpha-3" is used whenever this external country codelist is referenced. Similarly, "ISO 21090 NullFlavor enumeration" is used for null flavors.