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

Removal of Trio class #142

Open
PMenges opened this issue Jan 10, 2024 · 0 comments
Open

Removal of Trio class #142

PMenges opened this issue Jan 10, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@PMenges
Copy link
Member

PMenges commented Jan 10, 2024

Links between aliases of individuals potentially increase the likelihood of re-identification. This could be particularly problematic for rare diseases (if multiple or all members of a family have the same condition, small number of individuals in a dataset, rare phenotypes etc). Therefore, the Trio class should be deprecated in the non-personal metadata.

The information about pedigree should be captured in a .ped (or a comparable pedigree file) and hanlded similar as the encrypted research data.
We should indicate that such a file exists in a dataset to highlight that pedigree information is present without showing the family relations in our public non-personal metadata, eG with a separate field has_pedigree for dataset. Data Requesters still can view the .ped files after getting access.

@PMenges PMenges added the enhancement New feature or request label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants