Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Template updates and JIRA FDA comments
Page properties
Title

4-Stair Ascend (4-STAIR ASCEND)

CDISC Reference

Functional Test Supplement to the Study Data Tabulation Model Implementation Guide for Human Clinical Trials

QRS Short Name

4-STAIR ASCEND

QRS Permission StatusPublic Domain
TeamDuchenne Muscular Dystrophy (DMD) Standards Team and CDISC Questionnaires, Ratings, and Scales (QRS) Subteam
Supplement Version1.0
StatusDRAFT
Date20222023-0608-1525
NotesThis supplement is intended available to be used with other CDISC user guides for specific therapeutic/disease areas and follows the CDISC Study Data Tabulation Model Implementation Guide for Human Clinical Trials.

...

Revision History

DateVersion
20222023-0608-1525
1.0 Draft

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

...

CDISC specifies how to structure the data that data that has been collected in a database, not what should be collected or how to conduct clinical assessments or implement protocols. CDISC disclaims any liability for your use of this material.

Although the United States Food and Drug Administration (US FDA) has provided input with regard to this supplement, this input does not constitute US FDA endorsement of any particular instrument.

...

CDISC believes this instrument to be in the public domain, but you should perform your own assessment. CDISC has included the 4-STAIR ASCEND in the library CDISC inventory of QRS data standards supplements. Hence, CDISC developed FTTESTCD and FTTEST for each item based on the actual text on the instrument

Jira
showSummaryfalse
serverIssue Tracker (JIRA)
serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
keyQRSSUPP-605
. There may be many versions of this instrument in the public domain or copyrighted. CDISC has chosen to use this version as the data standard.

...

  1. The numerical value for the time to complete the 4-STAIR ASCEND is recorded using ISO 8601 format in FTORRES and FTSTRESC. Because ISO 8601 format is a text format, there are no standard numeric scores or units. The sponsor enters the time on the CRF in minutes and seconds according to their protocol. (e.g., 1 minute 10 seconds is represented in the FT domain in ISO 8601 format as "T1M10S")
  2. For the test grade (where FTTESTCD = "A4STR104"), FTORRES is populated with the text description. The numeric rating is represented in FTSTRESC and FTSTRESN.

  3. If the entire instrument was not done, the first question on the CRF represents the reason the entire instrument was not done. If the reason not done is provided, then FTSTAT = "NOT DONE" and FTREASND is equal to the text written on the form for all the test codes. 

    1. If the test was not done due to disease, the record where FTTESTCD = "A4STR101" will have FTORRES and FTSTRESC equal to "No, Due to disease under study" and the test grade (FTTESTCD = "A4STR104") will be represented with a value of 1 = "Unable to walk independentlyclimb up 4 standard stairs"

      Jira
      showSummaryfalse
      serverIssue Tracker (JIRA)
      serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
      keyQRSSUPP-608
      .

  4. Some items on the 4-STAIR ASCEND may be logically skipped conditionally branched per the instrument instructions. If the test was not done because of disease, FTTESTCD = "A4STR102" and "A4STR103" are not done and are treated as logically skipped conditionally branched items. A record is created in ft.xpt for all items. When an item is considered a logically skipped conditionally branched item, it is represented as follows:

    1. FTSTAT QNAM = "FTCBRFL", QLABEL = "NOT DONE"     Conditionally Branched Item Flag", QVAL = "Y" (this is a FT supplemental qualifier variable related to the record).FTREASND = "LOGICALLY SKIPPED ITEM"

      Jira
      showSummaryfalse
      serverIssue Tracker (JIRA)
      serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
      keyQRSSUPP-609

    2. FTORRES, FTSTRESC, and FTSTRESN are set to null (missing).

    5. Terminology:
    1. FTCAT, FTTESTCD, and FTTEST values are included in CDISC Controlled Terminology.

    2. A full list of value sets for result and units fields is provided in Section 4, SDTM Mapping Strategy.

...

The 4-STAIR ASCEND example below shows the terminology used to implement the instrument in the FT domain. This example shows the data for 1 subject collected at the baseline visit for the 4-STAIR ASCEND instrument, and data for 2 subjects who did not perform the test, 1 who refused and 1 who could not do the test because of disease progression. The example uses CDISC Controlled Terminology for FTTESTCD, FTTEST, FTORRESU, FTSTRESU,

Jira
showSummaryfalse
serverIssue Tracker (JIRA)
serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
keyQRSSUPP-610
and FTCAT. All original results, matching the CRF item response text, are represented in FTORRES. This result is then represented as a standard numeric score in FTSTRESN and as a standard character representation in FTSTRESC.

...

This section is used for reference regarding the CRF data capture and to understand the alignment of the instrument to the SDTM FT domain. It also provides guidance on how the result and unit variables

Jira
showSummaryfalse
serverIssue Tracker (JIRA)
serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
keyQRSSUPP-612
(FTORRES, FTSTRESC, and FTSTRESN) should be populated.

...