Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coding for diagnosis #2

Open
htwangtw opened this issue Feb 8, 2024 · 6 comments
Open

Coding for diagnosis #2

htwangtw opened this issue Feb 8, 2024 · 6 comments

Comments

@htwangtw
Copy link
Collaborator

htwangtw commented Feb 8, 2024

We forgot to decide how to code this
@clarkenj any ideas?

@clarkenj
Copy link
Collaborator

clarkenj commented Feb 8, 2024

Ah yes! In terms of variables I feel EMCI, LMCI, MCI, AD, SZ, ADHD, BP, FTD etc. is probably cleaner, and then we have a little dictionary somewhere? Or do you think full labels is preferable?

This might be a bit complicated where they have an overarching diagnosis (dementia) and a sub-diagnosis (e.g. AD). My preference for those cases would be for our variables to output the sub-diagnoses only, and then any grouping etc can be done later. What do you think?

@htwangtw
Copy link
Collaborator Author

htwangtw commented Feb 8, 2024

Sounds great!

I would imaging having a shared json file for the definition of the labels:

{"EMCI": "full name of the diagnosis. ", 
 "ADHD": "full name of the diagnosis. ",
...
}

And for each project where they can have their own coding, we can just write a dictionary to convert the two manually:
for example they have 0 for control, 1 for adhd
{0: "ADHD", 1: "HC"}

For grouping, would you prefer this to be done in the file also? or do you feel this is more project specific?

@clarkenj
Copy link
Collaborator

clarkenj commented Feb 8, 2024

Perfect! I think grouping should be project specific.

@clarkenj
Copy link
Collaborator

clarkenj commented Feb 8, 2024

I would perhaps go for CON over HC?

@htwangtw
Copy link
Collaborator Author

htwangtw commented Feb 8, 2024

sure! if you can compile this json file together that would be great!

@clarkenj
Copy link
Collaborator

clarkenj commented Feb 8, 2024

Sure thing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants