Skip to content

Commit 9d0a359

Browse files
authored
Merge pull request #63 from vantage6/incorporate-feedback-chapter1
Incorporate feedback chapter1
2 parents 0cec063 + aa7cb8e commit 9d0a359

1 file changed

Lines changed: 47 additions & 23 deletions

File tree

episodes/chap1_introduction_FL.md

Lines changed: 47 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -87,21 +87,27 @@ Internet Movie Database (IMDB).
8787

8888
## Federated data analysis
8989

90-
There are different ways in which privacy risks can be mitigated. We will focus on the idea of
91-
federated analysis. In a federated setting, the data with the data owner, who keeps full control
92-
over it. In this case, it is not the data that travels, but the analysis itself. The system sends
93-
a query or instruction to the data and only the results will get back to the user.
90+
There are different ways in which privacy risks can be mitigated. For example, a well-known technique
91+
is to send the data to a trusted third party (TTP). The data can then be analyzed at that location in
92+
a traditional way. However, there are issues with this technique. When the data is copied to the TTP,
93+
the original owner loses control over it. Another issue with it is that this technique results in a
94+
single point of failure. If the security at the TTP is breached, all the data it handled could be exposed.
95+
96+
In this course we will focus on federated analysis. In a federated setting, the data with the data owner,
97+
who keeps full control over it. In this case, it is not the data that travels, but the analysis itself.
98+
The system sends a query or instruction to the data and only the results will get back to the user.
9499
The results are often akin to a form of _aggregation_ of the data. This can be in the shape of
95-
traditional
96-
statistics like the mean, or it could be a combination of aggregations to form a more complicated
97-
analysis.
100+
traditional statistics like the mean, or it can be more intricate like a machine learning model.
98101

99102
Aggregating the data does not ensure complete protection of person-level information, but it
100-
certainly makes it less likely that this will happen.
103+
certainly makes it less likely that this will happen. It is usually the case that the larger
104+
the dataset, the lower the risk of data leakage. For instance, if you would like to take the mean of
105+
all records that fit a certain requirement, like age > 90, and there happens to be only one
106+
records that fits the requirement, the aggregation will be equal to the one matching individual record.
107+
101108

102109
![In federated analysis, an aggregation of the local data is sent to a central point. At the central point the local aggregations are combined. This can also be a small step in a larger analysis.](fig/chapter1/federated_sum.jpg)
103110

104-
TODO: Example of data leakage in simple aggregated case
105111

106112
## Federated learning
107113

@@ -128,12 +134,11 @@ branch
128134
of techniques that can be used for this is Secure Multiparty Computation (MPC). With MPC,
129135
computations are performed collaboratively by multiple parties. Data is encrypted in such a way that
130136
other parties cannot see the original values, but values of multiple parties can still be combined (
131-
e.g. added or
132-
multiplied).
137+
e.g. added or multiplied).
133138
A classic technique from the field of MPC is secret sharing. With this technique data is encrypted,
134139
after which pieces of the encryption are sent to the other parties. No single party will be able to
135-
reconstruct the original value. Only when all parties work together, the original value can be
136-
retrieved.
140+
reconstruct the original value. Only when a certain minimum of parties work together (n-1 in many cases)
141+
the original value can be retrieved.
137142

138143
When combining multiple values using secret sharing, this will result in the parties owning new
139144
puzzle pieces that when put together will reveal the result of the computation.
@@ -176,7 +181,9 @@ weighs.
176181

177182
An aggregation is differentially private when someone cannot infer whether a particular individual
178183
was used in the computation. A way to make a result more differentially private is to replace a
179-
selection of inputs with random noise. A single individual will then always be able to deny that
184+
selection of inputs with random noise. Given the dataset is large enough, and the noise is distributed
185+
appropriately for the data, this will approximately retain the same statistical properties as the
186+
original dataset. Because of this noise, a single individual will then always be able to deny that
180187
their data has contributed to the final result. An individual has _plausible deniability_ with
181188
regards to whether it was part of the dataset.
182189

