<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Public Health Surveill</journal-id><journal-id journal-id-type="publisher-id">publichealth</journal-id><journal-id journal-id-type="index">9</journal-id><journal-title>JMIR Public Health and Surveillance</journal-title><abbrev-journal-title>JMIR Public Health Surveill</abbrev-journal-title><issn pub-type="epub">2369-2960</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">v12i1e77763</article-id><article-id pub-id-type="doi">10.2196/77763</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Transforming a Pandemic Tool Into a Public Health Asset: Modified Delphi Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Malekinejad</surname><given-names>Mohsen</given-names></name><degrees>MD, DrPH</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Mendez-Lizarraga</surname><given-names>Cesar Arturo</given-names></name><degrees>MD, MS, MPH</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Skehan</surname><given-names>Nicole</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bercasio</surname><given-names>Alyssa</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Palekar</surname><given-names>Rakhee</given-names></name><degrees>MD, MPH</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lober</surname><given-names>William B</given-names></name><degrees>MD, MS</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib></contrib-group><aff id="aff1"><institution>Institute for Global Health Sciences, University of California, San Francisco</institution><addr-line>550, 16th St, 3406, Floor 3</addr-line><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff2"><institution>MITRE Corporation</institution><addr-line>McLean</addr-line><addr-line>VA</addr-line><country>United States</country></aff><aff id="aff3"><institution>School of Nursing, University of Washington</institution><addr-line>Seattle</addr-line><addr-line>WA</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Mavragani</surname><given-names>Amaryllis</given-names></name></contrib><contrib contrib-type="editor"><name name-style="western"><surname>Sanchez</surname><given-names>Travis</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Carot-Sans</surname><given-names>Gerard</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Mazrouee</surname><given-names>Sepideh</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Mohsen Malekinejad, MD, DrPH, Institute for Global Health Sciences, University of California, San Francisco, 550, 16th St, 3406, Floor 3, San Francisco, CA, 94143, United States, 1 4154765494; <email>mmalekinejad@ucsf.edu</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>16</day><month>9</month><year>2026</year></pub-date><volume>12</volume><elocation-id>e77763</elocation-id><history><date date-type="received"><day>19</day><month>05</month><year>2025</year></date><date date-type="rev-recd"><day>31</day><month>07</month><year>2026</year></date><date date-type="accepted"><day>02</day><month>08</month><year>2026</year></date></history><copyright-statement>&#x00A9; Mohsen Malekinejad, Cesar Arturo Mendez-Lizarraga, Nicole Skehan, Alyssa Bercasio, Rakhee Palekar, William B Lober. Originally published in JMIR Public Health and Surveillance (<ext-link ext-link-type="uri" xlink:href="https://publichealth.jmir.org">https://publichealth.jmir.org</ext-link>), 16.9.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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Public Health and Surveillance, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://publichealth.jmir.org">https://publichealth.jmir.org</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://publichealth.jmir.org/2026/1/e77763"/><abstract><sec><title>Background</title><p>During the COVID-19 pandemic, over 100 countries successfully deployed smartphone-based exposure notification (EN) apps alongside conventional contact tracing to mitigate the transmission of SARS-CoV-2. These systems enabled millions of COVID-19&#x2013;positive individuals to anonymously alert community members of a potential exposure. Although evidence on EN program implementation is limited, leveraging expertise from public health professionals, academics, and global implementers from various disciplines can contribute to addressing this research gap.</p></sec><sec><title>Objective</title><p>This study aimed to explore barriers and facilitators to adoption, identify optimal use cases for these tools, and understand how advancements in technology and policy might maximize EN utility for mitigating other infectious outbreaks.</p></sec><sec sec-type="methods"><title>Methods</title><p>We used the Delphi method to develop a comprehensive online survey comprising closed-ended and open-ended questions. We considered consensus was reached when at least 75% of respondents selected &#x201C;agree&#x201D; or &#x201C;strongly agree&#x201D; for an item or statement. More than 30 global EN experts known to the investigators were invited to participate in the survey, and those who participated were asked to nominate or recruit others deemed eligible via a peer-to-peer method. We used descriptive and content analyses to summarize key findings from the survey. We invited the same experts to attend virtual focus groups to further probe their insights into the survey findings.</p></sec><sec sec-type="results"><title>Results</title><p>Twenty-two experts from 6 countries, including 10 experts from the United States, representing 3 continents, participated. Respondents were involved in the implementation of various EN technologies that encompassed varying levels of integration with existing public health agencies&#x2019; infrastructure. Consensus was reached concerning the development of additional functionalities of the system, such as the ability for users to self-report a positive result from a SARS-CoV-2 at-home test, receive additional public health information from the app (ie, information on testing and social services), and receive general venue-based notifications concerning superspreader events. Other items that reached consensus included how the tool could be used for additional epidemiological purposes, such as expanding the technology to other airborne diseases, and the need for integration with surveillance data streams to augment analytics and forecasting.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Global EN systems have the potential to be optimized for public health emergencies beyond COVID-19 and can be used as epidemiological surveillance tools in future disease outbreaks. Decision-makers and experts should revise existing protocols and seek to incorporate new functionality to alleviate the disease burden on both users and public health agencies.</p></sec></abstract><kwd-group><kwd>exposure notification</kwd><kwd>preparedness</kwd><kwd>response, Delphi</kwd><kwd>method</kwd><kwd>pandemic</kwd><kwd>outbreak</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Background</title><p>The COVID-19 pandemic placed unprecedented demands on the public health workforce. In response, digital contact tracing (DCT) and exposure notification (EN) tools were developed to enhance the efficiency of public health outbreak control, particularly during large case surges [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. While some DCT systems were based on direct reporting, a new generation of more automated, scalable EN systems leveraged smart devices to alert individuals of a potential exposure to the SARS-CoV-2 virus, even without direct contact or relationship with the case. Implementation and evaluation of these EN systems within different jurisdictions were shaped by diverse system architectures, deployment strategies, and communication protocols, each influenced by political, social, and financial contexts. These tools also varied in their approach to privacy; some collected personal identifiers while others were completely anonymous and privacy-preserving [<xref ref-type="bibr" rid="ref3">3</xref>].</p></sec><sec id="s1-2"><title>Proximity Detection Technologies</title><p>EN systems work by measuring distances between individuals, using various technologies, such as GPS and Bluetooth Low Energy, to determine if a user was in close contact of a person with a confirmed COVID-19 diagnosis [<xref ref-type="bibr" rid="ref4">4</xref>]. GPS was used in multiple systems&#x2014;including those in South Korea and China&#x2014;because it can capture specific user information [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. However, standard GPS is considered unreliable in determining the exact position of a person and requires a significant amount of battery power.</p><p>On the other hand, Bluetooth-based systems could not record an individual&#x2019;s specific location and therefore were unable to identify where a person was exposed; however, they could assess the proximity between 2 individuals and provide greater privacy protection [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. These systems relied on the generation of random digital codes; when 2 devices came close together, the codes were exchanged. By relying on 2 servers, a key server that stored keys from devices whose users reported positive tests and a verification server that checked for genuine positive tests, devices routinely searched for matches among stored codes. If a match occurred, the app alerted the user about a potential exposure, without disclosing who, when, and where the exposure took place [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. Examples of Bluetooth-based EN systems include Singapore&#x2019;s BlueTrace protocol&#x2014;which was used in Singapore&#x2019;s TraceTogether app and Australia&#x2019;s COVIDSafe app&#x2014;and Google and Apple&#x2019;s jointly developed EN protocol, Google and Apple Exposure Notification (GAEN) system, which became the most widely adopted EN system during the pandemic. GAEN apps used Bluetooth Low-Energy signal exchanges between EN-enabled smartphones to estimate exposure risk based on duration and proximity to an individual&#x2019;s smartphone who voluntarily disclosed a positive COVID-19 test result (<xref ref-type="fig" rid="figure1">Figure 1</xref>) [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>].</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Overview of mobile exposure notification (EN) apps using the Google and Apple Exposure Notification (GAEN) System. Adapted from the California Department of Public Health and Aronoff-Spencer et al [<xref ref-type="bibr" rid="ref13">13</xref>].</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="publichealth_v12i1e77763_fig01.png"/></fig><p>Other proximity detection technologies used Wi-Fi or ultra-wideband systems, while others deployed a QR-based system or a combination of multiple approaches [<xref ref-type="bibr" rid="ref8">8</xref>]. Some apps also used a combination of different technologies, such as India&#x2019;s &#x201C;Aarogya Setu&#x201D; app, which used both GPS and Bluetooth [<xref ref-type="bibr" rid="ref14">14</xref>].</p></sec><sec id="s1-3"><title>Centralized vs Decentralized Data Systems</title><p>Global EN systems also differed in whether they used centralized or decentralized protocols. Centralized protocols stored user interactions on a central server, which allowed for more meticulous epidemiologic tracking and analysis. These protocols enabled public health agencies (PHAs) to track second-order contacts and super-spreader events. Singapore&#x2019;s BlueTrace system used a centralized system, as did China&#x2019;s and South Korea&#x2019;s apps [<xref ref-type="bibr" rid="ref6">6</xref>]. However, centralized protocols were often considered controversial, given that they potentially enabled governments to access personal health data and therefore raised many user privacy concerns. Conversely, decentralized protocols determine and save proximity data and exposure risk entirely on a user&#x2019;s mobile phone to preserve user privacy. While decentralized protocols made epidemiologic analysis difficult, they allowed for greater privacy of user data [<xref ref-type="bibr" rid="ref7">7</xref>]. Apps created on the GAEN system prioritized user privacy over disease surveillance, using a decentralized protocol, while allowing PHAs to set risk parameters and public health messaging by jurisdiction, at the national or subnational level [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p></sec><sec id="s1-4"><title>The Future of EN</title><p>Most EN systems relied on government-sponsored servers to enhance cross-jurisdictional interoperability while preserving user privacy. However, PHAs varied in how they assessed exposure thresholds, further complicating comparisons across implementations [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. While GAEN&#x2019;s privacy-preserving model limited targeted public health messaging and robust impact assessments, modeling studies in settings with meaningful adoption rates&#x2014;such as the United Kingdom and the states of Washington and California in the United States&#x2014;suggest that digital EN systems averted significant numbers of new cases [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. By contrast, non-GAEN systems, which collected identifiable data and location information, offered potential advantages in precision and public health follow-up. These systems could provide more tailored guidance to users and enable PHAs to assess the broader impact of exposures on public health. However, these systems often raised privacy concerns and faced barriers to adoption [<xref ref-type="bibr" rid="ref2">2</xref>].</p><p>As the COVID-19 public health emergency concluded, scientists, policymakers, and public health leaders began to discuss both future and alternative uses of EN systems. Proponents highlighted the unprecedented collaboration between major technology companies and government institutions, resulting in the global deployment of EN systems, with over 300 million users worldwide [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]. Critics noted that while some countries and states deployed EN systems successfully, many regions either did not adopt the technology or failed to achieve meaningful user uptake. Despite variations in adoption and evaluation, EN systems demonstrated significant potential to augment infectious disease response and a remarkable ability to scale to large numbers of users and link jurisdictions, all while preserving privacy. As health systems prepare for future outbreaks, it is crucial to address gaps in EN design, deployment, and adoption to maximize the impact of these tools. It is also critical to understand the barriers and facilitators to their use to guide the development of policies and technologies that strengthen national and global health capacities.</p><p>We developed a modified Delphi study and engaged experts to explore barriers and facilitators to adoption, identify optimal use cases for these tools, and understand how advancements in technology and policy might maximize EN utility for mitigating other infectious disease outbreaks. By learning from the successes and limitations of EN systems during the COVID-19 pandemic, we seek to inform the design and implementation of more effective outbreak response tools for future use.</p></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design Overview</title><p>We used a modified Delphi Type 3 approach to gather expert knowledge on EN systems, using a comprehensive survey designed to capture both quantitative and qualitative data [<xref ref-type="bibr" rid="ref32">32</xref>]. Appendix A in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> summarizes the study characteristics [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p></sec><sec id="s2-2"><title>Curation of Ideas to Inform Survey Development</title><p>We curated initial ideas based on the authors&#x2019; direct experiences implementing an EN system in California, as well as insights gathered from meetings of the Digital Notification Alliance (DNA), a US-based community of EN practitioners active during the COVID-19 pandemic, with participation from representatives of 16 states. To further develop our framework, we conducted a targeted literature search in PubMed and Google Scholar for relevant peer-reviewed articles and white papers during March-April 2023. The search focused on studies describing the implementation, evaluation, or adoption of EN systems and, when contextually relevant, other DCT tools during the COVID-19 pandemic. We used combinations of keywords such as &#x201C;exposure notification,&#x201D; &#x201C;digital contact tracing,&#x201D; &#x201C;implementation,&#x201D; &#x201C;barriers,&#x201D; &#x201C;facilitators,&#x201D; &#x201C;COVID-19,&#x201D; and &#x201C;evaluation.&#x201D; We searched for papers published between 2020 and 2023 in English. Publications were included if they discussed real-world implementation experiences, adoption barriers, or lessons learned from EN systems. The references identified through this process&#x2014;together with relevant white papers and reports from our professional networks&#x2014;were used to structure survey items and domains [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. Additionally, we contacted our network of EN implementers across the United States and internationally to inquire about relevant publications and gray literature.</p></sec><sec id="s2-3"><title>Survey Development</title><p>Based on curated inputs, we developed a Delphi survey to collect expert insights on best practices, implementation challenges, and future directions for EN systems, with a focus on those using the GAEN protocol during the COVID-19 pandemic. The survey comprised six major sections: (1) participant consent and survey introduction; (2) expert demographics and professional background; (3) perceived successes, barriers, and facilitators of EN deployment; (4) perspectives on key system functionalities, disease applicability, macro-level governance, and considerations around privacy, equity, and communication; (5) opinions on potential uses of EN technologies beyond infectious disease outbreaks; and (6) participant demographics and peer referrals.</p><p>The final survey included approximately 100 questions, incorporating multiple-choice (including Likert-scale and rank-order items) and open-ended formats. Likert-scale items assessed the perceived importance or level of agreement on various implementation dimensions, while open-ended items allowed for elaboration and identification of additional considerations. The survey was administered via Qualtrics [<xref ref-type="bibr" rid="ref36">36</xref>]. The instrument is available in Appendix B in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></sec><sec id="s2-4"><title>Participant Recruitment</title><p>Using a combination of convenience and peer-referral methods, we recruited participants from our extensive network of US-based and international EN experts with whom we had collaborated and exchanged scientific ideas throughout the pandemic. We initially identified participants through the DNA network group to share lessons learned and best practices in EN implementation. Through the DNA network, we distributed invitations via its membership listserv, solicited referrals (snowball sampling), and leveraged its endorsement to broaden participation beyond our immediate collaborators. We also invited key authors of published papers on EN prior to the inception of our study. In total, 56 eligible experts representing PHAs, academia, and the technology industry were invited to participate. Eligibility criteria included being at least 18 years of age and having experience in the development, implementation, or evaluation of EN systems during the COVID-19 pandemic. Of the 56 identified experts, a total of 30 initially expressed interest in participating.</p></sec><sec id="s2-5"><title>Pilot Testing and Data Collection</title><p>Using QualtricsXM, we conducted a pilot test with 4 individuals to evaluate the survey&#x2019;s logistics, length, content, and flow [<xref ref-type="bibr" rid="ref36">36</xref>]. Based on feedback, we made minor revisions and then distributed the survey via email to 30 experts who had previously expressed interest in participating. The survey was launched in fall 2024, with up to 3 reminder emails sent at 7- to 10-day intervals. All responses were anonymous and untraceable after the pilot phase. Data from the pilot were included in the final data analysis.</p></sec><sec id="s2-6"><title>Data Analysis</title><p>We conducted descriptive analysis of the quantitative data using Microsoft Excel. For Likert-scale questions, we adopted the 75% agreement threshold that was suggested in the systematic review of reporting Delphi studies to establish a working definition of &#x201C;large majority&#x201D; for our study [<xref ref-type="bibr" rid="ref34">34</xref>]. This threshold was used to identify items that were deemed more important or to represent a higher level of agreement among experts, but it should not be seen as a consensus threshold. For items or statements that required ranking, we used a weighted score to determine the order based on the number of responses for each question:</p><disp-formula id="E1"><mml:math id="eqn1"><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd><mml:mtext>Weighted score</mml:mtext></mml:mtd><mml:mtd><mml:mi/><mml:mo>=</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of first place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>1.0</mml:mn><mml:mo stretchy="false">]</mml:mo><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of second place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.5</mml:mn><mml:mo stretchy="false">]</mml:mo></mml:mtd></mml:mtr><mml:mtr><mml:mtd/><mml:mtd><mml:mi/><mml:mtext>&#x00A0;</mml:mtext><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of third place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.33</mml:mn><mml:mo stretchy="false">]</mml:mo><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of fourth place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.25</mml:mn><mml:mo stretchy="false">]</mml:mo></mml:mtd></mml:mtr><mml:mtr><mml:mtd/><mml:mtd><mml:mi/><mml:mtext>&#x00A0;</mml:mtext><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of fifth place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.2</mml:mn><mml:mo stretchy="false">]</mml:mo><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of sixth place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.16</mml:mn><mml:mo stretchy="false">]</mml:mo></mml:mtd></mml:mtr><mml:mtr><mml:mtd/><mml:mtd><mml:mi/><mml:mtext>&#x00A0;</mml:mtext><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of seventh place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.14</mml:mn><mml:mo stretchy="false">]</mml:mo><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of eighth place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.12</mml:mn><mml:mo stretchy="false">]</mml:mo></mml:mtd></mml:mtr><mml:mtr><mml:mtd/><mml:mtd><mml:mi/><mml:mtext>&#x00A0;</mml:mtext><mml:mo>+</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mtext>number of ninth place votes</mml:mtext><mml:mo stretchy="false">)</mml:mo><mml:mo>&#x00D7;</mml:mo><mml:mn>0.11</mml:mn><mml:mo stretchy="false">]</mml:mo></mml:mtd></mml:mtr></mml:mtable></mml:mstyle></mml:mrow></mml:mstyle></mml:math></disp-formula><p>For the qualitative data, 2 researchers conducted a thematic analysis to identify recurring themes, which were used to supplement our analysis of the quantitative data. This allowed us to further elaborate on expert experiences and opinions, from which we could infer major key points and generate actionable recommendations. Examples are shown in <xref ref-type="table" rid="table1">Table 1</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Thematic analysis of open-ended question responses<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup>.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Themes and questions</td><td align="left" valign="bottom">Responses</td><td align="left" valign="bottom">Subtheme</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="3">Lessons from the COVID-19 pandemic</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Do you think your EN<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup> program achieved goals and objectives?</td><td align="left" valign="top">&#x201C;It did so by complementing conventional contact tracing; compared to the latter, it led to an estimated 5%&#x2010;10% increase in the number of cases detected.&#x201D;</td><td align="left" valign="top">Public health</td></tr><tr><td align="left" valign="top" colspan="3">The next EN application</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Would you consider continuing EN programs if COVID-19 resources were available?</td><td align="left" valign="top">&#x201C;EN systems should ideally run continuously, even when there is no immediate need. That way, it can be ready to scale up quickly when needed.&#x201D;</td><td align="left" valign="top">Public health</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Do you have suggestions as to what governance principles and procedures should be in place prior to the next implementation of EN systems?</td><td align="left" valign="top">&#x201C;International coordination between public health agencies and tech companies is necessary to iron out interests and articulate norms that can guide decisions.&#x201D;</td><td align="left" valign="top">Public policy</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Are there ways to improve the opt-in sharing of information?</td><td align="left" valign="top">&#x201C;There should be levels of information sharing for the comfortability of opting into the system..., but there should be no requirement for it.&#x201D;</td><td align="left" valign="top">Technical features</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>The themes included in the survey are shown in the first column. Based on question types and responses, 3 subthemes emerged: technical features of EN applications, public health, and public policy issues.</p></fn><fn id="table1fn2"><p><sup>b</sup>EN: exposure notification.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-7"><title>Expert Review and Validation of Findings and Final Recommendations</title><p>Following the initial round of data analysis, all expert participants were invited to a live, 2-hour virtual presentation to review findings and provide additional insights. Two sessions were conducted, and discussions were recorded with participants&#x2019; permission. One researcher took detailed notes from the sessions and analyzed participant feedback. Comments and suggestions from these sessions were integrated into the final interpretation of results. The final recommendations were developed through a multistep process. Topics and ideas that were deemed important or reached a high level of agreement in the quantitative survey were prioritized. These were further enriched by qualitative feedback provided by participants and subsequently validated through the live expert reviews and discussions.</p></sec><sec id="s2-8"><title>Ethical Considerations</title><p>Our study protocol was reviewed and approved by the Committee on Human Research at the University of California, San Francisco (UCSF), through an expedited review process (IRB number: 23-39886; reference number: 398640). The study did not include personal or sensitive questions and focused instead on gathering expert opinions about a digital health product. All data were stored securely within UCSF&#x2019;s protected data systems and reported only in aggregate form to safeguard participant privacy. Participants could choose to share their general geographic location for national-level analysis. Those who provided informed consent were invited to complete the survey and received a US $50 gift card for participating in at least 1 round of data collection. Individuals who also took part in the live discussion received an additional US $100 gift card.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Demographics</title><p>A total of 22 individuals from 3 World Health Organization (WHO) Regions (Americas, Europe, and Western Pacific), representing 6 countries, participated in our Delphi. We asked participants to select their involvement with EN systems during the pandemic, as all had carried out more than one specific activity (<xref ref-type="table" rid="table2">Table 2</xref>). The most common roles included data analysis (n=19, 86.3%), coordination with public and private partners (n=17, 77.2%), and elaborating policies and guidelines for decision-makers (n=14, 63.6%; <xref ref-type="table" rid="table3">Table 3</xref>).</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Participants&#x2019; primary country for exposure notification (EN) implementation, years of experience with EN, and other characteristics of EN implementation (N=22).</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">Values, n (%)</td></tr></thead><tbody><tr><td align="left" valign="bottom" colspan="2">Primary country in which participants were involved in EN<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> implementation</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>United States of America</td><td align="left" valign="top">10 (45.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Belgium</td><td align="left" valign="top">2 (9.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>United Kingdom</td><td align="left" valign="top">2 (9.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Germany</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Singapore</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Italy</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unknown</td><td align="left" valign="top">5 (22.7)</td></tr><tr><td align="left" valign="top" colspan="2">Years of experience in EN systems</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1&#x2010;3 y</td><td align="left" valign="top">11 (50.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3 or more years</td><td align="left" valign="top">10 (45.4)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Not reported</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top" colspan="2">Type of EN system first implemented</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Customized GAEN<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup> app</td><td align="left" valign="top">8 (36.3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>ENX (Exposure Notification Express)</td><td align="left" valign="top">5 (22.7)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Fully custom app</td><td align="left" valign="top">5 (22.7)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Mixed or hybrid model</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Other</td><td align="left" valign="top">2 (9.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unknown</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top" colspan="2">Integration of EN systems to PHA<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup> public health response</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Not entirely integrated</td><td align="left" valign="top">9 (40.9)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Fully integrated</td><td align="left" valign="top">7 (31.8)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Stand-alone systems</td><td align="left" valign="top">2 (9.1)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Other</td><td align="left" valign="top">1 (4.5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unknown</td><td align="left" valign="top">3 (13.6)</td></tr><tr><td align="left" valign="top" colspan="2">Main implementer of EN systems in jurisdiction</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Mixed model</td><td align="left" valign="top">11 (55.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Health departments</td><td align="left" valign="top">7 (35.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Contract with private entity</td><td align="left" valign="top">2 (10.0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Not reported</td><td align="left" valign="top">2 (9.1)</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>EN: exposure notification.</p></fn><fn id="table2fn2"><p><sup>b</sup>GAEN: Google and Apple Exposure Notification system.</p></fn><fn id="table2fn3"><p><sup>c</sup>PHA: public health agencies.</p></fn></table-wrap-foot></table-wrap><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Participants&#x2019; areas of expertise and roles adopted in the exposure notification (EN) implementation<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup>.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Areas of expertise and roles adopted</td><td align="left" valign="bottom">Values (n)</td></tr></thead><tbody><tr><td align="left" valign="bottom" colspan="2">Areas of expertise</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Public health</td><td align="left" valign="top">15</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Epidemiology</td><td align="left" valign="top">14</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>EN<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup> systems and technology</td><td align="left" valign="top">12</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Policy</td><td align="left" valign="top">5</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Health communications</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Engineering</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Research</td><td align="left" valign="top">10</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Other</td><td align="left" valign="top">8</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Patient care</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top" colspan="2">Responder&#x2019;s role in EN implementation</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Data analysis</td><td align="left" valign="top">19</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coordination with public and private partners</td><td align="left" valign="top">17</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Health communication media</td><td align="left" valign="top">13</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Program implementation</td><td align="left" valign="top">12</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>User experience</td><td align="left" valign="top">11</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Interface design</td><td align="left" valign="top">8</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Systems development</td><td align="left" valign="top">12</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Policies and guidelines elaboration for decision-makers</td><td align="left" valign="top">14</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>Respondents (N=22) were asked to select all options that applied to their profile.</p></fn><fn id="table3fn2"><p><sup>b</sup>EN: exposure notification.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Lessons From EN System Implementation During the COVID-19 Pandemic</title><sec id="s3-2-1"><title>Overview</title><p>When inquired about specific barriers to EN program implementation, the large majority of participants (15/20, 75% of respondents) identified &#x201C;community mistrust in the government&#x201D; as a major barrier (<xref ref-type="fig" rid="figure2">Figure 2</xref>). Items voted by at least half of the participants as barriers to implementation included the following: the lack of political support from policymakers (11/20, 55%) and community mistrust in EN systems (11/21, 52.4%). Other items voted by less than 50% of respondents as barriers included, but were not limited to, the following: community mistrust in technology companies (10/21, 47.6%), lack of staff workforce within PHAs <italic>(</italic>7/19, 36.8%<italic>)</italic>, and lack of departmental technical knowledge (6/19, 31.6%).</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Barriers to exposure notification (EN) program implementation during COVID-19. Response statements have been shortened for practical reasons. Agreement and disagreement percentages are aggregates of &#x201C;agree,&#x201D; &#x201C;strongly agree,&#x201D; &#x201C;disagree,&#x201D; and &#x201C;strongly disagree,&#x201D; respectively. Statements are ranked from the highest to the lowest percentage of agreement.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="publichealth_v12i1e77763_fig02.png"/></fig></sec><sec id="s3-2-2"><title>Implementation Barriers</title><p>Respondents pointed out a combination of factors such as &#x201C;lack of awareness, privacy concerns, government mistrust, and lack of understanding of how the app worked&#x201D; as barriers to PHA implementation. For others, a bigger budget could have translated into &#x201C;continuous development, better privacy features, and relevant data analysis.&#x201D; In the case of the United States, the lack of a centralized system caused a &#x201C;significant burden on jurisdictions.&#x201D; In addition, we inquired about ideal resources (framed as a &#x201C;Wishlist&#x201D;) for better programmatic and health outcomes. Respondents indicated a desire for higher budgets for increasing user engagement, stronger analytical resources for tracking relevant metrics, access to testing without symptoms, full support from decision-makers, an opt-out modality, central collection of outcome data (eg, test results for notified contacts), better integration between testing and treatment resources (as well as with other agencies), more app promotion, and a &#x201C;multilateral dialogue on EN system design principles with tech giants with a deference to public health.&#x201D;</p></sec><sec id="s3-2-3"><title>Program Goals</title><p>When inquired whether participants thought their EN programs achieved proposed goals and objectives, some stressed that they did so by &#x201C;alerting hundreds of thousands of people of exposures,&#x201D; while others expressed that the system notified &#x201C;far more contacts per exposure than traditional contact tracing.&#x201D; Conversely, some believed they did not achieve their goals and objectives because they faced little adoption, late integration into their health authorities&#x2019; processes, and &#x201C;lack of public communication about the processes of the app.&#x201D;</p></sec></sec><sec id="s3-3"><title>Epidemiological and Clinical Considerations for Future EN Systems</title><p>With respect to the applicability of proximity-based EN apps for infectious diseases, the large majority of respondents labeled airborne diseases as &#x201C;very applicable&#x201D; (17/21, 80.9%), while fomite-transmitted diseases were considered &#x201C;very applicable&#x201D; by less than half (9/20, 45%). On the other hand, blood-borne diseases and sexually transmitted infections were predominantly considered as &#x201C;not very applicable&#x201D; by 80% (16/20) and 65% (13/20) of respondents, respectively. Concerning the incorporation of diseases into future EN apps, the large majority of participants considered COVID-19 (20/22, 90.9%) and measles (17/22, 77.3%). Other diseases that were considered by at least half of the respondents were influenza (15/22, 68.2%) and tuberculosis (13/22, 59.1%). Additional pathogens that were suggested in the written comments by participants included respiratory syncytial virus, meningococcal meningitis, Disease X, HIV, hepatitis A, Mpox, and other sexually transmitted infections.</p><p>Finally, we asked participants to rank key epidemiological and clinical characteristics of pathogens that should be considered for future app developments, which resulted in the following order of priorities: (1) transmissibility of the pathogen (incubation period, infectiousness, etc; 82 points); (2) available protective actions (75 points); (3) disease burden (71 points); (4) level of community immunity (67 points); and (5) economic availability (or feasibility) to take protective actions (65 points).</p></sec><sec id="s3-4"><title>Public Health and Implementation Considerations for Future EN Systems</title><sec id="s3-4-1"><title>EN Value for the Future</title><p>When asked if there was any value in continuing EN programs after the end of the COVID-19 pandemic as a public emergency of international concern, respondents agreed that there is a need to be ready: &#x201C;waiting for an emergency will always be too late...even modest benefit with ongoing use is worthwhile.&#x201D; Pandemic preparedness and response require a set of continuous actions, and for EN systems, &#x201C;ideally they should run continuously...ready to scale up quickly when needed.&#x201D; A challenge highlighted was the need to demonstrate its value to secure the necessary resources and political support, with one participant noting, &#x201C;we need to demonstrate value to enable resource allocation and political support.&#x201D;</p></sec><sec id="s3-4-2"><title>Strategies to Improve EN Adoption</title><p>Clear communication&#x2014;such as the benefits for the individual and community, goals, and privacy issues&#x2014;is key, as is open communication about any uncertainties (ie, &#x201C;letting the wider public know what we don&#x2019;t know&#x201D;). On communicating with users about their exposure, messages need to be accurate and readable. As shared by the group, &#x201C;information has to be credible and accessible.&#x201D; Another suggested strategy was to include venue-based exposure alerts. On how to best leverage experience from implementors, a shared answer was to create standardized guides for PHA EN deployment, covering design, development, implementation, evaluation, and other aspects encompassing a public health intervention.</p></sec><sec id="s3-4-3"><title>Communication Campaign</title><p>When participants were asked to select topics that should be considered for public-facing communication campaigns, topics deemed &#x201C;very important&#x201D; by the large majority were as follows: reminders to use the system when testing positive (18/22, 81.8%) and that users should directly benefit from using the system (17/22, 77.2%). Items that were selected by more than 50% but were below the large majority threshold included how to use the system (15/22, 68.1%), community benefits from using the system (13/22, 59.1%), and user privacy protection (13/22, 59.1%). Marketing strategies for EN technologies through public agencies included using social media and communicating to the broader public while advertising the app as &#x201C;a tool for citizen science&#x201D; to strengthen societal preparedness. About reducing technological disparities, &#x201C;using free standalone devices&#x201D; that can provide text-based notifications and inform of actions that communities can take was identified as the most common approach. Finally, when inquired about the utility and importance of a comprehensive and multifunctional EN app for future public health threats, participants stated that &#x201C;it may lose focus on what the main priority...and users may become overwhelmed,&#x201D; while a participant suggested that EN apps should be limited to infectious disease monitoring and control.</p></sec></sec><sec id="s3-5"><title>Technical Features Considerations for Future EN Systems</title><sec id="s3-5-1"><title>General Technical Features for Future App Development</title><p>Participants were asked to label the importance of functionalities and characteristics for future EN systems. The ability to self-report at-home tests was the only item that was considered &#x201C;very important&#x201D; by the large majority (18/22, 81.8%) of respondents, while the ability to get additional public health information was considered &#x201C;very important&#x201D; by 68.2% (15/22). Also, the venue-based notifications feature was labeled as &#x201C;important&#x201D; by more than half (14/21, 66.7%) of participants. Features like the use of sensors to assess the level of risk and the ability to set a personal risk score for notifications were categorized as &#x201C;somewhat important&#x201D; by almost half of the participants. No feature was deemed &#x201C;not very important&#x201D; by one-third or more of respondents. The level of importance of all functionalities is shown below (<xref ref-type="fig" rid="figure3">Figure 3</xref>).</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>System functionalities and characteristics for the next exposure notification (EN) app are shown together by their level of importance on a 4-point Likert scale. Items are ranked based on the percentages obtained for &#x201C;very important&#x201D; from respondents (n=22).</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="publichealth_v12i1e77763_fig03.png"/></fig></sec><sec id="s3-5-2"><title>Specific Technology for Proximity Detection</title><p>Half of the participants considered mixed EN signaling technologies to be the best solution for future developments, followed by only Bluetooth Low Energy (5/22, 22.7%) and ultra-wideband (2/22, 9.1%). Mixed EN technology examples included combining Bluetooth Low Energy with other methods (ie, GPS or venue-based alerts), and participants commonly wrote down &#x201C;Bluetooth plus Ultra-wideband system&#x201D; as another option. Nearly 20% (4/22) of respondents did not offer a specific opinion.</p><p>When participants were asked to rank strategies to ease user burden, the order is as follows: (1) easier methods for activation (97 points), (2) increased access to other public health resources (86 points), (3) more accessible language (85 points), (4) different user workflows (73 points), (5) new methods for direct user communication (50 points), and (6) new EN hardware (29 points). Furthermore, the group was divided on whether the use of custom hardware or devices should (10/21, 47.7%) or should not (11/21, 52.3%) be incorporated. Further insight on this revealed that it has the potential &#x201C;to be quickly deployed in outbreaks in populations without smartphones&#x201D; but made no sense in settings where mobile phone coverage is high, as &#x201C;it seems unnecessary to ask them to carry another device.&#x201D;</p></sec><sec id="s3-5-3"><title>Privacy</title><p>Out of 4 options (accuracy of EN, perceived risk by users and their willingness to adopt, scalability tradeoff, and system evaluation capabilities), we asked participants to identify the option that is more important to consider for future EN development in relation to the level of privacy. Privacy was the only characteristic deemed as &#x201C;more important&#x201D; by the large majority against the perceived risk by users and their willingness to adopt (18/22, 81.8%). Privacy was voted as &#x201C;less important&#x201D; by more than half of participants and less than the large majority for the following: accuracy of EN (13/22, 59.1%) and system evaluation capabilities (12/21, 57.1%). Finally, privacy was neither more nor less important for the scalability tradeoff (50% vs 50%; N=20). The use of technology with a Bluetooth-based protocol that does not require information about the location of the user was considered advantageous, as &#x201C;it preserved privacy while not creating a huge burden on user batteries&#x2014;unlike GPS&#x2014;...with the downside of not fully understanding the location of cases.&#x201D; Concerning how users should share information, participants felt that &#x201C;there should not be a requirement for data sharing&#x201D; and that users should be provided with layers or levels of data sharing that users can choose to opt into, allowing users to exercise autonomy.</p></sec></sec><sec id="s3-6"><title>Institutional and Governance Considerations for the Future EN Systems</title><p>Concerning where to place EN programs in organizational structures, more than half opted for a hybrid model (eg, sharing responsibilities between emergency response and data informatics; 13/22, 59.1%), leaving out emergency response (5/22, 22.7%), data systems-information (2/22, 9.1%), and contact tracing programs (2/22, 9.1%) as potential sites. Other proposed locations included disease surveillance and biosecurity within the military structure. Another response suggested a more restrained approach: &#x201C;discussing the benefits and challenges with agencies, as it requires an interdisciplinary approach.&#x201D;</p><p>On governance for EN programs, some acknowledge that it should be on a country level and that &#x201C;a regulatory framework should be in place before the next public health emergency.&#x201D; A considerable proportion of participants (13/21, 61.9%) expressed that implementation levels should be nationwide, with an option for states to customize.</p><p>International and national institutions that should be reached out to for future collaborations include the WHO (14/34, 41.2%), National Institutes of Health (9/34, 26.4%), and Federal Emergency Management Agency (8/34, 23.5%), as well as other agencies such as Centers for Disease Control and Prevention, Homeland Security, Food and Drug Administration, European Center for Disease Prevention and Control, and central hubs from around the world. When asked to rank institutions that should be tasked with building trust, the following order emerged: (1) public health departments (79 points), (2) EN system-technologies (66 points), (3) state government (64 points), (4) technology companies (54 points), and (5) federal governments (52 points). With respect to organizing working groups (such as DNA in the United States), respondents expressed that these groups should continue to meet and plan for the next steps, as &#x201C;it fosters relationships with private and public partners.<italic>&#x201D;</italic> The most effective way to use these groups is to leverage their expertise in designing next-generation tools.</p><p>The importance of working with smartphone manufacturers was emphasized by the large majority of the group (17/22, 77.2%), as some pointed out that in addition to tapping into their technical expertise, &#x201C;it helps build relationships and improve operations that benefit actors.&#x201D; When examining the possibility of working with other companies aside from Google and Apple, participants expressed that mobile phone and app companies should be included, though &#x201C;many settings are regulated by these two companies...both need to open up their ecosystem and infrastructure that allows others to work<italic>,</italic>&#x201D; highlighting the support from big tech companies.</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Summary of Key Findings</title><p>To our knowledge, this is the first study to systematically capture insights from experts on the future of EN systems. Although others convened group discussions for similar purposes, those attempts were not as comprehensive as ours, were not peer-reviewed, and were convened or led by industry personnel [<xref ref-type="bibr" rid="ref35">35</xref>]. Our study suggests that during the COVID-19 pandemic, the main barriers to EN program implementation included community mistrust in technology companies and mistrust in EN systems, followed by a lack of political support from policymakers. Airborne diseases, such as measles, influenza, respiratory syncytial virus, and tuberculosis, were considered the most appropriate group of diseases to incorporate into EN systems. Additional features to consider for the next app include pathogen transmissibility, protective measures, and the burden of disease in the community. Some of the most important features and system characteristics for future apps were the capacity to self-report at-home tests, access to additional public health information, general venue notifications, and differential messaging based on risk level. Finally, for public policy purposes, the study highlights the need to further discuss the benefits and challenges with involved agencies, as it requires collaboration within and across institutions, and efforts should be made to foster working groups to enhance EN systems.</p></sec><sec id="s4-2"><title>Public Health and Policy Implications and Recommendations</title><p>This study serves multiple purposes. The first is to describe barriers experienced during the COVID-19 pandemic that require action for improving performance and facilitating the implementation of future EN systems. The second is to provide a landscape of improvements to be considered for the next batch of EN systems. These improvements build upon the experience participants shared and make a call for intersectoral collaboration across public health professionals, the technology industry, and policymakers with key roles in advancing preparedness and response against infectious diseases across all government levels, civil society, and academia. Third, it advocates the preservation of current technologies to enhance public health functions by expanding its scope of work to other infectious diseases and by promoting working groups to leverage expertise (regardless of geographical dimensions), develop guidelines, and foster networks across sectors. Finally, it lays out recommendations for decision-makers, public health professionals, and the technology industry for enhancing the next generation of EN systems as follows:</p><p>First, efforts to strengthen EN systems should address key implementation and adoption barriers. Legal barriers should be identified and resolved first to facilitate timely technological development and deployment. At the same time, community trust should be built via close partnership with public health authorities at local, state, and national levels. Furthermore, close collaboration with technology companies is critical to develop strategic work plans aimed at strengthening user trust and increasing app adoption.</p><p>Second, to enhance the functionality and effectiveness of EN apps, participants recommended incorporating several core epidemiological and clinical features. These include information about the transmissibility and natural history of the pathogen, clear guidance on protective actions that individuals can take&#x2014;both pharmacological and nonpharmacological&#x2014;as well as information about available economic resources to support those actions. Including contextual information about disease burden was also considered important. In addition, experts supported expanding EN systems beyond COVID-19 to other high-burden pathogen groups, including airborne diseases, vaccine-preventable diseases, and sexually transmitted infections.</p><p>Third, several system-level and user-level characteristics were identified as priorities for future development. EN systems should enable general venue notifications and provide differential messaging based on individual risk level. The use of metadata to improve risk estimation and the integration of other surveillance data sources to enhance analytics and forecasting were also recommended. At the user level, functionality should allow individuals to self-report at-home test results, request additional public health information, incorporate individual-level risk factors, and receive notifications that clearly indicate exposure risk level (eg, high or low). Participants also emphasized that users should be able to turn off the app regardless of Bluetooth status. To improve access, EN systems should incorporate easier methods for app activation, expand access to other public health resources, and improve accessibility by offering multiple language options.</p><p>Finally, to support sustainable implementation, experts recommended fostering structured working groups that include local and national public health departments and other relevant organizations. These groups should create subcommittees focused on specific topics, use standardized approaches to estimate key performance indicators, organize workshops to equip implementation teams with practical tools, and systematically document and share lessons learned. Finally, planning, implementation, and evaluation of EN systems should involve coordinated engagement with public health departments, EN technology developers, state and local governments, technology companies, and, when appropriate, federal agencies.</p></sec><sec id="s4-3"><title>Comparison to Prior Work</title><p>Although no prior peer-reviewed study has examined the same breadth of EN implementation barriers, disease applicability, future system functionality, and governance priorities in one place, some studies addressed certain aspects of our findings. For instance, other studies also noted that adoption of EN and DCT apps was influenced by privacy concerns, trust, perceived usefulness, and usability [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. Furthermore, another paper emphasized that EN deployment depended on close collaboration among technology companies, developers, and public health authorities, while fragmented rollout and limited data collection complicated effectiveness assessment [<xref ref-type="bibr" rid="ref7">7</xref>]. Our findings also reinforce the conclusions from the best-practice guidance and implementation experiences from several European countries: EN apps should rapidly connect users to testing, quarantine guidance, and other public health resources, and risk-stratified messaging and actionable recommendations may improve both engagement and public health utility [<xref ref-type="bibr" rid="ref8">8</xref>]. Implementation experiences in Finland also suggested that EN systems function best when integrated into broader public health response activities rather than operating as stand-alone notification tools [<xref ref-type="bibr" rid="ref38">38</xref>]. Our findings on future system characteristics suggest integration with surveillance data&#x2014;extending prior work that proposed standardized evaluation metrics for EN systems [<xref ref-type="bibr" rid="ref13">13</xref>] and suggested that EN activity may support short-term outbreak forecasting and surveillance functions [<xref ref-type="bibr" rid="ref39">39</xref>]. Finally, our recommendation for structured working groups and stronger cross-sector coordination is reinforced by lessons from collaborative work in the United States during the COVID-19 pandemic, such as the MIT Lincoln Laboratory initiatives [<xref ref-type="bibr" rid="ref35">35</xref>] and DNA [<xref ref-type="bibr" rid="ref40">40</xref>], which emphasized iterative assessment, governance mechanisms, and sustained collaboration among PHAs, policymakers, and technology partners.</p></sec><sec id="s4-4"><title>Caveats and Limitations</title><p>Although this study is the first to systematically gather and synthesize data to outline actionable steps for strengthening EN systems, the findings should be interpreted with caution. First, our sampling strategy and modest sample size limit generalizability, particularly because most participants were based in the United States and only about half reported direct implementation experience.</p><p>Second, this study employed a type 3 Delphi approach to gather expert perspectives on enhancing EN systems as part of infectious disease response. By design, our modified Delphi approach included only a single round, which constrained our ability to capture a more iterative or comprehensive assessment. Unlike a type 4 Delphi that seeks structured consensus over multiple rounds, our goal was to surface areas of opportunity and identify priorities as health systems prepare for emerging and reemerging infectious disease outbreaks. Additional work is needed to further refine these priorities and inform next steps for advancing EN technologies.</p><p>Finally, although our analysis was not explicitly structured around an implementation science framework, the barriers and facilitators identified map closely onto commonly used domains&#x2014;such as contextual readiness, stakeholder engagement, and system integration&#x2014;and can guide future research that applies models like the CFIR (Consolidated Framework for Implementation Research) or RE-AIM (Reach, Effectiveness, Adoption, Implementation, and Maintenance) to digital public health interventions.</p></sec><sec id="s4-5"><title>Conclusion</title><p>EN systems have the potential to play a broader role in supporting ongoing public health responses to outbreaks beyond COVID-19. Our findings suggest that there are opportunities to adapt EN technologies into more flexible tools for future outbreaks. Achieving this mandate will require revisiting existing protocols, improving core functionalities, and addressing practical barriers that limit usability and integration with routine public health activities and cross-sectoral coordination.</p><p>Despite its limitations, our study helped identify priorities as a starting point for a roadmap to strengthen EN systems as part of preparedness for emerging and re-emerging infectious diseases. With system improvements, stronger coordination between technology and public health leaders, and continued evaluation, EN technologies can evolve into a more reliable and sustainable component of modern outbreak response.</p></sec></sec></body><back><ack><p>The authors thank the California Department of Public Health, University of California-San Francisco&#x2019;s Institute for Global Health Sciences Master of Science Program. The authors used generative AI tools, including Grammarly and ChatGPT (OpenAI, version 4.0), for limited language editing and proofreading under full human supervision. AI was not used for data analysis, interpretation, or generation of scientific content. All responsibility for the final manuscript rests with the authors. Use of AI was limited to selected sections of the Introduction and Discussion.</p></ack><notes><sec><title>Funding</title><p>This project was supported by the Resource Allocation Program (RAP) award, a University of California, San Francisco, internal funding mechanism.</p></sec><sec><title>Data Availability</title><p>The datasets generated or analyzed during this study are available from the corresponding author on reasonable request.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: MM</p><p>Data curation: CAM-L, NS</p><p>Formal analysis: CAM-L, NS</p><p>Methodology: MM</p><p>Project administration: NS, AB</p><p>Resources: AB</p><p>Supervision: MM</p><p>Visualization: CAM-L</p><p>Writing &#x2013; original draft: MM, CAM-L</p><p>Writing &#x2013; review &#x0026; editing: NS, RP, WBL</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>ABBREVIATIONS</title><def-list><def-item><term id="abb1">DCT</term><def><p>digital contact tracing</p></def></def-item><def-item><term id="abb2">DNA</term><def><p>Digital Notification Alliance</p></def></def-item><def-item><term id="abb3">EN</term><def><p>exposure notification</p></def></def-item><def-item><term id="abb4">GAEN</term><def><p>Google and Apple Exposure Notification system</p></def></def-item><def-item><term id="abb5">PHAs</term><def><p>public health agencies</p></def></def-item><def-item><term id="abb6">UCSF</term><def><p>University of California, San Francisco</p></def></def-item><def-item><term id="abb7">WHO</term><def><p>World Health Organization</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="web"><article-title>Coronavirus disease (COVID-19): contact tracing</article-title><source>World Health Organization</source><access-date>2025-01-10</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.who.int/news-room/questions-and-answers/item/coronavirus-disease-covid-19-contact-tracing">https://www.who.int/news-room/questions-and-answers/item/coronavirus-disease-covid-19-contact-tracing</ext-link></comment></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>Amicosante</surname><given-names>AMV</given-names> </name><name name-style="western"><surname>Rosso</surname><given-names>A</given-names> </name><name name-style="western"><surname>Bernardini</surname><given-names>F</given-names> </name><etal/></person-group><article-title>COVID-19 contact tracing strategies during the first wave of the pandemic: systematic review of published studies</article-title><source>JMIR Public Health Surveill</source><year>2023</year><month>06</month><day>23</day><volume>9</volume><fpage>e42678</fpage><pub-id pub-id-type="doi">10.2196/42678</pub-id><pub-id pub-id-type="medline">37351939</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>Nebeker</surname><given-names>C</given-names> </name><name name-style="western"><surname>Kareem</surname><given-names>D</given-names> </name><name name-style="western"><surname>Yong</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kunowski</surname><given-names>R</given-names> </name><name name-style="western"><surname>Malekinejad</surname><given-names>M</given-names> </name><name name-style="western"><surname>Aronoff-Spencer</surname><given-names>E</given-names> </name></person-group><article-title>Digital exposure notification tools: a global landscape analysis</article-title><source>PLOS Digit Health</source><year>2023</year><month>09</month><volume>2</volume><issue>9</issue><fpage>e0000287</fpage><pub-id pub-id-type="doi">10.1371/journal.pdig.0000287</pub-id><pub-id pub-id-type="medline">37656671</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>Alghamdi</surname><given-names>NS</given-names> </name><name name-style="western"><surname>Alghamdi</surname><given-names>SM</given-names> </name></person-group><article-title>The role of digital technology in curbing COVID-19</article-title><source>Int J Environ Res Public Health</source><year>2022</year><month>07</month><day>7</day><volume>19</volume><issue>14</issue><fpage>8287</fpage><pub-id pub-id-type="doi">10.3390/ijerph19148287</pub-id><pub-id pub-id-type="medline">35886139</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>Kim</surname><given-names>H</given-names> </name></person-group><article-title>COVID-19 apps as a digital intervention policy: a longitudinal panel data analysis in South Korea</article-title><source>Health Policy</source><year>2021</year><volume>125</volume><issue>11</issue><fpage>1430</fpage><lpage>1440</lpage><pub-id pub-id-type="doi">10.1016/j.healthpol.2021.07.003</pub-id><pub-id pub-id-type="medline">34301408</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>Bannister-Tyrrell</surname><given-names>M</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>M</given-names> </name><name name-style="western"><surname>Choi</surname><given-names>V</given-names> </name><name name-style="western"><surname>Miglietta</surname><given-names>A</given-names> </name><name name-style="western"><surname>Galea</surname><given-names>G</given-names> </name></person-group><article-title>Systematic scoping review of the implementation, adoption, use, and effectiveness of digital contact tracing interventions for COVID-19 in the Western Pacific Region</article-title><source>Lancet Reg Health West Pac</source><year>2023</year><month>05</month><volume>34</volume><fpage>100647</fpage><pub-id pub-id-type="doi">10.1016/j.lanwpc.2022.100647</pub-id><pub-id pub-id-type="medline">37256207</pub-id></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>Bair</surname><given-names>H</given-names> </name><name name-style="western"><surname>Wanger</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Shah</surname><given-names>NR</given-names> </name></person-group><article-title>A brief history of exposure notification during the COVID-19 pandemic in the United States, 2020-2021</article-title><source>Public Health Rep</source><year>2022</year><volume>137</volume><issue>2_suppl</issue><fpage>23S</fpage><lpage>28S</lpage><pub-id pub-id-type="doi">10.1177/00333549221099533</pub-id><pub-id pub-id-type="medline">35674242</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>O&#x2019;Connell</surname><given-names>J</given-names> </name><name name-style="western"><surname>Abbas</surname><given-names>M</given-names> </name><name name-style="western"><surname>Beecham</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Best practice guidance for digital contact tracing apps: a cross-disciplinary review of the literature</article-title><source>JMIR mHealth uHealth</source><year>2021</year><month>06</month><day>7</day><volume>9</volume><issue>6</issue><fpage>e27753</fpage><pub-id pub-id-type="doi">10.2196/27753</pub-id><pub-id pub-id-type="medline">34003764</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="web"><article-title>Exposure notification</article-title><source>Apple Developer</source><access-date>2025-04-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://developer.apple.com/exposure-notification/">https://developer.apple.com/exposure-notification/</ext-link></comment></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="web"><article-title>Privacy-preserving contact tracing</article-title><source>Apple</source><access-date>2025-04-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.apple.com/covid19/contacttracing">https://www.apple.com/covid19/contacttracing</ext-link></comment></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>Pegollo</surname><given-names>L</given-names> </name><name name-style="western"><surname>Maggioni</surname><given-names>E</given-names> </name><name name-style="western"><surname>Gaeta</surname><given-names>M</given-names> </name><name name-style="western"><surname>Odone</surname><given-names>A</given-names> </name></person-group><article-title>Characteristics and determinants of population acceptance of COVID-19 digital contact tracing: a systematic review</article-title><source>Acta Biomed</source><year>2021</year><month>12</month><day>10</day><volume>92</volume><issue>S6</issue><fpage>e2021444</fpage><pub-id pub-id-type="doi">10.23750/abm.v92iS6.12234</pub-id><pub-id pub-id-type="medline">34889313</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>Elmokashfi</surname><given-names>A</given-names> </name><name name-style="western"><surname>Sundnes</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kvalbein</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Nationwide rollout reveals efficacy of epidemic control through digital contact tracing</article-title><source>Nat Commun</source><year>2021</year><month>10</month><day>11</day><volume>12</volume><issue>1</issue><fpage>5918</fpage><pub-id pub-id-type="doi">10.1038/s41467-021-26144-8</pub-id><pub-id pub-id-type="medline">34635661</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>Aronoff-Spencer</surname><given-names>E</given-names> </name><name name-style="western"><surname>Nebeker</surname><given-names>C</given-names> </name><name name-style="western"><surname>Wenzel</surname><given-names>AT</given-names> </name><etal/></person-group><article-title>Defining key performance indicators for the California COVID-19 Exposure Notification System (CA Notify)</article-title><source>Public Health Rep</source><year>2022</year><volume>137</volume><issue>2_suppl</issue><fpage>67S</fpage><lpage>75S</lpage><pub-id pub-id-type="doi">10.1177/00333549221129354</pub-id><pub-id pub-id-type="medline">36314660</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>Prakash</surname><given-names>AV</given-names> </name><name name-style="western"><surname>Das</surname><given-names>S</given-names> </name></person-group><article-title>Explaining citizens&#x2019; resistance to use digital contact tracing apps: a mixed-methods study</article-title><source>Int J Inf Manage</source><year>2022</year><month>04</month><volume>63</volume><fpage>102468</fpage><pub-id pub-id-type="doi">10.1016/j.ijinfomgt.2021.102468</pub-id><pub-id pub-id-type="medline">36540570</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="web"><article-title>Apple and Google partner on COVID-19 contact tracing technology</article-title><source>News from Google</source><access-date>2025-01-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://blog.google/inside-google/company-announcements/apple-and-google-partner-covid-19-contact-tracing-technology/">https://blog.google/inside-google/company-announcements/apple-and-google-partner-covid-19-contact-tracing-technology/</ext-link></comment></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>Burdinski</surname><given-names>A</given-names> </name><name name-style="western"><surname>Brockmann</surname><given-names>D</given-names> </name><name name-style="western"><surname>Maier</surname><given-names>BF</given-names> </name></person-group><article-title>Understanding the impact of digital contact tracing during the COVID-19 pandemic</article-title><source>PLOS Digit Health</source><year>2022</year><month>12</month><volume>1</volume><issue>12</issue><fpage>e0000149</fpage><pub-id pub-id-type="doi">10.1371/journal.pdig.0000149</pub-id><pub-id pub-id-type="medline">36812611</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>Pozo-Martin</surname><given-names>F</given-names> </name><name name-style="western"><surname>Beltran Sanchez</surname><given-names>MA</given-names> </name><name name-style="western"><surname>M&#x00FC;ller</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Diaconu</surname><given-names>V</given-names> </name><name name-style="western"><surname>Weil</surname><given-names>K</given-names> </name><name name-style="western"><surname>El Bcheraoui</surname><given-names>C</given-names> </name></person-group><article-title>Comparative effectiveness of contact tracing interventions in the context of the COVID-19 pandemic: a systematic review</article-title><source>Eur J Epidemiol</source><year>2023</year><month>03</month><volume>38</volume><issue>3</issue><fpage>243</fpage><lpage>266</lpage><pub-id pub-id-type="doi">10.1007/s10654-023-00963-z</pub-id><pub-id pub-id-type="medline">36795349</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>Hossain</surname><given-names>AD</given-names> </name><name name-style="western"><surname>Jarolimova</surname><given-names>J</given-names> </name><name name-style="western"><surname>Elnaiem</surname><given-names>A</given-names> </name><name name-style="western"><surname>Huang</surname><given-names>CX</given-names> </name><name name-style="western"><surname>Richterman</surname><given-names>A</given-names> </name><name name-style="western"><surname>Ivers</surname><given-names>LC</given-names> </name></person-group><article-title>Effectiveness of contact tracing in the control of infectious diseases: a systematic review</article-title><source>Lancet Public Health</source><year>2022</year><month>03</month><volume>7</volume><issue>3</issue><fpage>e259</fpage><lpage>e273</lpage><pub-id pub-id-type="doi">10.1016/S2468-2667(22)00001-9</pub-id><pub-id pub-id-type="medline">35180434</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>Unim</surname><given-names>B</given-names> </name><name name-style="western"><surname>Zile-Velika</surname><given-names>I</given-names> </name><name name-style="western"><surname>Pavlovska</surname><given-names>Z</given-names> </name><etal/></person-group><article-title>The role of digital tools and emerging devices in COVID-19 contact tracing during the first 18 months of the pandemic: a systematic review</article-title><source>Eur J Public Health</source><year>2024</year><month>07</month><day>1</day><volume>34</volume><issue>Supplement_1</issue><fpage>i11</fpage><lpage>i28</lpage><pub-id pub-id-type="doi">10.1093/eurpub/ckae039</pub-id><pub-id pub-id-type="medline">38946444</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sujarwoto</surname><given-names>S</given-names> </name><name name-style="western"><surname>Maharani</surname><given-names>A</given-names> </name></person-group><article-title>Facilitators and barriers to the adoption of mHealth apps for COVID-19 contact tracing: a systematic review of the literature</article-title><source>Front Public Health</source><year>2023</year><volume>11</volume><fpage>1222600</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2023.1222600</pub-id><pub-id pub-id-type="medline">38145061</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Thomas Craig</surname><given-names>KJ</given-names> </name><name name-style="western"><surname>Rizvi</surname><given-names>R</given-names> </name><name name-style="western"><surname>Willis</surname><given-names>VC</given-names> </name><name name-style="western"><surname>Kassler</surname><given-names>WJ</given-names> </name><name name-style="western"><surname>Jackson</surname><given-names>GP</given-names> </name></person-group><article-title>Effectiveness of contact tracing for viral disease mitigation and suppression: evidence-based review</article-title><source>JMIR Public Health Surveill</source><year>2021</year><month>10</month><day>6</day><volume>7</volume><issue>10</issue><fpage>e32468</fpage><pub-id pub-id-type="doi">10.2196/32468</pub-id><pub-id pub-id-type="medline">34612841</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Barrat</surname><given-names>A</given-names> </name><name name-style="western"><surname>Cattuto</surname><given-names>C</given-names> </name><name name-style="western"><surname>Kivel&#x00E4;</surname><given-names>M</given-names> </name><name name-style="western"><surname>Lehmann</surname><given-names>S</given-names> </name><name name-style="western"><surname>Saram&#x00E4;ki</surname><given-names>J</given-names> </name></person-group><article-title>Effect of manual and digital contact tracing on COVID-19 outbreaks: a study on empirical contact data</article-title><source>J R Soc Interface</source><year>2021</year><month>05</month><volume>18</volume><issue>178</issue><fpage>20201000</fpage><pub-id pub-id-type="doi">10.1098/rsif.2020.1000</pub-id><pub-id pub-id-type="medline">33947224</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Salath&#x00E9;</surname><given-names>M</given-names> </name><name name-style="western"><surname>Althaus</surname><given-names>C</given-names> </name><name name-style="western"><surname>Anderegg</surname><given-names>N</given-names> </name><etal/></person-group><article-title>Early evidence of effectiveness of digital contact tracing for SARS-CoV-2 in Switzerland</article-title><source>Swiss Med Wkly</source><year>2020</year><month>12</month><volume>150</volume><fpage>w20457</fpage><pub-id pub-id-type="doi">10.4414/smw.2020.20457</pub-id><pub-id pub-id-type="medline">33327003</pub-id></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>Daniore</surname><given-names>P</given-names> </name><name name-style="western"><surname>Nittas</surname><given-names>V</given-names> </name><name name-style="western"><surname>Ballouz</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Performance of the Swiss digital contact-tracing app over various SARS-CoV-2 pandemic waves: repeated cross-sectional analyses</article-title><source>JMIR Public Health Surveill</source><year>2022</year><month>11</month><day>11</day><volume>8</volume><issue>11</issue><fpage>e41004</fpage><pub-id pub-id-type="doi">10.2196/41004</pub-id><pub-id pub-id-type="medline">36219833</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>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>e258</lpage><pub-id pub-id-type="doi">10.1016/S2468-2667(22)00010-X</pub-id><pub-id pub-id-type="medline">35131045</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>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><etal/></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>412</lpage><pub-id pub-id-type="doi">10.1038/s41586-021-03606-z</pub-id><pub-id pub-id-type="medline">33979832</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>Chow</surname><given-names>BWK</given-names> </name><name name-style="western"><surname>Lim</surname><given-names>YD</given-names> </name><name name-style="western"><surname>Poh</surname><given-names>RCH</given-names> </name><etal/></person-group><article-title>Use of a digital contact tracing system in Singapore to mitigate COVID-19 spread</article-title><source>BMC Public Health</source><year>2023</year><month>11</month><day>16</day><volume>23</volume><issue>1</issue><fpage>2253</fpage><pub-id pub-id-type="doi">10.1186/s12889-023-17150-0</pub-id><pub-id pub-id-type="medline">37974135</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>Jeon</surname><given-names>S</given-names> </name><name name-style="western"><surname>Rainisch</surname><given-names>G</given-names> </name><name name-style="western"><surname>Harris</surname><given-names>AM</given-names> </name><etal/></person-group><article-title>Estimated cases averted by COVID-19 digital exposure notification, Pennsylvania, USA, November 8, 2020&#x2013;January 2, 2021</article-title><source>Emerg Infect Dis</source><year>2023</year><month>02</month><volume>29</volume><issue>2</issue><fpage>426</fpage><lpage>430</lpage><pub-id pub-id-type="doi">10.3201/eid2902.220959</pub-id><pub-id pub-id-type="medline">36639132</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>Alanoca</surname><given-names>S</given-names> </name><name name-style="western"><surname>Guetta-Jeanrenaud</surname><given-names>N</given-names> </name><name name-style="western"><surname>Ferrari</surname><given-names>I</given-names> </name><name name-style="western"><surname>Weinberg</surname><given-names>N</given-names> </name><name name-style="western"><surname>&#x00C7;etin</surname><given-names>RB</given-names> </name><name name-style="western"><surname>Miailhe</surname><given-names>N</given-names> </name></person-group><article-title>Digital contact tracing against COVID-19: a governance framework to build trust</article-title><source>Int Data Priv Law</source><year>2021</year><month>05</month><day>5</day><volume>11</volume><issue>1</issue><fpage>3</fpage><lpage>17</lpage><pub-id pub-id-type="doi">10.1093/idpl/ipab001</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="report"><article-title>Health at a glance: Latin America and the Caribbean 2020</article-title><year>2020</year><access-date>2022-12-08</access-date><publisher-name>OECD Publishing</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2020/06/health-at-a-glance-latin-america-and-the-caribbean-2020_4f138987/6089164f-en.pdf">https://www.oecd.org/content/dam/oecd/en/publications/reports/2020/06/health-at-a-glance-latin-america-and-the-caribbean-2020_4f138987/6089164f-en.pdf</ext-link></comment></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="web"><article-title>How contact tracing and warning apps helped during the COVID-19 pandemic</article-title><source>European Commission</source><access-date>2025-01-11</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://commission.europa.eu/strategy-and-policy/coronavirus-response/travel-during-coronavirus-pandemic/contact-tracing-and-warning-apps-during-covid-19_en">https://commission.europa.eu/strategy-and-policy/coronavirus-response/travel-during-coronavirus-pandemic/contact-tracing-and-warning-apps-during-covid-19_en</ext-link></comment></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Niederberger</surname><given-names>M</given-names> </name><name name-style="western"><surname>Spranger</surname><given-names>J</given-names> </name></person-group><article-title>Delphi technique in health sciences: a map</article-title><source>Front Public Health</source><year>2020</year><volume>8</volume><fpage>457</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2020.00457</pub-id><pub-id pub-id-type="medline">33072683</pub-id></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>Humphrey-Murto</surname><given-names>S</given-names> </name><name name-style="western"><surname>Varpio</surname><given-names>L</given-names> </name><name name-style="western"><surname>Gonsalves</surname><given-names>C</given-names> </name><name name-style="western"><surname>Wood</surname><given-names>TJ</given-names> </name></person-group><article-title>Using consensus group methods such as Delphi and nominal group in medical education research</article-title><source>Med Teach</source><year>2017</year><month>01</month><volume>39</volume><issue>1</issue><fpage>14</fpage><lpage>19</lpage><pub-id pub-id-type="doi">10.1080/0142159X.2017.1245856</pub-id><pub-id pub-id-type="medline">27841062</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>Diamond</surname><given-names>IR</given-names> </name><name name-style="western"><surname>Grant</surname><given-names>RC</given-names> </name><name name-style="western"><surname>Feldman</surname><given-names>BM</given-names> </name><etal/></person-group><article-title>Defining consensus: a systematic review recommends methodologic criteria for reporting of Delphi studies</article-title><source>J Clin Epidemiol</source><year>2014</year><month>04</month><volume>67</volume><issue>4</issue><fpage>401</fpage><lpage>409</lpage><pub-id pub-id-type="doi">10.1016/j.jclinepi.2013.12.002</pub-id><pub-id pub-id-type="medline">24581294</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="web"><article-title>Automated exposure notification for COVID-19</article-title><source>MIT Lincoln Laboratory</source><access-date>2025-04-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.ll.mit.edu/r-d/publications/automated-exposure-notification-covid-19">https://www.ll.mit.edu/r-d/publications/automated-exposure-notification-covid-19</ext-link></comment></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="web"><source>Qualtrics XM</source><access-date>2025-04-28</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.qualtrics.com/">https://www.qualtrics.com/</ext-link></comment></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>Oyibo</surname><given-names>K</given-names> </name><name name-style="western"><surname>Sahu</surname><given-names>KS</given-names> </name><name name-style="western"><surname>Oetomo</surname><given-names>A</given-names> </name><name name-style="western"><surname>Morita</surname><given-names>PP</given-names> </name></person-group><article-title>Factors influencing the adoption of contact tracing applications: systematic review and recommendations</article-title><source>Front Digit Health</source><year>2022</year><volume>4</volume><fpage>862466</fpage><pub-id pub-id-type="doi">10.3389/fdgth.2022.862466</pub-id><pub-id pub-id-type="medline">35592459</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>Pihlajam&#x00E4;ki</surname><given-names>M</given-names> </name><name name-style="western"><surname>Wickstr&#x00F6;m</surname><given-names>S</given-names> </name><name name-style="western"><surname>Puranen</surname><given-names>K</given-names> </name><name name-style="western"><surname>Helve</surname><given-names>O</given-names> </name><name name-style="western"><surname>Yrttiaho</surname><given-names>A</given-names> </name><name name-style="western"><surname>Siira</surname><given-names>L</given-names> </name></person-group><article-title>Implementing and maintaining a SARS-CoV-2 exposure notification application for mobile phones: the Finnish experience</article-title><source>JMIR Public Health Surveill</source><year>2023</year><month>07</month><day>13</day><volume>9</volume><fpage>e46563</fpage><pub-id pub-id-type="doi">10.2196/46563</pub-id><pub-id pub-id-type="medline">37440286</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>Aronoff-Spencer</surname><given-names>E</given-names> </name><name name-style="western"><surname>Mazrouee</surname><given-names>S</given-names> </name><name name-style="western"><surname>Graham</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Exposure notification system activity as a leading indicator for SARS-CoV-2 caseload forecasting</article-title><source>PLOS One</source><year>2023</year><volume>18</volume><issue>8</issue><fpage>e0287368</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0287368</pub-id><pub-id pub-id-type="medline">37594936</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="web"><source>Digital Notification Alliance (DNA)</source><access-date>2026-05-08</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://dna-enx.org/">https://dna-enx.org/</ext-link></comment></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Supplementary study quality characteristics and Delphi survey questions.</p><media xlink:href="publichealth_v12i1e77763_app1.docx" xlink:title="DOCX File, 76 KB"/></supplementary-material></app-group></back></article>