Instructions on how to use this template
- Copy ADQRS QS Template pages to the Initial development (Not ready for internal review). Please DO NOT OVERWRITE the template pages.
- Change the title of the page as follows:
- Remove 'Copy of ADQRS QS Template - '. The new title should begin with 'ADaM ADQRS Short_Name...'.
- Change 'ADQRS Short_Name' to the short name (QSCAT) for the current measure.
- This change needs to be done in the title as well as throughout the document.
- The version number will be 'v1' if there has never been a supplement for the measure before. Otherwise, increment as appropriate.
- When copyrighted instruments are used, 'Public domain' will need to be changed to 'Approved'. Note that the copyright approval must allow for the creation of analysis supplements.
- Replace 'ADQRS Long_Name' and 'ADQRS Short_Name' with the long and short name of the measure that the supplement is being created for.
- Replace royal blue text with information pertaining to the measure the supplement is being created for. Delete royal blue text which does not apply to the new measure. Unless otherwise noted, text in black applies to all QRS Questionnaire Supplements and should not be deleted.
Remove all information blocks, except for the one immediately below this called 'Information for Reviewers'.
Keep changes in blue for ease throughout internal and public review. Once the supplement has gone thru public review and all comments are resolved, change all text color to black except for hyperlinks.
Information for Reviewers
Text in black is part of the template used to create this document and is not under review. Please review the blue text; this text represents the changes made to the template that are specific to this QRS instrument.
Revision History
Date | Version |
---|---|
2023 (update whenever text is modified below, even during development) | 1.0 Draft |
© 2023 Clinical Data Interchange Standards Consortium, Inc. All rights reserved.
1 General Considerations
This section describes the implementation of the analysis dataset for QRS instruments as based on the Basic Data Structure (BDS) described in the Analysis Data Model Implementation Guide (ADaMIG). The ADaMIG can be found on the CDISC website at https://www.cdisc.org/standards/foundational/adam. The BDS was chosen as the model for analysis datasets of QRS instruments because it supports a wide variety of analyses, including summaries of total score by timepoint as well as change from baseline by timepoint. This data structure allows the ADaM variables PARAM and PARAMCD to come directly from Study Data Tabulation Model (SDTM) variables RS.RSTEST and RS.RSTESTCD, respectively, for individually captured questions, thus ensuring traceability between SDTM and ADaM data. If other analyses are required that are not supported by the BDS, then consideration would be needed as to the appropriate structure. Analysis requirements always drive the design of the analysis datasets.
This ADaM supplement is based on the Acute Physiology and Chronic Health Evaluation II (APACHE II) Clinical Classification Supplement Version 1.1 to the SDTM Implementation Guide for Human Clinical Trials (SDTMIG).
Note that source SDTM score values may not be suitable for analysis because the values may need to be imputed or transformed. In addition, recalculation of collected values may be needed per analysis rules. In these cases, the derivation of AVAL may not be a simple copying of RS.RSSTRESN.
These specific analysis implementation details for the APACHE II are meant to be used in conjunction with ADaMIG. All completed questionnaires, ratings, and scales documentation can be found on the CDISC website at: https://www.cdisc.org/foundational/qrs.
1.1 Representations and Warranties, Limitations of Liability, and Disclaimers
This document is a supplement to the ADaMIG and is covered under Appendix C of that document, which describes representations, warranties, limitations of liability, and disclaimers. Please see Appendix C of the ADaMIG for a complete version of this material.
CDISC does not endorse any QRS instrument and does not specify how to conduct clinical assessments, protocols, or analyses. CDISC disclaims any liability for your use of this material.
Include this line only for supplements that the US FDA will be reviewing: 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.
1.2 Copyright Status
CDISC believes this instrument to be in the public domain, but you should perform your own assessment. CDISC has included the APACHE II in the CDISC library of QRS data standards supplements. There may be many versions of this instrument in the public domain or copyrighted. CDISC has chosen to use the version attached to the QRS supplement to the SDTMIG, and the QRS supplement to the ADaMIG is based on the same version.
Note: CDISC Controlled Terminology is maintained by National Cancer Institute (NCI) Enterprise Vocabulary Services (EVS). The most recent versions of the SDTM and ADaM controlled terminologies should be accessed through the CDISC website (https://www.cdisc.org/standards/terminology).
1.3 Known Issues
The Acute Physiology and Chronic Health Evaluation (APACHE II) is a severity of disease measurement and mortality estimation tool for adult patients applied within 24 hours of admission to an intensive care unit (ICU). The instrument consists of individual items that are summed up to create a total score. This instrument is generally collected once at Screening/Baseline and used as a predictor of mortality rather than an outcome measure. The total score is normally collected as part of the instrument with no instructions provided for handling missing data. In the majority of cases, where APACHE II is only assessed once and the collected total score used as a baseline covariate, the SDTM RS domain may be sufficient to support the analysis requirements, as a variable in ADSL copied directly from a result/value in SDTM.
2 Rules and References
The primary source used in the development of this supplement is Knaus WA, Draper EA, Wagner DP, Zimmerman JE. APACHE II: a severity of disease classification system. Critical Care Medicine 1985; 13(10):818–29.
All links are valid and referenced information is current as of the date of this ADaMIG QRS supplement. This supplement does not make recommendations for the handling of missing data or adoption of imputation methods.
3 Scoring Software
There is no known publicly available scoring software as of the date of this ADaMIG QRS supplement.
4 Introduction to the Instrument
The APACHE II, is a severity-of-disease classification system that uses a point score based on the initial values of 12 routine physiologic measurements, age, and previous health status. Scores range from 0 to 71 and higher scores correspond to more severe disease and a higher risk of death. The composite score is based on findings represented in other SDTM domains such as Laboratory Test Results (LB) and Vital Signs (VS).
5 Key Data Checks
The computed total score consists of integer values ranging from 0 to 71. The classification system consists of 11 physiology measures based on a numeric rating scale (0-4) where 0 reflects values within the normal range and an increase in the numeric rating scale represents an increase in the abnormality of the physiology measure in either the high or low direction. the score for The final physiology measure, the Glasgow Coma Score (GCS), is reversed; so that lower scores indicate mild or no head injury and higher scores represent more severe head injury and range from (0-12). Chronological age is divided into disjoint categories and assigned values of (0, 2, 3, 5, 6). For patients with a history of severe organ system insufficiency or who are immunocompromised, a numeric rating of 2 or 5 is assigned for chronic health points, where 2 is assigned “for elective postoperative patients” and 5 is assigned “for nonoperative or emergency postoperative patients”.
6 Example
6.1 Background
Analyses based on ADaM datasets may vary depending on the sponsor, therapeutic area, and the needs of regulatory authorities in their decision-making processes. This fictional example is provided for illustrative purposes only. The ADaM dataset describing the analysis results from an instrument is based on the protocol and statistical analysis plan (SAP) for the individual study.
The example dataset described here is intended to support a variety of analyses, ranging from simple univariate summary statistics on the actual total scores to other types of by-visit and repeated-measure analyses. For that reason, standard ADaM BDS variables such as AVAL (analysis value) have been included in the example. In addition, although not illustrated in the example, the APACHE II total score can be divided into categories (e.g., <17 >=17) reflecting disease severity or risk of death and the frequency of subjects reporting in each category may be generated or used for analysis.
In the example presented here, it is assumed that the final APACHE II analysis dataset (ADAPCH) contains all of the original records, plus a record for the computed total acute physiology score and a record for the computed total APACHE II for each patient and assessment timepoint. The date of the assessment—and time of the assessment, if collected—should also be included in the dataset. For traceability, raw item-level responses from the SDTM RS.RSORRES variable, stored separately from the analysis variable AVAL, are included. Derivation type (DTYPE) should be used to clearly indicate records where missing values have been imputed using sponsor-defined imputation methods. If useful for analysis, a summary analysis dataset which includes only the computed total score records may also be created.
6.2 Example Analysis Dataset, Variable and Value-level Metadata
The ADAPCH Dataset Metadata table shows an example of how the APACHE II may be implemented in ADaM. The dataset metadata is a recommendation for the dataset name, label, structure, and keys. These can be modified for sponsor-specific standards and analyses.
ADAPCH Dataset Metadata
Dataset | Label | Structure | Keys | Class |
---|---|---|---|---|
ADAPCH | APACHE II Analysis | 1 record per subject per analysis visit per parameter. | USUBJID, AVISITN, ADT, PARAMN | BASIC DATA STRUCTURE |
ADAPCH Variable Metadata
Variable Name | Variable Label | Type | Controlled Terms | Source | Derivation | User Notes |
---|---|---|---|---|---|---|
STUDYID | Study Identifier | Char | RS.STUDYID | |||
USUBJID | Unique Subject Identifier | Char | RS.USUBJID | |||
SITEID | Site Identifier | Char | ADSL.SITEID | |||
RSSEQ | Sequence Number | Num | RS.RSSEQ | RSSEQ is included to provide traceability back to SDTM. | ||
ASEQ | Analysis Sequence Number | Num | After sorting by key variables, renumber all the records from 1 to n within a subject. | Provides a sequence number to derived rows which are not present in RSSEQ. | ||
ITTFL | Intent-to-Treat Population Flag | Char | “Y”, “N” | ADSL.ITTFL | Conditional; must include at least 1 population flag. | |
TRTP | Planned Treatment | Char | "DRUG A + SOC", "SOC" | Derivation should be defined by sponsor according to analysis needs. Conditional; should include at least 1 treatment variable (e.g., TRTP, TRTA, TRTSEQP, TRT01P). | ||
PARAM | Parameter | Char | APCH1TN, APCH1PN | RS.RSTEST for responses to individual questions copied from SDTM. Set PARAM to "APCH1-A: Total Acute Physiology Score - Analysis" for the derived total acute physiology score. Set PARAM to "APCH1-Total APACHE II Score - Analysis" for the derived total score. | ||
PARAMCD | Parameter Code | Char | APCH1TC, APCH1PC | RS.RSTESTCD for responses to individual questions copied from SDTM. Set PARAMCD to "APCH1TPS" for the derived total acute physiology score and "APCH1TS" for the derived total score. | ||
PARAMN | Parameter Number | Num | Number of the item in the order it appears on the form; assign a higher value to the derived total score record. | |||
PARCAT1 | Parameter Category 1 | Char | "APACHE II" | Set to RS.RSCAT for records that come directly from SDTM and "APACHE II" for any derived records such as total scores. | ||
VISIT | Visit Name | Char | RS.VISIT | RS.VISIT included for traceability. | ||
VISITNUM | Visit Number | Num | RS.VISITNUM | RS.VISITNUM included for traceability. | ||
AVISIT | Analysis Visit | Char | AVISIT represents the analysis visit for the record. Refer to the SAP for additional details. | |||
AVISITN | Analysis Visit (N) | Num | A numeric representation of AVISIT. | |||
RSDTC | Date/Time of Finding | Char | RS.RSDTC | RS.RSDTC included for traceability. | ||
ADT | Analysis Date | Num | Date portion of RS.RSDTC converted to numeric and displayed in a format such as DATE9. For derived total score records where PARAMCD in("APCH1TPS" "APCH1TS"), this information will be copied from the individual records that comprise that instrument. | |||
ADY | Analysis Relative Day | Num | ADT-ADSL.TRTSDT+1 if ADT≥TRTSDT; else, ADT-ADSL.TRTSDT if ADT<TRTSDT. | This derivation is for example only. | ||
RSORRES | Finding in Original Units | Char | RS.RSORRES | |||
RSORRESU | Original Units | Char | RS.RSORRESU | |||
AVAL | Analysis Value | Num | See Parameter Value Level List - ADAPCH table. | |||
DTYPE | Derivation Type | Char | "WOC" | |||
ABLFL | Baseline Record Flag | Char | “Y” | Set ABLFL="Y" on the record defined as the baseline value. This flag will only be populated on the derived acute physiology and APACHE II total score records (PARAMCD in("APCH1TPS" "APCH1TS")) in this example. | ||
COUNTRY | Country | Char | ADSL.COUNTRY | Permissible if needed for analysis. Generally represented using ISO 3166-1 Alpha-3. Note that regulatory agency specific requirements (e.g., US FDA) may require other terminologies; in such cases, follow regulatory requirements. | ||
REGION1 | Geographic Region 1 | Char | ADSL.REGION1 | Permissible if needed for analysis. | ||
REGION1N | Geographic Region 1 (N) | Num | ADSL.REGION1N | Permissible if needed for analysis. |
All controlled terminology for instruments in both SDTM and ADaM is associated with a specific version of the instrument. When integrating responses from an instrument across studies, it is important to know which version of the instrument was used for each study. When multiple versions of the same instrument exist in an integration, a pooled analysis of responses across different versions can only be performed if determined to be clinically and statistically acceptable. In that case, sponsor-defined terminology, similar to CDISC Controlled Terminology but without the reference to a specific version, should be used for PARAMCD, PARAM and PARCATy.
Parameter Value List - ADAPCH [AVAL]
Variable | Where | Type | Controlled Terms | Source | Derivation | User Notes |
---|---|---|---|---|---|---|
AVAL | PARAMCD NOT IN ("APCH1TPS" (APCH1-A: Total Acute Physiology Score - Analysis), "APCH1TS" (APCH1-Total APACHE II Score - Analysis)) | Num | Set AVAL=RS.RSSTRESN. | The analysis value is the result copied from SDTM. | ||
AVAL | PARAMCD EQ "APCH1TPS" (APCH1-A: Total Acute Physiology Score - Analysis) | Num | The sum of RS.RSSTRESN for RS.RSTESTCD in ("APCH101"-"APCH112") if no question are missing. Note that one out of the following two items: RSTESTCD="APCH105A" or "APCH105B" must be answered or RSTESTCD="APCH106A" or "APCH106B" but not both. | The expectation is that issues with conditional branching are fixed in SDTM RS. | ||
AVAL | PARAMCD EQ "APCH1TS" (APCH1-Total APACHE II Score - Analysis) | Num | The sum of RS.RSSTRESN for RS.RSTESTCD in ("APCH101"-"APCH112") and "APCH114", "APCH115" if no question are missing. Note that one out of the following two items: RSTESTCD="APCH105A" or "APCH105B" must be answered or RSTESTCD="APCH106A" or "APCH106B" but not both. If a subject dies on or before Day 15, they are assigned the highest observed APACHE II score of any of the participants at any time during the trial for their Total APACHE II Score at Day 15 (Day of Discharge). | The assignment of the highest observed APACHE II score is for illustration purposes only and not meant as a recommendation. |
6.3 Example Analysis Dataset
The APACHE II Summary Analysis Dataset table shows the terminology and variables for implementing the example analysis dataset for this instrument in the BDS. This specific example is taken from a Phase II, randomized, controlled, open label multi-center study to assess the efficacy and safety of Drug A for the treatment of SARS-CoV-2 infected patients with COVID-19 pneumonia and impaired respiratory function. The primary outcome measure is APACHE II Severity of Disease Score on Day 15 or on the Day of Discharge (Whichever is Earlier). This measure compares Drug A + Standard of Care (SOC) versus the Standard of Care (SOC).
In this example, the APACHE II score was measured on Day 1 (prior to implementation of treatment), Day 7, and Day 15 or on the day of discharge (whichever was earlier). In the example, as per the SAP, participants who died on Day 15 or earlier were assigned the highest observed APACHE II score of any of the participants at any time during the trial (worst case imputation for deaths). This imputation method is for example purposes only and not meant to be a recommendation nor considered a common practice. Missing data values of the parameters required for the derivation of the APACHE II score were replaced by the last available assessment. Item level imputation, in this example, is handled by the investigators and/or clinicians at the site and is considered source data, already captured in SDTM. The --LNKID variable can be used to determine the source or input record used to assess that particular physiological item on APACHE II at that time point. SOC included a variety of supportive therapies that ranged from the administration of supplementary oxygen to full intensive care support, alongside the use of antiviral treatment, convalescent plasma, corticosteroids, antibiotics or other agents.
In the example, the SAP specifies that planned collected visits, including baseline measurements, are to be used in analyses and displays of results. In fact, no Unscheduled Visits exist in the source data. If the planned physiology assessment is not done or invalid, the investigator may choose to use a previous or repeat assessment of that parameter as the value at that visit for the scoring of APACHE II. The records for 2 subjects are show in the example datasets. The data for 3 visits is shown for the first subject with no missing data. The data for 1 visit is shown for the second subject and the subject dies before the Day 15 (Day of Discharge) Visit so the APACHE II total score is imputed to the worst case value of any subjects across any timepoints at that visit. Note that the worst case value is not shown in the sample data.
APACHE II Complete Analysis Dataset
The APACHE II Complete Analysis Dataset table shows all of the individual question responses for this example, as well as the computed total Acute Physiology score and the computed total APACHE II score. This example is considered to be the final analysis dataset for submission. Computed total scores can appear after the individual item responses, with appropriate labels for identification.
Due to the number of items on the instrument and the fact that only the total APACHE II score records are required for analysis, the separate summary dataset shown in the following example, which contains only the total APACHE II score records, may also be created. RSSEQ was not included in this example because it would be null for all computed total score records. RSORRES is not shown because only derived total score records are displayed.
7 References
- Knaus WA, Draper EA, Wagner DP, Zimmerman JE. APACHE II: a severity of disease classification system. Critical Care Medicine 1985; 13(10):818–29.
End of Document