CanPath Baseline Biological Sample - Collection and Processing Harmonization Protocol
Networks
-
Variables
-
The objective of the Baseline Biological Sample - Collection and Processing Harmonization Protocol was to generate harmonized datasets across the population-based cohorts to address the research objective of the CanPath Harmonization Initiative.
- Version
- 2.2
- Number of Participants
- 127,397
- Approach
- Prospective
- Type
- Quantitative
- Procedures
- Harmonized data is generated by a central harmonization team (with the collaboration of studies).
- Participant Inclusion
- All CanPath participants from cohorts collecting data on the collection and processing of biological samples at baseline are eligible.
- Infrastructure
- Harmonized data can be transferred to external servers, and pooled data analysis can be achieved.
Information Content
The Baseline Biological Sample - Collection and Processing Harmonization Protocol includes information about variables collected at baseline by four of the six CanPath population-based cohorts: BC Generations Project, Alberta's Tomorrow Project, Ontario Health Study and CARTaGENE (Quebec). The current dataset is the second release and includes more than 2,790,000 biological samples donated at baseline.
The harmonized dataset covers information on:
* Biological Sample Collection
* Biological Sample Shipping
* Biological Sample Processing
* Biological Sample Long-Term Storage
* Standard PREanalytical Code (SPREC) v3.0
Harmonization
- Complete - study-specific variable is the same as DataSchema variable (status detail = identical) or needs transformation to generate DataSchema variable (status detail = compatible)
- Partial - categorical study-specific variable (status detail = proximate) or other types (status detail = tentative) could generate DataSchema variable but with loss of information
- Impossible - study does not collect DataSchema variable (status detail = unavailable) or cannot be used to generate DataSchema variable (status detail = incompatible)
- Undetermined - harmonization status not determined
- Not Applicable - harmonization status is not relevant