MINDMAP Harmonization Protocol
Networks
-
Variables
-
The objective of the MINDMAP Harmonization Protocol was to generate harmonized datasets across participating longitudinal cohort studies to address the research objectives of the MINDMAP Harmonization Initiative.
- Version
- 3
- Number of Participants
- 223,632
- Approach
- Retrospective
- Type
- Quantitative
- Procedures
- Harmonized data were generated by a central harmonization team (with the collaboration of studies).
- Participant Inclusion
- All study participants were eligible for inclusion.
- Infrastructure
- Harmonized data can be transferred to external servers, and pooled data analysis can be achieved.
Information Content
The MINDMAP Harmonization Protocol includes participant data on individual-level determinants and outcomes collected by 7 longitudinal cohort studies, with 1 to 7 data collection events per study, and area-level information on environmental exposures from publicly available databases. The harmonization protocol includes a total of 2,890 core variables, generated across 11 study-specific datasets.
The harmonized dataset covers information on:
Individual-level determinants and outcomes
* Participants' socio-demographic and economic characteristics
* Participants' lifestyle and behaviours
* Participants' perception of health, quality of life, development, and functional limitations
* Participants' personal and family history of diseases
* Participants' use of prescription medications
* Participants' physical measures and assessments
* Participants' cognition, personality, and psychological measures and assessments
* Participants' life events, life plans, beliefs and values
* Participants' laboratory measures
Area-level environmental exposures
* Physical environment
* Social environment
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