Page History

The scientific subject matter of the data and related activities such as data collection, data tabulation, data analysis, and data exchange drive which standards to implement. Implementation of standards in this guide starts with determining which data standards are appropriate should be used based on the nature of the data and activities to be supported. After standards are selectedan applicable set or sets of data standards have been identified, it is then possible to determine how the data are collected, represented, or exchanged using the standards. 

Standards Sets of data standards in this guide are aligned with both use cases and activities. Given this, determining which standards to use may begin by selecting standards for the use case and activity to be supported. It is recommended that all guidance is reviewed, both higher level and detailed, All TIG guidance—both general and detailed—should be reviewed prior to implementing standards. For ease of use, the table below The following table presents use cases, activities, and corresponding sections in this guide which that provide detailed instructions for implementation. Detailed instructions referenced areinclude:

• Section x2.x7, Standards for Collection,  to guide which guides development and use of case report forms ( CRFs ) by implementing the CDISC CDASH Model.
• Section x2.x8, Standards for Tabulation, to guide which guides organization of data collected, assigned, or derived for a study by implementing SDTM.
• Section x2.x9, Standards for Analysis, to specify which specifies the principles to follow in the creation of creating analysis datasets and associated metadata by implementing the ADaM.
• Section x2.x10, Standards for Data Exchange, to support which supports sharing of structured data between parties and across different information systems by implementing specified standards and resources. 

Once applicable standards are selected determined based on the use case and activity, the scientific subject matter of the data, its role, and analysis needs will determine where data belong , (i.e., how the data are collected, represented, or exchanged using the standards).  Standards for collection and tabulation in this guide collect and represent data in using groupings of logically related data called domains. Domains are aligned between collection and tabulation standards to facilitate the transition of collected observations to their representation in tabulation datasets. Standards for analysis focus on analysis requirements are used to design customized datasets is cucustomizable per analysis requirements.

Analysis needs drive the selection of analysis standards, where analysis requirements are supported by both the structure and the contents of the resulting dataset. 

further drives the selection of collection and tabulation standards, where the nature of the data must be within the scope of a domain for the domain to be used. Analysis needs drive the selection of analysis standards, where analysis requirements are supported by both the structure and the contents of the resulting dataset. Standards for data exchange are applicable to all use cases and support sharing of standard CRFs, tabulation datasets, and analysis datasets.

...

• Groups logically related data in domains 
• Domains are aligned

organized in relation to analysis requirements, with the structure of tabulation datasets facilitating the generation of analysis datasets.

To use standards for collection and tabulation, compare the nature or role of the data to the scope of a domain. Domain names provide short descriptions of intended scope and may be used to narrow down which domains to consider. A domain standard may be used when the nature of the data and the domain scope are aligned.Observations will be collected using standardized collection fields when applicable and represented as rows in tabulation datasets. Each observation is described by a series of data points, which correspond to applicable data collection fields and variables in a tabulation dataset. A data collection field and/or tabulation variable may be used when the subject matter of a data point and the scope of a field and/or variable are aligned. The majority of data for a submission will be in scope for domains based on the General Observation Classes and a subset of Special Purpose domains described in the SDTM. Given this, referring to both the CDASH Model when applicable and the SDTM is highly recommended when using domains to support understanding of intended scope and to inform extensions and creation of custom domains when needed.

The design of analysis datasets is generally driven by the scientific and medical objectives of the study. A fundamental principle is that the structure and content of analysis datasets must support clear, unambiguous communication of the scientific and statistical aspects of the study. The purpose of ADaM is to provide a framework that both enables analysis of the data and allows reviewers and other recipients of the data to have a clear understanding of the data’s lineage from collection to analysis to results. ADaM provides the core and defines the spirit and intent of its concepts and standards. The model outlines the fundamental principles to follow in constructing analysis datasets and related metadata. Four types of metadata—analysis dataset metadata, analysis variable metadata, analysis parameter value-level metadata, and analysis results metadata—are described in ADaM. To establish which components are required in a submission, review current relevant files provided by the agency to which the submission is being sent. Other relevant documentation might include the study protocol, the statistical analysis plan (SAP), mock shells that define desired outputs, and any dataset specifications that have been defined.

Standards for data exchange are applicable to all use cases and support sharing of standard CRFs developed using collection standards, tabulation datasets generated using tabulation standards, and analysis datasets designed using analysis standards.

Standards for collection and tabulation group logically related data in domains while  All standards are designed to flow together - The table below describes 

The logic of the relationship may pertain to the scientific subject matter of the data or to its role in the trial. 

