You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: