Participants who have changed ID number (RID codes)

[Kostas Ioannou]

Hi,

Looking the Registry file I noticed the column. "RGPREVID". Based on the data dictionary this column contains the information about the "the paticipant's initial ID number".

According to my understanding, this means that some participants  registered in the study with a RID code and later the RID code changed. For example the participant 023_S_0027 later renamed to 023_S_0030. I have two questions:

1.) why did this happen? Is it somehow relevant with the design of ADNI? Is this expected?

2.) how should we deal with the information related to these participants? Is their information splitted in two different RID codes? For example if I want all the MMSE scores or the PET scans of the participant now named 023_S_0030, should I also check the files for the participant 023_S_0027 and merge the information? because the partipant may have some years follow up as 023_S_0027 and after a point his/her information is registered as 023_S_0030?

Thank you 

Kind regards,

Konstantinos MD

[Danielle J Harvey]

Hi Kostas,

 

We shouldn’t have data under two different IDs for the same person. In the specific case you mention below, if you look at the REGISTRY entry for 023_S_0027, you will see that the visit code is “f”, meaning they failed screening (the “f” is only in ADNI1)…while I haven’t checked all the cases with an entry in RGPREVID, I think that likely explains most, if not all.

 

Danielle

--
You received this message because you are subscribed to the Google Groups "Alzheimer's Disease Neuroimaging Initiative (ADNI) Data" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adni-data+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/adni-data/fa044eb3-218b-4d8b-b964-275fe45bf6dbn%40googlegroups.com.

**CONFIDENTIALITY NOTICE** This e-mail communication and any attachments are for the sole use of the intended recipient and may contain information that is confidential and privileged under state and federal privacy laws. If you received this e-mail in error, be aware that any unauthorized use, disclosure, copying, or distribution is strictly prohibited. If you received this e-mail in error, please contact the sender immediately and destroy/delete all copies of this message.

[Kostas Ioannou]

Hi Danielle, 

Thanks for the response! I understand this! I also see such cases in later ADNI phases. 

For example 022_S_10440, previously named 022_S_10136. But the SC visit of the 022_S_10136 not been failed.

So what happens if the SC is not a "fail" visit? How is this explained then?

Are there any more reasons that the visits of RIDs in RGPREVID should not be taken into consideration?

Thanks again 

Best,

Kostas

To view this discussion visit https://groups.google.com/d/msgid/adni-data/BL1PR11MB54649CB66D28A745741C0B6CF241A%40BL1PR11MB5464.namprd11.prod.outlook.com.

[Danielle J Harvey]

Hi Kostas,

 

The “f” visit code was really only used in ADNI-1. All other phases, there may be a “sc” visit, but if it isn’t followed by a “bl” visit, then either 1) the bl visit hasn’t happened yet (if it hasn’t been that long since “sc”) or 2) the person failed screening. 022_S_10136 only has sc and nothing else but then was rescreened as 022_S_10440 who then has a bl visit.

To view this discussion visit https://groups.google.com/d/msgid/adni-data/CAAJKB8Gfo07R9o_QA7RajHGw2yT4-P7PsCU4GpxR2N1GhigXqA%40mail.gmail.com.

[Kostas Ioannou]

Hi Danielle,

Thank you for the response. I understand. I think that the best solution would be that participants like  022_S_10136 who have no more data should be removed from the dataset to avoid confusion. I hope that  this is the same for all RIDs in RGPREVID. An alternative would be to check for all RIDs in RGPREVID in the separate datafiles of ADNI. I say it in case someone wants to doublechek.

Thanks again

Best regards,

Kostas

To view this discussion visit https://groups.google.com/d/msgid/adni-data/BL1PR11MB5464813F239D872087C09F40F240A%40BL1PR11MB5464.namprd11.prod.outlook.com.