Page History
...
Page properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Date | Version | Summary of Changes | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
2021-0811-2722 | 2.0 Revision Draft |
| ||||||||||
2016-03-24 | 1.0 | Final - Updated per Evidera instructions. They have trademarked the EXACT® and updated the name of the E-RS™: COPD. |
...
The scale points include a text rating (e.g., "Not at all", "Slightly", etc.).
The E-RS (EXACT-Respiratory Symptoms)* USER MANUAL (Version 4.0) May 2015 that is provided upon user's receiving copyright permission provides the numeric scoring of the responses for the questions. Based on this being copyrighted, the numeric scores cannot be provided in this supplement. Upon receiving permission, sponsors must apply these numeric responses in their SDTMIG and ADaM datasets. For this EXACT supplement, QSORRES is populated with the text description while the numeric rating is represented as "xxx" in QSSTRESC and QSSTRESN.
Jira showSummary false serverIdserver Issue Tracker (JIRA) 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key QRSSUPP-322
The time period of evaluation for the EXACT is populated in the QSEVINTX field. The evaluation interval for the EXACT is in the past 7 days
(QSEVINTX QSEVINTX = "EVERY EVENING BEFORE BEDTIME" ) as represented on the CRF.Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key QRSSUPP-325 The EXACT instrument includes 3 raw and domain respiratory symptom scores, a raw total score, and an EXACT total score that are not represented on the CRF, but described in the user manual, that are considered as captured data and is not considered as derived in the example below. These scores may be submitted in SDTM or derived in the Analysis Data Model (ADaM) per scoring instructions from the user manual. The E-RS (EXACT-Respiratory Symptoms)* USER MANUAL (Version 4.0) May 2015 that is provided upon user's receiving copyright permission provides information to calculate these items. The EXACT raw total score is computed across the 14 items and then transformed via a table lookup to obtain the EXACT total score that has a theoretical range of 0 to 100. Three raw respiratory symptom scores are also computed for: Breathlessness, Cough & Sputum, and Chest Symptoms. These raw respiratory scores are transformed via a table lookup to obtain the respiratory symptom domain scores that have a theoretical range of 0 to 100.
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 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).
- If scores are received by the sponsor, it is recommended that they are submitted to SDTM and verified in ADaM.
Timing of the EXACT Instrument Diary Collection
- The QRS EXACT instrument diary or manual describes that it is a self-administered daily diary, completed by respondents each evening before bedtime. There is no further information provided with the necessary timing information needed to align the timing to the CDISC QRS domain variables. Any additional information regarding the timing of the diary capture should be described in a protocol.
- The following CDISC timing variables represent the EXACT collection timing.
- VISITNUM variable is represented as a null value since sponsors have different operating procedures to assign visit information relative to diary collection.
- QSDTC variable represents the date/time the diary information was collected by the subject and is used for the timing of this measure.
- QSEVINTX variable represent the evaluation interval text timing described on the instrument relative to diary collection.
- VISITNUM variable is represented as a null value since sponsors have different operating procedures to assign visit information relative to diary collection.
- As described in the user manual, where no diary entry exists for a given day, create a record in the dataset for that collection date. Each day a patient is followed in the study must have a record for the day. For these missing diary days, a record is created for each item with QSORRES, QSSTRESC and QSSTRESN represented with missing values and QSSTAT = "NOT DONE". If a reason for not collecting an item is collected, it is represented in the QSREASND variable. Collecting this reason would be a good practice, but is not specfically described in the manual.
“Presence of Data” items missing data rule:
- A record is created in qs.xpt for all items.
- If the reason for the not done record is collected, then QSSTAT=“NOT DONE” and QSREASND=reason provided (e.g., “PREFER NOT TO ANSWER”). If a reason for the not done record is not collected, the QSREASND variable is not populated,
Terminology
QSCAT, QSTESTCD, and QSTEST values are included in CDISC Controlled Terminology.
A full list of value sets for the result fields is provided in Section 4, SDTM Mapping Strategy.
...
The EXACT example below shows the terminology used to implement the instrument in the QS domain. This example shows the data for 1 subject collected at 7 evenings of diary data capture on the EXACT instrument. The example uses CDISC Controlled Terminology for QSTESTCD, QSTEST, and QSCAT. All original results are represented with preferred terminology in QSORRES. Based on assumption 1. above, the numeric values from the user manual is represented as "xxx" in QSSTRESC and QSSTRESN. There is no baseline observation flag represented, since the user manual describes how to drive
derive and potentially re-derive the baseline EXACT domain and total scores as an analysis variable based on the subject disease status. Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key QRSSUPP-323
...
The table represents the items from the EXACT instrument. The timing of diary collection is explained in assumption 4. Rows 15 - 22 represent the 08-Nov-2012 diary collected raw, domain, and EXACT total scores as described in assumption 3 above. These are also represented for each additonal
diary additional diary collection date. The subject did not fill out the EXACT diary on 09-Nov-2012 and no reason for not collecting the diary was provided. Since the reason for not completing the assessments was not collected, no , but the protocol specified the evaluations to occur nightly for 7 straight days, the collection date is assumed for when the diary collection would have occurred. Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key QRSSUPP-326
included for these missing evaluations. The remaining diary collection follows the same pattern thru Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key QRSSUPP-327
through the completion of the dairy. Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key QRSSUPP-328
...