<?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 article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <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">v27i1e75584</article-id>
      <article-id pub-id-type="pmid">40838797</article-id>
      <article-id pub-id-type="doi">10.2196/75584</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>Sociotechnical Cybersecurity Framework for Securing Health Care From Vulnerabilities and Cyberattacks: Scoping Review</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Sarvestan</surname>
            <given-names>Javad</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Krishnapatnam</surname>
            <given-names>Mahendra</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Wani</surname>
            <given-names>Tafheem Ahmad</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Ewoh</surname>
            <given-names>Pius</given-names>
          </name>
          <degrees>MBA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>School of Technology and Innovations</institution>
            <institution>Information Systems Science</institution>
            <institution>University of Vaasa</institution>
            <addr-line>Wolffintie 32</addr-line>
            <addr-line>Vaasa, 65200</addr-line>
            <country>Finland</country>
            <phone>358 414888477</phone>
            <email>pius.ewoh@uwasa.fi</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4006-619X</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Vartiainen</surname>
            <given-names>Tero</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3843-8561</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Mantere</surname>
            <given-names>Timo</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9266-1006</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>School of Technology and Innovations</institution>
        <institution>Information Systems Science</institution>
        <institution>University of Vaasa</institution>
        <addr-line>Vaasa</addr-line>
        <country>Finland</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>School of Technology and Innovations</institution>
        <institution>Automation Technology</institution>
        <institution>University of Vaasa</institution>
        <addr-line>Vaasa</addr-line>
        <country>Finland</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Pius Ewoh <email>pius.ewoh@uwasa.fi</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>15</day>
        <month>10</month>
        <year>2025</year>
      </pub-date>
      <volume>27</volume>
      <elocation-id>e75584</elocation-id>
      <history>
        <date date-type="received">
          <day>7</day>
          <month>4</month>
          <year>2025</year>
        </date>
        <date date-type="rev-request">
          <day>16</day>
          <month>4</month>
          <year>2025</year>
        </date>
        <date date-type="rev-recd">
          <day>11</day>
          <month>6</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>8</day>
          <month>8</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Pius Ewoh, Tero Vartiainen, Timo Mantere. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 15.10.2025.</copyright-statement>
      <copyright-year>2025</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2025/1/e75584" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The vulnerability of health care systems to cyberattacks and breaches of health information is on the rise worldwide. Considering the increasing rate of reported cyber incidents and the risks they pose to patient safety, privacy, and financial losses, there is a need to examine the way cybersecurity is conceptualized in health care organizations, taking into account technology, processes, and humans.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study examined the dynamics of the factors of vulnerabilities and cyberattacks in the context of sociotechnical systems theory underlying the relationships among humans, technology, and processes. It developed a conceptual sociotechnical cybersecurity framework for preventing vulnerabilities and responding to cyberattacks and threats in health care systems.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A scoping review was conducted to search the extant literature in 3 databases—Web of Science, PubMed (MEDLINE), and Scopus. A total of 1375 papers from the period of 2012-2024 were retrieved, 76 of which, in the domain of health care and cybersecurity, were reviewed and analyzed. Original research and review papers were included. Only published English-language papers were included to focus on contemporary issues, challenges, and solutions. Relevant information from the included sources was charted and summarized. The study characteristics were extracted from the included papers, and the evidence was synthesized using thematic analysis.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Of the 1375 papers identified, 76 (5.5%) met the inclusion criteria. The results showed that the factors of vulnerabilities to cyberattacks comprise 12 subfactors in health care systems. Concerning technology-related factors of vulnerabilities, most studies described the complex system design and usability (16/76, 21%) and integration of new technology (15/76, 20%) as challenges in health care systems. Concerning human-related factors, most studies described a shortage of skilled professionals and limited budgets as contributing to poor cybersecurity management. The study found that processes involved both technology and humans relative to the unit factors of vulnerabilities to cyberattacks. There was a sociotechnical interplay across the factors of vulnerabilities. The concept of sociotechnical cybersecurity offers a comprehensive and explicit perspective on the sociotechnical underpinning and joint optimization required to advance cybersecurity toward achieving sustainable health care systems.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The conceptual framework of sociotechnical cybersecurity provides a contemporary foundation and deep insight for identifying and preventing vulnerabilities and responding to cyberattacks in health care systems. The framework is important due to its suitability, applicability, and customizability for dynamic and complex health care systems. The study also provides compliance standards for applying the proposed conceptual framework to guide health care organizations in cybersecurity practices. The study of cybersecurity through the sociotechnical lens in the health care domain is limited. Further studies are needed on cybersecurity incident management. Health care organizations should leverage the strength of cybersecurity through the implementation of risk assessment and incident response plans.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>computer security</kwd>
        <kwd>network security</kwd>
        <kwd>digital health</kwd>
        <kwd>health information</kwd>
        <kwd>electronic health record system</kwd>
        <kwd>cyber threats</kwd>
        <kwd>ransomware</kwd>
        <kwd>breaches</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>The digitalization of the health care system has introduced numerous positive effects and gains, such as easy access to health information and effective and efficient health care delivery processes and outcomes [<xref ref-type="bibr" rid="ref1">1</xref>]. In the last 2 decades, health care digitalization has emerged as a topic of discussion among stakeholders in securing critical infrastructure. Understanding how health care professionals use digital technologies to provide high-quality care requires a stakeholder’s viewpoint.</p>
        <p>Technology integration is the implementation of electronic health records (EHRs), integration of Internet of Medical Things (IoMTs) devices, and broader IT infrastructure. The rapid integration of these technologies into health care systems created this pathway of improved access to medical services, enhanced patient outcomes, and streamlined workflows for health care providers and services in a borderless, continuous health care journey for transitional nations. Patient health care diagnostics reports and information can be accessed in real-time to enable managing medical history and response to emergency cases with the use of EHR systems. However, this has introduced significant vulnerabilities, making health care systems more susceptible to cyberattacks that could compromise sensitive patient data and disrupt health care services [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. As these vulnerabilities are linked to their areas of occurrence, they can be categorized and described through the interplay of technology, humans, and processes. This enables the application of sociotechnical systems (STS) theory and knowledge management approaches to health care systems [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. The National Institute of Standards and Technology (NIST) Cybersecurity Framework acknowledges that these vulnerabilities may arise from human factors, technology, and organizational processes [<xref ref-type="bibr" rid="ref6">6</xref>]. Additionally, the research by Kaberuka and Johnson [<xref ref-type="bibr" rid="ref7">7</xref>] on adapting the STAMP (Systems Theoretic Accident Model and Processes) for sociotechnical cybersecurity challenges in emerging nations acknowledges that human factors, organizational processes, and technology are of great concern. These vulnerabilities must be addressed for organizations to maintain resilience to cyberattacks and threats. NIST interagency and internal reports define these vulnerabilities as weaknesses in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>].</p>
        <p>The relationships among technology, humans, and organizational processes lead to vulnerabilities exploited by cybercriminals or state-sponsored attackers to gain access and control over critical health care infrastructure and sensitive data, thereby disrupting health services. These vulnerabilities can be considered a sociotechnical problem in a complex health care system [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. This problem can be solved using a sociotechnical approach to tackling vulnerabilities in health care systems. According to the 2024 report of the World Economic Forum, the cost of damage incurred by all forms of cybercrime resulting from humans, technology, and organizational processes could reach US $10.5 trillion in 2025. Some of the main sociotechnical cybersecurity problems in health care systems include the following. First, in 2021, ransomware attacks were launched on the health care systems of Ireland, known as the Health Service Executive, disrupting the health care services of 54 public hospitals, and IT systems nationwide were shut down. As a result, more than 80% of the IT environment was encrypted by cybercriminals, and information was exposed at a great financial cost [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Second, the WannaCry ransomware attacks in 2017 infected over 200,000 computers worldwide and disrupted services due to vulnerabilities in computer operating systems [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. Third, in 2017, Hollywood Presbyterian Medical Center was also attacked by ransomware that encrypted all health information. The medical center paid a ransom of US $17,000 to regain access to its data [<xref ref-type="bibr" rid="ref18">18</xref>]. Fourth, in 2016, Lukaskrankenhaus, a public hospital in Germany, was attacked by ransomware initiated through phishing. Computer systems were forced by authorities to shut down [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>Based on this knowledge gap identified, the following research questions (RQs) were asked: (1) What are the sociotechnical factors of vulnerabilities to cyberattacks that affect health care systems? (RQ 1) (2) What kind of framework is best suited for preventing vulnerabilities and responding to cyberattacks and threats in health care systems? (RQ 2). The objective of this study was to examine the dynamics of the factors of vulnerabilities to cyberattacks from a sociotechnical perspective and develop a conceptual framework for preventing vulnerabilities and responding to cyberattacks and threats in health care systems.</p>
      </sec>
      <sec>
        <title>Rationale and Sociotechnical Perspective</title>
        <sec>
          <title>Rationale</title>
          <p>The motivation for this research emerged following the increasing number of cyberattacks in health care organizations. Preventing cyberattacks requires an understanding of the multidimensional complexities of health care system factors of vulnerabilities. However, few studies have been conducted in the field of cybersecurity in health care from a sociotechnical perspective. Garcia-Perez et al [<xref ref-type="bibr" rid="ref20">20</xref>], Szczepaniuk and Szczepaniuk [<xref ref-type="bibr" rid="ref21">21</xref>], and Vukotich [<xref ref-type="bibr" rid="ref22">22</xref>] addressed cybersecurity challenges in health care systems from a technical perspective. Zimmermann and Renaud [<xref ref-type="bibr" rid="ref23">23</xref>] and Nicho and McDermott [<xref ref-type="bibr" rid="ref24">24</xref>] focused on addressing vulnerabilities in health care organizations using a social approach. This contributes to the literature by addressing the scholarly call for a sociotechnical cybersecurity framework in health care aimed at preventing vulnerabilities and responding to cyberattacks and threats [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>]. Nicho and McDermott [<xref ref-type="bibr" rid="ref24">24</xref>], Wani et al [<xref ref-type="bibr" rid="ref28">28</xref>], and Sutton and Tompson [<xref ref-type="bibr" rid="ref29">29</xref>] noted that a comprehensive cybersecurity framework that closes the sociotechnical gap within health care organizations’ cyberspace is important. A study conducted by Malatji et al [<xref ref-type="bibr" rid="ref17">17</xref>] found that “only four security frameworks, namely NIST, ISO/IEC, COBIT, and IT-CMF partially fulfilled the security requirements of the social dimension of a sociotechnical system” [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
          <p>Scholars have contributed to cybersecurity theory by developing various generic frameworks for different types of organizations [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]. This study proposed a conceptual sociotechnical cybersecurity framework for health care organizations to prevent vulnerabilities and respond to cyberattacks.</p>
        </sec>
        <sec>
          <title>STSs Perspective</title>
          <p>The STS theory examines the introduction of new technologies in organizations, their impact on humans, and the interactions between individuals of different skill sets, all within organized units to optimize the performance of social and technical systems [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. According to Trist [<xref ref-type="bibr" rid="ref33">33</xref>], an STS perspective in any organization comprises a set of integrated and interacting social and technical subsystems or constructs, such as people, infrastructure, technology, culture, goals, and processes. At their core, STSs conceptualize the design and performance of any organizational system that can only be optimized if there is an integration and interplay of the social and technical aspects, and they are deemed interdependent parts of a complex system.</p>
          <p>The term STSs originated with Emery and Tris in 1960, as they observed that systems involve complex interactions among people, machines, and the environmental aspects of the organizational system [<xref ref-type="bibr" rid="ref34">34</xref>]. The concept of STS theory was proposed by the Tavistock Institute as a method used to treat wounded soldiers and in constructions by Mumford [<xref ref-type="bibr" rid="ref35">35</xref>], Emery [<xref ref-type="bibr" rid="ref36">36</xref>], and Trist [<xref ref-type="bibr" rid="ref37">37</xref>]. The underlying assumption of STSs advocates that systems design should be a process that considers both social and technical aspects that influence the functionality and usage of interconnected computer-based systems [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
          <p>This study adopted an STS perspective on cybersecurity in the domain of health care that integrates technology, humans, and processes, subsystems, or constructs. In the context of cybersecurity in health care, the aforementioned constructs were established in the study conducted by Zimmermann and Renaud [<xref ref-type="bibr" rid="ref23">23</xref>]. <xref rid="figure1" ref-type="fig">Figure 1</xref> illustrates the 3 areas of STSs that were integrated in a holistic approach to prevent vulnerabilities and respond to cyberattacks in health care systems through an intervention framework [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Sociotechnical interplay.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e75584_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Protocol and Registration</title>
        <p>The review was performed based on the PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for Scoping Reviews) checklist by the JBI (Joanna Briggs Institute) [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. This study aimed to examine the dynamics of the factors of vulnerabilities to cyberattacks and propose a conceptual framework for health care systems. During the planning stage of this scoping review, a protocol was created that reflected sources of information, search strategies, inclusion and exclusion criteria, source selection, and data charting processes. This scoping review protocol was not registered. The PRISMA-ScR checklist is presented in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
      </sec>
      <sec>
        <title>Information Sources</title>
        <p>Three scientific databases—Web of Science, PubMed (MEDLINE), and Scopus—were searched to retrieve relevant papers, including both original research and review papers.</p>
      </sec>
      <sec>
        <title>Search</title>
        <p>Search queries were customized to the syntax and indexing features of each database. Keyword searches targeted the key concepts of cyberattacks and health care for PubMed, Scopus, and Web of Science. The title and additional abstract search terms were used to identify relevant publications. Truncation was used to identify word variations of the key concepts in different publications. The search terms were separated with the Boolean operators “AND” and “OR.”</p>
        <p>PubMed (MEDLINE) incorporated a combination of Medical Subject Headings, including computer security, health care facilities, workforce, services, and delivery of health care. An example of the search strategy in one of the databases is shown in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>. The detailed search strategy used for the other databases is provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
        <boxed-text id="box1" position="float">
          <title>Search strategy showing the search string for PubMed.</title>
          <p>“Computer Security”[Mesh] OR Cyberattack*[tw] OR Cybercrime*[tw] OR “Cyber Crime”[tw] OR Cyberthreat*[tw] OR “Cyber Threat”[tw] OR “Cyber Crises”[tw] OR “Cyber Risk”[tw] OR “Cyber Incident”[tw] OR Cyber Operation[tw] OR Cyberspace[tw] OR “Cyber Infrastructure”[tw] OR “Data Breach”[tw] OR “Data Security”[tw] OR “Firewall”[tw] OR “Information Security”[tw] OR “Information Technology Security”[tw] OR “Information Systems Security”[tw] OR “Security Incident”[tw] OR “Network Security”[tw] OR Ransomware[tw] OR Malware[tw] OR Phishing[tw] ) AND ( “Health Care Facilities, Workforce, and Services”[Mesh] OR “Delivery of Health Care, Integrated”[Mesh] OR “Health Care”[tw] OR “Health Information”[tw] OR “Health Information Management”[tw] OR “Healthcare Systems”[tw] OR “Health Systems”[tw] OR “Health System Infrastructure”[tw] OR “Medical Devices”[tw] OR Medical Technolog*[tw] OR Health Technolog*[tw] OR Health Care Technolog*[tw].</p>
        </boxed-text>
      </sec>
      <sec>
        <title>Eligibility Criteria</title>
        <p>The inclusion criteria for the papers were relevance to health care cybersecurity, coverage of cybersecurity issues, challenges, and solutions in health care systems. Only English-language papers published between 2012 and 2024 were included (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Inclusion and exclusion criteria.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="300"/>
            <col width="350"/>
            <col width="350"/>
            <thead>
              <tr valign="top">
                <td>Criterion</td>
                <td>Inclusion</td>
                <td>Exclusion</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Language of papers</td>
                <td>Papers in English</td>
                <td>Non–English-language papers</td>
              </tr>
              <tr valign="top">
                <td>Year of publication</td>
                <td>Papers published between 2012 and 2024</td>
                <td>Papers published outside the range of 2012-2024</td>
              </tr>
              <tr valign="top">
                <td>Research topic focus</td>
                <td>Cybersecurity and health care</td>
                <td>The topic is different from the topic areas</td>
              </tr>
              <tr valign="top">
                <td>Scope of work</td>
                <td>Key elements and factors that contribute to or lead to breaches, cyberthreats, cyberattacks, and vulnerabilities, and the development of a sociotechnical intervention framework for health care system resilience</td>
                <td>Topics outside the research scope of work</td>
              </tr>
              <tr valign="top">
                <td>Publication type</td>
                <td>Original research and review papers</td>
                <td>Research in-progress papers, editorial papers, and theses</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Selection of Sources of Evidence</title>
        <p>The retrieved papers were exported to the citation tool Zotero (Digital Scholar), in which duplicates were identified and removed using the duplicate item function. To assess eligibility, the titles and abstracts of each paper were analyzed by 2 of the authors. In instances in which the eligibility criteria for the papers were not clear, all 3 authors checked the papers and perused them to assess their relevance.</p>
      </sec>
      <sec>
        <title>Data Charting Process</title>
        <p>Using a standard Microsoft Excel (Microsoft Corp) spreadsheet, data from the studies that met the eligibility criteria were extracted independently by one of the authors and assessed by the other 2 authors to ensure data quality and consistency. This was used to identify the key characteristics of each study and relevant information regarding cyberattacks in health care.</p>
      </sec>
      <sec>
        <title>Data Items</title>
        <p>The key data items extracted included author, year of publication, country of origin, study design, aims, and key findings. The extracted data items were checked by the second author. A list of the extracted characteristics for the included studies (N=76) is provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref99">99</xref>].</p>
      </sec>
      <sec>
        <title>Critical Appraisal Within Sources of Evidence</title>
        <p>The quality of the source of evidence was checked by 2 authors using 3 different appraisal tools. Joanna Briggs Critical Appraisal Tools were used for qualitative research [<xref ref-type="bibr" rid="ref100">100</xref>], the Mixed Methods Appraisal Tool [<xref ref-type="bibr" rid="ref101">101</xref>] was used for mixed methods studies, and the Centre for Evidence-Based Medicine Critical Appraisal Checklist was used for cross-sectional studies [<xref ref-type="bibr" rid="ref102">102</xref>] and the Scale for the Assessment of Narrative Review Articles Appraisal Tool for narrative review papers [<xref ref-type="bibr" rid="ref103">103</xref>]. This was carried out to ensure that the sources of evidence were up-to-date, relevant, and reputable. For instances in which this was not clear, all 3 authors assessed the sources (<xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref> [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref99">99</xref>,<xref ref-type="bibr" rid="ref104">104</xref>]). However, the JBI Manual for Evidence Synthesis suggests that critical appraisal is not required for scoping review [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref105">105</xref>]. <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref> elucidates the different quality appraisal methods in detail. Studies were not excluded based on quality to capture as much literature as possible; however, low-quality studies were not used to draw conclusions.</p>
      </sec>
      <sec>
        <title>Synthesis of Results</title>
        <p>Thematic analysis was conducted manually following the 6-step approach described by Braun and Clarke [<xref ref-type="bibr" rid="ref106">106</xref>]. The 6-step approach involves familiarization with data, generating initial code by using sticky notes, searching for themes, reviewing the themes, defining and naming the themes, and producing the report. The analysis is hybrid in nature. The results were presented for the data extracted from the relevant papers in tabular form and descriptive formats (categorized into themes), which aligned with the objective and scope of the review.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>A total of 1375 papers were identified from the databases. Thereafter, 377 duplicate papers were removed, and 998 were screened. Subsequently, 213 full-text papers underwent screening. In the end, 76 papers were included in the review (<xref rid="figure2" ref-type="fig">Figure 2</xref> illustrates the selection process).</p>
        <p>The review of the extant literature confirmed the 3 factors of vulnerabilities to cyberattacks (technology, humans, and processes) from the lens of the STS theory in health care systems; they are presented in <xref ref-type="table" rid="table2">Tables 2</xref>-4. These factors were further categorized into twelve subfactors: (1) new technology integration, (2) complex system design and usability, (3) third-party application and plugin, (4) limited monitoring, (5) inadequate access control management, (6) insider threats, (7) shortage of skilled professionals and limited budget, (8) inefficient training, (9) security culture, (10) untimely incidence response and recovery plan, (11) inadequate policy and procedure, and (12) lack of regular audit and assessment. Subsequently, these 12 subfactors were outlined in descriptive formats.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>PRISMA diagram for paper selection. PRISMA: Preferred Reporting Items for Systematic Reviews and Meta-Analyses.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e75584_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Technology factors.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="670"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Technology</td>
                <td colspan="2">Studies, n (%)</td>
                <td>References</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>New technology integration</bold>
                </td>
                <td colspan="2">15 (20)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>New technology integration into health care systems creates a new landscape for health care systems to be vulnerable to cyberattacks and threats.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref41">41</xref>-<xref ref-type="bibr" rid="ref45">45</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inappropriate technology integration creates loopholes and interoperability and compatibility challenges that lead to cyberattacks and threats.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Interconnected medical and end point devices, when exposed to the internet, create security risks that are possible points of access for cyberattackers to gain access to health care systems.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref48">48</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Complex system design and usability</bold>
                </td>
                <td colspan="2">16 (21)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Complex system design tends not to be user-friendly; thus, its application in health care systems creates ambiguity in managing cloud-based big data and information, which results in exploitation by cybercriminals.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Design limitations on implanted medical sensor devices, such as assembly size and limited energy source, lead to connectivity and communication interruption for health care professionals in monitoring patients and data due to denial-of-service attacks. Such limitations also create encryption challenges.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Lack of a comprehensive or holistic framework for the security design in all layers of connected medical devices and software applications creates health information and privacy risks for internet-based device architecture and the operational environment.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Highly complex interconnected network systems increase the likelihood of vulnerabilities.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>,<xref ref-type="bibr" rid="ref99">99</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Third-party applications and plugins</bold>
                </td>
                <td colspan="2">7 (9)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Software internet-based products from third-party applications leverage vulnerabilities in medical devices and authentication errors that can be exploited by hackers to steal sensitive data or manipulate health care system operations.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Most incidents of vulnerability and cyberattacks in health care systems stem from a wide range of sources, such as operating systems or cloud-based software architectures of third-party developers.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref56">56</xref>-<xref ref-type="bibr" rid="ref58">58</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Third-party universal applications and devices, such as mobile apps and hardware integration in health care systems used for telemedicine applications, are not able to provide user anonymity when confronted with cyberattacks.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Health care plugin apps for mobile devices often face privacy and security issues due to developer deviation from compliance with regulatory standards.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref61">61</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Limited monitoring</bold>
                </td>
                <td colspan="2">11 (15)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inadequate capabilities for continuous monitoring of systems result in health information breaches and cyberattacks in health care systems.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref90">90</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inconsistent monitoring affects compliance, health care cyber-critical infrastructure updates, and organizational processes. This invariably constrains organizations’ preparedness to achieve the goals of security standards.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref65">65</xref>,<xref ref-type="bibr" rid="ref83">83</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Complexities in monitoring processes in health care organizations are a gateway to data breaches, cyber threats, and cyberattacks.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Inadequate access control management</bold>
                </td>
                <td colspan="2">8 (11)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Reactive health care systems that lack a strong access control system are prone to privilege escalation attacks.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>In the course of a malware incident, attackers can modify access control systems to grant administrative privileges to exploit health care systems.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Breakdown in access control management resulting from an update, server disruption, or malicious intrusion pushes health care organizations to shut down operational processes in the event of a cyberattack to reduce harm.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Human factors.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="670"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Humans</td>
                <td colspan="2">Studies, n (%)</td>
                <td>References</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>Insider threats</bold>
                </td>
                <td colspan="2">7 (9)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Insiders can introduce threats and vulnerabilities through inadvertent actions, such as inappropriate behavior, clicking phishing links, and falling victim to cyber threats.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Most of the breaches that occur in health care organizations originate with insiders stealing and leaking sensitive information to cybercriminals for money or political gain.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Negligence by internal IT teams in failing to terminate vendor accounts or agreements in intersupport systems of care could create an entry point for vulnerability to cyberattacks.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref61">61</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Inefficient training</bold>
                </td>
                <td colspan="2">9 (12)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Health care cybersecurity training implementations are largely misdirected, with a focus on cybersecurity professionals and information and communication technology (ICT) departments only, while neglecting health care–based professionals.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ineffective cybersecurity training helps cybercriminals gain access to a health care system’s sensitive information through social engineering methods such as phishing, malware, and baiting.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Training that lacks blended skill development is ineffective in achieving a sustainable goal to mitigate cyber exploitation and ensure personal development for health care professionals.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Shortage of skilled professionals and limited budget</bold>
                </td>
                <td colspan="2">15 (20)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Another reason for increasing cyber breaches of sensitive health information is the limited budget allocation for cybersecurity.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2"> [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref68">68</xref>-<xref ref-type="bibr" rid="ref70">70</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Health care organizations endure poor security management in containing attacks and cybercrime, and developing new strategies to counteract cyber threats and breaches due to a shortage of skilled professionals and limited budget.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The shortage of cybersecurity experts in health care organizations creates a vacuum for attacks and breaches, while also hindering the development of cybersecurity knowledge among employees.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref73">73</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Security culture</bold>
                </td>
                <td colspan="2">11 (15)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Lack of security culture awareness among health care organization staff, coupled with inadequate training in behavior, interactions, and meaningful work practices within the work environment, constitutes a significant factor that may facilitate improper data handling practices and protection.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref74">74</xref>-<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref96">96</xref>,<xref ref-type="bibr" rid="ref97">97</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Novel viral infections and pandemics requiring rapid technological advancement in health care diagnostics invariably affect behavioral patterns at work and the daily cybersecurity activities of employees.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2"> [<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref78">78</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Poor management of organizational culture may affect employees’ cybersecurity behaviors and attitudes toward technology use, thereby increasing the risk of cyberattacks.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2"> [<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref78">78</xref>-<xref ref-type="bibr" rid="ref81">81</xref>]</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Process factors.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="670"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="150"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Processes</td>
                <td colspan="2">Studies, n (%)</td>
                <td>Reference</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="3">
                  <bold>Untimely incident response and recovery plan</bold>
                </td>
                <td colspan="2">12 (16)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Ineffective operational communication systems create poor incident response and preparedness to respond to threats and cyberattacks.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref82">82</xref>-<xref ref-type="bibr" rid="ref84">84</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Containing an attack and a breach in a health care system through postincident response takes approximately 100 days or more before a health information system is restored to normal, safe mode.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref85">85</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Cybersecurity strategies in health care systems are often reactive instead of proactive in cyber defense mechanisms, backup, and recovery.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref86">86</xref>,<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref98">98</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>There is limited research on cybersecurity response strategies, which is a great concern.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref87">87</xref>-<xref ref-type="bibr" rid="ref89">89</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Inadequate policies and procedures</bold>
                </td>
                <td colspan="2">11 (15)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Standard policy protocol for most health care organizations is inadequate to meet best practice measures in cybersecurity.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref92">92</xref>-<xref ref-type="bibr" rid="ref94">94</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Some policies and procedures set out by regulatory bodies are cumbersome in laying down information security expectations and are complex to follow. For example, breaches below 500 are neglected and not taken into account.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Policies in line with secure behavioral awareness are inadequate for safeguarding health care systems from cyber breaches.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref90">90</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Lack of regular audits and assessments</bold>
                </td>
                <td colspan="2">10 (13)</td>
                <td>
                  <break/>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Most health care organizations do not perform regular or consistent security audits and risk assessments as required by regulations and best practices to visualize security risk levels.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Most health care organizations do not categorize their risks into external and internal risks or have an effective risk plan in place.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref84">84</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Conducting an assessment and audit of a complex sociotechnical system in cybersecurity fails to factor in technology, organizational environment, and humans as a whole.</td>
                <td colspan="2">
                  <break/>
                </td>
                <td colspan="2"> [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Technology Factors</title>
        <sec>
          <title>Integration of New Technology</title>
          <p>Smart health care systems have successfully procured and integrated medical cyber-physical systems technologies with the Internet of Things to facilitate operations using virtual networks, applications, and devices, as well as to monitor diagnoses, manage treatment, and manage administrative processes in the delivery of health care services [<xref ref-type="bibr" rid="ref11">11</xref>]. This new technology integration has helped to streamline health care for effective service delivery. The integration of these digital technologies has evolved as they create complex interconnected ecosystems, making it challenging to implement and maintain robust security measures across all components [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref47">47</xref>].</p>
          <p>Inappropriate technology integration increases the vulnerability of health care organizations to cyberattacks and breaches when the complex STSs integration process and standards are not properly followed or managed [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref90">90</xref>]. Additionally, it poses a risk when data is exchanged between the cloud and electronic records, or when it travels within the health care delivery ecosystem. Some of the reasons for the risk are unsupported integration, inappropriate standard implementation [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>], lack of secure development in the ideation stage [<xref ref-type="bibr" rid="ref107">107</xref>], ineffective communication, and interoperability issues. These issues, in turn, can give cybercriminals unauthorized access to health information or data because of such vulnerabilities in technology [<xref ref-type="bibr" rid="ref64">64</xref>]. Furthermore, it is necessary for health care system actors to know that the integration of medical devices and interconnectivity does not equate to interoperability; likewise, interoperability does not equate to the security of medical devices and data protection.</p>
        </sec>
        <sec>
          <title>Complex System Design and Usability</title>
          <p>Complex design and usability can lead to security vulnerabilities in health care information systems [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref104">104</xref>] by affecting data processing, confidentiality, availability, integrity, and design limitations. It creates friction for staff, which can lead to unhealthy security practices in monitoring the IoMT devices and compromising patient safety and privacy [<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. Additionally, complex and poor system design can make it easier for hackers to exploit vulnerabilities in medical devices and systems, resulting in cyber incidents such as phishing attacks or other social engineering tactics to trick users into giving up their login credentials or downloading and executing malicious software [<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref85">85</xref>]. This can harm patients in an emergency and slow care delivery, which can be linked to biomedical nonmaleficence principles [<xref ref-type="bibr" rid="ref108">108</xref>]. In managing complex health IT challenges, adopting a user-centered approach to health care service operations is pivotal for preventing vulnerabilities and cyberattacks in health care systems [<xref ref-type="bibr" rid="ref12">12</xref>].</p>
          <p>Complex designs and user interfaces of health care devices and applications make it difficult to secure the valuable information in health care systems. Poor design and usability can lead to human user errors, such as accidentally exposing sensitive patient information or mistakenly changing critical medical settings or configurations. The emerging usability literature has highlighted these sociotechnical shortcomings, which could lead to threats and medical errors in health care systems [<xref ref-type="bibr" rid="ref68">68</xref>]. User satisfaction—whether for patients or health care professionals—at every stage of task performance is enhanced by a friendly design process that prioritizes usability [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], design, and data processing. This, in turn, facilitates the effective and efficient delivery of health care services.</p>
        </sec>
        <sec>
          <title>Third-Party Applications and Plugins</title>
          <p>The adoption of third-party applications and plugin software in modern-day smart health care systems can be used in many more ways than traditional standalone software in health care delivery. Third-party application software, in the form of software as a service, has evolved to make use of web-based, intelligent chatbots and large language models. The complexity of these technologies makes it difficult to control their service dynamics as they become vulnerable to cyberattacks [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref109">109</xref>]. In some cases, the vulnerability of cyber-critical systems that expose health information and patient privacy is not only an issue of the medical device, but also a software malfunction that could put organizations at risk and affect the quality of services [<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref110">110</xref>].</p>
          <p>Hackers can embed malicious software, such as ransomware, in application software or operating systems. Such malicious software can execute and replicate viruses in health care systems by acting like a legitimate third-party software program. It can then create a backdoor to gain access to sensitive information and organization files for launching cryptolocker attacks [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref111">111</xref>]. Additionally, cybercriminals use third-party software and application plugins to impersonate health care service providers, all the while having malicious motives as part of organized syndicates illegally collecting health data. Some medical applications hosted on mobile systems are illegitimate third-party apps, which are another source of privacy violations and data leakage [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref112">112</xref>,<xref ref-type="bibr" rid="ref113">113</xref>].</p>
          <p>Malware can easily be introduced to the medical network of systems when the IT team of the medical device software application makes an error during the development stage. It is estimated that 90% of incidents or breaches occur through exploiting vulnerabilities in a device system’s software application program [<xref ref-type="bibr" rid="ref114">114</xref>]. The use of implanted devices always has issues of software malfunction and update-related problems [<xref ref-type="bibr" rid="ref1">1</xref>]. For instance, a 2013 analysis of mobile medical health fitness apps showed that over 40% of paid medical applications were completely lacking privacy policies, and 40% of the applications stored sensitive patient information, such as financial details, biodata, and addresses [<xref ref-type="bibr" rid="ref60">60</xref>]. While only 50% of mobile apps encrypt the personal identifying information sent over the internet, 80% of these third-party applications store this personal identifying information on a local device without encryption, which is liable to be accessed [<xref ref-type="bibr" rid="ref115">115</xref>]. Having control over third-party software applications and systems while also focusing on developing software from the same device manufacturer will help curb the risk of data breaches and protect sensitive health care–related information [<xref ref-type="bibr" rid="ref42">42</xref>].</p>
          <p>Researchers seem to relate cyber issues to medical devices, neglecting the fact that without operating systems and application software, medical devices would not execute other clinical functions and administrative services in delivering health care [<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref83">83</xref>]. Regularly updating system software is necessary to improve security against new threats and viruses, since over 90% of breaches stem from programmable software applications or boot systems kernel development, which can be used for implanting viruses in computer systems.</p>
        </sec>
        <sec>
          <title>Limited Monitoring</title>
          <p>Limited monitoring of the health care systems’ critical infrastructure increases the risk of delayed detection of threats and vulnerabilities, allowing them to propagate in the system and cause even greater damage [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. Perimeter monitoring technology, such as antivirus and firewalls, also called detection technology, has been developed to recognize known variants of viruses and other threats. In the era of fast-paced technology advancement, ransomware coders are also advancing with detection technology by reprogramming malicious code so that it can remain undetected by the monitoring scanner [<xref ref-type="bibr" rid="ref52">52</xref>]. Despite the advancement of technology, many health care organizations are still using traditional security monitoring procedures to protect sensitive information and health care systems. Continuous monitoring of health care systems in both real-time and offline modes is essential to enable detection and mitigation of threats [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref65">65</xref>].</p>
        </sec>
        <sec>
          <title>Inadequate Access Control Management</title>
          <p>New technology in health care systems requires role-based access control management for professionals and organizations in managing sensitive resources and operations. Many health care organizations become victims of health information breaches or cyberattacks due to inadequate access control management across different technology platforms and applications. This creates a weak access point for cybersecurity operational integration, which results in system flaws, compatibility issues, and interoperability challenges that facilitate access for cybercriminals to gain entry into the health care system network. Strong access control policies help foster effective access control and identity management [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref84">84</xref>]. Managing employee privileges and training them not to share passkeys can help prevent lapses in access authorization while ensuring role-based access control to strengthen identity and access management in health care systems [<xref ref-type="bibr" rid="ref71">71</xref>].</p>
          <p>Health care organizations must ensure that their network has strong control systems and structures for better identity management to avoid unauthorized access, breaches of sensitive information, and identity theft [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]. Weak cybersecurity control and identity management could stem from software applications, human factors, and organizational management processes as a result of outdated systems and technology [<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref116">116</xref>-<xref ref-type="bibr" rid="ref118">118</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Human Factors</title>
        <sec>
          <title>Insider Threats</title>
          <p>Insider threats have recently been seen as a growing challenge. Research has attributed these specific threats to the emergence of connected health care IT, which is one of the causes of data breaches or leakages of protected health information [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref119">119</xref>]. However, insider threats are linked to the human element of health care IT systems, wherein human error has been seen as one of the major sources of vulnerabilities in the critical cyber infrastructure [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref67">67</xref>,<xref ref-type="bibr" rid="ref96">96</xref>]. The root causes of insider threats include insecure behavior by employees and organizations’ inadequate investment in employees’ cybersecurity skills for social and technical know-how [<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref120">120</xref>]. In contrast, during the era of nontechnical application of care delivery, insider threats were less visible to organizations when protected health information was filed through paper-based manual storage systems. The traditional breaches from insider threats were physical breaches, such as the theft of patients’ valuable information, theft of files and computers, or missing paper health care records [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]. The missing data or breach in patient information was known only to the health care organizations, so the collection of new health records from patients would begin without the need to notify patients about General Data Protection Regulation or Health Insurance Portability and Accountability Act violations [<xref ref-type="bibr" rid="ref95">95</xref>].</p>
          <p>Research has also revealed that since the emergence of the interconnectivity of records, the level of insider threats and attacks has increased tremendously, as such interconnectivity provides multiple gateways for access in a remote location and setting [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref61">61</xref>]. Furthermore, the level of insider threats in this era of digital health processes will be more accountable with proper cybersecurity systems and monitoring compared to the paper-based process, where the insider goes unnoticed and underreported. Research has also revealed that, between 2019 and 2024, organizations reported that insider threats increased from 66% to 74% [<xref ref-type="bibr" rid="ref119">119</xref>]. The literature has also revealed that insiders, rather than outsiders, contributed to about 70% of data fraud and breaches in an organization [<xref ref-type="bibr" rid="ref86">86</xref>]. This is also attributed to a lack of employee cybersecurity ethics, management implementation of data integrity, and privacy of patient records as a culture of ethics in the workplace [<xref ref-type="bibr" rid="ref108">108</xref>]. Authors have highlighted different issues of insider threats, digging deep into the risks and issues of insider threats and breaches in health care organizations [<xref ref-type="bibr" rid="ref67">67</xref>].</p>
        </sec>
        <sec>
          <title>Inefficient Training</title>
          <p>Inefficient training of employees can have a significant negative impact on health care systems, most importantly when a health care professional lacks the knowledge and understanding of cybersecurity vulnerabilities and threat patterns of the health care system [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. It is the duty of health care organizations to give proper training and awareness of cyber threats and attacks to their staff [<xref ref-type="bibr" rid="ref64">64</xref>,<xref ref-type="bibr" rid="ref65">65</xref>]; otherwise, employees may easily become vulnerable, resulting in data breaches of sensitive health information [<xref ref-type="bibr" rid="ref70">70</xref>]. It is important to conduct training assessments for employees; otherwise, it will be difficult to ascertain the extent of the training required [<xref ref-type="bibr" rid="ref62">62</xref>]. Phishing training, including gamification-based methods, is one approach to assessing employee knowledge. Training results can then be used to design a curriculum that is tailored to work processes, ensuring that employees acquire the training needed to enhance IT security awareness and readiness [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref67">67</xref>]. It is important that health care professionals who use critical hospital infrastructure are trained in comprehensive cybersecurity user applications, including sociotechnical techniques for dealing with health care cybersecurity vulnerabilities, threats, and risks [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
        </sec>
        <sec>
          <title>Shortage of Skilled Professionals and Limited Budget</title>
          <p>Cybersecurity breaches in health care increase daily due to a growing shortage of skilled professionals and limited budgets, posing a significant concern [<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref73">73</xref>]. This concern is critical for health care organizations due to the large amounts of valuable sensitive data stored in the EHR system and cloud. This sensitive data includes medical records, insurance information, and financial data [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
          <p>Many health care institutions lack the cybersecurity expertise required to defend their digital health care systems from cyberattacks [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. However, while the demand for cybersecurity experts in health care is high, the supply is low. As a result, health care organizations may be subjected to complex assaults on critical infrastructure requiring specific knowledge [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref71">71</xref>]. For instance, cybercriminals take advantage of employees’ low skill sets to exploit them [<xref ref-type="bibr" rid="ref52">52</xref>]. This shortage of skills continues to leave health care organizations challenged in the changing environment of health care systems, which constrains the organizations from detecting and preventing cyberattacks in health care systems [<xref ref-type="bibr" rid="ref54">54</xref>]. Furthermore, limited investment in cybersecurity systems and technology accelerates vulnerabilities, threats, and attacks in health care organizations [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref47">47</xref>,<xref ref-type="bibr" rid="ref104">104</xref>] due to obsolete techniques that lag behind digital trust and security protection. In some cases, health care businesses have limited cybersecurity budgets, making it difficult to invest in the required technologies and resources for defending themselves against threat actors and vulnerabilities [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref68">68</xref>]. The shortage of skilled professionals and limited budgets can lead to major cybersecurity vulnerabilities in the health care system [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref69">69</xref>].</p>
        </sec>
        <sec>
          <title>Security Culture</title>
          <p>Security culture plays a crucial role in addressing cyber threats in health care organizations. To properly protect information assets, information security behavior is essential [<xref ref-type="bibr" rid="ref79">79</xref>]. The norms, values, and attitudes of health care professionals contribute to the development and maintenance of a robust security culture in health care organizations that actively support security initiatives [<xref ref-type="bibr" rid="ref121">121</xref>]. Thus, employees’ behavior with regard to data privacy is important for the effectiveness of cybersecurity in the workplace environment [<xref ref-type="bibr" rid="ref70">70</xref>]. Insecure behavior has been identified as one of the most significant factors contributing to vulnerabilities in cybersecurity [<xref ref-type="bibr" rid="ref76">76</xref>]. Its 4 key components are lack of awareness and experience, unauthorized workflows, behavior prioritization, and environmental appropriateness [<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref81">81</xref>].</p>
          <p>In this digital health care era, the social influence of peers is a critical driver that influences health care professionals’ motives regarding data privacy policy and security. Furthermore, attitude plays a mediating role in employees’ motives regarding compliance with data privacy and policy [<xref ref-type="bibr" rid="ref97">97</xref>]. Digitalization in health care organizations can be influenced by attitudes toward cybersecurity, subjective norms, and perception of control over security measures [<xref ref-type="bibr" rid="ref9">9</xref>]. Insecure behaviors and attitudes of employees and patients regarding the use of technology increase vulnerabilities to cyberattacks.</p>
        </sec>
      </sec>
      <sec>
        <title>Process Factors</title>
        <sec>
          <title>Untimely Incident Response and Recovery Plan</title>
          <p>Untimely incident responses and recovery plans in the event of health information breaches and cyberattacks in health care systems undermine public, stakeholder, and patient trust that health care organizations or hospitals can manage their sensitive health information [<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref111">111</xref>]. A planned or coordinated response and recovery strategy determines the health care systems’ ability to contain breaches or threats [<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref88">88</xref>]. Effective response and recovery plans can mitigate the severity of cyberattacks in health care systems, reducing their impact and preventing future occurrences [<xref ref-type="bibr" rid="ref71">71</xref>,<xref ref-type="bibr" rid="ref82">82</xref>]. Despite this, many health care organizations ignore incident response and recovery plans as part of their cybersecurity strategy and measures for protecting health care systems [<xref ref-type="bibr" rid="ref84">84</xref>,<xref ref-type="bibr" rid="ref122">122</xref>].</p>
          <p>The WannaCry cyberattack incident against the UK’s National Health Service metamorphosed to infect larger systems of health care. This was due to the negligence and poor response strategies associated with the attack [<xref ref-type="bibr" rid="ref87">87</xref>]. Although the National Health Service management was informed of the vulnerability of the Windows operating system, the IT team was slow to respond to updating the legacy system [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref69">69</xref>]. To mitigate both visualized and hidden cyberattacks in health care systems, the cybersecurity IT team must establish an effective response strategy that integrates evolving technological advancements with new approaches to advanced persistent threats [<xref ref-type="bibr" rid="ref58">58</xref>,<xref ref-type="bibr" rid="ref116">116</xref>].</p>
          <p>In some cases in which health care organizations were attacked with ransomware, the organizations lost all health care data when they refused to pay a ransom to a cybercriminal. This was due to the lack of a contingency plan, backup, and recovery systems [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref85">85</xref>]. Health care organizations are expected to have backup and recovery plans that enable failover of health care data in the event of a cyberattack [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref83">83</xref>] to avoid disruption of services [<xref ref-type="bibr" rid="ref82">82</xref>].</p>
        </sec>
        <sec>
          <title>Inadequate Policies and Procedures</title>
          <p>Many health care organizations still operate under traditional information security policies and procedures despite technological advancements and the increase in health care breaches and cyberattacks. Traditional information security policies and old-order operational procedures have become obsolete as technology has evolved [<xref ref-type="bibr" rid="ref93">93</xref>]. Security policies and operational procedures form the foundation for health care systems’ defense against cyber threats and vulnerabilities because they dictate how sensitive health information is protected, incidents are handled, and employees are trained on cybersecurity programs to ensure best practices [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]. Inadequate policies and procedures predispose health care systems to the risk of cyberattacks and threats [<xref ref-type="bibr" rid="ref121">121</xref>]. Inadequate policies can stem from several factors, such as underestimation of cyber threats, lack of awareness to engage with cybersecurity issues, and underinvestment [<xref ref-type="bibr" rid="ref85">85</xref>]. For example, Health Insurance Portability and Accountability Act regulations state that cybersecurity breaches affecting fewer than 500 people should not be reported or fined, which can create ambiguity and gaps in enforcement [<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>]. Additionally, this may encourage organizations with fewer than 500 patients to neglect the security and privacy of this group of patients. Such organizations might endure breaches without disclosing them to the necessary data protection and regulatory authority. The 2015 Anthem breach is a case study of one of the largest breaches, in which the personal information of over 78 million individuals was exposed as a result of inadequate encryption, weak access control policies, and human error [<xref ref-type="bibr" rid="ref70">70</xref>].</p>
          <p>As technology develops, some health care organizations fail to implement new policies that align with evolving technology and the compliance standards necessary to protect health care systems and ensure resilience in managing health information and the entire ecosystem [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref69">69</xref>,<xref ref-type="bibr" rid="ref104">104</xref>].</p>
        </sec>
        <sec>
          <title>Lack of Regular Audit and Assessment</title>
          <p>Existing research has shown that many health care organizations conduct security audits and assessments once a year. Health care organizations that do not engage in regular and comprehensive cybersecurity audits and risk assessments often fail to identify cyberthreats and vulnerabilities in health care systems [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref91">91</xref>]. Furthermore, in the absence of regular security audits and assessments health care organizations may struggle to detect vulnerabilities, making it easier for cybercriminals to exploit the weaknesses in their systems [<xref ref-type="bibr" rid="ref45">45</xref>]. For instance, the cause of the SolarWinds supply chain attack, in which the back door was created by a cybercriminal without detection, is a case in which sensitive information was harvested for more than a year before being detected only after the cybercriminals exposed the information in the public domain. A regular audit ensures the proper monitoring and evaluation of employee behaviors and security practices [<xref ref-type="bibr" rid="ref84">84</xref>]. Additionally, with these measures, health care organizations can easily detect vulnerabilities and risk levels of third-party applications through comprehensive and regular audits of the health care systems [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref91">91</xref>].</p>
          <p>Health care organizations that do not conduct monthly and quarterly audits and assessments will significantly increase their cybersecurity risk profile, which may lead to the possibility of continual breaches [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref71">71</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Taxonomy Factors of Vulnerabilities to Cyberattacks</title>
        <p><xref ref-type="table" rid="table5">Table 5</xref> indicates the taxonomy-related factors of vulnerabilities to cyberattacks, unit-related factors of vulnerabilities to cyberattacks, types of cyberattacks, and their effects on health care organizations.</p>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Taxonomy factors of vulnerabilities to cyberattacks.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="170"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="300"/>
            <col width="0"/>
            <col width="200"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Factors of vulnerabilities to cyberattacks</td>
                <td colspan="2">Unit factors of vulnerabilities to cyberattacks</td>
                <td colspan="2">Types of cyberattacks</td>
                <td colspan="2">Effect on the health care organization</td>
                <td>Reference</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="10">
                  <bold>Technology</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>New technology integration</td>
                <td colspan="2">EHRs<sup>a</sup>, medical and network devices, and software</td>
                <td colspan="2">Ransomware, cryptojacking, and DOS<sup>b</sup></td>
                <td colspan="2">Health information breaches, legal fines from regulators, operational disruptions, data loss, and reputation damage</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref70">70</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Complex system design and usability</td>
                <td colspan="2">EHRs, medical and network devices, and software</td>
                <td colspan="2">Ransomware and DOS</td>
                <td colspan="2">Operation disruptions, cyber breaches, loss of trust, legal fines from regulators, financial loss, and reputation damage</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref61">61</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Third-party application and plugin</td>
                <td colspan="2">EHRs, medical and network devices, and software</td>
                <td colspan="2">Phishing, DOS, and ransomware</td>
                <td colspan="2">Cyber breaches, health care security weakness, operational disruption, compromised safety, and data loss</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref109">109</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Limited monitoring</td>
                <td colspan="2">EHRs, medical and network devices, and applications</td>
                <td colspan="2">DOS, worm infection, ransomware, and data exfiltration</td>
                <td colspan="2">Patient safety risk, service disruption, data breaches, data loss, compromise of Confidentiality, Integrity, and Availability, and operational handicap</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref52">52</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inadequate access control management</td>
                <td colspan="2">EHRs, medical and network devices, and applications</td>
                <td colspan="2">Ransomware, DOS, privilege escalation attack, and phishing</td>
                <td colspan="2">Patient safety risk, data breaches, identity theft, manipulation of data, and possible ransom payments</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref66">66</xref>,<xref ref-type="bibr" rid="ref92">92</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Humans</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Insider threats</td>
                <td colspan="2">Health care professionals and EHRs</td>
                <td colspan="2">Identity theft, espionage, and sabotage</td>
                <td colspan="2">Service disruption, loss of trust, sale of data, sensitive data breaches, and data loss</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref70">70</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inefficient training</td>
                <td colspan="2">Health care professionals</td>
                <td colspan="2">Phishing, worm infection, and ransomware</td>
                <td colspan="2">Financial loss, fine imposition, huge cost implication, data loss, incorrect diagnosis, and error treatment</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref70">70</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Shortage of skilled professionals and limited budget</td>
                <td colspan="2">Health care professionals</td>
                <td colspan="2">Ransomware, viruses, phishing, and DOS</td>
                <td colspan="2">Patient safety risk, decreased secure care quality, inadequate compliance, insecure health care services, budget reallocation, and data breaches</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref72">72</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Security culture</td>
                <td colspan="2">Health care professionals</td>
                <td colspan="2">Ransomware, virus, phishing, DOS, DDOS<sup>c</sup></td>
                <td colspan="2">Insecure behavior, reputation damage, loss of trust, identity theft, security negligence, data breaches, and poor service delivery</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref70">70</xref>,<xref ref-type="bibr" rid="ref77">77</xref>,<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref97">97</xref>]</td>
              </tr>
              <tr valign="top">
                <td colspan="10">
                  <bold>Processes</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Poor incident response and recovery plan</td>
                <td colspan="2">Health information, medical devices, applications, health care professionals, and patients</td>
                <td colspan="2">Ransomware, crypto jacking, DNS<sup>d</sup> spoofing, and DOS</td>
                <td colspan="2">Health information breaches, identity theft, legal suits, health care service disruption, ransom payments, loss of data, hard-to-recover data, and financial loss</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref82">82</xref>,<xref ref-type="bibr" rid="ref85">85</xref>,<xref ref-type="bibr" rid="ref98">98</xref>,<xref ref-type="bibr" rid="ref123">123</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Inadequate policy and procedure</td>
                <td colspan="2">Health information, medical devices, applications, health care professionals, and patients</td>
                <td colspan="2">Ransomware, worm infection, phishing, and DOS</td>
                <td colspan="2">Service disruption, possible patient harm, compromised sensitive data, regulatory fines, violation of privacy, financial loss, poor security strategies, and data breaches</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref61">61</xref>,<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref95">95</xref>]</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Lack of regular audit and assessment</td>
                <td colspan="2">Health information, medical devices, applications, health care professionals, and patients</td>
                <td colspan="2">Man-in-the-middle attack, crypto jacking, and worm infection</td>
                <td colspan="2">Reputation damage, possible patient harm, service disruption, privacy violation, unauthorized access freedom, breaches of sensitive information, and data loss</td>
                <td colspan="2">[<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>EHR: electronic health record.</p>
            </fn>
            <fn id="table5fn2">
              <p><sup>b</sup>DOS: denial of service.</p>
            </fn>
            <fn id="table5fn3">
              <p><sup>c</sup>DDOS: distributed denial of service.</p>
            </fn>
            <fn id="table5fn4">
              <p><sup>d</sup>DNS: domain name system.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of the Findings</title>
        <p>This study examined the dynamics of the factors of vulnerability to cyberattacks in the 3 core areas of the STSs theory of technology, humans, and processes in health care systems through a scoping review of 76 papers.</p>
        <p>This study found that the integration of new technology can be challenging in protecting health care systems from cyberattacks in the absence of an appropriate intervention. The findings also showed that complexities in system design present adaptability challenges for health care professionals; thus, cyberspace is prone to a high-risk incidence of threats. Furthermore, third-party software limits security in smart health care, which has various impacts on health organizations.</p>
        <p>The findings revealed that internal threats existing in health care systems are not linked only to health care professionals but also to IT teams. Additionally, inefficient cybersecurity training exposes health care organizations to vulnerabilities and cyberattacks. The findings also showed that inadequate investment in human capital and limited finances contribute to poor cybersecurity management. This study further found that the decline in security culture is based on cultural deviation and radical technological change in health care organizations, which is deeply rooted in the behaviors and attitudes of employees.</p>
        <p>The present study found that most health care organizations are unprepared and do not have a proactive incident response and recovery plan in place in the event of a cyberattack [<xref ref-type="bibr" rid="ref85">85</xref>]. The communication gap, untimely postincident response, cybersecurity strategies, and limited research on cybersecurity responses contribute immensely to cyber threats and cyberattacks. Furthermore, limitations in continuous monitoring include inadequate capabilities, inconsistent monitoring, and complex monitoring processes that increase cyber insecurity in health care organizations. The findings also indicate that cybersecurity policies and procedures can be complex and inadequate in shaping the security of health care cyberspace. Additionally, cybersecurity auditing and assessment can be inconsistent, fail to classify risks as internal or external, and include nonholistic perspectives of the STS. The study further found that weak access control management and breakdowns facilitate the exploitation of sensitive data in health care systems.</p>
        <p>The findings showed that despite the similar unit factors of vulnerabilities to cyberattacks for the subfactor of technology and the occurrence of various types of cyberattacks, the effect on health care organizations remains the same. Additionally, despite the similar unit factors of vulnerabilities to cyberattacks for the subfactor of humans, the types of cyberattacks that occurred differed to some extent; however, the effect on health care organizations was somewhat varied. Furthermore, despite the similar unit factors of vulnerabilities to cyberattacks for the subfactors of processes, the types of cyberattacks that occurred were similar to a great extent; consequently, the effects on health care organizations were also similar to a great extent. In general, this study found that processes involve both technology and humans relative to the unit factors of vulnerabilities to cyberattacks. This confirms the sociotechnical interplay among the factors of vulnerabilities in health care systems [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
      </sec>
      <sec>
        <title>Sociotechnical Cybersecurity Framework</title>
        <sec>
          <title>Overview</title>
          <p>The three core constructs of STSs that can protect health care systems from vulnerabilities to cyberattacks and breaches are technology, humans, and processes [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. In the context of this study, the three constructs of STSs are referred to as the factors of vulnerabilities, which are the areas in which vulnerabilities occur.</p>
          <p>This study proposed a conceptual sociotechnical cybersecurity framework for health care systems that entails the factors of vulnerabilities, IT team, cyberattackers, and cybersecurity knowledge management and intelligence response (CKMIR). The framework incorporates features such as intrusion detection and response, user behavior monitoring, threat intelligence, vulnerability scanning, alert sensors, cloud-based repositories, and recovery mechanisms as a comprehensive approach in responding to the vulnerabilities, cyberattacks, and threats in health care systems; this framework is presented in <xref rid="figure3" ref-type="fig">Figure 3</xref>.</p>
          <p>The components of the sociotechnical cybersecurity framework are explained in the following sections.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Conceptual sociotechnical cybersecurity framework. DDOS: distributed denial of service; IT: information technology.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e75584_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Factors of Vulnerabilities</title>
          <p>The factors of vulnerabilities involve humans, technology, and processes, which are interwoven in the sociotechnical cybersecurity framework [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref87">87</xref>].</p>
        </sec>
        <sec>
          <title>IT Team</title>
          <p>The IT team is one of the human elements in the loop that provides technical support, maintenance, and remediation for the health care system. The IT team includes software engineers, system developers, cybersecurity experts, compliance officers, IT support staff, and network engineers. They are responsible for the day-to-day health of IT operations to ensure smooth and secure health care service delivery.</p>
        </sec>
        <sec>
          <title>Health Care Professionals</title>
          <p>Health care professionals include doctors, nurses, administrative staff, etc. The doctors consult with the patients online and onsite, access their medical history from the cloud through the EHR system, and prescribe medication, while the nurses monitor patients’ health, provide care, and access patients’ medical information through the medical network. Health care administrative staff are responsible for administrative and clinical tasks, such as scheduling staff and appointments for patients to ensure the practice runs smoothly.</p>
        </sec>
        <sec>
          <title>Cyberattackers</title>
          <p>The cyberattacker is a cybercriminal who exploits the health care system using sophisticated techniques to launch attacks on health care–critical infrastructure. They launch attacks through denial of service, ransomware, and identity theft of patient health information. The stolen information is sold on the dark web for financial gain.</p>
        </sec>
        <sec>
          <title>About CKMIR</title>
          <p>The CKMIR intrusion detection feature systematically analyzes network traffic, human behavior, technology, and processes in real time to optimally detect and isolate known and unknown cyber threats and attacks in health care systems to enable remediation.</p>
          <p>The CKMIR user behavior monitoring feature identifies and analyzes the patterns of human behavior and interactions within health care systems, such as login times, access patterns, file transfers, and application usage, as well as internal and external threats, to determine unauthorized access and compromised accounts.</p>
          <p>The CKMIR threat intelligence feature collects, analyzes, and interprets raw data on the intent, opportunity, and capability of malicious actors and shares structured information with the IT team through actionable intelligence.</p>
          <p>The CKMIR vulnerability scanning feature scans, detects, identifies, and classifies technology, human, and process factors of vulnerabilities in health care systems and provides countermeasures for cyber threats.</p>
          <p>The CKMIR alert sensor senses isolated cyber threats and attacks and sends alerts to the IT team in real time.</p>
          <p>The CKMIR cloud repository and recovery feature store and back up encrypted data, critical system files, and security event records to recover data in the event of a cyberattack.</p>
        </sec>
        <sec>
          <title>Drivers</title>
          <p>The drivers are the factors that determine the transition of cybersecurity in health care organizations. They play critical roles in shaping sustainable cybersecurity in health care systems. These drivers include policy, leadership, communications and transparency, cultural sensitivity, and collaborators.</p>
          <p>In this conceptual framework, CKMIR plays a significant role in automated defense regarding vulnerabilities and intelligent response in the event of a cyber threat or attack.</p>
          <p>The framework provides a contemporary foundation and pathway for identifying and preventing vulnerabilities and responding to cyberattacks and threats in health care systems. This conceptual framework is important for identifying, capturing, organizing, storing, and sharing real-time data and actionable intelligence and preventing vulnerabilities to cyberattacks in health care systems. The conceptual framework functions holistically from a sociotechnical perspective of cybersecurity in health care systems. The proposed framework plays a critical role in system interplay for detecting, classifying, and preventing vulnerabilities and providing real-time incident response and automated report generation to ensure that the IT team is informed of the current security status, ongoing incidents, and actions taken.</p>
          <p>In <xref rid="figure3" ref-type="fig">Figure 3</xref>, an up-down bidirectional arrow indicates the relationship between CKMIR and health care systems. This up-down bidirectional relationship shows that CKMIR prevents vulnerabilities, provides real-time incident response, stores data, and remediates it in the event of threat intrusion and cyberattack, while the health care systems transmit data to CKMIR. Furthermore, opposing 2-way arrows show a relationship between CKMIR and the IT team. This 2-way relationship indicates that CKMIR transmits automated reports while the IT team accesses CKMIR to perform maintenance, remediation, and decision-making. In essence, this framework offers a comprehensive and well-defined approach to the sociotechnical underpinning and joint optimization of cybersecurity’s progress in achieving sustainable health care systems. The visual model of the proposed CKMIR system is shown in <xref rid="figure4" ref-type="fig">Figure 4</xref>.</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Visual model: proposed CKMIR system. CKMIR: cybersecurity knowledge management and intelligence response.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e75584_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Practical Implementation Steps for the Conceptual Framework</title>
        <p>The practical implementation steps for the validation of the proposed conceptual sociotechnical cybersecurity framework are shown in <xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref>. The implementation steps involve the classification of the vulnerability’s areas of occurrence (technology, humans, and processes), defining goals, mapping stakeholders, orientation, risk assessment, validation, and feedback. The guide indicates an interplay within the vulnerability’s areas of occurrence (technology, humans, and processes). It also shows that there is a joint optimization between the vulnerabilities’ areas of occurrence and the CKMIR system to identify and prevent vulnerabilities and respond to cyberattacks. The implementation of the proposed sociotechnical cybersecurity framework for health care systems (hospitals) in a real-world scenario is aimed at achieving optimal cybersecurity resilience.</p>
      </sec>
      <sec>
        <title>Linking the CKMIR System to the NIST Model</title>
        <p>The CKMIR elements align with the core functions of the NIST model in <xref rid="figure5" ref-type="fig">Figure 5</xref>. The core functions of the NIST model involve identifying, protecting, detecting, responding, and recovering [<xref ref-type="bibr" rid="ref124">124</xref>]. The CKMIR elements involve intrusion detection, vulnerability scanning, user behavior monitoring, alert sensors, threat intelligence, and cloud repository and recovery.</p>
        <p>The unique value proposition of the CKMIR model is the configuration, dynamic integration, and its mode of operation, such as real-time incident response optimization. Specifically, its unique value proposition is the provision of threat intelligence, human behavior analytics, and cross-component integration in the health care system. The CKMIR model applies to the health care system in its capacity to solve complex health care problems in the vulnerable areas of occurrence emanating from IoMT devices, cloud, EHRs, health care professionals, and patients. The model-specific sociotechnical contributions encompass the optimal identification and mitigation of vulnerabilities arising from technology, humans, and processes.</p>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>CKMIR element alignment with the NIST model. CKMIR: cybersecurity knowledge management and intelligence response; NIST: National Institute of Standards and Technology.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e75584_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Compliance Standards for Applying the Proposed Framework</title>
        <p>Compliance standards are necessary for the application of the conceptual sociotechnical cybersecurity framework to guide health care organizations in their cybersecurity practices. It will also facilitate the process of cybersecurity risk assessment for health care professionals. The compliance standard is detailed in <xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref> [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref61">61</xref>, <xref ref-type="bibr" rid="ref63">63</xref>,<xref ref-type="bibr" rid="ref70">70</xref>-<xref ref-type="bibr" rid="ref72">72</xref>,<xref ref-type="bibr" rid="ref75">75</xref>,<xref ref-type="bibr" rid="ref76">76</xref>,<xref ref-type="bibr" rid="ref80">80</xref>,<xref ref-type="bibr" rid="ref81">81</xref>,<xref ref-type="bibr" rid="ref87">87</xref>,<xref ref-type="bibr" rid="ref95">95</xref>,<xref ref-type="bibr" rid="ref99">99</xref>,<xref ref-type="bibr" rid="ref125">125</xref>].</p>
      </sec>
      <sec>
        <title>Practical Implications</title>
        <p>Considering the increase in cyberattacks, breaches, and overdependence on modern technology for health care diagnosis and treatment, it is important for health care organizations and stakeholders to examine how technology can be implemented. In particular, policies should mandate secure development for technology integration and third-party applications through adoption and control measures within health care system audit assessments and compliance procurement plans. Health care organizations should leverage the strength of cybersecurity through the implementation of risk assessment and incident response plans that complement current and emerging threats and cyberattacks. Health care organizations should adopt compliance standards for applying the sociotechnical framework as a guide to maintaining cybersecurity hygiene in health care systems (<xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref>). Health care institutions should ensure that the implementation of a medical device security lifecycle is integrated into Confidentiality, Integrity, and Availability practices as quality control measures [<xref ref-type="bibr" rid="ref21">21</xref>]. Health care organizations should implement network segregation of sensitive areas for greater protection, easy usability, and secure workarounds. Additionally, regular network assessment is required to monitor traffic and network behavior, and to trigger alerts regarding abnormalities [<xref ref-type="bibr" rid="ref50">50</xref>]. The design of network systems should be simplified and while training professionals to develop secure health care systems. Further, health care management should recruit more skilled professionals, offer training to employees, and increase budgeting for cybersecurity to ensure the delivery of uninterrupted health care services. Health care organizations must implement strong access control systems and policies that ensure the use of strong password systems, multifactor authentication, and strong privileges that grant access to health care critical infrastructure only to authorized employees.</p>
        <p>The adoption of the sociotechnical cybersecurity framework by health care organizations will accelerate and optimize cybersecurity progression and support IT teams and operational processes in sustaining the health care cyber space.</p>
      </sec>
      <sec>
        <title>Comparison With the Previous Literature</title>
        <p>The findings of the scoping review are in line with the existing evidence that obsolete infrastructure, limited budget, complex policies and procedures, ineffective training, and a shortage of cybersecurity experts are barriers to cybersecurity in health care systems [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref68">68</xref>,<xref ref-type="bibr" rid="ref72">72</xref>]. Additionally, Al-Qarni [<xref ref-type="bibr" rid="ref92">92</xref>] affirms our findings that health care organizations must have an evolving policy that aligns with emerging technological trends and cyber threats, along with a continuous upgrade and backup plan.</p>
        <p>Various schools of thought advocate addressing cybersecurity vulnerabilities in health care systems through a sociotechnical approach, rather than relying solely on technical or social perspectives. Invariably, studies support holistic and joint optimization approaches [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref126">126</xref>,<xref ref-type="bibr" rid="ref127">127</xref>].</p>
        <p>The concept of applying a sociotechnical perspective to cybersecurity in the health care domain has received little attention over the years, and the notion of a sociotechnical perspective on cybersecurity in health care is still evolving. Nevertheless, for cybersecurity in health care, a myriad of perspectives, such as a social perspective [<xref ref-type="bibr" rid="ref24">24</xref>], a cybersecurity perspective [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref20">20</xref>], a sociotechnical perspective [<xref ref-type="bibr" rid="ref12">12</xref>], the NIST perspective [<xref ref-type="bibr" rid="ref45">45</xref>], an organizational perspective [<xref ref-type="bibr" rid="ref104">104</xref>], and a knowledge management perspective [<xref ref-type="bibr" rid="ref5">5</xref>] have been applied. In this study, cybersecurity challenges and issues were addressed in health care organizations from an outstanding approach of the sociotechnical viewpoint by developing the sociotechnical cybersecurity framework; this is a novel instance of the theoretical contributions (<xref rid="figure3" ref-type="fig">Figure 3</xref>).</p>
        <p>In the quest for solutions, scholars have developed various frameworks that contribute to the theory of cybersecurity in health care. Rehman et al [<xref ref-type="bibr" rid="ref55">55</xref>] proposed a framework for a secure health monitoring system in health care 5.0 and used blockchain technology and an intrusion detection system to detect any malicious activity in health care networks. Wazid et al [<xref ref-type="bibr" rid="ref53">53</xref>] proposed a framework for generalized secure healthcare 5.0 to provide solutions for the challenges in health care systems. Furthermore, Jalali et al [<xref ref-type="bibr" rid="ref88">88</xref>] proposed the Eight Aggregated Response Strategies (EARSs) framework for cybersecurity incidents. In this context, the CKMIR model differs from the secure health monitoring model [<xref ref-type="bibr" rid="ref55">55</xref>] in the configuration of its elements. Further, the CKMIR model differs from the secure healthcare 5.0 model [<xref ref-type="bibr" rid="ref53">53</xref>] in its capability to respond to numerous simultaneous cyberattacks. Additionally, our proposed model optimized cybersecurity response capabilities compared to the EARS model [<xref ref-type="bibr" rid="ref88">88</xref>]. The incident reporting and vulnerability analysis are automated and embedded within our model, unlike in the EARS model. Generally, the CKMIR model differs from existing models in its components’ compatibility, design, and joint optimization of the technology, humans, and processes in preventing vulnerabilities and responding to cyberattacks.</p>
        <p>This study contributes to existing cybersecurity theory in several ways, taking an entirely different approach. One way is through the thematic classification of technology, human, and process-related factors of vulnerabilities to cyberattacks in health care systems in their descriptive format (<xref ref-type="table" rid="table2">Tables 2</xref>-<xref ref-type="table" rid="table4">4</xref>). It highlights the 3 constructs of sociotechnical-related factors of vulnerabilities to cyberattacks relative to their subfactors in health care systems. The second contribution is an in-depth analytical synthesis of the taxonomy factors of vulnerabilities to cyberattacks. It highlights such factors relative to their subfactors in health care systems (<xref ref-type="table" rid="table5">Table 5</xref>). The main contribution is the development of the conceptual sociotechnical cybersecurity framework for health care systems (<xref rid="figure3" ref-type="fig">Figure 3</xref>). The framework identifies and prevents vulnerabilities and responds to threats and cyberattacks. The proposed framework provides the foundation for understanding the connection and integration of the factors of vulnerabilities (technology, humans, and processes) to cyberattacks and threats from a sociotechnical perspective in health care systems. It presents a comprehensive approach that is important for fostering and supporting the current understanding of cybersecurity from a sociotechnical lens in health care systems.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>This study included only papers published in English. Gray literature was not examined. Reports, research-in-progress papers, editorial papers, and inaccessible papers were also excluded. Furthermore, papers outside the study’s context were excluded. Cybersecurity in health care papers from a sociotechnical perspective were rarely available.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The sociotechnical perspective of cybersecurity is a critical prerequisite and foundation for resolving vulnerabilities and preventing cyberattacks, breaches, and threats in a complex health care system. This study used a scoping review to examine the dynamics of the factors of vulnerabilities to cyberattacks and develop the sociotechnical cybersecurity framework for preventing vulnerabilities and responding to threats and cyberattacks in health care systems. Furthermore, this study also presents the compliance standards for the application of the conceptual framework to guide health care organizations’ cybersecurity practices. This study examined the landscape of cybersecurity vulnerabilities and confirmed that an interplay exists among the 3 sociotechnical themes of technology, humans, and processes.</p>
        <p>Despite the growing benefits of technology, this study observed that the increasing number of breaches and cyberattacks is linked to the unpreparedness of health care organizations, a lack of compliance, communication issues, irregular adverse assessments, and a lack of timely response to cybersecurity incidents and proper monitoring. It should be noted that online and offline backup and recovery plans are important for mitigating incidents. Health care organizations that embed a culture of inclusiveness and training with the necessary skills can eliminate insider threats and cyberattacks in health care systems. To address the vulnerabilities related to complexities in system design, health care organizations must ensure that priority is given to cybersecurity and user-centered designs for processes and the technological integration, application, and implementation of critical health care infrastructure as a sociotechnical approach [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref54">54</xref>]. This includes implementing security design and multifactor authentication instructions, secure text display, cryptographic instructions, tokenization, and alert triggers to providers and legitimate users to control system security operations. This implementation can affect usability and complex design from the patients’ and providers’ points of view to track intrusions, detect abnormalities, and prevent unlawful access to health information.</p>
        <p>The proposed conceptual sociotechnical cybersecurity framework provides a comprehensive and explicit overview of the sociotechnical foundations of vulnerabilities (technology, human factors, and processes) in health care systems.</p>
        <p>In spite of the existing generic cybersecurity frameworks from a sociotechnical perspective to tackle issues of vulnerabilities and cyberattacks in organizations, the framework is important for its suitability, applicability, and customization to a dynamic and complex health care system.</p>
        <p>In addition to further research to empirically validate the proposed framework for accuracy, feasibility, and effectiveness in health care organizations, there is also a need to investigate the adoption of blockchain technology for accelerating incident response processes in health care systems.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>PRISMA-ScR checklist.</p>
        <media xlink:href="jmir_v27i1e75584_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 101 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Detailed search strategy.</p>
        <media xlink:href="jmir_v27i1e75584_app2.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Characteristics of the included studies.</p>
        <media xlink:href="jmir_v27i1e75584_app3.docx" xlink:title="DOCX File , 51 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Critical appraisal.</p>
        <media xlink:href="jmir_v27i1e75584_app4.docx" xlink:title="DOCX File , 35 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Quality appraisal grouped by study method.</p>
        <media xlink:href="jmir_v27i1e75584_app5.docx" xlink:title="DOCX File , 17 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Practical implementation steps for the conceptual framework.</p>
        <media xlink:href="jmir_v27i1e75584_app6.docx" xlink:title="DOCX File , 165 KB"/>
      </supplementary-material>
      <supplementary-material id="app7">
        <label>Multimedia Appendix 7</label>
        <p>The compliance standards to guide the conceptual framework.</p>
        <media xlink:href="jmir_v27i1e75584_app7.docx" xlink:title="DOCX File , 19 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CKMIR</term>
          <def>
            <p>cybersecurity knowledge management and intelligence response</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">EARS</term>
          <def>
            <p>Eight Aggregated Response Strategy</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">IoMT</term>
          <def>
            <p>Internet of Medical Things</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">JBI</term>
          <def>
            <p>Joanna Briggs Institute</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">NIST</term>
          <def>
            <p>National Institute of Standards and Technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">PRISMA-ScR</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for Scoping Reviews</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">RQ</term>
          <def>
            <p>research question</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">STAMP</term>
          <def>
            <p>systems theoretic accident model and processes</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">STS</term>
          <def>
            <p>sociotechnical system</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The author is grateful to the Finnish Cultural Foundation for its support in funding this research.</p>
    </ack>
    <fn-group>
      <fn fn-type="con">
        <p>PE was responsible for this study’s design, quality appraisal, screening, data extraction, synthesis of results, and paper preparation. TV contributed by providing inputs and advice on protocols, data extraction, and eligibility criteria, as well as screening papers, abstracts, and full texts. Additionally, TV played a significant role in shaping this paper by offering critical feedback on the draft for continuous improvement. TM provided guidance, data collection, and comments on the revised paper.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kioskli</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Fotis</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Mouratidis</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>The landscape of cybersecurity vulnerabilities and challenges in healthcare: security standards and paradigm shift recommendations</article-title>
          <year>2021</year>
          <conf-name>ARES '21: Proceedings of the 16th International Conference on Availability, Reliability and Security</conf-name>
          <conf-date>August 17-20, 2021</conf-date>
          <conf-loc>Vienna, Austria</conf-loc>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1145/3465481.3470033</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Slayton</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Governing uncertainty or uncertain governance? Information security and the challenge of cutting ties</article-title>
          <source>Sci, Tech, Hum Values</source>
          <year>2020</year>
          <volume>46</volume>
          <issue>1</issue>
          <fpage>81</fpage>
          <lpage>111</lpage>
          <pub-id pub-id-type="doi">10.1177/0162243919901159</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wurm</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jin</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Heffner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rahman</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Tehranipoor</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Introduction to cyber-physical system security: a cross-layer perspective</article-title>
          <source>IEEE Trans Multi-Scale Comput Syst</source>
          <year>2017</year>
          <volume>3</volume>
          <issue>3</issue>
          <fpage>215</fpage>
          <lpage>227</lpage>
          <pub-id pub-id-type="doi">10.1109/tmscs.2016.2569446</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dias</surname>
              <given-names>FM</given-names>
            </name>
            <name name-style="western">
              <surname>Martens</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Monken</surname>
              <given-names>SFDP</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>LFD</given-names>
            </name>
            <name name-style="western">
              <surname>Santibanez-Gonzalez</surname>
              <given-names>EDR</given-names>
            </name>
          </person-group>
          <article-title>Risk management focusing on the best practices of data security systems for healthcare</article-title>
          <source>Int J Innovation</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>45</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.5585/iji.v9i1.18246</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A sociotechnical systems analysis of knowledge management for cybersecurity</article-title>
          <source>Int J Sociotechnol Knowl Dev</source>
          <year>2021</year>
          <volume>13</volume>
          <issue>3</issue>
          <fpage>77</fpage>
          <lpage>94</lpage>
          <pub-id pub-id-type="doi">10.4018/ijskd.2021070105</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaberuka</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Case studies in the socio-technical analysis of cybersecurity incidents: comparing attacks on the UK NHS and irish healthcare systems</article-title>
          <year>2022</year>
          <conf-name>Proceedings of the International Conference on Cybersecurity, Situational Awareness and Social Media</conf-name>
          <conf-date>June 20–21, 2022</conf-date>
          <conf-loc>Wales</conf-loc>
          <fpage>357</fpage>
          <lpage>387</lpage>
          <pub-id pub-id-type="doi">10.1007/978-981-19-6414-5_21</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kaberuka</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Adapting STPA-sec for socio-technical cyber security challenges in emerging nations: a case study in risk management for Rwandan health care</article-title>
          <year>2020</year>
          <conf-name>International Conference on Cyber Security and Protection of Digital Services (Cyber Security)</conf-name>
          <conf-date>2020 June 15-19</conf-date>
          <conf-loc>Dublin, Ireland</conf-loc>
          <pub-id pub-id-type="doi">10.1109/cybersecurity49315.2020.9138863</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kissel</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Glossary of key information security terms glossary of key information security terms</article-title>
          <source>The National Institute of Standards and Technology</source>
          <year>2013</year>
          <access-date>2025-09-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://nvlpubs.nist.gov/nistpubs/ir/2013/nist.ir.7298r2.pdf">https://nvlpubs.nist.gov/nistpubs/ir/2013/nist.ir.7298r2.pdf</ext-link>
          </comment>
        </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>Zhan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmad</surname>
              <given-names>SF</given-names>
            </name>
            <name name-style="western">
              <surname>Irshad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Razgan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Awwad</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Ali</surname>
              <given-names>YA</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmad Ayassrah</surname>
              <given-names>AYB</given-names>
            </name>
          </person-group>
          <article-title>Investigating the role of cybersecurity's perceived threats in the adoption of health information systems</article-title>
          <source>Heliyon</source>
          <year>2024</year>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>e22947</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2405-8440(23)10155-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.heliyon.2023.e22947</pub-id>
          <pub-id pub-id-type="medline">38148811</pub-id>
          <pub-id pub-id-type="pii">S2405-8440(23)10155-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC10750060</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Anastasopoulou</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mari</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Magkanaraki</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Spanakis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Merialdo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sakkalis</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Public and private healthcare organisations: a socio-technical model for identifying cybersecurity aspects</article-title>
          <year>2020</year>
          <conf-name>ICEGOV '20: Proceedings of the 13th International Conference on Theory and Practice of Electronic Governance</conf-name>
          <conf-date>September 23-25, 2020</conf-date>
          <conf-loc>Athens, Greece</conf-loc>
          <fpage>168</fpage>
          <lpage>175</lpage>
          <pub-id pub-id-type="doi">10.1145/3428502.3428525</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>Offner</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Sitnikova</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Joiner</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>MacIntyre</surname>
              <given-names>CR</given-names>
            </name>
          </person-group>
          <article-title>Towards understanding cybersecurity capability in Australian healthcare organisations: a systematic review of recent trends, threats and mitigation</article-title>
          <source>Intell Natl Security</source>
          <year>2020</year>
          <volume>35</volume>
          <issue>4</issue>
          <fpage>556</fpage>
          <lpage>585</lpage>
          <pub-id pub-id-type="doi">10.1080/02684527.2020.1752459</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>Sittig</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Singh</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>A socio-technical approach to preventing, mitigating, and recovering from ransomware attacks</article-title>
          <source>Appl Clin Inform</source>
          <year>2016</year>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>624</fpage>
          <lpage>632</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/27437066"/>
          </comment>
          <pub-id pub-id-type="doi">10.4338/ACI-2016-04-SOA-0064</pub-id>
          <pub-id pub-id-type="medline">27437066</pub-id>
          <pub-id pub-id-type="pmcid">PMC4941865</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bennouri</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Keane</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <conf-name>13th Mediterranean Conference on Embedded Computing (MECO)</conf-name>
          <conf-date>June 11-14, 2024</conf-date>
          <conf-loc>Budva, Montenegro</conf-loc>
          <fpage>1</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1109/meco62516.2024.10577790</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <article-title>Health sector cybersecurity: 2021 retrospective and 2022 look ahead</article-title>
          <source>Health and Human Services</source>
          <access-date>2025-09-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hhs.gov/sites/default/files/2021-retrospective-and-2022-look-ahead-tlpwhite.pdf">https://www.hhs.gov/sites/default/files/2021-retrospective-and-2022-look-ahead-tlpwhite.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lasky</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>WannaCry ransomware worm attacks the world</article-title>
          <source>SecurityInfoWatch.com</source>
          <year>2017</year>
          <access-date>2025-09-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.securityinfowatch.com/cybersecurity/information-security/article/12334948/wannacry-ransomware-worm-attacks-the-world">https://www.securityinfowatch.com/cybersecurity/information-security/article/12334948/wannacry-ransomware-worm-attacks-the-world</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coventry</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Branley</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in healthcare: a narrative review of trends, threats and ways forward</article-title>
          <source>Maturitas</source>
          <year>2018</year>
          <volume>113</volume>
          <fpage>48</fpage>
          <lpage>52</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://core.ac.uk/reader/157854043?utm_source=linkout"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.maturitas.2018.04.008</pub-id>
          <pub-id pub-id-type="medline">29903648</pub-id>
          <pub-id pub-id-type="pii">S0378-5122(18)30165-8</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>Malatji</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Von Solms</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marnewick</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Socio-technical systems cybersecurity framework</article-title>
          <source>ICS</source>
          <year>2019</year>
          <volume>27</volume>
          <issue>2</issue>
          <fpage>233</fpage>
          <lpage>272</lpage>
          <pub-id pub-id-type="doi">10.1108/ics-03-2018-0031</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>Argaw</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Bempong</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Eshaya-Chauvin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Flahault</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The state of research on cyberattacks against hospitals and available best practice recommendations: a scoping review</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2019</year>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>10</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-018-0724-5"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-018-0724-5</pub-id>
          <pub-id pub-id-type="medline">30634962</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-018-0724-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC6330387</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>Argaw</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Troncoso-Pastoriza</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Lacey</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Florin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Calcavecchia</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Burleson</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Vogel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>O'Leary</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Eshaya-Chauvin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Flahault</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity of hospitals: discussing the challenges and working towards mitigating the risks</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2020</year>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>146</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-020-01161-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-020-01161-7</pub-id>
          <pub-id pub-id-type="medline">32620167</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-020-01161-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC7333281</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>Garcia-Perez</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cegarra-Navarro</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Sallos</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Martinez-Caro</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Chinnaswamy</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Resilience in healthcare systems: cyber security and digital transformation</article-title>
          <source>Technovation</source>
          <year>2023</year>
          <volume>121</volume>
          <fpage>102583</fpage>
          <pub-id pub-id-type="doi">10.1016/j.technovation.2022.102583</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>Szczepaniuk</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Szczepaniuk</surname>
              <given-names>EK</given-names>
            </name>
          </person-group>
          <article-title>Cryptographic evidence-based cybersecurity for smart healthcare systems</article-title>
          <source>Inf Sci</source>
          <year>2023</year>
          <volume>649</volume>
          <fpage>119633</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ins.2023.119633</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>Vukotich</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Healthcare and cybersecurity: taking a zero trust approach</article-title>
          <source>Health Serv Insights</source>
          <year>2023</year>
          <volume>16</volume>
          <fpage>11786329231187826</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/11786329231187826?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/11786329231187826</pub-id>
          <pub-id pub-id-type="medline">37485022</pub-id>
          <pub-id pub-id-type="pii">10.1177_11786329231187826</pub-id>
          <pub-id pub-id-type="pmcid">PMC10359660</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>Zimmermann</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Renaud</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Moving from a ‘human-as-problem” to a ‘human-as-solution” cybersecurity mindset</article-title>
          <source>Int J Hum-Comput Stud</source>
          <year>2019</year>
          <volume>131</volume>
          <fpage>169</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijhcs.2019.05.005</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nicho</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>McDermott</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Dimensions of ‘Socio’ vulnerabilities of advanced persistent threats</article-title>
          <year>2019</year>
          <conf-name>International Conference on Software, Telecommunications and Computer Networks (SoftCOM)</conf-name>
          <conf-date>September 19-21, 2019</conf-date>
          <conf-loc>Split, Croatia</conf-loc>
          <publisher-name>IEEE</publisher-name>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.23919/softcom.2019.8903788</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>Malatji</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Marnewick</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>von Solms</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Validation of a socio-technical management process for optimising cybersecurity practices</article-title>
          <source>Comput Secur</source>
          <year>2020</year>
          <volume>95</volume>
          <fpage>101846</fpage>
          <pub-id pub-id-type="doi">10.1016/j.cose.2020.101846</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>Svandova</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Smutny</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Internet of medical things security frameworks for risk assessment and management: a scoping review</article-title>
          <source>J Multidiscip Healthc</source>
          <year>2024</year>
          <volume>17</volume>
          <fpage>2281</fpage>
          <lpage>2301</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.2147/JMDH.S459987?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.2147/JMDH.S459987</pub-id>
          <pub-id pub-id-type="medline">38765613</pub-id>
          <pub-id pub-id-type="pii">459987</pub-id>
          <pub-id pub-id-type="pmcid">PMC11102065</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>Ewoh</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Vartiainen</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Vulnerability to cyberattacks and sociotechnical solutions for health care systems: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e46904</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e46904/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/46904</pub-id>
          <pub-id pub-id-type="medline">38820579</pub-id>
          <pub-id pub-id-type="pii">v26i1e46904</pub-id>
          <pub-id pub-id-type="pmcid">PMC11179043</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>Wani</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Mendoza</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A sociotechnical approach to bring-your-own-device security in hospitals: development and pilot testing of a maturity model using mixed methods action research</article-title>
          <source>JMIR Hum Factors</source>
          <year>2025</year>
          <volume>12</volume>
          <fpage>e71912</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2025//e71912/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/71912</pub-id>
          <pub-id pub-id-type="medline">40802372</pub-id>
          <pub-id pub-id-type="pii">v12i1e71912</pub-id>
          <pub-id pub-id-type="pmcid">PMC12391842</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>Sutton</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tompson</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Towards a cybersecurity culture-behaviour framework: a rapid evidence review</article-title>
          <source>Comput Secur</source>
          <year>2025</year>
          <volume>148</volume>
          <fpage>104110</fpage>
          <pub-id pub-id-type="doi">10.1016/j.cose.2024.104110</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>Mozzaquatro</surname>
              <given-names>BA</given-names>
            </name>
            <name name-style="western">
              <surname>Agostinho</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Goncalves</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Martins</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jardim-Goncalves</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>An ontology-based cybersecurity framework for the internet of things</article-title>
          <source>Sensors (Basel)</source>
          <year>2018</year>
          <volume>18</volume>
          <issue>9</issue>
          <fpage>3053</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s18093053"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s18093053</pub-id>
          <pub-id pub-id-type="medline">30213085</pub-id>
          <pub-id pub-id-type="pii">s18093053</pub-id>
          <pub-id pub-id-type="pmcid">PMC6163186</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mtsweni</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gcaza</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Thaba</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A unified cybersecurity framework for complex environments</article-title>
          <year>2018</year>
          <conf-name>SAICSIT '18: Proceedings of the Annual Conference of the South African Institute of Computer Scientists and Information Technologists</conf-name>
          <conf-date>September 26-28, 2018</conf-date>
          <conf-loc>Port Elizabeth South Africa</conf-loc>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1145/3278681.3278682</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>Davis</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Challenger</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jayewardene</surname>
              <given-names>DN</given-names>
            </name>
            <name name-style="western">
              <surname>Clegg</surname>
              <given-names>CW</given-names>
            </name>
          </person-group>
          <article-title>Advancing socio-technical systems thinking: a call for bravery</article-title>
          <source>Appl Ergon</source>
          <year>2014</year>
          <volume>45</volume>
          <issue>2, Part A</issue>
          <fpage>171</fpage>
          <lpage>180</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eprints.whiterose.ac.uk/83439/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.apergo.2013.02.009</pub-id>
          <pub-id pub-id-type="medline">23664481</pub-id>
          <pub-id pub-id-type="pii">S0003-6870(13)00032-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Trist</surname>
              <given-names>EL</given-names>
            </name>
          </person-group>
          <source>Towards A Social Ecology: Contextual Appreciation of the Future in the Present</source>
          <year>1973</year>
          <publisher-loc>London; New York</publisher-loc>
          <publisher-name>Plenum Press</publisher-name>
        </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>Appelbaum</surname>
              <given-names>SH</given-names>
            </name>
          </person-group>
          <article-title>Socio‐technical systems theory: an intervention strategy for organizational development</article-title>
          <source>Manage Decis</source>
          <year>1997</year>
          <volume>35</volume>
          <issue>6</issue>
          <fpage>452</fpage>
          <lpage>463</lpage>
          <pub-id pub-id-type="doi">10.1108/00251749710173823</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>Mumford</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The story of socio‐technical design: reflections on its successes, failures and potential</article-title>
          <source>Inf Syst J</source>
          <year>2006</year>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>317</fpage>
          <lpage>342</lpage>
          <pub-id pub-id-type="doi">10.1111/j.1365-2575.2006.00221.x</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>Emery</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Sociotechnical foundations for a new social order?</article-title>
          <source>Hum Relat</source>
          <year>1982</year>
          <volume>35</volume>
          <issue>12</issue>
          <fpage>1095</fpage>
          <lpage>1122</lpage>
          <pub-id pub-id-type="doi">10.1177/001872678203501203</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Trist</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The evolution of socio-technical systems</article-title>
          <source>Conf Organ Des Perform</source>
          <year>1981</year>
          <access-date>2025-09-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://sistemas-humano-computacionais.wdfiles.com/local--files/capitulo%3Aredes-socio-tecnicas/Evolution_of_socio_technical_systems.pdf">https://sistemas-humano-computacionais.wdfiles.com/local--files/capitulo%3Aredes-socio-tecnicas/Evolution_of_socio_technical_systems.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baxter</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sommerville</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Socio-technical systems: from design methods to systems engineering</article-title>
          <source>Interact Comput</source>
          <year>2011</year>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>4</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.1016/j.intcom.2010.07.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arksey</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>O'Malley</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Scoping studies: towards a methodological framework</article-title>
          <source>Int J Soc Res Methodol</source>
          <year>2005</year>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>19</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1080/1364557032000119616</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Lillie</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Zarin</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Colquhoun</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Levac</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Horsley</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Weeks</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hempel</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McGowan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hartling</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Aldcroft</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>MG</given-names>
            </name>
            <name name-style="western">
              <surname>Garritty</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lewin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Macdonald</surname>
              <given-names>MT</given-names>
            </name>
            <name name-style="western">
              <surname>Langlois</surname>
              <given-names>EV</given-names>
            </name>
            <name name-style="western">
              <surname>Soares-Weiser</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Moriarty</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Clifford</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Tunçalp</surname>
              <given-names>Ö</given-names>
            </name>
            <name name-style="western">
              <surname>Straus</surname>
              <given-names>SE</given-names>
            </name>
          </person-group>
          <article-title>PRISMA Extension for Scoping Reviews (PRISMA-ScR): checklist and explanation</article-title>
          <source>Ann Intern Med</source>
          <year>2018</year>
          <volume>169</volume>
          <issue>7</issue>
          <fpage>467</fpage>
          <lpage>473</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/10.7326/M18-0850?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M18-0850</pub-id>
          <pub-id pub-id-type="medline">30178033</pub-id>
          <pub-id pub-id-type="pii">2700389</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>Tully</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Selzer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Phillips</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>O'Connor</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Dameff</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Healthcare challenges in the era of cybersecurity</article-title>
          <source>Health Secur</source>
          <year>2020</year>
          <volume>18</volume>
          <issue>3</issue>
          <fpage>228</fpage>
          <lpage>231</lpage>
          <pub-id pub-id-type="doi">10.1089/hs.2019.0123</pub-id>
          <pub-id pub-id-type="medline">32559153</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>Arafa</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sheerah</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Alsalamah</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Emerging digital technologies in healthcare with a spotlight on cybersecurity: a narrative review</article-title>
          <source>information</source>
          <year>2023</year>
          <volume>14</volume>
          <issue>12</issue>
          <fpage>640</fpage>
          <pub-id pub-id-type="doi">10.3390/info14120640</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>He</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Aliyu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Health care cybersecurity challenges and solutions under the climate of COVID-19: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>e21747</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/4/e21747/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21747</pub-id>
          <pub-id pub-id-type="medline">33764885</pub-id>
          <pub-id pub-id-type="pii">v23i4e21747</pub-id>
          <pub-id pub-id-type="pmcid">PMC8059789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alhammad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Yusof</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Jambari</surname>
              <given-names>DI</given-names>
            </name>
          </person-group>
          <article-title>A review of cyber threats to medical devices integration with electronic medical records</article-title>
          <year>2022</year>
          <conf-name>International Conference on Cyber Resilience (ICCR)</conf-name>
          <conf-date>October 06-07, 2022</conf-date>
          <conf-loc>Dubai, United Arab Emirates</conf-loc>
          <pub-id pub-id-type="doi">10.1109/iccr56254.2022.9995984</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kandasamy</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Srinivas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Achuthan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rangan</surname>
              <given-names>VP</given-names>
            </name>
          </person-group>
          <article-title>Digital healthcare - cyberattacks in Asian organizations: an analysis of vulnerabilities, risks, NIST perspectives, and recommendations</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <volume>10</volume>
          <fpage>12345</fpage>
          <lpage>12364</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3145372</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kruse</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Frederick</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jacobson</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Monticone</surname>
              <given-names>DK</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in healthcare: a systematic review of modern threats and trends</article-title>
          <source>Technol Health Care</source>
          <year>2017</year>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.3233/THC-161263?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.3233/THC-161263</pub-id>
          <pub-id pub-id-type="medline">27689562</pub-id>
          <pub-id pub-id-type="pii">THC1263</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pool</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Akhlaghpour</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fatehi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Burton-Jones</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A systematic analysis of failures in protecting personal health data: a scoping review</article-title>
          <source>Int J Inf Manage</source>
          <year>2024</year>
          <volume>74</volume>
          <fpage>102719</fpage>
          <pub-id pub-id-type="doi">10.1016/j.ijinfomgt.2023.102719</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cartwright</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>The elephant in the room: cybersecurity in healthcare</article-title>
          <source>J Clin Monit Comput</source>
          <year>2023</year>
          <volume>37</volume>
          <issue>5</issue>
          <fpage>1123</fpage>
          <lpage>1132</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37088852"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10877-023-01013-5</pub-id>
          <pub-id pub-id-type="medline">37088852</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10877-023-01013-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC10123010</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Calyam</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kejriwal</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Rao</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Bai</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Towards a domain-agnostic knowledge graph-as-a-service infrastructure for active cyber defense with intelligent agents</article-title>
          <year>2023</year>
          <conf-name>IEEE Applied Imagery Pattern Recognition Workshop (AIPR)</conf-name>
          <conf-date>September 27-29, 2023</conf-date>
          <conf-loc>St. Louis, MO</conf-loc>
          <pub-id pub-id-type="doi">10.1109/aipr60534.2023.10440708</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Messinis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Temenos</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Protonotarios</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Rallis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Kalogeras</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Doulamis</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Enhancing internet of medical things security with artificial intelligence: a comprehensive review</article-title>
          <source>Comput Biol Med</source>
          <year>2024</year>
          <volume>170</volume>
          <fpage>108036</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0010-4825(24)00120-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2024.108036</pub-id>
          <pub-id pub-id-type="medline">38295478</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(24)00120-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lopatina</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Dokuchaev</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Maklachkova</surname>
              <given-names>VV</given-names>
            </name>
          </person-group>
          <article-title>Data risks identification in healthcare sensor networks</article-title>
          <year>2021</year>
          <conf-name>International Conference on Engineering Management of Communication and Technology (EMCTECH)</conf-name>
          <conf-date>October 20-22, 2021</conf-date>
          <conf-loc>Vienna, Austria</conf-loc>
          <pub-id pub-id-type="doi">10.1109/emctech53459.2021.9619178</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>Filipec</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Plášil</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The cybersecurity of healthcare the case of the Benešov hospital hit by Ryuk ransomware, and lessons learned</article-title>
          <source>OaS</source>
          <year>2021</year>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>27</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.3849/1802-7199.21.2021.01.027-052</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>Wazid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Das</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Mohd</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Healthcare 5.0 security framework: applications, issues and future research directions</article-title>
          <source>IEEE Access</source>
          <year>2022</year>
          <volume>10</volume>
          <fpage>129429</fpage>
          <lpage>129442</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2022.3228505</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>Ogunniye</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hana</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Watson</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>PETRAS: a socio-technical framework for internet of things research and development</article-title>
          <source>Front Internet Things</source>
          <year>2024</year>
          <volume>3</volume>
          <fpage>1336564</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.frontiersin.org/journals/the-internet-of-things/articles/10.3389/friot.2024.1336564"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/friot.2024.1336564</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>Rehman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Abbas</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ghazal</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Adnan</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mosavi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A secure healthcare 5.0 system based on blockchain technology entangled with federated learning technique</article-title>
          <source>Comput Biol Med</source>
          <year>2022</year>
          <volume>150</volume>
          <fpage>106019</fpage>
          <pub-id pub-id-type="doi">10.31219/osf.io/gvkqc</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Semancik</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wells</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Techniques to maximize O-level cyber security protection</article-title>
          <year>2023</year>
          <conf-name>IEEE AUTOTESTCON</conf-name>
          <conf-date>August 28-31, 2023</conf-date>
          <conf-loc>National Harbor, MD</conf-loc>
          <pub-id pub-id-type="doi">10.1109/autotestcon47464.2023.10296266</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>Giansanti</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity and the digital-health: the challenge of this millennium</article-title>
          <source>Healthcare (Basel)</source>
          <year>2021</year>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>62</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare9010062"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare9010062</pub-id>
          <pub-id pub-id-type="medline">33440612</pub-id>
          <pub-id pub-id-type="pii">healthcare9010062</pub-id>
          <pub-id pub-id-type="pmcid">PMC7827661</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>Lee</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Analyzing web descriptions of cybersecurity breaches in the healthcare provider sector: a content analytics research method</article-title>
          <source>Comput Secur</source>
          <year>2023</year>
          <volume>129</volume>
          <fpage>103185</fpage>
          <pub-id pub-id-type="doi">10.1016/j.cose.2023.103185</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>Arora</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yttri</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nilse</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Privacy and security in mobile health (mHealth) research</article-title>
          <source>Alcohol Res</source>
          <year>2014</year>
          <volume>36</volume>
          <issue>1</issue>
          <fpage>143</fpage>
          <lpage>152</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26259009"/>
          </comment>
          <pub-id pub-id-type="medline">26259009</pub-id>
          <pub-id pub-id-type="pmcid">PMC4432854</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>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Huo</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>A dynamic identity based authentication scheme using chaotic maps for telecare medicine information systems</article-title>
          <source>J Med Syst</source>
          <year>2015</year>
          <volume>39</volume>
          <issue>1</issue>
          <fpage>158</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-014-0158-2</pub-id>
          <pub-id pub-id-type="medline">25486894</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>Abraham</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sims</surname>
              <given-names>RR</given-names>
            </name>
          </person-group>
          <article-title>Muddling through cybersecurity: insights from the U.S. healthcare industry</article-title>
          <source>Bus Horiz</source>
          <year>2019</year>
          <volume>62</volume>
          <issue>4</issue>
          <fpage>539</fpage>
          <lpage>548</lpage>
          <pub-id pub-id-type="doi">10.1016/j.bushor.2019.03.010</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>Wasserman</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wasserman</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Hospital cybersecurity risks and gaps review for the non-cyber professional</article-title>
          <source>Front Digit Health</source>
          <year>2022</year>
          <volume>4</volume>
          <fpage>862221</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.frontiersin.org/articles/10.3389/fdgth.2022.862221/full"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2022.862221</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Janith</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Iddagoda</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gunawardena</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sankalpa</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Abeywardena</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Yapa</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>SentinelPlus: a cost-effective cyber security solution for healthcare organizations</article-title>
          <year>2021</year>
          <conf-name>ICAC 2021 - 3rd International Conference on Advancements in Computing, Proceedings</conf-name>
          <conf-date>December 09-11, 2021</conf-date>
          <conf-loc>Colombo, Sri Lanka</conf-loc>
          <publisher-loc>In</publisher-loc>
          <fpage>359</fpage>
          <lpage>364</lpage>
          <pub-id pub-id-type="doi">10.1109/icac54203.2021.9670892</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>Dameff</surname>
              <given-names>CJ</given-names>
            </name>
            <name name-style="western">
              <surname>Selzer</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Fisher</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Killeen</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Tully</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Clinical cybersecurity training through novel high-fidelity simulations</article-title>
          <source>J Emerg Med</source>
          <year>2019</year>
          <volume>56</volume>
          <issue>2</issue>
          <fpage>233</fpage>
          <lpage>238</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jemermed.2018.10.029</pub-id>
          <pub-id pub-id-type="medline">30553562</pub-id>
          <pub-id pub-id-type="pii">S0736-4679(18)31055-2</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>Feeley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Crowley</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Feeley</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Roopnarinesingh</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Geraghty</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cosgrave</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sheehan</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Merghani</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Under viral attack: an orthopaedic response to challenges faced by regional referral centres during a national cyber-attack</article-title>
          <source>Surgeon</source>
          <year>2022</year>
          <volume>20</volume>
          <issue>5</issue>
          <fpage>334</fpage>
          <lpage>338</lpage>
          <pub-id pub-id-type="doi">10.1016/j.surge.2021.09.007</pub-id>
          <pub-id pub-id-type="medline">34782238</pub-id>
          <pub-id pub-id-type="pii">S1479-666X(21)00164-5</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>Beaman</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Barkworth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Akande</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Hakak</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>MK</given-names>
            </name>
          </person-group>
          <article-title>Ransomware: recent advances, analysis, challenges and future research directions</article-title>
          <source>Comput Secur</source>
          <year>2021</year>
          <volume>111</volume>
          <fpage>102490</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34602684"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cose.2021.102490</pub-id>
          <pub-id pub-id-type="medline">34602684</pub-id>
          <pub-id pub-id-type="pii">S0167-4048(21)00314-X</pub-id>
          <pub-id pub-id-type="pmcid">PMC8463105</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>Hijji</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Alam</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>A multivocal literature review on growing social engineering based cyber-attacks/threats during the COVID-19 pandemic: challenges and prospective solutions</article-title>
          <source>IEEE Access</source>
          <year>2021</year>
          <volume>9</volume>
          <fpage>7152</fpage>
          <lpage>7169</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34786300"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/ACCESS.2020.3048839</pub-id>
          <pub-id pub-id-type="medline">34786300</pub-id>
          <pub-id pub-id-type="pmcid">PMC8545234</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>Fernando</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dawson</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The natural hospital environment: a socio-technical-material perspective</article-title>
          <source>Int J Med Inform</source>
          <year>2014</year>
          <volume>83</volume>
          <issue>2</issue>
          <fpage>140</fpage>
          <lpage>158</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2013.10.008</pub-id>
          <pub-id pub-id-type="medline">24286731</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(13)00226-8</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>Pranggono</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Arabo</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 pandemic cybersecurity issues</article-title>
          <source>Internet Technol Lett</source>
          <year>2021</year>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e247</fpage>
          <pub-id pub-id-type="doi">10.1002/itl2.247</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>Wilner</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Luce</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ouellet</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Costa</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>From public health to cyber hygiene: cybersecurity and Canada’s healthcare sector</article-title>
          <source>Int J</source>
          <year>2022</year>
          <volume>76</volume>
          <issue>4</issue>
          <fpage>522</fpage>
          <lpage>543</lpage>
          <pub-id pub-id-type="doi">10.1177/00207020211067946</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>DeFord</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Sustainable digital health demands cybersecurity transformation</article-title>
          <source>Front Health Serv Manage</source>
          <year>2022</year>
          <volume>38</volume>
          <issue>3</issue>
          <fpage>31</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1097/HAP.0000000000000137</pub-id>
          <pub-id pub-id-type="medline">35191859</pub-id>
          <pub-id pub-id-type="pii">01974520-202203000-00006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hines</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Trivedi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hoang-Tran</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mocharnuk</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pfaff</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Perspectives on cybersecurity and plastic surgery: a survey of plastic surgeons and scoping review of the literature</article-title>
          <source>Aesthet Surg J</source>
          <year>2023</year>
          <volume>43</volume>
          <issue>11</issue>
          <fpage>1376</fpage>
          <lpage>1383</lpage>
          <pub-id pub-id-type="doi">10.1093/asj/sjad122</pub-id>
          <pub-id pub-id-type="medline">37186025</pub-id>
          <pub-id pub-id-type="pii">7142817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wright</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Glynn</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kadakia</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mazzone</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Leinbach</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Landman</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of a mandatory phishing training program for high-risk employees at a US healthcare system</article-title>
          <source>J Am Med Inf Assoc</source>
          <year>2019</year>
          <volume>26</volume>
          <issue>6</issue>
          <fpage>547</fpage>
          <lpage>552</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30861069"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz005</pub-id>
          <pub-id pub-id-type="medline">30861069</pub-id>
          <pub-id pub-id-type="pii">5376646</pub-id>
          <pub-id pub-id-type="pmcid">PMC6515532</pub-id>
        </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>Ireland</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Ireland</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>NS</given-names>
            </name>
            <name name-style="western">
              <surname>Chu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Predicting security incidents in high secure male psychiatric care</article-title>
          <source>Int J Law Psychiatry</source>
          <year>2019</year>
          <volume>64</volume>
          <fpage>40</fpage>
          <lpage>52</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijlp.2019.01.004</pub-id>
          <pub-id pub-id-type="medline">31122639</pub-id>
          <pub-id pub-id-type="pii">S0160-2527(18)30252-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sekandi</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Murray</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Berryman</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Davis-Olwell</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hurst</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kakaire</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kiwanuka</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Whalen</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Mwaka</surname>
              <given-names>ES</given-names>
            </name>
          </person-group>
          <article-title>Ethical, legal, and sociocultural issues in the use of mobile technologies and call detail records data for public health in the East African region: scoping review</article-title>
          <source>Interact J Med Res</source>
          <year>2022</year>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>e35062</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.i-jmr.org/2022/1/e35062/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/35062</pub-id>
          <pub-id pub-id-type="medline">35533323</pub-id>
          <pub-id pub-id-type="pii">v11i1e35062</pub-id>
          <pub-id pub-id-type="pmcid">PMC9204580</pub-id>
        </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>Yeng</surname>
              <given-names>PK</given-names>
            </name>
            <name name-style="western">
              <surname>Szekeres</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Snekkenes</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>Mapping the psychosocialcultural aspects of healthcare professionals' information security practices: systematic mapping study</article-title>
          <source>JMIR Hum Factors</source>
          <year>2021</year>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>e17604</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2021/2/e17604/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17604</pub-id>
          <pub-id pub-id-type="medline">34106077</pub-id>
          <pub-id pub-id-type="pii">v8i2e17604</pub-id>
          <pub-id pub-id-type="pmcid">PMC8235336</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>Alfawzan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Christen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Spitale</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Biller-Andorno</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Privacy, data sharing, and data security policies of women's mHealth apps: scoping review and content analysis</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2022</year>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>e33735</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2022/5/e33735/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/33735</pub-id>
          <pub-id pub-id-type="medline">35522465</pub-id>
          <pub-id pub-id-type="pii">v10i5e33735</pub-id>
          <pub-id pub-id-type="pmcid">PMC9123546</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>Monteith</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bauer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Alda</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Geddes</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Whybrow</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Glenn</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Increasing cybercrime since the pandemic: concerns for psychiatry</article-title>
          <source>Curr Psychiatry Rep</source>
          <year>2021</year>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>18</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33660091"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11920-021-01228-w</pub-id>
          <pub-id pub-id-type="medline">33660091</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11920-021-01228-w</pub-id>
          <pub-id pub-id-type="pmcid">PMC7927777</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>Sari</surname>
              <given-names>PK</given-names>
            </name>
            <name name-style="western">
              <surname>Handayani</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Hidayanto</surname>
              <given-names>AN</given-names>
            </name>
            <name name-style="western">
              <surname>Yazid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aji</surname>
              <given-names>RF</given-names>
            </name>
          </person-group>
          <article-title>Information security behavior in health information systems: a review of research trends and antecedent factors</article-title>
          <source>Healthcare (Basel)</source>
          <year>2022</year>
          <volume>10</volume>
          <issue>12</issue>
          <fpage>2531</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=healthcare10122531"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/healthcare10122531</pub-id>
          <pub-id pub-id-type="medline">36554055</pub-id>
          <pub-id pub-id-type="pii">healthcare10122531</pub-id>
          <pub-id pub-id-type="pmcid">PMC9777837</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coventry</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Branley-Bell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sillence</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Magalini</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mari</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Magkanaraki</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Cyber-risk in healthcare: exploring facilitators and barriers to secure behavior</article-title>
          <source>Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)</source>
          <year>2020</year>
          <access-date>2025-09-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://scispace.com/pdf/cyber-risk-in-healthcare-exploring-facilitators-and-barriers-1kmegfd0ff.pdf">https://scispace.com/pdf/cyber-risk-in-healthcare-exploring-facilitators-and-barriers-1kmegfd0ff.pdf</ext-link>
          </comment>
        </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>Branley-Bell</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Coventry</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Sillence</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Magalini</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mari</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Magkanaraki</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Anastasopoulou</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Your hospital needs you: eliciting positive cybersecurity behaviours from healthcare staff</article-title>
          <source>Ann Disaster Risk Sci</source>
          <year>2020</year>
          <volume>3</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.51381/adrs.v3i1.51</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>Abbou</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kessel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Natan</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Gabbay-Benziv</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Dahan Shriki</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ophir</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Goldschmid</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Roguin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dudkiewicz</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>When all computers shut down: the clinical impact of a major cyber-attack on a general hospital</article-title>
          <source>Front Digit Health</source>
          <year>2024</year>
          <volume>6</volume>
          <fpage>1321485</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38433989"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fdgth.2024.1321485</pub-id>
          <pub-id pub-id-type="medline">38433989</pub-id>
          <pub-id pub-id-type="pmcid">PMC10904636</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>Harrison</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Kubli</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>DeGregorio</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Riggs</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Werner-Wasik</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dicker</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vinogradskiy</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>How to respond to a ransomware attack? One radiation oncology department's response to a cyber-attack on their record and verify system</article-title>
          <source>Pract Radiat Oncol</source>
          <year>2022</year>
          <volume>12</volume>
          <issue>2</issue>
          <fpage>170</fpage>
          <lpage>174</lpage>
          <pub-id pub-id-type="doi">10.1016/j.prro.2021.09.011</pub-id>
          <pub-id pub-id-type="medline">34644601</pub-id>
          <pub-id pub-id-type="pii">S1879-8500(21)00275-7</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>Mohammed</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Data breach recovery areas: an exploration of organization's recovery strategies for surviving data breaches</article-title>
          <source>OCJ</source>
          <year>2022</year>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>41</fpage>
          <lpage>59</lpage>
          <pub-id pub-id-type="doi">10.1108/ocj-05-2021-0014</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>Keogh</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Brady</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hassett</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Costelloe</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>O'Sullivan</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Twomey</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>O'Leary</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cahill</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>O'Riordan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Joyce</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Moloney</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Flavin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>M Bambury</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Murray</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Mullooly</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>O'Reilly</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Dealing with digital paralysis: surviving a cyberattack in a national cancer center</article-title>
          <source>J Cancer Policy</source>
          <year>2024</year>
          <volume>39</volume>
          <fpage>100466</fpage>
          <pub-id pub-id-type="doi">10.1016/j.jcpo.2023.100466</pub-id>
          <pub-id pub-id-type="medline">38176467</pub-id>
          <pub-id pub-id-type="pii">S2213-5383(23)00083-8</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>Bhuyan</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Kabir</surname>
              <given-names>UY</given-names>
            </name>
            <name name-style="western">
              <surname>Escareno</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Ector</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Palakodeti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Wyant</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Levy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kedia</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dasgupta</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dobalian</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Transforming healthcare cybersecurity from reactive to proactive: current status and future recommendations</article-title>
          <source>J Med Syst</source>
          <year>2020</year>
          <volume>44</volume>
          <issue>5</issue>
          <fpage>98</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-019-1507-y</pub-id>
          <pub-id pub-id-type="medline">32239357</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-019-1507-y</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>He</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Maglaras</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Aliyu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Healthcare security incident response strategy - a proactive incident response (IR) procedure</article-title>
          <source>Secur Commun Networks</source>
          <year>2022</year>
          <volume>2022</volume>
          <issue>1</issue>
          <fpage>2775249</fpage>
          <pub-id pub-id-type="doi">10.1155/2022/2775249</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>Jalali</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Razak</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>EARS to cyber incidents in health care</article-title>
          <source>J Am Med Inf Assoc</source>
          <year>2019</year>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>81</fpage>
          <lpage>90</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30517701"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy148</pub-id>
          <pub-id pub-id-type="medline">30517701</pub-id>
          <pub-id pub-id-type="pii">5229203</pub-id>
          <pub-id pub-id-type="pmcid">PMC7647158</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>Lohrke</surname>
              <given-names>FT</given-names>
            </name>
            <name name-style="western">
              <surname>Frownfelter-Lohrke</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity research from a management perspective: a systematic literature review and future research agenda</article-title>
          <source>J Gen Manage</source>
          <year>2023</year>
          <pub-id pub-id-type="doi">10.1177/03063070231200512</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>McEvoy</surname>
              <given-names>TR</given-names>
            </name>
            <name name-style="western">
              <surname>Kowalski</surname>
              <given-names>SJ</given-names>
            </name>
          </person-group>
          <article-title>Deriving cyber security risks from human and organizational factors – a socio-technical approach</article-title>
          <source>CSIMQ</source>
          <year>2019</year>
          <issue>18</issue>
          <fpage>47</fpage>
          <lpage>64</lpage>
          <pub-id pub-id-type="doi">10.7250/csimq.2019-18.03</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>Tin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hata</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Granholm</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ciottone</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Staynings</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ciottone</surname>
              <given-names>GR</given-names>
            </name>
          </person-group>
          <article-title>Cyberthreats: a primer for healthcare professionals</article-title>
          <source>Am J Emerg Med</source>
          <year>2023</year>
          <volume>68</volume>
          <fpage>179</fpage>
          <lpage>185</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ajem.2023.04.001</pub-id>
          <pub-id pub-id-type="medline">37061434</pub-id>
          <pub-id pub-id-type="pii">S0735-6757(23)00187-0</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>Al-Qarni</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in healthcare: a review of recent attacks and mitigation strategies [internet]</article-title>
          <source>Int J Adv Comput Sci Appl</source>
          <year>2023</year>
          <volume>14</volume>
          <issue>5</issue>
          <fpage>135</fpage>
          <lpage>140</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://thesai.org/Publications/ViewPaper?Volume=14&amp;Issue=5&amp;Code=IJACSA&amp;SerialNo=13"/>
          </comment>
          <pub-id pub-id-type="doi">10.14569/IJACSA.2023.0140513</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Makaryus</surname>
              <given-names>AN</given-names>
            </name>
          </person-group>
          <article-title>The implications of cardiac device cybersecurity responsibilities and challenges faced by policymakers, manufacturers, and patients</article-title>
          <source>Expert Rev Pharmacoecon Outcomes Res</source>
          <year>2024</year>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>743</fpage>
          <lpage>747</lpage>
          <pub-id pub-id-type="doi">10.1080/14737167.2024.2361076</pub-id>
          <pub-id pub-id-type="medline">38808954</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parmeggiani</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Moccia</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Torelli</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Miele</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Luongo</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Sperlongano</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The adoption of a cybersecurity framework in a healthcare, surgical and oncological environment: Synergy-net a Campania FESR-POR (European Fund of Regional Development-Regional Operative Program) research project</article-title>
          <source>Onkologia i Radioterapia</source>
          <year>2024</year>
          <volume>18</volume>
          <issue>7</issue>
          <fpage>1</fpage>
          <lpage>7</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>Grande</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Luna Marti</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Feuerstein-Simon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Merchant</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Asch</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Lewson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cannuscio</surname>
              <given-names>CC</given-names>
            </name>
          </person-group>
          <article-title>Health policy and privacy challenges associated with digital technology</article-title>
          <source>JAMA Netw Open</source>
          <year>2020</year>
          <volume>3</volume>
          <issue>7</issue>
          <fpage>e208285</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32644138"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2020.8285</pub-id>
          <pub-id pub-id-type="medline">32644138</pub-id>
          <pub-id pub-id-type="pii">2768091</pub-id>
          <pub-id pub-id-type="pmcid">PMC7348687</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>Khando</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Salman</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Enhancing employees information security awareness in private and public organisations: a systematic literature review</article-title>
          <source>Comput Secur</source>
          <year>2021</year>
          <volume>106</volume>
          <fpage>102267</fpage>
          <pub-id pub-id-type="doi">10.1016/j.cose.2021.102267</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>Alhassani</surname>
              <given-names>ND</given-names>
            </name>
            <name name-style="western">
              <surname>Windle</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Konstantinidis</surname>
              <given-names>ST</given-names>
            </name>
          </person-group>
          <article-title>A scoping review of the drivers and barriers influencing healthcare professionals' behavioral intentions to comply with electronic health record data privacy policy</article-title>
          <source>Health Informatics J</source>
          <year>2024</year>
          <volume>30</volume>
          <issue>4</issue>
          <fpage>14604582241296398</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/14604582241296398?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/14604582241296398</pub-id>
          <pub-id pub-id-type="medline">39435737</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>Sullivan</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Tully</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Dameff</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Opara</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Snead</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Selzer</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A national survey of hospital cyber attack emergency operation preparedness</article-title>
          <source>Disaster Med Public Health Prep</source>
          <year>2023</year>
          <volume>17</volume>
          <fpage>e363</fpage>
          <pub-id pub-id-type="doi">10.1017/dmp.2022.283</pub-id>
          <pub-id pub-id-type="medline">36945857</pub-id>
          <pub-id pub-id-type="pii">S193578932200283X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref99">
        <label>99</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Giansanti</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Monoscalco</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>The cyber-risk in cardiology: towards an investigation on the self-perception among the cardiologists</article-title>
          <source>mHealth</source>
          <year>2021</year>
          <volume>7</volume>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33898597"/>
          </comment>
          <pub-id pub-id-type="doi">10.21037/mhealth.2020.01.08</pub-id>
          <pub-id pub-id-type="medline">33898597</pub-id>
          <pub-id pub-id-type="pii">mh-07-2020.01.08</pub-id>
          <pub-id pub-id-type="pmcid">PMC8063011</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Lockwood</collab>
            <name name-style="western">
              <surname>Munn</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Porritt</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Qualitative research synthesis: methodological guidance for systematic reviewers utilizing meta-aggregation</article-title>
          <source>Int J Evid Based Healthc</source>
          <year>2015</year>
          <volume>13</volume>
          <issue>3</issue>
          <fpage>179</fpage>
          <lpage>187</lpage>
          <pub-id pub-id-type="doi">10.1097/XEB.0000000000000062</pub-id>
          <pub-id pub-id-type="medline">26262565</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>QN</given-names>
            </name>
            <name name-style="western">
              <surname>Fàbregues</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bartlett</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Boardman</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Cargo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dagenais</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gagnon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Griffiths</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Nicolau</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>O’Cathain</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rousseau</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vedel</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Pluye</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The mixed methods appraisal tool (MMAT) version 2018 for information professionals and researchers</article-title>
          <source>EFI</source>
          <year>2018</year>
          <volume>34</volume>
          <issue>4</issue>
          <fpage>285</fpage>
          <lpage>291</lpage>
          <pub-id pub-id-type="doi">10.3233/efi-180221</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="web">
          <article-title>Critical appraisal checklist for cross-sectional study</article-title>
          <source>Center for Evidence Based Management</source>
          <year>2014</year>
          <access-date>2025-09-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cebma.org/assets/Uploads/Critical-Appraisal-Questions-for-a-Cross-Sectional-Study-July-2014-1-v2.pdf">https://cebma.org/assets/Uploads/Critical-Appraisal-Questions-for-a-Cross-Sectional-Study-July-2014-1-v2.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Baethge</collab>
            <name name-style="western">
              <surname>Goldbeck-Wood</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mertens</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>SANRA-a scale for the quality assessment of narrative review articles</article-title>
          <source>Res Integr Peer Rev</source>
          <year>2019</year>
          <volume>4</volume>
          <fpage>5</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://researchintegrityjournal.biomedcentral.com/articles/10.1186/s41073-019-0064-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s41073-019-0064-8</pub-id>
          <pub-id pub-id-type="medline">30962953</pub-id>
          <pub-id pub-id-type="pii">64</pub-id>
          <pub-id pub-id-type="pmcid">PMC6434870</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jalali</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in hospitals: a systematic, organizational perspective</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <volume>20</volume>
          <issue>5</issue>
          <fpage>e10059</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/5/e10059/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10059</pub-id>
          <pub-id pub-id-type="medline">29807882</pub-id>
          <pub-id pub-id-type="pii">v20i5e10059</pub-id>
          <pub-id pub-id-type="pmcid">PMC5996174</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McInerney</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Munn</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khalil</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Chapter 11: scoping reviews</article-title>
          <source>JBI manual for evidence synthesis</source>
          <year>2020</year>
          <access-date>2025-09-28</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jbi-global-wiki.refined.site/space/MANUAL/355863557/Previous+versions?attachment=/download/attachments/355863557/JBI_Reviewers_Manual_2020June.pdf&amp;type=application/pdf&amp;filename=JBI_Reviewers_Manual_2020June.pdf#page=406">https://jbi-global-wiki.refined.site/space/MANUAL/355863557/Previous+versions?attachment=/download/attachments/355863557/JBI_Reviewers_Manual_2020June.pdf&amp;type=application/pdf&amp;filename=JBI_Reviewers_Manual_2020June.pdf#page=406</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Using thematic analysis in psychology</article-title>
          <source>Qual Res Psychol</source>
          <year>2008</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>101</lpage>
          <pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fernández Maimó</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Huertas Celdrán</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Perales Gómez</surname>
              <given-names>ÁL</given-names>
            </name>
            <name name-style="western">
              <surname>García Clemente</surname>
              <given-names>FJ</given-names>
            </name>
            <name name-style="western">
              <surname>Weimer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Intelligent and dynamic ransomware spread detection and mitigation in integrated clinical environments</article-title>
          <source>Sensors (Basel)</source>
          <year>2019</year>
          <volume>19</volume>
          <issue>5</issue>
          <fpage>1114</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s19051114"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s19051114</pub-id>
          <pub-id pub-id-type="medline">30841592</pub-id>
          <pub-id pub-id-type="pii">s19051114</pub-id>
          <pub-id pub-id-type="pmcid">PMC6427746</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Loi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Christen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kleine</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in health – disentangling value tensions</article-title>
          <source>JICES</source>
          <year>2019</year>
          <volume>17</volume>
          <issue>2</issue>
          <fpage>229</fpage>
          <lpage>245</lpage>
          <pub-id pub-id-type="doi">10.1108/jices-12-2018-0095</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iqbal</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Aurangzeb</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Aleem</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Srivastava</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>JC</given-names>
            </name>
          </person-group>
          <article-title>RThreatDroid: a ransomware detection approach to secure IoT based healthcare systems</article-title>
          <source>IEEE Trans Netw Sci Eng</source>
          <year>2023</year>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>2574</fpage>
          <lpage>2583</lpage>
          <pub-id pub-id-type="doi">10.1109/tnse.2022.3188597</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ghanbari</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Vartiainen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Siponen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Omission of quality software development practices</article-title>
          <source>ACM Comput Surv</source>
          <year>2018</year>
          <volume>51</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>27</lpage>
          <pub-id pub-id-type="doi">10.1145/3177746</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ghafir</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Prenosil</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Hammoudeh</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baker</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Jabbar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Khalid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jaf</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>BotDet: a system for real time botnet command and control traffic detection</article-title>
          <source>IEEE Access</source>
          <year>2018</year>
          <volume>6</volume>
          <fpage>38947</fpage>
          <lpage>38958</lpage>
          <pub-id pub-id-type="doi">10.1109/access.2018.2846740</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref112">
        <label>112</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Loughlin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Gee</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Gieras</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Hoyme</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rajagopalan</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Ransford</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Vasserman</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wirth</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A roundtable discussion: safeguarding information and resources against emerging cybersecurity threats</article-title>
          <source>Biomed Instrum Technol</source>
          <year>2014</year>
          <volume>48</volume>
          <issue>s1</issue>
          <fpage>8</fpage>
          <lpage>17</lpage>
          <pub-id pub-id-type="doi">10.2345/0899-8205-48.s1.8</pub-id>
          <pub-id pub-id-type="medline">24848144</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref113">
        <label>113</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Niu</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>A hybrid solution for privacy preserving medical data sharing in the cloud environment</article-title>
          <source>Future Gener Comput Syst</source>
          <year>2015</year>
          <volume>43-44</volume>
          <fpage>74</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1016/j.future.2014.06.004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref114">
        <label>114</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zorabedian</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>How Malware Works: Anatomy of Drive-By Download Web Attack</source>
          <year>2014</year>
          <access-date>2025-09-16</access-date>
          <publisher-loc>Boston</publisher-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://news.sophos.com/en-us/2014/03/26/how-malware-works-anatomy-of-a-drive-by-download-web-attack-infographic/">https://news.sophos.com/en-us/2014/03/26/how-malware-works-anatomy-of-a-drive-by-download-web-attack-infographic/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref115">
        <label>115</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ackerman</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Mobile health and fitness applications and information privacy</article-title>
          <source>Protection Foundation. Privacy Rights Clearinghouse</source>
          <year>2013</year>
          <access-date>2025-09-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://privacyrights.org/">https://privacyrights.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref116">
        <label>116</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jalali</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Razak</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Perakslis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Madnick</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Health care and cybersecurity: bibliometric analysis of the literature</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12644</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/2/e12644/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12644</pub-id>
          <pub-id pub-id-type="medline">30767908</pub-id>
          <pub-id pub-id-type="pii">v21i2e12644</pub-id>
          <pub-id pub-id-type="pmcid">PMC6396074</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref117">
        <label>117</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Woodward</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity vulnerabilities in medical devices: a complex environment and multifaceted problem</article-title>
          <source>Med Devices (Auckl)</source>
          <year>2015</year>
          <volume>8</volume>
          <fpage>305</fpage>
          <lpage>316</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26229513"/>
          </comment>
          <pub-id pub-id-type="doi">10.2147/MDER.S50048</pub-id>
          <pub-id pub-id-type="medline">26229513</pub-id>
          <pub-id pub-id-type="pii">mder-8-305</pub-id>
          <pub-id pub-id-type="pmcid">PMC4516335</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref118">
        <label>118</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Borky</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bradley</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Protecting information with cybersecurity</article-title>
          <source>Effective Model-Based Systems Engineering</source>
          <year>2019</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer International Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref119">
        <label>119</label>
        <nlm-citation citation-type="web">
          <article-title>Insider threat report 2024</article-title>
          <source>Cybersecurity Insider</source>
          <year>2024</year>
          <access-date>2025-09-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cybersecurity-insiders.com/2024-insider-threat-report/">https://www.cybersecurity-insiders.com/2024-insider-threat-report/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref120">
        <label>120</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pollini</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Callari</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Tedeschi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ruscio</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Save</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Chiarugi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Guerri</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Leveraging human factors in cybersecurity: an integrated methodological approach</article-title>
          <source>Cogn Technol Work</source>
          <year>2022</year>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>371</fpage>
          <lpage>390</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34149309"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10111-021-00683-y</pub-id>
          <pub-id pub-id-type="medline">34149309</pub-id>
          <pub-id pub-id-type="pii">683</pub-id>
          <pub-id pub-id-type="pmcid">PMC8195225</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref121">
        <label>121</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wani</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Mendoza</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>BYOD security behaviour and preferences among hospital clinicians - a qualitative study</article-title>
          <source>Int J Med Inform</source>
          <year>2024</year>
          <volume>192</volume>
          <fpage>105606</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(24)00269-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2024.105606</pub-id>
          <pub-id pub-id-type="medline">39226635</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(24)00269-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref122">
        <label>122</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jalali</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Siegel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Madnick</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Decision-making and biases in cybersecurity capability development: evidence from a simulation game experiment</article-title>
          <source>J Strategic Inf Syst</source>
          <year>2019</year>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>66</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jsis.2018.09.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref123">
        <label>123</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pham</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Loo</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Malhotra</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Longhurst</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hylton</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dameff</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Tully</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wardi</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sell</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Pearce</surname>
              <given-names>AK</given-names>
            </name>
          </person-group>
          <article-title>Ransomware cyberattack associated with cardiac arrest incidence and outcomes at untargeted, adjacent hospitals</article-title>
          <source>Crit Care Explor</source>
          <year>2024</year>
          <volume>6</volume>
          <issue>4</issue>
          <fpage>e1079</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38605720"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/CCE.0000000000001079</pub-id>
          <pub-id pub-id-type="medline">38605720</pub-id>
          <pub-id pub-id-type="pii">CCE-D-24-00111</pub-id>
          <pub-id pub-id-type="pmcid">PMC11008621</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref124">
        <label>124</label>
        <nlm-citation citation-type="web">
          <article-title>Cybersecurity framework 2.0</article-title>
          <source>National Institute of Standards and Technology</source>
          <access-date>2025-09-16</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf">https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref125">
        <label>125</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Badidi</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lamaazi</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Toward a secure healthcare ecosystem: a convergence of edge analytics, blockchain, and federated learning</article-title>
          <year>2024</year>
          <conf-name>20th International Conference on the Design of Reliable Communication Networks (DRCN)</conf-name>
          <conf-date>2024 May 06-09</conf-date>
          <conf-loc>Montreal, QC, Canada</conf-loc>
          <pub-id pub-id-type="doi">10.1109/drcn60692.2024.10539174</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref126">
        <label>126</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carayon</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Hancock</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Leveson</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Noy</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Sznelwar</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>van Hootegem</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Advancing a sociotechnical systems approach to workplace safety--developing the conceptual framework</article-title>
          <source>Ergonomics</source>
          <year>2015</year>
          <volume>58</volume>
          <issue>4</issue>
          <fpage>548</fpage>
          <lpage>564</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/10.1080/00140139.2015.1015623?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/00140139.2015.1015623</pub-id>
          <pub-id pub-id-type="medline">25831959</pub-id>
          <pub-id pub-id-type="pmcid">PMC4647652</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref127">
        <label>127</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Perrotin</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Belloir</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sadou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hairion</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Beugnard</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Using the architecture of socio-technical system to analyse its vulnerability</article-title>
          <year>2022</year>
          <conf-name>17th Annual System of Systems Engineering Conference (SOSE)</conf-name>
          <conf-date>June 07-11, 2022</conf-date>
          <conf-loc>Rochester, NY</conf-loc>
          <pub-id pub-id-type="doi">10.1109/sose55472.2022.9812648</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
