Versions Compared

Old Version 8

changes.mady.by.user Anthony Chow

Saved on

compared with

New Version 9

changes.mady.by.user Anthony Chow

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleNews and updates
  • 2020-02-14: New contents, new endpoints, editorial updates
  • 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

...

Section
bordertrue


Column

The URL for Data Standards Browser is:

Code Block
linenumberstrue
https://library.cdisc.org/browser



...

Section
bordertrue


Column

Status
colourYellow
titleUpdated
The following standards have been loaded:

  • CDISC Controlled Terminology P19 (2014-09-26) to P39 P40 (2019-0912-2720)*, a total of 21 22 quarters with 77 83 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, 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 20192020-1102-18 14 release



Section
bordertrue


Column

Status
colourYellow
titleUpdated
Included in the 20192020-1102-18 14 release are these categoriesstandards:

New contents

  • SDTM CDASH Model v1.8SENDIG-AR v1.01
  • CDASHIG v2.1
  • CDISC Controlled Terminology P39

Enhancements

  • Content for the Controlled Terms, Codelist or Format column is now populated in the CSV and Excel outputs for all applicable SDTM, SDTMIG, and SENDIG foundational standards. This column matches the text in published documents.
  • For all ADaMIGs, added the model they implement, i.e., JSON path $._links.model

Corrections & Patches

  • Data Standard Browser v1.1.4, addressing minor UI display issues in Internet Explorer 11.
  • For CDASH Model v1.0 and CDASHIG v1.1, updated domain AE label from "Adverse Event" to "Adverse Events".
  • For SDTM v1.6, removed MedDRA as described value domain from Events observation class variables.
  • For SDTMIG v3.1.2, removed extraneous newline characters from within the description.
  • For SDTMIG-MD v1.0, updated version from "1-1" to "1.1"
  • For SENDIG v3.0, updated short name from "SENDIG 3.0" to "SENDIG V3.0".
Section
bordertrue
  • P40, including the new Define-XML CT
  • ADaMIG v1.2

Enhancements

  • Added two endpoints (details below):
    • /mdr/about
    • /mdr/lastupdated

Corrections & Patches

  • Amended API documentation with these previously omitted endpoints:
    • /mdr/cdash/{version}/classes/{class}/domains
    • /mdr/root/cdash/domains/{domain}/fields/{field}



Section
bordertrue


Column

For health check, use this endpoint to verify LDAP and database availability:

Code Block
linenumberstrue
/health




Section
bordertrue


Column

For a machine-readable method to obtain a full listing of products loaded into the metadata repository use:

Code Block
linenumberstrue
/mdr/products

Or, by product group:

Code Block
firstline2
linenumberstrue
/mdr/products/{product-group}

where product-group is one of these values:

  • Terminology
  • DataCollection
  • DataTabulation
  • DataAnalysis



For health check, use this endpoint to verify LDAP and database availability:

Section
bordertrue


Column

Status
colourGreen
titleNew
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.

Code Block
linenumberstrue
/mdr/about

/mdr/lastupdated returns dates of last updated, organized by CDISC product group.

Code Block
linenumberstrue
/mdr/lastupdated

For example:

Code Block
title/mdr/about example output
linenumberstrue
{
  "_links": {
    "self": {
      "href": "/mdr/about",
      "title": "Information About CDISC Library",
      "type": "About CDISC Library"
    },
    "lastupdated": {
      "href": "/mdr/lastupdated",
      "title": "Last Update Date of CDISC Library Products",
      "type": "About CDISC Library"
    }
  },
  "release-notes": "https://wiki.cdisc.org/display/LIBSUPRT/Release+Notes",
  "api-documentation": "https://www.cdisc.org/cdisc-library/api-documentation"
}


Code Block
title/mdr/lastupdated example output
linenumberstrue
{
  "_links": {
    "self": {
      "href": "/mdr/lastupdated",
      "title": "Last Update Date of CDISC Library Products",
      "type": "About CDISC Library"
    }
  },
  "overall": "2020-02-14",
  "data-analysis": "2020-02-14",
  "data-collection": "2020-02-14",
  "data-tabulation": "2019-11-18",
  "terminology": "2020-02-14"
}
Column
Code Block
linenumberstrue
/health
Section
bordertrue
Column

For a machine-readable method to obtain a full listing of products loaded into the metadata repository use:

Code Block
linenumberstrue
/mdr/products

Or, by product family:

Code Block
firstline2
linenumberstrue
/mdr/products/{product-family}

where product-family is one of these values:

  • Terminology
  • DataCollection
  • DataTabulation
    • DataAnalysis



     Section
    bordertrue

     Column
    CDISC finished updating all internal (meta-model, URIs, etc.) and textual references of SHARE to CDISC Library. The base URL and API interface remain unaffected. User will find this update mostly in the value of _link/self/title and _links/self/label. For example:
     Code Block
    linenumberstrue
    {
  "_links": {
    "self": {
      "href": "/mdr/products",
      "title": "CDISC Library Product List",
      "type": "CDISC Library Product List"
    },
  ...
}


    ...
     Section
    bordertrue

     Column
    Added to the 2019-07-18 release is the support for two additional media types: CSV and Excel. Users may request top-level foundational standards extract exports in either CSV or Excel Workbook format. The media type for CSV is text/csv, while application/vnd.ms-excel for Excel.
     Note
    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.
    For example, 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:
     Code Block
    languagetext
    linenumberstrue
    curl -X GET \
  https://library.cdisc.org/api/mdr/adam/adam-occds-1-0 \
  -H 'Accept: text/csv'

curl -X GET \
  https://library.cdisc.org/api/mdr/sdtmig/3-3 \
  -H 'Accept: text/csv'


curl -X GET \
  https://library.cdisc.org/api/mdr/ct/packages/sdtmct-2019-06-28 \
  -H 'Accept: text/csv'
    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:
     Code Block
    languagetext
    linenumberstrue
    curl -X GET \
  https://library.cdisc.org/api/mdr/adam/adam-occds-1-0 \
  -H 'Accept: application/vnd.ms-excel'

curl -X GET \
  https://library.cdisc.org/api/mdr/sdtmig/3-3 \
  -H 'Accept: application/vnd.ms-excel'


curl -X GET \
  https://library.cdisc.org/api/mdr/ct/packages/sdtmct-2019-06-28 \
  -H 'Accept: application/vnd.ms-excel'


    ...
     Section
    CDASH

     Section
    bordertrue

     Column
     
     Status
    colourYellow
    titleUpdated
     All instances  of "N/A" in CDASH publications are treated as null in the metadata repositoryof "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.


     Section
    bordertrue

     Column
    In the CDASH Model v1.0 and the CDASHIG v2.0, the CDASH team applied the class concept to all domains. As a result, identifier Identifier and timing variables have class 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 CDASH CDASHIG v1.1 domains. In consequence, "Common variables" (identifier and visit timing variables in Sections 5.1, 5.2) were also instantiated to all CDASH CDASHIG v1.1 domains in order to present the common API design for all CDASH products.
    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.

    ...
     Section
    bordertrue

     Column
    The CDASHIG includes 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:
    • sdtmClassMappingTargets 
    • sdtmDatasetMappingTargets 
    • sdtmigDatasetMappingTargets 


     Section
    SDTM

     Section
    bordertrue

     Column
    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: 
     Code Block
    linenumberstrue
    "ordinal": "11", 
"name": "SVUPDES", 
"label": "Description of Unplanned Visit", 
"description": "Description of what happened to the subject during an unplanned visit. Null for protocol-defined visits.", 
"role": "Qualifier", 
"roleDescription": "Optional Qualifier", 
...


    ...