Domains

he CDASH Model aligns with and is structured similarly to the SDTM. The CDASH Model organizes data into classes, which represent meaningful groupings of data in clinical research. It defines CDASH metadata for identifier variables, timing variables, general observation class variables (Events, Interventions, and Findings), domain-specific variables, and special-purpose domain variables.

The current CDASH Model represents Identifier, Timing, and Domain-specific variables in the metadata as an Observation Class. This does not align with the SDTM. This will be revised in a future version of the CDASH Model.

Connections between standards

Determiining the standard to use

Observations and Variables - SDTMIG v3.4 - Wiki (cdisc.org) The SDTMIG for Human Clinical Trials is based on the SDTM’s general framework for organizing clinical trial information that is to be submitted to regulatory authorities. The SDTM is built around the concept of observations collected about subjects who participated in a clinical study. Each observation can be described by a series of variables, corresponding to a row in a dataset. 

Datasets and Domains - SDTMIG v3.4 - Wiki (cdisc.org)

A domain is defined as a collection of logically related observations with a common topic. 

Each domain dataset is distinguished by a unique, 2-character code that should be used consistently throughout the submission. This code, which is stored in the SDTM variable named DOMAIN, is used in 4 ways: as the dataset name, as the value of the DOMAIN variable in that dataset, as a prefix for most variable names in that dataset, and as a value in the RDOMAIN variable in relationship tables (see Section 8, Representing Relationships and Data).

Data represented in SDTM datasets include data as originally collected or received, data from the protocol, assigned data, and derived data. 

Datasets and Domains - SENDIG v3.1.1 - Wiki (cdisc.org) 

Test results, examinations, and observations for subjects in a nonclinical study are represented in a series of SEND domains. A domain is defined as a collection of logically related observations with a common topic. The logic of the relationship may pertain to the scientific subject matter of the data or to its role in the study. 

Although the domain name is carefully selected, it is the structures and specifications within the domain that drive placement of data. It is important to note that the domain structure is only used for organizational purposes. The --TEST and --METHOD variable entries in the domain contribute to the identification of the test performed and the conditions under which the test was performed; the domain name or organization is not intended to imply any of this information.

Each domain dataset is distinguished by a unique, 2-character code that should be used consistently throughout the submission. This code, which is stored in the SDTM variable named DOMAIN, is used in 4 ways: as the dataset name, as the value of the DOMAIN variable in that dataset, as a prefix for most variable names in that dataset, and as a value in the RDOMAIN variable in relationship tables (see Section 8, Representing Relationships and Data).

Datasets and Domains - SENDIG v3.1.1 - Wiki (cdisc.org) 

When determining which general-observation class domain model is appropriate for reporting specific observations, refer to the domain definition included in the Assumptions section for each domain model (see Section 6, Domain Models Based on the General Observation Classes).

What or who is a subject

Add language here

Determining Where Data Belong

Domains

SDTM

Observations about study subjects are normally collected for all subjects in a series of domains. A domain is defined as a collection of logically related observations with a common topic. The logic of the relationship may pertain to the scientific subject matter of the data or to its role in the trial. Each domain is represented by a single dataset.

Each domain dataset is distinguished by a unique, 2-character code that should be used consistently throughout the submission. This code, which is stored in the SDTM variable named DOMAIN, is used in 4 ways: as the dataset name, as the value of the DOMAIN variable in that dataset, as a prefix for most variable names in that dataset, and as a value in the RDOMAIN variable in relationship tables (see Section 8, Representing Relationships and Data).

SEND

Aside from a limited number of special-purpose domains, all subject-level SDTM datasets are based on 1 of the 3 general observation classes. When faced with a set of data that were collected and that "go together" in some sense, the first step is to identify SDTM observations within the data and the general observation class of each observation. Once these observations are identified at a high level, 2 other tasks remain:

• Determining whether the relationships between these observations need to be represented using GRPID within a dataset, as described in Section 8.1, (SENDIG v3.1.1) Relating Groups of Records Within a Domain Using the --GRPID Variable, or using RELREC between datasets, as described in Section 8.3, (SENDIG v3.1.1) Supplemental Qualifiers - SUPP-- Datasets
• Placing all the data items in 1 of the identified general observation class records, or in a SUPP-- dataset, as described in Section 8.5, (SENDIG v3.1.1) Relating Findings To Multiple Subjects - Subject Pooling

In practice, considering the representation of relationships and placing individual data items may lead to reconsidering the identification of observations, so the whole process may require several iterations.

ADD MORE TEXT HERE