Our results should inform regulators and practitioners of FIGG, as well as quantify biobank privacy risks.
10/10
Our results should inform regulators and practitioners of FIGG, as well as quantify biobank privacy risks.
10/10
* Finding a match does not guarantee identification
* Many relatives missed because of the limited time depth of the register
* Data errors (clerical, adoption, non-paternity, gamete donation, relationship misclassification, MZ twins)
* Generalizability to other countries
9/10
* Finding a match does not guarantee identification
* Many relatives missed because of the limited time depth of the register
* Data errors (clerical, adoption, non-paternity, gamete donation, relationship misclassification, MZ twins)
* Generalizability to other countries
9/10
This is important, as it is often the intersection of the family trees of multiple matches that leads to identification.
The match rate naturally decreases, although not as much for the very large databases.
8/10
This is important, as it is often the intersection of the family trees of multiple matches that leads to identification.
The match rate naturally decreases, although not as much for the very large databases.
8/10
This is probably because the common ancestors of third cousins usually lived before the country's foundation.
Implication: whenever relatives are found in the database, they are usually not too distant.
7/10
This is probably because the common ancestors of third cousins usually lived before the country's foundation.
Implication: whenever relatives are found in the database, they are usually not too distant.
7/10
The match rate is the proportion of people with at least one relative (a "match") in the database.
For a database covering 1% of the country, the match rate is ~25%. For a database covering 10% of the country, the rate is 68%.
6/10
The match rate is the proportion of people with at least one relative (a "match") in the database.
For a database covering 1% of the country, the match rate is ~25%. For a database covering 10% of the country, the rate is 68%.
6/10
We designated a random subset of the population as the "database".
For each person in the database, we used the register to track all of their relatives up to 7th degree (eg, 3rd cousins). This gave us the list of people who would have one or more relatives in the database.
5/10
We designated a random subset of the population as the "database".
For each person in the database, we used the register to track all of their relatives up to 7th degree (eg, 3rd cousins). This gave us the list of people who would have one or more relatives in the database.
5/10
We used the entire Israeli national population register, documenting all parent-child relationships in all present and past citizens.
After QC, the dataset covered 12.5 million people, among them 10.4 million alive.
Summary stats look reasonable.
4/10
We used the entire Israeli national population register, documenting all parent-child relationships in all present and past citizens.
After QC, the dataset covered 12.5 million people, among them 10.4 million alive.
Summary stats look reasonable.
4/10
Given a genomic database covering x% of the population of a country, what is the probability that a target person has one or more relatives in the database?
Particularly, we focus on relatives from whom the target can be traced using available genealogical data.
3/10
Given a genomic database covering x% of the population of a country, what is the probability that a target person has one or more relatives in the database?
Particularly, we focus on relatives from whom the target can be traced using available genealogical data.
3/10
2/10
2/10