Skip to content

Coding for diagnosis #2

Open
Open

Description

@htwangtw

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

Activity

  1. clarkenj commented on Feb 8, 2024

    @clarkenj
    Collaborator

    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?

  2. htwangtw commented on Feb 8, 2024

    @htwangtw
    CollaboratorAuthor

    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?

  3. clarkenj commented on Feb 8, 2024

    @clarkenj
    Collaborator

    Perfect! I think grouping should be project specific.

  4. clarkenj commented on Feb 8, 2024

    @clarkenj
    Collaborator

    I would perhaps go for CON over HC?

  5. htwangtw commented on Feb 8, 2024

    @htwangtw
    CollaboratorAuthor

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

  6. clarkenj commented on Feb 8, 2024

    @clarkenj
    Collaborator

    Sure thing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions