Page History

• Domain datasets based on the SDTM general observations classes will be named using the

• 2-character code for the domain or using the applicable

• 4-character code when a dataset is split (e.g., LB, LBHM).
• Supplemental Qualifier

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

  datasets will be named using

• "SUPP" concatenated withthe

• Variables will be named per guidance in the SDTM. The SDTM guidance uses fragment names in

• the CDISC

• Non-Standard Variables Registry.
• Variable names in TIG

• domain specifications align with naming conventions in the SDTM.  
• Variable names will be 8 characters or less and

• uppercase. 

Variable

length

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

• The maximum length of character

• variables is 200 characters, and the full 200 characters

• should not be used unless necessary.
• Applicants will consider the nature of the data and apply reasonable, appropriate lengths to variables. For example:

• • --TESTCD and IDVAR values will never be

• • longer than 8 characters, so the

• • lengths of those variables can

• • be set to 8.
  • The length for variables that use controlled terminology can be set to the length of the longest term.

Splitting

datasets

A domain dataset may be split into physically separate datasets to support submission when needed and as allowable by the regulatory authority. The following conventions must be adhered to when splitting domains into separate datasets:

• A domain based on a General Observation Class may be split according to values in variable --CAT. When a domain is split on --CAT, --CAT must not be null.
• The Findings About Events or Interventions (FA) domain may be split

• according to the domain in which the interventions or events in --OBJ are represented (or would be represented).

To ensure split datasets can be appended back into

1 domain dataset:

• The value of DOMAIN must be consistent across the separate datasets as it would have been if they had not been split (e.g., LB, FA).
• All variables that require a domain prefix (e.g., --TESTCD, --LOC) must use the value of DOMAIN as the prefix value (e.g., LB, FA).
• --SEQ must be unique within USUBJID for all records across all the split datasets. If there are 1000 records for a USUBJID across the separate datasets, all 1000 records need unique values for --SEQ.
• When relationship datasets (e.g., SUPPxx, FAxx, CO, RELREC) relate back to split parent domains, the value of IDVAR will be from a variable with unique values for each observation

• .

• Permissible variables included in one split dataset need not be included in all split datasets.
• For domains with 2-letter domain codes, split dataset names can be up to 4 characters in length. For example, if splitting by --CAT, dataset names would be the domain name plus up to 2 additional characters to indicate the value of --CAT (e.g., LBHM for LB if the value of --CAT is HEMATOLOGY). If splitting Findings About by parent domain, then the dataset name would be the domain code, "FA", plus the two-character domain code for parent domain code (e.g., "FACM"). The

• 4-character dataset-name limitation allows the use of a Supplemental Qualifier dataset associated with the split dataset.
• Supplemental Qualifier datasets for split domains will also be split. The nomenclature will include the additional

• 1 to

• 2 characters used to identify the split dataset (e.g., SUPPLBHM, SUPPFACM). The value of RDOMAIN in the SUPP-- datasets would be the

• 2-character domain code (e.g., LB, FA).
• In RELREC, if a dataset-level relationship is defined for a split Findings About domain, then RDOMAIN will contain the

• 4-character dataset name, rather than the domain name "FA" (e.g., the value of RDOMAIN will be FACM)

• .

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. The only pre-defined name for analysis  datasets is ADSL which is suggested for studies where a one-record-per-subject dataset is created to capture subject-level demographics, product usage, and/or trial experience information.
• All other ADaM datasets (besides for ADSL) should be named AD + applicant-defined name (ADXXXXXX). The exception to this general naming convention is the addition of the RF prefix for reference data that has been introduced in the TIG.
• 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 variable ordering 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.  

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

• must use 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).

Variable value text case generally depends on the variable usage and how it is presented on outputs (but there is no requirement that this usage must be followed

).