Versions Compared

Key

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

...

Metadataspec
Use CaseDataset Structure(s)Implementation
Product Description

OTHER

Follows ADaM fundamental principles but is not subject based.

Product Impact on Individual Health

ADSL, BDS, and OCCDS

Follows ADaM fundamental principles and current ADaM structures.

Product Impact on Population HealthREFERENCEFollows ADaM fundamental principles and the new dataset structure developed for the TIG.


For the TIG Product Description use cases, there are two streams that are not yet covered by the ADaM standard, however the individual health stream is very similar to the analyses done in drug development and the general ADaM structures will cover these types of datasets. however Product Health is not subject-based and therefore updates to the ADaM standard are needed to allow for case, ADaM fundemental principles will be followed with identifiers in addition to the currently allowed USUBJID and SPEVID.   there is a proposed stucture to cover these types of data.

ADaM specifications in this guide are instructions for implementing the ADaM to build analysis datasets for representation of collected or derived data. ADaM dataset specifications for the TIG are provided in:

  • Section x.x, Data Structures for Product Description
    • this section contains an ADaM example woth a class of ADAM OTHER that is not based on USUBJID like all other datasets in the current ADaM 
  • Section x.x, Data Structures for Individual Health
    • this section contains examples of ADSL, BDS, and OCCDS structures for some datasets to support typical safety analyses
  • Section x.x, Specifications for Population Health
    • this section contains the introduction of a REFERENCE data structure designed to capture historical results of various TIG components and several examples of historical data

For the Product Impact on Population Health use case, the REFERENCE dataset structure addresses reference data which captures historic trends and results that are used as input for study analyses.


Analysis dataset specifications Analysis Dataset Specifications list standard ADaM variables and define the required characteristics of standard variables (columns) that are frequently needed in ADaM datasets. The ADaM standard requires that these variable names be used when a variable that contains the content defined in the pre-defined ADaM variables sections is sections is included in any ADaM dataset, regardless of dataset class. It also requires these ADaM standard variables be used for the purposes indicated, even if the content of an ADaM variable is a copy of the content of an SDTM dataset variable.

Currently ADaM has three structures: ADSL, BDS, and OCCDS, which correspond to the SUBJECT LEVEL ANALYSIS DATASET, BASIC DATA STRUCTURE, and OCCURRENCE DATA STRUCTURE classes of ADaM datasets. Analysis datasets that follow the ADaM fundamental principles and other ADaM conventions, but which do not follow one of the three defined structures (ADSL, BDS, OCCDS), are considered to be ADaM datasets with a class of ADAM OTHER. 

Domain specifications will be used with all guidance in this section and are organized with one specification per domain or dataset.All domain specifications begin with a description, expected name, and record structure for the resulting dataset. A domain specification table follows to describe dataset variables and their attributes. Assumptions for the domain are also provided to further guide implementation. Domain specification tables are structured to present one row for each variable with columns to describe expected attributes of the variable in resulting datasets. The order of variables in a domain specification table reflects the expected order of variables in the resulting dataset.The columns in a domain specification table are:


The columns in an ADaM dataset specification table are:

...