Page History
...
Privacy concerns surrounding the DM and Subject Characteristics (SC) data were taken into account when these domains were created. For example, there are optional collection variables to collect the components of birthdate (e.g., BRTHDD, BRTHMO, BRTHYY); therefore, limited elements of birth day birthday may be collected and later mapped to the tabulation variable BRTHDTC. This approach provides flexibility in categorizing some variables to facilitate compliance with local privacy issues.
Collection of Age vs. Date of Birth
It is recognized that applicants may typically collect the age or date of birth of the subject . In but may collect both if required by the study. In multiregional studies, applicants may need to enable the collection of either in order to comply with local regulations. But only one or the other should be collected for any given subject.
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
Date of birth should be implemented such that incomplete dates may be entered, as allowed by the EDC system.jira
showSummary | false |
---|---|
server | Issue Tracker (JIRA) |
serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
key | TOBA-717 |
The collection of some demographics data Sex is the assemblage of properties or qualities by which male is distinguished from female. This is often collected as it is useful to perform simple analyses based upon population stratification.
...
- Scenario 1: Birth date collection using 3 date fields: This scenario includes date of birth collected as 3 fields (i.e., month, day, year).
- Scenario 2: Birth date collection using a single date field: This scenario includes date of birth collected as a full date, in a single date field. An example CRF is not shown for this scenario.
...