For example, I have encountered mismatched diagnosis among these files:
- Diagnosis and exam dates in DXSUM_PDXCONV_ADNIALL.csv do not match with those in ADNIMERGE.csv (e.g. RID 230 at visit m36 has (NL to Dementia) in ADNIMERGE.csv but (5=Conv:MCI to AD) in the other; RID 984 has some mismatched examdates for different viscode).
- dxsum.sas indicates which dementia cases are due to either Alzheimer's disease or other etiology. So there are patients like RID 552, at viscode m60, has MCI to AD in DXSUM_PDXCONV_ADNIALL.csv; MCI to Dementia due to other etiology in dxsum.sas; and MCI to Dementia in ADNIMERGE.csv.
Thank you,
Minh
Hi Minh,
In general, all of those files are using the same information. ADNIMERGE and the dxsum.sas file are both drawing from the DXSUM_PDXCONV_ADNIALL.csv file (dxsum.sas should just be reading in that file and formatting/labeling variables according to the data dictionary).
When I checked
RID 230 at m36, I see NL to dementia in all three files that you noted.
DXSUM_PDXCONV_ADNIALL.csv has a variable for etiology (see, for example, DXDDUE and see the Data Dictionary file for coding information).
ADNIMERGE only contains the global categories of diagnosis (NL, MCI, dementia), so does not include the information about the etiology - it is best to go to the original data file,
DXSUM_PDXCONV_ADNIALL.csv
Danielle
Hi Minh,
In the DXSUM_PDXCONV_ADNIALL file that I just downloaded, DXCHANGE is missing for RID 230 at m36, so I only see information for DXCURREN, DXCONV, and DXCONTYP.
As for the reliability of the etiology of the dementia and how to handle this when it changes, I don’t really have a good answer. I’d recommend submitting a question through the Ask the Experts tool and direct it to the Clinical Core (http://adni.loni.usc.edu/support/experts-knowledge-base/ask-experts/). The Clinical Core folks might better be able to address this question (though I would say that any assessment of etiology is a guess until autopsy!)
Danielle