Appendix B — ID Information
A2CPS relies on several different schemes for labeling and describing metadata entities. This appendix describes those schemes to facilitate linking entities across data modalities.
B.1 Location
Location refers to where the data were collected.
| Terminology | Venue | Notes |
|---|---|---|
| site (code) | Imaging | In Imaging, the code is a two-letter acronym set when the project began. Sites changed their name, and so the acronym may not obviously correspond to the longer name. The mapping is always one-to-one. participants.tsv |
| site (LongName) | ||
| collection site | VBR | locations table |
The following table may be used for mapping across datatypes.
B.2 Participants
| Terminology | Venue | Notes |
|---|---|---|
| subject | Imaging | In Imaging, “subject” is used interchangeably with “participant“ and both are equivalent to “record” |
| participant | Imaging | In Imaging, “participant” is used interchangeably with “subject“ and both are equivalent to “record” |
| subject_guid | VBR | In the VBR, “subject_guid” refers to the same entity as “NDA GUID” in Imaging, but the format is a UUID |
| record | REDCap | 10000-14999: MCC1 TKA; 15000-19999: MCC1 Thoracic; 20000-24999: MCC2 Thoracic; 25000-29999: MCC2 TKA |
| Individual ID | Genetics | Chapter 2 |
| Globally Unique ID (GUID*) | NDA | The GUIDs used in A2CPS are not typical GUIDs but “pseudo-GUIDs“. A decision to upload to the NDA was made partway through the project, at which time it was too late to collect the information that would be required to make typical GUIDs. In practice, this means that the GUIDs used by A2CPS cannot be used to link these participants to other studies within the NDA. https://nda.nih.gov/nda/using-the-nda-guid |
B.3 Visits
| Terminology | Venue | Notes |
|---|---|---|
| session | Imaging | |
| visit | NDA, Imaging | image03 |
| visnum | NDA | image03 |
| session_det | NDA | image03, fmriresults01 |
| protocol_name | VBR | protocol table |
The following table may be used for mapping across datatypes.