<?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="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</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">v28i1e99645</article-id>
      <article-id pub-id-type="pmid">42832790</article-id>
      <article-id pub-id-type="doi">10.2196/99645</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Viewpoint</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Viewpoint</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>From Measurement Failure to Privacy Infrastructure: Reframing Contact Tracing Governance for the Next Pandemic</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Balcarras</surname>
            <given-names>Matthew</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Ray Amat</surname>
            <given-names>Kapileshwor</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Liu</surname>
            <given-names>Zhao</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Hu</surname>
            <given-names>Yihan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Fujii</surname>
            <given-names>Yusaku</given-names>
          </name>
          <degrees>Prof Dr</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Gunma University</institution>
            <addr-line>1-5-1 Tenjin-cho</addr-line>
            <addr-line>Kiryu, Gunma, 3768515</addr-line>
            <country>Japan</country>
            <phone>81 277 30 1756</phone>
            <email>fujii@gunma-u.ac.jp</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6440-7358</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Gunma University</institution>
        <addr-line>Kiryu, Gunma</addr-line>
        <country>Japan</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Yusaku Fujii <email>fujii@gunma-u.ac.jp</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>5</day>
        <month>10</month>
        <year>2026</year>
      </pub-date>
      <volume>28</volume>
      <elocation-id>e99645</elocation-id>
      <history>
        <date date-type="received">
          <day>27</day>
          <month>4</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>9</day>
          <month>6</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>19</day>
          <month>6</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>21</day>
          <month>9</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Yusaku Fujii. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 05.10.2026.</copyright-statement>
      <copyright-year>2026</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 the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2026/1/e99645" xlink:type="simple"/>
      <abstract>
        <p>No measurement, no understanding; no understanding, no control: this foundational scientific principle was exposed as a public health dysfunction by the COVID-19 pandemic. Transmission chains spread invisibly, and the contact histories, mobility patterns, and biosignals necessary for control were never systematically collected. Although sensors and digital technologies existed, the fundamental reason measurement failed was the absence of privacy infrastructure that would have enabled people to provide data with confidence. This failure had structural reasons. The object of measurement in infectious disease control is not a physical phenomenon but human beings, and measurement therefore enters the core of privacy: contact histories, social relationships, and bodily states. Because greater precision also deepens privacy intrusion, contact-tracing apps faced 2 failures: privacy-centered designs lost epidemiological utility, while utility-centered designs were rejected through public distrust. Neither achieved sufficient measurement. This Viewpoint reframes the problem. Privacy protection is not a constraint that impedes infectious disease control but the enabling condition upon which effective measurement depends. Existing regulations and technical methods have not been designed from this premise and have therefore failed to break the cycle of structural distrust. As an institutional approach to filling this gap, we present VRAIO (verifiable record of AI output), which integrates democratic rule-setting, metadata declaration, third-party verification, tamper-proof ledgers, and violation-deterrence incentives. Once privacy infrastructure is established, this foundational principle can operate freely in infectious disease control for the first time. It will enable high-resolution epidemiology and precision intervention, opening a new path for public health that reconciles infection control with individual autonomy and social freedom without relying on blanket social shutdowns.</p>
      </abstract>
      <kwd-group>
        <kwd>no measurement, no control</kwd>
        <kwd>infectious disease control</kwd>
        <kwd>privacy infrastructure</kwd>
        <kwd>measurement failure</kwd>
        <kwd>contact tracing</kwd>
        <kwd>verifiable record of AI output</kwd>
        <kwd>VRAIO</kwd>
        <kwd>contextual integrity</kwd>
        <kwd>public health surveillance</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec>
      <title>Introduction: No Measurement, No Understanding, No Control</title>
      <p>No measurement, no understanding. No understanding, no control. This is a foundational principle running through natural science and scientific technology. From classical mechanics to contemporary AI, this chain admits no exception; it applies equally to infectious disease control.</p>
      <p>The COVID-19 pandemic showed how this principle can fail in public health. Contact histories, mobility patterns, and biosignals necessary for control were not systematically collected, and authorities were trying to control a system they could not see. Before the Wuhan mobility restrictions, approximately 86% of all infections were estimated to have spread undocumented, and 79% of documented cases were attributed to these invisible transmission chains [<xref ref-type="bibr" rid="ref1">1</xref>]. It has also been shown that surveillance recorded deaths while systematically underestimating the true scale of infection [<xref ref-type="bibr" rid="ref2">2</xref>]. At its core, COVID-19 was a “measurement failure.”</p>
      <p>However, this was not a failure of technology. Sensors, algorithms, and communications infrastructure existed; contact-tracing apps were deployed in many countries; and new data streams were available [<xref ref-type="bibr" rid="ref3">3</xref>]. UK data showed that each 1-percentage-point increase in app adoption reduced infections by approximately 0.8% to 2.3% [<xref ref-type="bibr" rid="ref4">4</xref>]. What failed was not the availability of measurement tools but the prerequisite that would make measurement acceptable to citizens: privacy protection.</p>
      <p>This Viewpoint argues that privacy infrastructure is not a secondary issue attached to epidemiological architecture but the foundational condition for effective measurement and control. The Viewpoint first explains why infectious disease measurement overlaps with privacy, then analyze 2 patterns of failure in contact tracing, present institutional redesign through VRAIO (verifiable record of AI output), and finally discuss the future of infectious disease science once the barriers to measurement are removed.</p>
    </sec>
    <sec>
      <title>Why Infectious Disease Measurement Is a Privacy Problem</title>
      <p>The object of measurement in infectious disease control is not a physical phenomenon but human beings, and measurement therefore inevitably enters the core of privacy. Unlike monitoring bridge deterioration or the weather, infectious disease transmission measurement handles behavioral records: who was where, when, and in contact with whom. It discloses social relationships and directly implicates informational self-determination. Moreover, collecting heart rate, body temperature, blood oxygen levels, and similar data through wearables extends measurement into the domain of bodily integrity. The very fact that personally identifiable information, location data, and vaccination records had to be shared with authorities impeded the adoption of contact-tracing apps [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
      <p>This problem is not confined to contact tracing. The moment measurement reaches the body or behavior of an individual, it becomes social measurement. Although this Viewpoint focuses on contact tracing, its thesis—no legitimate social measurement without trust infrastructure—extends to social measurement involving privacy in general.</p>
      <p>This point is captured by the concept of contextual integrity. As Nissenbaum [<xref ref-type="bibr" rid="ref6">6</xref>] argues, the appropriateness of information flow is determined by the norms of the social context in which the information is generated. The contact, behavioral, and biometric data used in infectious disease measurement are generated in health care and public health contexts; diversion to commercial, law enforcement, or surveillance purposes is a privacy violation even if technically feasible [<xref ref-type="bibr" rid="ref7">7</xref>]. Resistance to contact-tracing apps was inseparable from distrust that data provided for epidemic control might be repurposed. Infectious disease measurement is therefore a political and ethical undertaking that asks not only whether measurement is possible but also whether it is permissible [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
      <p>Here lies a structural asymmetry. In engineering measurement, improved precision is welcomed; in infectious disease measurement, greater precision, granularity, and coverage also deepen privacy intrusion. A structure that mobilizes individual informational sovereignty as a means of infection prevention cannot be resolved by technical ingenuity alone. The World Health Organization (WHO) has also recognized that improving measurement systems for future threats requires trust and cooperation with society [<xref ref-type="bibr" rid="ref9">9</xref>].</p>
      <p>Therefore, a privacy-protection foundation must be built as social and technical infrastructure beyond individual technical improvements and legal rules. Sufficient measurement cannot be achieved without an institutional structure in which each person can concretely trust how their data will be handled. Official assessments share the view that almost every country’s surveillance system has vulnerabilities and that “bold changes” are necessary [<xref ref-type="bibr" rid="ref10">10</xref>]. However, the debate remains skewed toward measurement infrastructure, while the privacy-protection foundation that would make implementation socially possible has not been systematically addressed.</p>
    </sec>
    <sec>
      <title>Two Patterns of Failure: COVID-19 Contact-Tracing Apps as a Case Study</title>
      <p>Contact-tracing apps during the COVID-19 pandemic were a case in which the tension between measurement and privacy became acute. They were deployed in many countries but failed to fulfill their expected role. A prospective evaluation of Australia’s COVIDSafe app found that contacts additionally detected by the app amounted to less than 0.1% of those not identified by conventional tracing, and no significant contribution to the 6-month response was observed [<xref ref-type="bibr" rid="ref11">11</xref>]. This was not the failure of a particular country or design decision but a structural failure.</p>
      <p>That structure is the trade-off between privacy and data utility [<xref ref-type="bibr" rid="ref12">12</xref>]. Policymakers are drawn in 1 of 2 directions: prioritizing privacy and losing utility, or prioritizing utility and being rejected through public distrust. Either way, sufficient data are not collected, and control is not achieved.</p>
      <p>The first pattern is loss of utility through privacy prioritization. The Google Apple Exposure Notification (GAEN) framework collected no location data; only anonymous encrypted identifiers were exchanged between devices, and infection determination was completed on the device. It was strong in terms of privacy protection but could not obtain epidemiologically important information such as place, movement route, and contact context, making secondary contact tracing and identification of superspreader events difficult. As Meijerink et al [<xref ref-type="bibr" rid="ref13">13</xref>] note, decentralized apps collect no data, making epidemiological evaluation itself difficult. Norway’s Smittestopp version 1 was suspended because of privacy concerns, and version 2 shifted to a GAEN-type design, but epidemiological analytical capability was substantially lost as a result [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
      <p>The second pattern is public distrust caused by insufficient privacy consideration. A national Australian survey found that privacy concerns were the most common reason for nonadoption of COVIDSafe (25%) [<xref ref-type="bibr" rid="ref14">14</xref>]. Another study similarly identified privacy concerns as the leading reason for nonadoption (31%), followed by distrust of government (18%) [<xref ref-type="bibr" rid="ref15">15</xref>]. Ho et al [<xref ref-type="bibr" rid="ref5">5</xref>] showed a mechanism in which concerns about sharing personally identifiable information, location data, and vaccination records, together with government distrust, impeded adoption. In Singapore, the adoption of TraceTogether increased from 38.4% under voluntary uptake to 85.1% following coercive intervention; however, the coercive measures themselves led to a further loss of trust [<xref ref-type="bibr" rid="ref16">16</xref>]. Even when technical privacy design is appropriate, the subjective distrust that “the government wants to track me” may remain [<xref ref-type="bibr" rid="ref17">17</xref>]. Distrust is a barrier that fundamentally governs technical effectiveness [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
      <p>Common to both patterns is the fact that the privacy problem cannot be solved by technical improvement alone. Bluetooth ranging accuracy, battery consumption, and the digital divide are subjects for engineering improvement. Privacy, however, requires institutional design, democratic legitimacy, and sustained legal infrastructure.</p>
      <p>The failure of contact tracing cannot be attributed solely to privacy concerns. Privacy concerns repeatedly rank high among reasons for nonadoption [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>], but distrust of government, doubts about usefulness, disparities in smartphone penetration and literacy, and constraints in the public health system also acted independently [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. Infectious disease measurement also consists of multiple data streams—contact apps, clinical records, syndromic surveillance, mobility data, and wastewater epidemiology—all of which directly involve privacy and require trust infrastructure for integration [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. This Viewpoint focuses on privacy infrastructure not because it is the sole cause but because it is a common necessary condition.</p>
      <p>Here lies a vicious cycle. If privacy protection is incomplete, distrust persists; if distrust persists, adoption cannot exceed the effective threshold; if uptake is insufficient, utility is not demonstrated; and if utility is not demonstrated, investment in institutional infrastructure is not prioritized. As Bengio et al [<xref ref-type="bibr" rid="ref19">19</xref>] warned, without appropriate attention to privacy, public trust cannot be obtained, and without trust, broad uptake cannot be achieved. However, this warning has not been sufficiently translated into substantive investment in institutional infrastructure.</p>
    </sec>
    <sec>
      <title>Reframing the Problem: Privacy Protection as the Core</title>
      <sec>
        <title>Existing Approaches and Their Limitations</title>
        <p>Efforts to protect privacy have progressed on both social and technical fronts. On the social side, frameworks such as the European Union (EU) General Data Protection Regulation (GDPR) [<xref ref-type="bibr" rid="ref20">20</xref>], EU AI Act [<xref ref-type="bibr" rid="ref21">21</xref>], Digital Services Act [<xref ref-type="bibr" rid="ref22">22</xref>], and the US Children's Online Privacy Protection Act [<xref ref-type="bibr" rid="ref23">23</xref>] have normatively established purpose limitation, consent, data subject rights, and transparency. Legal demands for privacy protection in health information have also continued to grow [<xref ref-type="bibr" rid="ref24">24</xref>]. However, these frameworks mainly declare what must not be done; they do not constitute social infrastructure for continuous and verifiable enforcement of violations.</p>
        <p>On the technical side, differential privacy [<xref ref-type="bibr" rid="ref25">25</xref>], decentralized architectures, anonymization and pseudonymization, federated learning, and encrypted communications have been implemented [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. GAEN-type decentralized design is one example. However, the preceding analysis of contact-tracing apps shows that decentralized design does not fundamentally resolve the trade-off between privacy protection and data utility, and it makes epidemiologically necessary information difficult to obtain [<xref ref-type="bibr" rid="ref12">12</xref>]. More generally, risks of information reconstruction through AI inference remain [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>], and the black box nature of machine learning models obstructs accountability for internal processes [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. Technical improvements can make risks manageable but cannot remove the barriers to measurement in principle.</p>
        <p>Both social and technical approaches are indispensable, but neither is sufficient alone (necessary but insufficient). Their common gap is an institutional foundation that addresses the structural problem: without appropriate attention to privacy, neither trust nor broad participation can be obtained [<xref ref-type="bibr" rid="ref19">19</xref>]. The fact that nontechnical considerations govern technical effectiveness has not been sufficiently institutionalized [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p>
        <p>The point to reconsider is that privacy protection is not a constraint that impedes infectious disease control. As McGraw et al [<xref ref-type="bibr" rid="ref24">24</xref>] argue, privacy protection is an enabler: people participate in health information sharing precisely when trust is established. The trade-off between privacy and utility is a limitation of current technologies and institutions, not a principled limit.</p>
        <p>The problem to be solved is the institutional establishment of a privacy-protection foundation at the scale of social infrastructure: a structure in which each person can concretely trust how their data will be handled.</p>
        <p>Such a structure requires 3 conditions. First, permitted and prohibited outputs must be transparent and predictable to citizens. Second, commitments must be continuously verifiable in real time rather than checked only after the fact. Third, the incentive structure must make violation an irrational choice in advance. Existing regulations and technical methods do not satisfy these 3 conditions simultaneously.</p>
        <p>VRAIO is one concrete proposal in this direction [<xref ref-type="bibr" rid="ref31">31</xref>]. It was originally proposed for AI-connected cameras in public spaces, but its core idea—ex ante control of output—can also be applied to personal data in infectious disease measurement. In both cases, the essence of the problem is whether citizens can trust what their data will be used for.</p>
        <p>The point of governance in VRAIO is concentrated not inside the AI system but at output. The data analyzer may handle full-resolution data inside the outbound firewall, but VRAIO governs only the moment when analytical results cross the boundary toward external receivers. Requests themselves are not governed. Even if an output candidate is generated from a nonconforming request, it fails recorder verification, is blocked by the valve, and does not become output. The rules distinguish permitted purpose and content by destination, such as the individual and public health authority (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Receiver-specific rules in contact tracing.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="240"/>
            <col width="230"/>
            <col width="530"/>
            <thead>
              <tr valign="top">
                <td>Receivers</td>
                <td>Permitted purposes</td>
                <td>Permitted content and granularity</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>General public (including citizens, employers, and insurers)</td>
                <td>Situational awareness and risk avoidance</td>
                <td>Population-level, nonidentifying information only (eg, regional spread status and high-risk area alerts)</td>
              </tr>
              <tr valign="top">
                <td>Individuals (data subjects)</td>
                <td>Awareness of one’s own exposure or status</td>
                <td>Full-resolution information about oneself, accessible only to the individual concerned</td>
              </tr>
              <tr valign="top">
                <td>Public health planners</td>
                <td>Cluster detection, epidemic modeling, and resource allocation</td>
                <td>Pseudonymized, aggregated cluster or mesh-level information and no individual-identifying granularity to third parties</td>
              </tr>
              <tr valign="top">
                <td>Enforcement or notification bodies</td>
                <td>Issuing exposure notifications</td>
                <td>Only the minimum information necessary for notification, with no broader behavioral history</td>
              </tr>
              <tr valign="top">
                <td>Health care institutions</td>
                <td>Treatment of the specific patient</td>
                <td>Only the data of the patient under that institution’s care</td>
              </tr>
              <tr valign="top">
                <td>Research institutions</td>
                <td>Analysis, modeling, and simulation</td>
                <td>May drive repeated analysis on the inside-boundary data analyzer and only nonidentifying products (model parameters, aggregate or differentially private statistics, and simulation results) leave the boundary</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>VRAIO in Operation: 5 Layers Centered on Output Governance</title>
        <sec>
          <title>Overview</title>
          <p>The design principle of VRAIO is concentrated at a single point: what ultimately affects society is the output of the AI system. VRAIO therefore makes output the primary object of governance. If output can be limited to the purposes and content democratically permitted by society, social accountability can be established without fully elucidating the interior of the data analyzer. The following 5 layers support this point (<xref rid="figure1" ref-type="fig">Figure 1</xref>): democratic rule-setting (rules), metadata declaration, formal verification by the recorder, full recording in a tamper-proof ledger, and ex ante destruction of misuse through incentives. However, even if output is governed, the fact that the AI system “knows” the data remains. VRAIO is not a universal remedy but a realistic step toward addressing the greatest barrier.</p>
          <p>In a transitional period where social trust remains insufficient, input-stage regulation and approaches oriented toward value formation inside AI [<xref ref-type="bibr" rid="ref32">32</xref>] may also be useful complements. VRAIO centers governance on outputs not to exclude them but because it has the practical advantage of establishing accountability without waiting for the interior to be clarified.</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Structure and operation of VRAIO (verifiable record of AI output) applied to contact tracing. The data analyzer is located inside the outbound firewall boundary; any information released across that boundary, including analytical results, is treated as “output” and governed by VRAIO.</p>
            </caption>
            <graphic xlink:href="jmir_v28i1e99645_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Democratic Rule-Setting (Rules)</title>
          <p>Permitted and prohibited outputs are defined at the level of legislation through democratic processes by the legislature and regulatory authorities. The rules translate obligations under instruments such as the GDPR [<xref ref-type="bibr" rid="ref20">20</xref>] into machine-readable schemas—field definitions, value domains, and logical conditions for metadata—and are made public, including to operators and the recorder. The essence is to distinguish the purpose and content of output by receiver. The legitimacy of the same information varies with its destination [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. For example, population-level infection status and high-risk area information may be provided broadly at nonidentifying granularity. An individual’s own exposure status may be disclosed to that individual at full resolution, while public health authorities receive only pseudonymized or aggregated information; third-party provision at individual-identifying granularity is not permitted. The correspondence is shown in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        </sec>
        <sec>
          <title>Metadata Declaration</title>
          <p>For every output candidate, the data-processing system attaches structured metadata indicating “purpose, content, and receiver”; sends it to the recorder; and receives a determination on whether the output may be released.</p>
        </sec>
        <sec>
          <title>Formal Verification by the Recorder</title>
          <p>The independent third-party recorder does not touch the output content itself; it verifies only whether the declaration formally conforms to the rules. Output that does not pass through the recorder is physically impossible through the outbound firewall (<xref rid="figure1" ref-type="fig">Figure 1</xref>), and only conforming output passes the valve. The recorder is independent of operators and regulatory authorities and holds no decryption keys; therefore, it cannot access the content. This design avoids the need to elucidate the black box [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>] or address the epistemological limitations of internal regulation approaches [<xref ref-type="bibr" rid="ref33">33</xref>]. Requests are not objects of governance; the governance point is unified at the output stage. The recorder’s own independence is supported by ledger transparency and external audit.</p>
        </sec>
        <sec>
          <title>Full Recording in a Tamper-Proof Ledger</title>
          <p>The declaration, verification result, and determination process are irreversibly recorded in a distributed ledger (the blockchain network in <xref rid="figure1" ref-type="fig">Figure 1</xref>). A record infrastructure accessible to audit bodies, independent investigators, researchers, and citizens enables multilayered verification, including verification of the recorder itself.</p>
        </sec>
        <sec>
          <title>Ex Ante Destruction of Misuse Through Incentives</title>
          <p>A false declaration—submitting metadata that differs from the actual output—leaves a trace in the ledger and is therefore easy to discover after the fact, triggering sanctions at a level that threatens the survival of the operating entity. Privacy-preserving spot audits reinforce this (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The essence of VRAIO is not to “monitor and catch” but to provide infrastructure that “makes violation an irrational choice in advance” [<xref ref-type="bibr" rid="ref18">18</xref>]. Trust cannot be obtained through technical design alone [<xref ref-type="bibr" rid="ref17">17</xref>]; institutional structure complements it.</p>
          <p>VRAIO governs the output stage and does not replace privacy-preserving technologies at the collection stage. Differential privacy [<xref ref-type="bibr" rid="ref25">25</xref>], federated learning [<xref ref-type="bibr" rid="ref26">26</xref>], and GAEN-type decentralized design [<xref ref-type="bibr" rid="ref13">13</xref>] complement VRAIO as means of determining output granularity and lowering reidentification risk. VRAIO realizes its value when a verifiable output-governance layer is superimposed on these methods.</p>
          <p>The primary aim of VRAIO is not to restrict outputs but to enable analysis, model building, and simulation using full-resolution data within the data analyzer (<xref rid="figure1" ref-type="fig">Figure 1</xref>), while releasing only nonidentifying models and aggregate results at a granularity appropriate to each recipient. This enables characterization of infection status; higher-fidelity infection models; and more localized, individualized, and efficient countermeasures while preserving privacy. The purposes and permitted granularities for each receiver are summarized in <xref ref-type="table" rid="table1">Table 1</xref>.</p>
        </sec>
      </sec>
      <sec>
        <title>Integrative Significance as Privacy-Protection Infrastructure</title>
        <p>VRAIO does not replace existing social or technical approaches; it functions as infrastructure that connects them. If rule conformity by output destination is verifiably guaranteed, the collection and computation methods inside the boundary can be selected according to the application. Federated analytics analyzes without aggregating data; secure multiparty computation [<xref ref-type="bibr" rid="ref34">34</xref>] obtains statistics without disclosing raw data; and trusted research environments [<xref ref-type="bibr" rid="ref35">35</xref>] allow researchers to analyze full-resolution data within controlled areas and carry out only aggregate results. All of these approaches can be incorporated inside the VRAIO boundary. The GDPR’s purpose limitation principle [<xref ref-type="bibr" rid="ref20">20</xref>], differential privacy [<xref ref-type="bibr" rid="ref25">25</xref>], and algorithm auditing [<xref ref-type="bibr" rid="ref33">33</xref>] also mutually reinforce one another on VRAIO’s verification and enforcement layer. VRAIO is a common layer that guarantees that whatever method is used, the product released to the outside is legitimate.</p>
        <p>Trust infrastructure is a necessary condition for infectious disease measurement. Cryptography, distributed ledgers, privacy engineering, and legal-institutional design are all indispensable, but none alone constitutes infrastructure. What is needed is an integrated function that brings them together, verifiably enforces conformity to receiver-specific rules, and deters violations. To the best of our knowledge, VRAIO is currently the only proposal that concretizes this integration as an institutional design. The claim of this Viewpoint, however, is not that VRAIO is the only answer but that research and development should be directed toward integrated infrastructure rather than the mere accumulation of individual technologies.</p>
        <p>Some issues remain beyond the scope of this Viewpoint. First is the trustworthiness of the recorder. VRAIO presupposes an independent third-party institution, and its appointment, supervision, and separation of powers belong to the design of audit systems and regulatory institutions. What VRAIO adds is that the recorder’s determinations themselves are recorded in a ledger and made subject to independent verification, as described above. Second, the legal basis for sanctions is left to national legislation, but VRAIO provides an evidentiary foundation: false declarations remain as tamper-proof records. Third, cross-border measurement requires national laws and international coordination. Provision to foreign receivers is also treated as destination-specific output and permitted only within the scope allowed by each country’s law (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <p>What, then, becomes possible when the door of privacy protection is opened? This question leads directly to the broader implications of privacy protection for infectious disease science.</p>
      </sec>
    </sec>
    <sec>
      <title>Privacy Protection as the “Door to the Next Stage”</title>
      <p>The establishment of privacy protection is not the end point of infectious disease control but the entrance to the next stage.</p>
      <sec>
        <title>From “Constraint” to “Capability-Enabling Condition”</title>
        <p>In public health, privacy protection is often regarded as a constraint that impedes stronger infection control. However, as COVID-19 showed, the main cause of measurement failure was not the absence of technology but the absence of an institutional foundation that allowed people to participate with confidence. The question is not “what must be sacrificed to protect privacy” but “what becomes possible precisely because privacy can be protected.”</p>
      </sec>
      <sec>
        <title>The Horizon of Liberated Measurement</title>
        <p>If the door of privacy protection opens, many measurement technologies can move toward social implementation. Contact-tracing apps are the paradigmatic case: they deliver sufficient epidemiological value only when adoption exceeds a certain level [<xref ref-type="bibr" rid="ref36">36</xref>]. The same logic extends to functional expansion. PAPR for Everyone [<xref ref-type="bibr" rid="ref37">37</xref>], which deploys powered air-purifying respirators as a third axis against airborne infectious disease, and PWS-NET [<xref ref-type="bibr" rid="ref38">38</xref>], which records wearing status at social scale, measure “compliance with protective behavior.” A powered air-purifying respirator equipped with a differential-pressure sensor can continuously estimate respiratory flow [<xref ref-type="bibr" rid="ref39">39</xref>], opening a path to continuous measurement of respiratory state. Digital phenotyping may detect presymptomatic changes [<xref ref-type="bibr" rid="ref40">40</xref>]. Long-term accumulation of routine testing records also depends on voluntary participation once concerns over discrimination and employment disadvantage are removed. Contact, mobility, testing, and biosignal data, when safely linked, can provide high-resolution understanding of the relationship among exposure, infection, and onset. The greatest bottleneck is not technological insufficiency but the absence of trust in privacy protection [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
      </sec>
      <sec>
        <title>High-Resolution Epidemiology and the Self-Reinforcing Loop</title>
        <p>If these data are safely integrated, the resolution of epidemiology changes qualitatively. Beyond conventional spatiotemporal characterization, next-generation measurement may quantitatively explain the conditions under which infection occurs. If risk characterization moves from coarse categories to precise understanding, countermeasures can evolve from uniform implementation to local and selective concentration of resources on high-impact interventions [<xref ref-type="bibr" rid="ref41">41</xref>]. Better measurement deepens understanding, understanding produces appropriate control, and verification of effects justifies further investment in measurement. When this virtuous cycle is established, infection control becomes an adaptive learning system that links measurement, modeling, localized intervention, and immediate verification. Higher resolution is not an intensification of surveillance but a condition for avoiding unnecessarily broad blanket restrictions.</p>
        <p>This virtuous cycle, however, has prerequisites. Measurement failure does not simply mean that no measurement was performed. During the pandemic, reported values were often treated at face value without evaluating temporal biases such as reporting delays, revisions, and backfills, creating the risk that apparent decreases would be mistaken for convergence. To obtain reliable epidemiological signals from heterogeneous surveillance systems, systematic biases must be separated from random variation, and measurements must be handled correctly [<xref ref-type="bibr" rid="ref42">42</xref>]. For AI output as well, retrieval-grounded evaluation has been presented as a direction for making factuality auditable, supporting the verifiability of VRAIO at the output stage [<xref ref-type="bibr" rid="ref43">43</xref>].</p>
      </sec>
      <sec>
        <title>Remaining Limitations</title>
        <p>Nevertheless, VRAIO-type infrastructure does not completely eliminate the trade-off between privacy and utility. The first challenge is implementation cost. Recorder verification, firewall blocking, and spot audits all become more costly as completeness is pursued; VRAIO therefore adopts probabilistic ex post deterrence rather than full inspection. The second challenge is more fundamental: the legitimacy of output depends on the definition of permitted purpose, but society cannot specify this with perfect precision. Rules are not a one-time completed product; they should be updated as social consensus evolves. What VRAIO guarantees is verifiable conformity to given rules, not the correctness of the rules themselves. Uneven digital access and uneven institutional trust are also matters that the rules must address.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The principle “no measurement, no understanding; no understanding, no control” has not been adequately realized in public health. The COVID-19 pandemic demonstrated the consequences of this failure on a devastating scale. However, the root cause was not a lack of technology but the failure to institutionalize the prerequisite for measurement: social trust in privacy protection.</p>
        <p>This recognition reverses the structure of the problem. Privacy protection is not a constraint on infectious disease control but a capability-enabling condition that makes effective measurement socially possible. Unless this shift is accepted, structural barriers to measurement will remain even if more refined sensors and stricter legal regulations are developed.</p>
        <p>The question to solve is clear: can society build, at infrastructure scale, an institutional structure in which citizens can concretely trust how their data will be handled? VRAIO infrastructure is one response to that question, but not the only one. What matters is that research and development in this direction begin before the next pandemic.</p>
        <p>If privacy infrastructure is established, the trade-off between stronger surveillance and the loss of freedom can be resolved for the first time on a common foundation that supports both. “No measurement, no understanding; no understanding, no control”: the day this principle begins to operate fully in infectious disease control is within reach, not as a technological matter, but as an institutional one.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">EU</term>
          <def>
            <p>European Union</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">GAEN</term>
          <def>
            <p>Google Apple Exposure Notification</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">GDPR</term>
          <def>
            <p>General Data Protection Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">VRAIO</term>
          <def>
            <p>verifiable record of AI output</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">WHO</term>
          <def>
            <p>World Health Organization</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The author would like to thank colleagues and collaborators who provided valuable discussion during the development of this work. The author used generative AI assistants, including Anthropic Claude, to support the literature search, review of the argument, language refinement, and English translation of the manuscript. AI tools were not used to generate research data, analyses, or scientific conclusions. The author reviewed and verified all content and takes full responsibility for the integrity and accuracy of the final manuscript.</p>
    </ack>
    <notes>
      <sec>
        <title>Funding</title>
        <p>This work was supported by the Japan Society for the Promotion of Science KAKENHI (grant 25K00735).</p>
      </sec>
    </notes>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>Data sharing is not applicable to this article as no datasets were generated or analyzed during this study.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="conflict">
        <p>YF proposes the VRAIO (verifiable record of AI output) and powered air-purifying respirator frameworks discussed in this manuscript and holds related patents. No commercial or financial conflicts of interest are 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>Li</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pei</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Shaman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Substantial undocumented infection facilitates the rapid dissemination of novel coronavirus (SARS-CoV-2)</article-title>
          <source>Science</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <volume>368</volume>
          <issue>6490</issue>
          <fpage>489</fpage>
          <lpage>93</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.science.org/doi/10.1126/science.abb3221?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1126/science.abb3221</pub-id>
          <pub-id pub-id-type="medline">32179701</pub-id>
          <pub-id pub-id-type="pii">science.abb3221</pub-id>
          <pub-id pub-id-type="pmcid">PMC7164387</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alwan</surname>
              <given-names>NA</given-names>
            </name>
          </person-group>
          <article-title>Surveillance is underestimating the burden of the COVID-19 pandemic</article-title>
          <source>Lancet</source>
          <year>2020</year>
          <month>09</month>
          <day>05</day>
          <volume>396</volume>
          <issue>10252</issue>
          <fpage>e24</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32861312"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(20)31823-7</pub-id>
          <pub-id pub-id-type="medline">32861312</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(20)31823-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC7836224</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>Buckee</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Improving epidemic surveillance and response: big data is dead, long live big data</article-title>
          <source>Lancet Digit Health</source>
          <year>2020</year>
          <month>05</month>
          <volume>2</volume>
          <issue>5</issue>
          <fpage>e218</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(20)30059-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(20)30059-5</pub-id>
          <pub-id pub-id-type="medline">32518898</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(20)30059-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7270775</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>Wymant</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ferretti</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tsallis</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Charalambides</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abeler-Dörner</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bonsall</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hinch</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kendall</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Milsom</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ayres</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Holmes</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Briers</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Fraser</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>The epidemiological impact of the NHS COVID-19 app</article-title>
          <source>Nature</source>
          <year>2021</year>
          <month>06</month>
          <volume>594</volume>
          <issue>7863</issue>
          <fpage>408</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1038/s41586-021-03606-z</pub-id>
          <pub-id pub-id-type="medline">33979832</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-021-03606-z</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>Ho</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Chiu</surname>
              <given-names>DK</given-names>
            </name>
            <name name-style="western">
              <surname>Sayama</surname>
              <given-names>KL</given-names>
            </name>
          </person-group>
          <article-title>When privacy, distrust, and misinformation cause worry about using COVID-19 contact-tracing apps</article-title>
          <source>IEEE Internet Comput</source>
          <year>2023</year>
          <volume>27</volume>
          <issue>2</issue>
          <fpage>7</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1109/MIC.2022.3225568</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nissenbaum</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Privacy as contextual integrity</article-title>
          <source>Wash Law Rev</source>
          <year>2004</year>
          <volume>79</volume>
          <issue>1</issue>
          <fpage>119</fpage>
          <lpage>57</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://digitalcommons.law.uw.edu/wlr/vol79/iss1/10"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vitak</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zimmer</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>More than just privacy: using contextual integrity to evaluate the long-term risks from COVID-19 surveillance technologies</article-title>
          <source>Soc Media Soc</source>
          <year>2020</year>
          <month>07</month>
          <day>30</day>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>2056305120948250</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/2056305120948250?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/2056305120948250</pub-id>
          <pub-id pub-id-type="medline">34192036</pub-id>
          <pub-id pub-id-type="pii">10.1177_2056305120948250</pub-id>
          <pub-id pub-id-type="pmcid">PMC7399567</pub-id>
        </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>Budd</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Manning</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Lampos</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Zhuang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Edelstein</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rees</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Emery</surname>
              <given-names>VC</given-names>
            </name>
            <name name-style="western">
              <surname>Stevens</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Keegan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Short</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Pillay</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Manley</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Cox</surname>
              <given-names>IJ</given-names>
            </name>
            <name name-style="western">
              <surname>Heymann</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>McKendry</surname>
              <given-names>RA</given-names>
            </name>
          </person-group>
          <article-title>Digital technologies in the public-health response to COVID-19</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>08</month>
          <volume>26</volume>
          <issue>8</issue>
          <fpage>1183</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1038/s41591-020-1011-4</pub-id>
          <pub-id pub-id-type="medline">32770165</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-020-1011-4</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>Morgan</surname>
              <given-names>OW</given-names>
            </name>
            <name name-style="western">
              <surname>Abdelmalik</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Perez-Gutierrez</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Fall</surname>
              <given-names>IS</given-names>
            </name>
            <name name-style="western">
              <surname>Kato</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hamblion</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Matsui</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Nabeth</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Pebody</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pukkila</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stephan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ihekweazu</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>How better pandemic and epidemic intelligence will prepare the world for future threats</article-title>
          <source>Nat Med</source>
          <year>2022</year>
          <month>08</month>
          <volume>28</volume>
          <issue>8</issue>
          <fpage>1526</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35764683"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-022-01900-5</pub-id>
          <pub-id pub-id-type="medline">35764683</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-022-01900-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC9243925</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>Morgan</surname>
              <given-names>OW</given-names>
            </name>
            <name name-style="western">
              <surname>Aguilera</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Ammon</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Amuasi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fall</surname>
              <given-names>IS</given-names>
            </name>
            <name name-style="western">
              <surname>Frieden</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Heymann</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ihekweazu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jeong</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Leung</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Mahon</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Nkengasong</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Qamar</surname>
              <given-names>FN</given-names>
            </name>
            <name name-style="western">
              <surname>Schuchat</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wieler</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Dowell</surname>
              <given-names>SF</given-names>
            </name>
          </person-group>
          <article-title>Disease surveillance for the COVID-19 era: time for bold changes</article-title>
          <source>Lancet</source>
          <year>2021</year>
          <month>06</month>
          <day>19</day>
          <volume>397</volume>
          <issue>10292</issue>
          <fpage>2317</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34000258"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(21)01096-5</pub-id>
          <pub-id pub-id-type="medline">34000258</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(21)01096-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC8121493</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>Vogt</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Haire</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Selvey</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Katelaris</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Kaldor</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Effectiveness evaluation of digital contact tracing for COVID-19 in New South Wales, Australia</article-title>
          <source>Lancet Public Health</source>
          <year>2022</year>
          <month>03</month>
          <volume>7</volume>
          <issue>3</issue>
          <fpage>e250</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2468-2667(22)00010-X"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2468-2667(22)00010-X</pub-id>
          <pub-id pub-id-type="medline">35131045</pub-id>
          <pub-id pub-id-type="pii">S2468-2667(22)00010-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC8816387</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>Seto</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Challa</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ware</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Adoption of COVID-19 contact tracing apps: a balance between privacy and effectiveness</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>03</month>
          <day>04</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>e25726</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/3/e25726/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25726</pub-id>
          <pub-id pub-id-type="medline">33617459</pub-id>
          <pub-id pub-id-type="pii">v23i3e25726</pub-id>
          <pub-id pub-id-type="pmcid">PMC7935397</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>Meijerink</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Mauroy</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Johansen</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Braaten</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Lunde</surname>
              <given-names>CU</given-names>
            </name>
            <name name-style="western">
              <surname>Arnesen</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Feruglio</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Nygård</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Madslien</surname>
              <given-names>EH</given-names>
            </name>
          </person-group>
          <article-title>The first GAEN-based COVID-19 contact tracing app in Norway identifies 80% of close contacts in "real life" scenarios</article-title>
          <source>Front Digit Health</source>
          <year>2021</year>
          <month>11</month>
          <day>17</day>
          <volume>3</volume>
          <fpage>731098</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34870268"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2021.731098</pub-id>
          <pub-id pub-id-type="medline">34870268</pub-id>
          <pub-id pub-id-type="pmcid">PMC8637921</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>Thomas</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Michaleff</surname>
              <given-names>ZA</given-names>
            </name>
            <name name-style="western">
              <surname>Greenwood</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Abukmail</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Concerns and misconceptions about the Australian Government's COVIDSafe app: cross-sectional survey study</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>11</month>
          <day>04</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e23081</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/4/e23081/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23081</pub-id>
          <pub-id pub-id-type="medline">33048826</pub-id>
          <pub-id pub-id-type="pii">v6i4e23081</pub-id>
          <pub-id pub-id-type="pmcid">PMC7644267</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>Smoll</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Khandaker</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>The barriers and enablers to downloading the COVIDSafe app - a topic modelling analysis</article-title>
          <source>Aust N Z J Public Health</source>
          <year>2021</year>
          <month>08</month>
          <volume>45</volume>
          <issue>4</issue>
          <fpage>344</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33970555"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/1753-6405.13119</pub-id>
          <pub-id pub-id-type="medline">33970555</pub-id>
          <pub-id pub-id-type="pmcid">PMC8209892</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>Huang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>HY</given-names>
            </name>
            <name name-style="western">
              <surname>Chow</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Determinants of the acceptance and adoption of a digital contact tracing tool during the COVID-19 pandemic in Singapore</article-title>
          <source>Epidemiol Infect</source>
          <year>2022</year>
          <month>03</month>
          <day>02</day>
          <volume>150</volume>
          <fpage>e54</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35232505"/>
          </comment>
          <pub-id pub-id-type="doi">10.1017/S0950268822000401</pub-id>
          <pub-id pub-id-type="medline">35232505</pub-id>
          <pub-id pub-id-type="pii">S0950268822000401</pub-id>
          <pub-id pub-id-type="pmcid">PMC8914141</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>Tan</surname>
              <given-names>GK</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>SS</given-names>
            </name>
          </person-group>
          <article-title>Communicative strategies for building public confidence in data governance: analyzing Singapore's COVID-19 contact-tracing initiatives</article-title>
          <source>Big Data Soc</source>
          <year>2022</year>
          <month>06</month>
          <day>28</day>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1177/20539517221104086</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Afroogh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Esmalian</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mostafavi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Akbari</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rasoulkhani</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Esmaeili</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hajiramezanali</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Tracing app technology: an ethical review in the COVID-19 era and directions for post-COVID-19</article-title>
          <source>Ethics Inf Technol</source>
          <year>2022</year>
          <volume>24</volume>
          <issue>3</issue>
          <fpage>30</fpage>
          <pub-id pub-id-type="doi">10.1007/s10676-022-09659-6</pub-id>
          <pub-id pub-id-type="medline">35915595</pub-id>
          <pub-id pub-id-type="pii">9659</pub-id>
          <pub-id pub-id-type="pmcid">PMC9330978</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bengio</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Janda</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>YW</given-names>
            </name>
            <name name-style="western">
              <surname>Ippolito</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jarvie</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pilat</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Struck</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Krastev</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The need for privacy with public digital contact tracing during the COVID-19 pandemic</article-title>
          <source>Lancet Digit Health</source>
          <year>2020</year>
          <month>07</month>
          <volume>2</volume>
          <issue>7</issue>
          <fpage>e342</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(20)30133-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(20)30133-3</pub-id>
          <pub-id pub-id-type="medline">32835192</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(20)30133-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7266569</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</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)</article-title>
          <source>European Union</source>
          <year>2016</year>
          <access-date>2026-09-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng">https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence and amending Regulations (EC) No 300/2008, (EU) No 167/2013, (EU) No 168/2013, (EU) 2018/858, (EU) 2018/1139 and (EU) 2019/2144 and Directives 2014/90/EU, (EU) 2016/797 and (EU) 2020/1828 (Artificial Intelligence Act) (Text with EEA relevance)</article-title>
          <source>European Union</source>
          <year>2024</year>
          <access-date>2026-09-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng">https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2022/2065 of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC (Digital Services Act) (Text with EEA relevance)</article-title>
          <source>European Union</source>
          <year>2022</year>
          <access-date>2026-09-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng">https://eur-lex.europa.eu/eli/reg/2022/2065/oj/eng</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <article-title>Part 312—Children's Online Privacy Protection rule (COPPA rule)</article-title>
          <source>eCFR</source>
          <access-date>2026-09-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-312">https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-312</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McGraw</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dempsey</surname>
              <given-names>JX</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Goldman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Privacy as an enabler, not an impediment: building trust into health information exchange</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2009</year>
          <volume>28</volume>
          <issue>2</issue>
          <fpage>416</fpage>
          <lpage>27</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.28.2.416</pub-id>
          <pub-id pub-id-type="medline">19275998</pub-id>
          <pub-id pub-id-type="pii">28/2/416</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>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>Found Trends Theor Comput Sci</source>
          <year>2014</year>
          <volume>9</volume>
          <issue>3-4</issue>
          <fpage>211</fpage>
          <lpage>407</lpage>
          <pub-id pub-id-type="doi">10.1561/0400000042</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>Liu</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shaham</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rahayu</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Farokhi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>When machine learning meets privacy: a survey and outlook</article-title>
          <source>ACM Comput Surv</source>
          <year>2021</year>
          <month>03</month>
          <day>05</day>
          <volume>54</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>36</lpage>
          <pub-id pub-id-type="doi">10.1145/3436755</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>Rigaki</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Garcia</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A survey of privacy attacks in machine learning</article-title>
          <source>ACM Comput Surv</source>
          <year>2023</year>
          <month>11</month>
          <day>10</day>
          <volume>56</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>34</lpage>
          <pub-id pub-id-type="doi">10.1145/3624010</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>Lipton</surname>
              <given-names>ZC</given-names>
            </name>
          </person-group>
          <article-title>The mythos of model interpretability</article-title>
          <source>Commun ACM</source>
          <year>2018</year>
          <month>09</month>
          <day>26</day>
          <volume>61</volume>
          <issue>10</issue>
          <fpage>36</fpage>
          <lpage>43</lpage>
          <pub-id pub-id-type="doi">10.1145/3233231</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>Guidotti</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Monreale</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ruggieri</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Turini</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Giannotti</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Pedreschi</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>A survey of methods for explaining black box models</article-title>
          <source>ACM Comput Surv</source>
          <year>2018</year>
          <month>08</month>
          <day>22</day>
          <volume>51</volume>
          <issue>5</issue>
          <fpage>1</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1145/3236009</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>Tsamados</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Aggarwal</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Cowls</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Morley</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Taddeo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Floridi</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The ethics of algorithms: key problems and solutions</article-title>
          <source>AI Soc</source>
          <year>2021</year>
          <month>02</month>
          <day>20</day>
          <volume>37</volume>
          <fpage>215</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1007/s00146-021-01154-8</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>Fujii</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Verifiable record of AI output for privacy protection: public space watched by AI-connected cameras as a target example</article-title>
          <source>AI Soc</source>
          <year>2024</year>
          <month>11</month>
          <day>09</day>
          <volume>40</volume>
          <fpage>3697</fpage>
          <lpage>706</lpage>
          <pub-id pub-id-type="doi">10.1007/s00146-024-02122-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Beyond external constraints: the missing dimension of AI governance</article-title>
          <source>SSRN</source>
          <year>2026</year>
          <month>4</month>
          <day>1</day>
          <access-date>2026-09-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6449738">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6449738</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>Brown</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Davidovic</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hasan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The algorithm audit: scoring the algorithms that score us</article-title>
          <source>Big Data Soc</source>
          <year>2021</year>
          <month>01</month>
          <day>28</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>2053951720983865</fpage>
          <pub-id pub-id-type="doi">10.1177/2053951720983865</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>Lindell</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Secure multiparty computation</article-title>
          <source>Commun ACM</source>
          <year>2020</year>
          <month>12</month>
          <day>17</day>
          <volume>64</volume>
          <issue>1</issue>
          <fpage>86</fpage>
          <lpage>96</lpage>
          <pub-id pub-id-type="doi">10.1145/3387108</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>Williamson</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bhaskaran</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bacon</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bates</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Morton</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Mehrkar</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Inglesby</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cockburn</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>HI</given-names>
            </name>
            <name name-style="western">
              <surname>MacKenna</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Tomlinson</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Douglas</surname>
              <given-names>IJ</given-names>
            </name>
            <name name-style="western">
              <surname>Rentsch</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Mathur</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>AY</given-names>
            </name>
            <name name-style="western">
              <surname>Grieve</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Harrison</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Forbes</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Schultze</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Croker</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Parry</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hester</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Harper</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Perera</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Smeeth</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Goldacre</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Factors associated with COVID-19-related death using OpenSAFELY</article-title>
          <source>Nature</source>
          <year>2020</year>
          <month>08</month>
          <volume>584</volume>
          <issue>7821</issue>
          <fpage>430</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32640463"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41586-020-2521-4</pub-id>
          <pub-id pub-id-type="medline">32640463</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41586-020-2521-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC7611074</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</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="https://www.science.org/doi/10.1126/science.abb6936?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </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="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fujii</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>An engineering alternative to lockdown during COVID-19 and other airborne infectious disease pandemics: feasibility study</article-title>
          <source>JMIR Biomed Eng</source>
          <year>2024</year>
          <month>05</month>
          <day>14</day>
          <volume>9</volume>
          <fpage>e54666</fpage>
          <pub-id pub-id-type="doi">10.2196/54666</pub-id>
          <pub-id pub-id-type="medline">38875692</pub-id>
          <pub-id pub-id-type="pii">v9i1e54666</pub-id>
          <pub-id pub-id-type="pmcid">PMC11134249</pub-id>
        </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>Fujii</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Time-managed PAPR use enables a balanced approach to infection control and personal freedom</article-title>
          <source>Sci Rep</source>
          <year>2025</year>
          <month>12</month>
          <day>13</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>2878</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41598-025-32625-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41598-025-32625-3</pub-id>
          <pub-id pub-id-type="medline">41390906</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41598-025-32625-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC12827256</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fujii</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>The real-time estimation of respiratory flow and mask leakage in a PAPR using a single differential-pressure sensor and microcontroller-based smartphone interface in the development of a public-oriented powered air-purifying respirator as an alternative to lockdown measures</article-title>
          <source>Sensors (Basel)</source>
          <year>2025</year>
          <month>08</month>
          <day>28</day>
          <volume>25</volume>
          <issue>17</issue>
          <fpage>5340</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s25175340"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s25175340</pub-id>
          <pub-id pub-id-type="medline">40942768</pub-id>
          <pub-id pub-id-type="pii">s25175340</pub-id>
          <pub-id pub-id-type="pmcid">PMC12431141</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mishra</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Metwally</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Bogu</surname>
              <given-names>GK</given-names>
            </name>
            <name name-style="western">
              <surname>Brooks</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Bahmani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alavi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Celli</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Higgs</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Dagan-Rosenfeld</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Fay</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kirkpatrick</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kellogg</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gibson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hunting</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Mamic</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ganz</surname>
              <given-names>AB</given-names>
            </name>
            <name name-style="western">
              <surname>Rolnik</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Snyder</surname>
              <given-names>MP</given-names>
            </name>
          </person-group>
          <article-title>Pre-symptomatic detection of COVID-19 from smartwatch data</article-title>
          <source>Nat Biomed Eng</source>
          <year>2020</year>
          <month>12</month>
          <volume>4</volume>
          <issue>12</issue>
          <fpage>1208</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33208926"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41551-020-00640-6</pub-id>
          <pub-id pub-id-type="medline">33208926</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41551-020-00640-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC9020268</pub-id>
        </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>Ladner</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Grubaugh</surname>
              <given-names>ND</given-names>
            </name>
            <name name-style="western">
              <surname>Pybus</surname>
              <given-names>OG</given-names>
            </name>
            <name name-style="western">
              <surname>Andersen</surname>
              <given-names>KG</given-names>
            </name>
          </person-group>
          <article-title>Precision epidemiology for infectious disease control</article-title>
          <source>Nat Med</source>
          <year>2019</year>
          <month>02</month>
          <volume>25</volume>
          <issue>2</issue>
          <fpage>206</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30728537"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-019-0345-2</pub-id>
          <pub-id pub-id-type="medline">30728537</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-019-0345-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC7095960</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>Hu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Protocol-aware epidemic forecasting across heterogeneous public health surveillance systems</article-title>
          <source>Front Public Health</source>
          <year>2026</year>
          <month>5</month>
          <day>29</day>
          <volume>14</volume>
          <fpage>1829302</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fpubh.2026.1829302"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpubh.2026.1829302</pub-id>
          <pub-id pub-id-type="medline">42293655</pub-id>
          <pub-id pub-id-type="pmcid">PMC13260628</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>Hu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Toward retrieval-grounded evaluation for conversational large language model-based risk assessment</article-title>
          <source>JMIR AI</source>
          <year>2026</year>
          <month>03</month>
          <day>12</day>
          <volume>5</volume>
          <fpage>e90759</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ai.jmir.org/2026//e90759/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/90759</pub-id>
          <pub-id pub-id-type="medline">41818631</pub-id>
          <pub-id pub-id-type="pii">v5i1e90759</pub-id>
          <pub-id pub-id-type="pmcid">PMC12981538</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
