All content on this Wiki is non-binding and any individual opinions expressed should not be considered indicative of the policies or positions of CDISC or any other organization.
Page tree

Versions Compared

Key

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

...

Info
titleNews and updates
  • 2021-03-30: Added a section about handling CDISC CT's extensible codelist attribute
  • 2020-11-11: Document revision with new and updated information
  • 2020-07-07: New Controlled Terminology section
  • 2020-02-14: Document revision with new and updated information

  • Expand
    titleHistory Prior to 2020...

    2019-07-18: Document revision with new and updated information
    2019-04-10: Document revision with new and updated information
    2019-02-15: Initial version


...

Section


Section
bordertrue


Updated
Column
Status
colourYellow
title

Refer to Search (Copy) for details.


...

Section
bordertrue


Column

P41a is an interim, out-of-cycle publication, released on 2020-05-08 in conjunction with the Interim User Guide for COVID-19. All new and updated terms are subsumed in the P42 (2020-06-26) publication. P41a is not loaded into CDISC Library.



Section
bordertrue


Column

Status
colourGreen
titleNew
Some codelists have "N/A" in the Extensible attribute. This is common in the Glossary and Protocol packages. For backward compatibility, CDISC Library maintains this as a Boolean attribute. The use of "N/A" is intentionally a close concept to "No". With those, the Data Standard Browser displays "No" in this case, while the API shows false for the extensible object in the JSON response.



Section

CDASH


Section
bordertrue


Column

In the CDASHIG v2.0 and v2.1, Data Scenario and Implementation Options are two independent columns. Implementation Options is not a concept in the CDASHIG v1.1. In order to offer one common API design for all CDASH products, these two columns are combined to become one single attribute. Example: This is an API response excerpt showing the two scenarios for domain DA:

Code Block
linenumberstrue
"scenarios": [ 
  { 
    "href": "/mdr/cdashig/2-0/scenarios/DA.Denormalized", 
    "title": "DA - Denormalized - Implementation Options: Horizontal-Example", 
    "type": "CDASH Scenario" 
  }, 
  { 
    "href": "/mdr/cdashig/2-0/scenarios/DA.HorizontalGeneric", 
    "title": "DA - Implementation Options: Horizontal-Generic", 
    "type": "CDASH Scenario" 
  }, 
  ...



...

Section
bordertrue


Column

For the SDTMIG and the SENDIG, the general observations class serves as a container for Interventions, Events, and Findings classes. Datasets belong to their respective general observation classes, such as Exposure (EX) to Interventions, Adverse Events (AE) to Events, and Laboratory Test Results (LB) to Findings. Therefore, no datasets will be listed under General Observations Class in the API response. In other words, when applying this JSON Path against the response from /mdr/sdtmig/{version}, it yields an empty result: $..classes[?(@.name=="General Observations")].datasets.

They are available in each of the three general observation classes. For example, an excerpt from the API response for this query /mdr/sdtmig/3-2/classes/Events:

Code Block
linenumberstrue
"datasets": [ 
  { 
    "ordinal": "10", 
    "name": "AE", 
    ... 
  }, 
  { 
    "ordinal": "11", 
    "name": "CE", 
    "label": "Clinical Events", 
    ... 
  }, 
  { 
      "ordinal": "12", 
      "name": "DS", 
      "label": "Disposition", 
    ... 
  }, 
  ... 
]




Section
bordertrue


New
Column
Status
colourGreen
title

In the Table 2.2.2 Events of SDTM v1.3, the variable --PRESP is said to be a Variable Qualifier of --TRT. However, --TRT is not valid in the Events class. Due to this typographical error, qualifiesVariables no longer appears in the response from this API request: /mdr/sdtm/1-3/classes/Events/variables/--PRESP.


...