Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The remainder of this section addresses cases where the ADaM datasets contain not only the analysis data but also input data that are necessary to provide clearer traceability of the algorithms used to derive the analysis data. In addition to the actual values used in the analysis, the dataset may include rows not used in the analysis, rows containing input data, and rows containing intermediate values computed during the derivation of the analysis data. Flags or other columns are used to distinguish the various data types as well as to provide a traceable path from the input data to the value used in the analysis. The analysis results metadata specify how the appropriate rows are identified (by a specific selection clause). The identification of rows used in an analysis is addressed in ADD LINKS Sections 4.5, Identification of Records Used for Analysis, and 4.6, Identification of Population-specific Analyzed Records.


Unless the input data are already present as column(s) on the row (e.g., as covariate(s) or supportive variable(s)), the input data will be retained as rows in the ADaM dataset. The analysis value column (AVAL and/or AVALC) on the retained input data row will contain a value for the analysis parameter. Not all columns from the input dataset are carried into the ADaM dataset; instead, additional variables will be included indicating the source of the input data – domain, variable name, and sequence number. This approach allows the inclusion of input data from multiple domains. If the input data are already included in columns on the analysis parameter row (e.g., as covariates or supportive information), there is no need to include additional rows for those input data. The decision regarding keeping the input data as rows or columns will therefore be dictated by the types of input data and whether they are used for other purposes in the ADaM dataset.

...