| Literature DB >> 34846691 |
Jessica A Turner1, Vince D Calhoun2,3, Paul M Thompson4, Neda Jahanshad4, Christopher R K Ching4, Sophia I Thomopoulos4, Eric Verner3, Gregory P Strauss5, Anthony O Ahmed6, Matthew D Turner2, Sunitha Basodi3, Judith M Ford7,8, Daniel H Mathalon7,8, Adrian Preda9, Aysenil Belger10, Bryon A Mueller11, Kelvin O Lim11, Theo G M van Erp12,13.
Abstract
The FAIR principles, as applied to clinical and neuroimaging data, reflect the goal of making research products Findable, Accessible, Interoperable, and Reusable. The use of the Collaborative Informatics and Neuroimaging Suite Toolkit for Anonymized Computation (COINSTAC) platform in the Enhancing Neuroimaging Genetics through Meta-Analysis (ENIGMA) consortium combines the technological approach of decentralized analyses with the sociological approach of sharing data. In addition, ENIGMA + COINSTAC provides a platform to facilitate the use of machine-actionable data objects. We first present how ENIGMA and COINSTAC support the FAIR principles, and then showcase their integration with a decentralized meta-analysis of sex differences in negative symptom severity in schizophrenia, and finally present ongoing activities and plans to advance FAIR principles in ENIGMA + COINSTAC. ENIGMA and COINSTAC currently represent efforts toward improved Access, Interoperability, and Reusability. We highlight additional improvements needed in these areas, as well as future connections to other resources for expanded Findability.Entities:
Keywords: COINSTAC; Data privacy; Decentralized; ENIGMA; Meta-analysis
Mesh:
Year: 2021 PMID: 34846691 PMCID: PMC9149142 DOI: 10.1007/s12021-021-09559-y
Source DB: PubMed Journal: Neuroinformatics ISSN: 1539-2791
Fig. 1The example analysis workflow as originally implemented for ENIGMA meta-analyses (left) and as implemented with COINSTAC (right). For more detail see text
Fig. 2Example COINSTAC Consortium. A screenshot of the consortium set up with the members having joined and mapped their data as needed for the consortium analysis pipeline
Fig. 3Example Data Mapping. For this consortium analysis, data mapping consisted of identifying the needed files, which were then grouped as a bundle for use in the analysis. Data mapping does not move the files, but sets up the communication needed for the analysis pipeline to find the needed files when it runs locally
Demographics of the participating sites’ samples as shown in Fig. 2, including the site, the number of subjects with SZ, the number of self-reported male and female (M/F), the mean age in years, the mean duration of illness in years (DOI), and the means SANS total score for the sample
| test1 | 28 | 22/6 | 35.8 (22–53) | 12.3 (1–27) | 19.6 (1–61) |
| test2 | 15 | 14/1 | 41.7 (23–58) | 19.3 (3–41) | 29.5 (9–54) |
| test3 | 35 | 26/9 | 44.5 (20–60) | 23.3 (2–40) | 15.9 (2–63) |
| test4 | 31 | 26/5 | 37.0 (21–62) | 15.3 (3–49) | 20.4 (0–48) |
| test5 | 15 | 10/5 | 37.1 (21–51) | 16.3 (2–31) | 20.3 (0–44) |
| Test6 (tvanerp) | 31 | 18/13 | 36.6 (19–56) | 15.1 (2–48) | 18.6 (4–45) |
| Test7 (author) | 32 | 25/7 | 39.3 (18–60) | 18.5 (1–39) | 19.4 (0–53) |
For each score (Total, MAP, EXP, and the five factors), the meta-analysis estimate of Cohen’s d for the gender effect, the standard error, the z, p, and effect size confidence interval lower bound (ci.lb) and upper bound (ci.ub)
| -0.29 | 0.18 | -1.62 | 0.10 | -0.64 | 0.06 | |
| -0.05 | 0.17 | -0.30 | 0.76 | -0.40 | 0.29 | |
| -0.39 | 0.18 | -2.14 | 0.03* | -0.74 | -0.03 | |
| 0.094 | 0.18 | 0.52 | 0.61 | -0.26 | 0.44 | |
| 0.049 | 0.18 | 0.22 | 0.83 | -0.31 | 0.39 | |
| -0.26 | 0.18 | -1.45 | 0.15 | -0.61 | 0.09 | |
| -0.36 | 0.18 | -1.99 | 0.047* | -0.71 | -0.004 | |
| -0.36 | 0.18 | -1.97 | 0.04* | -0.729 | -0.001 |
* denotes p < .05 for the EXP factor score and its two subdomain factors
Fig. 4Forest plots for Meta-analysis of Gender Differences in EXP (Expression), and associated Blunted Affect (Fact4), and Alogia (Fact 5) Negative Symptom Domain Factors
FAIR principles’ status through ENIGMA + COINSTAC
| F1. (meta)data are assigned a globally unique and persistent identifier | In development | Facilitated | Addressed | Addressed |
| F2. data are described with rich metadata (defined by R1 below) | N/A | Facilitated | Facilitated | In development |
| F3. metadata clearly and explicitly include the identifier of the data it describes | Addressed | Facilitated | Addressed | Addressed |
| F4. (meta)data are registered or indexed in a searchable resource | In development | Facilitated | Addressed | Addressed |
| A1. (meta)data are retrievable by their identifier using a standardized communications protocol | In development | In development | In development | In development |
| A1.1 the protocol is open, free, and universally implementable | Addressed | Addressed | Addressed | Addressed |
| A1.2 the protocol allows for an authentication and authorization procedure, where necessary | Addressed | Addressed | Addressed | Addressed |
| A2. metadata are accessible, even when the data are no longer available | Facilitated | Facilitated | In development | In development |
| I1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation | In development | In development | In development | In development |
| I2. (meta)data use vocabularies that follow FAIR principles | In development | In development | In development | In development |
| I3. (meta)data include qualified references to other (meta)data | In development | In development | In development | In development |
| R1. meta(data) are richly described with a plurality of accurate and relevant attributes | In development | In development | In development | In development |
| R1.1. (meta)data are released with a clear and accessible data usage license | Addressed | Facilitated | Addressed | Addressed |
| R1.2. (meta)data are associated with detailed provenance | N/A | Facilitated | In development | In development |
| R1.3. (meta)data meet domain-relevant community standards | In development | In development | In development | In development |