Versions Compared

Old Version 52

changes.mady.by.user Christine Connolly

Saved on

compared with

New Version Current

changes.mady.by.user Christine Connolly

Saved on

Key

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

If data are in scope for a domain defined in this guide but not all data can be collected using the domain's collection fields, then collection fields may be added to the applicant's CRF from the CDASH Model, the SDTM, or created by the applicant using guidance in the TIG.

Prior to adding fields from the CDASH Model, the SDTM, or considering a new applicant-defined collection field, confirm that none of the fields in the domain will fit the need. Fields may be added from the CDASH Model, the SDTM, or created only when data are different in nature and are not in scope for collection fields in this guide.

Once confirmed, the overall process for extending metadata is as follows:

  1. Using the root variables and other CDASH metadata in the CDASH Model, add any additional variables that are needed to meet the requirements of data collection.

    1. Refer to both the CDASH Model and Appendix C, CDASH Model Metadata Tables.

    2. Follow CDASH root variable-naming conventions where they exist (e.g., --DAT for dates, --TIM for times, --YN for prompts, as described in the CDASH Model) and align with CDISC NSV Registry conventions as applicable.

  2. Select variables from the SDTM when fields from the CDASH Model cannot be used. Selection of variables must align with SDTM usage restrictions.

  3. Create a new applicant-defined collection field when fields in the CDASH Model and variables from the SDTM cannot be used.

    1. When creating a new applicant-defined

Prior to adding any new fields to a sponsor's study CRF, the CDASH Model should be reviewed to see if there is a 
root field that will work for the data collection need

...

    1. collection field, determine whether the data will be used for an operational use case (e.g.,

...

    1. data cleaning

...

    1. ) or are

...

    1. to be represented in a tabulation dataset. In general,

...

    1. new data collection fields (not already defined in the CDASH Model) will fall in 1 of following categories:

...

      1. a field used for operational,

...

      1. data cleaningpurposes only

...

      1. ;

...

      1. a field used to collect data that have

...

      1. direct mappingto a target variable in the tabulation dataset

...

      1. ; or

...

      1. a field used to collect data that have

...

      1. no direct mapping to a target variable in the tabulation dataset.

Prior to adding a custom field to a CRF, confirm that none of the collection fields in this guide or in the CDASH Model fit the need.

    1. The following table provides implementation guidance aligned with both the category of the field and target variable.

Metadataspec
NumField CategoryTarget Tabulation VariableImplementation
1Data CleaningcleaningNAThe field --YN with Question Text "Were there any [interventions/events/findings]?" can be used for this purpose. Replace the two 2 dashes (--) with the two2-character domain code and create the Question Text question text or Prompt prompt using generic Question Text question text or Prompt prompts from the CDASH Model as a base. Always create custom data-cleaning/operational variables using consistent naming conventions.
2Direct MappingmappingYes

If a value can be collected exactly as it will be reported in the tabulation dataset (i.e., same value, same data type, same meaning, same controlled terminology), the tabulation variable name will be used as the data collection variable name in the operational database to streamline the mapping process.

Extensions

Characters may be appended

if

to the data collection variable name if needed to create a unique variable name in the collection database. Any collection variable whose meaning is the same as tabulation variable will align with tabulation variable and the meaning will not be modified for data collection.

3

No Direct Mappingdirect mapping


Yes

If a value cannot be collected in alignment with the tabulation dataset variable (e.g., collected data type is different from the data type in the corresponding tabulation variable) or if the tabulation variable is derived from the collected value, then the operational database should use a collection variable with a different name from tabulation variable into which it will be mapped.

No

If a field does not align with a tabulation variable, a unique name should be assigned based on applicant business rules using CDASH naming fragments (e.g., --DAT, --TIM) as appropriate and CDISC variable naming fragments, found in

Section x.x, CDISC Variable-naming Fragments, where possible. 

the CDISC NSV Registry, where possible. 

If data are not in scope for a domain in this guide, a custom domain can be used. An existing domain may help in selecting the fields and terminology needed for the custom domain. The custom domain must be based on one of the SDTM general observation classes. See Section 2.8.3 How to Create New Specifications for further information.

Pagenav