<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="review-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v9i10e29871</article-id>
      <article-id pub-id-type="pmid">34652278</article-id>
      <article-id pub-id-type="doi">10.2196/29871</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Data Anonymization for Pervasive Health Care: Systematic Literature Mapping Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Schiering</surname>
            <given-names>Ina</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Zuo</surname>
            <given-names>Zheming</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1576-0865</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Watson</surname>
            <given-names>Matthew</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6375-3905</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Budgen</surname>
            <given-names>David</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7143-0241</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Hall</surname>
            <given-names>Robert</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3410-1817</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Kennelly</surname>
            <given-names>Chris</given-names>
          </name>
          <degrees>BSc, MBA</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0339-2866</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Al Moubayed</surname>
            <given-names>Noura</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Department of Computer Science</institution>
            <institution>Durham University</institution>
            <addr-line>Lower Mountjoy, South Rd</addr-line>
            <addr-line>Durham, DH1 3LE</addr-line>
            <country>United Kingdom</country>
            <phone>44 1913341749</phone>
            <email>Noura.al-moubayed@durham.ac.uk</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8942-355X</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Computer Science</institution>
        <institution>Durham University</institution>
        <addr-line>Durham</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Cievert Ltd</institution>
        <addr-line>Newcastle upon Tyne</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Noura Al Moubayed <email>Noura.al-moubayed@durham.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>10</month>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>15</day>
        <month>10</month>
        <year>2021</year>
      </pub-date>
      <volume>9</volume>
      <issue>10</issue>
      <elocation-id>e29871</elocation-id>
      <history>
        <date date-type="received">
          <day>23</day>
          <month>4</month>
          <year>2021</year>
        </date>
        <date date-type="rev-request">
          <day>14</day>
          <month>5</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>6</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>2</day>
          <month>8</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Zheming Zuo, Matthew Watson, David Budgen, Robert Hall, Chris Kennelly, Noura Al Moubayed. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 15.10.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2021/10/e29871" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Data science offers an unparalleled opportunity to identify new insights into many aspects of human life with recent advances in health care. Using data science in digital health raises significant challenges regarding data privacy, transparency, and trustworthiness. Recent regulations enforce the need for a clear legal basis for collecting, processing, and sharing data, for example, the European Union’s General Data Protection Regulation (2016) and the United Kingdom’s Data Protection Act (2018). For health care providers, legal use of the electronic health record (EHR) is permitted only in clinical care cases. Any other use of the data requires thoughtful considerations of the legal context and direct patient consent. Identifiable personal and sensitive information must be sufficiently anonymized. Raw data are commonly anonymized to be used for research purposes, with risk assessment for reidentification and utility. Although health care organizations have internal policies defined for information governance, there is a significant lack of practical tools and intuitive guidance about the use of data for research and modeling. Off-the-shelf data anonymization tools are developed frequently, but privacy-related functionalities are often incomparable with regard to use in different problem domains. In addition, tools to support measuring the risk of the anonymized data with regard to reidentification against the usefulness of the data exist, but there are question marks over their efficacy.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>In this systematic literature mapping study, we aim to alleviate the aforementioned issues by reviewing the landscape of data anonymization for digital health care.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We used Google Scholar, Web of Science, Elsevier Scopus, and PubMed to retrieve academic studies published in English up to June 2020. Noteworthy gray literature was also used to initialize the search. We focused on review questions covering 5 bottom-up aspects: basic anonymization operations, privacy models, reidentification risk and usability metrics, off-the-shelf anonymization tools, and the lawful basis for EHR data anonymization.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>We identified 239 eligible studies, of which 60 were chosen for general background information; 16 were selected for 7 basic anonymization operations; 104 covered 72 conventional and machine learning–based privacy models; four and 19 papers included seven and 15 metrics, respectively, for measuring the reidentification risk and degree of usability; and 36 explored 20 data anonymization software tools. In addition, we also evaluated the practical feasibility of performing anonymization on EHR data with reference to their usability in medical decision-making. Furthermore, we summarized the lawful basis for delivering guidance on practical EHR data anonymization.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This systematic literature mapping study indicates that anonymization of EHR data is theoretically achievable; yet, it requires more research efforts in practical implementations to balance privacy preservation and usability to ensure more reliable health care applications.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>healthcare</kwd>
        <kwd>privacy-preserving</kwd>
        <kwd>GDPR</kwd>
        <kwd>DPA 2018</kwd>
        <kwd>EHR</kwd>
        <kwd>SLM</kwd>
        <kwd>data science</kwd>
        <kwd>anonymization</kwd>
        <kwd>reidentification risk</kwd>
        <kwd>usability</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Digital health [<xref ref-type="bibr" rid="ref1">1</xref>] encompasses several distinct domains, including but not limited to automatic visual diagnostic systems [<xref ref-type="bibr" rid="ref2">2</xref>], medical image segmentation [<xref ref-type="bibr" rid="ref3">3</xref>], continuous patient monitoring [<xref ref-type="bibr" rid="ref4">4</xref>], clinical data–driven decision support systems [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>], connected biometric sensors [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], and expert-knowledge–based consultations [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>] using personal electronic health records (EHRs) [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Of late, pervasive health care has become the central topic, attracting intensive attention and interest from academia [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref4">4</xref>], industry [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>], and the general health care sector [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref15">15</xref>]. Developments achieved in the industry [<xref ref-type="bibr" rid="ref5">5</xref>] and the health care sector [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref16">16</xref>] reveal the huge potential of data science in health care because of the common availability of medical patient data for secondary use (secondary use, also dubbed as reuse, of health care data refers to the use of data for a different purpose than the one for which the data were originally collected). However, such potential could be hindered by legitimate concerns over privacy [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
        <p>The United Kingdom’s Human Rights Act 1998 defines privacy as “everyone has the right to respect for [their] private and family life, [their] home and [their] correspondence” in Article 8 [<xref ref-type="bibr" rid="ref18">18</xref>]. However, it is difficult to explicitly define true privacy because of the discrepancies among target problems, for example, human-action recognition from videos [<xref ref-type="bibr" rid="ref19">19</xref>], camera-pose estimation from images [<xref ref-type="bibr" rid="ref20">20</xref>], and next-word prediction from articles [<xref ref-type="bibr" rid="ref21">21</xref>]. In general, privacy can be treated as any personally identifiable information [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. In the context of digital health care, the secondary use of patients’ clinical data requires both the data controller (responsible for determining the purpose for which, and the means by which, health care data are processed) and data processor (responsible for processing health care data on behalf of the data controller) to comply with the lawful basis and gain direct consent from the data owner [<xref ref-type="bibr" rid="ref24">24</xref>]. Recently, privacy invasion became an increasing concern in digital health care [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. In 2014, the UK charity Samaritans (ie, data processor) released the app Radar [<xref ref-type="bibr" rid="ref29">29</xref>] to identify potential distress and suicidality using the words and phrases of approximately 2 million Twitter (ie, data controller) users (ie, data owners). This app raised severe concerns among Twitter users, including those with a history of mental health issues, and thus it was pulled within weeks [<xref ref-type="bibr" rid="ref26">26</xref>]. In 2015, the Royal Free London National Health Service (NHS) Foundation Trust (ie, data controller) shared 1.6 million complete and identifiable medical records of patients (ie, data owners) with DeepMind Technologies (Alphabet Inc; ie, data processor) to support further testing of the app Stream in assisting the detection of acute kidney injury [<xref ref-type="bibr" rid="ref30">30</xref>]. This collaboration came under fire [<xref ref-type="bibr" rid="ref27">27</xref>] for the inappropriate sharing of confidential patient data [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref31">31</xref>] and failure to comply with the United Kingdom’s Data Protection Act (DPA), as was ruled [<xref ref-type="bibr" rid="ref32">32</xref>] by the Information Commissioner’s Office (ICO), which cited missing patient consent as well as lack of detailed purpose of use, research ethics approval, and the necessary process transparency [<xref ref-type="bibr" rid="ref25">25</xref>]. Thus, a prerequisite for secondary use of clinical patient data is to guarantee patient privacy through data anonymization [<xref ref-type="bibr" rid="ref33">33</xref>]. This is supported by legislation established in different countries that states that secondary use of clinical patient data is permitted if, and only if, the exchanged information is sufficiently anonymized in advance to prevent any possible future association with the data owners (ie, patients) [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. For instance, researchers from academia pointed out the importance of patient-specific health data, which became the impetus for updating the United States’ Health Information Portability and Accountability Act (HIPAA) in 2003 [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>].</p>
        <p>On January 30, 2020, a declaration [<xref ref-type="bibr" rid="ref37">37</xref>] by the World Health Organization named the COVID-19 [<xref ref-type="bibr" rid="ref38">38</xref>] outbreak a Public Health Emergency of International Concern. At present (as of April 18, 2021), there are a total of 140,835,884 and 4,385,938 confirmed cases and 3,013,111 and 150,419 deaths, respectively, throughout the world [<xref ref-type="bibr" rid="ref39">39</xref>] and the United Kingdom [<xref ref-type="bibr" rid="ref40">40</xref>]. As COVID-19 spread to every inhabitable continent within weeks [<xref ref-type="bibr" rid="ref41">41</xref>], data science research relating to digital health care through large-scale data collection [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>] and crowdsourcing [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>] has been highly recommended to curb the ongoing pandemic, including virus tracing [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>] and contact tracing [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]. Public concern with respect to privacy has significantly increased amid the COVID-19 pandemic [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. For instance, mobile apps have been adopted to make contact tracing and notification instantaneous upon case confirmation [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>], for example, the latest NHS COVID-19 app [<xref ref-type="bibr" rid="ref54">54</xref>]. This is typically achieved by storing a temporary record of proximity events among individuals and thus immediately alerting users of recent close contact with diagnosed cases and prompting them to self-isolate. These apps have been placed under public scrutiny over issues of data protection and privacy [<xref ref-type="bibr" rid="ref48">48</xref>].</p>
        <p>Currently, the lack of more intuitive guidance and a deeper understanding of how to feasibly anonymize personally identifiable information in EHRs (it should be noted that data from wearables, smart home sensors, pictures, videos, and audio files, as well as the combination of EHR and social media data, are out of the scope of this study) while ensuring an acceptable approach for both patients and the public leave the data controller and data processor susceptible to breaches of privacy. Although several diligent survey papers [<xref ref-type="bibr" rid="ref55">55</xref>-<xref ref-type="bibr" rid="ref58">58</xref>] have been published to ensure privacy protection and suppress disclosure risk in data anonymization, sensitive information still cannot be thoroughly anonymized by reducing the risk of reidentification while still retaining the usefulness of the anonymized data—<italic>the curse of anonymization</italic> (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Concretely, the gaps in the existing survey studies are four-fold: (1) there does not exist a single data anonymization survey that considers lawful aspects such as the European Union’s General Data Protection Regulation (GDPR) as well as the DPA, ICO, and health care provider regulations; (2) most existing survey studies do not focus on digital health care; (3) the existing privacy models are usually incomparable (particularly for the values of parameters) and have been proposed for different problem domains; and (4) the most recent trends of privacy model–based and machine learning–based data anonymization tools have not been summarized with adequate discussions in terms of their advantages and disadvantages. Motivated by these observations, we aim to deliver a clear picture of the landscape of lawful data anonymization while mitigating its curse in pervasive health care.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>The curse of anonymization. Blue hue indicates an increase in data anonymity, which, in turn, reveals the decrease in usability of the anonymized data, very likely reaching minimum usability before reaching full anonymization (red hue).</p>
          </caption>
          <graphic xlink:href="medinform_v9i10e29871_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>A Brief Overview of the Problem Domain</title>
        <sec>
          <title>Private Data and Their Categorization</title>
          <p>In line with the updated scope of the GDPR and its associated Article 9 [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>], private (ie, personal) data are defined as any direct or indirect information related to an identified or identifiable natural person. In general, based on the definition and categorization presented in chapter 10 of <italic>Guide to the De-Identification of Personal Health Information</italic> by El Emam [<xref ref-type="bibr" rid="ref61">61</xref>], there are 5 types of data: relational data, transactional data, sequential data, trajectory data, and graph data. In addition, inspired by the survey study by Zigomitros et al [<xref ref-type="bibr" rid="ref62">62</xref>], we also included image data because an EHR is essentially a 2D data matrix and thus could be viewed as a 2D image and anonymized using statistical and computer vision techniques.</p>
          <p>Relational data [<xref ref-type="bibr" rid="ref62">62</xref>] are the most common type of data. This category usually contains a fixed number of variables (ie, columns) and data records (ie, rows). Each data record usually pertains to a single patient, with that patient appearing only once in the data set. Typical relational data in health care can include clinical data in a disease or population registry. Transactional data [<xref ref-type="bibr" rid="ref63">63</xref>] have a variable number of columns for each record. For instance, a data set of follow-up appointments from a hospital may consist of a set of prescription drugs that were prescribed to patients, and different patients may have a different number of transactions (ie, appointments) and prescribed drugs in each transaction. Sequential data [<xref ref-type="bibr" rid="ref64">64</xref>] are similar to transactional data, but there is an order to the items in each record. For instance, a data set containing <italic>Brachytherapy planning time</italic> would be considered sequential data because some items appear before others. Sequential data can also be termed relational-transactional data. Trajectory data [<xref ref-type="bibr" rid="ref65">65</xref>] combine sequential data with location information. For instance, data on the movement of patients would have location and timestamp information. Trajectory data can also be termed geolocational data. Graph data [<xref ref-type="bibr" rid="ref66">66</xref>] encapsulate the relationships among objects using techniques from graph theory. For instance, data showing telephone calling, emailing, or instant messaging patterns between patients and general practitioners (GPs) could be represented as a graph, with patients and GPs being represented as nodes and a call between a given patient and their GP represented as an edge between their respective nodes. Graph data are also commonly used in social media [<xref ref-type="bibr" rid="ref67">67</xref>]. Image data, as tabular medical records (ie, EHRs), can be treated as a grayscale image in 2D space. It should be noted that, in this study, the term image data does not refer to medical images such as computed tomography scans.</p>
        </sec>
        <sec>
          <title>Types of Identifiers</title>
          <p>How the attributes are handled during the anonymization process depends on their categorization [<xref ref-type="bibr" rid="ref61">61</xref>]. All attributes contained in a table X are usually grouped into 4 types: direct identifying attributes <italic>I</italic>, indirect identifying attributes (ie, quasi-identifiers [QIs]) <italic>Q</italic>, sensitive attributes <italic>S</italic>, and other attributes <italic>O</italic> [<xref ref-type="bibr" rid="ref61">61</xref>]. Refer to <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> for the mathematical symbols and definitions used throughout this study.</p>
          <p>Direct identifiers <italic>I</italic>, which are also termed direct identifying attributes, provide explicit links to data subjects and can be used to directly identify patients [<xref ref-type="bibr" rid="ref68">68</xref>]. In practice, one or more direct identifying attributes can be assigned to uniquely identify a patient, either by themselves or in conjunction with other information sources. Typical examples of the former case include NHS number, national insurance number, biometric residence permit number, and email address. Suppose there are 2 patients with the same full name within a single NHS foundation trust, the attribute <italic>full name</italic> cannot be a direct identifier by itself. However, a combination of <italic>full name</italic> and <italic>living address</italic> will be a direct identifier.</p>
          <p>Indirect identifiers <italic>Q</italic>, or QIs, are identifiers that, when used with background knowledge of patients in the anonymized data set, can be used to reidentify a patient record with a high probability. Note that if someone, say, an adversary, does not have background knowledge of patients at hand, then this attribute cannot be deemed a QI. In addition, a common choice of QI also considers the analytical utility of the attribute. That is, a QI is usually useful for data analysis, whereas a direct identifier is not [<xref ref-type="bibr" rid="ref61">61</xref>]. Typical QIs include gender, date of birth, postcode, and ethnic origin.</p>
          <p>Sensitive attributes <italic>S</italic> are not useful with respect to the determination of the patient’s identity; yet, they contain sensitive health-related information about patients, such as clinical drug dosage. Other attributes <italic>O</italic> represent variables that are not considered sensitive and would be difficult for an adversary to use for reidentification.</p>
          <p>Among the 4 categories of identifiers, it is particularly difficult to differentiate between direct identifiers <italic>I</italic> and QIs <italic>Q</italic> In general, there are 3 determination rules used for this purpose [<xref ref-type="bibr" rid="ref61">61</xref>], which are depicted in <xref rid="figure2" ref-type="fig">Figure 2</xref>: (1) an attribute can be either <italic>I</italic> or <italic>Q</italic> if it can be known by an adversary as background knowledge; (2) an attribute must be treated as <italic>Q</italic> if it is useful for data analysis and as <italic>I</italic> otherwise; and (3) an attribute should be specified as <italic>I</italic> if it can uniquely identify an individual.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Logical flow of distinguishing direct identifiers I from quasi-identifiers Q. F: false; T: true.</p>
            </caption>
            <graphic xlink:href="medinform_v9i10e29871_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>In <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref70">70</xref>], we summarize the features that are commonly listed as direct and indirect identifiers by health care bodies [<xref ref-type="bibr" rid="ref71">71</xref>] that guide, inform, and legislate medical data release. All listed features may lead to personal information disclosure, and the list is by no means exhaustive. As more varied health care data are released and explored, more identifiers will be added to the lists of those featured in common data attack strategies, such as those in the studies by Hrynaszkiewicz et al [<xref ref-type="bibr" rid="ref69">69</xref>] and Tucker et al [<xref ref-type="bibr" rid="ref70">70</xref>], 18 HIPAA identifiers [<xref ref-type="bibr" rid="ref72">72</xref>], and policies published by the NHS [<xref ref-type="bibr" rid="ref73">73</xref>] and its foundation trusts, for example, Kernow [<xref ref-type="bibr" rid="ref74">74</xref>] and Solent [<xref ref-type="bibr" rid="ref75">75</xref>].</p>
        </sec>
        <sec>
          <title>Data Anonymization Versus Data Pseudonymization</title>
          <p>Given the definition in Recital 26 [<xref ref-type="bibr" rid="ref76">76</xref>] of the most recent GDPR update, data anonymization (the term is common in Europe, whereas deidentification is more commonly used in North America) is a useful tool for sharing personal data while preserving privacy. Anonymization can be achieved by changing identifiers through removal, substitution, distortion, generalization, or aggregation. In contrast, data pseudonymization is a data management and deidentification procedure by which personally identifiable information fields within a data record are replaced by one or more artificial identifiers or pseudonyms.</p>
          <p>It should be noted therefore that the relationship between data anonymization and pseudonymization techniques is characterized as follows:</p>
          <list list-type="bullet">
            <list-item>
              <p>Anonymized data are not identifiable, whereas pseudonymized data are identifiable.</p>
            </list-item>
            <list-item>
              <p>Pseudonymized data remain personal based on Recital 26 of the GDPR and the conclusion [<xref ref-type="bibr" rid="ref77">77</xref>] provided by the ICO.</p>
            </list-item>
            <list-item>
              <p>Solving the problem of data anonymization necessarily means solving pseudonymization.</p>
            </list-item>
          </list>
          <p>Concretely, given an anonymization function <italic>A</italic> and raw data X, we have the anonymized data X’=<italic>A(</italic>X<italic>)</italic> such that there does not exist another function <italic>R</italic> that reidentifies the raw data X from the anonymized data X’, that is, <italic>R</italic>(X’)=<italic>R</italic>(<italic>A</italic>(X))=X. If such a function does exist, this is pseudonymization. The difference between these 2 operations can be generalized as follows: X→X’ for anonymization and X→X’.</p>
          <p>In a real-world scenario, efficient data anonymization is challenging because it is usually problem dependent (ie, solutions vary across problem domains) and requires substantial domain expertise (eg, to specify the direct and indirect identifiers present in raw data) and effort (eg, user involvement in specifying the privacy model before the data anonymization process). Fundamentally, it is very challenging and nontrivial to define what <italic>true anonymization</italic> is or, equivalently, to determine whether the raw data have been adequately anonymized (as well as to agree upon the definition of <italic>adequate anonymization</italic>). In practice, as visualized in <xref rid="figure1" ref-type="fig">Figure 1</xref>, we observe that as the level of data anonymity increases, the usability of the anonymized data decreases and very likely reaches minimum usability before reaching full anonymization. This fact combined with the need for more accurate models in health care provides sufficient motivation for continued research into methods of data anonymization. For this study, we believe that how anonymization is defined is problem dependent. We reiterate that there is no clear-cut line between pseudonymization and anonymization because even anonymized data can practically have different reidentification risks [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref79">79</xref>] (depending on the type of anonymization performed).</p>
        </sec>
      </sec>
      <sec>
        <title>Aims of the Study</title>
        <sec>
          <title>Objectives</title>
          <p>To minimize bias and deliver up-to-date studies related to data anonymization for health care, we organized this survey in a systematic literature mapping (SLM) manner. In general, there are 2 main approaches to conduct literature reviews: systematic literature review (SLR) and SLM [<xref ref-type="bibr" rid="ref80">80</xref>-<xref ref-type="bibr" rid="ref82">82</xref>]. SLRs aim to identify, classify, and evaluate results to respond to a specific review question (RQ), whereas SLMs seek to investigate multiple RQs. In addition, SLRs synthesize evidence and consider the strength of such evidence [<xref ref-type="bibr" rid="ref83">83</xref>], whereas an SLM provides an overview of a research area by reviewing the topics that have been covered in the literature [<xref ref-type="bibr" rid="ref84">84</xref>]. Concretely, we combined high-quality systematic review studies—provided in the Cochrane Database of Systematic Reviews [<xref ref-type="bibr" rid="ref85">85</xref>], Manchester; Centre for Reviews and Dissemination [<xref ref-type="bibr" rid="ref86">86</xref>], York; and Health Technology Assessment [<xref ref-type="bibr" rid="ref87">87</xref>], National Institute for Health Research—to explain this work explicitly and concisely with respect to the validity, applicability, and implication of the results.</p>
          <p>Our overall objective is to alleviate the issues introduced toward the end of the previous section by reviewing the landscape of data anonymization for digital health care to benefit practitioners aiming to achieve appropriate trade-offs in leveraging the reidentification risk and usability of anonymized health care data. In other words, we evaluate the evidence regarding the effectiveness and practicality of data anonymization operations, models, and tools in secondary care from the perspective of data processors.</p>
        </sec>
        <sec>
          <title>Defining RQs</title>
          <p>The aims of the study are to evaluate the potential of preserving privacy using data anonymization techniques in secondary care. Concretely, we, as data processors, are highly motivated to investigate the best possible way of anonymizing real-world EHRs by leveraging the privacy and usability concerns visualized in <xref rid="figure1" ref-type="fig">Figure 1</xref>. Therefore, our RQs were defined as follows:</p>
          <list list-type="bullet">
            <list-item>
              <p>RQ 1: Do best practices exist for the anonymization of realistic EHR data?</p>
            </list-item>
            <list-item>
              <p>RQ 2: What are the most frequently applied data anonymization operations, and how can these operations be applied?</p>
            </list-item>
            <list-item>
              <p>RQ 3: What are the existing conventional and machine learning–based privacy models for measuring the level of anonymity? Are they practically useful in handling real-world health care data? Are there any new trends?</p>
            </list-item>
            <list-item>
              <p>RQ 4: What metrics could be adopted to measure the reidentification risk and usability of the anonymized data?</p>
            </list-item>
            <list-item>
              <p>RQ 5: What are the off-the-shelf data anonymization tools based on conventional privacy models and machine learning?</p>
            </list-item>
          </list>
          <p>The knowledge generated from this SLM, especially the answer to our driving question, RQ 1, will build on the study’s evidence on the future of the development of data anonymization toolkits for data processors such as the companies and organizations in which they are situated. The evidence gained may also contribute to our understanding of how data anonymization tools are implemented and their applicability to anonymizing real-world health care data. Finally, we intend to identify the major facilitators and barriers to data anonymization in secondary care in relation to reidentification risk and utility.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Research Design</title>
        <sec>
          <title>Data Sources and Search Strategy</title>
          <p>In keeping with our RQs, we built up our search strategy using <italic>keywords and indexing terms</italic> and <italic>Boolean operators</italic>; the former refers to the general terms used when searching, and the latter represents the restrictions on these terms. Example keywords and indexing terms used included domain-specific terms such as <italic>healthcare</italic>, <italic>digital health</italic>, <italic>digital healthcare</italic>, <italic>health monitoring</italic>, and <italic>eHealth</italic>; problem-specific terms such as <italic>data anonymization</italic>, <italic>anonymizer</italic>, <italic>de-identification</italic>, <italic>privacy-preserving</italic>, and <italic>data protection</italic>; data-specific terms such as <italic>electronic medical records</italic>, <italic>electronic health records (EHR)</italic>, <italic>DICOM/CT images</italic>, and <italic>videos</italic>; disease-specific terms such as <italic>brain tumor</italic>, <italic>cervical cancer</italic>, <italic>breast cancer</italic>, and <italic>diabetes</italic>; organization-specific terms such as <italic>NHS</italic>, <italic>ICO</italic>, <italic>NIHR</italic>, and <italic>MRC</italic>; and law-specific terms such as <italic>DPA</italic>, <italic>GDPR</italic>, and <italic>HIPAA</italic>. Example Boolean operators are <italic>AND</italic> and <italic>OR</italic>. Next, to avoid bias and ensure reliability, 2 researchers (ZZ and MW) used Google Scholar, Web of Science, Elsevier Scopus, and PubMed for searching academic studies up to June 2020; these services were used because they encompass a wide spectrum of databases such as IEEE Xplore, SpringerLink, ACM Digital Library, Elsevier Science Direct, arXiv, <italic>The BMJ</italic>, <italic>Lancet</italic>, and the <italic>New England Journal of Medicine</italic>. In addition, to maximize search coverage, we conducted forward and backward <italic>snowball sampling</italic> [<xref ref-type="bibr" rid="ref88">88</xref>] (snowball sampling refers to using the reference list of a selected paper [backward snowballing] or the citations of a selected paper [forward snowballing]) on the selected studies. In particular, because gray literature is an important source of SLRs and SLMs [<xref ref-type="bibr" rid="ref89">89</xref>] and they play a primary role in health care [<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref91">91</xref>], gray literature was used to initialize our search in this study. Concretely, preprints from non–peer-reviewed electronic archives (eg, arXiv) or early-stage research were examined and distinguished in the follow-up study selection phase.</p>
        </sec>
        <sec>
          <title>Inclusion and Exclusion Criteria</title>
          <p>Articles were eligible for inclusion based on the criteria defined in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>. ZZ and MW assessed articles independently for inclusion eligibility. Inclusion is relatively straightforward in comparison with exclusion which can be more sweeping. Therefore, further clarification regarding some of the exclusion criteria is required. For instance, <italic>without Experiment section</italic> denotes that the article does not report on any evaluation of the ideas it contains using real-word clinical data sets. <italic>Insights not suitable for EU/UK</italic> indicates observations delivered by articles that treat personally identifiable data as a commercial commodity, as is the practice in, for example, the United States [<xref ref-type="bibr" rid="ref92">92</xref>]. Preprints (tier 2 gray literature [<xref ref-type="bibr" rid="ref93">93</xref>]) were carefully considered for selection in line with the inclusion and exclusion criteria summarized in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>. For duplicate articles (eg, a conference article that extended to a journal paper or a preprint paper accepted by either a conference or a journal), including those with a different title but essentially the same content, we only retained the publication with the highest quality to avoid double counting. To this end, we preferred to retain the article published by the journal with the highest impact factor. In the worst case, none of the duplicates would have been selected if they were all conference papers because this would have been a breach of research ethics.</p>
          <boxed-text id="box1" position="float">
            <title>Inclusion and exclusion criteria for article selection.</title>
            <p>
              <bold>Inclusion criteria</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Related to anonymization or privacy-preserving techniques</p>
              </list-item>
              <list-item>
                <p>Related to privacy-preserving techniques in health care</p>
              </list-item>
              <list-item>
                <p>Presented privacy concerns in health care</p>
              </list-item>
              <list-item>
                <p>Proposed methods for privacy preservation in electronic health records</p>
              </list-item>
              <list-item>
                <p>Proposed methods for using private information, for example, biometric data</p>
              </list-item>
              <list-item>
                <p>Proposed methods partially related to protected health care</p>
              </list-item>
            </list>
            <p>
              <bold>Exclusion criteria</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Written in language other than English</p>
              </list-item>
              <list-item>
                <p>Without <italic>Abstract</italic> or <italic>Experiment</italic> section</p>
              </list-item>
              <list-item>
                <p>About other health care issues, for example, clinical trials</p>
              </list-item>
              <list-item>
                <p>Insights not suitable for European Union or United Kingdom</p>
              </list-item>
              <list-item>
                <p>Out of our research scope</p>
              </list-item>
              <list-item>
                <p>Duplicate articles (case dependent)</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>Article Selection Phases</title>
          <p>Article selection (<xref rid="figure3" ref-type="fig">Figure 3</xref>) consisted of 5 phases: (1) initially, we searched Google Scholar, Web of Science, Elsevier Scopus, and PubMed; (2) next, we applied the inclusion-exclusion criteria to the returned results from the initial search, including the qualifying preprints; (3) we then read the included articles and removed the irrelevant articles; (4) next, we conducted forward and backward snowball sampling on highly related articles; (5) finally, we double-checked the excluded articles and added relevant ones. In addition, we used the <italic>GL+D Checker</italic> mechanism shown in <xref rid="figure3" ref-type="fig">Figure 3</xref>, which refers to a combination of a <italic>Gray Literature Checker</italic> and a <italic>Duplicates Checker</italic>, each of which could also be used separately, depending on the situation.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Systematic literature mapping process for articles. GL+D: gray literature and duplicates.</p>
            </caption>
            <graphic xlink:href="medinform_v9i10e29871_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Data Anonymization Toolkit Selection Phases</title>
          <p>As mentioned at the beginning of this section, the phases involved in selecting data anonymization software tools are difficult because of the limited tools available in the existing studies. Thus, the initially included tools were selected from the qualified articles without considering whether their source code was publicly accessible, maintainable, and extensible. The only criterion was whether the tool could be downloaded and executed. Furthermore, to guarantee that the selection process was less biased, we decided that in each of the 2 (ie, privacy model–based and machine learning–based) categories of privacy-preserving software tools, the number of tools chosen from outside of the selected articles would be no more than 30% of the total.</p>
        </sec>
      </sec>
      <sec>
        <title>Conduct of the Study</title>
        <sec>
          <title>Qualified Articles</title>
          <p>In keeping with the five-phase article selection strategy described in the previous section, ZZ and MW independently selected articles for eligibility in phase 2. Articles were moved forward to the <italic>Article reading</italic> phase or excluded after a full agreement was reached. In addition, NAM served as an arbitrator for any unresolved disagreement. The selection process was conducted using 3 consecutive steps: (1) the title and abstract of each article were screened for relevance; (2) full article contents were reviewed for those without certainty for inclusion; and (3) forward and backward snowballing was applied to the remaining articles to maximize search coverage. The full reference list of the included articles and the related systematic review or mapping studies were also screened by hand for additional articles. There were a total of 13 preprints among the 192 selected articles (<xref rid="figure4" ref-type="fig">Figure 4</xref>) after phase 1. Before beginning phase 2, by applying the <italic>Gray Literature Checker</italic> mechanism, we observed that 4 of the 13 preprints had been successfully published in either peer-reviewed conferences [<xref ref-type="bibr" rid="ref94">94</xref>-<xref ref-type="bibr" rid="ref96">96</xref>] or journals [<xref ref-type="bibr" rid="ref97">97</xref>]. Next, the <italic>Duplicates Checker</italic> was applied consecutively to remove their preprint versions. Using the same process in each phase, we accumulated a total of 239 articles to include in this SLM study, including 9 preprints. Details of the 239 selected research articles are grouped in categorical order and chronological order in <xref ref-type="table" rid="table1">Table 1</xref> and <xref rid="figure5" ref-type="fig">Figure 5</xref>, respectively.</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Number of selected articles during the study selection process.</p>
            </caption>
            <graphic xlink:href="medinform_v9i10e29871_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>An overview of the 239 selected research articles grouped in categorical order.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="530"/>
              <col width="470"/>
              <thead>
                <tr valign="top">
                  <td>Category</td>
                  <td>Selected research articles, n (%)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Background knowledge</td>
                  <td>60 (25.1)</td>
                </tr>
                <tr valign="top">
                  <td>Data anonymization operations</td>
                  <td>16 (6.7)</td>
                </tr>
                <tr valign="top">
                  <td>Privacy models</td>
                  <td>104 (43.5)</td>
                </tr>
                <tr valign="top">
                  <td>Risk metrics</td>
                  <td>4 (1.7)</td>
                </tr>
                <tr valign="top">
                  <td>Utility metrics</td>
                  <td>19 (7.9)</td>
                </tr>
                <tr valign="top">
                  <td>Data anonymization tools</td>
                  <td>36 (15.1)</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>An overview of the 239 selected research articles grouped in chronological order.</p>
            </caption>
            <graphic xlink:href="medinform_v9i10e29871_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Qualified Software Tools</title>
          <p>In accordance with the strategy of selecting qualified privacy-preserving software tools described in the previous section, there were 5 out of a total of 15 privacy model–based data anonymization tools that were not derived from the qualified (ie, selected) articles. Of these 5 tools, 3 (<italic>Amnesia,</italic> OpenAIRE; <italic>Anonimatron,</italic> realrolfje; and <italic>Anonymizer,</italic> Divante Ltd) were obtained by searching GitHub [<xref ref-type="bibr" rid="ref98">98</xref>], and the remaining 2 (<italic>OpenPseudonymiser,</italic> Julia Hippisley-Cox and <italic>NLM-Scrubber</italic> from the US National Library of Medicine) were found through Google Search. Of the 5 machine learning–based tools, only one (<italic>CrypTen</italic>, Facebook Inc) was obtained from GitHub.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Four Categories</title>
        <p>To add structure to this SLM, we grouped the results of the reviewed articles into four categories: <italic>Basic Data Anonymization Operations</italic> (for RQ 2), <italic>Level of Anonymity Guarantees and Evaluations</italic> (for RQ 3), <italic>Disclosure Risk Assessments</italic> and <italic>Usability Measurements</italic> (for RQ 4), and <italic>Existing Privacy Model</italic>–<italic>Based Data Anonymization Tools</italic>, <italic>Existing Machine Learning</italic>–<italic>Based Data Anonymization Tools</italic>, and <italic>Legal Framework Support</italic> (for RQ 5). RQ 1, as the leading RQ, is answered in <italic>Results Summary for RQs</italic>.</p>
      </sec>
      <sec>
        <title>Basic Data Anonymization Operations</title>
        <sec>
          <title>Perturbation</title>
          <p>This technique is implemented by modifying the original data in a nonstatistically significant fashion. As described in the code of practice [<xref ref-type="bibr" rid="ref99">99</xref>] provided by the ICO, the alteration of values within the data set should decrease the vulnerability of that data set to data linkage. The benefit of this method is that it anonymizes the raw data while guaranteeing that the statistical usefulness of the data remains unchanged. On this basis, the possible drawback of such a method is the accuracy of the anonymized data.</p>
          <p>This technique can be achieved through, for instance, microaggregation [<xref ref-type="bibr" rid="ref100">100</xref>], data swapping [<xref ref-type="bibr" rid="ref101">101</xref>] (equivalent to permutation [<xref ref-type="bibr" rid="ref102">102</xref>]), rank swapping [<xref ref-type="bibr" rid="ref103">103</xref>]), postrandomization [<xref ref-type="bibr" rid="ref104">104</xref>], adding noise [<xref ref-type="bibr" rid="ref105">105</xref>], and resampling [<xref ref-type="bibr" rid="ref106">106</xref>], all of which are described, with real-world health care examples to explain each operation, in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> [<xref ref-type="bibr" rid="ref100">100</xref>,<xref ref-type="bibr" rid="ref101">101</xref>,<xref ref-type="bibr" rid="ref104">104</xref>-<xref ref-type="bibr" rid="ref109">109</xref>]. For microaggregation, an observed value is replaced with the average value calculated over a small group of units. The units belonging to the same group are represented by the same value in the anonymized data. This operation can be applied independently to a single variable or to a set of variables with the original column or columns removed. For data swapping, the data records are altered through the switching of variable values across pairs of records in a fraction of the raw data. Equivalently, permutation rearranges the values (either randomly or systematically) and is useful where mapping to alternate configurations of alphanumeric values is problematic or redundant. To this end, the raw data can be efficiently perturbed by permuting the sensitive attribute and the value of a similar record. This operation not only guarantees the statistical significance of the anonymized data but also reduces the risk of the record-wise reidentification. For postrandomization, categorical variables are perturbed based on a prescribed probability mechanism such as a Markov matrix. For raw numerical data with low variance, adding noise, that is, adding a random value, is commonly adopted. Alternatively, resampling is also frequently used on raw numerical data by drawing repeated samples from the original data.</p>
        </sec>
        <sec>
          <title>Generalization</title>
          <p>Generalization [<xref ref-type="bibr" rid="ref107">107</xref>] relies on an observable attribute having an underlying hierarchy. This is an example of such a typical hierarchy:</p>
          <p>Full postcode → street → city or town → county (optional) → country</p>
          <p>with a possible instance being as follows:</p>
          <p>DH1 3LE → South Road → Durham → UK</p>
          <p>and</p>
          <p>DH → Durham → UK</p>
          <p>Typically, generalization is used to reduce the specificity of the data and thereby the probability of information disclosure. Given the examples above, the degree of generalization is fully controlled by the granularity defined in the hierarchy.</p>
        </sec>
        <sec>
          <title>Suppression</title>
          <p>Suppression [<xref ref-type="bibr" rid="ref110">110</xref>] refers to local suppression in data anonymization research. This is usually achieved by replacing the observed value of one or more variables with <italic>missing</italic> or <italic>NA</italic> or <italic>-</italic>. This method helps to address problems where rows would be dropped because of the difficulty of successfully applying perturbation or other generalization methods to guarantee their inclusion in the anonymized data set. By suppressing categorical values that render the rows identifiable, useful data from those rows will not be lost. This method can only be used when the raw data are varied enough that they prevent the suppressed value from being inferred.</p>
        </sec>
        <sec>
          <title>Data Masking</title>
          <p>Data masking [<xref ref-type="bibr" rid="ref108">108</xref>] is a technique frequently used for creating a structurally similar yet inauthentic version of the raw data. This technique helps to protect the original sensitive data while providing a functional substitute and should be used in settings in which the original raw data are not required.</p>
        </sec>
        <sec>
          <title>Differential Privacy</title>
          <p>Differential privacy (DP) [<xref ref-type="bibr" rid="ref109">109</xref>] aims to help organizations better understand the requirements of end users by maximizing the accuracy of search queries while minimizing the probability of identifying personal data information. This is achieved in practice by performing techniques such as data filtering, adaptive sampling, adding noise by fuzzifying certain features, and analyzing or blocking intrusive queries. Essentially, a DP algorithm updates values, leaving some intact while replacing others such that a potential attacker is unable to determine whether a value is fake or genuine. For details about practical DP and related techniques, please refer to section 1.4 of <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref> [<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref111">111</xref>-<xref ref-type="bibr" rid="ref165">165</xref>].</p>
        </sec>
        <sec>
          <title>Homomorphic Encryption</title>
          <p>Homomorphic encryption (HE) [<xref ref-type="bibr" rid="ref166">166</xref>] is a technique that enables calculations to be performed on encrypted data directly, without the need to decrypt the data. The drawbacks of such a method are slow execution speeds. To the best of our knowledge, and in accordance with the definitions used in this paper, a technique that uses an encryption method cannot be treated as anonymization. The presence of the <italic>key</italic> makes the data theoretically reversible and therefore constitutes data pseudonymization. A well-known extension of HE is termed additive HE, which supports secure addition of numbers given only the encrypted data [<xref ref-type="bibr" rid="ref167">167</xref>].</p>
        </sec>
        <sec>
          <title>Compressive Privacy</title>
          <p>Compressive privacy (CP) [<xref ref-type="bibr" rid="ref168">168</xref>] is a technique that proposes to perform privatization by mapping the original data into space with a lower dimension. This is usually achieved by extracting the key features required for the machine learning model before sending the data to the cloud server. To this end, data owners (eg, NHS trusts and authorized companies) have control over privacy [<xref ref-type="bibr" rid="ref169">169</xref>]. Alternatively, this technique could be performed before applying the chosen privacy models. Essentially, CP can be treated as a dimensionality reduction technique that also preserves privacy. Privacy models related to CP are presented in the following section.</p>
        </sec>
      </sec>
      <sec>
        <title>Level of Anonymity Guarantees and Evaluations</title>
        <sec>
          <title>Measurement and Evaluation</title>
          <sec>
            <title>Two Models</title>
            <p>The objective of satisfying different levels of anonymity is usually achieved through 2 consecutive steps: measurement and evaluation. The former refers to the use of either conventional or machine learning–based privacy models to perform data anonymization, and the latter is the process of evaluating the reidentification risk and degree of usability of the anonymized data. The anonymization operations are usually adopted by conventional privacy models or machine-learning–based models. <xref rid="figure6" ref-type="fig">Figure 6</xref> provides a way to quickly locate content of interest.</p>
            <fig id="figure6" position="float">
              <label>Figure 6</label>
              <caption>
                <p>Categorizations of measurements and evaluations for achieving different levels of anonymity. ML: machine learning; RT: relational-transactional privacy model.</p>
              </caption>
              <graphic xlink:href="medinform_v9i10e29871_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
          </sec>
          <sec>
            <title>Conventional Privacy Models</title>
            <p>The attributes contained in a table are usually divided into direct identifiers <italic>I</italic>, QIs <italic>Q</italic>, and sensitive identifiers <italic>S</italic>. The direct identifiers <italic>I</italic> are usually removed at the very beginning stage of data anonymization. Thus, a table X required to be anonymized is denoted as X(<italic>S</italic>, <italic>Q</italic>).</p>
            <p>Given a class of records <italic>G</italic> in a table X, we want to create a single equivalent group <italic>C</italic> using a function <italic>A</italic> such that <italic>C</italic>=<italic>A</italic>(<italic>G</italic>) or <italic>C’</italic>=<italic>A</italic>(<italic>C</italic>). The monotonicity property of privacy models is defined for a single equivalent group <italic>C</italic> or class of records <italic>G</italic>. This property is required by several models for the purpose of refining the level of anonymization of <italic>C</italic>. This property is also useful for manipulating anonymized data by converting it into coarse-grained classes with equivalent classes (ie, a set of anonymized data records that share the same <italic>Q</italic>). This is a simple and computationally inexpensive solution. However, it would be inefficient, particularly in a case where the anonymized data are released to several organizations, each of which has a different minimum acceptable degree of anonymity. To this end, it is always a good practice to first perform the anonymization and then generate multiple coarser versions of the data, rather than performing separate anonymization for each organization [<xref ref-type="bibr" rid="ref170">170</xref>].</p>
            <p>During the process of data anonymization, interpretable and realistically feasible measurements (ie, privacy models [<xref ref-type="bibr" rid="ref171">171</xref>]) should be considered to measure the level of anonymity of the anonymized data. The off-the-shelf privacy models (summarized as part of <xref rid="figure7" ref-type="fig">Figure 7</xref>) are usually independent of any data deanonymization attack and measure the privacy level using features of the anonymized data. One step further, 35 conventional privacy models were investigated to support data with the types grouped into 5 categories (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
            <fig id="figure7" position="float">
              <label>Figure 7</label>
              <caption>
                <p>General pipeline for existing privacy model–based data anonymization tools. F: false; T: true.</p>
              </caption>
              <graphic xlink:href="medinform_v9i10e29871_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
            <table-wrap position="float" id="table2">
              <label>Table 2</label>
              <caption>
                <p>A summary of privacy models for relational electronic health record data with respect to parameter interval and degree of privacy of data.</p>
              </caption>
              <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
                <col width="180"/>
                <col width="210"/>
                <col width="180"/>
                <col width="170"/>
                <col width="130"/>
                <col width="130"/>
                <thead>
                  <tr valign="top">
                    <td>Category</td>
                    <td>Privacy model</td>
                    <td>Section in Multimedia Appendix 4</td>
                    <td>Parameter interval</td>
                    <td>Privacy level</td>
                    <td>References</td>
                  </tr>
                </thead>
                <tbody>
                  <tr valign="top">
                    <td colspan="6">
                      <bold>Relational</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>κ-anonymity</td>
                    <td>1.1</td>
                    <td>[1, &#124;X&#124;]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref111">111</xref>-<xref ref-type="bibr" rid="ref117">117</xref>,<xref ref-type="bibr" rid="ref172">172</xref>,<xref ref-type="bibr" rid="ref173">173</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(α, <italic>k</italic>)-anonymity</td>
                    <td>1.1.1</td>
                    <td>α ∈ [0, 1], <italic>k</italic> ∈ [0, +∞]</td>
                    <td>α: low, <italic>k</italic>: high</td>
                    <td>[<xref ref-type="bibr" rid="ref114">114</xref>,<xref ref-type="bibr" rid="ref174">174</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>k</italic>-map</td>
                    <td>1.1.2</td>
                    <td>[1, &#124;X&#124;]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref175">175</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>m</italic>-invariance</td>
                    <td>1.1.3</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref176">176</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>k</italic>, <italic>e</italic>)-anonymity</td>
                    <td>1.1.4</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref118">118</xref>,<xref ref-type="bibr" rid="ref177">177</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>k</italic>, <italic>g</italic>)-anonymity</td>
                    <td>1.1.5</td>
                    <td><italic>k</italic> ∈ [0, +∞], <italic>g</italic> ∈ [0, 1]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref178">178</xref>,<xref ref-type="bibr" rid="ref179">179</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Multirelational <italic>k</italic>-anonymity</td>
                    <td>1.1.6</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref180">180</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Strict average risk</td>
                    <td>1.1.7</td>
                    <td>N/A<sup>a</sup></td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref181">181</xref>,<xref ref-type="bibr" rid="ref182">182</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>l</italic>-diversity</td>
                    <td>1.2</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref119">119</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>l</italic><sup>+</sup>-diversity</td>
                    <td>1.2.1</td>
                    <td><italic>l</italic> ∈ [0, +∞], <italic>θ</italic> ∈ [0, 1]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref120">120</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>t</italic>-closeness</td>
                    <td>1.3</td>
                    <td>[0, +∞]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref121">121</xref>,<xref ref-type="bibr" rid="ref122">122</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Stochastic <italic>t</italic>-closeness</td>
                    <td>1.3.1</td>
                    <td><italic>t</italic> ∈ [0, +∞], ε ∈ [0, +∞]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref123">123</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>c</italic>, <italic>t</italic>)-isolation</td>
                    <td>1.3.2</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref124">124</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>β-Likeness and enhanced β-likeness</td>
                    <td>1.3.3</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref125">125</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Differential privacy</td>
                    <td>1.4</td>
                    <td>[0, +∞]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref109">109</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>k</italic>, ε)-anonymity</td>
                    <td>1.4.1</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref126">126</xref>-<xref ref-type="bibr" rid="ref131">131</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(ε, δ)-anonymity</td>
                    <td>1.4.2</td>
                    <td>ε ∈ [0, +∞], δ ∈ [0, +∞]</td>
                    <td>ε: low, δ: low</td>
                    <td>[<xref ref-type="bibr" rid="ref132">132</xref>-<xref ref-type="bibr" rid="ref137">137</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(ε, <italic>m</italic>)-anonymity</td>
                    <td>1.4.3</td>
                    <td>ε ∈ [0, 1], <italic>m</italic> ∈ [1, +∞]</td>
                    <td>ε: high, <italic>m</italic>: high</td>
                    <td>[<xref ref-type="bibr" rid="ref118">118</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Distributed differential privacy</td>
                    <td>1.4.4</td>
                    <td>[0, +∞]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref138">138</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Distributional differential privacy</td>
                    <td>1.4.5</td>
                    <td>ε ∈ [0, +∞], δ ∈ [0, +∞]</td>
                    <td>ε: low, δ: low</td>
                    <td>[<xref ref-type="bibr" rid="ref139">139</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>d</italic>-χ-privacy</td>
                    <td>1.4.6</td>
                    <td>[0, +∞]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref140">140</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Joint differential privacy</td>
                    <td>1.4.7</td>
                    <td>ε ∈ [0, +∞], δ ∈ [0, +∞]</td>
                    <td>ε: low, δ: low</td>
                    <td>[<xref ref-type="bibr" rid="ref183">183</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>X</italic>, <italic>Y</italic>)-anonymity</td>
                    <td>1.5.1</td>
                    <td>[0, 1]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref141">141</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Normalized variance</td>
                    <td>1.5.2</td>
                    <td>[0, 1]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref142">142</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>δ-disclosure privacy</td>
                    <td>1.5.3</td>
                    <td>[0, +∞]</td>
                    <td>High</td>
                    <td>[<xref ref-type="bibr" rid="ref143">143</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>d</italic>,<italic>y</italic>)-privacy</td>
                    <td>1.5.4</td>
                    <td>[0, 1]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref144">144</xref>,<xref ref-type="bibr" rid="ref145">145</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>δ-presence</td>
                    <td>1.5.5</td>
                    <td>[0, 1]</td>
                    <td>Low</td>
                    <td>[<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref146">146</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Population and sample Uniqueness</td>
                    <td>1.5.6 or 1.5.7</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref79">79</xref>,<xref ref-type="bibr" rid="ref147">147</xref>-<xref ref-type="bibr" rid="ref151">151</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>Profitability</td>
                    <td>1.5.8</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref152">152</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Transactional</td>
                    <td><italic>k<sup>m</sup></italic>-anonymity</td>
                    <td>2</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref153">153</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Relational-transactional</td>
                    <td>(<italic>k</italic>, <italic>k<sup>m</sup></italic>)-anonymity</td>
                    <td>3</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref154">154</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td colspan="6">
                      <bold>Graph</bold>
                    </td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>k</italic>-degree</td>
                    <td>4.1</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref155">155</xref>-<xref ref-type="bibr" rid="ref158">158</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>k</italic><sup>2</sup> degree</td>
                    <td>4.2</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref156">156</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td><italic>k</italic>-automorphism</td>
                    <td>4.3</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref157">157</xref>,<xref ref-type="bibr" rid="ref159">159</xref>,<xref ref-type="bibr" rid="ref160">160</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>
                      <break/>
                    </td>
                    <td>(<italic>k</italic>, <italic>l</italic>)-anonymity</td>
                    <td>4.4</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref161">161</xref>,<xref ref-type="bibr" rid="ref162">162</xref>]</td>
                  </tr>
                  <tr valign="top">
                    <td>Geolocational</td>
                    <td>Historical <italic>k</italic>-anonymity</td>
                    <td>5</td>
                    <td>N/A</td>
                    <td>N/A</td>
                    <td>[<xref ref-type="bibr" rid="ref163">163</xref>]</td>
                  </tr>
                </tbody>
              </table>
              <table-wrap-foot>
                <fn id="table2fn1">
                  <p><sup>a</sup>N/A: not applicable.</p>
                </fn>
              </table-wrap-foot>
            </table-wrap>
          </sec>
          <sec>
            <title>Machine Learning–Based Privacy Models</title>
          </sec>
          <sec>
            <title>Two Categories</title>
            <p>In light of machine learning and its derived subset, deep learning, there has been an upsurge of interest in machine learning– or deep learning–based privacy models for anonymizing patient or general data; we explore these approaches in this section. We divided related machine learning–based privacy models into 2 categories in accordance with the type of data used: raw or synthetic. Of late, the use of synthetic data has become more popular because these generated data are both anonymous and realistic; therefore, consent from data owners is not required [<xref ref-type="bibr" rid="ref184">184</xref>]. The data in this category can be generated using techniques such as generative adversarial networks (GANs) [<xref ref-type="bibr" rid="ref185">185</xref>] and usually do not have the risk of reidentification; thus, research works concentrate on improving the utility of synthetic data.</p>
          </sec>
          <sec>
            <title>Models for Raw Data</title>
            <p>In the study by D’Acquisto and Naldi [<xref ref-type="bibr" rid="ref186">186</xref>], conventional principal component analysis (PCA) was used to anonymize sensitive data sets to achieve anonymization-utility trade-offs, that is, maximize both the information loss and utility. Different from its use in reducing the dimension of the data, where the smallest principal components are removed, PCA was instead adopted to remove the largest principal components before data projection. To measure the usefulness of the data anonymized through PCA, several utility metrics were presented; these are discussed in detail in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref> [<xref ref-type="bibr" rid="ref117">117</xref>,<xref ref-type="bibr" rid="ref172">172</xref>,<xref ref-type="bibr" rid="ref186">186</xref>-<xref ref-type="bibr" rid="ref213">213</xref>]. In the domain of data anonymization, the first work using PCA is termed as differentially private PCA [<xref ref-type="bibr" rid="ref214">214</xref>]. This technique explores the trade-off between the privacy and utility of low-rank data representations by guaranteeing DP. The study by Dwork et al [<xref ref-type="bibr" rid="ref215">215</xref>] suggested that noise be added directly to the covariance matrix before projection in PCA.</p>
            <p>Many similar PCA techniques rely on results derived from random matrix theory [<xref ref-type="bibr" rid="ref216">216</xref>-<xref ref-type="bibr" rid="ref219">219</xref>]. To reduce the computational cost of the privacy model, additive HE was used for PCA with a single data user [<xref ref-type="bibr" rid="ref217">217</xref>], where the rank of PCA with an unknown distribution could be adaptively estimated to achieve (𝜖, 𝛿)-DP [<xref ref-type="bibr" rid="ref218">218</xref>]. More recently, the concept of collaborative learning (or shared machine learning) [<xref ref-type="bibr" rid="ref94">94</xref>,<xref ref-type="bibr" rid="ref97">97</xref>,<xref ref-type="bibr" rid="ref220">220</xref>] became very popular in data anonymization. That is, the data collected from multiple parties are collectively used to improve the performance of model training while protecting individual data owners from any information disclosure. For instance, both HE and secret sharing were adopted in privacy-preserving PCA [<xref ref-type="bibr" rid="ref219">219</xref>] for horizontally partitioned data, that is, data sets share the same feature space but different sample space. In that work, HE could be substituted with secure multiparty computation (SMPC) [<xref ref-type="bibr" rid="ref221">221</xref>] for industrial use (more details are provided in <italic>SMPC Frameworks</italic> under <italic>Results</italic>).</p>
            <p>Despite the great success achieved by PCA and its variants in data anonymization, traditional clustering algorithms have also been adopted to deal with the same problem; 𝑘-means [<xref ref-type="bibr" rid="ref222">222</xref>], fuzzy c-means [<xref ref-type="bibr" rid="ref223">223</xref>,<xref ref-type="bibr" rid="ref224">224</xref>], Gaussian mixture model [<xref ref-type="bibr" rid="ref225">225</xref>,<xref ref-type="bibr" rid="ref226">226</xref>], spectral clustering [<xref ref-type="bibr" rid="ref227">227</xref>,<xref ref-type="bibr" rid="ref228">228</xref>], affinity propagation [<xref ref-type="bibr" rid="ref229">229</xref>], and density-based spatial clustering of applications with noise [<xref ref-type="bibr" rid="ref230">230</xref>,<xref ref-type="bibr" rid="ref231">231</xref>] are some of the algorithms that have been used for data anonymization. Most recently, anonymization solutions were proposed for privacy-preserving visual tasks in color images. For instance, the conventional 𝑘-nearest neighbor algorithm was combined with DP [<xref ref-type="bibr" rid="ref232">232</xref>] for privacy-preserving face attribute recognition and person reidentification. Homomorphic convolution was proposed by combining HE and secret sharing [<xref ref-type="bibr" rid="ref233">233</xref>] for visual object detection, and adversarial perturbation was devised to prevent disclosure of biometric information in finger-selfie images [<xref ref-type="bibr" rid="ref234">234</xref>].</p>
          </sec>
          <sec>
            <title>Models for Synthetic Data</title>
            <p>In the study by Choi et al [<xref ref-type="bibr" rid="ref95">95</xref>], GANs were adopted to generate realistic synthetic patient records (medical GAN [medGAN]; [<xref ref-type="bibr" rid="ref235">235</xref>]) by learning the distribution of real-world multilabel discrete EHRs. Concretely, medGAN was proposed to generate multilabel discrete patient records through the combination of an autoencoder and a GAN. Such a network supports the generation of both binary and numeric variables (ie, medical codes such as diagnosis, medication, and procedure codes) and the arrangement of records in a matrix format where each row corresponds to a patient and each column represents a specific medical code. The study by Baowaly et al [<xref ref-type="bibr" rid="ref236">236</xref>] extended the original medGAN by using both Wasserstein GANs with gradient penalty [<xref ref-type="bibr" rid="ref237">237</xref>] and boundary-seeking GANs [<xref ref-type="bibr" rid="ref96">96</xref>] to speed up model convergence and stability. In addition, GANs have also been used for segmenting medical images (ie, brain magnetic resonance imaging scans) while coping with privacy protection and data set imbalances [<xref ref-type="bibr" rid="ref238">238</xref>]. In other words, GANs have proven their potential in data augmentation for imbalanced data sets and data anonymization for privacy preservation. A conditional GAN framework— anonymization through data synthesis-GAN [<xref ref-type="bibr" rid="ref239">239</xref>]—was proposed to generate synthetic data while minimizing <italic>patient identifiability</italic>, which is based on the probability of reidentification given the combination of all data of any individual patient. In addition, DP has also been used in conjunction with GANs to generate synthetic EHRs [<xref ref-type="bibr" rid="ref240">240</xref>-<xref ref-type="bibr" rid="ref243">243</xref>]; most of these models were summarized in a recent survey [<xref ref-type="bibr" rid="ref244">244</xref>]. On the basis of the CP technique introduced in the previous section, the study by Tseng and Wu [<xref ref-type="bibr" rid="ref245">245</xref>] presented compressive privacy generative adversarial network to provide a data-driven local privatization scheme for creating compressed representations with lower dimensions for cloud services while removing sensitive information from raw images. Most recently, the conditional identity anonymization GAN [<xref ref-type="bibr" rid="ref246">246</xref>] was proposed for image and video anonymization based on conditional GANs [<xref ref-type="bibr" rid="ref247">247</xref>]. Concretely, conditional identity anonymization GAN supports the removal of identifiable information such as characteristics of human faces and bodies while guaranteeing the quality (granularity) of the generated images and videos.</p>
          </sec>
        </sec>
        <sec>
          <title>Disclosure Risk Assessments</title>
          <p>Given the conventional and machine learning–based privacy models, a disclosure risk assessment is usually conducted to measure the reidentification risk of the anonymized EHR data. In practice, risk values from different combinations of privacy models could be used when deciding which version of the anonymized data should be used for data analysis and possible machine learning tasks such as EHR classification with respect to treatment planning or distance recurrence identification.</p>
          <p>Concretely, there are 3 major types of disclosure that may occur during the process of data anonymization: identity, attribute, and membership disclosure (<xref ref-type="table" rid="table3">Table 3</xref>). For practical guidance, we have provided a comparative summary in <xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref> [<xref ref-type="bibr" rid="ref248">248</xref>-<xref ref-type="bibr" rid="ref251">251</xref>] of most of the 35 conventional privacy models investigated (in terms of parameter value ranges and privacy levels).</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Categorization of data reidentification risk metrics for electronic health record data.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="230"/>
              <col width="310"/>
              <col width="330"/>
              <col width="130"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Disclosure type and metric</td>
                  <td>Section in <xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref></td>
                  <td>Reference</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Identity</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Average risk</td>
                  <td>1</td>
                  <td>N/A<sup>a</sup></td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Overall risk</td>
                  <td>1</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>β-Likeness</td>
                  <td>1</td>
                  <td>[<xref ref-type="bibr" rid="ref125">125</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Distance-linked disclosure</td>
                  <td>2</td>
                  <td>[<xref ref-type="bibr" rid="ref248">248</xref>]</td>
                </tr>
                <tr valign="top">
                  <td colspan="4">
                    <bold>Attribute</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Probabilistic linkage disclosure</td>
                  <td>2</td>
                  <td>[<xref ref-type="bibr" rid="ref249">249</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Interval disclosure</td>
                  <td>2</td>
                  <td>[<xref ref-type="bibr" rid="ref250">250</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>Membership</td>
                  <td>Log-linear models</td>
                  <td>3</td>
                  <td>[<xref ref-type="bibr" rid="ref251">251</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>N/A: not applicable.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Usability Measurements</title>
          <p>The metrics used for measuring the usefulness of the anonymized data can be treated as an on-demand component of a data anonymization system. We revisit the proposed quantitative metrics in this section, although this important indicator is usually not fully covered in the off-the-shelf privacy model–based data anonymization tools. In addition, qualitative metrics are not covered in this study. This is due to the varied objectives of different data anonymization activities, including the evaluation of anonymization quality that is performed by health care professionals. <xref ref-type="table" rid="table4">Table 4</xref> lists the selected data usability metrics and the type of data for which they are suitable.</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Categorization of data usability metrics.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="440"/>
              <col width="0"/>
              <col width="400"/>
              <col width="0"/>
              <col width="130"/>
              <thead>
                <tr valign="top">
                  <td colspan="3">Data type and metric</td>
                  <td colspan="2">Section in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref></td>
                  <td>References</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="6">
                    <bold>Numerical and categorical</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Information loss and its variants</td>
                  <td colspan="2">1.1</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref172">172</xref>,<xref ref-type="bibr" rid="ref187">187</xref>-<xref ref-type="bibr" rid="ref189">189</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Privacy gain</td>
                  <td colspan="2">1.2</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref190">190</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Discernibility</td>
                  <td colspan="2">1.3</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref191">191</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Average equivalence class size</td>
                  <td colspan="2">1.4</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref117">117</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Matrix norm</td>
                  <td colspan="2">1.5</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref192">192</xref>,<xref ref-type="bibr" rid="ref193">193</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Correlation</td>
                  <td colspan="2">1.6</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref194">194</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Divergence</td>
                  <td colspan="2">1.7</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref195">195</xref>,<xref ref-type="bibr" rid="ref196">196</xref>]</td>
                </tr>
                <tr valign="top">
                  <td colspan="6">
                    <bold>Image<sup>a</sup></bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Mean squared error and its variants</td>
                  <td colspan="2">2.1</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref197">197</xref>-<xref ref-type="bibr" rid="ref200">200</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Peak signal-to-noise ratio</td>
                  <td colspan="2">2.2</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref201">201</xref>-<xref ref-type="bibr" rid="ref206">206</xref>]</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Structural similarity index</td>
                  <td colspan="2">2.3</td>
                  <td colspan="2">[<xref ref-type="bibr" rid="ref207">207</xref>,<xref ref-type="bibr" rid="ref208">208</xref>]</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>Any type of raw and anonymized electronic health record data that can be converted into an image.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
      </sec>
      <sec>
        <title>Existing Privacy Model–Based Data Anonymization Tools</title>
        <p>In this section, several off-the-shelf data anonymization tools based on conventional privacy models and operations are detailed. These tools are commonly adopted for anonymizing tabular data. It should be noted that EHRs are usually organized in the tabular data format and that the real difficulties of anonymizing tabular data lie in the inherent bias and presumption of the availability of limited forecast-linkable data. Therefore, we investigated 14 data anonymization toolboxes, all of which share a similar workflow (summarized in <xref rid="figure8" ref-type="fig">Figure 8</xref> and compared in <xref ref-type="table" rid="table5">Table 5</xref> and <xref ref-type="table" rid="table6">Table 6</xref>). Functionally similar toolboxes are introduced together below.</p>
        <fig id="figure8" position="float">
          <label>Figure 8</label>
          <caption>
            <p>Overall results of the systematic literature mapping study. This mapping consists of four contextually consecutive parts (from bottom to top): basic anonymization operations, existing privacy models, metrics proposed to measure re-identification risk and degree of usability of the anonymized data, and off-the-shelf data anonymization software tools. ADS-GAN: anonymization through data synthesis using generative adversarial networks; AP: affinity propagation; BL: β-Likeness; CIAGAN: conditional identity anonymization generative adversarial network; CPGAN: compressive privacy generative adversarial network; DBSCAN: density-based spatial clustering of apps with noise; DP: differential privacy; DPPCA: differentially private principal component analysis; FCM: fuzzy c-means; G: graph; GAN: generative adversarial network; GL: geolocational; GMM: Gaussian mixture model; HE: homomorphic encryption; IL: information loss; ILPG: ratio of information loss to privacy gain; KA: <italic>k</italic>-Anonymity; <italic>k</italic>NN+DP: <italic>k</italic>-nearest neighbor+differential privacy; LD: <italic>l</italic>-Diversity; medGAN: medical generative adversarial network; ML: machine learning; PCA: principal component analysis; PG: privacy gain; PPPCA: privacy-preserving principal component analysis; R: relational; RT: relational-transactional; SC: spectral clustering; T: transactional; TC: <italic>t</italic>-Closeness.</p>
          </caption>
          <graphic xlink:href="medinform_v9i10e29871_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Comparison of the off-the-shelf privacy model–based data anonymization tools in terms of available development options, anonymization functionality and risk metrics.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="180"/>
            <col width="140"/>
            <col width="90"/>
            <col width="80"/>
            <col width="110"/>
            <col width="100"/>
            <col width="110"/>
            <col width="0"/>
            <col width="110"/>
            <col width="0"/>
            <col width="80"/>
            <thead>
              <tr valign="top">
                <td>Tool</td>
                <td>Last release</td>
                <td colspan="6">Development support</td>
                <td colspan="2">Anonymization</td>
                <td>Risk assessment</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Open source</td>
                <td>Public API<sup>a</sup></td>
                <td>Extensibility</td>
                <td>Cross-platform</td>
                <td>Programming language</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>ARX</td>
                <td>November 2019</td>
                <td>✓<sup>b</sup></td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
              </tr>
              <tr valign="top">
                <td>Amnesia</td>
                <td>October 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>μ-ANT<sup>c</sup> </td>
                <td>August 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Anonimatron</td>
                <td>August 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>SECRETA<sup>d</sup></td>
                <td>June 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>C++</td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>sdcMicro</td>
                <td>May 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>Poorly supported</td>
                <td>✓</td>
                <td>R</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
              </tr>
              <tr valign="top">
                <td>Aircloak Insights</td>
                <td>April 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>Ruby</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>NLM<sup>e</sup> Scrubber</td>
                <td>April 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>Perl</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Anonymizer</td>
                <td>March 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>Ruby</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Shiny Anonymizer</td>
                <td>February 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>R</td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>μ-ARGUS</td>
                <td>March 2018</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>C++</td>
                <td colspan="2">✓</td>
                <td colspan="2">✓</td>
              </tr>
              <tr valign="top">
                <td>UTD<sup>f</sup> Toolbox</td>
                <td>April 2010</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>Poorly supported</td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>OpenPseudonymiser</td>
                <td>November 2011</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>TIAMAT<sup>g</sup></td>
                <td>2009</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>Java</td>
                <td colspan="2">✓</td>
                <td colspan="2">
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Cornell Toolkit</td>
                <td>2009</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>Poorly supported</td>
                <td>✓</td>
                <td>C++</td>
                <td colspan="2">✓</td>
                <td colspan="2">Poorly supported</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>API: application programming interface.</p>
            </fn>
            <fn id="table5fn2">
              <p><sup>b</sup>Feature present.</p>
            </fn>
            <fn id="table5fn3">
              <p><sup>c</sup>μ-ANT: microaggregation-based anonymization tool.</p>
            </fn>
            <fn id="table5fn4">
              <p><sup>d</sup>SECRETA: System for Evaluating and Comparing RElational and Transaction Anonymization.</p>
            </fn>
            <fn id="table5fn5">
              <p><sup>e</sup>NLM: National Library of Medicine.</p>
            </fn>
            <fn id="table5fn6">
              <p><sup>f</sup>UTD: University of Texas at Dallas.</p>
            </fn>
            <fn id="table5fn7">
              <p><sup>g</sup>TIAMAT: Tool for Interactive Analysis of Microdata Anonymization Techniques.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Comparison of the off-the-shelf privacy model–based data anonymization tools with respect to the supported privacy models.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="140"/>
            <col width="80"/>
            <col width="90"/>
            <col width="70"/>
            <col width="70"/>
            <col width="70"/>
            <col width="50"/>
            <col width="80"/>
            <col width="80"/>
            <col width="80"/>
            <col width="90"/>
            <col width="100"/>
            <thead>
              <tr valign="top">
                <td>Tool</td>
                <td>Last release</td>
                <td colspan="10">Privacy models</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td><italic>k</italic>-anonymity</td>
                <td><italic>l</italic>-diversity</td>
                <td><italic>t</italic>-closeness</td>
                <td>δ-presence</td>
                <td><italic>k</italic>-map</td>
                <td>(<italic>k</italic>, <italic>g</italic>)-anonymity</td>
                <td>(<italic>k</italic>, ε)-anonymity</td>
                <td>(ε, δ)-anonymity</td>
                <td><italic>k<sup>m</sup></italic>-anonymity</td>
                <td>(<italic>k</italic>, <italic>k<sup>m</sup></italic>)-anonymity</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>ARX</td>
                <td>November 2019</td>
                <td>✓<sup>a</sup></td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Amnesia</td>
                <td>October 2019</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>μ-ANT<sup>b</sup> </td>
                <td>August 2019</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Anonimatron</td>
                <td>August 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>SECRETA<sup>c</sup></td>
                <td>June 2019</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>✓</td>
              </tr>
              <tr valign="top">
                <td>sdcMicro</td>
                <td>May 2019</td>
                <td>✓</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Aircloak Insights</td>
                <td>April 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>NLM<sup>d</sup> Scrubber</td>
                <td>April 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Anonymizer</td>
                <td>March 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Shiny Anonymizer</td>
                <td>February 2019</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>μ-ARGUS</td>
                <td>March 2018</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>UTD<sup>e</sup> Toolbox</td>
                <td>April 2010</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>OpenPseudonymiser</td>
                <td>November 2011</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>TIAMAT<sup>f</sup></td>
                <td>2009</td>
                <td>✓</td>
                <td>✓</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>Cornell Toolkit</td>
                <td>2009</td>
                <td>
                  <break/>
                </td>
                <td>✓</td>
                <td>✓</td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table6fn1">
              <p><sup>a</sup>Feature present.</p>
            </fn>
            <fn id="table6fn2">
              <p><sup>b</sup>μ-ANT: microaggregation-based anonymization tool.</p>
            </fn>
            <fn id="table6fn3">
              <p><sup>c</sup>SECRETA: System for Evaluating and Comparing RElational and Transaction Anonymization.</p>
            </fn>
            <fn id="table6fn4">
              <p><sup>d</sup>NLM: National Library of Medicine.</p>
            </fn>
            <fn id="table6fn5">
              <p><sup>e</sup>UTD: University of Texas at Dallas.</p>
            </fn>
            <fn id="table6fn6">
              <p><sup>f</sup>TIAMAT: Tool for Interactive Analysis of Microdata Anonymization Techniques.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Amnesia [<xref ref-type="bibr" rid="ref252">252</xref>] supports 2 privacy models, <italic>k<sup>m</sup></italic>-anonymity and <italic>k</italic>-anonymity; the former is used for set-valued and relational-set data sets, and the latter is used for tabular data. Amnesia does not support any reidentification risk assessment; the authors claim that there is no risk associated with the anonymized data set because every query on the anonymized attributes will return at least <italic>k</italic> records.</p>
        <p>Anonimatron [<xref ref-type="bibr" rid="ref253">253</xref>] state that it has been GDPR-compliant since 2010. It supports working with several databases out of the box. It can also be used with text files. The software conducts search-and-replace tasks based on custom rules and as such is merely a pseudonymization tool; however, it is extensible because of its open-source nature.</p>
        <p>ARX [<xref ref-type="bibr" rid="ref164">164</xref>,<xref ref-type="bibr" rid="ref181">181</xref>,<xref ref-type="bibr" rid="ref254">254</xref>] was originally developed for biomedical data anonymization. In terms of conventional privacy models, ARX mainly supports 6 additional privacy models: (1) strict average risk, (2) population uniqueness, (3) sample uniqueness, (4) δ-disclosure privacy, (5) β-likeness, and (6) profitability. The population uniqueness can be measured using 4 different models described in the studies by Pitman [<xref ref-type="bibr" rid="ref148">148</xref>], Zayataz [<xref ref-type="bibr" rid="ref149">149</xref>], Chen and McNulty [<xref ref-type="bibr" rid="ref150">150</xref>], and Dankar et al [<xref ref-type="bibr" rid="ref255">255</xref>]. For <italic>t</italic>-closeness, there are 3 different variants for categorical and numeric data. The profitability privacy model is a game-theoretic model used to conduct cost-benefit analysis and maximize the monetary gains of the data publisher [<xref ref-type="bibr" rid="ref152">152</xref>]. ARX is open source [<xref ref-type="bibr" rid="ref256">256</xref>] and supports data of high dimensionality. It is available as a library to be integrated into custom projects or as an installable graphical user interface tool. Similar to ARX, the microaggregation-based anonymization tool (μ-ANT) [<xref ref-type="bibr" rid="ref257">257</xref>] is also open source [<xref ref-type="bibr" rid="ref258">258</xref>] and extensible. μ-ANT supports 2 privacy models, <italic>k<sup>m</sup></italic>-anonymity and <italic>k</italic>-anonymity, as well as <italic>t</italic>-closeness [<xref ref-type="bibr" rid="ref122">122</xref>]. With respect to usability measurements, μ-ANT supports both information loss and sum of the squared errors. However, μ-ANT does not support functions for filling the missing attribute values (this requires manual data preprocessing, instead, either by removal or filling with average values) or metrics to evaluate the reidentification risk of the anonymized data.</p>
        <p>sdcMicro [<xref ref-type="bibr" rid="ref259">259</xref>] supports 2 privacy models (<italic>k</italic>-anonymity and <italic>l</italic>-diversity) in conjunction with recoding, suppression, postrandomization method (PRAM; which works on categorical data and is usually treated as encompassing noise addition, data suppression, and data recoding. Specifically, each value of a categorical attribute is mapped to a different value in accordance with a prescribed Markov matrix, that is, PRAM matrix), noise addition, and microaggregation. Apart from these functions, this tool also supports the measurement of reidentification risk. As a tool similar to sdcMicro, μ-ARGUS [<xref ref-type="bibr" rid="ref260">260</xref>] has been implemented in multiple programming languages. It supports anonymization of both microdata and tabular data. It is packaged as disclosure control software and includes <italic>k</italic>-anonymity, recoding (generalization), suppression, PRAM, noise, and microaggregation. Compared with sdcMicro and μ-ARGUS, both University of Texas at Dallas Toolbox [<xref ref-type="bibr" rid="ref261">261</xref>] and Tool for Interactive Analysis of Microdata Anonymization Techniques [<xref ref-type="bibr" rid="ref262">262</xref>] support 3 privacy models but lack a risk-assessment module. In addition, University of Texas at Dallas Toolbox was compared with ARX in the study by Prasser et al [<xref ref-type="bibr" rid="ref263">263</xref>] because of their similar automated anonymization processes and perspectives (in both, the data set is treated as population data, describing one individual per record). In this comparison, ARX showed better performance with respect to execution times and measured data utility.</p>
        <p>SECRETA (System for Evaluating and Comparing RElational and Transaction Anonymization) [<xref ref-type="bibr" rid="ref264">264</xref>] handles 3 categories of data: relational data, transactional data, and relational-transactional data, which are respectively supported by <italic>k</italic>-anonymity and its variants, <italic>k<sup>m</sup></italic>-anonymity and (<italic>k</italic>, <italic>k<sup>m</sup></italic>)-anonymity. For relational data sets, SECRETA supports various schemes for data generalization, including full-domain generalization, subtree generalization, and multidimensional generalization. For transactional data, it supports <italic>k<sup>m</sup></italic>-anonymity using hierarchy-based generalization and constraint-based generalization. For measuring the risk of reidentification, the standalone Identification of Privacy Vulnerabilities toolkit [<xref ref-type="bibr" rid="ref265">265</xref>] is used.</p>
        <p>Aircloak Insights [<xref ref-type="bibr" rid="ref266">266</xref>,<xref ref-type="bibr" rid="ref267">267</xref>] can be deemed a data pseudonymization tool because it does not tackle any task of data anonymization. Concretely, by investigating 2 research studies [<xref ref-type="bibr" rid="ref266">266</xref>,<xref ref-type="bibr" rid="ref267">267</xref>], we argue that Aircloak Insights is focused more on data protection than on data anonymization. Aircloak Insights comes with a Diffix backend [<xref ref-type="bibr" rid="ref267">267</xref>], which is essentially a middleware proxy to add noise to user queries for database access in an encrypted fashion. This is also inconsistent with what the authors announced on their official website: “Our privacy-preserving analytics solution uses patented and proven data anonymization that provides GDPR-compliant and high-fidelity insights” [<xref ref-type="bibr" rid="ref268">268</xref>]. Nevertheless, a number of summarized attacks [<xref ref-type="bibr" rid="ref267">267</xref>] may be used for validating the efficiency and efficacy of the data anonymization toolbox associated with the Aircloak pipeline.</p>
        <p>National Library of Medicine-Scrubber [<xref ref-type="bibr" rid="ref269">269</xref>] is an anonymization software tool that is specifically designed for coping with unstructured clinical text data. As such, <italic>k</italic>-anonymity is not applicable. Privacy is achieved by applying the HIPAA Safe Harbor model. National Library of Medicine-Scrubber treats text data anonymization as a process of eliminating a specific set of identifiers from the data, and the level of anonymization depends on the comprehensiveness of the identifier lookup data source. In addition, the reidentification risk measurement is not considered in this tool because the authors think that there is no established measure for reidentification of the patient from an anonymized text document.</p>
        <p>OpenPseudonymiser [<xref ref-type="bibr" rid="ref270">270</xref>] and ShinyAnonymizer [<xref ref-type="bibr" rid="ref271">271</xref>] are very similar: both conduct data encryption only, although they have been specifically designed for medical data. As they only perform data encryption, they are not adequate for data anonymization. Concretely, they support a number of hashing functions (eg, MD5 and SHA512) and encryption algorithms (eg, data encryption standard and advanced encryption standard). Although they support several fundamental data anonymization operations (eg, removing information, suppression, generalization, and bottom and top coding), they do not implement any of the operations in line with privacy models. In addition, they do not provide tools for calculating the risk of reidentification or the measurement of data utility. Similarly, Anonymizer [<xref ref-type="bibr" rid="ref272">272</xref>] was introduced as a universal tool to create anonymized databases. This tool replaces all data in the given database with anonymized random data where the unique, alphanumeric values are generated by the MD5 hashing function. To this end, the anonymized data might be less useful in view of the authors’ announcement [<xref ref-type="bibr" rid="ref273">273</xref>]: “There is no way to keep nonanonymized rows in a table”; thus, this software tool is useful for database randomization rather than anonymization.</p>
        <p>The Cornell Toolkit [<xref ref-type="bibr" rid="ref274">274</xref>] supports <italic>l</italic>-diversity and <italic>t</italic>-closeness with flexible parameter configurations. Although the software supports the ability to display the disclosure risk of reidentification of the original tabular data, the method or methods used for implementing the risk measurement have not been introduced in either the paper [<xref ref-type="bibr" rid="ref274">274</xref>] or in the documentation on the web [<xref ref-type="bibr" rid="ref275">275</xref>], leaving this software with a low degree of explainability and, hence, trustworthiness.</p>
      </sec>
      <sec>
        <title>Existing Machine Learning–Based Data Anonymization Tools</title>
        <sec>
          <title>Two Classes</title>
          <p>Recently, in response to the GDPR and DPA regulations, efforts were made by the machine learning and cryptography communities to develop privacy-preserving machine learning methods. We define privacy-preserving methods as any machine learning method or tool that has been designed with data privacy as a fundamental concept (usually in the form of data encryption) and that can typically be divided into 2 classes: those that use SMPC and those that use fully HE (FHE). All the investigated machine learning–based data anonymization tools are compared in <xref ref-type="table" rid="table7">Table 7</xref>.</p>
          <table-wrap position="float" id="table7">
            <label>Table 7</label>
            <caption>
              <p>Comparison of existing machine learning–based data anonymization tools. The Largest model tested column reports the number of parameters in the largest model shown in the respective tool’s original paper (when reported); CrypTFlow has been shown to work efficiently on much larger machine learning models than the other available privacy-preserving machine learning tools.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="120"/>
              <col width="80"/>
              <col width="60"/>
              <col width="90"/>
              <col width="80"/>
              <col width="0"/>
              <col width="130"/>
              <col width="0"/>
              <col width="140"/>
              <col width="0"/>
              <col width="90"/>
              <col width="90"/>
              <col width="120"/>
              <thead>
                <tr valign="top">
                  <td>Tool</td>
                  <td colspan="5">Encryption methods</td>
                  <td colspan="2">Reidentification risk assessment</td>
                  <td colspan="2">Usability measurement</td>
                  <td colspan="3">Development support</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>SMPC<sup>a</sup></td>
                  <td>FHE<sup>b</sup></td>
                  <td>Differential privacy</td>
                  <td>Federated learning</td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">Supports training</td>
                  <td>Malicious security</td>
                  <td>Largest model tested</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>CrypTen</td>
                  <td>✓<sup>c</sup></td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>N/A<sup>d</sup></td>
                </tr>
                <tr valign="top">
                  <td>TF Encrypted</td>
                  <td>✓</td>
                  <td>✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>✓</td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>419,720</td>
                </tr>
                <tr valign="top">
                  <td>PySyft</td>
                  <td>✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>✓</td>
                  <td>✓</td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>CrypTFlow</td>
                  <td>✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>✓</td>
                  <td>65×10<sup>6</sup></td>
                </tr>
                <tr valign="top">
                  <td>CHET</td>
                  <td>
                    <break/>
                  </td>
                  <td>✓</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>421,098</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table7fn1">
                <p><sup>a</sup>SMPC: secure multiparty computation.</p>
              </fn>
              <fn id="table7fn2">
                <p><sup>b</sup>FHE: fully homomorphic encryption.</p>
              </fn>
              <fn id="table7fn3">
                <p><sup>c</sup>Feature present.</p>
              </fn>
              <fn id="table7fn4">
                <p><sup>d</sup>N/A: not applicable.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>SMPC Frameworks</title>
          <p>SMPC involves a problem in which <italic>n</italic> parties, each with their own private input <italic>x<sub>1</sub>, x<sub>2</sub>,..., x<sub>n</sub></italic> where party <italic>i</italic> has access to input <italic>x<sub>i</sub></italic> (and only <italic>x<sub>i</sub></italic>), wish to compute some function <italic>f</italic>(<italic>x<sub>1</sub>, x<sub>2</sub>,..., x<sub>n</sub></italic>) without revealing any information about their private data [<xref ref-type="bibr" rid="ref276">276</xref>] to the other parties. Most SMPC frameworks assume the parties to be semihonest: under this scheme we assume that malicious parties still follow the set protocol (although they may work together to attempt to extract private information). The current state-of-the-art framework for SMPC is SPDZ [<xref ref-type="bibr" rid="ref277">277</xref>], and it is upon this framework that many SMPC-based machine learning libraries are built. This allows data owners to keep their data private and also allows for the machine learning model to be hidden. However, it does require at least three trusted, noncolluding parties or servers to work together to provide the highest level of protection; this can mean it is difficult to implement in practice. There are also significant overheads with this method; not only do SPDZ algorithms necessarily take longer to compute (because of cryptographic overhead), but there is also a significant amount of communication that needs to take place among all participating parties. This results in SMPC machine learning models running approximately 46 times slower than plaintext variants [<xref ref-type="bibr" rid="ref278">278</xref>], meaning that it is impractical to use such models with large and complex data sets.</p>
          <p>There are several different practical implementations of this type of protocol, although none are ready for use in production environments. CrypTen [<xref ref-type="bibr" rid="ref279">279</xref>] is a library that supports privacy-preserving machine learning with PyTorch. CrypTen currently supports SMPC (although support for other methods such as FHE is in development) by providing SMPC-encrypted versions of tensors and many PyTorch functions; it also includes a tool for encrypting a pre-existing PyTorch model. Although CrypTen supports many of PyTorch’s existing functions, it still has certain limitations. Most notably, it does not currently support graphics processing unit computation, which significantly hinders its ability to be used in conjunction with large, complex models. TensorFlow (TF) Encrypted [<xref ref-type="bibr" rid="ref280">280</xref>] is a similar framework for the TF open-source software library for machine learning that also supports SMPC through the SPDZ framework. TF Encrypted also includes support for federated learning (which allows the training of machine learning models to be distributed over many devices without each device needing to reveal its private data) and HE.</p>
          <p>PySyft [<xref ref-type="bibr" rid="ref278">278</xref>] is a more general framework than CrypTen or TF Encrypted because it supports multiple machine learning libraries (including TF and PyTorch) and multiple privacy methods. As part of this, it features SMPC-based machine learning, much like CrypTen and TF Encrypted, but also allows for additional layers of security to be incorporated into the model such as DP and federated learning. It is also possible to use TF Encrypted as the provider for TF-based encryption using PySyft, allowing for tighter integration between the 2 libraries. Similar to CrypTen and TF Encrypted, PySyft is a high-level library that attempts to make it easy for machine learning researchers to transition to build privacy-preserving models. However, PySyft should currently only be used as a research tool because many of its underlying protocols are not secure enough to be used with confidence.</p>
          <p>CrypTFlow [<xref ref-type="bibr" rid="ref281">281</xref>] differs from the aforementioned libraries in that it is a compiler for TF models rather than a programming interface. CrypTFlow takes a TF model as an input and outputs code that can run under an SMPC model. An advantage that CrypTFlow has over CrypTen, TF Encrypted, and PySyft is that, as part of its compilation process, CrypTFlow performs a number of optimization steps that in the other libraries would have to be done by hand or cannot be performed at all. For example, when converting floating-point numbers to a fixed-precision representation (which is necessary because SMPC works inside a finite field), CrypTFlow chooses the smallest precision level that will match the classification accuracy of floating-point code. This, along with the other optimizations performed during the compilation process, means that it is possible to (efficiently) run much larger models in CrypTFlow than may be possible in other libraries. The possible real-world impact of CrypTFlow has been shown by running 2 networks designed for predicting lung disease from chest x-rays [<xref ref-type="bibr" rid="ref282">282</xref>] and diabetic retinopathy [<xref ref-type="bibr" rid="ref283">283</xref>] from retinal images. It is also possible to use CrypTFlow in conjunction with secure enclaves such as Software Guard Extension 41 (Intel Corporation) to work within the stricter malicious security assumptions; this is stricter than assuming semihonest parties because malicious parties may deviate from the defined protocol. The provision of malicious security means that CrypTFlow is more suitable for use in environments where extreme caution must be taken with the data set being used. Similar to CrypTen, the main issue with CrypTFlow is that it currently does not support the training of machine learning models because it is difficult to use the graphics processing unit in such a setting, meaning that there is still the need to be able to process plaintext data during the training process, which is not compatible with many of the scenarios where one may want to use privacy-preserving machine learning techniques.</p>
          <p>An example of how SMPC protocols and SMPC-supporting machine learning libraries can be used is shown in the study by Hong et al [<xref ref-type="bibr" rid="ref284">284</xref>], which used TF Encrypted to train a classifier on 2 genomic data sets, each containing a large number of features (12,634 and 17,814 features per sample), to detect tumors as part of the iDASH challenge. This task had an additional challenge because the 2 data sets were heavily imbalanced, but common countermeasures to this are difficult to implement in an SMPC framework. For example, resampling is commonly used to overcome this, but because the labels are private in SMPC, this is impossible. To overcome the imbalance, the weighting of samples in the loss function was adjusted to place a higher emphasis on those from the minority class. The study’s best results had an accuracy of 69.48%, which is close to the classifier trained on the plaintext data, which showed an accuracy of 70%. This demonstrates that it is possible to train machine learning models on encrypted data; the study also noted that the TF Encrypted framework is easy to use for anyone familiar with TF, meaning that privacy-preserving machine learning is accessible to experts from both machine learning and cryptography fields.</p>
          <p>CrypTen, TF Encrypted, and PySyft all have the advantage that they work closely with commonly used machine learning libraries (PyTorch, TF, and both PyTorch and TF, respectively), meaning that there is less of a learning curve required to make the existing models privacy preserving compared with tools such as CrypTFlow. This ease of use comes at the cost of efficiency, however, because more complex tools such as CrypTFlow are able to work at a lower level and perform more optimizations, allowing larger models to be encrypted.</p>
        </sec>
        <sec>
          <title>Fully HE</title>
          <p>HE is a type of encryption wherein the result of computations on the encrypted data, when decrypted, mirror the result of the same computations carried out on the plaintext data. Specifically, FHE is an encryption protocol that supports any computation on the ciphertext. Attempts have been made to apply FHE to machine learning [<xref ref-type="bibr" rid="ref285">285</xref>,<xref ref-type="bibr" rid="ref286">286</xref>]. Traditionally, because of the significant computational overhead required to run FHE computations, these models were trained in plaintext data; for example, it took 570 seconds to evaluate CryptoNet on the Modified National Institute of Standards and Technology data set [<xref ref-type="bibr" rid="ref285">285</xref>]. It is only recently that we have been able to train a full classification model using FHE computations [<xref ref-type="bibr" rid="ref36">36</xref>]. The main benefit of FHE over SMPC is that it does not require multiple and separate trusted parties; the models can be trained and run on encrypted data by a single entity. This makes FHE a more promising prospect than SMPC for problems involving data that are too sensitive to be entrusted to multiple parties (or in situations where multiple trusted parties may not be available).</p>
          <p>Applying FHE to privacy-preserving machine learning is a relatively new area of research, and thus there are few tools that tie the 2 concepts together, with most research focusing on specific model implementations rather than on creating a general framework for FHE machine learning. One such tool, however, is CHET [<xref ref-type="bibr" rid="ref287">287</xref>]. CHET is an optimizing compiler that takes a tensor circuit as an input and outputs an executable that can then be run with HE libraries such as Simple Encrypted Arithmetic Library (Microsoft Research) [<xref ref-type="bibr" rid="ref288">288</xref>] or Homomorphic Encryption for Arithmetic of Approximate Numbers [<xref ref-type="bibr" rid="ref289">289</xref>]. This automates many of the laborious processes (eg, encryption parameter setting) that are required when creating circuits that work with FHE libraries; these processes also require FHE domain knowledge, which we cannot expect many machine learning experts to possess. Hence, the use of CHET can result in more efficient FHE models. For example, the authors of CHET claim that it reduces the running time for analyzing a particular medical image model (provided by their industry partners) from 18 hours (the original, unoptimized FHE model) to just 5 minutes. However, despite CHET using numerous optimizing methods during its compilation phase, the resulting encrypted models are still restrictively slow (when compared with their nonencrypted counterparts). Not only does this mean it is only practical to use CHET with smaller models, but it also means that it is impractical to train a model using CHET. It is also important to consider whether FHE provides a level of security and privacy that is high enough for the task at hand; some current regulations argue that encryption is a form of pseudonymization rather than anonymization [<xref ref-type="bibr" rid="ref290">290</xref>] because it is possible to decrypt encrypted data.</p>
        </sec>
      </sec>
      <sec>
        <title>Legal Framework Support</title>
        <p>Although general data protection laws such as GDPR and DPA and health care–specific guidelines have been proposed for a while, data anonymization practitioners still demand a combined and intuitive reference list to check. In this discussion, we tentatively construct a policy base by collecting and sorting the available guidance provided by 4 lawful aspects in an effort to benefit future intelligent data anonymization for health care.</p>
        <p>The policy base was constructed by considering the documentation provided in accordance with legal frameworks and guidelines proposed by government-accountable institutions, that is, the GDPR, particularly Article 5 [<xref ref-type="bibr" rid="ref291">291</xref>]; the DPA [<xref ref-type="bibr" rid="ref292">292</xref>]; the ICO (mainly based on the code of practice); and the NHS (with documents published in 2013 [<xref ref-type="bibr" rid="ref293">293</xref>], 2015 [<xref ref-type="bibr" rid="ref294">294</xref>], 2017 [<xref ref-type="bibr" rid="ref75">75</xref>], 2019 [<xref ref-type="bibr" rid="ref74">74</xref>,<xref ref-type="bibr" rid="ref295">295</xref>], and 2021 [<xref ref-type="bibr" rid="ref296">296</xref>,<xref ref-type="bibr" rid="ref297">297</xref>]). Fundamentally, any organization (eg, the NHS or a UK company) that holds personal identifiable information is required to register with the ICO, and subsequently perform possible data anonymization followed by a reidentification risk assessment to evaluate the effectiveness of the anonymized data in line with the DPA (the UK implementation of the GDPR). In the case where the NHS or a UK company realizes that a data breach has occurred, it is required to report this to the ICO. In addition, the ICO provides guidance to help the NHS or UK companies to better understand the lawful basis for processing sensitive information. Recently, the ICO [<xref ref-type="bibr" rid="ref298">298</xref>] and the European Data Protection Board [<xref ref-type="bibr" rid="ref299">299</xref>] published their statements on the processing of personal identifiable data in coping with the COVID-19 outbreak.</p>
        <p>From the NHS perspective, pseudonyms should be used on a one-off and consistent basis. In terms of the best practice recommendations, they recommend adopting cryptographic hash functions (eg, MD5, SHA-1, and SHA-2) to create a fixed-length hash. We argue that the encrypted data might be less useful for possible later data analysis and explainability research. We summarize the suggestions provided by the 4 aforementioned entities in <xref ref-type="boxed-text" rid="box2">Textbox 2</xref>.</p>
        <boxed-text id="box2" position="float">
          <title>Guidance provided by 4 lawful aspects.</title>
          <p>
            <bold>General Data Protection Regulation</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Accuracy</p>
            </list-item>
            <list-item>
              <p>Accountability</p>
            </list-item>
            <list-item>
              <p>Storage limitation</p>
            </list-item>
            <list-item>
              <p>Purpose limitation</p>
            </list-item>
            <list-item>
              <p>Data minimization</p>
            </list-item>
            <list-item>
              <p>Purpose limitation</p>
            </list-item>
            <list-item>
              <p>Lawfulness, fairness, and transparency</p>
            </list-item>
          </list>
          <p>
            <bold>Data Protection Act</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Notify any personal data breach</p>
            </list-item>
            <list-item>
              <p>Settle system interruption or restoration</p>
            </list-item>
            <list-item>
              <p>Implement disclosure-risk measures</p>
            </list-item>
            <list-item>
              <p>Define legal basis for data processing</p>
            </list-item>
            <list-item>
              <p>Establish precise details of any processing</p>
            </list-item>
            <list-item>
              <p>Prevent unauthorized processing and inference</p>
            </list-item>
            <list-item>
              <p>Conduct data protection impact assessment</p>
            </list-item>
            <list-item>
              <p>Test anonymization effectiveness through reidentification</p>
            </list-item>
            <list-item>
              <p>No intent, threaten, or damage to cause in reidentification</p>
            </list-item>
            <list-item>
              <p>Ensure data integrity when malfunctions occur</p>
            </list-item>
          </list>
          <p>
            <bold>Information Commissioner’s Office</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Remove high-risk records</p>
            </list-item>
            <list-item>
              <p>Remove high-risk attribute</p>
            </list-item>
            <list-item>
              <p>Use average value of each group</p>
            </list-item>
            <list-item>
              <p>Use the week to replace the exact date</p>
            </list-item>
            <list-item>
              <p>Swap values of attributes with high risk</p>
            </list-item>
            <list-item>
              <p>Use partial postcode instead of full address</p>
            </list-item>
            <list-item>
              <p>Define a threshold and suppress the minority</p>
            </list-item>
            <list-item>
              <p>Probabilistically perturb categorical attributes</p>
            </list-item>
            <list-item>
              <p>Aggregate multiple variables into new classes</p>
            </list-item>
            <list-item>
              <p>Use city instead of postcode and house number, street</p>
            </list-item>
            <list-item>
              <p>Recode specific values into less-specific range</p>
            </list-item>
            <list-item>
              <p>Use secret key to link back (data owner only)</p>
            </list-item>
            <list-item>
              <p>Add noise to numerical data with low variations</p>
            </list-item>
          </list>
          <p>
            <bold>National Health Service</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Round off the totals</p>
            </list-item>
            <list-item>
              <p>Swap data attributes</p>
            </list-item>
            <list-item>
              <p>Use identifier ranges</p>
            </list-item>
            <list-item>
              <p>Mask part of the data</p>
            </list-item>
            <list-item>
              <p>Use age rather than date of birth</p>
            </list-item>
            <list-item>
              <p>Change the sort sequence</p>
            </list-item>
            <list-item>
              <p>Use the first part of the postcode</p>
            </list-item>
            <list-item>
              <p>Remove direct identifiers (National Health Service number)</p>
            </list-item>
            <list-item>
              <p>Risk assessment of indirect identifiers</p>
            </list-item>
            <list-item>
              <p>Provide only a sample of the population</p>
            </list-item>
            <list-item>
              <p>Provide range banding rather than exact data</p>
            </list-item>
            <list-item>
              <p>If aggregate totals less than 5, use pseudonyms</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Results Summary for RQs</title>
        <p>Here we present the results of the 5 defined RQs (<xref ref-type="boxed-text" rid="box3">Textbox 3</xref>) and, in the next section, discuss 3 open questions in real-world EHR data anonymization. The overall results of this SLM study are summarized in <xref rid="figure7" ref-type="fig">Figure 7</xref>.</p>
        <boxed-text id="box3" position="float">
          <title>Review questions.</title>
          <list list-type="bullet">
            <list-item>
              <p>Review question (RQ) 1: Do best practices exist for the anonymization of realistic electronic health record (EHR) data?</p>
              <list>
                <list-item>
                  <p>As the leading question of this systematic literature mapping study, we answer this question by exploring the answers to the other 4 RQs. It is theoretically feasible but practically challenging. On the basis of the answers to the remaining 4 questions, theoretical operations, privacy models, reidentification risk, and usability measurements are sufficient. Despite this, anonymization is practically difficult mainly because of 2 reasons: (1) the knowledge gap between health care professionals and privacy law (usually requiring huge collaborative efforts by clinical science, law, and data science), although we have summarized all lawful bases in the following subsection; and (2) automatic anonymization of EHR data is nontrivial and very case dependent.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>RQ 2: What are the most frequently applied data anonymization operations, and how can these operations be applied?</p>
              <list>
                <list-item>
                  <p>We investigated 7 categories of basic data anonymization operations in 16 articles, most of which are summarized in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. Apart from their fundamental uses, they can also be incorporated into the data anonymization process in both conventional and machine learning–based privacy models.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>RQ 3: What are the existing conventional and machine learning–based privacy models for measuring the level of anonymity? Are they practically useful in handling real-world health care data? Are there any new trends?</p>
              <list>
                <list-item>
                  <p>We presented 40 conventional (a taxonomy for relational data is summarized as part of <xref rid="figure7" ref-type="fig">Figure 7</xref>) privacy models and 32 machine learning–based privacy models from a total of 104 articles (summarized as part of <xref ref-type="table" rid="table1">Table 1</xref>). From this, we have observed that combinations of a deep learning architecture and one or more data anonymization operations have become a trend, particularly techniques based on (conditional-) generative adversarial networks. We have also realized that despite the increasing number of publications from the computer vision community, they rarely use real-world sensitive medical data. For the applicability of existing privacy models, we present an ablation study (<xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref> [<xref ref-type="bibr" rid="ref181">181</xref>,<xref ref-type="bibr" rid="ref300">300</xref>-<xref ref-type="bibr" rid="ref303">303</xref>]) using publicly accessible EHRs in the next subsection as part of the discussion.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>RQ 4: What metrics could be adopted to measure the reidentification risk and usability of the anonymized data?</p>
              <list>
                <list-item>
                  <p>We investigated 7 (from 4 articles) and 15 (from 19 articles) metrics to quantify the risk of reidentification and degree of usability of the anonymized data. Measuring reidentification risk requires a pair of raw and anonymized data records in which the original data are treated as an object of reference and compared with the anonymized data in terms of statistical difference. Such a difference may not sufficiently reveal the true risk of reidentification. To further investigate this issue, we combined the privacy models for discussing the trade-offs between these 2 privacy aspects. In contrast, more usability metrics were proposed because of the wider availability of performance indicators.</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>RQ 5: What are the off-the-shelf data anonymization tools based on conventional privacy models and machine learning?</p>
              <list>
                <list-item>
                  <p>We investigated and compared 19 data anonymization tools (reported in 36 articles), of which 15 are based on privacy models (compared in Tables <xref ref-type="table" rid="table5">5</xref> and <xref ref-type="table" rid="table6">6</xref>), whereas the remaining 5 (compared in <xref ref-type="table" rid="table7">Table 7</xref>) rely on privacy-preserving machine learning (with issues summarized in the next subsection). However, there does not exist any off-the-shelf data anonymization tool that truly supports the current legal frameworks such as the General Data Protection Regulation and Data Protection Act to dispel the doubts and concerns of data owners (we filled this gap as well).</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Privacy-Usability Trade-offs and Practical Feasibility</title>
        <p>The most important question to consider when data anonymization is required in the health care sector is the choice between the level of privacy and degree of usability. In <xref ref-type="table" rid="table2">Table 2</xref>, we listed parameter interval, which enables specific privacy model or models to be more practically configurable. The privacy level indicates the possible degree of privacy that can be achieved by each privacy model, where separate levels are provided for some variant models such as (α, <italic>k</italic>)-anonymity, stochastic <italic>t</italic>-closeness, and (ε, <italic>m</italic>)-anonymity. This problem can also be viewed as a trade-off between the risk of reidentification and data usability and can be quantified using specific methods [<xref ref-type="bibr" rid="ref304">304</xref>-<xref ref-type="bibr" rid="ref306">306</xref>].</p>
        <p>It should be noted that the privacy models, reidentification risk measurements, and data usability metrics reviewed in this study are relatively easy to understand, with equations provided along with adequate descriptions. However, these concepts are difficult to deploy in real-world data anonymization tools. Even given the intensive investigations summarized above, the utility of the anonymized data may not be easily measurable through a number of proposed metrics of reidentification risk and utility metrics.</p>
        <p>Given this discrepancy observed from the ablation study we conducted (<xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref>), it is worth considering the problem domain when quantifying the reidentification risk as well as the utility of the anonymized data, although we summarized the existing measures in the previous section. Overall, the trade-offs between reidentification risk and usability are practically feasible yet problem dependent.</p>
      </sec>
      <sec>
        <title>Issues of Privacy-Preserving Machine Learning</title>
        <p>SMPC and FHE share some disadvantages. They both use encryption methods that work over finite fields, and thus they cannot natively work with floating-point numbers. All practical implementations instead use a fixed-precision representation, but this adds computational overhead, and the level of precision used can affect the accuracy of the results.</p>
        <p>Another important issue is that of the trade-off between interpretability and privacy [<xref ref-type="bibr" rid="ref307">307</xref>] which, where privacy-preserving machine learning is concerned, is highly skewed toward privacy; encrypted models are, because of their very nature, entirely black-box models. This is not only an issue in the health care field, where the explainability of machine learning models is an important issue [<xref ref-type="bibr" rid="ref308">308</xref>], but also arguably in any machine learning application because of the GDPR’s “right to an explanation” [<xref ref-type="bibr" rid="ref309">309</xref>].</p>
        <p>Encrypted, trained models are also still vulnerable to reverse-engineering attacks (regardless of the encryption method used) [<xref ref-type="bibr" rid="ref278">278</xref>]; for example, a malicious user could use the outputs of a model to run a membership attack (ie, infer from the results of a model whether the input was from a member of the training set). Currently, the only known way to overcome this is to apply DP principles to the model, which adds yet another layer of complexity to the process. There are signs that existing libraries are starting to combat the possibility of such attacks by providing easy methods to apply DP to encrypted models; see, for example, the DP techniques available in PySyft in the <italic>SMPC Frameworks</italic> section above.</p>
        <p>It is also important to remember that, as noted previously, any type of encryption is regarded as a form of pseudonymization rather than anonymization because the encrypted data can be decrypted by anyone with access to the encryption key. However, we note that much of the current guidance on viewing encryption techniques as anonymization or pseudonymization is ambiguous; for example, ICO guidance [<xref ref-type="bibr" rid="ref290">290</xref>] suggests that encrypted data is classified as anonymized data so long as the party responsible for the encryption of the personal data is not also responsible for the processing of the encrypted data (because then the party processing the data would not be in possession of the encryption key and would therefore be unable to reverse the encryption). As such, it is important to carefully consider whether privacy-preserving machine learning techniques fully satisfy the requirements set out in law. For instance, tools that also include other privacy techniques, such as PySyft, may be more useful in situations where true anonymization is required.</p>
        <p>Overall, privacy-preserving machine learning is a promising area of research, although more work needs to be undertaken to ensure that such methods are ready for use in industrial applications; many of the tools currently available are only suitable for research rather than practical application. There also needs to be some consideration over which privacy-preserving methods best suit the needs of the application. SMPC currently offers a more viable approach than FHE because of its ability to run (and, more importantly, train) larger models, although the need to have multiple trusted parties may mean that it is seen as less secure than FHE. Meanwhile, FHE for privacy-preserving machine learning is still an emerging field, and it is encouraging to see research being undertaken by both the machine learning and cryptographic communities to improve the practicality of FHE methods by improving the running time of encrypted models and reducing the level of cryptographic knowledge needed to create efficient, encrypted models using FHE.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this SLM study, we presented a comprehensive overview of data anonymization research for health care by investigating both conventional and emerging privacy-preserving techniques. Given the results and the discussions regarding the 5 proposed RQs, privacy-preserving data anonymization for health care is a promising domain, although more studies are required to be conducted to ensure more reliable industrial applications.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Math notation system.</p>
        <media xlink:href="medinform_v9i10e29871_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 96 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Typical direct identifiers and quasi-identifiers in UK electronic health record data.</p>
        <media xlink:href="medinform_v9i10e29871_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 84 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Examples of fundamental data anonymization operations.</p>
        <media xlink:href="medinform_v9i10e29871_app3.pdf" xlink:title="PDF File  (Adobe PDF File), 68 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Conventional privacy models.</p>
        <media xlink:href="medinform_v9i10e29871_app4.pdf" xlink:title="PDF File  (Adobe PDF File), 321 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Usability metrics for privacy models.</p>
        <media xlink:href="medinform_v9i10e29871_app5.pdf" xlink:title="PDF File  (Adobe PDF File), 190 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Reidentification risk metrics for privacy models.</p>
        <media xlink:href="medinform_v9i10e29871_app6.pdf" xlink:title="PDF File  (Adobe PDF File), 139 KB"/>
      </supplementary-material>
      <supplementary-material id="app7">
        <label>Multimedia Appendix 7</label>
        <p>Ablation study for privacy-usability trade-offs and practical feasibility.</p>
        <media xlink:href="medinform_v9i10e29871_app7.pdf" xlink:title="PDF File  (Adobe PDF File), 195 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CP</term>
          <def>
            <p>compressive privacy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">DP</term>
          <def>
            <p>differential privacy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DPA</term>
          <def>
            <p>Data Protection Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">FHE</term>
          <def>
            <p>fully homomorphic encryption</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">GAN</term>
          <def>
            <p>generative adversarial network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">GP</term>
          <def>
            <p>general practitioner</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">HE</term>
          <def>
            <p>homomorphic encryption</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">HIPAA</term>
          <def>
            <p>Health Information Portability and Accountability Act</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">ICO</term>
          <def>
            <p>Information Commissioner’s Office</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">medGAN</term>
          <def>
            <p>medical generative adversarial network</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">PCA</term>
          <def>
            <p>principal component analysis</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">PRAM</term>
          <def>
            <p>postrandomization method</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">QI</term>
          <def>
            <p>quasi-identifier</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">RQ</term>
          <def>
            <p>review question</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">SECRETA</term>
          <def>
            <p>System for Evaluating and Comparing RElational and Transaction Anonymization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb19">SLM</term>
          <def>
            <p>systematic literature mapping</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb20">SLR</term>
          <def>
            <p>systematic literature review</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb21">SMPC</term>
          <def>
            <p>secure multiparty computation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb22">TF</term>
          <def>
            <p>TensorFlow</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb23">μ-ANT</term>
          <def>
            <p>microaggregation-based anonymization tool</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was sponsored by the UK Research and Innovation fund (project 312409) and Cievert Ltd.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duggal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Brindle</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Bagenal</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digital healthcare: regulating the revolution</article-title>
          <source>Br Med J</source>
          <year>2018</year>
          <month>01</month>
          <day>15</day>
          <volume>360</volume>
          <fpage>k6</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.k6</pub-id>
          <pub-id pub-id-type="medline">29335296</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Xue</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>LI</surname>
              <given-names>L-J</given-names>
            </name>
            <name name-style="western">
              <surname>Fei-Fei</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Thoracic disease identification and localization with limited supervision</article-title>
          <source>Proceedings of the 2018 IEEE/CVF Conference on Computer Vision and Pattern Recognition</source>
          <year>2018</year>
          <conf-name>2018 IEEE/CVF Conference on Computer Vision and Pattern Recognition</conf-name>
          <conf-date>Jun 18-23, 2018</conf-date>
          <conf-loc>Salt Lake City, UT, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr.2018.00865</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Zuluaga</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Pratt</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Aertsen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Doel</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>David</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Deprest</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ourselin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vercauteren</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>DeepIGeoS: a deep interactive geodesic framework for medical image segmentation</article-title>
          <source>IEEE Trans Pattern Anal Mach Intell</source>
          <year>2019</year>
          <month>7</month>
          <day>1</day>
          <volume>41</volume>
          <issue>7</issue>
          <fpage>1559</fpage>
          <lpage>72</lpage>
          <pub-id pub-id-type="doi">10.1109/tpami.2018.2840695</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zuo</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Qu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Gaze-informed egocentric action recognition for memory aid systems</article-title>
          <source>IEEE Access</source>
          <year>2018</year>
          <month>3</month>
          <day>1</day>
          <volume>6</volume>
          <fpage>12894</fpage>
          <lpage>904</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2018.2808486</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Senior</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jumper</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kirkpatrick</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sifre</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Qin</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Žídek</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Bridgland</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Penedones</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Simonyan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Crossan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kohli</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>DT</given-names>
            </name>
            <name name-style="western">
              <surname>Silver</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kavukcuoglu</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hassabis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Improved protein structure prediction using potentials from deep learning</article-title>
          <source>Nature</source>
          <year>2020</year>
          <month>01</month>
          <volume>577</volume>
          <issue>7792</issue>
          <fpage>706</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1038/s41586-019-1923-7</pub-id>
          <pub-id pub-id-type="medline">31942072</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-019-1923-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Veličković</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Karazija</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lane</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bhattacharya</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liberis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Liò</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chieh</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bellahsen</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Cross-modal recurrent models for weight objective prediction from multimodal time-series data</article-title>
          <source>Proceedings of the PervasiveHealth '18: 12th EAI International Conference on Pervasive Computing Technologies for Healthcare</source>
          <year>2018</year>
          <conf-name>PervasiveHealth '18:12th EAI International Conference on Pervasive Computing Technologies for Healthcare</conf-name>
          <conf-date>May 21-24, 2018</conf-date>
          <conf-loc>New York</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3240925.3240937</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhelezniak</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Savkov</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Moramarco</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Flann</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hammerla</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Don't settle for average, go for the max: fuzzy sets and max-pooled word vectors</article-title>
          <source>arXiv</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1904.13264">https://arxiv.org/abs/1904.13264</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>SY</given-names>
            </name>
            <collab>Omkar</collab>
            <name name-style="western">
              <surname>Yoshida</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Inda</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Xavier</surname>
              <given-names>CX</given-names>
            </name>
            <name name-style="western">
              <surname>Mu</surname>
              <given-names>WC</given-names>
            </name>
            <name name-style="western">
              <surname>Meng</surname>
              <given-names>YS</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Microstrip line-based glucose sensor for noninvasive continuous monitoring using the main field for sensing and multivariable crosschecking</article-title>
          <source>IEEE Sensors J</source>
          <year>2019</year>
          <month>1</month>
          <day>15</day>
          <volume>19</volume>
          <issue>2</issue>
          <fpage>535</fpage>
          <lpage>47</lpage>
          <pub-id pub-id-type="doi">10.1109/jsen.2018.2877691</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaisti</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tadi</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Lahdenoja</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Hurnanen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Saraste</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pankaala</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Koivisto</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Stand-alone heartbeat detection in multidimensional mechanocardiograms</article-title>
          <source>IEEE Sensors J</source>
          <year>2019</year>
          <month>1</month>
          <day>1</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>234</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1109/jsen.2018.2874706</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iacobucci</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Row over Babylon's chatbot shows lack of regulation</article-title>
          <source>Br Med J</source>
          <year>2020</year>
          <month>02</month>
          <day>28</day>
          <volume>368</volume>
          <fpage>m815</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.m815</pub-id>
          <pub-id pub-id-type="medline">32111647</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Spencer</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Noyes</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Biederman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Telemedicine in the management of ADHD: literature review of telemedicine in ADHD</article-title>
          <source>J Atten Disord</source>
          <year>2020</year>
          <month>01</month>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>3</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1177/1087054719859081</pub-id>
          <pub-id pub-id-type="medline">31257978</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Allen</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sudlow</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Downey</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Peakman</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Danesh</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Elliott</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gallacher</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Matthews</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Pell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sprosen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Collins</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>UK Biobank: current status and what it means for epidemiology</article-title>
          <source>Health Policy Technol</source>
          <year>2012</year>
          <month>9</month>
          <volume>1</volume>
          <issue>3</issue>
          <fpage>123</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1016/j.hlpt.2012.07.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Elliott</surname>
              <given-names>LT</given-names>
            </name>
            <name name-style="western">
              <surname>Sharp</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Alfaro-Almagro</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Douaud</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Marchini</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>Genome-wide association studies of brain imaging phenotypes in UK Biobank</article-title>
          <source>Nature</source>
          <year>2018</year>
          <month>10</month>
          <volume>562</volume>
          <issue>7726</issue>
          <fpage>210</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30305740"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41586-018-0571-7</pub-id>
          <pub-id pub-id-type="medline">30305740</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-018-0571-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6786974</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Turnbull</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Murugaesu</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Pretty</surname>
              <given-names>FB</given-names>
            </name>
            <name name-style="western">
              <surname>Halai</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Baple</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Craig</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hamblin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Henderson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patch</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>O'Neill</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Devereau</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Sosinsky</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>McDonagh</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Sultana</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mueller</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Smedley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Toms</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dinh</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Fowler</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bale</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hubbard</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Rendon</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hill</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Caulfield</surname>
              <given-names>MJ</given-names>
            </name>
            <collab>100 000 Genomes Project</collab>
          </person-group>
          <article-title>The 100 000 Genomes Project: bringing whole genome sequencing to the NHS</article-title>
          <source>Br Med J</source>
          <year>2018</year>
          <month>04</month>
          <day>24</day>
          <volume>361</volume>
          <fpage>k1687</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.k1687</pub-id>
          <pub-id pub-id-type="medline">29691228</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Heath</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Boost for sustainable healthcare</article-title>
          <source>Br Med J</source>
          <year>2020</year>
          <month>01</month>
          <day>28</day>
          <volume>368</volume>
          <fpage>m284</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.m284</pub-id>
          <pub-id pub-id-type="medline">31992564</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Agrawal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Prabakaran</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Big data in digital healthcare: lessons learnt and recommendations for general practice</article-title>
          <source>Heredity (Edinb)</source>
          <year>2020</year>
          <month>04</month>
          <volume>124</volume>
          <issue>4</issue>
          <fpage>525</fpage>
          <lpage>34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32139886"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41437-020-0303-2</pub-id>
          <pub-id pub-id-type="medline">32139886</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41437-020-0303-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC7080757</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moberly</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Should we be worried about the NHS selling patient data?</article-title>
          <source>Br Med J</source>
          <year>2020</year>
          <month>01</month>
          <day>15</day>
          <volume>368</volume>
          <fpage>m113</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.m113</pub-id>
          <pub-id pub-id-type="medline">31941645</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Human Rights Act 1998</article-title>
          <source>Legislation - UK Public General Acts</source>
          <year>1998</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.legislation.gov.uk/ukpga/1998/42/schedule/1">https://www.legislation.gov.uk/ukpga/1998/42/schedule/1</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Vineet</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Pittaluga</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sinha</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cossairt</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Bing</surname>
              <given-names>KS</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving action recognition using coded aperture videos</article-title>
          <source>Proceedings of the 2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition Workshops (CVPRW)</source>
          <year>2019</year>
          <conf-name>2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition Workshops (CVPRW)</conf-name>
          <conf-date>Jun 16-17, 2019</conf-date>
          <conf-loc>Long Beach, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvprw.2019.00007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Speciale</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Schonberger</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sinha</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Pollefeys</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Privacy preserving image queries for camera localization</article-title>
          <source>Proceedings of the 2019 IEEE/CVF International Conference on Computer Vision (ICCV)</source>
          <year>2019</year>
          <conf-name>2019 IEEE/CVF International Conference on Computer Vision (ICCV)</conf-name>
          <conf-date>Oct 27- Nov 2, 2019</conf-date>
          <conf-loc>Seoul, Korea (South)</conf-loc>
          <pub-id pub-id-type="doi">10.1109/iccv.2019.00157</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Khodak</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Caldas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Talwalkar</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Differentially private meta-learning</article-title>
          <source>arXiv</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1909.05830">https://arxiv.org/abs/1909.05830</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Recommendation of the council concerning guidelines governing the protection of privacy and transborder flows of personal data</article-title>
          <source>European Union Agency for Cybersecurity</source>
          <year>1980</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.enisa.europa.eu/topics/threat-risk-management/risk-management/current-risk/laws-regulation/data-protection-privacy/oecd-recommendation-of-the-council">https://www.enisa.europa.eu/topics/threat-risk-management/risk-management/current-risk/laws-regulation/data-protection-privacy/oecd-recommendation-of-the-council</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (Text with EEA relevance)</article-title>
          <source>Legislation - Regulations Originating from the EU</source>
          <year>2016</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.legislation.gov.uk/eur/2016/679/contents#">https://www.legislation.gov.uk/eur/2016/679/contents#</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>The Lancet</collab>
          </person-group>
          <article-title>Artificial intelligence in health care: within touching distance</article-title>
          <source>Lancet</source>
          <year>2017</year>
          <month>12</month>
          <day>23</day>
          <volume>390</volume>
          <issue>10114</issue>
          <fpage>2739</fpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(17)31540-4</pub-id>
          <pub-id pub-id-type="medline">29303711</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(17)31540-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iacobucci</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Patient data were shared with Google on an "inappropriate legal basis," says NHS data guardian</article-title>
          <source>Br Med J</source>
          <year>2017</year>
          <month>05</month>
          <day>18</day>
          <volume>357</volume>
          <fpage>j2439</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.j2439</pub-id>
          <pub-id pub-id-type="medline">28522583</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>The Lancet Technology: November, 2014. Trouble on the radar</article-title>
          <source>Lancet</source>
          <year>2014</year>
          <month>11</month>
          <day>29</day>
          <volume>384</volume>
          <issue>9958</issue>
          <fpage>1917</fpage>
          <pub-id pub-id-type="doi">10.1016/s0140-6736(14)62267-4</pub-id>
          <pub-id pub-id-type="medline">25478615</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(14)62267-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>The DeepMind debacle demands dialogue on data</article-title>
          <source>Nature</source>
          <year>2017</year>
          <month>07</month>
          <day>19</day>
          <volume>547</volume>
          <issue>7663</issue>
          <fpage>259</fpage>
          <pub-id pub-id-type="doi">10.1038/547259a</pub-id>
          <pub-id pub-id-type="medline">28726841</pub-id>
          <pub-id pub-id-type="pii">547259a</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Appelbaum</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kronish</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Busacca</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Davidson</surname>
              <given-names>KW</given-names>
            </name>
            <name name-style="western">
              <surname>Bigger</surname>
              <given-names>JT</given-names>
            </name>
          </person-group>
          <article-title>Using EHRs to integrate research with patient care: promises and challenges</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2012</year>
          <volume>19</volume>
          <issue>5</issue>
          <fpage>684</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22542813"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2012-000878</pub-id>
          <pub-id pub-id-type="medline">22542813</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2012-000878</pub-id>
          <pub-id pub-id-type="pmcid">PMC3422845</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Samaritans radar app</article-title>
          <source>Nurs Stand</source>
          <year>2014</year>
          <month>12</month>
          <day>15</day>
          <volume>29</volume>
          <issue>15</issue>
          <fpage>33</fpage>
          <pub-id pub-id-type="doi">10.7748/ns.29.15.33.s40</pub-id>
          <pub-id pub-id-type="medline">25492781</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>HM</given-names>
            </name>
          </person-group>
          <article-title>Ethical barriers to artificial intelligence in the national health service, United Kingdom of Great Britain and Northern Ireland</article-title>
          <source>Bull World Health Organ</source>
          <year>2020</year>
          <month>04</month>
          <day>01</day>
          <volume>98</volume>
          <issue>4</issue>
          <fpage>293</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32284657"/>
          </comment>
          <pub-id pub-id-type="doi">10.2471/BLT.19.237230</pub-id>
          <pub-id pub-id-type="medline">32284657</pub-id>
          <pub-id pub-id-type="pii">BLT.19.237230</pub-id>
          <pub-id pub-id-type="pmcid">PMC7133482</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hawkes</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>NHS data sharing deal with Google prompts concern</article-title>
          <source>Br Med J</source>
          <year>2016</year>
          <month>05</month>
          <day>05</day>
          <volume>353</volume>
          <fpage>i2573</fpage>
          <pub-id pub-id-type="doi">10.1136/bmj.i2573</pub-id>
          <pub-id pub-id-type="medline">27150956</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>Royal Free - Google DeepMind trial failed to comply with data protection law</article-title>
          <source>Information Commissioner's Office</source>
          <year>2017</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/about-the-ico/news-and-events/news-and-blogs/2017/07/royal-free-google-deepmind-trial-failed-to-comply-with-data-protection-law/">https://ico.org.uk/about-the-ico/news-and-events/news-and-blogs/2017/07/royal-free-google-deepmind-trial-failed-to-comply-with-data-protection-law/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chevrier</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Foufi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Gaudet-Blavignac</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lovis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Use and understanding of anonymization and de-identification in the biomedical literature: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>05</month>
          <day>31</day>
          <volume>21</volume>
          <issue>5</issue>
          <fpage>e13484</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/5/e13484/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13484</pub-id>
          <pub-id pub-id-type="medline">31152528</pub-id>
          <pub-id pub-id-type="pii">v21i5e13484</pub-id>
          <pub-id pub-id-type="pmcid">PMC6658290</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Elger</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Iavindrasana</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lo Iacono</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Roduit</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Summers</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Strategies for health data exchange for secondary, cross-institutional clinical research</article-title>
          <source>Comput Methods Programs Biomed</source>
          <year>2010</year>
          <month>09</month>
          <volume>99</volume>
          <issue>3</issue>
          <fpage>230</fpage>
          <lpage>51</lpage>
          <pub-id pub-id-type="doi">10.1016/j.cmpb.2009.12.001</pub-id>
          <pub-id pub-id-type="medline">20089327</pub-id>
          <pub-id pub-id-type="pii">S0169-2607(09)00304-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Annas</surname>
              <given-names>GJ</given-names>
            </name>
          </person-group>
          <article-title>HIPAA regulations - a new era of medical-record privacy?</article-title>
          <source>N Engl J Med</source>
          <year>2003</year>
          <month>04</month>
          <day>10</day>
          <volume>348</volume>
          <issue>15</issue>
          <fpage>1486</fpage>
          <lpage>90</lpage>
          <pub-id pub-id-type="doi">10.1056/NEJMlim035027</pub-id>
          <pub-id pub-id-type="medline">12686707</pub-id>
          <pub-id pub-id-type="pii">348/15/1486</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Badawi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mun</surname>
              <given-names>CF</given-names>
            </name>
            <name name-style="western">
              <surname>Jie</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>BH</given-names>
            </name>
            <name name-style="western">
              <surname>Nan</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Khin</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Chandrasekhar</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Towards the AlexNet moment for homomorphic encryption: HCNN, the first homomorphic CNN on encrypted data with GPUs</article-title>
          <source>arXiv</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1811.00778">https://arxiv.org/abs/1811.00778</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <article-title>Statement on the second meeting of the International Health Regulations (2005) Emergency Committee regarding the outbreak of novel coronavirus (2019-nCoV)</article-title>
          <source>World Health Organization</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/news/item/30-01-2020-statement-on-the-second-meeting-of-the-international-health-regulations-(2005)-emergency-committee-regarding-the-outbreak-of-novel-coronavirus-(2019-ncov)">https://tinyurl.com/5bcfwe8a</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Gardner</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>An interactive web-based dashboard to track COVID-19 in real time</article-title>
          <source>Lancet Infect Dis</source>
          <year>2020</year>
          <month>05</month>
          <volume>20</volume>
          <issue>5</issue>
          <fpage>533</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32087114"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S1473-3099(20)30120-1</pub-id>
          <pub-id pub-id-type="medline">32087114</pub-id>
          <pub-id pub-id-type="pii">S1473-3099(20)30120-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7159018</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>COVID-19 dashboard by the Center for  Systems Science and Engineering (CSSE)</article-title>
          <source>Arcgis</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6">https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <article-title>UK summary : The official UK government website for data and insights on coronavirus (COVID-19)</article-title>
          <source>GOV.UK</source>
          <year>2021</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://coronavirus.data.gov.uk/">https://coronavirus.data.gov.uk/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Keesara</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jonas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schulman</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Covid-19 and health care's digital revolution</article-title>
          <source>N Engl J Med</source>
          <year>2020</year>
          <month>06</month>
          <day>04</day>
          <volume>382</volume>
          <issue>23</issue>
          <fpage>e82</fpage>
          <pub-id pub-id-type="doi">10.1056/NEJMp2005835</pub-id>
          <pub-id pub-id-type="medline">32240581</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Flaxman</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gandy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Unwin</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mellan</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Coupland</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Whittaker</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Berah</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Eaton</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Monod</surname>
              <given-names>M</given-names>
            </name>
            <collab>Imperial College COVID-19 Response Team</collab>
            <name name-style="western">
              <surname>Ghani</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Donnelly</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vollmer</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Ferguson</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Okell</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Bhatt</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Estimating the effects of non-pharmaceutical interventions on COVID-19 in Europe</article-title>
          <source>Nature</source>
          <year>2020</year>
          <month>08</month>
          <volume>584</volume>
          <issue>7820</issue>
          <fpage>257</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.1038/s41586-020-2405-7</pub-id>
          <pub-id pub-id-type="medline">32512579</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-020-2405-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Nowcasting and forecasting the potential domestic and international spread of the 2019-nCoV outbreak originating in Wuhan, China: a modelling study</article-title>
          <source>Lancet</source>
          <year>2020</year>
          <month>02</month>
          <day>29</day>
          <volume>395</volume>
          <issue>10225</issue>
          <fpage>689</fpage>
          <lpage>97</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32014114"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(20)30260-9</pub-id>
          <pub-id pub-id-type="medline">32014114</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(20)30260-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC7159271</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Crowdsourcing data to mitigate epidemics</article-title>
          <source>Lancet Digit Health</source>
          <year>2020</year>
          <month>04</month>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>156</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(20)30055-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(20)30055-8</pub-id>
          <pub-id pub-id-type="medline">32296776</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(20)30055-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC7158995</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Viboud</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Early epidemiological analysis of the coronavirus disease 2019 outbreak based on crowdsourced data: a population-level observational study</article-title>
          <source>Lancet Digit Health</source>
          <year>2020</year>
          <month>04</month>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>201</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(20)30026-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(20)30026-1</pub-id>
          <pub-id pub-id-type="medline">32309796</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(20)30026-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7158945</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ferretti</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wymant</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kendall</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Nurtay</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Abeler-Dörner</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Parker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bonsall</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Fraser</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Quantifying SARS-CoV-2 transmission suggests epidemic control with digital contact tracing</article-title>
          <source>Science</source>
          <year>2020</year>
          <month>05</month>
          <day>08</day>
          <volume>368</volume>
          <issue>6491</issue>
          <fpage>eabb6936</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32234805"/>
          </comment>
          <pub-id pub-id-type="doi">10.1126/science.abb6936</pub-id>
          <pub-id pub-id-type="medline">32234805</pub-id>
          <pub-id pub-id-type="pii">science.abb6936</pub-id>
          <pub-id pub-id-type="pmcid">PMC7164555</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <article-title>Coronavirus: UK considers virus-tracing app to ease lockdown</article-title>
          <source>BBC News</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bbc.co.uk/news/technology-52095331">https://www.bbc.co.uk/news/technology-52095331</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Beck</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Strufe</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Covid notions: towards formal definitions - and documented understanding - of privacy goals and claimed protection in proximity-tracing services</article-title>
          <source>Online Soc Netw Media</source>
          <year>2021</year>
          <month>03</month>
          <volume>22</volume>
          <fpage>100125</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/33681543"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.osnem.2021.100125</pub-id>
          <pub-id pub-id-type="medline">33681543</pub-id>
          <pub-id pub-id-type="pii">S2468-6964(21)00009-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC7910700</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <article-title>Coronavirus: Moscow rolls out patient-tracking app</article-title>
          <source>BBC News</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bbc.co.uk/news/technology-52121264">https://www.bbc.co.uk/news/technology-52121264</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>The Lancet Digital Health</collab>
          </person-group>
          <article-title>Reflecting on a future ready for digital health</article-title>
          <source>Lancet Digit Health</source>
          <year>2020</year>
          <month>05</month>
          <volume>2</volume>
          <issue>5</issue>
          <fpage>e209</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(20)30087-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(20)30087-X</pub-id>
          <pub-id pub-id-type="medline">32373784</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(20)30087-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC7195348</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nay</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Can a virus undermine human rights?</article-title>
          <source>Lancet Public Health</source>
          <year>2020</year>
          <month>05</month>
          <volume>5</volume>
          <issue>5</issue>
          <fpage>238</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2468-2667(20)30092-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2468-2667(20)30092-X</pub-id>
          <pub-id pub-id-type="medline">32325013</pub-id>
          <pub-id pub-id-type="pii">S2468-2667(20)30092-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC7170793</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Bärnighausen</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 control in China during mass population movements at New Year</article-title>
          <source>Lancet</source>
          <year>2020</year>
          <month>03</month>
          <day>07</day>
          <volume>395</volume>
          <issue>10226</issue>
          <fpage>764</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/32105609"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(20)30421-9</pub-id>
          <pub-id pub-id-type="medline">32105609</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(20)30421-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC7159085</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Ran</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Musa</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Lou</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>MH</given-names>
            </name>
          </person-group>
          <article-title>Preliminary estimation of the basic reproduction number of novel coronavirus (2019-nCoV) in China, from 2019 to 2020: a data-driven analysis in the early phase of the outbreak</article-title>
          <source>Int J Infect Dis</source>
          <year>2020</year>
          <month>03</month>
          <volume>92</volume>
          <fpage>214</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1201-9712(20)30053-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijid.2020.01.050</pub-id>
          <pub-id pub-id-type="medline">32007643</pub-id>
          <pub-id pub-id-type="pii">S1201-9712(20)30053-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC7110798</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <article-title>NHS COVID-19 app support</article-title>
          <source>NHS</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.covid19.nhs.uk/">https://www.covid19.nhs.uk/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beigi</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A survey on privacy in social media: identification, mitigation, and applications</article-title>
          <source>ACM/IMS Trans Data Sci</source>
          <year>2020</year>
          <month>02</month>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1145/3343038</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fletcher</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>MZ</given-names>
            </name>
          </person-group>
          <article-title>Decision tree classification with differential privacy</article-title>
          <source>ACM Comput Surv</source>
          <year>2019</year>
          <month>09</month>
          <volume>52</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1145/3337064</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fung</surname>
              <given-names>BC</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>PS</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving data publishing: a survey of recent developments</article-title>
          <source>ACM Comput Surv</source>
          <year>2010</year>
          <month>06</month>
          <volume>42</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>53</lpage>
          <pub-id pub-id-type="doi">10.1145/1749603.1749605</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Eckhoff</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Technical privacy metrics</article-title>
          <source>ACM Comput Surv</source>
          <year>2018</year>
          <month>7</month>
          <volume>51</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1145/3168389</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <article-title>GDPR personal data</article-title>
          <source>Intersoft Consulting</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/issues/personal-data/">https://gdpr-info.eu/issues/personal-data/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="web">
          <article-title>Art. 9 GDPR Processing of special categories of personal data</article-title>
          <source>Intersoft Consulting</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/art-9-gdpr/">https://gdpr-info.eu/art-9-gdpr/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Emam</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <source>Guide to the De-Identification of Personal Health Information</source>
          <year>2013</year>
          <publisher-loc>Boca Raton, Fl</publisher-loc>
          <publisher-name>Auerbach Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zigomitros</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Casino</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Solanas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Patsakis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A survey on privacy properties for data publishing of relational data</article-title>
          <source>IEEE Access</source>
          <year>2020</year>
          <month>3</month>
          <day>11</day>
          <volume>8</volume>
          <fpage>51071</fpage>
          <lpage>99</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2020.2980235</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>A new approach for anonymizing relational and transaction data</article-title>
          <source>Proceedings of the 2nd International Conference on Healthcare Science and Engineering. ICHSE 2018</source>
          <year>2019</year>
          <publisher-loc>Singapore</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amiri</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Yazdani</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Shakery</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Bottom-up sequential anonymization in the presence of adversary knowledge</article-title>
          <source>Inf Sci: Int J</source>
          <year>2018</year>
          <month>06</month>
          <volume>450</volume>
          <fpage>316</fpage>
          <lpage>35</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.ins.2018.03.027"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ins.2018.03.027</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Balancing trajectory privacy and data utility using a personalized anonymization model</article-title>
          <source>J Netw  Comput Appl</source>
          <year>2014</year>
          <month>2</month>
          <volume>38</volume>
          <fpage>125</fpage>
          <lpage>34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.jnca.2013.03.010"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jnca.2013.03.010</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mortazavi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Erfani</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>GRAM: an efficient (k, l) graph anonymization method</article-title>
          <source>Expert Syst Appl</source>
          <year>2020</year>
          <month>09</month>
          <day>1</day>
          <volume>153</volume>
          <fpage>113454</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.eswa.2020.113454"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.eswa.2020.113454</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ninggal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abawajy</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Utility-aware social network graph anonymization</article-title>
          <source>J Netw Comput Appl</source>
          <year>2015</year>
          <month>10</month>
          <volume>56</volume>
          <fpage>137</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.jnca.2015.05.013"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jnca.2015.05.013</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stallings</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <source>Information Privacy Engineering and Privacy by Design: Understanding Privacy Threats, Technology, and Regulations Based on Standards and Best Practices</source>
          <year>2019</year>
          <publisher-loc>Boston, MA</publisher-loc>
          <publisher-name>Addison-Wesley Professional</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hrynaszkiewicz</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Norton</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Vickers</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Altman</surname>
              <given-names>DG</given-names>
            </name>
          </person-group>
          <article-title>Preparing raw clinical data for publication: guidance for journal editors, authors, and peer reviewers</article-title>
          <source>Br Med J</source>
          <year>2010</year>
          <month>01</month>
          <day>28</day>
          <volume>340</volume>
          <fpage>c181</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/20110312"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.c181</pub-id>
          <pub-id pub-id-type="medline">20110312</pub-id>
          <pub-id pub-id-type="pmcid">PMC2813427</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tucker</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Branson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dilleen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hollis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Loughlin</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Nixon</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Protecting patient privacy when sharing patient-level data from clinical trials</article-title>
          <source>BMC Med Res Methodol</source>
          <year>2016</year>
          <month>07</month>
          <day>08</day>
          <volume>16 Suppl 1</volume>
          <issue>Suppl 1</issue>
          <fpage>77</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/s12874-016-0169-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12874-016-0169-4</pub-id>
          <pub-id pub-id-type="medline">27410040</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12874-016-0169-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC4943495</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="web">
          <article-title>Recommendation CM/Rec(2019)2 of the Committee of Ministers to member States on the protection of health-related data</article-title>
          <source>Council of Europe</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.apda.ad/sites/default/files/2019-03/CM_Rec%282019%292E_EN.pdf">https://www.apda.ad/sites/default/files/2019-03/CM_Rec%282019%292E_EN.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="web">
          <article-title>HIPAA PHI: definition of PHI and list of 18 identifiers</article-title>
          <source>UC Berkeley Human Research Protection Program</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cphs.berkeley.edu/hipaa/hipaa18.html">https://cphs.berkeley.edu/hipaa/hipaa18.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="web">
          <article-title>Information sharing policy</article-title>
          <source>NHS</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.england.nhs.uk/wp-content/uploads/2019/10/information-sharing-policy-v4.1.pdf">https://www.england.nhs.uk/wp-content/uploads/2019/10/information-sharing-policy-v4.1.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="web">
          <article-title>Pseudonymisation policy</article-title>
          <source>Kernow NHS Foundation Trust</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://policies.kernowccg.nhs.uk/DocumentsLibrary/KernowCCG/ManagingInformation/Policies/PseudonymisationPolicy.pdf">http://policies.kernowccg.nhs.uk/DocumentsLibrary/KernowCCG/ManagingInformation/Policies/PseudonymisationPolicy.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="web">
          <article-title>Anonymisation of data (Pseudonymisation) policy and procedure</article-title>
          <source>Solent NHS Foundation Trust</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.solent.nhs.uk/media/1262/pseudonymisation-policy.pdf">https://www.solent.nhs.uk/media/1262/pseudonymisation-policy.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="web">
          <article-title>Recital 26 not applicable to anonymous data</article-title>
          <source>Intersoft Consulting</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/recitals/no-26/">https://gdpr-info.eu/recitals/no-26/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="web">
          <article-title>What is personal data?</article-title>
          <source>Information Commissioner's Office</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/what-is-personal-data/">https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/what-is-personal-data/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Templ</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Anonymization and re-identification risk of personal data</article-title>
          <source>Proceedings of the Gästekolloquium Psychologisches Institut Universität Zürich</source>
          <year>2020</year>
          <conf-name>Gästekolloquium Psychologisches Institut Universität Zürich</conf-name>
          <conf-date>Nov 9, 2020</conf-date>
          <conf-loc>Zurich</conf-loc>
          <pub-id pub-id-type="doi">10.4414/saez.2019.17441</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bandara</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Bandara</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Fernando</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of re-identification risks in data anonymization techniques based on population uniqueness</article-title>
          <source>Proceedings of the 2020 5th International Conference on Information Technology Research (ICITR)</source>
          <year>2020</year>
          <conf-name>2020 5th International Conference on Information Technology Research (ICITR)</conf-name>
          <conf-date>Dec 2-4, 2020</conf-date>
          <conf-loc>Moratuwa, Sri Lanka</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icitr51448.2020.9310884</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garousi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Bauer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Felderer</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>NLP-assisted software testing: a systematic mapping of the literature</article-title>
          <source>Inf Softw Technol</source>
          <year>2020</year>
          <month>10</month>
          <volume>126</volume>
          <fpage>106321</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.infsof.2020.106321"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.infsof.2020.106321</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Feldt</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mujtaba</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mattsson</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Systematic mapping studies in software engineering</article-title>
          <source>Proceedings of the 12th International Conference on Evaluation and Assessment in Software Engineering (EASE)</source>
          <year>2008</year>
          <conf-name>12th International Conference on Evaluation and Assessment in Software Engineering (EASE)</conf-name>
          <conf-date>Jun 26-17, 2008</conf-date>
          <conf-loc>Italy</conf-loc>
          <fpage>68</fpage>
          <lpage>77</lpage>
          <pub-id pub-id-type="doi">10.5555/2227115.2227123</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Witti</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Konstantas</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>IOT and security-privacy concerns: a systematic mapping study</article-title>
          <source>Int J Netw Secur Appl</source>
          <year>2018</year>
          <month>11</month>
          <day>21</day>
          <volume>10</volume>
          <issue>6</issue>
          <fpage>3319816</fpage>
          <pub-id pub-id-type="doi">10.2139/ssrn.3319816</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Budgen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brereton</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Drummond</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>What support do systematic reviews provide for evidence-informed teaching about software engineering practice?</article-title>
          <source>e-Infor Softw Eng J</source>
          <year>2020</year>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>7</fpage>
          <lpage>60</lpage>
          <pub-id pub-id-type="doi">10.37190/e-inf200101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Vakkalanka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kuzniarz</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Guidelines for conducting systematic mapping studies in software engineering: an update</article-title>
          <source>Inf Softw Technol</source>
          <year>2015</year>
          <month>08</month>
          <volume>64</volume>
          <fpage>1</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1016/j.infsof.2015.03.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="web">
          <article-title>Cochrane database of systematic reviews</article-title>
          <source>Cochrane Library</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cochranelibrary.com/cdsr/about-cdsr">https://www.cochranelibrary.com/cdsr/about-cdsr</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="web">
          <article-title>Centre for reviews and dissemination</article-title>
          <source>University of York</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.york.ac.uk/crd/">https://www.york.ac.uk/crd/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="web">
          <article-title>Health technology assessment</article-title>
          <source>National Institute for Health Research</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nihr.ac.uk/explore-nihr/funding-programmes/health-technology-assessment.htm">https://www.nihr.ac.uk/explore-nihr/funding-programmes/health-technology-assessment.htm</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wohlin</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Guidelines for snowballing in systematic literature studies and a replication in software engineering</article-title>
          <source>Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering</source>
          <year>2014</year>
          <conf-name>EASE '14: Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering</conf-name>
          <conf-date>May 13-14, 2014</conf-date>
          <conf-loc>London England United Kingdom</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2601248.2601268</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Paez</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Gray literature: an important resource in systematic reviews</article-title>
          <source>J Evid Based Med</source>
          <year>2017</year>
          <month>08</month>
          <volume>10</volume>
          <issue>3</issue>
          <fpage>233</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.1111/jebm.12266</pub-id>
          <pub-id pub-id-type="medline">28857505</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hopewell</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Egger</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Grey literature in meta-analyses of randomized trials of health care interventions</article-title>
          <source>Cochrane Database Syst Rev</source>
          <year>2007</year>
          <month>04</month>
          <day>18</day>
          <issue>2</issue>
          <fpage>MR000010</fpage>
          <pub-id pub-id-type="doi">10.1002/14651858.MR000010.pub3</pub-id>
          <pub-id pub-id-type="medline">17443631</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saleh</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Ratajeski</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Bertolet</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Grey literature searching for health sciences systematic reviews: a prospective study of time spent and resources utilized</article-title>
          <source>Evid Based Libr Inf Pract</source>
          <year>2014</year>
          <volume>9</volume>
          <issue>3</issue>
          <fpage>28</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25914722"/>
          </comment>
          <pub-id pub-id-type="doi">10.18438/b8dw3k</pub-id>
          <pub-id pub-id-type="medline">25914722</pub-id>
          <pub-id pub-id-type="pmcid">PMC4405801</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nimmer</surname>
              <given-names>RT</given-names>
            </name>
            <name name-style="western">
              <surname>Krauthaus</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Information as a commodity: new imperatives of commercial law</article-title>
          <source>Law Contemp Probs</source>
          <year>1992</year>
          <volume>55</volume>
          <issue>3</issue>
          <fpage>103</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.2307/1191865</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Smart</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Huff</surname>
              <given-names>AS</given-names>
            </name>
          </person-group>
          <article-title>Shades of grey: guidelines for working with the grey literature in systematic reviews for management and organizational studies</article-title>
          <source>Int J Manag Rev</source>
          <year>2016</year>
          <month>04</month>
          <day>19</day>
          <volume>19</volume>
          <issue>4</issue>
          <fpage>432</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.1111/ijmr.12102</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Secure social recommendation based on secret sharing</article-title>
          <source>Proceedings of the 24th European Conference on Artificial Intelligence - ECAI 2020</source>
          <year>2020</year>
          <conf-name>24th European Conference on Artificial Intelligence - ECAI 2020</conf-name>
          <conf-date>Aug 31- Sep 4, 2020</conf-date>
          <conf-loc>Spain</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ecai2020.eu/papers/609_paper.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Biswal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Malin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Duke</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Generating multi-label discrete patient records using generative adversarial networks</article-title>
          <source>Proceedings of the 2nd Machine Learning for Healthcare Conference</source>
          <year>2017</year>
          <month>08</month>
          <conf-name>Proceedings of the 2nd Machine Learning for Healthcare Conference</conf-name>
          <conf-date>Aug 18-19, 2017</conf-date>
          <conf-loc>Boston, Massachusetts, USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://proceedings.mlr.press/v68/choi17a.html"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hjelm</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jacob</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Trischler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Che</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bengio</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Boundary-seeking generative adversarial networks</article-title>
          <source>arXiv</source>
          <year>2017</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1702.08431">https://arxiv.org/abs/1702.08431</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Qi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Practical privacy preserving POI recommendation</article-title>
          <source>ACM Trans Intell Syst Technol</source>
          <year>2020</year>
          <month>09</month>
          <day>05</day>
          <volume>11</volume>
          <issue>5</issue>
          <fpage>1</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1145/3394138</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="web">
          <article-title>Where the world builds software</article-title>
          <source>GitHub</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/">https://github.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref99">
        <label>99</label>
        <nlm-citation citation-type="web">
          <article-title>Anonymisation: managing data protection risk code of practice</article-title>
          <source>Information Commissioner's Office</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/media/1061/anonymisation-code.pdf">https://ico.org.uk/media/1061/anonymisation-code.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Defays</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Anwar</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Masking microdata using micro-aggregation</article-title>
          <source>J Off Stat</source>
          <year>1998</year>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>449</fpage>
          <lpage>61</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.proquest.com/openview/7da3f33250f6da2e2ae0297f29e2ba14/1?pq-origsite=gscholar&#38;cbl=105444"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fienberg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McIntyre</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Data swapping: variations on a theme by Dalenius and Reiss</article-title>
          <source>J Off Stat</source>
          <year>2005</year>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>309</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.proquest.com/docview/1266788053"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-540-25955-8_2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Permutation anonymization</article-title>
          <source>J Intell Inf Syst</source>
          <year>2015</year>
          <month>8</month>
          <day>4</day>
          <volume>47</volume>
          <issue>3</issue>
          <fpage>427</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1007/s10844-015-0373-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Herranz</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Torra</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Rethinking rank swapping to decrease disclosure risk</article-title>
          <source>Data Knowl Eng</source>
          <year>2008</year>
          <month>1</month>
          <volume>64</volume>
          <issue>1</issue>
          <fpage>346</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.1016/j.datak.2007.07.006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gouweleeuw</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kooiman</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Willenborg</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wolf</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Post randomisation for statistical disclosure control: theory and implementation</article-title>
          <source>J Off Stat</source>
          <year>1998</year>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>463</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.1002/9781118348239</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brand</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Microdata protection through noise addition</article-title>
          <source>Inference Control in Statistical Databases</source>
          <year>2002</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mateo-Sanz</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Resampling for statistical confidentiality in contingency tables</article-title>
          <source>Comput Math Appl</source>
          <year>1999</year>
          <month>12</month>
          <volume>38</volume>
          <issue>11-12</issue>
          <fpage>13</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1016/s0898-1221(99)00281-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El Emam</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rodgers</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Malin</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Anonymising and sharing individual patient data</article-title>
          <source>Br Med J</source>
          <year>2015</year>
          <month>03</month>
          <day>20</day>
          <volume>350</volume>
          <fpage>h1139</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25794882"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.h1139</pub-id>
          <pub-id pub-id-type="medline">25794882</pub-id>
          <pub-id pub-id-type="pmcid">PMC4707567</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vijayarani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tamilarasi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>An efficient masking technique for sensitive data protection</article-title>
          <source>Proceedings of the 2011 International Conference on Recent Trends in Information Technology (ICRTIT)</source>
          <year>2011</year>
          <conf-name>2011 International Conference on Recent Trends in Information Technology (ICRTIT)</conf-name>
          <conf-date>2011</conf-date>
          <conf-loc>Chennai, India</conf-loc>
          <publisher-name>Jun 3-5, 2011</publisher-name>
          <pub-id pub-id-type="doi">10.1109/icrtit.2011.5972275</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dwork</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Differential privacy</article-title>
          <source>Proceedings of International Colloquium on Automata, Languages, and Programming</source>
          <year>2011</year>
          <conf-name>International Colloquium on Automata, Languages, and Programming</conf-name>
          <conf-date>July 4-8, 2011</conf-date>
          <conf-loc>Zurich, Switzerland</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-1-4419-5906-5_752</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Golden</surname>
              <given-names>BL</given-names>
            </name>
            <name name-style="western">
              <surname>Assad</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>Cell suppression: disclosure protection for sensitive tabular data</article-title>
          <source>Netw Int J</source>
          <year>1992</year>
          <month>07</month>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>397</fpage>
          <lpage>417</lpage>
          <pub-id pub-id-type="doi">10.1002/net.3230220407</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Samarati</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sweeney</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Protecting privacy when disclosing information: k-anonymity and its enforcement through generalization and suppression</article-title>
          <source>CiteSeer - Technical Report, SRI International</source>
          <year>1998</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://citeseerx.ist.psu.edu/viewdoc/citations;jsessionid=6175EF3A3D18C80FE50ADB6B3E03B675?doi=10.1.1.37.5829">http://citeseerx.ist.psu.edu/viewdoc/citations;jsessionid=6175EF3A3D18C80FE50ADB6B3E03B675?doi=10.1.1.37.5829</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref112">
        <label>112</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sweeney</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>k-Anonymity: a model for protecting privacy</article-title>
          <source>Int J Unc Fuzz Knowl Based Syst</source>
          <year>2002</year>
          <volume>10</volume>
          <issue>05</issue>
          <fpage>557</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.1142/s0218488502001648</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref113">
        <label>113</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Torra</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Ordinal, continuous and heterogeneous k-Anonymity through microaggregation</article-title>
          <source>Data Min Knowl Disc</source>
          <year>2005</year>
          <month>8</month>
          <day>23</day>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>195</fpage>
          <lpage>212</lpage>
          <pub-id pub-id-type="doi">10.1007/s10618-005-0007-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref114">
        <label>114</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Meyerson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>On the complexity of optimal K-anonymity</article-title>
          <source>Proceedings of the Twenty-Third ACM SIGMOD-SIGACT-SIGART Symposium on Principles of Database Systems</source>
          <year>2004</year>
          <conf-name>PODS '04: Proceedings of the Twenty-Third ACM SIGMOD-SIGACT-SIGART Symposium on Principles of Database Systems</conf-name>
          <conf-date>Jun 14-16, 2004</conf-date>
          <conf-loc>Paris France</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1055558.1055591</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref115">
        <label>115</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sweeney</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Achieving k-Anonymity privacy protection using generalization and suppression</article-title>
          <source>Int J Unc Fuzz Knowl Based Syst</source>
          <year>2012</year>
          <month>05</month>
          <day>02</day>
          <volume>10</volume>
          <issue>05</issue>
          <fpage>571</fpage>
          <lpage>88</lpage>
          <pub-id pub-id-type="doi">10.1142/s021848850200165x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref116">
        <label>116</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>LeFevre</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>DeWitt</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ramakrishnan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Incognito: efficient full-domain K-anonymity</article-title>
          <source>Proceedings of the 2005 ACM SIGMOD International Conference on Management of Data</source>
          <year>2021</year>
          <month>8</month>
          <day>30</day>
          <conf-name>SIGMOD '05: Proceedings of the 2005 ACM SIGMOD International Conference on Management of Data</conf-name>
          <conf-date>Jun 14-16, 2005</conf-date>
          <conf-loc>Baltimore Maryland</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1066157.1066164</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>LeFevre</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>DeWitt</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ramakrishnan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Mondrian multidimensional K-anonymity</article-title>
          <source>Proceedings of the 22nd International Conference on Data Engineering (ICDE'06)</source>
          <year>2006</year>
          <conf-name>22nd International Conference on Data Engineering (ICDE'06)</conf-name>
          <conf-date>Apr 3-7, 2006</conf-date>
          <conf-loc>Atlanta, GA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icde.2006.101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Preservation of proximity privacy in publishing numerical sensitive data</article-title>
          <source>Proceedings of the 2008 ACM SIGMOD International Conference on Management of Data</source>
          <year>2008</year>
          <conf-name>SIGMOD '08: Proceedings of the 2008 ACM SIGMOD International Conference on Management of Data</conf-name>
          <conf-date>Jun 9-12, 2008</conf-date>
          <conf-loc>Vancouver Canada</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1376616.1376666</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chaurasia</surname>
              <given-names>SK</given-names>
            </name>
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Comparison of K-automorphism and K2-degree anonymization for privacy preserving in social network</article-title>
          <source>Int J Comput Appl</source>
          <year>2013</year>
          <month>10</month>
          <volume>79</volume>
          <issue>14</issue>
          <fpage>30</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.5120/13811-1871</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref120">
        <label>120</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>On optimal anonymization for l+-diversity</article-title>
          <source>Proceedings of the 2010 IEEE 26th International Conference on Data Engineering (ICDE 2010)</source>
          <year>2010</year>
          <conf-name>2010 IEEE 26th International Conference on Data Engineering (ICDE 2010)</conf-name>
          <conf-date>Mar 1-6, 2010</conf-date>
          <conf-loc>Long Beach, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/ICDE.2010.5447898</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Venkatasubramanian</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>t-Closeness: privacy beyond k-anonymity and l-diversity</article-title>
          <source>Proceedings of the 2007 IEEE 23rd International Conference on Data Engineering</source>
          <year>2007</year>
          <conf-name>2007 IEEE 23rd International Conference on Data Engineering</conf-name>
          <conf-date>Apr 15-20, 2007</conf-date>
          <conf-loc>Istanbul, Turkey</conf-loc>
          <pub-id pub-id-type="doi">10.1109/ICDE.2007.367856</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Soria-Comas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sanchez</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>t-closeness through microaggregation: strict privacy with enhanced utility preservation</article-title>
          <source>Proceedings of the 2016 IEEE 32nd International Conference on Data Engineering (ICDE)</source>
          <year>2016</year>
          <conf-name>2016 IEEE 32nd International Conference on Data Engineering (ICDE)</conf-name>
          <conf-date>May 16-20, 2016</conf-date>
          <conf-loc>Helsinki, Finland</conf-loc>
          <pub-id pub-id-type="doi">10.1109/ICDE.2016.7498376</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Soria-Comas</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>From t-closeness to differential privacy and vice versa in data anonymization</article-title>
          <source>Knowl Based Syst</source>
          <year>2015</year>
          <month>01</month>
          <volume>74</volume>
          <fpage>151</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1016/j.knosys.2014.11.011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref124">
        <label>124</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chawla</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dwork</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McSherry</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wee</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Toward privacy in public databases</article-title>
          <source>Theory of Cryptography</source>
          <year>2005</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Karras</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Publishing microdata with a robust privacy guarantee</article-title>
          <source>Proc VLDB Endowment</source>
          <year>2012</year>
          <month>07</month>
          <volume>5</volume>
          <issue>11</issue>
          <fpage>1388</fpage>
          <lpage>99</lpage>
          <pub-id pub-id-type="doi">10.14778/2350229.2350255</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dwork</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McSherry</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Nissim</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Calibrating noise to sensitivity in private data analysis</article-title>
          <source>Theory of Cryptography</source>
          <year>2006</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gaboardi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Haeberlen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khanna</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Narayan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pierce</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Differential privacy: an economic method for choosing epsilon</article-title>
          <source>Proceedings of the 2014 IEEE 27th Computer Security Foundations Symposium</source>
          <year>2014</year>
          <conf-name>2014 IEEE 27th Computer Security Foundations Symposium</conf-name>
          <conf-date>Jul 19-22, 2014</conf-date>
          <conf-loc>Vienna, Austria</conf-loc>
          <pub-id pub-id-type="doi">10.1109/csf.2014.35</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref128">
        <label>128</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Krehbiel</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Choosing epsilon for privacy as a service</article-title>
          <source>Proc Priv Enhanc Technol</source>
          <year>2018</year>
          <volume>2019</volume>
          <issue>1</issue>
          <fpage>192</fpage>
          <lpage>205</lpage>
          <pub-id pub-id-type="doi">10.2478/popets-2019-0011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref129">
        <label>129</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Katewa</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Pasqualetti</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>On the role of cooperation in private multi-agent systems</article-title>
          <source>Privacy in Dynamical Systems</source>
          <year>2020</year>
          <publisher-loc>Singapore</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref130">
        <label>130</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holohan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Antonatos</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Braghin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aonghusa</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>($ k $, $\epsilon $)-anonymity: $ k $-anonymity with $\epsilon $-differential privacy</article-title>
          <source>Data Privacy @ IBMRisk and Privacy</source>
          <year>2017</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/320223744_kepsilon-Anonymity_k-Anonymity_with_epsilon-Differential_Privacy">https://www.researchgate.net/publication/320223744_kepsilon-Anonymity_k-Anonymity_with_epsilon-Differential_Privacy</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref131">
        <label>131</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Holohan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Braghin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mac</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Levacher</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Diffprivlib: the IBM differential privacy library</article-title>
          <source>arXiv</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1907.02444">https://arxiv.org/abs/1907.02444</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref132">
        <label>132</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dwork</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kenthapadi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>McSherry</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Mironov</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Naor</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Our data, ourselves: privacy via distributed noise generation</article-title>
          <source>Advances in Cryptology - EUROCRYPT 2006</source>
          <year>2006</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref133">
        <label>133</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bild</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Prasser</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>SafePub: a truthful data anonymization algorithm with strong privacy guarantees</article-title>
          <source>Proc Priv Enhanc Technol</source>
          <year>2018</year>
          <volume>2018</volume>
          <issue>1</issue>
          <fpage>67</fpage>
          <lpage>87</lpage>
          <pub-id pub-id-type="doi">10.1515/popets-2018-0004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref134">
        <label>134</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Blum</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ligett</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Roth</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A learning theory approach to noninteractive database privacy</article-title>
          <source>J Asso Comput Machin</source>
          <year>2013</year>
          <month>04</month>
          <volume>60</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1145/2450142.2450148</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref135">
        <label>135</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beimel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nissim</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Stemmer</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Private learning and sanitization: pure vs. Approximate differential privacy</article-title>
          <source>Approximation, Randomization, and Combinatorial Optimization. Algorithms and Techniques</source>
          <year>2013</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref136">
        <label>136</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dwork</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Roth</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The algorithmic foundations of differential privacy</article-title>
          <source>Foundations and Trends in Theoretical Computer</source>
          <year>2014</year>
          <publisher-loc>Boston</publisher-loc>
          <publisher-name>Now Publishers Inc</publisher-name>
          <fpage>211</fpage>
          <lpage>407</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref137">
        <label>137</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Goodfellow</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>McMahan</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mironov</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Talwar</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Deep learning with differential privacy</article-title>
          <source>Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security</source>
          <year>2016</year>
          <conf-name>CCS '16: Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security</conf-name>
          <conf-date>Oct 24-28, 2016</conf-date>
          <conf-loc>Vienna Austria</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2976749.2978318</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref138">
        <label>138</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>TH</given-names>
            </name>
            <name name-style="western">
              <surname>Rieffel</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving aggregation of time-series data</article-title>
          <source>Proceedings of the Network and Distributed System Security Symposium</source>
          <year>2011</year>
          <conf-name>Network and Distributed System Security Symposium</conf-name>
          <conf-date>Feb 6-9, 2011</conf-date>
          <conf-loc>San Diego, California, USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/221655415_Privacy-Preserving_Aggregation_of_Time-Series_Data"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref139">
        <label>139</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jelasity</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Birman</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Distributional differential privacy for large-scale smart metering</article-title>
          <source>Proceedings of the 2nd ACM workshop on Information Hiding and Multimedia Security</source>
          <year>2014</year>
          <conf-name>IH&#38;MMSec '14: 2nd ACM workshop on Information Hiding and Multimedia Security</conf-name>
          <conf-date>Jun 11-13, 2014</conf-date>
          <conf-loc>Salzburg Austria</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2600918.2600919</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref140">
        <label>140</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chatzikokolakis</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Andrés</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bordenabe</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Palamidessi</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Broadening the scope of differential privacy using metrics</article-title>
          <source>Proceedings of the International Symposium on Privacy Enhancing Technologies Symposium</source>
          <year>2013</year>
          <conf-name>International Symposium on Privacy Enhancing Technologies Symposium</conf-name>
          <conf-date>Jul 10-12, 2013</conf-date>
          <conf-loc>Bloomington, IN, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-3-642-39077-7_5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref141">
        <label>141</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Fung</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Anonymizing sequential releases</article-title>
          <source>Proceedings of the 12th ACM SIGKDD international conference on Knowledge discovery and data mining</source>
          <year>2006</year>
          <conf-name>KDD '06: 12th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</conf-name>
          <conf-date>Aug 20-23, 2006</conf-date>
          <conf-loc>Philadelphia PA USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1150402.1150449</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref142">
        <label>142</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oliveira</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Zaiane</surname>
              <given-names>OR</given-names>
            </name>
          </person-group>
          <article-title>Privacy preserving clustering by data transformation</article-title>
          <source>J Inf Data Manag</source>
          <year>2010</year>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://periodicos.ufmg.br/index.php/jidm/article/view/32"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref143">
        <label>143</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brickell</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shmatikov</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>The cost of privacy: destruction of data-mining utility in anonymized data publishing</article-title>
          <source>Proceedings of the 14th ACM SIGKDD international conference on Knowledge discovery and data mining</source>
          <year>2008</year>
          <conf-name>KDD '08: 14th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</conf-name>
          <conf-date>Aug 24-27, 2008</conf-date>
          <conf-loc>Las Vegas Nevada USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1401890.1401904</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref144">
        <label>144</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Evfimievski</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Srikant</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Agrawal</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gehrke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Privacy preserving mining of association rules</article-title>
          <source>Inf Syst</source>
          <year>2004</year>
          <month>6</month>
          <volume>29</volume>
          <issue>4</issue>
          <fpage>343</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.1016/j.is.2003.09.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref145">
        <label>145</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rastogi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Suciu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The boundary between privacy and utility in data publishing</article-title>
          <source>Proceedings of the 33rd International Conference on Very Large Data Bases</source>
          <year>2007</year>
          <conf-name>VLDB '07: 33rd International Conference on Very Large Data Bases</conf-name>
          <conf-date>Sep 23-27, 2007</conf-date>
          <conf-loc>Vienna, Austria</conf-loc>
          <fpage>531</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.5555/1325851.1325913</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref146">
        <label>146</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nergiz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Atzori</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Clifton</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Hiding the presence of individuals from shared databases</article-title>
          <source>Proceedings of the 2007 ACM SIGMOD International Conference on Management of Data</source>
          <year>2007</year>
          <conf-name>SIGMOD '07: 2007 ACM SIGMOD International Conference on Management of Data</conf-name>
          <conf-date>Jun 11-14, 2007</conf-date>
          <conf-loc>Beijing China</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1247480.1247554</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref147">
        <label>147</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rocher</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hendrickx</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>de Montjoye</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Estimating the success of re-identifications in incomplete datasets using generative models</article-title>
          <source>Nat Commun</source>
          <year>2019</year>
          <month>07</month>
          <day>23</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>3069</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41467-019-10933-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41467-019-10933-3</pub-id>
          <pub-id pub-id-type="medline">31337762</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41467-019-10933-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC6650473</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref148">
        <label>148</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hoshino</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Applying Pitman’s sampling formula to microdata disclosure risk assessment</article-title>
          <source>J Off Stat</source>
          <year>2001</year>
          <volume>17</volume>
          <issue>4</issue>
          <fpage>499</fpage>
          <lpage>520</lpage>
          <pub-id pub-id-type="doi">10.1007/978-3-319-50272-4_3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref149">
        <label>149</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zayatz</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Estimation of the percent of unique population elements on a microdata file using the sample</article-title>
          <source>Bureau of the Census Statistical Research Division Report Series</source>
          <year>1991</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.census.gov/srd/papers/pdf/rr91-08.pdf">https://www.census.gov/srd/papers/pdf/rr91-08.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref150">
        <label>150</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Keller-McNulty</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Estimation of identification disclosure risk in microdata</article-title>
          <source>J Off Stat</source>
          <year>1998</year>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>79</fpage>
          <lpage>95</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref151">
        <label>151</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Genz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bretz</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <source>Computation of Multivariate Normal and t Probabilities</source>
          <year>2009</year>
          <publisher-loc>Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref152">
        <label>152</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wan</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Vorobeychik</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xia</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Clayton</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Kantarcioglu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ganta</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Heatherly</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Malin</surname>
              <given-names>BA</given-names>
            </name>
          </person-group>
          <article-title>A game theoretic framework for analyzing re-identification risk</article-title>
          <source>PLoS One</source>
          <year>2015</year>
          <month>3</month>
          <day>25</day>
          <volume>10</volume>
          <issue>3</issue>
          <fpage>e0120592</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0120592"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0120592</pub-id>
          <pub-id pub-id-type="medline">25807380</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-47977</pub-id>
          <pub-id pub-id-type="pmcid">PMC4373733</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref153">
        <label>153</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gkountouna</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Angeli</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zigomitros</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Terrovitis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vassiliou</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>km-Anonymity for continuous data using dynamic hierarchies</article-title>
          <source>Privacy in Statistical Databases</source>
          <year>2014</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref154">
        <label>154</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Poulis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Loukides</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Gkoulalas-Divanis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Skiadopoulos</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Anonymizing data with relational and transaction attributes</article-title>
          <source>Machine Learning and Knowledge Discovery in Databases</source>
          <year>2013</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref155">
        <label>155</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Terzi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Towards identity anonymization on graphs</article-title>
          <source>Proceedings of the 2008 ACM SIGMOD International Conference on Management of Data</source>
          <year>2008</year>
          <conf-name>SIGMOD '08: 2008 ACM SIGMOD International Conference on Management of Data</conf-name>
          <conf-date>Jun 9-12, 2008</conf-date>
          <conf-loc>Vancouver Canada</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1376616.1376629</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref156">
        <label>156</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tai</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>DN</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving social network publication against friendship attacks</article-title>
          <source>Proceedings of the 17th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</source>
          <year>2011</year>
          <conf-name>KDD '11: 17th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</conf-name>
          <conf-date>Aug 21-24, 2011</conf-date>
          <conf-loc>San Diego California</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2020408.2020599</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref157">
        <label>157</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Özsu</surname>
              <given-names>MT</given-names>
            </name>
          </person-group>
          <article-title>k-automorphism: a general framework for privacy preserving network publication</article-title>
          <source>Proc VLDB Endow</source>
          <year>2009</year>
          <month>08</month>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>946</fpage>
          <lpage>57</lpage>
          <pub-id pub-id-type="doi">10.14778/1687627.1687734</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref158">
        <label>158</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Korolova</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Motwani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Nabar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Link privacy in social networks</article-title>
          <source>Proceedings of the 17th ACM Conference on Information and Knowledge Management</source>
          <year>2008</year>
          <conf-name>CIKM '08: 17th ACM Conference on Information and Knowledge Management</conf-name>
          <conf-date>Oct 26-30, 2008</conf-date>
          <conf-loc>Napa Valley California USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1458082.1458123</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref159">
        <label>159</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Pei</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Preserving privacy in social networks against neighborhood attacks</article-title>
          <source>Proceedings of the 2008 IEEE 24th International Conference on Data Engineering</source>
          <year>2008</year>
          <conf-name>2008 IEEE 24th International Conference on Data Engineering</conf-name>
          <conf-date>Apr 7-12, 2008</conf-date>
          <conf-loc>Cancun, Mexico</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icde.2008.4497459</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref160">
        <label>160</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Miklau</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Towsley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Weis</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Resisting structural re-identification in anonymized social networks</article-title>
          <source>Proc VLDB Endow</source>
          <year>2008</year>
          <month>08</month>
          <day>14</day>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>102</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.14778/1453856.1453873</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref161">
        <label>161</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Feder</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Nabar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Terzi</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Anonymizing graphs</article-title>
          <source>arXiv</source>
          <year>2008</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/0810.5578">https://arxiv.org/abs/0810.5578</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref162">
        <label>162</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stokes</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Torra</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Reidentification and k-anonymity: a model for disclosure risk in graphs</article-title>
          <source>Soft Comput</source>
          <year>2012</year>
          <month>5</month>
          <day>1</day>
          <volume>16</volume>
          <issue>10</issue>
          <fpage>1657</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.1007/s00500-012-0850-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref163">
        <label>163</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bettini</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Jajodia</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Protecting privacy against location-based personal identification</article-title>
          <source>Secure Data Management. SDM 2005. Lecture Notes in Computer Science</source>
          <year>2005</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref164">
        <label>164</label>
        <nlm-citation citation-type="web">
          <article-title>ARX: a comprehensive tool for anonymizing biomedical data</article-title>
          <source>Institute of Medical Statistics and Epidemiology</source>
          <year>2015</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pdfs.semanticscholar.org/dbe3/a46ea167e70a086ce96a2ffed56be2114c0f.pdf">https://pdfs.semanticscholar.org/dbe3/a46ea167e70a086ce96a2ffed56be2114c0f.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref165">
        <label>165</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Emam</surname>
              <given-names>KE</given-names>
            </name>
            <name name-style="western">
              <surname>Arbuckle</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>Anonymizing Health Data: Case Studies and Methods to Get You Started</source>
          <year>2014</year>
          <publisher-loc>Sebastopol, California, United States</publisher-loc>
          <publisher-name>O'Reilly Media</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref166">
        <label>166</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Erkin</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Veugen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Toft</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lagendijk</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Generating private recommendations efficiently using homomorphic encryption and data packing</article-title>
          <source>IEEE Trans Inform Forensic Secur</source>
          <year>2012</year>
          <month>06</month>
          <volume>7</volume>
          <issue>3</issue>
          <fpage>1053</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1109/tifs.2012.2190726</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref167">
        <label>167</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Paillier</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Public-key cryptosystems based on composite degree residuosity classes</article-title>
          <source>Proceedings of the Annual International Conference on the Theory and Applications of Cryptographic Techniques</source>
          <year>1999</year>
          <conf-name>Annual International Conference on the Theory and Applications of Cryptographic Techniques</conf-name>
          <conf-date>May 2-6, 1999</conf-date>
          <conf-loc>Prague, Czech Republic</conf-loc>
          <pub-id pub-id-type="doi">10.1007/3-540-48910-x_16</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref168">
        <label>168</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Compressive privacy: from information\/estimation theory to machine learning [lecture notes]</article-title>
          <source>IEEE Signal Process Mag</source>
          <year>2017</year>
          <month>1</month>
          <volume>34</volume>
          <issue>1</issue>
          <fpage>94</fpage>
          <lpage>112</lpage>
          <pub-id pub-id-type="doi">10.1109/msp.2016.2616720</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref169">
        <label>169</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chanyaswad</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Collaborative PCA/DCA learning methods for compressive privacy</article-title>
          <source>ACM Trans Embed Comput Syst</source>
          <year>2017</year>
          <month>07</month>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1145/2996460</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref170">
        <label>170</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pinto</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A comparison of anonymization protection principles</article-title>
          <source>Proceedings of the 2012 IEEE 13th International Conference on Information Reuse &#38; Integration (IRI)</source>
          <year>2012</year>
          <conf-name>2012 IEEE 13th International Conference on Information Reuse &#38; Integration (IRI)</conf-name>
          <conf-date>Aug 8-10, 2012</conf-date>
          <conf-loc>Las Vegas, NV, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/iri.2012.6303012</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref171">
        <label>171</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Elliot</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The future of statistical disclosure control</article-title>
          <source>arXiv</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1812.09204">https://arxiv.org/abs/1812.09204</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref172">
        <label>172</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ayala-Rivera</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>McDonagh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cerqueus</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Murphy</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A systematic comparison and evaluation of k-anonymization algorithms for practitioners</article-title>
          <source>Trans Data Privacy</source>
          <year>2014</year>
          <month>12</month>
          <volume>7</volume>
          <issue>3</issue>
          <fpage>337</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.5555/2870614.2870620</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref173">
        <label>173</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Machanavajjhala</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kifer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gehrke</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Venkitasubramaniam</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>L-diversity: privacy beyond k-anonymity</article-title>
          <source>Proceedings of the 22nd International Conference on Data Engineering (ICDE'06)</source>
          <year>2007</year>
          <conf-name>22nd International Conference on Data Engineering (ICDE'06)</conf-name>
          <conf-date>Apr 3-7, 2006</conf-date>
          <conf-loc>Atlanta, GA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/ICDE.2006.1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref174">
        <label>174</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>(α, k)-anonymity: an enhanced k-anonymity model for privacy preserving data publishing</article-title>
          <source>Proceedings of the 12th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</source>
          <year>2006</year>
          <conf-name>KDD '06: Proceedings of the 12th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</conf-name>
          <conf-date>Aug 20-23, 2006</conf-date>
          <conf-loc>Philadelphia PA USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1150402.1150499</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref175">
        <label>175</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sweeney</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Computational disclosure control: a primer on data privacy protection</article-title>
          <source>Thesis and Dissertations - Massachusetts Institute of Technology</source>
          <year>2001</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dspace.mit.edu/handle/1721.1/8589">https://dspace.mit.edu/handle/1721.1/8589</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref176">
        <label>176</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Tao</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>M-invariance: towards privacy preserving re-publication of dynamic datasets</article-title>
          <source>Proceedings of the 2007 ACM SIGMOD International Conference on Management of Data</source>
          <year>2007</year>
          <conf-name>SIGMOD '07: Proceedings of the 2007 ACM SIGMOD International Conference on Management of Data</conf-name>
          <conf-date>Jun 11-14, 2007</conf-date>
          <conf-loc>Beijing China</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1247480.1247556</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref177">
        <label>177</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Koudas</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Aggregate query answering on anonymized tables</article-title>
          <source>Proceedings of the 2007 IEEE 23rd International Conference on Data Engineering</source>
          <year>2007</year>
          <conf-name>2007 IEEE 23rd International Conference on Data Engineering</conf-name>
          <conf-date>Apr 15-20, 2007</conf-date>
          <conf-loc>Istanbul, Turkey</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icde.2007.367857</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref178">
        <label>178</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Qishan</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhensi</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Qunhua</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>(K, G)-anonymity model based on grey relational analysis</article-title>
          <source>Proceedings of 2013 IEEE International Conference on Grey systems and Intelligent Services (GSIS)</source>
          <year>2013</year>
          <conf-name>Proceedings of 2013 IEEE International Conference on Grey systems and Intelligent Services (GSIS)</conf-name>
          <conf-date>Nov 15-17, 2013</conf-date>
          <conf-loc>Macao, China</conf-loc>
          <pub-id pub-id-type="doi">10.1109/gsis.2013.6714730</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref179">
        <label>179</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Han</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Research in microaggregation algorithms for k-anonymization</article-title>
          <source>Acta Electronica Sinica</source>
          <year>2008</year>
          <volume>36</volume>
          <issue>10</issue>
          <fpage>2021</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/290599299_Research_in_microaggregation_algorithms_for_k-anonymization"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref180">
        <label>180</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nergiz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Clifton</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Nergiz</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Multirelational k-anonymity</article-title>
          <source>IEEE Trans Knowl Data Eng</source>
          <year>2009</year>
          <month>08</month>
          <volume>21</volume>
          <issue>8</issue>
          <fpage>1104</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.1109/tkde.2008.210</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref181">
        <label>181</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Prasser</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kohlmayer</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lautenschläger</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>ARX--a comprehensive tool for anonymizing biomedical data</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2014</year>
          <month>11</month>
          <day>14</day>
          <volume>2014</volume>
          <fpage>984</fpage>
          <lpage>93</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/25954407"/>
          </comment>
          <pub-id pub-id-type="medline">25954407</pub-id>
          <pub-id pub-id-type="pmcid">PMC4419984</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref182">
        <label>182</label>
        <nlm-citation citation-type="web">
          <article-title>Introduction of Anonimatron - The free, extendable, open source data anonymization tool</article-title>
          <source>GitHub</source>
          <access-date>2021-09-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://realrolfje.github.io/anonimatron/">https://realrolfje.github.io/anonimatron/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref183">
        <label>183</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kearns</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pai</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Roth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ullman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Mechanism design in large games: incentives and privacy</article-title>
          <source>Proceedings of the 5th conference on Innovations in Theoretical Computer Science</source>
          <year>2014</year>
          <conf-name>ITCS '14: Proceedings of the 5th conference on Innovations in Theoretical Computer Science</conf-name>
          <conf-date>Jan 12-14, 2014</conf-date>
          <conf-loc>Princeton New Jersey USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2554797.2554834</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref184">
        <label>184</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kasperbauer</surname>
              <given-names>TJ</given-names>
            </name>
          </person-group>
          <article-title>Protecting health privacy even when privacy is lost</article-title>
          <source>J Med Ethics</source>
          <year>2020</year>
          <month>11</month>
          <volume>46</volume>
          <issue>11</issue>
          <fpage>768</fpage>
          <lpage>72</lpage>
          <pub-id pub-id-type="doi">10.1136/medethics-2019-105880</pub-id>
          <pub-id pub-id-type="medline">31806677</pub-id>
          <pub-id pub-id-type="pii">medethics-2019-105880</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref185">
        <label>185</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goodfellow</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Pouget-Abadie</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mirza</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Warde-Farley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ozair</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Courville</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bengio</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Generative adversarial networks</article-title>
          <source>Commun ACM</source>
          <year>2020</year>
          <month>10</month>
          <day>22</day>
          <volume>63</volume>
          <issue>11</issue>
          <fpage>139</fpage>
          <lpage>44</lpage>
          <pub-id pub-id-type="doi">10.1145/3422622</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref186">
        <label>186</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>D’Acquisto</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Naldi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A conceptual framework for assessing anonymization-utility trade-offs based on principal component analysis</article-title>
          <source>arXiv</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1903.11700?utm_source=feedburner&#38;utm_medium=feed&#38;utm_campaign=Feed%3A+arxiv%2FQSXk+%28ExcitingAds%21+cs+updates+on+arXiv.org%29">https://arxiv.org/abs/1903.11700?utm_source=feedburner&#38;utm_medium=feed&#38;utm_campaign=Feed%3A+arxiv%2FQSXk+%28ExcitingAds%21+cs+updates+on+arXiv.org%29</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref187">
        <label>187</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Matatov</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rokach</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Maimon</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving data mining: a feature set partitioning approach</article-title>
          <source>Inf Sci</source>
          <year>2010</year>
          <month>7</month>
          <day>15</day>
          <volume>180</volume>
          <issue>14</issue>
          <fpage>2696</fpage>
          <lpage>720</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ins.2010.03.011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref188">
        <label>188</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iyengar</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Transforming data to satisfy privacy constraints</article-title>
          <source>Proceedings of the eighth ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</source>
          <year>2002</year>
          <conf-name>KDD02: The Eighth ACM SIGKDD International Conference on Knowledge Discovery and Data Mining</conf-name>
          <conf-date>Jul 23-26, 2002</conf-date>
          <conf-loc>Edmonton Alberta Canada</conf-loc>
          <pub-id pub-id-type="doi">10.1145/775047.775089</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref189">
        <label>189</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nergiz</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Clifton</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Thoughts on k-anonymization</article-title>
          <source>Data Know Eng</source>
          <year>2007</year>
          <month>12</month>
          <volume>63</volume>
          <issue>3</issue>
          <fpage>622</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1016/j.datak.2007.03.009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref190">
        <label>190</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mahesh</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Meyyappan</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Anonymization technique through record elimination to preserve privacy of published data</article-title>
          <source>Proceedings of the 2013 International Conference on Pattern Recognition, Informatics and Mobile Engineering</source>
          <year>2013</year>
          <conf-name>2013 International Conference on Pattern Recognition, Informatics and Mobile Engineering</conf-name>
          <conf-date>Feb 21-22, 2013</conf-date>
          <conf-loc>Salem, India</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icprime.2013.6496495</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref191">
        <label>191</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bayardo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Agrawal</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Data privacy through optimal k-anonymization</article-title>
          <source>Proceedings of the  21st International Conference on Data Engineering (ICDE'05)</source>
          <year>2005</year>
          <conf-name>21st International Conference on Data Engineering (ICDE'05)</conf-name>
          <conf-date>Apr 5-8, 2005</conf-date>
          <conf-loc>Tokyo, Japan</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icde.2005.42</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref192">
        <label>192</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Foygel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Srebro</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Salakhutdinov</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Matrix reconstruction with the local max norm</article-title>
          <source>arXiv</source>
          <year>2012</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1210.5196">https://arxiv.org/abs/1210.5196</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref193">
        <label>193</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zwillinger</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <source>CRC Standard Mathematical Tables and Formulas</source>
          <year>2018</year>
          <month>1</month>
          <publisher-loc>Boca Raton</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref194">
        <label>194</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kshirsagar</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Correlation between two vector variables</article-title>
          <source>J R Stat Soc Series B Stat Methodol</source>
          <year>2018</year>
          <month>12</month>
          <day>05</day>
          <volume>31</volume>
          <issue>3</issue>
          <fpage>477</fpage>
          <lpage>85</lpage>
          <pub-id pub-id-type="doi">10.1111/j.2517-6161.1969.tb00807.x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref195">
        <label>195</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kullback</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Leibler</surname>
              <given-names>RA</given-names>
            </name>
          </person-group>
          <article-title>On information and sufficiency</article-title>
          <source>Ann Math Stat</source>
          <year>1951</year>
          <month>03</month>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>79</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1214/aoms/1177729694</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref196">
        <label>196</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duchi</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Derivations for linear algebra and optimization</article-title>
          <source>Stanford</source>
          <year>2007</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://ai.stanford.edu/~jduchi/projects/general_notes.pdf">http://ai.stanford.edu/~jduchi/projects/general_notes.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref197">
        <label>197</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Heng</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>Depth-attentional features for single-image rain removal</article-title>
          <source>Proceedings of the 2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2019</year>
          <conf-name>2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 15-20, 2019</conf-date>
          <conf-loc>Long Beach, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr.2019.00821</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref198">
        <label>198</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>RT</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Joint rain detection and removal from a single image with contextualized deep networks</article-title>
          <source>IEEE Trans Pattern Anal Mach Intell</source>
          <year>2020</year>
          <month>6</month>
          <day>1</day>
          <volume>42</volume>
          <issue>6</issue>
          <fpage>1377</fpage>
          <lpage>93</lpage>
          <pub-id pub-id-type="doi">10.1109/tpami.2019.2895793</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref199">
        <label>199</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Spatial attentive single-image deraining with a high quality real rain dataset</article-title>
          <source>Proceedings of the 2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2019</year>
          <conf-name>2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 15-20, 2019</conf-date>
          <conf-loc>Long Beach, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr.2019.01255</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref200">
        <label>200</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Paisley</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Lightweight pyramid networks for image deraining</article-title>
          <source>IEEE Trans Neural Netw Learn Syst</source>
          <year>2020</year>
          <month>6</month>
          <volume>31</volume>
          <issue>6</issue>
          <fpage>1794</fpage>
          <lpage>807</lpage>
          <pub-id pub-id-type="doi">10.1109/tnnls.2019.2926481</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref201">
        <label>201</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kwon</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Mu</surname>
              <given-names>LK</given-names>
            </name>
          </person-group>
          <article-title>Accurate image super-resolution using very deep convolutional networks</article-title>
          <source>Proceedings of the 2016 IEEE Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2016</year>
          <conf-name>2016 IEEE Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 27-30, 2016</conf-date>
          <conf-loc>Las Vegas, NV, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr.2016.182</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref202">
        <label>202</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Kunpeng</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Kai</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhong</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Image super-resolution using very deep residual channel attention networks</article-title>
          <source>Computer Vision – ECCV 2018</source>
          <year>2018</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref203">
        <label>203</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lei</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Comparison of image quality objective evaluation</article-title>
          <source>Proceedings of the 2009 International Conference on Computational Intelligence and Software Engineering</source>
          <year>2009</year>
          <conf-name>2009 International Conference on Computational Intelligence and Software Engineering</conf-name>
          <conf-date>Dec 11-13, 2009</conf-date>
          <conf-loc>Wuhan, China</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cise.2009.5366163</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref204">
        <label>204</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>HVS-based structural similarity for image quality assessment</article-title>
          <source>Proceedings of the 2008 9th International Conference on Signal Processing</source>
          <year>2008</year>
          <conf-name>2008 9th International Conference on Signal Processing</conf-name>
          <conf-date>Oct 26-29, 2008</conf-date>
          <conf-loc>Beijing, China</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icosp.2008.4697344</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref205">
        <label>205</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Winkler</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Issues in vision modeling for perceptual video quality assessment</article-title>
          <source>Signal Process</source>
          <year>1999</year>
          <month>10</month>
          <volume>78</volume>
          <issue>2</issue>
          <fpage>231</fpage>
          <lpage>52</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/S0165-1684(99)00062-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/s0165-1684(99)00062-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref206">
        <label>206</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gool</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Timofte</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Deep unfolding network for image super-resolution</article-title>
          <source>Proceedings of the 2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2020</year>
          <conf-name>2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 13-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr42600.2020.00328</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref207">
        <label>207</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Bovik</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Simoncelli</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Image quality assessment: from error visibility to structural similarity</article-title>
          <source>IEEE Trans Image Process</source>
          <year>2004</year>
          <month>04</month>
          <volume>13</volume>
          <issue>4</issue>
          <fpage>600</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1109/tip.2003.819861</pub-id>
          <pub-id pub-id-type="medline">15376593</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref208">
        <label>208</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>RT</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Single image deraining: from model-based to data-driven and beyond</article-title>
          <source>IEEE Trans Pattern Anal Mach Intell</source>
          <year>2020</year>
          <month>5</month>
          <day>19</day>
          <fpage>1</fpage>
          <pub-id pub-id-type="doi">10.1109/tpami.2020.2995190</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref209">
        <label>209</label>
        <nlm-citation citation-type="web">
          <article-title>P.800 : Methods for subjective determination of transmission quality</article-title>
          <source>International Telecommunication Union</source>
          <year>1996</year>
          <access-date>2021-09-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.itu.int/rec/T-REC-P.800-199608-I">https://www.itu.int/rec/T-REC-P.800-199608-I</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref210">
        <label>210</label>
        <nlm-citation citation-type="web">
          <article-title>RECOMMENDATION ITU-R BT.500-11: Methodology for the subjective assessment of the quality of television pictures</article-title>
          <source>International Telecommunication Union</source>
          <year>2002</year>
          <access-date>2021-09-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.gpds.ene.unb.br/databases/2012-UNB-Varium-Exp/Exp3-Delft/00-report-alexandre/Papers---Judith/Subjective%20Studies/ITU-Recommendation---BT500-11.pdf">http://www.gpds.ene.unb.br/databases/2012-UNB-Varium-Exp/Exp3-Delft/00-report-alexandre/Papers---Judith/Subjective%20Studies/ITU-Recommendation---BT500-11.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref211">
        <label>211</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ren</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Scheirer</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Zhong</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>DI</given-names>
            </name>
            <name name-style="western">
              <surname>Pu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Qu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Qu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wan</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhong</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Su</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Quan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>BO</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>QI</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhuang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lei</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>SZ</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Yi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Zuo</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Chi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhong</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Qin</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Advancing image understanding in poor visibility environments: a collective benchmark study</article-title>
          <source>IEEE Trans Image Process</source>
          <year>2020</year>
          <month>03</month>
          <day>27</day>
          <volume>29</volume>
          <fpage>5737</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1109/TIP.2020.2981922</pub-id>
          <pub-id pub-id-type="medline">32224457</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref212">
        <label>212</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaufman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Fattal</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Deblurring using analysis-synthesis networks pair</article-title>
          <source>Proceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2020</year>
          <conf-name>IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>June 13-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/CVPR42600.2020.00585</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref213">
        <label>213</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mentzer</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gool</surname>
              <given-names>LV</given-names>
            </name>
            <name name-style="western">
              <surname>Timofte</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Learning for video compression with hierarchical quality and recurrent enhancement</article-title>
          <source>Proceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2020</year>
          <conf-name>IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>June 13-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/CVPR42600.2020.00666</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref214">
        <label>214</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chaudhuri</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sarwate</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sinha</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A near-optimal algorithm for differentially-private principal components</article-title>
          <source>J Mach Learn Res</source>
          <year>2013</year>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>2905</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.4016/38611.01</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref215">
        <label>215</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dwork</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Talwar</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Thakurta</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Analyze gauss: optimal bounds for privacy-preserving principal component analysis</article-title>
          <source>Proceedings of the Forty-Sixth Annual ACM Symposium on Theory of Computing</source>
          <year>2014</year>
          <conf-name>STOC '14: Proceedings of the Forty-Sixth Annual ACM Symposium on Theory of Computing</conf-name>
          <conf-date>May 31- Jun 3, 2014</conf-date>
          <conf-loc>New York</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2591796.2591883</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref216">
        <label>216</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sarwate</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Corander</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hero</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tarokh</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Analysis of a privacy-preserving PCA algorithm using random matrix theory</article-title>
          <source>Proceedings of the 2016 IEEE Global Conference on Signal and Information Processing (GlobalSIP)</source>
          <year>2016</year>
          <conf-name>2016 IEEE Global Conference on Signal and Information Processing (GlobalSIP)</conf-name>
          <conf-date>Dec 7-9, 2016</conf-date>
          <conf-loc>Washington, DC, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/globalsip.2016.7906058</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref217">
        <label>217</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Al-Rubaie</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kung</surname>
              <given-names>SY</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving PCA on horizontally-partitioned data</article-title>
          <source>Proceedings of the 2017 IEEE Conference on Dependable and Secure Computing</source>
          <year>2017</year>
          <conf-name>2017 IEEE Conference on Dependable and Secure Computing</conf-name>
          <conf-date>Aug 7-10, 2017</conf-date>
          <conf-loc>Taipei, Taiwan</conf-loc>
          <pub-id pub-id-type="doi">10.1109/desec.2017.8073817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref218">
        <label>218</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grammenos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mendoza-Smith</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mascolo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Crowcroft</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Federated PCA with adaptive rank estimation</article-title>
          <source>CoRR</source>
          <year>2019</year>
          <access-date>2021-09-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/334558717_Federated_PCA_with_Adaptive_Rank_Estimation">https://www.researchgate.net/publication/334558717_Federated_PCA_with_Adaptive_Rank_Estimation</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref219">
        <label>219</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Privacy preserving PCA for multiparty modeling</article-title>
          <source>arXiv</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2002.02091">https://arxiv.org/abs/2002.02091</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref220">
        <label>220</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Privacy preserving point-of-interest recommendation using decentralized matrix factorization</article-title>
          <source>Proceedings of the Thirty-Second AAAI Conference on Artificial Intelligence</source>
          <year>2018</year>
          <conf-name>Thirty-Second AAAI Conference on Artificial Intelligence</conf-name>
          <conf-date>Feb 2-7, 2018</conf-date>
          <conf-loc>New Orleans, Louisiana, USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ojs.aaai.org/index.php/AAAI/article/view/11244"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref221">
        <label>221</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mohassel</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>SecureML: a system for scalable privacy-preserving machine learning</article-title>
          <source>Proceedings of the 2017 IEEE Symposium on Security and Privacy (SP)</source>
          <year>2017</year>
          <conf-name>2017 IEEE Symposium on Security and Privacy (SP)</conf-name>
          <conf-date>May 22-26, 2017</conf-date>
          <conf-loc>San Jose, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/sp.2017.12</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref222">
        <label>222</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xing</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Mutual privacy preserving $k$ -means clustering in social participatory sensing</article-title>
          <source>IEEE Trans Ind Inf</source>
          <year>2017</year>
          <month>8</month>
          <day>18</day>
          <volume>13</volume>
          <issue>4</issue>
          <fpage>2066</fpage>
          <lpage>76</lpage>
          <pub-id pub-id-type="doi">10.1109/tii.2017.2695487</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref223">
        <label>223</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>LT</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Q</given-names>
            </name>
          </person-group>
          <article-title>A privacy-preserving high-order neuro-fuzzy c-means algorithm with cloud computing</article-title>
          <source>Neurocomputing</source>
          <year>2017</year>
          <month>09</month>
          <volume>256</volume>
          <fpage>82</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1016/j.neucom.2016.08.135</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref224">
        <label>224</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Manikandan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Porkodi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Mohammed</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sivaram</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Privacy preserving data mining using threshold based fuzzy cmeans clustering</article-title>
          <source>ICTACT J Soft Comput</source>
          <year>2018</year>
          <month>10</month>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>0253</fpage>
          <pub-id pub-id-type="doi">10.21917/ijsc.2018.0253</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref225">
        <label>225</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Anuradha</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Srinivas</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Prasad</surname>
              <given-names>MK</given-names>
            </name>
          </person-group>
          <article-title>A frame work for preserving privacy in social media using generalized gaussian mixture model</article-title>
          <source>Int J Adv Comput Sci Appl</source>
          <year>2015</year>
          <volume>6</volume>
          <issue>7</issue>
          <fpage>68</fpage>
          <lpage>71</lpage>
          <pub-id pub-id-type="doi">10.14569/ijacsa.2015.060711</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref226">
        <label>226</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hahn</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>GRAFFL: gradient-free federated learning of a Bayesian generative model</article-title>
          <source>arXiv</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2008.12925">https://arxiv.org/abs/2008.12925</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref227">
        <label>227</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Publishing social network graph eigenspectrum with privacy guarantees</article-title>
          <source>IEEE Trans Netw Sci Eng</source>
          <year>2020</year>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>892</fpage>
          <lpage>906</lpage>
          <pub-id pub-id-type="doi">10.1109/tnse.2019.2901716</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref228">
        <label>228</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Privacy‐preserving constrained spectral clustering algorithm for large‐scale data sets</article-title>
          <source>IET Inf Secur</source>
          <year>2020</year>
          <month>05</month>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>321</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.1049/iet-ifs.2019.0255</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref229">
        <label>229</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Miao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Choo</surname>
              <given-names>KR</given-names>
            </name>
          </person-group>
          <article-title>Similarity search for encrypted images in secure cloud computing</article-title>
          <source>IEEE Trans Cloud Comput</source>
          <year>2020</year>
          <month>4</month>
          <day>27</day>
          <fpage>1</fpage>
          <pub-id pub-id-type="doi">10.1109/tcc.2020.2989923</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref230">
        <label>230</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Almutairi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Coenen</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Dures</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Data clustering using homomorphic encryption and secure chain distance matrices</article-title>
          <source>Proceedings of the 10th International Joint Conference on Knowledge Discovery, Knowledge Engineering and Knowledge Management - KDIR</source>
          <year>2018</year>
          <conf-name>10th International Joint Conference on Knowledge Discovery, Knowledge Engineering and Knowledge Management - KDIR</conf-name>
          <conf-date>Sep 18-20, 2018</conf-date>
          <conf-loc>Seville, Spain</conf-loc>
          <pub-id pub-id-type="doi">10.5220/0006890800410050</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref231">
        <label>231</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Almutairi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Coenen</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Dures</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A cryptographic ensemble for secure third party data analysis: collaborative data clustering without data owner participation</article-title>
          <source>Data Knowl Eng</source>
          <year>2020</year>
          <month>03</month>
          <volume>126</volume>
          <fpage>101734</fpage>
          <pub-id pub-id-type="doi">10.1016/j.datak.2019.101734</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref232">
        <label>232</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Chandraker</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>YX</given-names>
            </name>
          </person-group>
          <article-title>Private-kNN: practical differential privacy for computer vision</article-title>
          <source>Proceedings of the 2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2020</year>
          <conf-name>2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 13-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr42600.2020.01187</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref233">
        <label>233</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bian</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hiromoto</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Sato</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>ENSEI: efficient secure inference via frequency-domain homomorphic convolution for privacy-preserving visual recognition</article-title>
          <source>Proceedings of the 2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2020</year>
          <conf-name>2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 13-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr42600.2020.00942</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref234">
        <label>234</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Malhotra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Chhabra</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Vatsa</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>On privacy preserving anonymization of finger-selfies</article-title>
          <source>Proceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition Workshops (CVPRW)</source>
          <year>2020</year>
          <conf-name>IEEE/CVF Conference on Computer Vision and Pattern Recognition Workshops (CVPRW)</conf-name>
          <conf-date>June 14-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvprw50498.2020.00021</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref235">
        <label>235</label>
        <nlm-citation citation-type="web">
          <article-title>mp2893 / medgan</article-title>
          <source>GitHub</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/mp2893/medgan">https://github.com/mp2893/medgan</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref236">
        <label>236</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baowaly</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>KT</given-names>
            </name>
          </person-group>
          <article-title>Synthesizing electronic health records using improved generative adversarial networks</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <month>03</month>
          <day>01</day>
          <volume>26</volume>
          <issue>3</issue>
          <fpage>228</fpage>
          <lpage>41</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/30535151"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy142</pub-id>
          <pub-id pub-id-type="medline">30535151</pub-id>
          <pub-id pub-id-type="pii">5235390</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647178</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref237">
        <label>237</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gulrajani</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Arjovsky</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dumoulin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Courville</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Improved training of wasserstein GANs</article-title>
          <source>Proceedings of the 31st International Conference on Neural Information Processing Systems</source>
          <year>2017</year>
          <conf-name>NIPS'17: 31st International Conference on Neural Information Processing Systems</conf-name>
          <conf-date>Dec 4-9, 2017</conf-date>
          <conf-loc>Long Beach California USA</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref238">
        <label>238</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Tenenholtz</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schwarz</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Senjem</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gunter</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Medical image synthesis for data augmentation and anonymization using generative adversarial networks</article-title>
          <source>Simulation and Synthesis in Medical Imaging</source>
          <year>2018</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref239">
        <label>239</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yoon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Drumright</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>van der Schaar</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Anonymization Through Data Synthesis Using Generative Adversarial Networks (ADS-GAN)</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2020</year>
          <month>08</month>
          <volume>24</volume>
          <issue>8</issue>
          <fpage>2378</fpage>
          <lpage>88</lpage>
          <pub-id pub-id-type="doi">10.1109/JBHI.2020.2980262</pub-id>
          <pub-id pub-id-type="medline">32167919</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref240">
        <label>240</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Beaulieu-Jones</surname>
              <given-names>BK</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>ZS</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Bhavnani</surname>
              <given-names>SP</given-names>
            </name>
            <name name-style="western">
              <surname>Byrd</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Greene</surname>
              <given-names>CS</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving generative deep neural networks support clinical data sharing</article-title>
          <source>Circ Cardiovasc Qual Outcomes</source>
          <year>2019</year>
          <month>07</month>
          <volume>12</volume>
          <issue>7</issue>
          <fpage>e005122</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31284738"/>
          </comment>
          <pub-id pub-id-type="doi">10.1161/CIRCOUTCOMES.118.005122</pub-id>
          <pub-id pub-id-type="medline">31284738</pub-id>
          <pub-id pub-id-type="pmcid">PMC7041894</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref241">
        <label>241</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chin-Cheong</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sutter</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Vogt</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Generation of differentially private heterogeneous electronic health records</article-title>
          <source>arXiv</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2006.03423#:~:text=Generation%20of%20Differentially%20Private%20Heterogeneous%20Electronic%20Health%20Records,-Kieran%20Chin%2DCheong&#38;text=Electronic%20Health%20Records%20(EHRs)%20are,to%20health%20care%20and%20medicine">https://tinyurl.com/j825avzj</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref242">
        <label>242</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jordon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yoon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>van der Schaar</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>PATE-GAN: generating synthetic data with differential privacy guarantees</article-title>
          <source>Proceedings of the International Conference on Learning Representations (2019)</source>
          <year>2019</year>
          <conf-name>International Conference on Learning Representations (2019)</conf-name>
          <conf-date>May 6-9, 2019</conf-date>
          <conf-loc>New Orleans, Louisiana, USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openreview.net/forum?id=S1zk9iRqF7"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref243">
        <label>243</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Differentially private generative adversarial network</article-title>
          <source>arXiv</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1802.06739">https://arxiv.org/abs/1802.06739</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref244">
        <label>244</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>A survey of differentially private generative adversarial networks</article-title>
          <source>Proceedings of the 2020 AAAI Workshop on Privacy-Preserving Artificial Intelligence</source>
          <year>2020</year>
          <conf-name>AAAI Workshop on Privacy-Preserving Artificial Intelligence</conf-name>
          <conf-date>Feb. 7-12, 2020</conf-date>
          <conf-loc>New York USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www2.isye.gatech.edu/~fferdinando3/cfp/PPAI20/papers/paper_9.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref245">
        <label>245</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tseng</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Compressive privacy generative adversarial network</article-title>
          <source>IEEE Trans Inform Forensic Secur</source>
          <year>2020</year>
          <month>1</month>
          <day>20</day>
          <volume>15</volume>
          <fpage>2499</fpage>
          <lpage>513</lpage>
          <pub-id pub-id-type="doi">10.1109/tifs.2020.2968188</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref246">
        <label>246</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maximov</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Elezi</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Leal-Taixe</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>CIAGAN: Conditional Identity Anonymization Generative Adversarial Networks</article-title>
          <source>Proceedings of the 2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</source>
          <year>2020</year>
          <conf-name>2020 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR)</conf-name>
          <conf-date>Jun 13-19, 2020</conf-date>
          <conf-loc>Seattle, WA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cvpr42600.2020.00549</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref247">
        <label>247</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mirza</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Osindero</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Conditional generative adversarial nets</article-title>
          <source>arXiv</source>
          <year>2014</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1411.1784">https://arxiv.org/abs/1411.1784</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref248">
        <label>248</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Microaggregation for database and location privacy</article-title>
          <source>Next Generation Information Technologies and Systems</source>
          <year>2006</year>
          <publisher-loc>Berlin, Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref249">
        <label>249</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fellegi</surname>
              <given-names>IP</given-names>
            </name>
            <name name-style="western">
              <surname>Sunter</surname>
              <given-names>AB</given-names>
            </name>
          </person-group>
          <article-title>A theory for record linkage</article-title>
          <source>J Am Stat Assoc</source>
          <year>1969</year>
          <month>12</month>
          <volume>64</volume>
          <issue>328</issue>
          <fpage>1183</fpage>
          <lpage>210</lpage>
          <pub-id pub-id-type="doi">10.1080/01621459.1969.10501049</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref250">
        <label>250</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A survey of inference control methods for privacy-preserving data mining</article-title>
          <source>Privacy-Preserving Data Mining. Advances in Database Systems</source>
          <year>2008</year>
          <publisher-loc>Boston, MA</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref251">
        <label>251</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Skinner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Holmes</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Estimating the re-identification risk per record in microdata</article-title>
          <source>J Off Stat</source>
          <year>1998</year>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>361</fpage>
          <lpage>72</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref252">
        <label>252</label>
        <nlm-citation citation-type="web">
          <article-title>Documentation</article-title>
          <source>Amnesia</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://amnesia.openaire.eu/about-documentation.html">https://amnesia.openaire.eu/about-documentation.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref253">
        <label>253</label>
        <nlm-citation citation-type="web">
          <article-title>Anonimatron</article-title>
          <source>GitHub</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://realrolfje.github.io/anonimatron/">https://realrolfje.github.io/anonimatron/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref254">
        <label>254</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Prasser</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Kohlmayer</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Putting statistical disclosure control into practice: the ARX data anonymization tool</article-title>
          <source>Medical Data Privacy Handbook</source>
          <year>2015</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref255">
        <label>255</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dankar</surname>
              <given-names>FK</given-names>
            </name>
            <name name-style="western">
              <surname>El Emam</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Neisa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Roffey</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Estimating the re-identification risk of clinical data sets</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2012</year>
          <month>07</month>
          <day>09</day>
          <volume>12</volume>
          <fpage>66</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/1472-6947-12-66"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1472-6947-12-66</pub-id>
          <pub-id pub-id-type="medline">22776564</pub-id>
          <pub-id pub-id-type="pii">1472-6947-12-66</pub-id>
          <pub-id pub-id-type="pmcid">PMC3583146</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref256">
        <label>256</label>
        <nlm-citation citation-type="web">
          <article-title>arx-deidentifier / arx</article-title>
          <source>GitHub</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/arx-deidentifier/arx">https://github.com/arx-deidentifier/arx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref257">
        <label>257</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sánchez</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Martínez</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Soria-Comas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Batet</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>µ -ANT: semantic microaggregation-based anonymization tool</article-title>
          <source>Bioinformatics</source>
          <year>2020</year>
          <month>03</month>
          <day>01</day>
          <volume>36</volume>
          <issue>5</issue>
          <fpage>1652</fpage>
          <lpage>3</lpage>
          <pub-id pub-id-type="doi">10.1093/bioinformatics/btz792</pub-id>
          <pub-id pub-id-type="medline">31621826</pub-id>
          <pub-id pub-id-type="pii">5588845</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref258">
        <label>258</label>
        <nlm-citation citation-type="web">
          <article-title>CrisesUrv / microaggregation-based_anonymization_tool</article-title>
          <source>GitHub</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/CrisesUrv/microaggregation-based_anonymization_tool">https://github.com/CrisesUrv/microaggregation-based_anonymization_tool</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref259">
        <label>259</label>
        <nlm-citation citation-type="web">
          <article-title>Package ‘sdcMicro’</article-title>
          <source>CRAN</source>
          <year>2021</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cran.r-project.org/web/packages/sdcMicro/sdcMicro.pdf">https://cran.r-project.org/web/packages/sdcMicro/sdcMicro.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref260">
        <label>260</label>
        <nlm-citation citation-type="web">
          <article-title>μ-ARGUS home page</article-title>
          <source>Statistical Disclosure Control</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://research.cbs.nl/casc/mu.htm">https://research.cbs.nl/casc/mu.htm</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref261">
        <label>261</label>
        <nlm-citation citation-type="web">
          <article-title>UT Dallas anonymization toolbox</article-title>
          <source>UT Dallas</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://cs.utdallas.edu/dspl/cgi-bin/toolbox/anonManual.pdf">http://cs.utdallas.edu/dspl/cgi-bin/toolbox/anonManual.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref262">
        <label>262</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ghinita</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bertino</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Byun</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>TIAMAT: a tool for interactive analysis of microdata anonymization techniques</article-title>
          <source>Proc VLDB Endow</source>
          <year>2009</year>
          <month>08</month>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>1618</fpage>
          <lpage>21</lpage>
          <pub-id pub-id-type="doi">10.14778/1687553.1687607</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref263">
        <label>263</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Prasser</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Eicher</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Spengler</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Bild</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>Flexible data anonymization using ARX—current status and challenges ahead</article-title>
          <source>Softw Pract Exper</source>
          <year>2020</year>
          <month>02</month>
          <day>25</day>
          <volume>50</volume>
          <issue>7</issue>
          <fpage>1277</fpage>
          <lpage>304</lpage>
          <pub-id pub-id-type="doi">10.1002/spe.2812</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref264">
        <label>264</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Poulis</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Gkoulalas-Divanis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Loukides</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Skiadopoulos</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tryfonopoulos</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>SECRETA: a system for evaluating and comparing relational and transaction anonymization algorithms</article-title>
          <source>Medical Data Privacy Handbook</source>
          <year>2015</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref265">
        <label>265</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gkoulalas-Divanis</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Braghin</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>IPV: a system for identifying privacy vulnerabilities in datasets</article-title>
          <source>IBM J Res Dev</source>
          <year>2016</year>
          <month>7</month>
          <day>27</day>
          <volume>60</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1147/jrd.2016.2576818</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref266">
        <label>266</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Francis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Probst</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Munz</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Diffix: high-utility database anonymization</article-title>
          <source>Privacy Technologies and Policy</source>
          <year>2017</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref267">
        <label>267</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Francis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Probst-Eide</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Obrok</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Berneanu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Juric</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Munz</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Diffix-Birch: extending Diffix-Aspen</article-title>
          <source>arXiv</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1806.02075">https://arxiv.org/abs/1806.02075</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref268">
        <label>268</label>
        <nlm-citation citation-type="web">
          <article-title>Aircloak home page</article-title>
          <source>Aircloak</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aircloak.com/">https://aircloak.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref269">
        <label>269</label>
        <nlm-citation citation-type="web">
          <article-title>NLM-Scrubber downloads</article-title>
          <source>NLM-Scrubber</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://scrubber.nlm.nih.gov/files/">https://scrubber.nlm.nih.gov/files/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref270">
        <label>270</label>
        <nlm-citation citation-type="web">
          <article-title>OpenPseudonymiser home page</article-title>
          <source>OpenPseudonymiser</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.openpseudonymiser.org/About.aspx">https://www.openpseudonymiser.org/About.aspx</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref271">
        <label>271</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vardalachakis</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kondylakis</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Koumakis</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kouroubali</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Katehakis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>ShinyAnonymizer: a tool for anonymizing health data</article-title>
          <source>Proceedings of the 5th International Conference on Information and Communication Technologies for Ageing Well and e-Health - ICT4AWE</source>
          <year>2019</year>
          <conf-name>5th International Conference on Information and Communication Technologies for Ageing Well and e-Health - ICT4AWE,</conf-name>
          <conf-date>May 2-4, 2019</conf-date>
          <conf-loc>Heraklion, Crete, Greece</conf-loc>
          <pub-id pub-id-type="doi">10.5220/0007798603250332</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref272">
        <label>272</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Karwatka</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>GDPR quick wins for software developers and teams</article-title>
          <source>LinkedIn</source>
          <year>2017</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.linkedin.com/pulse/gdpr-quick-wins-software-developers-teams-piotr-karwatka/">https://www.linkedin.com/pulse/gdpr-quick-wins-software-developers-teams-piotr-karwatka/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref273">
        <label>273</label>
        <nlm-citation citation-type="web">
          <article-title>A way to exclude rows matching certain criteria?</article-title>
          <source>GitHub</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/DivanteLtd/anonymizer/issues/4">https://github.com/DivanteLtd/anonymizer/issues/4</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref274">
        <label>274</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Gehrke</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Interactive anonymization of sensitive data</article-title>
          <source>Proceedings of the 2009 ACM SIGMOD International Conference on Management of Data</source>
          <year>2009</year>
          <conf-name>SIGMOD '09: Proceedings of the 2009 ACM SIGMOD International Conference on Management of Data</conf-name>
          <conf-date>Jun 29-Jul 2, 2009</conf-date>
          <conf-loc>Providence Rhode Island USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1559845.1559979</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref275">
        <label>275</label>
        <nlm-citation citation-type="web">
          <article-title>Cornell anonymization toolkit</article-title>
          <source>Source Forge</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://sourceforge.net/projects/anony-toolkit/files/Documents/">https://sourceforge.net/projects/anony-toolkit/files/Documents/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref276">
        <label>276</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Protocols for secure computations</article-title>
          <source>Proceedings of the 23rd IEEE Symposium on Foundations of Computer Science</source>
          <year>1982</year>
          <conf-name>23rd IEEE Symposium on Foundations of Computer Science</conf-name>
          <conf-date>Nov 3-5, 1982</conf-date>
          <conf-loc>San Francisco, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/sfcs.1982.38</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref277">
        <label>277</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Keller</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pastro</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Rotaru</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Overdrive: making SPDZ great again</article-title>
          <source>Advances in Cryptology – EUROCRYPT 2018</source>
          <year>2018</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref278">
        <label>278</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ryffel</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Trask</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dahl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mancuso</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rueckert</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A generic framework for privacy preserving deep learning</article-title>
          <source>CoRR</source>
          <year>2018</year>
          <fpage>4017</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref279">
        <label>279</label>
        <nlm-citation citation-type="web">
          <article-title>Crypten: a research tool for secure machine learning in PyTorc</article-title>
          <source>Crypten</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://crypten.ai">https://crypten.ai</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref280">
        <label>280</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dahl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mancuso</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dupis</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Decoste</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Giraud</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Livingstone</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Patriquin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Uhma</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Private machine learning in TensorFlow using secure computation</article-title>
          <source>Privacy Preserving Machine Learning Workshop</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ppml-workshop.github.io/ppml18/slides/56.pdf">https://ppml-workshop.github.io/ppml18/slides/56.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref281">
        <label>281</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rathee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chandran</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gupta</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rastogi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>CrypTFlow: secure TensorFlow inference</article-title>
          <source>Proceedings of the 2020 IEEE Symposium on Security and Privacy (SP)</source>
          <year>2020</year>
          <conf-name>2020 IEEE Symposium on Security and Privacy (SP)</conf-name>
          <conf-date>May 18-21, 2020</conf-date>
          <conf-loc>San Francisco, CA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/sp40000.2020.00092</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref282">
        <label>282</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Iordanescu</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Karmanov</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Zawaideh</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Using Microsoft AI to build a lung-disease prediction model using chest X-Ray images</article-title>
          <source>Microsoft</source>
          <year>2018</year>
          <access-date>2021-08-31</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://docs.microsoft.com/en-us/archive/blogs/machinelearning/using-microsoft-ai-to-build-a-lung-disease-prediction-model-using-chest-x-ray-images">https://docs.microsoft.com/en-us/archive/blogs/machinelearning/using-microsoft-ai-to-build-a-lung-disease-prediction-model-using-chest-x-ray-images</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref283">
        <label>283</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gulshan</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Coram</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stumpe</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Narayanaswamy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Venugopalan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Widner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Madams</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Cuadros</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Raman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Nelson</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Mega</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Webster</surname>
              <given-names>DR</given-names>
            </name>
          </person-group>
          <article-title>Development and validation of a deep learning algorithm for detection of diabetic retinopathy in retinal fundus photographs</article-title>
          <source>J Am Med Assoc</source>
          <year>2016</year>
          <month>12</month>
          <day>13</day>
          <volume>316</volume>
          <issue>22</issue>
          <fpage>2402</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2016.17216</pub-id>
          <pub-id pub-id-type="medline">27898976</pub-id>
          <pub-id pub-id-type="pii">2588763</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref284">
        <label>284</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Qu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dahl</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving collaborative machine learning on genomic data using TensorFlow</article-title>
          <source>Proceedings of the ACM Turing Celebration Conference - China</source>
          <year>2020</year>
          <conf-name>ACM TURC'20: ACM Turing Celebration Conference - China</conf-name>
          <conf-date>May 22-24, 2020</conf-date>
          <conf-loc>Hefei China</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3393527.3393535</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref285">
        <label>285</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dowlin</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Gilad-Bachrach</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Laine</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lauter</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Naehrig</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wernsing</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>CryptoNets: Applying neural networks to encrypted data with high throughput and accuracy</article-title>
          <source>Proceedings of the International Conference on Machine Learning</source>
          <year>2016</year>
          <conf-name>International Conference on Machine Learning</conf-name>
          <conf-date>June 20-22, 2016</conf-date>
          <conf-loc>New York, USA</conf-loc>
          <fpage>201</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://proceedings.mlr.press/v48/gilad-bachrach16.html"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref286">
        <label>286</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hesamifard</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Takabi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ghasemi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Privacy-preserving machine learning as a service</article-title>
          <source>Proc Priv Enhanc Technol</source>
          <year>2018</year>
          <month>4</month>
          <day>28</day>
          <issue>3</issue>
          <fpage>123</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1515/popets-2018-0024</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref287">
        <label>287</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dathathri</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Saarikivi</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Laine</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lauter</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Maleki</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Musuvathi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mytkowicz</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>CHET: an optimizing compiler for fully-homomorphic neural-network inferencing</article-title>
          <source>Proceedings of the 40th ACM SIGPLAN Conference on Programming Language Design and Implementation</source>
          <year>2019</year>
          <month>6</month>
          <conf-name>PLDI 2019: 40th ACM SIGPLAN Conference on Programming Language Design and Implementation</conf-name>
          <conf-date>Jun 22-26, 2019</conf-date>
          <conf-loc>Phoenix AZ USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3314221.3314628</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref288">
        <label>288</label>
        <nlm-citation citation-type="web">
          <article-title>microsoft / SEAL</article-title>
          <source>GitHub</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://github.com/Microsoft/SEAL">https://github.com/Microsoft/SEAL</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref289">
        <label>289</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cheon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Homomorphic encryption for arithmetic of approximate numbers</article-title>
          <source>Advances in Cryptology – ASIACRYPT 2017</source>
          <year>2017</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref290">
        <label>290</label>
        <nlm-citation citation-type="web">
          <article-title>What is encryption?</article-title>
          <source>Information Commissioner's Office</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/encryption/what-is-encryption/#%233">https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/encryption/what-is-encryption/#%233</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref291">
        <label>291</label>
        <nlm-citation citation-type="web">
          <article-title>Art. 5 GDPR Principles relating to processing of personal data</article-title>
          <source>Intersoft Consulting</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/art-5-gdpr/">https://gdpr-info.eu/art-5-gdpr/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref292">
        <label>292</label>
        <nlm-citation citation-type="web">
          <article-title>Data Protection Act 2018</article-title>
          <source>UK Government Legislation</source>
          <year>2018</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.legislation.gov.uk/ukpga/2018/12/pdfs/ukpga_20180012_en.pdf">https://www.legislation.gov.uk/ukpga/2018/12/pdfs/ukpga_20180012_en.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref293">
        <label>293</label>
        <nlm-citation citation-type="web">
          <article-title>Anonymisation standard for publishing health and social care data</article-title>
          <source>NHS Digital</source>
          <year>2013</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digital.nhs.uk/binaries/content/assets/legacy/pdf/b/o/1523202010spec.pdf">https://digital.nhs.uk/binaries/content/assets/legacy/pdf/b/o/1523202010spec.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref294">
        <label>294</label>
        <nlm-citation citation-type="web">
          <article-title>Confidentiality and disclosure of information policy</article-title>
          <source>National Health Service</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.newhamccg.nhs.uk/Downloads/News-and-Publications/Policies-and-procedures/Confidentiality%20and%20Disclosure%20of%20Information%20Policy.pdf">https://www.newhamccg.nhs.uk/Downloads/News-and-Publications/Policies-and-procedures/Confidentiality%20and%20Disclosure%20of%20Information%20Policy.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref295">
        <label>295</label>
        <nlm-citation citation-type="web">
          <article-title>Pseudonymisation and anonymisation of data - procedure</article-title>
          <source>Tavistock and Portman NHS Foundation Trust</source>
          <year>2019</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tavistockandportman.nhs.uk/documents/1301/pseudomymisation-anonymisation-data-procedure-Jan-19.pdf">https://tavistockandportman.nhs.uk/documents/1301/pseudomymisation-anonymisation-data-procedure-Jan-19.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref296">
        <label>296</label>
        <nlm-citation citation-type="web">
          <article-title>Pseudonymisation policy</article-title>
          <source>Hounslow NHS Clinical Commissioning Group</source>
          <year>2021</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hounslowccg.nhs.uk/media/164202/Pseudonymisation-and-Anonymisation-Policy-v11-Final-05022021.pdf">https://www.hounslowccg.nhs.uk/media/164202/Pseudonymisation-and-Anonymisation-Policy-v11-Final-05022021.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref297">
        <label>297</label>
        <nlm-citation citation-type="web">
          <article-title>Guidance for using patient data</article-title>
          <source>NHS Health Research Authority</source>
          <year>2021</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hra.nhs.uk/covid-19-research/guidance-using-patient-data/">https://www.hra.nhs.uk/covid-19-research/guidance-using-patient-data/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref298">
        <label>298</label>
        <nlm-citation citation-type="web">
          <article-title>Data protection and coronavirus – advice for organisations</article-title>
          <source>Information Commissioner's Office</source>
          <year>2021</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ico.org.uk/global/data-protection-and-coronavirus-information-hub/coronavirus-recovery-data-protection-advice-for-organisations/">https://ico.org.uk/global/data-protection-and-coronavirus-information-hub/coronavirus-recovery-data-protection-advice-for-organisations/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref299">
        <label>299</label>
        <nlm-citation citation-type="web">
          <article-title>Statement by the EDPB Chair on the processing of personal data in the context of the COVID-19 outbreak</article-title>
          <source>European Data Protection Board</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://edpb.europa.eu/news/news/2020/statement-edpb-chair-processing-personal-data-context-covid-19-outbreak_en">https://edpb.europa.eu/news/news/2020/statement-edpb-chair-processing-personal-data-context-covid-19-outbreak_en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref300">
        <label>300</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>da Silva</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>de Sá</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Jossinet</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Classification of breast tissue by electrical impedance spectroscopy</article-title>
          <source>Med Biol Eng Comput</source>
          <year>2000</year>
          <month>1</month>
          <volume>38</volume>
          <issue>1</issue>
          <fpage>26</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1007/bf02344684</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref301">
        <label>301</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Antal</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Hajdu</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>An ensemble-based system for automatic screening of diabetic retinopathy</article-title>
          <source>Knowl Based Syst</source>
          <year>2014</year>
          <month>04</month>
          <volume>60</volume>
          <fpage>20</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.knosys.2013.12.023</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref302">
        <label>302</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zuo</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Naik</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Grooming detection using fuzzy-rough feature selection and text classification</article-title>
          <source>Proceedings of the 2018 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE)</source>
          <year>2018</year>
          <conf-name>2018 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE)</conf-name>
          <conf-date>Jul 8-13, 2018</conf-date>
          <conf-loc>Rio de Janeiro, Brazil</conf-loc>
          <pub-id pub-id-type="doi">10.1109/fuzz-ieee.2018.8491591</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref303">
        <label>303</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zuo</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Naik</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Adaptive activation function generation for artificial neural networks through fuzzy inference with application in grooming text categorisation</article-title>
          <source>Proceedings of the 2019 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE)</source>
          <year>2019</year>
          <conf-name>2019 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE)</conf-name>
          <conf-date>Jun 23-26, 2019</conf-date>
          <conf-loc>New Orleans, LA, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1109/fuzz-ieee.2019.8858838</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref304">
        <label>304</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Domingo-Ferrer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Torra</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>A quantitative comparison of disclosure control methods for microdata</article-title>
          <source>Confidentiality, Disclosure and Data Access: Theory and Practical Applications for Statistical Agencies</source>
          <year>2001</year>
          <publisher-loc>Amsterdam, Netherlands</publisher-loc>
          <publisher-name>Elsevier</publisher-name>
          <fpage>111</fpage>
          <lpage>34</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref305">
        <label>305</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>GT</given-names>
            </name>
            <name name-style="western">
              <surname>Fienberg</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Padman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Roehrig</surname>
              <given-names>SF</given-names>
            </name>
          </person-group>
          <article-title>Disclosure limitation methods and information loss for tabular data</article-title>
          <source>Confidentiality, Disclosure and Data Access: Theory and Practical Applications for Statistical Agencies</source>
          <year>2001</year>
          <publisher-loc>Amsterdam</publisher-loc>
          <publisher-name>Elsevier</publisher-name>
          <fpage>135</fpage>
          <lpage>66</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref306">
        <label>306</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>GT</given-names>
            </name>
            <name name-style="western">
              <surname>Stokes</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>Disclosure risk vs. data utility: the R-U confidentiality map as applied to topcoding</article-title>
          <source>Chance</source>
          <year>2012</year>
          <month>09</month>
          <day>20</day>
          <volume>17</volume>
          <issue>3</issue>
          <fpage>16</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1080/09332480.2004.10554908</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref307">
        <label>307</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Harder</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bauer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Interpretable and differentially private predictions</article-title>
          <source>arXiv</source>
          <year>2020</year>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/1906.02004">https://arxiv.org/abs/1906.02004</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref308">
        <label>308</label>
        <nlm-citation citation-type="web">
          <article-title>Artificial intelligence: how to get it right</article-title>
          <source>National Health Service</source>
          <year>2019</year>
          <month>1</month>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nhsx.nhs.uk/ai-lab/explore-all-resources/understand-ai/artificial-intelligence-how-get-it-right/">https://www.nhsx.nhs.uk/ai-lab/explore-all-resources/understand-ai/artificial-intelligence-how-get-it-right/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref309">
        <label>309</label>
        <nlm-citation citation-type="web">
          <article-title>GDPR right to be informed</article-title>
          <source>Intersoft Consulting</source>
          <access-date>2021-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://gdpr-info.eu/issues/right-to-be-informed/">https://gdpr-info.eu/issues/right-to-be-informed/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