@@ -189,7 +196,9 @@ The previously mentioned techniques are not used in isolation, but are usually s
189196
eachother to mitigate the privacy risks that are relevant within the usecase.
190197
Typically, the process begins by anonymizing or pseudonymizing the data. With vantage6, the data is
191198
then placed in a federated setting. Then, the data is analyzed using federated learning,
192-
which may also include, for instance, MPC protocols to further safeguard data privacy.
199+
which may also include, for instance, MPC protocols to further safeguard data privacy. Additionally,
200+
noise may be added to the raw data as well before it is analyzed, using techniques from differential
201+
privacy.
193202

194203
## Data partitioning
195204

@@ -212,7 +221,11 @@ to be found to link identities across datasources. Vertical partitioning require
212221
of privacy enhancing algorithms than horizontal partitioning.
213222

214223
Data can even be horizontally and vertically partitioned at the same time. In these cases, it may be
215-
necessary to combine multiple techniques.
224+
necessary to combine multiple techniques. For example, you might want to combine census data with
225+
medical records from hospitals. This is vertically partitioned because the census and medical features
226+
are stored in different places. On top of that, you might want to combine multiple hospitals, that
227+
all store their records separately. Since the medical records are physically separated as well, it is
228+
horizontally partitioned.
216229

217230
![Horizontal and vertical partitioning refers to how data is separated](fig/chapter1/horizontal_vertical_partitioning.jpg)
218231

@@ -225,21 +238,32 @@ privacy enhancing technologies, a lot of work goes into complying with regulatio
225238
trust.
226239

227240
Since these projects have a risk of affecting the privacy of individuals, a Data Protection Impact
228-
Assessment (DPIA)
229-
is usually required. This is a process that will help identify and minimize privacy risks of a
230-
project
231-
and is required by the GDPR.
241+
Assessment (DPIA) is usually required. This is a process that will help identify and minimize privacy risks of a
242+
project and is required by the GDPR. There is already a [DPIA available for vantage6](https://vantage6.ai/documents/28/DPIA_vantage6_version2023.pdf)
232243

233244
Apart from procedures required by GDPR there might be other regulations in place enforced by the
234-
owners of the data (e.g. hospitals). The specific situation of a project can affect the way in which
245+
owners of the data (e.g. hospitals). For healthcare specifically there will be the
246+
[European Health Data Space (EHDS)](https://health.ec.europa.eu/ehealth-digital-health-and-care/european-health-data-space_en).
247+
EHDS builds upon the GDPR and ensures the exchange and reuse of healthcare data in a safe and secure way.
248+
249+
The specific situation of a project can affect the way in which
235250
the data is allowed to be processed. Some privacy enhancing technologies might be allowed in one
236251
project but prohibited in another. It is always important to stay transparent about privacy risks
237252
of the technologies you intend to use.
238253

254+
Another factor in performing PET analysis is *data harmonization*. All parties need to make sure that
255+
their data is in the right shape to be combined. For instance, if you have two datasets where one
256+
stores the height of patients in a column "height" in centimeters, and another dataset where it is stored
257+
in meters in the column "patient_height" you cannot perform your analysis. You will need to make sure
258+
all datasets follow the same standards and schemas in order to process them together. There are a
259+
couple of datastandards out there to help you with that, such as [OMOP CDM](https://www.ohdsi.org/data-standardization/)
260+
or [FHIR](https://hl7.org/fhir/) together with [SNOMED-CT](https://www.snomed.org/).
261+
262+
In conclusion, PETs will help you to extract valuable insights from sensitive data, but they are only one aspect
263+
of the process. It is also important to consider other factors such as regulations and data preprocessing.
264+
239265
::::::::::::::::::::::::::::::::::::: keypoints
240266

241267
- TODO
242268

243269
::::::::::::::::::::::::::::::::::::::::::::::::
244-
245-
[r-markdown]: https://rmarkdown.rstudio.com/

0 commit comments

Comments
 (0)