Page History

Data represented in datasets will include the following per regulatory requirements, scientific needs, and standards in this guide:

• Data as originally collected or received (using controlled terminology where applicable) to support the submission
• Data from external references relevant to the submission (e.g., reference data)
• Data assigned per conventions in the TIG
• Data derived per regulatory and TIG conventions

• Analysis dataset naming has no predefined values besides for the requirement

  Jira
  showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-390

  to have a dataset named ADSL. 
• Other ADaM datasets should be named AD + applicant-defined name (ADXXXXXX). The exception to this is the addition of the RF prefix for reference data that has been introduced in the TIG.

  Jira
  showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-391

• There is no rule that noncompliant datasets must start with AX or that they cannot start with AD.
• ADaM datasets should be named logically, if possible, and consistent naming conventions should be used across studies within a submission. 

• There is no ordering

  Jira
  showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-392

  defined for the ADaM standards, although having variables ordered together within a variable group helps review and dataset understanding.
• Variable order in the ADaM dataset must match the order in the define.xml file.  

• Variables will be named per ADaM guidance, which uses fragment names in the CDISC NSV Registry.
• Variable names in TIG ADaM specifications align with naming conventions in ADaM.  
• Variable names will be 8 characters or less and uppercase. 

• Descriptive labels per this guide, up to 40 characters, will be provided as data variable labels for all variables.

  Jira
  showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-393

• All variables must used the labels defined in Section 2.9.5, Predefined Standard Variables for ADSL, Predefined Standard Variables for BDS, and Section 2.9.7, Predefined Standard Variables for OCCDS (besides for the 2 exceptions described therein).

When variable length is referenced in the TIG, this refers to the length in bytes of ASCII character strings.

• The maximum length of character variable is 200 characters, which should not be used unless necessary.
• Applicants will consider the nature of the data and apply reasonable, appropriate lengths to variables. For example:
  • The length of flags will always be 1.
  • PARAMCD will never be more than 8, so the length can always be set to 8.
  • The length for variables that use controlled terminology can be set to the length of the longest term.

Missing values for individual data items will be represented by nulls if necessary for analysis. Otherwise, it is up to the dataset creator whether to include missing values in an analysis dataset. 

An analysis dataset may be split into physically separate datasets to support submission when needed. ADaM currently has no conventions as to the proper way to split analysis datasets, although like types of data should have similar dataset naming.