Metadata tables Collection metadata in this guide are instructions for implementation of implementing the CDASH model Model to develop CRFs and the underlying database or other data collection structure. Metadata tables Collection metadata for the TIG are provided in the following sections:
Section 2.7.6, Metadata for Individual Health. Guidance in this section describes how to read collection metadata provided in Section 2.7.6. Implementers should refer to Section 2.7.6 when reading this guidance.
Collection metadata will be used with guidance in this section and are organized with 1 set of metadata per domain.All collection metadata begin with a description of the domain. A metadata table follows to describe data collection fields and their attributes. Assumptions for the domain are also provided to further guide implementation. Metadata tables are structured to present one 1 or more rows for each standard data collection field with columns to describe expectations for the CRF and data management system design, mapping of collected data in tabulation datasets, as well as guidance for individuals involved in data collection. Metadata tables contain more than one row when... Multiple rows for are present - Columns describing CRF and data management system design are intended to assist the designers with remaining in conformance with the standard. When multiple options are contained in a single cell, the options are separated by a semicolon.
The columns in a metadata table are:
attributes for each field. More than 1 row will be present in a metadata table when data collection for a field can be performed using different scenarios/options. Multiple data collection options may also be provided in single cell within a row for a field with each option separated by a semicolon.
Each column in a metadata table provides domain specific guidance for data collection, including guidance for:
- CRF and System Design, with attributes to assist the development of CRF(s) and the underlying database structure in conformance with the standard
- Tabulation Dataset Generation, with attributes to assist the electronic generation of tabulation datasets from compliant data (e.g., via programming)
- CRF Completion Instructions, to assist the creation of applicant documentation for instructing how to complete CRF fields
The columns present in each metadata table are described below with the column name, guidance, and purpose:
| Metadataspec |
|---|
| Num | Metadata Table Column Name | Guidance | Purpose of Column Content | | 1 |
|
| Metadataspec |
|---|
| Column | For | Purpose | Observation Class | Tabulation Dataset |
Mapping| Generation | Specifies the SDTM class for the domain |
. (see SDTM v2.1 Sections 2.1 and 3.1 for more information on Observation Classes). | | 2 | Domain | Tabulation Dataset |
Mapping| Generation | Specifies the 2-letter domain code |
. | | 3 | Data Collection Scenario |
Collection Guidance | Indicates when a collection field should be used based on a specific context. Values in this column should be used with values in TIG Core | CRF and System Design | Specifies when there are different data collection contexts for collection fields in the same domain (e.g., central or local processing for collection of laboratory test results). Values provide context for values in the TIG Core column to determine when a field should be present on |
a the CRF. Values in this column are: - A short description of the
|
context in which the collection field should be present.- data collection context
- N/A for when
|
no specific for use applies to the collection field.Implementation Options | Collection Guidance | Indicates Specifies how to read/implement. When this column contains "Horizontal-Generic," a sampling of the CDASHIG - is provided for the domain
This column can be used to filter the metadata table for specific data collection scenarios when developing CRFs. | 4 | Implementation Options | CRF and System Design | Specifies when a sampling of collection metadata is provided as a template for the metadata of the CRF in a denormalized structure. |
Is this applicable to TIG specifications? Values in this column are: - NA to indicate data are collected in a normalized structure using a general variable for the name of the test and 1 variable for the collected results, resulting in a vertical dataset structure in which there is 1 record for each test/result
- Horizontal-generic to indicate data are collected using a unique variable name for each test, resulting in a wide, horizontal dataset with multiple test results in each record
| | 5 | Order Number | CRF and System Design |
Order Number | Collection Guidance | Provides a suggested order of fields to be displayed on a CRF |
. CDASHIG | Collection Variable | Tabulation Dataset |
Mapping variable namesdata collection variable name When the value in the Observation Class column is Findings, controlled terms must be incorporated into the data collection variable name. |
CDASHIG | 7 | Collection Variable Label |
Tabulation Dataset Mapping| CRF and System Design | Provides the |
CDASHIG | data collection variable label |
. CDASHIG | Collection Definition | CRF and System Design | Provides |
a of CDASHIG for to support understanding and |
proper usageintended usage. Values in this column are further described in Section 1.5, Known Issues. | | 9 | Question Text | CRF and System Design | Provides full sentence/question forms to prompt for data. Values in this column are: - Without text in brackets or parentheses, to be used as-is
|
. to - , indicating an option on the verb tense of the question or text that can be replaced with protocol-specified verbiage
|
.- or controlled terminology
- With text in parentheses, indicating options for text (e.g., singular/plural) or optional text
|
.- that may be omitted
- With text separated with a forward slash, indicating
|
optional wording.- In Findings domains, values from the relevant CDISC CT lists must also be used to create appropriate Question Text, Prompts, and/or variable names. For example, if the question is about the subject's height, incorporate the value of "Height" from the VSTEST codelist as the prompt on the CRF, and incorporate "HEIGHT" from VSTESTCD in the variable name.
- options for wording from which an implementer may choose.
The CDASH Model can be referenced to create conformant alternative question text. | 10 | Prompt | CRF and System Design | Provides short phrases to prompt for data. Values in this column are phrases: |
Suitable as column headers.- Without text in brackets or parentheses, to be used as-is
- With text in brackets, to be replaced with protocol-specified verbiage
|
.- or controlled terminology
- With text in parentheses, indicating optional text
|
.- With text with NULL indicating the prompt is not required on a CRF screen/page if not needed
The CDASH Model can be referenced to create conformant alternative prompt text. | | 11 | Data Type | Tabulation Dataset |
Mapping| Generation | Specifies the data type of the variable. Values for in this column are: - Num for numeric data
- Char for character or alphanumeric date
| 12 |
TIG Collection Core | CRF and System Design | Specifies expectations for inclusion of |
fields a in this column should be are used with values in the Data Collection Scenario column to determine when a field |
should a the CRF. Values in this column are: |
which - that are Highly Recommended and
|
for which a data collection field - should always be included on the CRF
|
. which - that are Recommended/Conditional and
|
for which a data collection field that a based on . which for which a data collection field is available for use.- should be included on the CRF when needed to support data collection
When the value in this column is R/C, conditions are described in the Implementation Notes column. | | 13 | Case Report Form Completion Instructions |
Collection Guidance| CRF Completion Instructions | Provides recommended example instructions for the data collection field to support authoring of study-level |
documentation instructing sites complete CRF fields. enter collected information on the CRF | | 14 |
| Tabulation Target | Tabulation Dataset |
Mapping| Generation | This column provides the suggested mapping to the tabulation dataset variable. Values in this column are: - The name of the tabulation dataset variable to which the value of the data collection variable will be mapped
- N/A for when no direct mapping to a tabulation dataset variable is available
|
.- Text with the prefix SUPP for when the value of the data collection variable
|
SUPP–.QNAM for when a value represented in the field to Supplemental Qualifier | | 15 | Mapping Instructions | Tabulation Dataset |
Mapping| Generation | Provides information on the suggested mapping of the data collection variable to the tabulation variable. Additional guidance for mapping values may be described in the Implementation Notes column. | | 16 | Controlled Terminology Codelist Name | CRF and System Design |
Specifies controlled terminology applicable to the fieldTabulation Dataset Generation | Specifies the name or names of the CDISC Controlled Terminology codelist or codelists associated with the data collection field and variable. Values in this column are: |
Names of controlled terminology codelists with allowable terms to populate the variable. Codelist names are specified in paratheses. Multiple codelist names indicate the variable is subject to one or more of the codelists.- The codelist name in parentheses, when 1 codelist is associated
- Codelist names in parentheses separated by commas, when more than 1 codelist is associated
- N/A for when controlled terminology is not associated with the data collection field and variable
| | 17 | Subset Controlled Terminology/CDASH Codelist Name |
:This column contains the Tabulation Dataset Generation | Specifies CDISC CT terms or the name of the CDASH subset codelist associated with the data collection field and variable.Values in this column are: - A controlled terminology term or a subset of terms from the codelist
|
name that may be used for that specific variable (e.g., EXDOSFRM). - referenced in the Controlled Terminology Codelist Name column
- The name of the CDASH subset codelist in parentheses
- N/A for when specific controlled terms or CDASH subset terminology are not applicable
| 18 |
Link back to CT section. | Implementation Notes | CRF and System Design Tabulation Dataset Generation | Provides |
additional further context for implementation of |
CRF data collection fields and |
mapping to tabulation datasets content variables. Values in this column may include: - Rationale for implementation guidance
|
Implementation instructionsFor any R/C fields, the "condition" is described in the Implementation Notes column of the CDASHIG metadata table.- Additional instructions for implementing fields and variables on the CRF and in the underlying database structure
- Example values which could appear in the in the data collection field and variable
- Additional guidance for mapping values from data collection to tabulation variables
Example values provided are intended to support understanding and are not intended to influence decisions regarding what data to collect. For guidance on the selection of data to collect, please refer to the appropriate regulatory authority. |
|