<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="review-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v25i1e41168</article-id>
      <article-id pub-id-type="pmid">37145840</article-id>
      <article-id pub-id-type="doi">10.2196/41168</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>User Compliance With the Health Emergency and Disaster Management System: Systematic Literature Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Leung</surname>
            <given-names>Tiffany</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Tomczyk</surname>
            <given-names>Samuel</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Yon</surname>
            <given-names>Dong Keon</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Fitriani</surname>
            <given-names>Widia Resti</given-names>
          </name>
          <degrees>MKom</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Faculty of Computer Science</institution>
            <institution>Universitas Indonesia</institution>
            <addr-line>Jl Prof DR Sudjono D Pusponegoro</addr-line>
            <addr-line>Depok, 16424</addr-line>
            <country>Indonesia</country>
            <phone>62 85280114733</phone>
            <email>widiaresti@cs.ui.ac.id</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1022-6754</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Sutanto</surname>
            <given-names>Juliana</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1587-5948</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Handayani</surname>
            <given-names>Putu Wuri</given-names>
          </name>
          <degrees>Dr</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5341-3800</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Hidayanto</surname>
            <given-names>Achmad Nizar</given-names>
          </name>
          <degrees>Dr</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5793-9460</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Faculty of Computer Science</institution>
        <institution>Universitas Indonesia</institution>
        <addr-line>Depok</addr-line>
        <country>Indonesia</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department Human Centred Computing, Faculty of Information Technology</institution>
        <institution>Monash University</institution>
        <addr-line>Melbourne</addr-line>
        <country>Australia</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Widia Resti Fitriani <email>widiaresti@cs.ui.ac.id</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>5</day>
        <month>5</month>
        <year>2023</year>
      </pub-date>
      <volume>25</volume>
      <elocation-id>e41168</elocation-id>
      <history>
        <date date-type="received">
          <day>18</day>
          <month>7</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>30</day>
          <month>1</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>20</day>
          <month>3</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>30</day>
          <month>3</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Widia Resti Fitriani, Juliana Sutanto, Putu Wuri Handayani, Achmad Nizar Hidayanto. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 05.05.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2023/1/e41168" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Health-related hazards have a detrimental impact on society. The health emergency and disaster management system (Health EDMS), such as a contact-tracing application, is used to respond to and cope with health-related hazards. User compliance with Health EDMS warnings is key to its success. However, it was reported that user compliance with such a system remains low.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>Through a systematic literature review, this study aims to identify the theories and corresponding factors that explain user compliance with the warning message provided by Health EDMS.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The systematic literature review was conducted using Preferred Reporting Items for Systematic reviews and Meta-Analyses 2020 guidelines. The search was performed using the online databases Scopus, ScienceDirect, ProQuest, IEEE, and PubMed, for English journal papers published between January 2000 and February 2022.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 14 papers were selected for the review based on our inclusion and exclusion criteria. Previous research adopted 6 theories when examining user compliance, and central to the research was Health EDMS. To better understand Health EDMS, based on the literature reviewed, we mapped the activities and features of Health EDMS with the key stakeholders involved. We identified features that require involvement from individual users, which are surveillance and monitoring features and medical care and logistic assistance features. We then proposed a framework showing the individual, technological, and social influencing factors of the use of these features, which in turn affects compliance with the warning message from Health EDMS.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Research on the Health EDMS topic increased rapidly in 2021 due to the COVID-19 pandemic. An in-depth understanding of Health EDMS and user compliance before designing the system is essential for governments and developers to increase the effectiveness of Health EDMS. Through a systematic literature review, this study proposed a research framework and identified research gaps for future research on this topic.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health emergency and disaster management system</kwd>
        <kwd>systematic literature review</kwd>
        <kwd>user compliance</kwd>
        <kwd>theoretical lens</kwd>
        <kwd>influential factors</kwd>
        <kwd>contact-tracing application</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Emergencies and disasters threaten the safety of human life and trigger acute feelings of stress, anxiety, and uncertainty [<xref ref-type="bibr" rid="ref1">1</xref>]. The increasing number of disasters and the exposure of people and property to hazards have prompted an increased interest in and support for emergency and disaster management (EDM) policies and programs [<xref ref-type="bibr" rid="ref2">2</xref>]. The terms “emergency management” and “disaster management” are often used interchangeably. Disaster management is the organization, planning, and application of measures to prepare for, respond to, and recover from disasters [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. Meanwhile, emergency management is defined as a strategic management process to protect critical assets from hazards, save lives, minimize property or environmental damage, and reduce suffering [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. During disaster or emergency management, there is a need to coordinate the efforts within and across organizations and securely exchange data and share information through a system [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
        <p>Previous studies [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref11">11</xref>] have distinguished between the emergency management system (EMS) and the disaster management system (DMS). An EMS aims to handle emergency planning, control, and reduction with 3 essential components: hazard detection, emergency management, and public communication [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Meanwhile, a DMS consists of 3 application domains: monitoring, response, and forecasting the expected disasters [<xref ref-type="bibr" rid="ref10">10</xref>]. In addition, a DMS includes the functionality of information sharing, search and rescue missions, and damage assessment [<xref ref-type="bibr" rid="ref11">11</xref>]. In general, the functionality of the EMS and DMS follows the EDM phases, which are mitigation, preparedness, response, and recovery. This study uses the term “emergency and disaster management system” (EDMS) to cover all the EDM phases.</p>
        <p>With the increasing risk of emergency and disaster, research related to EDMSs is constantly evolving for various hazard types, including health-related hazards. Health-related hazards, such as disease outbreaks (eg, COVID-19, avian influenza, and Ebola), are 1 of the most common hazardous events [<xref ref-type="bibr" rid="ref9">9</xref>]. From 2012 to 2017, the World Health Organization (WHO) recorded more than 1200 outbreaks in 168 countries, including those due to new or re-emerging infectious diseases. In 2018, another 352 infectious disease events emerged. Several disease outbreaks are classified as Public Health Emergency for International Concern (PHEIC) by WHO, including the 2009 H1N1 influenza pandemic, Ebola (2013-2015 West African outbreak and 2018-2020 outbreak in the Democratic Republic of Congo), poliomyelitis (2014 to present), Zika (2016), and COVID-19 (2020 to now) [<xref ref-type="bibr" rid="ref7">7</xref>]. From the ongoing COVID-19 pandemic, there have been more than 349 million cases of COVID-19 worldwide, including more than 5.5 million deaths as of January 31, 2022 [<xref ref-type="bibr" rid="ref12">12</xref>]. Moreover, the International Monetary Fund estimates that the global economy shrunk by 4.4% in 2020 compared to 2019 due to the COVID-19 pandemic [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
        <p>Health-related hazards have different characteristics from natural disasters and disasters caused by humans. When a natural disaster or human-induced disaster occurs, people are advised to evacuate to a safe place. In contrast, during a pandemic, people must stay at home or be quarantined to prevent disease transmission [<xref ref-type="bibr" rid="ref14">14</xref>]. As infectious diseases spread quickly, they require fast and appropriate treatment [<xref ref-type="bibr" rid="ref14">14</xref>]. Various media and information sources, such as mass media, text messages, social media, and notifications in the community, can be used to disseminate warnings [<xref ref-type="bibr" rid="ref15">15</xref>]. During the COVID-19 pandemic, self-administered warning systems or applications, called contact-tracing applications (CTAs), have been widely used to disseminate alerts and recommendations [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. A CTA is a form of the health emergency and disaster management system (Health EDMS) that is used to prevent, prepare for, respond to, and deal with emergencies and disasters that threaten public health [<xref ref-type="bibr" rid="ref3">3</xref>]. Health EDMS can be applied to all stages of EDM, but the response stage requires user involvement the most. During the response phase, Health EDMS performs disease monitoring and tracing, provides medical care, and disseminates information and warnings [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref21">21</xref>]. Risk communication plays a vital role in attracting user attention and encouraging compliance to Health EDMS warnings.</p>
        <p>Understanding individual behavior toward Health EDMS is essential because health EDM is not solely the government's responsibility [<xref ref-type="bibr" rid="ref2">2</xref>]. Individuals are an integral part of the system as they are responsible for the health of themselves, their families, and their neighbors [<xref ref-type="bibr" rid="ref2">2</xref>]. Previous studies [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref30">30</xref>] have identified the factors driving individuals' adoption of Health EDMS. In addition to these studies, 2 literature reviews [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>] have summarized the determining factors of individuals' acceptance and adoption of Health EDMS. The first literature review compiled 25 studies of individuals' acceptance and adoption of a CTA. The second literature review conducted a systematic review of 21 national COVID-19 CTAs and verified CTA quality and public adoption [<xref ref-type="bibr" rid="ref32">32</xref>]. These reviews have shown that engagement could increase adoption and that there is an association between higher application adoption and lower infection rates [<xref ref-type="bibr" rid="ref32">32</xref>]. Several other literatures reviewed on the Health EDMS topic have discussed the privacy concerns [<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref35">35</xref>] and the digital solutions for dealing with the COVID-19 outbreak [<xref ref-type="bibr" rid="ref36">36</xref>,<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        <p>The extant literature reviews focus on the acceptance and adoption of Health EDMS. Although they have offered valuable insights into the development of studies in the Health EDMS field, little attention has been paid to how effective the warning message provided by Health EDMS generates user compliance [<xref ref-type="bibr" rid="ref38">38</xref>]. According to Han et al [<xref ref-type="bibr" rid="ref38">38</xref>], Abdelhamid et al [<xref ref-type="bibr" rid="ref39">39</xref>], and O’Malley et al [<xref ref-type="bibr" rid="ref40">40</xref>], compliance with warning messages sent by Health EDMS is crucial to determining the EDMS's effectiveness. Users who comply with Health EDMS's warning message play an active role in preventing disease transmission [<xref ref-type="bibr" rid="ref38">38</xref>]. However, the compliance rate is reported to be low in the context of health-related hazards [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Therefore, it is important to understand the factors affecting user compliance with Health EDMS's warning message. This paper addresses the following question: What theories and corresponding factors explain user compliance with the warning message provided by Health EDMS?</p>
        <p>To answer this question, we reviewed concepts related to hazards, the EDM cycle, and EDMS features from previous research to understand the activities and stakeholders involved in EDM. After that, we mapped the EDMS feature into a CTA to find out which EDMS features have been implemented to deal with health-related hazards. We also analyzed the roles and authorization of stakeholders in each feature to find out which features involve user participation and compliance. Through this mapping, this research can make a specific contribution regarding user participation in Health EDMS and compliance with Health EDMS’s warning message.</p>
        <p>Our systematic review followed the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) 2020 method because it has clear, structured, transparent, and complete reporting of systematic reviews [<xref ref-type="bibr" rid="ref42">42</xref>]. The target audience for this review was threefold: first, researchers who are interested in pursuing research on compliance with the warning message provided by Health EDMS; second, organizations and governments that need information about what related factors can influence the design and implementation of Health EDMS; and third, Health EDMS vendors or developers who would like to understand the sociotechnical factors affecting the compliance of warning messages prior to Health EDMS implementation.</p>
        <p>This paper is organized into 5 sections. Section 1 describes the research background and explains the key concepts, and the research methodology is discussed in Section 2. Next, the results and discussion of this study are elaborated in Sections 3 and 4. The final section concludes this study.</p>
      </sec>
      <sec>
        <title>Key Concepts</title>
        <sec>
          <title>Hazard</title>
          <p>Before discussing emergencies and disasters, it is important to understand the definition and classification of hazards. A hazard is a process, phenomenon, or human activity that can harm people's lives and health, damage property, disrupt social and economic activities, and damage the environment [<xref ref-type="bibr" rid="ref3">3</xref>]. The WHO classification of hazards generally consists of natural, human-induced, and environmental hazards, as provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> [<xref ref-type="bibr" rid="ref36">36</xref>].</p>
          <p>Hazards have the potential to create any scale of emergency or disaster. Emergency and disaster, at first glance, have a similar meaning, but there are fundamental differences between the two. An emergency can be defined as a severe disruption to the functioning of a community or society, causing human, material, economic, or environmental impacts, which can be overcome by the internal resources of the community and society itself [<xref ref-type="bibr" rid="ref43">43</xref>]. However, a disaster is a severe disturbance that impacts communities and society and cannot be overcome solely by relying on internal resources [<xref ref-type="bibr" rid="ref43">43</xref>]. In other words, a disaster is an event that causes significant damage or loss and thus requires resources beyond a community's capability and multiple agency responses [<xref ref-type="bibr" rid="ref44">44</xref>]. Thus, an event is declared a disaster if there is a need for external assistance to address its impact [<xref ref-type="bibr" rid="ref45">45</xref>]. Both emergencies and disasters must be managed to prevent or minimize their impacts.</p>
        </sec>
        <sec>
          <title>Emergency and Disaster Management</title>
          <p>To answer the research question, we need to understand the general concept of EDM. As previously mentioned, the terms “emergency management” and “disaster management” are often used interchangeably because they have considerable overlap [<xref ref-type="bibr" rid="ref3">3</xref>]. The EDM cycle consists of 4 phases, namely mitigation, preparedness, response, and recovery [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>], as shown in <xref rid="figure1" ref-type="fig">Figure 1</xref>. The mitigation and preparedness phases are part of risk assessments before a hazardous event [<xref ref-type="bibr" rid="ref45">45</xref>]. Mitigation is the application of actions to prevent a hazard from occurring or reduce its impact [<xref ref-type="bibr" rid="ref18">18</xref>]. Although the impact of a hazard is often not wholly preventable, various strategies and actions can substantially reduce its scale or severity. Activities during the mitigation phase include engineering techniques and hazard-resistant construction, environmental and social policy development, and public awareness enhancement [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>The EDM cycle. EDM: emergency and disaster management.</p>
            </caption>
            <graphic xlink:href="jmir_v25i1e41168_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>The second phase, preparedness, aims to prepare the community to respond to a hazard [<xref ref-type="bibr" rid="ref18">18</xref>] by providing information, creating partnerships, developing plans, building resources, and creating procedures [<xref ref-type="bibr" rid="ref47">47</xref>]. When a hazardous event occurs, response and recovery must be carried out [<xref ref-type="bibr" rid="ref45">45</xref>]. The response actions directly before, during, or immediately after a hazardous event occurs can save lives, reduce health impacts, ensure public safety, and meet the basic needs of the affected people [<xref ref-type="bibr" rid="ref3">3</xref>]. Activities during the response phase include evacuation, search and rescue, medical care, and temporary housing [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. The response activities may also extend to the recovery stage [<xref ref-type="bibr" rid="ref45">45</xref>]. Recovery is a long-term action taken after the immediate effects of a hazardous event have passed in order to stabilize society and return to normalcy [<xref ref-type="bibr" rid="ref18">18</xref>]. Recovery also aims to restore or improve the livelihoods and health of the affected populations and restore the economic, physical, social, cultural, and environmental systems [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
          <p>Each activity shown in <xref rid="figure1" ref-type="fig">Figure 1</xref> requires cooperation and coordination among the various parties, including the community, governments, health institutions, other groups, and regional and international organizations [<xref ref-type="bibr" rid="ref48">48</xref>]. The community includes at-risk populations, survivors, and community groups or organizations [<xref ref-type="bibr" rid="ref48">48</xref>]. Governments at all levels include leaders and politicians, ministries and agencies, national disaster management agencies, emergency services (eg, fire department, police, ambulance), and military service [<xref ref-type="bibr" rid="ref48">48</xref>]. The third stakeholder is health institutions, including the Ministry of Health and health authorities, health-related nongovernment organizations (NGOs), health care providers, hospitals and other health care facilities, the health workforce, and private sector health organizations and professionals [<xref ref-type="bibr" rid="ref48">48</xref>]. Other groups include universities and research institutes, nongovernment and volunteer groups, media, social media, new media, community influencers, and the private sector [<xref ref-type="bibr" rid="ref48">48</xref>]. Finally, regional and international organizations include WHO and international NGOs [<xref ref-type="bibr" rid="ref48">48</xref>].</p>
          <p>This research focuses on community stakeholders affected by health hazards. Individuals can contribute to community-level surveillance, household preparedness, first-aid training, and emergency response [<xref ref-type="bibr" rid="ref48">48</xref>]. Their active engagement in all aspects of EDM activities is vital [<xref ref-type="bibr" rid="ref48">48</xref>]. To encourage active participation from the community, EDM needs to implement effective risk communication to attract attention and encourage user compliance. A warning is a risk communication used to inform people about a hazard so that accidents, injuries, or unwanted consequences can be avoided [<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]. The purpose of warning messages is to draw the attention of people at risk, to reduce the time it takes to understand the warning, and to guide people to take appropriate protective measures [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. In this case, risk communication serves as a component of disaster control and strategies to reduce the health, economic, and psychosocial impacts of major disaster events [<xref ref-type="bibr" rid="ref40">40</xref>]. Risk communication is vital in all EDM phases, especially the response phase. The next section maps EDM phases and activities to EDMS features.</p>
        </sec>
        <sec>
          <title>Emergency and Disaster Management System</title>
          <p>Various studies have used different terms to describe the EDMS features for each of the 4 EDM phases. The term “emergency management system” is used by the United Nations [<xref ref-type="bibr" rid="ref4">4</xref>] and Landau [<xref ref-type="bibr" rid="ref54">54</xref>], which refers to a system that works for emergency planning, control, and reduction. The term “disaster management system” is used by Hannan et al [<xref ref-type="bibr" rid="ref55">55</xref>] and Currion et al [<xref ref-type="bibr" rid="ref56">56</xref>] as a system that aims to manage relief operations, recovery, and rehabilitation. The term “emergency response system“ is used by Amailef and Lu [<xref ref-type="bibr" rid="ref57">57</xref>] and refers to a system that supports communications, data gathering, data analysis, and decision-making during the response phase. Meanwhile, research by Edwards et al [<xref ref-type="bibr" rid="ref58">58</xref>] and Malizia et al [<xref ref-type="bibr" rid="ref59">59</xref>] uses the term “emergency notification system,” which refers to a system that aims to broadcast information to as many devices as possible. Other studies by Ouyang et al [<xref ref-type="bibr" rid="ref60">60</xref>] and Bonaretti and Fischer-Preßler [<xref ref-type="bibr" rid="ref61">61</xref>] use the term “early warning system,” which aims to disseminate warnings to a threatened population before or at an early stage of hazardous events. In the context of biological hazards that threaten public health, the terms “digital contact tracing” [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref62">62</xref>] and “contact-tracing application” [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref63">63</xref>] are used to refer to a system that monitors and tracks infection and provides immediate support and information during pandemics.</p>
          <p><xref ref-type="table" rid="table1">Tables 1</xref>-<xref ref-type="table" rid="table4">4</xref> map the activities and system features for each EDM phase and the stakeholders involved according to previous studies. The stakeholders consist of the community, governments, health institutions, other groups, and regional and international organizations. <xref ref-type="table" rid="table1">Tables 1</xref>-<xref ref-type="table" rid="table4">4</xref> also show the stakeholders' roles in each feature with the responsible, accountable, consulted, and informed (RACI) matrix. In this study, the RACI matrix was used to analyze stakeholders and their level of involvement and authorization in each feature of the EDMS. Because this research focused on community users, the RACI matrix showed which features require involvement from community users. From the 4 stages of EDM, 19 main activities and 42 EDMS features were identified. Among all the features identified, there were 27 features that require involvement from the community users that the other stakeholder groups should pay attention to in order to encourage user compliance with the warning messages.</p>
          <p>Based on <xref ref-type="table" rid="table1">Tables 1</xref>-<xref ref-type="table" rid="table4">4</xref>, community users can act as actors who are informed by or responsible for several features in an EDMS. Before a hazard occurs, community users can receive information about policies and strategies, potential hazards, and various types of education to increase their awareness of emergencies and disasters. When a hazard occurs, community users need information about the location of shelters, evacuation routes, and regular reports on ongoing disasters. During the response and recovery phases, community users play a more important role because in addition to obtaining information, they are also responsible for being actively involved in disaster management efforts. They must actively report disaster victims and missing persons, report tracing data and lab results, report damage to infrastructure, and request medical assistance and treatment. Community users who actively use EDMS features are encouraged to comply with the protocols and measures to deal with emergencies and disasters. Therefore, the design of these features is essential to drive user compliance.</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>System features and key stakeholders of an EDMS<sup>a</sup> for the mitigation (MT) activity.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="670"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="100"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Activity code and system feature</td>
                  <td colspan="5">Key stakeholders</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Co<sup>b</sup></td>
                  <td>G<sup>c</sup></td>
                  <td>H<sup>d</sup></td>
                  <td>O<sup>e</sup></td>
                  <td>Ro<sup>f</sup></td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="7">
                    <bold>MT1</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT1.1. Manage document repositories [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A<sup>g</sup></td>
                  <td>A<sup>h</sup></td>
                  <td>C<sup>i</sup></td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT1.2. Create maps [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>C</td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT1.3. Disseminate information to increase public awareness [<xref ref-type="bibr" rid="ref56">56</xref>]</td>
                  <td>I<sup>j</sup></td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>MT2</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT2.1. Identify possible hazards [<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>C</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT2.2. Assess vulnerability and impact of the hazard [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>C</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT2.3. Assess local capacity capability [<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>C</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>MT3</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT3.1. Develop mitigation strategy and policy [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>C</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT3.2. Manage data on zonation, land use, and hazard-resistant infrastructure [<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>N/A</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>MT4</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT4.1. Monitor and report the potential hazard [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>R<sup>k</sup></td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>MT4.2. Manage vaccination system data [<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>N/A</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table1fn1">
                <p><sup>a</sup>EDMS: emergency and disaster management system.</p>
              </fn>
              <fn id="table1fn2">
                <p><sup>b</sup>Co: community.</p>
              </fn>
              <fn id="table1fn3">
                <p><sup>c</sup>G: governments.</p>
              </fn>
              <fn id="table1fn4">
                <p><sup>d</sup>H: health institutions.</p>
              </fn>
              <fn id="table1fn5">
                <p><sup>e</sup>O: other groups.</p>
              </fn>
              <fn id="table1fn6">
                <p><sup>f</sup>Ro: regional and international organizations.</p>
              </fn>
              <fn id="table1fn7">
                <p><sup>g</sup>N/A: not applicable.</p>
              </fn>
              <fn id="table1fn8">
                <p><sup>h</sup>A: accountable.</p>
              </fn>
              <fn id="table1fn9">
                <p><sup>i</sup>C: consulted.</p>
              </fn>
              <fn id="table1fn10">
                <p><sup>j</sup>I: informed.</p>
              </fn>
              <fn id="table1fn11">
                <p><sup>k</sup>R: responsible.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>System features and key stakeholders of an EDMS<sup>a</sup> for the preparedness (PR) activity.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="670"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="100"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Activity code and system feature</td>
                  <td colspan="5">Key stakeholders</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Co<sup>b</sup></td>
                  <td>G<sup>c</sup></td>
                  <td>H<sup>d</sup></td>
                  <td>O<sup>e</sup></td>
                  <td>Ro<sup>f</sup></td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="7">
                    <bold>PR1</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR1.1. Manage a hazard database [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A<sup>g</sup></td>
                  <td>A<sup>h</sup></td>
                  <td>I<sup>i</sup></td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR1.2. Manage available resources and personnel database [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>PR2</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR2.1. Create an emergency and disaster plan [<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>C<sup>j</sup></td>
                  <td>N/A</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR2.2. Manage multiorganizational partnership and communication [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>R<sup>k</sup></td>
                  <td>R</td>
                  <td>R</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR2.3. Manage financial resources [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>PR3</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR3.1. Manage personnel recruitment and allocation [<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR3.2. Manage training and scenario data [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>PR4</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR4.1. Manage supplies and equipment procurement and storage [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>PR5</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR5.1. Monitor, detect, and report the potential hazard [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>C</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR5.2. Analyze spatial data [<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>C</td>
                  <td>N/A</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>PR5.3. Disseminate an early warning [<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref66">66</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>A</td>
                  <td>I</td>
                  <td>A</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>EDMS: emergency and disaster management system.</p>
              </fn>
              <fn id="table2fn2">
                <p><sup>b</sup>Co: community.</p>
              </fn>
              <fn id="table2fn3">
                <p><sup>c</sup>G: governments.</p>
              </fn>
              <fn id="table2fn4">
                <p><sup>d</sup>H: health institutions.</p>
              </fn>
              <fn id="table2fn5">
                <p><sup>e</sup>O: other groups.</p>
              </fn>
              <fn id="table2fn6">
                <p><sup>f</sup>Ro: regional and international organizations.</p>
              </fn>
              <fn id="table2fn7">
                <p><sup>g</sup>N/A: not applicable.</p>
              </fn>
              <fn id="table2fn8">
                <p><sup>h</sup>A: accountable.</p>
              </fn>
              <fn id="table2fn9">
                <p><sup>i</sup>I: informed.</p>
              </fn>
              <fn id="table2fn10">
                <p><sup>j</sup>C: consulted.</p>
              </fn>
              <fn id="table2fn11">
                <p><sup>k</sup>R: responsible.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>System features and key stakeholders of an EDMS<sup>a</sup> for the response (RS) activity.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="670"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="100"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Activity code and system feature</td>
                  <td colspan="5">Key stakeholders</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Co<sup>b</sup></td>
                  <td>G<sup>c</sup></td>
                  <td>H<sup>d</sup></td>
                  <td>O<sup>e</sup></td>
                  <td>Ro<sup>f</sup></td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RS1</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS1.1. Manage shelter and response organization data [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>I<sup>g</sup></td>
                  <td>A<sup>h</sup></td>
                  <td>R<sup>i</sup></td>
                  <td>R</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS1.2. Manage missing person and victim data [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>R</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS1.3. Track personnel location [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>R</td>
                  <td>R</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RS2</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS2.1. Monitor and report the ongoing hazard [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C<sup>j</sup></td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS2.2. Disseminate the warning and notification [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS2.3. Share timely, credible, and actionable information to the public through various channels (eg, mass media, social media) [<xref ref-type="bibr" rid="ref19">19</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RS3</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS3.1. Manage evacuation data [<xref ref-type="bibr" rid="ref67">67</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>R</td>
                  <td>R</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS3.2. Manage request data to deliver assistance and aid supplies for threatened populations and field respondents [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>R</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RS4</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td> RS4.1. Manage tracing data [<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS4.2. Manage first-aid and medical treatment data [<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS4.3. Manage laboratory test data [<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RS5</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS5.1. Manage situational reports related to infrastructure damage [<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>N/A<sup>k</sup></td>
                  <td>R</td>
                  <td>I</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>EDMS: emergency and disaster management system.</p>
              </fn>
              <fn id="table3fn2">
                <p><sup>b</sup>Co: community.</p>
              </fn>
              <fn id="table3fn3">
                <p><sup>c</sup>G: governments.</p>
              </fn>
              <fn id="table3fn4">
                <p><sup>d</sup>H: health institutions.</p>
              </fn>
              <fn id="table3fn5">
                <p><sup>e</sup>O: other groups.</p>
              </fn>
              <fn id="table3fn6">
                <p><sup>f</sup>Ro: regional and international organizations.</p>
              </fn>
              <fn id="table3fn7">
                <p><sup>g</sup>I: informed.</p>
              </fn>
              <fn id="table3fn8">
                <p><sup>h</sup>A: accountable.</p>
              </fn>
              <fn id="table3fn9">
                <p><sup>i</sup>R: responsible.</p>
              </fn>
              <fn id="table3fn10">
                <p><sup>j</sup>C: consulted.</p>
              </fn>
              <fn id="table3fn11">
                <p><sup>k</sup>N/A: not applicable.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>System features and key stakeholders of an EDMS<sup>a</sup> for the recovery (RC) activity.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="670"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="50"/>
              <col width="100"/>
              <thead>
                <tr valign="top">
                  <td colspan="2">Activity code and system feature</td>
                  <td colspan="5">Key stakeholders</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>Co<sup>b</sup></td>
                  <td>G<sup>c</sup></td>
                  <td>H<sup>d</sup></td>
                  <td>O<sup>e</sup></td>
                  <td>Ro<sup>f</sup></td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RC1</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC1.1. Collect data on the hazardous event and impacted population [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>N/A<sup>g</sup></td>
                  <td>A<sup>h</sup></td>
                  <td>C<sup>i</sup></td>
                  <td>C</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC1.2. Create reports related to the responses [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>I<sup>j</sup></td>
                  <td>A</td>
                  <td>I</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RC2</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC2.1. Assess infrastructure and lifeline service damage [<xref ref-type="bibr" rid="ref69">69</xref>]</td>
                  <td>N/A</td>
                  <td>A</td>
                  <td>N/A</td>
                  <td>I</td>
                  <td>I</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC2.2. Manage data of infrastructure and lifeline services rebuilding [<xref ref-type="bibr" rid="ref18">18</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>N/A</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RC3</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC3.1. Manage continuous tracing or mapping of case data [<xref ref-type="bibr" rid="ref21">21</xref>]</td>
                  <td>R<sup>k</sup></td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC3.2. Manage continuous medical treatment and mental health care [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC3.3. Manage continuous laboratory testing data [<xref ref-type="bibr" rid="ref20">20</xref>]</td>
                  <td>R</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RC4</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC4.1. Manage continuous monitoring and reporting of hazards [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>R</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
                <tr valign="top">
                  <td colspan="7">
                    <bold>RC5</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC5.1. Manage lessons learned data [<xref ref-type="bibr" rid="ref64">64</xref>]</td>
                  <td>I</td>
                  <td>A</td>
                  <td>C</td>
                  <td>I</td>
                  <td>C</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>EDMS: emergency and disaster management system.</p>
              </fn>
              <fn id="table4fn2">
                <p><sup>b</sup>Co: community.</p>
              </fn>
              <fn id="table4fn3">
                <p><sup>c</sup>G: governments.</p>
              </fn>
              <fn id="table4fn4">
                <p><sup>d</sup>H: health institutions.</p>
              </fn>
              <fn id="table4fn5">
                <p><sup>e</sup>O: other groups.</p>
              </fn>
              <fn id="table4fn6">
                <p><sup>f</sup>Ro: regional and international organizations.</p>
              </fn>
              <fn id="table4fn7">
                <p><sup>g</sup>N/A: not applicable.</p>
              </fn>
              <fn id="table4fn8">
                <p><sup>h</sup>A: accountable.</p>
              </fn>
              <fn id="table4fn9">
                <p><sup>i</sup>C: consulted.</p>
              </fn>
              <fn id="table4fn10">
                <p><sup>j</sup>I: informed.</p>
              </fn>
              <fn id="table4fn11">
                <p><sup>k</sup>R: responsible.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Health Emergency and Disaster Management System</title>
          <p>All the features analyzed in the previous section are used in a general EDMS dealing with all types of emergencies and disasters. To find out how these features have been used to address health-related disasters, we investigated their application to Health EDMS, an EDMS that is specifically used to respond to and cope with hazardous events that threaten public health. During the COVID-19 pandemic, Health EDMS was used by multiple countries to assist in contact tracing. Contact tracing is a control measure to prevent further disease transmission [<xref ref-type="bibr" rid="ref70">70</xref>]. When someone tests positive for COVID-19, that person must be quarantined or self-isolated. After that, the contact-tracing process is carried out by identifying the person's close contacts and advising them to take precautionary self-isolation [<xref ref-type="bibr" rid="ref71">71</xref>]. Close contact means direct face-to-face contact with an infected person or confirmed case [<xref ref-type="bibr" rid="ref71">71</xref>]. Various countries have developed contact-tracing mechanisms with technology support. A CTA allows devices to communicate through Bluetooth technology, GPS, wireless technology, and sensors [<xref ref-type="bibr" rid="ref71">71</xref>]. A CTA has features to automate contact-tracing activities and other features to disseminate information and provide medical care [<xref ref-type="bibr" rid="ref70">70</xref>].</p>
          <p>In this study, the discussion of Health EDMS will focus on a CTA because a CTA is a clear example of a technology application that deals with health emergencies and disasters. As a self-administered warning system, CTAs have been widely used in more than 50 countries [<xref ref-type="bibr" rid="ref72">72</xref>]. A CTA is implemented when COVID-19 emerges in order to respond to and recover from the pandemic [<xref ref-type="bibr" rid="ref16">16</xref>]. Therefore, the system features are geared more toward the response and recovery phases than the mitigation and preparedness phases. <xref ref-type="table" rid="table5">Table 5</xref> displays a list of features for response and recovery phases in some CTAs implemented by different countries. The countries shown were selected based on the number of COVID-19 cases: high (the United States and India), medium (the United Kingdom and France), and low (Singapore and Switzerland) [<xref ref-type="bibr" rid="ref73">73</xref>]. In addition to the number of cases, these countries were also chosen to represent the Americas, Europe, and Asia regions. The CTAs selected are available on Apple App Store and Google Play Store with the most significant number of users, free of cost, and launched and supported by the governments of selected countries [<xref ref-type="bibr" rid="ref73">73</xref>]. The CTA features in the selected countries were based on the information provided by Alanzi [<xref ref-type="bibr" rid="ref16">16</xref>] and Blasimme et al [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
          <p>There are 6 CTAs reviewed in <xref ref-type="table" rid="table5">Table 5</xref>. PathCheck SafePlace is a CTA developed in the United States that aims to integrate people and health departments to prevent the spread of COVID-19 by sharing information [<xref ref-type="bibr" rid="ref16">16</xref>]. The application was developed by the Massachusetts Institute of Technology, TripleBlind, and a nonprofit organization called PathCheck Foundation [<xref ref-type="bibr" rid="ref16">16</xref>]. Aarogya Setu is an official CTA launched by the Indian government with more than 1.4 million users [<xref ref-type="bibr" rid="ref16">16</xref>]. NHS COVID19 is a CTA launched by the National Health Service (NHS) Test and Trace in the United Kingdom [<xref ref-type="bibr" rid="ref16">16</xref>]. Although this application does not store personal information, it still collects location information for track and trace purposes [<xref ref-type="bibr" rid="ref16">16</xref>]. TousAntiCovid is implemented in France using a centralized IT architecture where data are stored on centralized servers run by the national health authorities [<xref ref-type="bibr" rid="ref17">17</xref>]. Users must enter their personal information to report a positive test, which triggers a notification to other users [<xref ref-type="bibr" rid="ref17">17</xref>]. The health authorities in France send an exposure code to users via email and post [<xref ref-type="bibr" rid="ref17">17</xref>]. In contrast to TousAntiCovid, SwissCovid implements a decentralized protocol like in other European countries, such as the United Kingdom [<xref ref-type="bibr" rid="ref66">66</xref>]. Users must contact health authorities to activate an exposure code after receiving a notification of a positive test result [<xref ref-type="bibr" rid="ref66">66</xref>]. Another application, TraceTogether, is an official CTA launched by the Singapore government [<xref ref-type="bibr" rid="ref16">16</xref>]. This application emphasizes user privacy by using anonymous IDs and giving users the right to delete their data [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>CTA<sup>a</sup> features.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="120"/>
              <col width="0"/>
              <col width="160"/>
              <col width="0"/>
              <col width="110"/>
              <col width="0"/>
              <col width="140"/>
              <col width="0"/>
              <col width="120"/>
              <col width="0"/>
              <col width="120"/>
              <col width="0"/>
              <col width="200"/>
              <thead>
                <tr valign="top">
                  <td colspan="3">EDMS<sup>b</sup> feature code</td>
                  <td colspan="2">PathCheck SafePlace (United States)</td>
                  <td colspan="2">Aarogya Setu (India)</td>
                  <td colspan="2">NHS<sup>c</sup> COVID19 (United Kingdom)</td>
                  <td colspan="2">TousAntiCovid (France)</td>
                  <td colspan="2">Trace Together (Singapore)</td>
                  <td>SwissCovid (Switzerland)</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td colspan="14">
                    <bold>Response (RS)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS1.1</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS1.2</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS1.3</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS2.1</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS2.2</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS2.3</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS3.1</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS3.2</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">No</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS4.1</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS4.2</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">No</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS4.3</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RS5.1</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td colspan="14">
                    <bold>Recovery (RC)</bold>
                  </td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC1.1</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC1.2</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC2.1</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC2.2</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC3.1</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC3.2</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">No</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC3.3</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC4.1</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">Yes</td>
                  <td colspan="2">No</td>
                </tr>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>RC5.1</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                  <td colspan="2">Unknown</td>
                </tr>
                <tr valign="top">
                  <td colspan="3">Total “yes,” n</td>
                  <td colspan="2">11</td>
                  <td colspan="2">11</td>
                  <td colspan="2">10</td>
                  <td colspan="2">5</td>
                  <td colspan="2">8</td>
                  <td>2</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>CTA: contact-tracing application.</p>
              </fn>
              <fn id="table5fn2">
                <p><sup>b</sup>EDMS: emergency and disaster management system.</p>
              </fn>
              <fn id="table5fn3">
                <p><sup>c</sup>NHS: National Health Service.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>Based on <xref ref-type="table" rid="table5">Table 5</xref>, at the most, the CTAs implemented 11 EDMS features in 5 EDM activities: response (RS)2, RS3, RS4, recovery (RC)3, and RC4. Most CTAs implemented all 3 features in RS2 to monitor and report the ongoing hazard; disseminate notifications and warnings; and provide timely, credible, and actionable information to the public. The CTAs also provide data visualization that enables users to monitor the ongoing status of the COVID-19 cases in their areas. Some CTAs (ie, PathCheck SafePlace, and Aarogya Setu, provide query resolution feature as part of RS3, allowing users to request help and ask questions through the applications [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
          <p>Medical care provision (RS4) is 1 of the priority features in CTAs. CTAs provide automatic contact-tracing tools integrated with location mapping through GPS. Aarogya Setu integrates these tools with an electronic pass (e-pass) in transportation and public places [<xref ref-type="bibr" rid="ref16">16</xref>]. CTAs also provide users with self-assessment tools to check their health status and exposure to COVID-19. Health institutions provide laboratory check reports to users through their handheld devices. Some CTAs(ie, PathCheck SafePlace and Aarogya Setu) also come with online consultation and appointment scheduling with health facilities [<xref ref-type="bibr" rid="ref16">16</xref>]. The medical care and surveillance activities continue to the recovery phases in RC3 and RC4.</p>
          <p>In the previous section, there were 27 EDMS features that involved the user community. Meanwhile, <xref ref-type="table" rid="table5">Table 5</xref> shows that only 11 have been implemented in Health EDMS, mainly functioning to monitor and report ongoing hazards and provide medical care and logistical support. Health EDMS does not implement all the features at the mitigation and preparedness stages. Several features in the response and recovery phases are also not implemented because they are not in accordance with the scope of health-related hazards, such as shelter data management, reporting of victims and missing persons, and recording of infrastructure damage. In Health EDMS, all the measures need to be complied with by the users to make them effective in controlling the pandemic [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. When surveillance and monitoring tools detect hazardous conditions, Health EDMS disseminates notifications and warnings to users. User compliance with notifications and warnings determines the success of Health EDMS. The following section discusses user compliance in the information system (IS) context.</p>
        </sec>
        <sec>
          <title>Compliance</title>
          <p>Compliance refers to the agreement with the expectations stated in the rules, standards, proposals, requests, orders, or suggestions [<xref ref-type="bibr" rid="ref74">74</xref>]. It is also defined as a relationship consisting of the power used by superiors to control subordinates and subordinates' orientation to this power [<xref ref-type="bibr" rid="ref75">75</xref>]. Compliance can include approval as well as obedience [<xref ref-type="bibr" rid="ref74">74</xref>]. In health care, compliance is conceptualized as a cognitive-motivational process of personal attitudes and intentions, behaviors, and the outcome of patient-practitioner interactions [<xref ref-type="bibr" rid="ref76">76</xref>]. It also involves professional power over the patient [<xref ref-type="bibr" rid="ref76">76</xref>]. Compliance is not based solely on an individual risk-benefit assessment but also involves relationships between commanders and followers and between organizations and members [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
          <p>Research on compliance has been investigated in various fields, and theories regarding compliance also come from multiple domains, such as psychology, criminology, health, management, and organization [<xref ref-type="bibr" rid="ref77">77</xref>]. In the organizational context, business dynamism and IT advancements encourage companies to frequently update their IS and its usage policy [<xref ref-type="bibr" rid="ref78">78</xref>]. In this case, users need to maintain IS compliance behavior due to the interdependent nature of tasks that need to be accomplished through IS [<xref ref-type="bibr" rid="ref78">78</xref>]. Social (trust and support) and performance (discipline and stretch) management influences collective compliance with IS [<xref ref-type="bibr" rid="ref78">78</xref>]. Compliance also has been widely studied in IS security policy research [<xref ref-type="bibr" rid="ref38">38</xref>]. Employees are willing to comply with IS security policy if they feel they have the capacity to carry out a security task, have a positive attitude in carrying it out, and see others performing the same security task [<xref ref-type="bibr" rid="ref77">77</xref>]. When they encounter a security threat, they evaluate the threat and coping behavior to decide whether to comply [<xref ref-type="bibr" rid="ref77">77</xref>]. Employee compliance with IS and its usage policy is critical to achieving IS objectives in supporting business operations [<xref ref-type="bibr" rid="ref78">78</xref>].</p>
          <p>Health EDMS differs from other ISs as it is used in life-critical and time-sensitive situations, often with limited resources. Immediate compliance with the health notifications and warnings is essential to save lives [<xref ref-type="bibr" rid="ref38">38</xref>]. When a person receives a warning, the warning response can be sequenced as follows: listen to the warning, understand the content of the warning message, believe that the warning is credible and accurate, personalize the warning, confirm the warning, and respond by taking protective action [<xref ref-type="bibr" rid="ref79">79</xref>]. Previous studies have shown that responses to warning messages are influenced by the type of hazard, the message and its source, the medium or channel through which the message is communicated, the characteristics of the recipient, and situational or environmental factors [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref79">79</xref>]. We conducted a systematic literature review to map the extant studies on user compliance with Health EDMS.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Search Strategy</title>
        <p>A systematic literature review is a secondary study conducted to identify, evaluate, and interpret all available research relevant to a particular research question, topic area, or phenomenon of interest [<xref ref-type="bibr" rid="ref80">80</xref>]. A systematic literature review summarizes the existing research insights, identifies research gaps, suggests areas for further investigation, or provides a framework to position new research activities [<xref ref-type="bibr" rid="ref81">81</xref>]. Our systematic review was conducted using PRISMA 2020 guidelines [<xref ref-type="bibr" rid="ref42">42</xref>]. The PRISMA checklist can be seen in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
        <p>The search was conducted using the online databases Scopus, ScienceDirect, ProQuest, IEEE, and PubMed. The keywords or search strings used to search the papers were (“emergency” OR “disaster” OR “response” OR “notification” OR “warning” OR “alert” OR “tracing”) AND (“system” OR “apps” OR “application”) AND (“compliance”). The search was conducted for journal papers published between January 2000 and February 2022.</p>
      </sec>
      <sec>
        <title>Inclusion and Exclusion Criteria</title>
        <p>The inclusion criteria were the review guidelines for study selection, as displayed in <xref ref-type="table" rid="table6">Table 6</xref>: be published in a journal, have full text available, and be written in English. In addition, in accordance with the objectives of this study, the papers had to discuss compliance with the warning or alert from Health EDMS and focus on individual perceptions or behaviors on Health EDMS. Therefore, papers with related terms, such as “emergency management system,” “disaster management system,” “emergency notification system,” “emergency warning system,” “emergency response system,” and “contact-tracing application,” were also included in this review. We did not include the keywords “mobile health” or “mHealth” because these applications are not used specifically for health emergencies and disasters but are for everyday use, which was not the scope of this research. This study was limited to a review of previous research on compliance from a user perspective and did not include the technical design of Health EDMS.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Inclusion and exclusion criteria.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="160"/>
            <col width="300"/>
            <col width="540"/>
            <thead>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inclusion criteria</td>
                <td>Exclusion criteria</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Paper type</td>
                <td>Journal paper</td>
                <td>Other than journal paper (eg, conference paper, book, editorial)</td>
              </tr>
              <tr valign="top">
                <td>Language</td>
                <td>English</td>
                <td>Other than English</td>
              </tr>
              <tr valign="top">
                <td>Publication date</td>
                <td>January 2000-February 2022</td>
                <td>Before January 2000 and after February 2022</td>
              </tr>
              <tr valign="top">
                <td>Topic</td>
                <td>User compliance with Health EDMS<sup>a</sup></td>
                <td> Compliance with health behavior without the use of the system or application, organization compliance, and technical design of Health EDMS</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table6fn1">
              <p><sup>a</sup>EDMS: emergency and disaster management system.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Study Selection</title>
        <p>The study selection was carried out as follows:</p>
        <list list-type="bullet">
          <list-item>
            <p>Step 1: The keyword or search string was searched in the aforementioned online databases. We limited the search to the abstract, title, or keyword fields. Duplicate records were removed.</p>
          </list-item>
          <list-item>
            <p>Step 2: The title and abstract of the identified papers were reviewed based on the inclusion criteria. Papers that did not meet inclusion criteria were removed.</p>
          </list-item>
          <list-item>
            <p>Step 3: The remaining papers were read in full to determine whether they met the inclusion criteria.</p>
          </list-item>
        </list>
      </sec>
      <sec>
        <title>Data Items and Synthesis</title>
        <p>The data extraction process aimed to identify relevant information from the included studies that pertained to our research question. This process included producing a Microsoft Excel data sheet consisting of key aspects related to the research aim. The following data were extracted from each publication: title, author(s), year of publication, name of the journal, country, topic, research question or objective, factor(s), method, recommendation, finding, and research gap. Each paper's full text was read, and the research data were entered into the Excel sheet. Once the extraction was completed, the Excel sheet was reviewed, and then the findings of the studies were analyzed to answer the research question. The results of the review are discussed in the next section.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Review Process</title>
        <p>The selected electronic databases were searched following the previously explained search strategy. In total, 618 papers were retrieved. Next, duplicate papers were removed, resulting in 573 (92.7%) papers. The papers' titles and abstracts were reviewed by applying the inclusion criteria. After removing the papers that did not fulfill the inclusion criteria, we were left with 95 (16.6%) papers. Next, the papers' full texts were read to ensure they covered the predefined scope. This step resulted in 14 (14.7%) selected papers. A summary table of the characteristics of the included studies is provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. <xref rid="figure2" ref-type="fig">Figure 2</xref> shows the review process using PRISMA guidelines.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>PRISMA flow diagram. EDMS: emergency and disaster management system; PRISMA: Preferred Reporting Items for Systematic Reviews and Meta-Analyses.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e41168_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Study Characteristics</title>
        <p>The included papers showed that Health EDMS research was conducted in the United States (n=5, 35.7%), the United Kingdom (n=2, 14.3%), China (n=2, 14.3%), Switzerland (n=1, 7.1%), France (n=1, 7.1%), Germany (n=1, 7.1%), South Korea (n=1, 7.1%), and Israel (n=1, 7.1%). <xref rid="figure3" ref-type="fig">Figure 3</xref> shows the distribution of the papers by country.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Distribution of papers based on country.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e41168_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>From 2004 to 2022, 14 studies on user compliance with Health EDMS were found. There were relatively few studies before 2021. Research on Health EDMS compliance increased rapidly in 2021 (there were 7, 50.0%, studies) due to the COVID-19 pandemic. The COVID-19 pandemic has led to many studies on user compliance with CTAs, EDMSs for handling health-related emergencies and disasters.</p>
        <p>Related to the sources of publications, 2 (14.3%) papers were published in the <italic>Journal of Medical Internet Research</italic> and 1 (7.1%) paper each was published in the following journals: <italic>MIS Quarterly</italic>, <italic>AIS Transactions on Replication Research</italic>, <italic>Applied Ergonomics</italic>, <italic>BMJ Open</italic>, <italic>Disaster Medicine and Public Health Preparedness</italic>, <italic>Disasters</italic>, <italic>Frontiers in Psychology</italic>, <italic>Human Factors</italic>, <italic>Humanities and Social Sciences Communications</italic>, <italic>International Journal of Disaster Risk Reduction</italic>, <italic>Public Health</italic>, and <italic>Public Relations Review</italic>. These papers used the quantitative research method (n=11, 78.6%), mixed method (n=1, 7.1%), and conceptual method (n=2, 14.3%). The papers that applied quantitative methods used surveys (n=7, 50.0%) and experiments (n=4, 28.6%) to collect data. The 1 (7.1%) paper that applied a mixed method used a combination of experiments (quantitative) and focus group discussions (qualitative). In addition, 2 (14.3%) conceptual papers developed arguments about concept associations.</p>
      </sec>
      <sec>
        <title>Theoretical Lens of User Compliance with Health EDMS</title>
        <p>The theories used in Health EDMS compliance research (<xref ref-type="table" rid="table7">Table 7</xref>) include the protective action decision model (PADM), Etzioni's compliance theory, the Health Belief Model (HBM), protection motivation theory (PMT), social amplification of risk framework (SARF), extension of the technology acceptance model (TAM2), and the theory of planned behavior (TPB). Of the 14 papers in this review, 5 (35.7%) did not use any theory to analyze compliance factors, 2 (14.3) were conceptual papers [<xref ref-type="bibr" rid="ref82">82</xref>,<xref ref-type="bibr" rid="ref83">83</xref>], and the others applied selected concepts or themes from previous studies. To investigate compliance with Health EDMS, Freberg [<xref ref-type="bibr" rid="ref84">84</xref>] examined the message source and message reliability; Albrecht et al [<xref ref-type="bibr" rid="ref85">85</xref>] examined risk perception, risk preference, and social preference; and Panchal et al [<xref ref-type="bibr" rid="ref86">86</xref>] examined security and privacy concerns, information content, usability, and knowledge of the application. Next, we elaborate on each of the theories used in Health EDMS compliance research.</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>Theoretical lenses to investigate compliance with Health EDMS<sup>a</sup>.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="420"/>
            <col width="200"/>
            <col width="380"/>
            <thead>
              <tr valign="top">
                <td>Theory</td>
                <td>Papers (N=14), n (%)</td>
                <td>Reference(s)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>PADM<sup>b</sup></td>
                <td>3 (21.4)</td>
                <td>[<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref87">87</xref>]</td>
              </tr>
              <tr valign="top">
                <td>Etzioni’s compliance theory</td>
                <td>2 (14.3)</td>
                <td>[<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td>
              </tr>
              <tr valign="top">
                <td>HBM<sup>c</sup></td>
                <td>2 (14.3)</td>
                <td>[<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref88">88</xref>]</td>
              </tr>
              <tr valign="top">
                <td>PMT<sup>d</sup></td>
                <td>2 (14.3)</td>
                <td>[<xref ref-type="bibr" rid="ref89">89</xref>,<xref ref-type="bibr" rid="ref90">90</xref>]</td>
              </tr>
              <tr valign="top">
                <td>SARF<sup>e</sup></td>
                <td>1 (7.1)</td>
                <td>[<xref ref-type="bibr" rid="ref15">15</xref>]</td>
              </tr>
              <tr valign="top">
                <td>TAM2<sup>f</sup></td>
                <td>1 (7.1)</td>
                <td>[<xref ref-type="bibr" rid="ref27">27</xref>]</td>
              </tr>
              <tr valign="top">
                <td>TPB<sup>g</sup></td>
                <td>1 (7.1)</td>
                <td> [<xref ref-type="bibr" rid="ref90">90</xref>]</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table7fn1">
              <p><sup>a</sup>EDMS: emergency and disaster management system.</p>
            </fn>
            <fn id="table7fn2">
              <p><sup>b</sup>PADM: protective action decision model.</p>
            </fn>
            <fn id="table7fn3">
              <p><sup>c</sup>HBM: Health Belief Model.</p>
            </fn>
            <fn id="table7fn4">
              <p><sup>d</sup>PMT: protection motivation theory.</p>
            </fn>
            <fn id="table7fn5">
              <p><sup>e</sup>SARF: social amplification of risk framework.</p>
            </fn>
            <fn id="table7fn6">
              <p><sup>f</sup>TAM2: extension of the technology acceptance model.</p>
            </fn>
            <fn id="table7fn7">
              <p><sup>g</sup>TPB: theory of planned behavior.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <sec>
          <title>Protective Action Decision Model</title>
          <p>The PADM is a framework for managing the societal response to environmental hazards [<xref ref-type="bibr" rid="ref51">51</xref>]. The PADM has been applied to 3 different areas: risk communication, evacuation modeling, and long-term hazard adjustment [<xref ref-type="bibr" rid="ref51">51</xref>]. In the PADM, decision-making begins with environmental cues, social cues, and warnings [<xref ref-type="bibr" rid="ref51">51</xref>]. Environmental cues are signs of threat obtained from the environment, such as sight, smell, or sound [<xref ref-type="bibr" rid="ref51">51</xref>]. Social cues are signs obtained after observing the behavior of others [<xref ref-type="bibr" rid="ref51">51</xref>]. A warning is a message sent from an information source through a channel to the recipient [<xref ref-type="bibr" rid="ref51">51</xref>]. The 3 triggers encourage a pre–decision-making process involving exposure, attention, and comprehension [<xref ref-type="bibr" rid="ref51">51</xref>]. Exposure measures whether people receive information, attention measures whether people care about the information, and comprehension measures whether people understand the information [<xref ref-type="bibr" rid="ref51">51</xref>].</p>
          <p>Furthermore, the pre–decision-making process generates perceptions of the environmental threats, alternative protective actions, and relevant stakeholders (government, other groups, and community) [<xref ref-type="bibr" rid="ref51">51</xref>]. These perceptions provide the basis for protective action decision-making [<xref ref-type="bibr" rid="ref51">51</xref>]. The dependent variable of the PADM is a behavioral response that is generally in the form of information seeking, protective responses, or emotion-focused coping [<xref ref-type="bibr" rid="ref51">51</xref>]. The actual implementation of a response depends not only on people's intentions to act but also on the physical and social conditions that can hinder or facilitate the action [<xref ref-type="bibr" rid="ref51">51</xref>]. The final stage in the PADM is the feedback loop [<xref ref-type="bibr" rid="ref51">51</xref>]. People attempt to confirm or contradict every warning they receive, usually by searching for additional information from different sources and channels [<xref ref-type="bibr" rid="ref51">51</xref>].</p>
          <p>Stakeholder perceptions and protective action perceptions have been shown to influence compliance with warnings during the avian influenza A (H7N9) outbreak [<xref ref-type="bibr" rid="ref87">87</xref>] and the COVID-19 pandemic [<xref ref-type="bibr" rid="ref15">15</xref>]. Meanwhile, threat perception has not been shown to affect warning compliance based on COVID-19 research in Germany and China [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. The use of protective measures can reduce threat appraisal, making people feel less likely to be infected. However, the duration of the pandemic, the extended and repeated warnings, and the familiar feeling of the disease resulted in information fatigue that undermined the perceived threat [<xref ref-type="bibr" rid="ref52">52</xref>]. Among all the theories in <xref ref-type="table" rid="table7">Table 7</xref>, the PADM is the only theory that focuses on the human response to threats [<xref ref-type="bibr" rid="ref51">51</xref>]. The PADM also specifies prompts for action, which are important for encouraging engagement in health-related behaviors [<xref ref-type="bibr" rid="ref87">87</xref>]. However, for slow-moving and long-term health-related hazards, the PADM has not been able to predict changes in threat perceptions.</p>
        </sec>
        <sec>
          <title>Etzioni's Compliance Theory</title>
          <p>Etzioni's compliance theory states that there are 2 parties to a compliance relationship: an actor who has power and another actor who responds to the power (subordinated actor) [<xref ref-type="bibr" rid="ref91">91</xref>]. Power can be differentiated into 3 types according to the means used to make the subject comply [<xref ref-type="bibr" rid="ref91">91</xref>]. Coercive power applies physical sanctions, force, and fear to control lower-level participants [<xref ref-type="bibr" rid="ref91">91</xref>]. Remuneration power applies material resources and rewards to control others [<xref ref-type="bibr" rid="ref91">91</xref>]. However, normative power is the provision and manipulation of symbolic rewards and deprivations [<xref ref-type="bibr" rid="ref91">91</xref>]. The effectiveness of each power in obtaining the cooperation of subordinates depends on their involvement [<xref ref-type="bibr" rid="ref91">91</xref>].</p>
          <p>The subordinated actor can have 3 kinds of involvement: alienative, calculative, and moral [<xref ref-type="bibr" rid="ref91">91</xref>]. Alienative involvement leads to intense negative orientation, while calculative involvement can lead to positive or negative orientation [<xref ref-type="bibr" rid="ref91">91</xref>]. However, moral involvement, also known as commitment, leads to intensely positive orientation [<xref ref-type="bibr" rid="ref91">91</xref>]. Moral involvement can be based on pure commitment (based on the internalization of norms) and social commitment (based on pressure from primary groups and their members) [<xref ref-type="bibr" rid="ref91">91</xref>]. Subsequently, combining 3 types of power and 3 types of involvement produces 9 kinds of compliance [<xref ref-type="bibr" rid="ref91">91</xref>]. However, 3 kinds of compliance are more frequently found in practice [<xref ref-type="bibr" rid="ref91">91</xref>]. These are the relationships between coercive power and alienative involvement, remuneration power and calculative involvement, and normative power and moral involvement [<xref ref-type="bibr" rid="ref91">91</xref>]. These compliance types are called congruent types [<xref ref-type="bibr" rid="ref91">91</xref>]. This happens when the subordinate's involvement type is the same as the types that want to be generated by organization power [<xref ref-type="bibr" rid="ref91">91</xref>]. The congruent types are more frequent because they are more effective to implement.</p>
          <p>Etzioni's compliance theory has been adapted to campus emergencies [<xref ref-type="bibr" rid="ref38">38</xref>] and health care–related emergencies [<xref ref-type="bibr" rid="ref41">41</xref>]. Both studies were designed to accommodate emergency notifications sent by normative organizations, such as the campus and the government [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. Normative power was adapted as the subjective norm, while coercive power and remuneration power were adapted as a perceived security threat and a perceived financial threat, respectively [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. The results of the 2 studies are similar and show that subjective norms are the most important factor promoting immediate compliance in health-related hazard scenarios [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref41">41</xref>].</p>
        </sec>
        <sec>
          <title>Health Belief Model</title>
          <p>The HBM is a conceptual model for understanding why individuals do or do not perform various actions related to health behavior [<xref ref-type="bibr" rid="ref92">92</xref>]. The HBM defines 6 different constructs. These constructs focus on individual representations of threat perceptions and evaluation of health behaviors [<xref ref-type="bibr" rid="ref93">93</xref>]. Threat perception is defined as 2 central beliefs: perceived susceptibility to health problems and perceived severity of disease consequences [<xref ref-type="bibr" rid="ref93">93</xref>]. Health behavioral evaluation also consists of 2 constructs: perceptions of the benefits or efficacy of the recommended health behaviors and perceptions related to the barriers to enacting these behaviors [<xref ref-type="bibr" rid="ref93">93</xref>]. In addition, the HBM proposes that cues to action can activate health behaviors when individuals hold appropriate beliefs [<xref ref-type="bibr" rid="ref92">92</xref>]. Cues to action can be individual perceptions of symptoms, social influences, and health education campaigns [<xref ref-type="bibr" rid="ref93">93</xref>]. In a later version of the theory, individual health motivations are also included as constructs that drive health behavior actions [<xref ref-type="bibr" rid="ref93">93</xref>].</p>
          <p>The HBM has been used to analyze individual compliance with warnings to take recommended protective actions during the H7N9 [<xref ref-type="bibr" rid="ref87">87</xref>] and COVID-19 [<xref ref-type="bibr" rid="ref88">88</xref>] outbreaks. The perceived risk or perceived vulnerability positively influenced compliance intentions in the H7N9 outbreak [<xref ref-type="bibr" rid="ref87">87</xref>]. Meanwhile, all HBM constructs except health motivation were used by Guillon and Kergall [<xref ref-type="bibr" rid="ref88">88</xref>] and were shown to affect compliance to protective measures and CTAs during the COVID-19 pandemic. However, the HBM does not consider the effect of information on protective behavior, even though risk information has been seen as an essential driver of risk perception and behavioral response [<xref ref-type="bibr" rid="ref87">87</xref>].</p>
        </sec>
        <sec>
          <title>Protection Motivation Theory</title>
          <p>In a hazardous event, the increased fear of the individual also increases their intention to take action [<xref ref-type="bibr" rid="ref90">90</xref>]. The PMT describes the social and cognitive processes that underlie protective behavior [<xref ref-type="bibr" rid="ref94">94</xref>]. The PMT proposes that people protect themselves based on threat appraisal and coping appraisal [<xref ref-type="bibr" rid="ref94">94</xref>]. Threat appraisal refers to the perceived likelihood that the event will occur and have negative consequences [<xref ref-type="bibr" rid="ref94">94</xref>]. Threat appraisal is a person's assessment of the estimated severity of the disease (perceived severity) and estimates the likelihood of contracting the disease (perceived susceptibility) [<xref ref-type="bibr" rid="ref95">95</xref>]. In addition, the PMT also states that fear arousal indirectly affects attitudes and behavior changes through the perceived severity of danger [<xref ref-type="bibr" rid="ref95">95</xref>]. However, coping appraisal consists of the individual's expectation that implementing the recommendations will eliminate the threat (response efficacy) and the belief that they can successfully carry out the recommended actions (self-efficacy) [<xref ref-type="bibr" rid="ref95">95</xref>]. Thus, if individuals conclude that a threat will affect them, they will be more motivated to protect themselves and initiate or continue certain self-protective behaviors [<xref ref-type="bibr" rid="ref94">94</xref>].</p>
          <p>In Health EDMS compliance studies, the PMT has been used in campus emergency notification systems [<xref ref-type="bibr" rid="ref90">90</xref>] and emergency alerts during the COVID-19 pandemic in South Korea [<xref ref-type="bibr" rid="ref89">89</xref>]. However, the PMT constructs cannot explain rapid compliance with health advisory warnings on campus. Instead, the PMT can better explain compliance in fast-evolving scenarios, such as robberies, active shooters, and building fires. In the COVID-19 alert study, the PMT construct was used as a mediating factor between reading text messages and practicing preventive behaviors. Response efficacy was the only variable driving compliance to warnings, whereas the perceived risk was insignificant. Based on these 2 studies [<xref ref-type="bibr" rid="ref89">89</xref>,<xref ref-type="bibr" rid="ref90">90</xref>], the PMT constructs are less predictive of explaining compliance in slower-developing scenarios, such as health-related hazards.</p>
        </sec>
        <sec>
          <title>Social Amplification of Risk Framework</title>
          <p>SARF describes a dynamic process for understanding how risk is perceived when communicated to the community [<xref ref-type="bibr" rid="ref15">15</xref>]. SARF conceptualizes that individual and social perceptions of risk and risk behavior can be shaped, enhanced, or attenuated when there is an interaction between hazardous events and psychological, social, institutional, and cultural processes [<xref ref-type="bibr" rid="ref96">96</xref>]. In this case, the IS and the characteristics of the public response can form a social amplification that determines the nature and magnitude of the risk. ISs can amplify risk events in 2 ways: by intensifying or attenuating the signals that individuals and social groups receive about risk and by filtering out the many signals related to risk attributes and their importance [<xref ref-type="bibr" rid="ref96">96</xref>].</p>
          <p>Amplification occurs in 2 stages: when transferring information about the risk and when the community responds to the information [<xref ref-type="bibr" rid="ref96">96</xref>]. Signals about risk are processed by individual and social amplification stations, including scientists communicating risk assessments, news media, cultural groups, and interpersonal networks [<xref ref-type="bibr" rid="ref96">96</xref>]. Reinforced risk leads to a behavioral response, resulting in secondary impacts, such as financial loss, organizational change, and physical risk [<xref ref-type="bibr" rid="ref96">96</xref>]. Communication is at the core of SARF, as individuals are most often exposed to risky information through the media or discussions with others [<xref ref-type="bibr" rid="ref15">15</xref>]. In this manner, risk amplification allows different “amplification stations” to compete for public attention and influence how the public perceives and responds to risk [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
          <p>SARF has been used to investigate compliance behavior in China during the COVID-19 pandemic [<xref ref-type="bibr" rid="ref15">15</xref>]. One variable from SARF, namely information interaction, is used to examine how interactions between individuals can shape risk perceptions [<xref ref-type="bibr" rid="ref15">15</xref>]. Information interaction significantly influences risk perception and preparedness intentions, while also serving as a mediator for warning [<xref ref-type="bibr" rid="ref15">15</xref>]. Of the 2 stages of amplification in SARF, this study only analyzed amplification when the public responds to information [<xref ref-type="bibr" rid="ref15">15</xref>]. Other SARF variables have not been found in Health EDMS compliance studies.</p>
        </sec>
        <sec>
          <title>Extension of the Technology Acceptance Model</title>
          <p>TAM2 extends the original TAM by including additional key determinants of perceived usefulness and usage intention constructs: social influence and cognitive instrumental process [<xref ref-type="bibr" rid="ref97">97</xref>]. The social influence processes consist of subjective norms, voluntariness, and image [<xref ref-type="bibr" rid="ref97">97</xref>]. Subjective norms are added as determinants considering that people can choose to perform a behavior if they believe their important references think they should [<xref ref-type="bibr" rid="ref97">97</xref>]. TAM2 distinguishes between mandatory and voluntary use arrangements by adding voluntariness as a moderating variable [<xref ref-type="bibr" rid="ref97">97</xref>]. In addition, TAM2 theorizes that social influences can affect how users judge the system's image (ie, whether the system can increase their status in a social system) [<xref ref-type="bibr" rid="ref97">97</xref>]. The elevated status leads to increased power and influence that eventually provides a general basis for greater productivity (perceived usefulness) [<xref ref-type="bibr" rid="ref97">97</xref>]. TAM2 also investigates how these determinants' effects change with increasing user experience over time with the target system [<xref ref-type="bibr" rid="ref97">97</xref>]. As cognitive instrumental processes, TAM2 includes job relevance, output quality, and result demonstrability constructs. TAM2 shows that the influence of cognitive instrumental processes is not influenced by experience over time [<xref ref-type="bibr" rid="ref97">97</xref>].</p>
          <p>Research on CTAs in the United Kingdom found that most TAM2 constructs significantly affect user behavior to download the application and comply with notifications [<xref ref-type="bibr" rid="ref27">27</xref>]. The trust factor was added and proved to be significant [<xref ref-type="bibr" rid="ref27">27</xref>]. Compliance with the notification was fairly high, but there were issues surrounding trust and understanding of the application's features that hindered the adoption of the CTA [<xref ref-type="bibr" rid="ref27">27</xref>]. Moreover, Dowthwaite et al [<xref ref-type="bibr" rid="ref27">27</xref>] stated that users would likely delete the CTA when they are frustrated by a notification from the application (output quality) and do not understand how their data would be used (result demonstrability). Although TAM2 has described the factors that influence compliance with Health EDMS, it is still unclear what level of experience, output quality, and result demonstrability can positively affect compliance.</p>
        </sec>
        <sec>
          <title>Theory of Planned Behavior</title>
          <p>The TPB was first introduced as a development of the theory of reasoned action (TRA) and has been most widely adopted in the research on motivations for human behavior. The TPB explains that behavior is influenced by intention and intention is determined by 3 types of beliefs: attitudes, subjective norms, and perceived behavioral control [<xref ref-type="bibr" rid="ref98">98</xref>]. Attitude is a comprehensive evaluation of the implementation of behavior [<xref ref-type="bibr" rid="ref98">98</xref>]. Subjective norms are individual perceptions of other people's expectations considered important about certain behaviors [<xref ref-type="bibr" rid="ref98">98</xref>]. Meanwhile, perceived behavioral control is an individual's perception of how easy or difficult it is to do something [<xref ref-type="bibr" rid="ref98">98</xref>]. It can also be interpreted as the resources and opportunities available to a person to encourage them to perform a behavior [<xref ref-type="bibr" rid="ref98">98</xref>]. The TPB has been applied in studies of ISs, organizations, and user populations.</p>
          <p>The TPB is 1 of the most influential theories in disaster and emergency preparedness planning. The TPB has been used to analyze the factors that affect rapid compliance with emergency notifications in 7 emergency scenarios in a campus: robbery, active shooter, building fire, hazardous material, riot/violent protest, air quality advisory, and health advisory [<xref ref-type="bibr" rid="ref90">90</xref>]. Attitude significantly affected compliance across all scenarios, while subjective norms significantly affected almost all scenarios except the active shooter [<xref ref-type="bibr" rid="ref90">90</xref>]. However, perceived behavioral control was only significant in the air quality advisory scenario [<xref ref-type="bibr" rid="ref90">90</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Factors Affecting User Compliance With Health EDMS</title>
        <p>This section summarizes the factors affecting compliance with Health EDMS from the selected papers. People can comply immediately or verify and then comply after receiving a warning [<xref ref-type="bibr" rid="ref38">38</xref>]. Verification is performed by contacting other people or seeking information from other media and channels [<xref ref-type="bibr" rid="ref41">41</xref>]. In this case, various features of Health EDMS, such as warning and notification (RS2.2), interactive messaging (RS2.3), or video and media (RS2.3), can facilitate remote verification to increase compliance levels [<xref ref-type="bibr" rid="ref41">41</xref>]. Other technological factors, such as system design, including communication channels, public education, usability, and information content, also affect warning compliance [<xref ref-type="bibr" rid="ref78">78</xref>].</p>
        <p>In addition, individual characteristics and social influence play a significant role in driving compliance [<xref ref-type="bibr" rid="ref78">78</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref90">90</xref>]. The individual evaluates the situation to build their belief about whether compliance with an emergency message yields a valuable outcome [<xref ref-type="bibr" rid="ref90">90</xref>]. They also consider their expectations from influential people in their lives, social pressures, and cultural norms about behavior [<xref ref-type="bibr" rid="ref90">90</xref>]. The factors affecting compliance with Health EDMS can be categorized into 3 main groups: individual, technology, and social.</p>
        <p>Sorensen [<xref ref-type="bibr" rid="ref79">79</xref>] stated that warning compliance is influenced by sender and receiver factors, situational factors, and social contacts. Upon receiving the warning, individuals make decisions based on their judgment of the message source, their ability to understand the message and implement countermeasures, and the personal situation they experienced. The sender and receiver are included in the category of individual factors. Moreover, compliance results from interactions between users and other parties who provide warnings. In this study, the interaction is described in the form of social factors consisting of situational factors and social contact. Sorensen [<xref ref-type="bibr" rid="ref79">79</xref>] also stated that system design can affect the response to warnings.</p>
        <p>From the literature reviewed, our study identified 14 individual, 10 technological, and 4 social factors that influenced users' compliance with Health EDMS. Most of them were derived from the previously discussed behavior theories, while others were added by the researchers without referring to any particular theory. From individual factors, perceived risk and response efficacy are the most widely used predictors of compliance. From technological factors, the most frequently used factors are warning message characteristics. Moreover, subjective norms and stakeholder perception are the most researched social factors. A summary table of the individual, technological, and social factors influencing users' compliance with Health EDMS is provided in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>EDM is 1 of the most challenging management tasks because decisions must be made in a short time, under a rapidly changing environment, with unique situations for each incident, and involve high operational costs [<xref ref-type="bibr" rid="ref64">64</xref>]. In this case, an IS (EDMS) can be used to support decision-making. Each stage in EDM (ie, mitigation, preparedness, response, and recovery) requires a different type of EDMS feature in terms of the problem to be solved, the stakeholders involved, the need to provide real-time data, presentation of the data to users, and the technological sophistication required [<xref ref-type="bibr" rid="ref64">64</xref>]. This research mapped EDMS features from various literatures into the main activities at each EDM stage. From the 4 stages of EDM, 19 main activities and 42 EDMS features were identified (<xref ref-type="table" rid="table1">Tables 1</xref>-<xref ref-type="table" rid="table4">4</xref>). This study also identified stakeholder roles for each feature using the RACI matrix, which will be helpful during EDMS development. The list of features presented in this study is expected to guide governments and system developers in designing a comprehensive and integrated EDMS.</p>
        <p>This study mapped the EDMS features into CTA functionalities. Contact-tracing strategies have been implemented worldwide, with varying degrees of success [<xref ref-type="bibr" rid="ref86">86</xref>]. In 2020, months after COVID-19 spread, CTAs were launched in more than 50 countries [<xref ref-type="bibr" rid="ref72">72</xref>], both official and unofficial, to respond to the pandemic. This study found that at the most, a CTA implements 11 EDMS features for the response and recovery phases. For the response phase, a CTA provides features to monitor and report ongoing hazards, disseminate notifications and alerts, provide information to the public, manage request data, manage contact-tracing data, manage medical care, and manage laboratory test data. When the number of infected cases decreases and activities return to normal, a CTA can still be used in the recovery phase to support ongoing medical care and monitoring activities. An important feature that needs to be implemented in the recovery phase is the management of lessons learned data. The lessons learned can provide insight into the use of Health EDMS in the response stage [<xref ref-type="bibr" rid="ref63">63</xref>], especially for new infectious diseases that have not been previously identified. This feature will be beneficial in determining future strategies and policies. A CTA was only implemented when the disease had spread, so there were no mitigation and preparedness functions. The system should also be equipped with these functions for further development to enable early strategic planning and build sufficient capacity for dealing with the health-related hazard.</p>
        <p>Rapid compliance with warnings is vital to save lives. The features of Health EDMS can provide information and warnings that increase the sense of urgency and become a source of verification to improve compliance levels [<xref ref-type="bibr" rid="ref41">41</xref>]. Through a systematic literature review using the PRISMA method, this study classified factors that determine compliance with Health EDMS into individual, technological, and social factors. Based on the analysis and synthesis of the literature, we proposed a research framework showing the relationship between the influencing factors of Health EDMS feature use and design and user compliance with Health EDMS (<xref rid="figure4" ref-type="fig">Figure 4</xref>). The framework shows that individual, technological, and social factors influence the use and design of surveillance and reporting features, and medical care and logistical support features. Appropriate use of these Health EDMS features during health disaster events affects user compliance with Health EDMS.</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Proposed research framework. EDMS: emergency and disaster management system.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e41168_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>In the previous explanation (<xref ref-type="table" rid="table5">Table 5</xref>), 11 features have been implemented in Health EDMS, mainly for surveillance and reporting ongoing hazards and providing medical care and logistical support. Individual, technological, and social factors influence the use of these features. Individual factors are related to perceptions of health risks, experiences, attitudes, and perceptions of Health EDMS. The perceived probability and consequences of contracting a disease can encourage someone to take protective actions in Health EDMS [<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref88">88</xref>]. Individuals who feel the threat of an illness will seek more information about it and will always be aware of warnings and notifications from the system. Therefore, individual factors influence the use of surveillance and monitoring features of Health EDMS. During the COVID-19 pandemic, the perception of risk also encouraged the public to carry out laboratory tests and self-quarantine to ensure they did not contract the disease or infect other people [<xref ref-type="bibr" rid="ref88">88</xref>]. They were self-encouraged to take preventive measures, such as testing, medical treatment, and requesting logistical assistance through Health EDMS.</p>
        <p>Technological factors cover all aspects of information and technical quality. System notifications and warnings can change how individuals think and feel about threats and risks. Health EDMS must provide sufficient information to users about their possible risk exposure and the actions they should take [<xref ref-type="bibr" rid="ref86">86</xref>]. The information quality of the system will drive the use of both feature sets in Health EDMS (ie, surveillance and monitoring, and medical care and logistical support). In addition, if users believe that Health EDMS is easy to use, relevant to their needs, and protects their privacy, they will be encouraged to use the system [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref86">86</xref>].</p>
        <p>In addition to technological and individual factors, the use and design of Health EDMS are influenced by social factors. Opinions from influential people, such as family, friends, or coworkers, encourage individuals to use Health EDMS [<xref ref-type="bibr" rid="ref90">90</xref>], for example, seeking information about hazards and viewing daily case reports. Moreover, users who believe that Health EDMS stakeholders have the expertise to manage hazards will use Health EDMS as their primary source of information and warnings [<xref ref-type="bibr" rid="ref15">15</xref>]. Users will also ask for medical and logistical assistance through Health EDMS if they believe the stakeholders can respond quickly and effectively [<xref ref-type="bibr" rid="ref15">15</xref>]. In designing Health EDMS, social factors can be supported by allowing users to share information to social media or messaging applications. Health EDMS must also highlight the ability of the stakeholders to overcome the health hazards [<xref ref-type="bibr" rid="ref15">15</xref>]. Frequent use of the surveillance and monitoring features as well as the medical and logistical assistance features of Health EDMS may increase compliance. User compliance analyzed in previous research is limited to the intention to comply, not actual compliance. Future research needs to examine actual compliance to produce stronger evidence on the causal factors and effective interventions in this area.</p>
        <p>The proposed research framework was developed based on our analysis of theories and corresponding factors affecting user compliance with Health EDMS in the existing literature. Future research can empirically examine the framework with a specific health EDMS. Collaborations with CTA providers are needed to examine actual compliance. In addition to the proposed research framework, we proposed 2 research topics on Health EDMS that require further investigation. First, Health EDMS has only implemented features to handle the response and recovery phases of EDM. The mitigation and preparedness phases of EDM are not supported by Health EDMS. Health EDMS should not only be used to respond to and cope with disasters but also be used to prevent and prepare for health-related hazards. Nevertheless, unlike natural disasters or human-induced disasters, such as forest fires, the characteristics of future health-related hazards are unknown. How to design features for mitigation and preparedness of future health-related hazards is an interesting research topic. Second, considering that a CTA is a relatively new IS implemented for a specific pandemic case, the effectiveness of CTA features in increasing user compliance with warnings has not been widely analyzed. Instead of examining a CTA as a whole, future research should investigate each feature of a CTA in depth toward increasing user compliance.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>Health EDMS has been implemented to cope with health-related hazards. However, the compliance rate with Health EDMS remains low [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. This study reviewed previous research on user compliance with Health EDMS based on PRISMA reporting guidelines. Research on this topic increased rapidly in 2021 due to the COVID-19 pandemic. This study identified 7 theories researchers adopted when examining Health EDMS compliance behavior: PADM, Etzioni's compliance theory, HBM, PMT, SARF, TAM2, and TPB. This study also discussed the individual, technological, and social factors influencing the use of 2 Health EDMS features (ie, surveillance and reporting features, and medical care and logistical support features). During health-related hazards, community users play an important role in actively reporting disaster victims and missing persons, report tracing data and lab results, report damage to infrastructure, and request medical assistance and treatment. Community users who actively use the surveillance and reporting features as well as the medical care and logistical support features will be encouraged to comply with the protocols and measures to deal with the health disaster. An in-depth understanding of user compliance before designing a health EDMS is essential for governments and developers to increase the effectiveness of Health EDMS implementation.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Hazard classification by WHO [<xref ref-type="bibr" rid="ref36">36</xref>]. WHO: World Health Organization.</p>
        <media xlink:href="jmir_v25i1e41168_app1.docx" xlink:title="DOCX File , 14 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>PRISMA 2020 checklist. PRISMA: Preferred Reporting Items for Systematic Reviews and Meta-Analyses.</p>
        <media xlink:href="jmir_v25i1e41168_app2.docx" xlink:title="DOCX File , 32 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Studies included in the final review.</p>
        <media xlink:href="jmir_v25i1e41168_app3.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Factors affecting user compliance with Health EDMS. EDMS: emergency and disaster management system.</p>
        <media xlink:href="jmir_v25i1e41168_app4.docx" xlink:title="DOCX File , 50 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CTA</term>
          <def>
            <p>contact-tracing application</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">DMS</term>
          <def>
            <p>disaster management system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EDM</term>
          <def>
            <p>emergency and disaster management</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EDMS</term>
          <def>
            <p>emergency and disaster management system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EMS</term>
          <def>
            <p>emergency management system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">H7N9</term>
          <def>
            <p>avian influenza A</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">HBM</term>
          <def>
            <p>Health Belief Model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">IS</term>
          <def>
            <p>information system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">NGO</term>
          <def>
            <p>nongovernment organization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">PADM</term>
          <def>
            <p>protective action decision model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">PMT</term>
          <def>
            <p>protection motivation theory</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">RACI</term>
          <def>
            <p>responsible, accountable, consulted, and informed</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">SARF</term>
          <def>
            <p>social amplification of risk framework</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">TAM2</term>
          <def>
            <p>extension of the technology acceptance model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">TPB</term>
          <def>
            <p>theory of planned behavior</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">WHO</term>
          <def>
            <p>World Health Organization</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This work is supported by the Penelitian Dasar Unggulan Perguruan Tinggi (PDUPT) grant from the Ministry of Education, Culture, Research, and Technology, Republic of Indonesia (contract number: NKB-905/UN2.RST/HKP.05.00/2022).</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>All data analyzed during this study are included in this published paper and its Multimedia Appendices.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Van de Walle</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Turoff</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Decision support for emergency situations</article-title>
          <source>Inf Syst E-Bus Manag</source>
          <year>2008</year>
          <month>3</month>
          <day>26</day>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>295</fpage>
          <lpage>316</lpage>
          <pub-id pub-id-type="doi">10.1007/s10257-008-0087-z</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Waugh Jr</surname>
              <given-names>WL</given-names>
            </name>
          </person-group>
          <source>Living with Hazards Dealing with Disasters: An Introduction to Emergency Management</source>
          <year>2015</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Routledge</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>Terminology on disaster risk reduction</article-title>
          <source>United Nations Office for Disaster Risk Reduction</source>
          <year>2017</year>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.undrr.org/terminology/">https://www.undrr.org/terminology/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>UN Secretary-General</collab>
          </person-group>
          <article-title>Report of the open-ended intergovernmental expert working group on indicators and terminology relating to disaster risk reduction, vol. 21184</article-title>
          <source>United Nations Office for Disaster Risk Reduction</source>
          <year>2016</year>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.undrr.org/publication/report-open-ended-intergovernmental-expert-working-group-indicators-and-terminology-0">https://www.undrr.org/publication/report-open-ended-intergovernmental-expert-working-group-indicators-and-terminology-0</ext-link>
          </comment>
        </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>Albtoush</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dobrescu</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ionescou</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>A hierarchical model for emergency management systems</article-title>
          <source>UPB Sci Bull Ser C Electr Eng</source>
          <year>2011</year>
          <volume>73</volume>
          <issue>2</issue>
          <fpage>53</fpage>
          <lpage>62</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-79958132483&#38;partnerID=40&#38;md5=0805e65cbd14538987181f760162909a"/>
          </comment>
        </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>Rodrigues</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Santos</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Santos</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Rocha</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Dam-break flood emergency management system</article-title>
          <source>Water Resour Manag</source>
          <year>2002</year>
          <volume>16</volume>
          <issue>6</issue>
          <fpage>489</fpage>
          <lpage>503</lpage>
          <pub-id pub-id-type="doi">10.1023/A:1022225108547</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>Wilder-Smith</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Osman</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Public health emergencies of international concern: a historic overview</article-title>
          <source>J Travel Med</source>
          <year>2020</year>
          <month>12</month>
          <day>23</day>
          <volume>27</volume>
          <issue>8</issue>
          <fpage>1</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33284964"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jtm/taaa227</pub-id>
          <pub-id pub-id-type="medline">33284964</pub-id>
          <pub-id pub-id-type="pii">6025447</pub-id>
          <pub-id pub-id-type="pmcid">PMC7798963</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>Nikolic</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Savic</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Stankovic</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Designing a multimedia platform for emergency management</article-title>
          <source>Manag Environ Qual Int J</source>
          <year>2007</year>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>198</fpage>
          <lpage>210</lpage>
          <pub-id pub-id-type="doi">10.1108/14777830710725858</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sorensen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Mileti</surname>
              <given-names>DS</given-names>
            </name>
          </person-group>
          <article-title>Decision-making uncertainties in emergency warning system organization</article-title>
          <source>Int J Mass Emerg Disasters</source>
          <year>2023</year>
          <month>01</month>
          <day>04</day>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>33</fpage>
          <lpage>61</lpage>
          <pub-id pub-id-type="doi">10.1177/028072708700500103</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dou</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Natural disaster monitoring with wireless sensor networks: a case study of data-intensive applications upon low-cost scalable systems</article-title>
          <source>Mobile Netw Appl</source>
          <year>2013</year>
          <month>8</month>
          <day>15</day>
          <volume>18</volume>
          <issue>5</issue>
          <fpage>651</fpage>
          <lpage>663</lpage>
          <pub-id pub-id-type="doi">10.1007/s11036-013-0456-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Erdelj</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Król</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Natalizio</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Wireless sensor networks and multi-UAV systems for natural disaster management</article-title>
          <source>Comput Netw</source>
          <year>2017</year>
          <month>09</month>
          <volume>124</volume>
          <fpage>72</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1016/j.comnet.2017.05.021</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>Kim</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Yeniova</surname>
              <given-names>AÖ</given-names>
            </name>
          </person-group>
          <article-title>Global, regional, and national incidence and mortality of COVID-19 in 237 countries and territories, January 2022: a systematic analysis for World Health Organization COVID-19 dashboard</article-title>
          <source>Life Cycle</source>
          <year>2022</year>
          <month>05</month>
          <day>12</day>
          <volume>2</volume>
          <fpage>1</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.54724/lc.2022.e10</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Palumbo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Coronavirus: how the pandemic has changed the world economy</article-title>
          <source>BBC News</source>
          <year>2021</year>
          <access-date>2022-03-10</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bbc.com/news/business-51706225">https://www.bbc.com/news/business-51706225</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kahn</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <source>Digital Contact Tracing for Pandemic Respons: Ethics and Governance Guidance</source>
          <year>2020</year>
          <publisher-loc>Baltimore, MD</publisher-loc>
          <publisher-name>Johns Hopkins University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>An</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Comes</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>From warning messages to preparedness behavior: the role of risk perception and information interaction in the Covid-19 pandemic</article-title>
          <source>Int J Disaster Risk Reduct</source>
          <year>2022</year>
          <month>04</month>
          <day>15</day>
          <volume>73</volume>
          <fpage>102871</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35261877"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijdrr.2022.102871</pub-id>
          <pub-id pub-id-type="medline">35261877</pub-id>
          <pub-id pub-id-type="pii">S2212-4209(22)00090-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC8891153</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alanzi</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>A review of mobile applications available in the App and Google Play Stores used during the COVID-19 outbreak</article-title>
          <source>J Multidiscip Healthc</source>
          <year>2021</year>
          <month>01</month>
          <volume>14</volume>
          <fpage>45</fpage>
          <lpage>57</lpage>
          <pub-id pub-id-type="doi">10.2147/jmdh.s285014</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>Blasimme</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ferretti</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vayena</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Digital contact tracing against COVID-19 in Europe: current features and ongoing developments</article-title>
          <source>Front Digit Health</source>
          <year>2021</year>
          <month>6</month>
          <day>17</day>
          <volume>3</volume>
          <fpage>660823</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34713135"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2021.660823</pub-id>
          <pub-id pub-id-type="medline">34713135</pub-id>
          <pub-id pub-id-type="pmcid">PMC8521942</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>Altay</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>WG</given-names>
            </name>
          </person-group>
          <article-title>OR/MS research in disaster operations management</article-title>
          <source>Eur J Oper Res</source>
          <year>2006</year>
          <month>11</month>
          <volume>175</volume>
          <issue>1</issue>
          <fpage>475</fpage>
          <lpage>493</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ejor.2005.05.016</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>Rose</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Murthy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Brooks</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bryant</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The evolution of public health emergency management as a field of practice</article-title>
          <source>Am J Public Health</source>
          <year>2017</year>
          <month>09</month>
          <volume>107</volume>
          <issue>S2</issue>
          <fpage>S126</fpage>
          <lpage>S133</lpage>
          <pub-id pub-id-type="doi">10.2105/ajph.2017.303947</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>Hu</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rao</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Identification of a detailed function list for public health emergency management using three qualitative methods</article-title>
          <source>Chin Med J</source>
          <year>2007</year>
          <volume>120</volume>
          <issue>21</issue>
          <fpage>1908</fpage>
          <lpage>1913</lpage>
          <pub-id pub-id-type="doi">10.1097/00029330-200711010-00011</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>Ming</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Untong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Aliudin</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Osili</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kifli</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Goh</surname>
              <given-names>KW</given-names>
            </name>
            <name name-style="western">
              <surname>Ng</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Worafi</surname>
              <given-names>YM</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>KS</given-names>
            </name>
            <name name-style="western">
              <surname>Goh</surname>
              <given-names>HP</given-names>
            </name>
          </person-group>
          <article-title>Mobile health apps on COVID-19 launched in the early days of the pandemic: Content analysis and review</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2020</year>
          <month>09</month>
          <day>16</day>
          <volume>8</volume>
          <issue>9</issue>
          <fpage>e19796</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2020/9/e19796/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19796</pub-id>
          <pub-id pub-id-type="medline">32609622</pub-id>
          <pub-id pub-id-type="pii">v8i9e19796</pub-id>
          <pub-id pub-id-type="pmcid">PMC7505686</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>Abuhammad</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khabour</surname>
              <given-names>OF</given-names>
            </name>
            <name name-style="western">
              <surname>Alzoubi</surname>
              <given-names>KH</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 contact-tracing technology: Acceptability and ethical issues of use</article-title>
          <source>Patient Prefer Adherence</source>
          <year>2020</year>
          <month>09</month>
          <volume>14</volume>
          <fpage>1639</fpage>
          <lpage>1647</lpage>
          <pub-id pub-id-type="doi">10.2147/ppa.s276183</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>Ahmad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Iram</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jabeen</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Perception-based influence factors of intention to adopt COVID-19 epidemic prevention in China</article-title>
          <source>Environ Res</source>
          <year>2020</year>
          <month>11</month>
          <volume>190</volume>
          <fpage>109995</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32739626"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.envres.2020.109995</pub-id>
          <pub-id pub-id-type="medline">32739626</pub-id>
          <pub-id pub-id-type="pii">S0013-9351(20)30892-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7384406</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>Altmann</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Milsom</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zillessen</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Blasone</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gerdon</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Bach</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kreuter</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Nosenzo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Toussaert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Abeler</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Acceptability of app-based contact tracing for COVID-19: cross-country survey study</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2020</year>
          <month>08</month>
          <day>28</day>
          <volume>8</volume>
          <issue>8</issue>
          <fpage>e19857</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2020/8/e19857/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19857</pub-id>
          <pub-id pub-id-type="medline">32759102</pub-id>
          <pub-id pub-id-type="pii">v8i8e19857</pub-id>
          <pub-id pub-id-type="pmcid">PMC7458659</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>Blom</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Wenz</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cornesse</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Rettig</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Fikel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Friedel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Möhring</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Naumann</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Reifenscheid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Krieger</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Barriers to the large-scale adoption of a covid-19 contact tracing app in Germany: survey study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>03</month>
          <day>02</day>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>e23362</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/3/e23362/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23362</pub-id>
          <pub-id pub-id-type="medline">33577466</pub-id>
          <pub-id pub-id-type="pii">v23i3e23362</pub-id>
          <pub-id pub-id-type="pmcid">PMC7927947</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>Bradshaw</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Noetel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Saeri</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Slattery</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Grundy</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Calvo</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Information safety assurances increase intentions to use COVID-19 contact tracing applications, regardless of autonomy-supportive or controlling message framing</article-title>
          <source>Front Psychol</source>
          <year>2020</year>
          <month>1</month>
          <day>7</day>
          <volume>11</volume>
          <fpage>591638</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33542699"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2020.591638</pub-id>
          <pub-id pub-id-type="medline">33542699</pub-id>
          <pub-id pub-id-type="pmcid">PMC7852485</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>Dowthwaite</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Perez Vallejos</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Portillo</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Nichele</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Goulden</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>McAuley</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Public adoption of and trust in the nhs covid-19 contact tracing app in the united kingdom: quantitative online survey study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>09</month>
          <day>17</day>
          <volume>23</volume>
          <issue>9</issue>
          <fpage>e29085</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/9/e29085/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/29085</pub-id>
          <pub-id pub-id-type="medline">34406960</pub-id>
          <pub-id pub-id-type="pii">v23i9e29085</pub-id>
          <pub-id pub-id-type="pmcid">PMC8451731</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>Duan</surname>
              <given-names>SX</given-names>
            </name>
            <name name-style="western">
              <surname>Deng</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Hybrid analysis for understanding contact tracing apps adoption</article-title>
          <source>Ind Manag Data Syst</source>
          <year>2021</year>
          <month>04</month>
          <day>30</day>
          <volume>121</volume>
          <issue>7</issue>
          <fpage>1599</fpage>
          <lpage>1616</lpage>
          <pub-id pub-id-type="doi">10.1108/imds-12-2020-0697</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>Garrett</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>White</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Lewandowsky</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kashima</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Perfors</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Little</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Geard</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tomko</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dennis</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The acceptability and uptake of smartphone tracking for COVID-19 in Australia</article-title>
          <source>PLoS One</source>
          <year>2021</year>
          <month>1</month>
          <day>22</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>e0244827</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0244827"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0244827</pub-id>
          <pub-id pub-id-type="medline">33481841</pub-id>
          <pub-id pub-id-type="pii">PONE-D-20-30595</pub-id>
          <pub-id pub-id-type="pmcid">PMC7822556</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grill</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Eitze</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>De Bock</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Dragano</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Huebl</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schmich</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Wieler</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Betsch</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Sociodemographic characteristics determine download and use of a corona contact tracing app in Germany-results of the COSMO surveys</article-title>
          <source>PLoS One</source>
          <year>2021</year>
          <month>9</month>
          <day>2</day>
          <volume>16</volume>
          <issue>9</issue>
          <fpage>e0256660</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0256660"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0256660</pub-id>
          <pub-id pub-id-type="medline">34473733</pub-id>
          <pub-id pub-id-type="pii">PONE-D-21-09958</pub-id>
          <pub-id pub-id-type="pmcid">PMC8412249</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Villius Zetterholm</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Jokela</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Digital contact tracing applications during COVID-19: a scoping review about public acceptance</article-title>
          <source>Informatics</source>
          <year>2021</year>
          <month>07</month>
          <day>22</day>
          <volume>8</volume>
          <issue>3</issue>
          <fpage>48</fpage>
          <pub-id pub-id-type="doi">10.3390/informatics8030048</pub-id>
        </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>Kahnbach</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lehr</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Brandenburger</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mallwitz</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Jent</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hannibal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Funk</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Janneck</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Quality and adoption of COVID-19 tracing apps and recommendations for development: systematic interdisciplinary review of European apps</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>06</month>
          <day>02</day>
          <volume>23</volume>
          <issue>6</issue>
          <fpage>e27989</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/6/e27989/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/27989</pub-id>
          <pub-id pub-id-type="medline">33890867</pub-id>
          <pub-id pub-id-type="pii">v23i6e27989</pub-id>
          <pub-id pub-id-type="pmcid">PMC8174558</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>Ribeiro-Navarrete</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Saura</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Palacios-Marqués</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Towards a new era of mass data collection: assessing pandemic surveillance technologies to preserve user privacy</article-title>
          <source>Technol Forecast Soc Change</source>
          <year>2021</year>
          <month>06</month>
          <volume>167</volume>
          <fpage>120681</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33840865"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.techfore.2021.120681</pub-id>
          <pub-id pub-id-type="medline">33840865</pub-id>
          <pub-id pub-id-type="pii">S0040-1625(21)00113-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC8019834</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>Kolasa</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mazzi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Leszczuk-Czubkowska</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Zrubka</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Péntek</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>State of the art in adoption of contact tracing apps and recommendations regarding privacy protection and public health: systematic review</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>6</issue>
          <fpage>e23250</fpage>
          <pub-id pub-id-type="doi">10.2196/preprints.23250</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jandl</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Moser</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Schlund</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Reasons and strategies for privacy features in tracking and tracing systems—a systematic literature review</article-title>
          <source>Sensors (Basel)</source>
          <year>2021</year>
          <month>06</month>
          <day>30</day>
          <volume>21</volume>
          <issue>13</issue>
          <fpage>4501</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s21134501"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s21134501</pub-id>
          <pub-id pub-id-type="medline">34209327</pub-id>
          <pub-id pub-id-type="pii">s21134501</pub-id>
          <pub-id pub-id-type="pmcid">PMC8271682</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Golinelli</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Boetto</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Carullo</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Nuzzolese</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Landini</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Fantini</surname>
              <given-names>MP</given-names>
            </name>
          </person-group>
          <article-title>Adoption of digital technologies in health care during the COVID-19 pandemic: systematic review of early scientific literature</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>11</month>
          <day>06</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>e22280</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/11/e22280/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22280</pub-id>
          <pub-id pub-id-type="medline">33079693</pub-id>
          <pub-id pub-id-type="pii">v22i11e22280</pub-id>
          <pub-id pub-id-type="pmcid">PMC7652596</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bassi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Arfin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>John</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>An overview of mobile applications (apps) to support the coronavirus disease 2019 response in India</article-title>
          <source>Indian J Med Res</source>
          <year>2020</year>
          <month>05</month>
          <volume>151</volume>
          <issue>5</issue>
          <fpage>468</fpage>
          <lpage>473</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.lww.com/ijmr/10.4103/ijmr.IJMR_1200_20"/>
          </comment>
          <pub-id pub-id-type="doi">10.4103/ijmr.IJMR_1200_20</pub-id>
          <pub-id pub-id-type="medline">32474557</pub-id>
          <pub-id pub-id-type="pii">284753</pub-id>
          <pub-id pub-id-type="pmcid">PMC7530460</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>Han</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Ada</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sharman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rao</surname>
              <given-names>HR</given-names>
            </name>
          </person-group>
          <article-title>Campus emergency notification systems: An examination of factors affecting compliance with alerts</article-title>
          <source>MIS Q</source>
          <year>2015</year>
          <month>4</month>
          <day>4</day>
          <volume>39</volume>
          <issue>4</issue>
          <fpage>909</fpage>
          <lpage>929</lpage>
          <pub-id pub-id-type="doi">10.25300/MISQ/2015/39.4.8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdelhamid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Howell</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sharman</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The impact of information and system quality on emergency notification systems adoption</article-title>
          <year>2017</year>
          <conf-name>AMCIS 2017: America’s Conference on Information Systems: A Tradition of Innovation</conf-name>
          <conf-date>August 10-12, 2017</conf-date>
          <conf-loc>Boston, MA</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>O'Malley</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Rainford</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Transparency during public health emergencies: from rhetoric to reality</article-title>
          <source>Bull World Health Organ</source>
          <year>2009</year>
          <month>08</month>
          <day>1</day>
          <volume>87</volume>
          <issue>8</issue>
          <fpage>614</fpage>
          <lpage>618</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/19705012"/>
          </comment>
          <pub-id pub-id-type="doi">10.2471/blt.08.056689</pub-id>
          <pub-id pub-id-type="medline">19705012</pub-id>
          <pub-id pub-id-type="pii">S0042-96862009000800018</pub-id>
          <pub-id pub-id-type="pmcid">PMC2733257</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Leroy</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Factors affecting compliance with alerts in the context of healthcare-related emergencies</article-title>
          <source>AIS Trans Replication Res</source>
          <year>2021</year>
          <volume>7</volume>
          <fpage>1</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="doi">10.17705/1atrr.00068</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Page</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>McKenzie</surname>
              <given-names>JE</given-names>
            </name>
            <name name-style="western">
              <surname>Bossuyt</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Boutron</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Hoffmann</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Mulrow</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Shamseer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Tetzlaff</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Brennan</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Chou</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Glanville</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Grimshaw</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Hróbjartsson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lalu</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loder</surname>
              <given-names>EW</given-names>
            </name>
            <name name-style="western">
              <surname>Mayo-Wilson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>McDonald</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>McGuinness</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Welch</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Whiting</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The PRISMA 2020 statement: an updated guideline for reporting systematic reviews</article-title>
          <source>BMJ</source>
          <year>2021</year>
          <month>03</month>
          <day>29</day>
          <volume>372</volume>
          <fpage>n71</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33782057"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmj.n71</pub-id>
          <pub-id pub-id-type="medline">33782057</pub-id>
          <pub-id pub-id-type="pmcid">PMC8005924</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <article-title>Western Pacific Regional Framework for action for disaster risk management for health</article-title>
          <source>World Health Organization</source>
          <year>2015</year>
          <month>5</month>
          <day>18</day>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/9789290617082">https://www.who.int/publications/i/item/9789290617082</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Blanchard</surname>
              <given-names>BW</given-names>
            </name>
          </person-group>
          <source>Department of Homeland Security,</source>
          <year>2008</year>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://defencemanagement.org/article/guide-emergency-management-and-related-terms-definitions-concepts-acronyms-organizations">https://defencemanagement.org/article/guide-emergency-management-and-related-terms-definitions-concepts-acronyms-organizations</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <article-title>Emergency and disaster management</article-title>
          <source>United Nations</source>
          <access-date>2022-03-24</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.un-spider.org/risks-and-disasters/emergency-and-disaster-management#no-back">https://www.un-spider.org/risks-and-disasters/emergency-and-disaster-management#no-back</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <article-title>Disaster response in Asia and the Pacific - a guide to international tools and services [EN/ID/JA/ZH]</article-title>
          <source>UN Office for the Coordination of Humanitarian Affairs</source>
          <year>2013</year>
          <month>4</month>
          <day>9</day>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://reliefweb.int/report/world/disaster-response-asia-and-pacific-guide-international-tools-and-services">http://reliefweb.int/report/world/disaster-response-asia-and-​pacific-guide-international-tools-and-services</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="web">
          <source>World Health Organization</source>
          <year>2002</year>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://apps.who.int/disasters/repo/7656.pdf">http://apps.who.int/disasters/repo/7656.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="web">
          <article-title>Health emergency and disaster risk management framework</article-title>
          <source>World Health Organization</source>
          <year>2019</year>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://apps.who.int/iris/bitstream/handle/10665/326106/9789241516181-eng.pdf">https://apps.who.int/iris/bitstream/handle/10665/326106/9789241516181-eng.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duarte</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Rebelo</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Teles</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Noriega</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>What should I do? - A study about conflicting and ambiguous warning messages</article-title>
          <source>Work</source>
          <year>2012</year>
          <volume>41</volume>
          <issue>Suppl 1</issue>
          <fpage>3633</fpage>
          <lpage>3640</lpage>
          <pub-id pub-id-type="doi">10.3233/wor-2012-0113-3633</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wogalter</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Woga</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <article-title>Communication-human information processing (C-HIP) model</article-title>
          <source>Forensic Human Factors &#38; Ergonomics: Case Studies and Analyses</source>
          <year>2019</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press/Taylor &#38; Francis Group</publisher-name>
          <fpage>33</fpage>
          <lpage>49</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lindell</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Perry</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>The protective action decision model: theoretical modifications and additional evidence</article-title>
          <source>Risk Anal</source>
          <year>2012</year>
          <month>04</month>
          <volume>32</volume>
          <issue>4</issue>
          <fpage>616</fpage>
          <lpage>632</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1539-6924.2011.01647.x</pub-id>
          <pub-id pub-id-type="medline">21689129</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rahn</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tomczyk</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schopp</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Warning messages in crisis communication: risk appraisal and warning compliance in severe weather, violent acts, and the COVID-19 pandemic</article-title>
          <source>Front Psychol</source>
          <year>2021</year>
          <month>4</month>
          <day>1</day>
          <volume>12</volume>
          <fpage>557178</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33868065"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2021.557178</pub-id>
          <pub-id pub-id-type="medline">33868065</pub-id>
          <pub-id pub-id-type="pmcid">PMC8046918</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sutton</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Spiro</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Fitzhugh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gibson</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Butts</surname>
              <given-names>CT</given-names>
            </name>
          </person-group>
          <article-title>Warning tweets: serial transmission of messages during the warning phase of a disaster event</article-title>
          <source>Inf Commun Soc</source>
          <year>2013</year>
          <month>12</month>
          <day>20</day>
          <volume>17</volume>
          <issue>6</issue>
          <fpage>765</fpage>
          <lpage>787</lpage>
          <pub-id pub-id-type="doi">10.1080/1369118x.2013.862561</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Landau</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Security and privacy landscape in emerging technologies</article-title>
          <source>IEEE Secur Privacy Mag</source>
          <year>2008</year>
          <month>07</month>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>74</fpage>
          <lpage>77</lpage>
          <pub-id pub-id-type="doi">10.1109/msp.2008.95</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hannan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Arshad</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Azam</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Loo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Majeed</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Disaster management system aided by named data network of things: architecture, design, and analysis</article-title>
          <source>Sensors (Basel)</source>
          <year>2018</year>
          <month>07</month>
          <day>26</day>
          <volume>18</volume>
          <issue>8</issue>
          <fpage>2431</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s18082431"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s18082431</pub-id>
          <pub-id pub-id-type="medline">30049980</pub-id>
          <pub-id pub-id-type="pii">s18082431</pub-id>
          <pub-id pub-id-type="pmcid">PMC6111799</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Currion</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Van de Walle</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Open source software for disaster management</article-title>
          <source>Commun ACM</source>
          <year>2007</year>
          <month>03</month>
          <volume>50</volume>
          <issue>3</issue>
          <fpage>61</fpage>
          <lpage>65</lpage>
          <pub-id pub-id-type="doi">10.1145/1226736.1226768</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Amailef</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Ontology-supported case-based reasoning approach for intelligent m-government emergency response services</article-title>
          <source>Decis Support Syst</source>
          <year>2013</year>
          <month>04</month>
          <volume>55</volume>
          <issue>1</issue>
          <fpage>79</fpage>
          <lpage>97</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.dss.2012.12.034"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.dss.2012.12.034</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Edwards</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Cuthbertson</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Peterson</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Developing and testing an emergency notification system for a county emergency management agency</article-title>
          <source>J Homel Secur Emerg Manag</source>
          <year>2020</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>0000102202154773551911</fpage>
          <pub-id pub-id-type="doi">10.2202/1547-7355.1911</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Malizia</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Acuna</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Onorati</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Diaz</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Aedo</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>CAP-ONES: an emergency notification system for all</article-title>
          <source>Int J Emerg Manag</source>
          <year>2009</year>
          <volume>6</volume>
          <issue>3/4</issue>
          <fpage>302</fpage>
          <pub-id pub-id-type="doi">10.1504/ijem.2009.031568</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ouyang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F-Y</given-names>
            </name>
          </person-group>
          <article-title>A novel framework of collaborative early warning for COVID-19 based on blockchain and smart contracts</article-title>
          <source>Inf Sci (N Y)</source>
          <year>2021</year>
          <month>09</month>
          <volume>570</volume>
          <fpage>124</fpage>
          <lpage>143</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33846657"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ins.2021.04.021</pub-id>
          <pub-id pub-id-type="medline">33846657</pub-id>
          <pub-id pub-id-type="pii">S0020-0255(21)00342-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC8028591</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bonaretti</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer-Preßler</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The problem with SMS campus warning systems: an evaluation based on recipients’ spatial awareness</article-title>
          <source>Int J Disaster Risk Reduct</source>
          <year>2021</year>
          <month>02</month>
          <volume>54</volume>
          <fpage>102031</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.ijdrr.2020.102031"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijdrr.2020.102031</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kraus</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dwivedi</surname>
              <given-names>YK</given-names>
            </name>
          </person-group>
          <article-title>Digital health innovation: exploring adoption of COVID-19 digital contact tracing apps</article-title>
          <source>IEEE Trans Eng Manag</source>
          <year>2020</year>
          <fpage>1</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.1109/tem.2020.3019033</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tomczyk</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Barth</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Schmidt</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Muehlan</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Utilizing health behavior change and technology acceptance models to predict the adoption of COVID-19 contact tracing apps: cross-sectional survey study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>05</month>
          <day>19</day>
          <volume>23</volume>
          <issue>5</issue>
          <fpage>e25447</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/5/e25447/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/25447</pub-id>
          <pub-id pub-id-type="medline">33882016</pub-id>
          <pub-id pub-id-type="pii">v23i5e25447</pub-id>
          <pub-id pub-id-type="pmcid">PMC8136409</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ristvej</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zagorecki</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Information aystems for crisis management - current applications and future directions</article-title>
          <source>Komunikácie</source>
          <year>2011</year>
          <month>6</month>
          <day>30</day>
          <volume>13</volume>
          <issue>2</issue>
          <fpage>59</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.26552/com.c.2011.2.59-63</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mitraka</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Siachalou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Doxani</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Patias</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Decision support on monitoring and disaster management in agriculture with Copernicus sentinel applications</article-title>
          <source>Sustainability</source>
          <year>2020</year>
          <month>02</month>
          <day>08</day>
          <volume>12</volume>
          <issue>3</issue>
          <fpage>1233</fpage>
          <pub-id pub-id-type="doi">10.3390/su12031233</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Damalas</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mettas</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Evagorou</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Giannecchini</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Iasio</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Papadopoulos</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Konstantinou</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hadjimitsis</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Development and implementation of a DECATASTROPHIZE platform and tool for the management of disasters or multiple hazards</article-title>
          <source>Int J Disaster Risk Reduct</source>
          <year>2018</year>
          <month>10</month>
          <volume>31</volume>
          <fpage>589</fpage>
          <lpage>601</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijdrr.2018.05.011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Integration of spatial analysis and an agent-based model into evacuation management for shelter assignment and routing</article-title>
          <source>J Spat Sci</source>
          <year>2016</year>
          <month>04</month>
          <day>18</day>
          <volume>61</volume>
          <issue>2</issue>
          <fpage>283</fpage>
          <lpage>298</lpage>
          <pub-id pub-id-type="doi">10.1080/14498596.2016.1147393</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>He</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Development of a mobile post-disaster management system using free and open source technologies</article-title>
          <source>Int J Disaster Risk Reduct</source>
          <year>2017</year>
          <month>10</month>
          <volume>25</volume>
          <fpage>101</fpage>
          <lpage>110</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijdrr.2017.08.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Du</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>An integrated geospatial information service system for disaster management in China</article-title>
          <source>Int J Digit Earth</source>
          <year>2014</year>
          <month>09</month>
          <day>08</day>
          <volume>8</volume>
          <issue>11</issue>
          <fpage>918</fpage>
          <lpage>945</lpage>
          <pub-id pub-id-type="doi">10.1080/17538947.2014.955540</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Michaleff</surname>
              <given-names>ZA</given-names>
            </name>
            <name name-style="western">
              <surname>Greenwood</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Abukmail</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Glasziou</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Concerns and misconceptions about the Australian government's COVIDsafe app: cross-sectional survey study</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>11</month>
          <day>04</day>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e23081</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/4/e23081/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23081</pub-id>
          <pub-id pub-id-type="medline">33048826</pub-id>
          <pub-id pub-id-type="pii">v6i4e23081</pub-id>
          <pub-id pub-id-type="pmcid">PMC7644267</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mbunge</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Integrating emerging technologies into COVID-19 contact tracing: opportunities, challenges and pitfalls</article-title>
          <source>Diabetes Metab Syndr</source>
          <year>2020</year>
          <month>11</month>
          <volume>14</volume>
          <issue>6</issue>
          <fpage>1631</fpage>
          <lpage>1636</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32892060"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.dsx.2020.08.029</pub-id>
          <pub-id pub-id-type="medline">32892060</pub-id>
          <pub-id pub-id-type="pii">S1871-4021(20)30332-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7833487</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="web">
          <article-title>Which countries are deploying coronavirus tracing apps?</article-title>
          <source>Statista</source>
          <year>2020</year>
          <access-date>2022-05-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.statista.com/chart/22335/development-of-tracing-apps-by-country/">https://www.statista.com/chart/22335/development-of-tracing-apps-by-country/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="web">
          <article-title>WHO coronavirus (COVID-19) dashboard</article-title>
          <source>World Health Organization</source>
          <year>2022</year>
          <access-date>2022-07-11</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://covid19.who.int/table">https://covid19.who.int/table</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Étienne</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Compliance theories: a literature review</article-title>
          <source>Rev Fr Sci Polit</source>
          <year>2010</year>
          <volume>60</volume>
          <issue>3</issue>
          <fpage>493</fpage>
          <lpage>517</lpage>
          <pub-id pub-id-type="doi">10.3917/rfspe.602.0139</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Etzioni</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>An analytical classification coercive and utilitarian organizations</article-title>
          <source>A Comparative Analysis of Complex Organizations</source>
          <year>1961</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Free Press</publisher-name>
          <fpage>23</fpage>
          <lpage>39</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kyngäs</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Duffy</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Kroll</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Conceptual analysis of compliance</article-title>
          <source>J Clin Nurs</source>
          <year>2000</year>
          <month>01</month>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1046/j.1365-2702.2000.00309.x</pub-id>
          <pub-id pub-id-type="medline">11022487</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuppusamy</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Samy</surname>
              <given-names>GN</given-names>
            </name>
            <name name-style="western">
              <surname>Maarop</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Magalingam</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kamaruddin</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Shanmugam</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Perumal</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Systematic literature review of information security compliance behaviour theories</article-title>
          <source>J Phys: Conf Ser</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <volume>1551</volume>
          <issue>1</issue>
          <fpage>012005</fpage>
          <pub-id pub-id-type="doi">10.1088/1742-6596/1551/1/012005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Fang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Grover</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Managing collective enterprise information systems compliance:  a social and performance management context perspective</article-title>
          <source>MIS Q</source>
          <year>2022</year>
          <month>02</month>
          <day>15</day>
          <volume>46</volume>
          <issue>1</issue>
          <fpage>71</fpage>
          <lpage>100</lpage>
          <pub-id pub-id-type="doi">10.25300/misq/2022/14727</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sorensen</surname>
              <given-names>JH</given-names>
            </name>
          </person-group>
          <article-title>Hazard warning systems: review of 20 years of progress</article-title>
          <source>Nat Hazards Rev</source>
          <year>2000</year>
          <month>05</month>
          <volume>1</volume>
          <issue>2</issue>
          <fpage>119</fpage>
          <lpage>125</lpage>
          <pub-id pub-id-type="doi">10.1061/(asce)1527-6988(2000)1:2(119)</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kitchenham</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Procedures for performing systematic reviews</article-title>
          <source>Tech Rep</source>
          <year>2004</year>
          <month>7</month>
          <volume>33</volume>
          <issue>2004</issue>
          <fpage>1</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.1109/metric.2004.1357885</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kitchenham</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Charters</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Guidelines for performing systematic literature reviews in Software Engineering version 2.3</article-title>
          <source>Engineering</source>
          <year>2007</year>
          <volume>45</volume>
          <issue>4</issue>
          <fpage>1051</fpage>
          <pub-id pub-id-type="doi">10.1145/1134285.1134500</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Meyer</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Conceptual issues in the study of dynamic hazard warnings</article-title>
          <source>Hum Factors</source>
          <year>2004</year>
          <month>08</month>
          <day>28</day>
          <volume>46</volume>
          <issue>2</issue>
          <fpage>196</fpage>
          <lpage>204</lpage>
          <pub-id pub-id-type="doi">10.1518/hfes.46.2.196.37335</pub-id>
          <pub-id pub-id-type="medline">15359670</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Laughery</surname>
              <given-names>KR</given-names>
            </name>
          </person-group>
          <article-title>Safety communications: warnings</article-title>
          <source>Appl Ergon</source>
          <year>2006</year>
          <month>07</month>
          <volume>37</volume>
          <issue>4</issue>
          <fpage>467</fpage>
          <lpage>478</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.apergo.2006.04.020"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2006.04.020</pub-id>
          <pub-id pub-id-type="medline">16759630</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(06)00053-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Freberg</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Intention to comply with crisis messages communicated via social media</article-title>
          <source>Public Relat Rev</source>
          <year>2012</year>
          <month>9</month>
          <volume>38</volume>
          <issue>3</issue>
          <fpage>416</fpage>
          <lpage>421</lpage>
          <pub-id pub-id-type="doi">10.1016/j.pubrev.2012.01.008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Albrecht</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jarecki</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Meier</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Rieskamp</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Risk preferences and risk perception affect the acceptance of digital contact tracing</article-title>
          <source>Humanit Soc Sci Commun</source>
          <year>2021</year>
          <month>08</month>
          <day>06</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1057/s41599-021-00856-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Panchal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Rodriguez-Villegas</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Analysis of the factors affecting the adoption and compliance of the NHS COVID-19 mobile application: a national cross-sectional survey in England</article-title>
          <source>BMJ Open</source>
          <year>2021</year>
          <month>08</month>
          <day>13</day>
          <volume>11</volume>
          <issue>8</issue>
          <fpage>e053395</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=34389583"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2021-053395</pub-id>
          <pub-id pub-id-type="medline">34389583</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2021-053395</pub-id>
          <pub-id pub-id-type="pmcid">PMC8366285</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Compliance with recommended protective actions during an H7N9 emergency: a risk perception perspective</article-title>
          <source>Disasters</source>
          <year>2018</year>
          <month>04</month>
          <day>11</day>
          <volume>42</volume>
          <issue>2</issue>
          <fpage>207</fpage>
          <lpage>232</lpage>
          <pub-id pub-id-type="doi">10.1111/disa.12240</pub-id>
          <pub-id pub-id-type="medline">28799670</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guillon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kergall</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Attitudes and opinions on quarantine and support for a contact-tracing application in France during the COVID-19 outbreak</article-title>
          <source>Public Health</source>
          <year>2020</year>
          <month>11</month>
          <volume>188</volume>
          <fpage>21</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33059232"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.puhe.2020.08.026</pub-id>
          <pub-id pub-id-type="medline">33059232</pub-id>
          <pub-id pub-id-type="pii">S0033-3506(20)30395-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC7550094</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>You</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Effects of COVID-19 emergency alert text messages on practicing preventive behaviors: cross-sectional web-based survey in South Korea</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>02</month>
          <day>25</day>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>e24165</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/2/e24165/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24165</pub-id>
          <pub-id pub-id-type="medline">33544691</pub-id>
          <pub-id pub-id-type="pii">v23i2e24165</pub-id>
          <pub-id pub-id-type="pmcid">PMC7909457</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Forster</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bahr</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Benjamin</surname>
              <given-names>SM</given-names>
            </name>
          </person-group>
          <article-title>A cross-sectional study using health behavior theory to predict rapid compliance with campus emergency notifications among college students</article-title>
          <source>Disaster Med Public Health Prep</source>
          <year>2021</year>
          <month>04</month>
          <day>07</day>
          <volume>15</volume>
          <issue>2</issue>
          <fpage>198</fpage>
          <lpage>207</lpage>
          <pub-id pub-id-type="doi">10.1017/dmp.2019.153</pub-id>
          <pub-id pub-id-type="medline">32029013</pub-id>
          <pub-id pub-id-type="pii">S1935789319001538</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fricke</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Etzioni</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A comparative analysis of complex organizations</article-title>
          <source>Polit Sci Q</source>
          <year>1976</year>
          <volume>91</volume>
          <issue>2</issue>
          <fpage>341</fpage>
          <lpage>342</lpage>
          <pub-id pub-id-type="doi">10.2307/2148419</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rosenstock</surname>
              <given-names>IM</given-names>
            </name>
          </person-group>
          <article-title>The Health Belief Model and preventive health behavior</article-title>
          <source>Health Educ Monogr</source>
          <year>1974</year>
          <month>12</month>
          <day>01</day>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>354</fpage>
          <lpage>386</lpage>
          <pub-id pub-id-type="doi">10.1177/109019817400200405</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abraham</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sheeran</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The health belief model</article-title>
          <source>Cambridge Handbook of Psychology, Health and Medicine, 2nd edition</source>
          <year>2014</year>
          <publisher-loc>Cambridge, UK</publisher-loc>
          <publisher-name>Cambridge University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rogers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Cacioppo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Petty</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Cacioppo</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Petty</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Cognitive and physiological processes in fear appeals and attitude change: a revised theory of protection motivation</article-title>
          <source>Basic Social Psycophysiological Research</source>
          <year>1983</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Guilford Press</publisher-name>
          <fpage>153</fpage>
          <lpage>177</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Plotnikoff</surname>
              <given-names>RC</given-names>
            </name>
            <name name-style="western">
              <surname>Trinh</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Protection motivation theory: is this a worthwhile theory for physical activity promotion?</article-title>
          <source>Exerc Sport Sci Rev</source>
          <year>2010</year>
          <volume>38</volume>
          <issue>2</issue>
          <fpage>91</fpage>
          <lpage>98</lpage>
          <pub-id pub-id-type="doi">10.1097/jes.0b013e3181d49612</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kasperson</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Renn</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Slovic</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>HS</given-names>
            </name>
            <name name-style="western">
              <surname>Emel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kasperson</surname>
              <given-names>JX</given-names>
            </name>
            <name name-style="western">
              <surname>Ratick</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The social amplification of risk: a conceptual framework</article-title>
          <source>Risk Anal</source>
          <year>1988</year>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>177</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.4324/9781849772549-16</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Venkatesh</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>FD</given-names>
            </name>
          </person-group>
          <article-title>A theoretical extension of the technology acceptance model: four longitudinal field studies</article-title>
          <source>Manag Sci</source>
          <year>2000</year>
          <month>02</month>
          <volume>46</volume>
          <issue>2</issue>
          <fpage>186</fpage>
          <lpage>204</lpage>
          <pub-id pub-id-type="doi">10.1287/mnsc.46.2.186.11926</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ajzen</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>The theory of planned behavior</article-title>
          <source>Org Behav Hum Decis Process</source>
          <year>1991</year>
          <month>12</month>
          <volume>50</volume>
          <issue>2</issue>
          <fpage>179</fpage>
          <lpage>211</lpage>
          <pub-id pub-id-type="doi">10.1016/0749-5978(91)90020-T</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
