Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updating year in header and version section

...

Revision History

DateVersion
20232024-mm-dd1.0 Draft

© 2023 Clinical 2024 Clinical Data Interchange Standards Consortium, Inc. All rights reserved. 

Info

For the first version of a supplement, use the above Revision History table and delete this information box.

When a previously published supplement is being revised, a modified "Revision History" table will need to be used. Add a new column at the right called "Summary of Changes" if this is the first revision to the supplement (see table below). Also add a new row under the column headers with the current information, keeping all rows previously added. The bottom row should be for Version 1.0, with subsequent versions added above each of the previous rows.

If you are making changes to a supplement for the first time, put "Initial Final Version" in the Summary of Changes column for Version 1.0. Then add a row above with the new version number (1.1 if the changes are considered minor such as a typo, 2.0 if they are major such as variable changes) and summary of changes.


Revision History

DateVersionSummary of Changes
20232024-mm-ddx.x (e.g., 1.1, 2.0)xxx
2019-mm-dd1.0Initial Final Version

© 2023 2024 Clinical Data Interchange Standards Consortium, Inc. All rights reserved. 

...

The QRS Short_Name is a multiple-choice instrument that clinicians may use to assess the severity of depressive symptoms. It consists of 30 items, each rated on a 4-point scale. A total score between 0-84 is also captured.

  1. Include a description of scale an original score or other possible responses (You may need multiple numbered points for this, though the IDS-SR did not.). For scale scores original scores use the following language: The scale points include original scores include a numeric rating (0-3) and a definition of what is represented by the rating (e.g., 0 = "I never take longer than 30 minutes to fall asleep"). For the QRS Short_Name, QSORRES is populated with the text description while the numeric rating is represented in the standardized character and numeric result variables QSSTRESC and QSSTRESN. (Replace this sentence for instruments with text only responses with “QSORRES and QSSTRESC are populated with the text description and QSSTRESN is not represented with a numeric value”.

  2. Include a description of the evaluation interval if one exists. This may be numeric (QSEVLINT) or text (QSEVINTX). When the evaluation interval is provided in text and cannot be described in ISO 8601 format, use QSEVINTX instead of "QSEVLINT field in ISO 8601 format" and replace "the past 7 days" with the text (e.g., "DAYTIME'". Refer to SDTMIG Section 2.2.5 Timing Variables for All Classes). The evaluation interval needs to be clearly defined on the CRF. Remove this point if it does not apply.: 

    1. If numeric use this wording: The time period of evaluation for theQRS Short_Name is populated in the --EVLINTfield in ISO 8601 format when the evaluation interval can be precisely described as duration. The evaluation interval for the QRS Short_Name is the past 7 days (--EVLINT = "-P7D")

    2. If text use this wording: The time period of evaluation for the QRS Short_Name is populated in the --EVINTX field as an evaluation interval text value, since it cannot be precisely described as an ISO 8601 duration. The evaluation interval for the QRS Short_Name is "LIFETIME" (--EVINTX = "LIFETIME").
  3. If there are subcategories, include a note that subcategories will be represented in QSSCAT. Also provide a list of the subcategories unless one is already provided in the description preceding the assumptions. Remove this point if it does not apply.  For example:  Items are divided into 5 subcategories represented in QSSCAT: "PHYSICAL WELL-BEING", "SOCIAL/FAMILY WELL-BEING", "EMOTIONAL WELL-BEING", "FUNCTIONAL WELL-BEING", and "ADDITIONAL CONCERNS".
  4. Records are created in qs.xpt for every instrument item

    1. For items with no data, QSORRES, QSSTRESC, and QSSTRESN are all missing and QSSTAT = "NOT DONE". If the reason is known then that reason is represented in QSREASND (e.g., QSREASND = "PREFER NOT TO ANSWER"). If the reason is unknown, then QSSTAT = "NOT DONE" and QSREASND is missing.

    2. Due to the variability of copyright holder and public domain derived the derived subscore and overall score generation processes, records are not included for derived subscores or total overall scores that are not provided.
  5. If the instrument standards currently being developed includes conditionally branched items, insert: Some items on the QRS Short_Name may be conditionally branched per the instrument instructions. Only one of the 2 oxygen saturation scales (RSTESTCD = "NEWS102" or "NEWS103") is completed for each subject. The other will be treated as a conditionally branched item. In addition, item RSTESTCD = "NEWS104A" is only completed when the response to RSTESTCD = "NEWS104" is the amount of oxygen received (in L/min). A record is created in rs.xpt for all items. When an item is considered a conditionally branched item, it is represented as follows:

    When assigned with conditionally branched responses are not documented in the instrument’s instructions or a user manual:

    1. QNAM = “QSCBRFL”, QLABEL = “Conditional Branched Item Flag“, QVAL = “Y” (this is a QS supplemental qualifier variable related to the record).
    2. QSORRES, QSSTRESC, and QSSTRESN are set to null (missing).

    When assigned conditionally branched responses are documented in instructions or a user manual:

    1. QNAM = “QSCBRFL”, QLABEL = “Conditional Branched Item Flag“, QVAL = “Y” (this is a QS supplemental qualifier variable).
    2. The QSORRES responses are represented as follows:
      1. For severity items, QSORRES = "None".
      2. For interference items, QSORRES = "Not at all".
    3. If numeric response values are assigned, they are represented here: QSSTRESC = 0 and QSSTRESN = 0.

       or if no numeric responses are assigned: QSSTRESC = NULL and QSSTRESN = NULL.

  6. Include this point if overall score(s) are submitted to SDTM. Update blue  blue text: The QRS Short_Name instrument includes a total score  instrument includes an overall score (and subscores or other scores as needed.  If so, change "that is" to "that are") that is considered as captured data on the instrument and is not considered as derived in the example below.  These scores may These scores may be submitted in SDTM or derived and derived in the Analysis Data Model (ADaM) per scoring instructions from [Insert copyright holder's name or other source.].

    1. Subtotal Subscores and total scores overall scores are represented in--ORRES, --STRESC, and --STRESN.
    2. If subscores or overall scores are received or derived by a central provider or vendor or derived by the sponsor, it is recommended that they are submitted to SDTM and verified in ADaM whenever feasible. It is the sponsors repsonsibility responsibility to do this verification based on the instrument's user manual or instructions from the copyright owner.  If the scoring is proprietary, then wording should be added to that effect to explain that the score is verified in ADaM when feasible.
  7. Please review the decision on not including –EVAL and --EVALID in the QRS Supplement Best Practices topic “--EVAL/–EVALID not included in QRS domains/datasets”.Now we only represent administrative information if it is explicitly collected on an instrument. No assumptions are made for this data; if it's not on the instrument, it's not in the data.

    The SUPPQUAL variables used are a series of non-standard variables that represent collected administrator information, administration device, etc., and these updated SUPPQUAL variables are included in the WIKI non-standard variable registry (Non-standard Variable Registry). For example:

    1. PPRAID which is "Preprinted Administrator Identifier".
    2. COLAVL which is "Collected Administrator Value".

    The supplement version 1.0 of the FAS-NACC UDS V3.0 instrument shows an implementation example.

    The QRS Short_Name instrument collects administrative information as the preprinted examiner’s initials and the collected response. This is represented in the SUPPQUAL variable QNAM = --PPRAID” with QNAM = “Preprinted Administrator Identifier” and QVAL = “EXAMINER’S INITIALS”. The collected initials response is represented with QNAM = “--COLAID” and QNAM = “Collected Administrator Identifier” and QVAL = “ADM1”.

    This is part of the data example for the SUPPQUAL variables.

    The SUPPRS table represents the preprinted and collected administrative items represented on the CRF. 

     supprs.xpt

    STUDYID

    RDOMAIN

    USUBJID

    IDVAR

    IDVARVAL

    QNAM

    QLABEL

    QVAL

    QORIG

    STUDYX

    RS

    100-10001

    RSCAT

    FAS-NACC UDS V3.0

    RSPPRAID

    Preprinted Administrator Identifier

    EXAMINER'S INITIALS

    CRF

    STUDYX

    RS

    100-10001

    RSCAT

    FAS-NACC UDS V3.0

    RSCOLAID

    Collected Administrator Identifier

    ADM1

    CRF

  8. Include this point if there are comments at the end of the instrument. Remove this point if it does not apply.: Comments located at the end of the QRS Short_Name will be recorded in the Comments domain (CO). All assumptions and business rules described in the SDTMIG CO domain are applicable.

  9. Include this point if there are responses over 200 characters. Remove this point if it does not apply: Some responses to the QRS Short_Name items exceeded the 200-character limit for the QSORRES variable and needed to be reduced to fewer than 200 characters. Section 4, SDTM Mapping Strategy, indicates which item responses were revised in order to fit the 200-character limit.

  10. Terminology

    1. QSCAT, QSTESTCD, QSTEST, QSORRES, QSSTRESC, and QSSTRESN (and other variables such as QSORRESU as needed; only include QSORRES, QSSTRESC, and QSSTRESN if the responses are published in CT with public domains instruments) values are included in CDISC Controlled Terminology.

    2. A full list of value sets for the qualifier, timing, resultand unit fields is provided in Section 4, SDTM Mapping Strategy. (Note: Only the result field is always used. Include qualifier, timing, and unit fields as needed and remove this note.)

...