Page History
...
Date | Version | Summary of Changes |
2013-10-18 | 1.0 | Kurtzke Functional Systems Scores (KFSS) Draft |
2013-11-13 | 1.0 | Kurtzke Functional Systems Scores (KFSS) |
2014-02-19 | 1.1 | Kurtzke Functional Systems Scores (KFSS) Revised
|
2020-06-15 | 2.0 | Converted from Questionnaires (QS) domain to Clinical Classifications Disease Response and Clin Classification (RS) |
© 2020 Clinical Data Interchange Standards Consortium, Inc. All rights reserved.
...
This document describes the CDISC implementation of the Title instrument.the Kurtzke Functional System Scores (KFSS) instrument.
CDISC For CRFs that are NOT created by CDISC, remove this statement: CDISC does not modify questionnaires, ratings, and scales (QRS) instruments to meet Clinical Data Acquisition Standards Harmonization (CDASH) case report form (CRF) standards.
For CRFs that are created by CDISC, use this statement: There is no standard case report form (CRF) available for this instrument. CDISC created this CRF to represent the instrument, which is in the public domain. This is not an endorsement of the instrument. The creation of this instrument was based on input from PASI (TA or instrument) subject matter experts. Sponsors may create this instrument’s CRF using their style guidelines, but they need to maintain the wording and order of the questions/items and responses as described on the CRF. (note that if you use this statement, then QRS is not spelled out for the first time until where noted below.)
The representation of data collected for this instrument is based on the Study Data Tabulation Model Implementation Guide (SDTMIG) Disease Response and Clin Classification (RS) domain model, which can be found on the CDISC website at: https://www.cdisc.org/standards/foundational/sdtmig.
These specific implementation details for this clinical classification are meant to be used in conjunction with the SDTMIG. All CDISC QRS (spell out "questionnaires, ratings, and scales" if this is a CDISC-created CRF and put QRS in parentheses.) documentation packages can be found on the CDISC website at: https://www.cdisc.org/foundational/qrs.
The CDISC Intellectual Property Policy The representation of data collected for this instrument is based on the Study Data Tabulation Model Implementation Guide (SDTMIG) Questionnaires (QS) domain model, which can be found on the CDISC website at: https://www.cdisc.org/standardsabout/foundational/sdtmig.
These specific implementation details for this questionnaire are meant to be used in conjunction with the SDTMIG. All CDISC QRS (spell out "questionnaires, ratings, and scales" if this is a CDISC-created CRF and put QRS in parentheses.) documentation packages can be found on the CDISC website at: https://www.cdisc.org/foundational/qrs.
The CDISC Intellectual Property Policy can be found on the CDISC website at: https://www.cdisc.org/about/bylaws.
1.1 Representations and Warranties, Limitations of Liability, and Disclaimers
This document is a supplement to the SDTMIG for Human Clinical Trials and is covered under Appendix F of that document, which describes representations, warranties, limitations of liability, and disclaimers. Please see Appendix F of the SDTMIG for a complete version of this material.
CDISC specifies how to structure the data that has been collected in a database, not what should be collected or how to conduct clinical assessments or protocols.
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. (Include this line only for supplements that the US FDA will be reviewing. Please DO NOT MODIFY the sentence.)
2 Copyright Status
For copyrighted instruments use the following text: Name of copyright holder (e.g., Board of Regents of The University of Texas System) owns the copyright for the QRS Short_Name instrument and has granted CDISC permission to include this supplement in the CDISC library of QRS data standards supplements. (For supplements that are to be distributed by the copyright holder, add: Name of copyright holder (e.g., Board of Regents of The University of Texas System) will distribute the CDISC supplement package to sponsors when they are approved to use this instrument.) Hence, CDISC developed QSTESTCD and QSTEST for each item based on the actual text on the questionnaire. (For public domain instruments, add: )There may be many versions of this instrument. CDISC has chosen to use this version as the data standard.
For public domain instruments use the following text: This instrument is in the public domain. CDISC has included the QRS Short_Name in the CDISC library of QRS data standards supplements. Hence, CDISC developed QSTESTCD and QSTEST for each item based on the actual text on the questionnaire. 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.
The CDISC documentation of this instrument consists of: (1) controlled terminology, (2) standard database structure with example(s), and (3) CRF(s) annotated with the CDISC SDTMIG variables with submission values.
Info | ||
---|---|---|
| ||
The CRF is attached at the top of the Wiki. When you click the paperclip image, you will find the file for the annotated CRF. |
Note: CDISC Controlled Terminology is maintained by National Cancer Institute (NCI) Enterprise Vocabulary Services (EVS). The most recent version should be accessed through the CDISC website at: https://www.cdisc.org/standards/terminology.
Info |
---|
Include the following statements as standalone paragraphs for copyrighted instruments: CDISC has developed this documentation at no cost to the copyright holder or any additional cost to users of the instrument beyond the normal license fees charged by the copyright holder. CDISC acknowledges [insert the name of the copyright holder, in blue text] (e.g., Dr. A. J. Rush, at the UT Southwestern Medical Center) for the approval to include the QRS Short_Name in the CDISC data standards. |
Reference for the QRS Short_Name:
Rush, A.J., Carmody, T. and Reimitz, P.E. The Inventory of Depressive Symptomatology (IDS): Clinician (IDS-C) and self-report (IDS-SR) ratings of depressive symptoms. International Journal of Methods in Psychiatric Research, 9:45-59, 2000.
Info |
---|
This is an example only. Use the reference from the CDISC definition of the --CAT.
If there are multiple references, please use the following format: References for the Title:
|
Info |
---|
Notes on the use of quotation marks:
|
3 The QS Domain Model
3.1 Assumptions for the QS Domain Model
All assumptions and business rules described in the SDTMIG QS domain are applicable to this supplement. Additional assumptions specific to the QRS Short_Name are listed below.
The QRS Short_Name is a multiple-choice questionnaire 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.
Include a description of scale score or other possible responses (You may need multiple numbered points for this, tho the IDS-SR did not.). For scale scores use the following language: The scale points 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.
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.: The time period of evaluation for the QRS Short_Name is populated in the QSEVLINT field in ISO 8601 format (or QSEVINTX, as appropriate) when the evaluation interval can be precisely described as duration. The evaluation interval for the QRS Short_Name is the past 7 days (QSEVLINT = "-P7D").
- 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.
If the instrument standards currently being developed includes logically skipped items, insert: 'Some items on the QRS Short_Name may be logically skipped per the instrument instructions. Language to be used for this assumption is currently under review.'
This language is currently under review. Remove this point if it does not apply.: Some items on the QRS Short_Name may be logically skipped per the instrument instructions. Responses for logically skipped items should be (1) recorded and/or scored according to the instructions provided in the instrument’s user manual, scoring manual, or other documentation provided by the instrument developer and (2) included in the submission dataset. If such instructions are not available, then records for logically skipped items should be included in the submission dataset with:· QSSTAT = NOT DONE;· QSREASND = LOGICALLY SKIPPED ITEM; and· QSORRES, QSSTRESC, and QSSTRESN all set to nullWhen submitting data to US FDA or some other regulatory authority to support regulatory review of a medical product, if the electronic data collection system is not capable of automatically populating records for logically skipped items, these records should be post-populated prior to submission and the sponsor will need to explain this in the corresponding reviewer's guide.Include this point if score(s) are submitted to SDTM. Update blue text: The QRS Short_Name instrument includes a total score (and other scores as needed. If so, change "that is" to "that are") that is considered as captured data on the CRF and is not considered as derived in the example below.
If operationally defined by the sponsor, it is the sponsor's responsibility to set the --DRVFL flag based on their eCRF process to derive subtotals and total scores. An investigator-derived score written on a CRF will be considered a captured score and not flagged. When subtotal and total scores are derived by the sponsor, the derived flag (--DRVFL) is set to Y. However, when the subtotal and total scores are received from a central provider or vendor, the value would go into --ORRES and --DRVFL would be null (see SDTMIG Section 4.1.8.1, Origin Metadata for Variables).
This language is currently under review. Evaluator information is only to be included when the information is collected directly on the CRF. Questionnaires will no longer be using QSEVAL/QSEVALID; however RSEVAL/RSEVALID and FTEVAL/FTEVALID will continue to be used on Clinical Classifications and Functional Tests. Language for Clinical Classifications and Functional tests follows; language for questionnaires is currently under review. Remove this point if it does not apply.
For Clinical Classifications and Functional Tests (only when collected on the CRF): *** This section to be updated. QSEVAL/ID, FTEVAL/ID, and RSEVAL/ID will no longer be used. Supplemental qualifiers will represent this information. *** For QRS Short_Name, the evaluator is defined as the (the appropriate term from controlled terminology). Alternatively, if only evaluator name or initials could be collected: For QRS Short_Name, sponsors should follow their internal data management procedures on representing the name or initials of the evaluator. CDISC Controlled Terminology is available for Evaluator (e.g., --EVAL = "HEALTH CARE PROFESSIONAL") and Medical Evaluator (e.g., --EVALID = "RATER 1"). To reiterate, only include this point if the evaluator/administrator is collected directly on the CRF.
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.
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.
Terminology
QSCAT, QSTESTCD, and QSTEST (and other variables such as QSORRESU as needed) values are included in CDISC Controlled Terminology.
A full list of value sets for the qualifier, timing, result, and 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.)
3.2 Example for the QRS Short_Name QS Domain Model
The QRS Short_Name example below shows the terminology used to implement the instrument in the QS domain. This example shows the data for 1 subject collected at the baseline visit for the QRS Short_Name instrument. The example uses CDISC Controlled Terminology for QSTESTCD, QSTEST, and QSCAT. All original results are represented with preferred terminology in QSORRES. This result is then transformed into the standard numeric score in QSSTRESN and a character representation of the standard numeric score in QSSTRESC.
Info |
---|
Note: There are several optional space-saving options that can be included in the paragraph as appropriate or needed. Historically, we needed these to save space in Word/PDF documents. As we move to all wiki/html, these are likely not needed, but we are waiting to remove these options until we're sure:
|
Info |
---|
Update the data in the table below to the current instrument. Include row descriptions as needed to highlight idiosyncrasies or items otherwise of note in this particular instrument. If there are only a few row descriptions, information should be included in the text prior to the example instead of in separate row headers. |
Info |
---|
We are unable to make the example consistently show blue in the Wiki. All examples are updated for each QRS instrument so we ask that you please review the example below. |
...
Name | qs |
---|
...
The following is for illustrative purposes and would not really be included for the IDS-SR instrument in this template. It provides an example of what would need to be included if the instrument required supplemental qualifiers (see Section 5 Supplemental Qualifier Name Codes):
Text that would remain unchanged has been left in black:
The evaluation interval text value for data collection needs to be populated in SUPPQS as follows. The standard terminology for QNAM and QLABEL are listed below.
...
Name | suppqs |
---|
...
4 SDTM Mapping Strategy
This section is used for reference regarding the CRF data capture and to understand the alignment of the instrument to the SDTM QS domain. It also provides guidance on how the result variables (QSORRES, QSSTRESC, and QSSTRESN) should be populated.
Info |
---|
Include mappings for all sets of result values. For ease of use of this template, the complete set of response values for the example in Section 3.2 is not included. If the instrument has been entered into QRS Maker (all instruments should be), then the complete set of response values can be copied from QRS Maker and pasted into this supplement. Some example mappings are below. |
...
For QRS instruments with subcategories:
When subcategories are used on an instrument, a table with the following introduction information should appear before the mappings for results.
QSSCAT alignment with QSTESTCD
As stated in Section 3.1 assumptions, items on the QRS Short_Name are grouped into subcategories. The table below includes the subcategory names along with the applicable item numbers for each category. The values of the subcategories are used to populate QSSCAT and are annotated on the CRF.
...
If all items have the same original result values, with the same standardized character and numeric values, then only include one table showing the values of QSORRES/QSSTRESC/QSSTRESN and put "All QSTESTCDs" (title case "All", and in quotes) above the table:
"All QSTESTCDs"
...
Similarly, if some, but not all, QSTESTCDs share the same original result and standardized values, then the QSTESTCD and corresponding QSTEST values are put in a list above the table rather than providing a separate table for each QSTESTCD/QSTEST.
...
If there are responses that correspond to non-consecutive items or 1-7 consecutive items, include the test codes and test names above the table with the responses as follows:
QSTESTCD = "test code 1" QSTEST = "test name 1"
QSTESTCD = "test code 4" QSTEST = "test name 4"
QSTESTCD = "test code 5" QSTEST = "test name 5"
QSTESTCD = "test code 6" QSTEST = "test name 6"
QSTESTCD = "test code 7" QSTEST = "test name 7"
QSTESTCD = "test code 8" QSTEST = "test name 8"
QSTESTCD = "test code 15" QSTEST = "test name 15"
QSTESTCD = "test code 22" QSTEST = "test name 22"
QSTESTCD = "test code 27" QSTEST = "test name 27"
QSTESTCD = "test code 29" QSTEST = "test name 29"
1.1 Representations and Warranties, Limitations of Liability, and Disclaimers
This document is a supplement to the SDTMIG for Human Clinical Trials and is covered under Appendix F of that document, which describes representations, warranties, limitations of liability, and disclaimers. Please see Appendix F of the SDTMIG for a complete version of this material.
CDISC specifies how to structure the data that has been collected in a database, not what should be collected or how to conduct clinical assessments or protocols.
2 Copyright Status
This instrument is in the public domain. CDISC has included the Kurtzke Functional System Scores (KFSS) in the CDISC library of QRS data standards supplements. Hence, CDISC developed RSTESTCD and RSTEST for each item based on the actual text on the clinical classification. 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.
The CDISC documentation of this instrument consists of: (1) controlled terminology, (2) standard database structure with example(s), and (3) CRF(s) annotated with the CDISC SDTMIG variables with submission values.
Info | ||
---|---|---|
| ||
The CRF is attached at the top of the Wiki. When you click the paperclip image, you will find the file for the annotated CRF. |
Note: CDISC Controlled Terminology is maintained by National Cancer Institute (NCI) Enterprise Vocabulary Services (EVS). The most recent version should be accessed through the CDISC website at: https://www.cdisc.org/standards/terminology.
Info |
---|
Include the following statements as standalone paragraphs for copyrighted instruments: CDISC has developed this documentation at no cost to the copyright holder or any additional cost to users of the instrument beyond the normal license fees charged by the copyright holder. CDISC acknowledges Kurtzke JF. Rating neurologic impairment in multiple sclerosis: an expanded disability status scale (EDSS). Neurology. 1983 Nov;33(11):1444-52 for the approval to include the Kurtzke Functional System Scores (KFSS) in the CDISC data standards. |
Reference for the Kurtzke Functional System Scores (KFSS):
Info |
---|
This is an example only. Use the reference from the CDISC definition of the --CAT.
If there are multiple references, please use the following format: References for the Title:
|
Info |
---|
Notes on the use of quotation marks:
|
3 The RS Domain Model
3.1 Assumptions for the RS Domain Model
All assumptions and business rules described in the SDTMIG RS domain are applicable to this supplement. Additional assumptions specific to the Kurtzke Functional System Scores (KFSS) are listed below.
Kurtzke Functional Systems Scores (KFSS): The KFSS consists of 7 functional systems (plus “other”) with an ordinal clinical rating scale for each. The functional systems included in the KFSS are the pyramidal, cerebellar, brain stem, sensory, bowel/bladder, visual, cerebral, and other functions. In addition to the functional system rating scales, there are 2 additional questions asking about weakness and temporal pallor, which could affect the ratings.
- For each functional system of the KFSS, the scale points include a numeric rating (e.g. “0”) and a description of what is represented by the rating (e.g. “Normal”) with the exception of the “Unknown” option, which does not have a numeric rating. QSORRES is populated with the rating description. For the options with a numeric rating, QSSTRESC and QSSTRESN are populated with the numeric rating. Otherwise, QSSTRESC is populated with the rating description and QSSTRESN is left blank.
- For item KFSS104, one of the rating definitions is longer than the 200 character limit imposed by SAS v5 transport files. The QS sub-team has paraphrased the text to shorten the responses. The original and modified values are summarized in Section 5.
- Items KFSS102A and KFSS106A have the instruction “check here” when the subject has the specified condition (weakness, temporal pallor). QSORRES and QSSTRESC = “CHECKED” or “NOT CHECKED”. QSSTRESN is always left blank.
- Item KFSS108A will only be answered if KFSS108 has QSORRES = “Any other neurologic findings attributed to MS (specify)”. If KFSS108A is not answered, do not create a record in SDTM for it.
- Terminology:
- RSCAT, RSTESTCD and RSTEST are approved CDISC controlled terminology.
- A full list of value sets for qualifier and result fields is provided in Section 4: SDTM Mapping Strategy.
Terminology
QSCAT, QSTESTCD, and QSTEST values are included in CDISC Controlled Terminology.
A full list of value sets for the qualifier, timing, result, and unit fields is provided in Section 4, SDTM Mapping Strategy.
3.2 Example for the Kurtzke Functional System Scores (KFSS) Domain Model
The Kurtzke Functional System Scores (KFSS) example below shows the terminology used to implement the instrument in the RS domain. This example shows the data for one subject collected at the baseline visit for a KFSS questionnaire. The subject did not experience weakness that interfered with the testing, but did have temporal pallor. The example uses CDISC controlled terminology for RSTESTCD, RSTEST, and RSCAT. RSBLFL is Y based on VISITNUM=1. All original results are represented with preferred terminology in RSORRES. Typically, this result is then transformed into a standard numeric score in RSSTRESN and a character representation of the standard numeric score in RSSTRESC.
Rows 1-10: Shows the questions from the KFSS form. Note that a record for RSTESTCD=KFSS108A is not shown since RSORRES=“None” for RSTESTCD=KFSS108.
Rows 3 and 8 show RSORRES = “NOT CHECKED” and “CHECKED”, respectively, since the subject did not experience weakness that interfered with the testing and the subject had temporal pallor.
rs.xpt
Row | STUDYID | DOMAIN | USUBJID | RSSEQ | RSTESTCD | RSTEST | RSCAT | RSORRES | RSSTRESC | RSSTRESN |
1 | STUDYX | RS | P0001 | 1 | KFSS101 | KFSS1-Pyramidal Functions | KFSS | Minimal disability | 2 | 2 |
2 | STUDYX | RS | P0001 | 2 | KFSS102 | KFSS1-Cerebellar Functions | KFSS | Severe ataxia, all limbs | 4 | 4 |
3 | STUDYX | RS | P0001 | 3 | KFSS102A | KFSS1-Weakness Interferes With Testing | KFSS | NOT CHECKED | NOT CHECKED |
|
4 | STUDYX | RS | P0001 | 4 | KFSS103 | KFSS1-Brain Stem Functions | KFSS | Normal | 0 | 0 |
5 | STUDYX | RS | P0001 | 5 | KFSS104 | KFSS1-Sensory Functions | KFSS | Vibration or figure-writing decrease only, in one or two limbs | 1 | 1 |
6 | STUDYX | RS | P0001 | 6 | KFSS105 | KFSS1-Bowel and Bladder Functions | KFSS | Frequent urinary incontinence | 3 | 3 |
7 | STUDYX | RS | P0001 | 7 | KFSS106 | KFSS1-Visual or Optic Functions | KFSS | Grade 5 plus maximal visual acuity of better eye of 20/60 or less | 6 | 6 |
8 | STUDYX | RS | P0001 | 8 | KFSS106A | KFSS1-Presence of Temporal Pallor | KFSS | CHECKED | CHECKED |
|
9 | STUDYX | RS | P0001 | 9 | KFSS107 | KFSS1-Cerebral or Mental Functions | KFSS | Unknown | Unknown |
|
10 | STUDYX | RS | P0001 | 10 | KFSS108 | KFSS1-Other Functions | KFSS | None | 0 | 0 |
rs.xpt (cont)
Row | RSBLFL | VISITNUM | RSDTC |
1 (cont) | Y | 1 | 2012-11-16 |
2 (cont) | Y | 1 | 2012-11-16 |
3 (cont) | Y | 1 | 2012-11-16 |
4 (cont) | Y | 1 | 2012-11-16 |
5 (cont) | Y | 1 | 2012-11-16 |
Info | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The following is for illustrative purposes and would not really be included for the IDS-SR instrument in this template. It provides an example of what would need to be included if the instrument required supplemental qualifiers (see Section 5 Supplemental Qualifier Name Codes): Text that would remain unchanged has been left in black: The evaluation interval text value for data collection needs to be populated in SUPPQS as follows. The standard terminology for QNAM and QLABEL are listed below.
|
4 SDTM Mapping Strategy
This section is used for reference regarding the CRF data capture and to understand the alignment of the instrument to the SDTM RS domain. It also provides guidance on how the result variables (RSORRES, RSSTRESC, and RSSTRESN) should be populated.
Do I copy from the legacy document or from QRS maker?
what should be done for section 5? the legacy document has a table.
...
Omit the QSSTRESN column when it is not applicable to the dataset.
QSTESTCD = "test code" QSTEST = "test name"
...
For responses that are for 8 or more consecutive items, an override label should be used in QRS Maker to show the items that are included as follows:
QSTESTCD = "first test code in sequence" QSTEST = "first test name in sequence" through
QSTESTCD = "last test code in sequence" QSTEST = "last test name in sequence"
...
5 Supplemental Qualifier Name Codes
...