Versions Compared

Key

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

...

Info
titleNews and updates
  • 2020-0811-06: Added to Search section, a clarification about scope phrase "Value Domain"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

General


Section
bordertrue


Column

Text in an CDISC Note (in the SDTMIG) or Description (in the SDTM) may not be identical to the original publication due to differences in newlines, curly quotation marks, non-ASCII, and other special characters. This is done to better align with data exchange mechanisms (e.g., XML, CDISC ODM), as well as to avoid system compatibility issues. This is most notable in early PDF publications such as the SDTM, the SDTMIG, and the CDASHIG.


...

Section
bordertrue


Column

When an enumerated value domain is relevant in an XML media type response (also known as value list), individual member terms will be in its own XML element <value> . Value lists are most common in SDTMIG and ADaMIG products. For example, an excerpt from ADaMIG OCCDS v1.0' SMQzzC variable:

Code Block
languagexml
linenumberstrue
<?xml version="1.0" encoding="utf-8"?>
<cdiscLibrary>
    <analysisVariable>
        <ordinal>96</ordinal>
        <name>SMQzzSC</name>
        <label>SMQ zz Scope</label>
        ...
        <valueList>
            <value>BROAD</value>
            <value>NARROW</value>
        </valueList>
        ...



...

Section


Section
bordertrue


  • Text searching is case-insensitive.
  • Query parameter names and operators are case-sensitive.
  • It is important to note the requirement about character escaping and URL encoding when constructing the URL for search. Visit Character Escaping and URL Encoding section in Search (2020-02-14) for details.

    Column

    Status
    colour

    Green

    Yellow
    title

    New
    Updated
    Refer to Search (Copy) for details

    The scope phrase "Value Domain" (or, "valueDomain" from /mdr/search/scopes") is referred to described value domains (describedValueDomain) found in various SDTM, SEND, and ADaM variables

    .



    Section
    bordertrue


    Column

    type is one of the scopes supported. Both "SDTM Dataset" and "SDTM Dataset Variable" are pre-aggregated for type. To limit search for just SDTM Dataset, use the negation operator, i.e., hyphen (0x2D):

    Code Block
    linenumberstrue
    /mdr/search/?q={searchExpression}type:SDTM Dataset -Variable



    ...

    Section

    Controlled Terminology


    Section
    bordertrue


    New
    Column
    Status
    colourGreen
    title

    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

    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


    Column

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



    Section

    ADaM


    Section
    bordertrue


    Column

    For the ADaMIG, text such as "One record per subject" is used to describe an ADaM data structure concept. Actual structures used in submission datasets are defined based on study specific criteria. For example, users will get this as part of the API response when querying about the ADaMIG OCCDS v1.0:

    Code Block
    linenumberstrue
    "ordinal": "1", 
    "name": "OCCDS", 
    "label": "Occurrence Data Structure", 
    "description": "One record per record in SDTM domain (optional: per coding path, per Analysis Period and/or Phase)", 
    "class": "OCCDS", 
    ...



    ...