Collection metadata in this guide are instructions for implementing the CDASH Model
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-702 |
|---|
|
to develop CRFs and the underlying database or other data collection structure.
Collection metadata for the TIG are provided in Section 2.7.6,
Metadata for Individual Health.
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-580 |
|---|
|
Collection metadata will be used with all guidance in this section and are organized with 1 set of metadata per domain.All collection metadata begin with a description.
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-395 |
|---|
|
A metadata specification follows to describe data collection fields and their attributes. Assumptions are also provided to further guide implementation. Metadata are structured to present 1 or more rows for each data collection field with columns to describe attributes for each field. More than 1 row will be present in the metadata specification when there is more than 1 data collection scenario for a data collection field
| Jira |
|---|
| showSummary | false |
|---|
| server | Issue Tracker (JIRA) |
|---|
| serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
|---|
| key | TOBA-396 |
|---|
|
. When more than 1 option is applicable in a single cell, semicolons are used to separate discrete options.
...