<?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">v26i1e50505</article-id>
      <article-id pub-id-type="pmid">38990611</article-id>
      <article-id pub-id-type="doi">10.2196/50505</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Insights From a Clinically Orientated Workshop on Health Care Cybersecurity and Medical Technology: Observational Study and Thematic Analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>de Azevedo Cardoso</surname>
            <given-names>Taiane</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Röhrig</surname>
            <given-names>Rainer</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>van der Velde</surname>
            <given-names>Enno</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Straw</surname>
            <given-names>Isabel</given-names>
          </name>
          <degrees>BMedSci, BMBS, MPH, MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Institute of Health Informatics</institution>
            <institution>University College London</institution>
            <addr-line>222 Euston Road</addr-line>
            <addr-line>London, NW1 2DA</addr-line>
            <country>United Kingdom</country>
            <phone>44 020 7679 2000</phone>
            <email>isabelstraw@doctors.org.uk</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0003-3550</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Brass</surname>
            <given-names>Irina</given-names>
          </name>
          <degrees>BA, MSc, PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5067-4191</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Mkwashi</surname>
            <given-names>Andrew</given-names>
          </name>
          <degrees>BSc, MBA, PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3609-1317</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Charles</surname>
            <given-names>Inika</given-names>
          </name>
          <degrees>BA, LLB, MPA</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0002-0693-3680</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Soares</surname>
            <given-names>Amelie</given-names>
          </name>
          <degrees>BA, MPA</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-3485-9988</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Steer</surname>
            <given-names>Caroline</given-names>
          </name>
          <degrees>BA, MPA</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-8359-0112</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Institute of Health Informatics</institution>
        <institution>University College London</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Science, Technology, Engineering and Public Policy</institution>
        <institution>University College London</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Newcastle University</institution>
        <addr-line>Newcastle</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>University College London</institution>
        <addr-line>London</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Isabel Straw <email>isabelstraw@doctors.org.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2024</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>11</day>
        <month>7</month>
        <year>2024</year>
      </pub-date>
      <volume>26</volume>
      <elocation-id>e50505</elocation-id>
      <history>
        <date date-type="received">
          <day>3</day>
          <month>7</month>
          <year>2023</year>
        </date>
        <date date-type="rev-request">
          <day>3</day>
          <month>10</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>28</day>
          <month>11</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>17</day>
          <month>5</month>
          <year>2024</year>
        </date>
      </history>
      <copyright-statement>©Isabel Straw, Irina Brass, Andrew Mkwashi, Inika Charles, Amelie Soares, Caroline Steer. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 11.07.2024.</copyright-statement>
      <copyright-year>2024</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/2024/1/e50505" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Health care professionals receive little training on the digital technologies that their patients rely on. Consequently, practitioners may face significant barriers when providing care to patients experiencing digitally mediated harms (eg, medical device failures and cybersecurity exploits). Here, we explore the impact of technological failures in clinical terms.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>Our study explored the key challenges faced by frontline health care workers during digital events, identified gaps in clinical training and guidance, and proposes a set of recommendations for improving digital clinical practice.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A qualitative study involving a 1-day workshop of 52 participants, internationally attended, with multistakeholder participation. Participants engaged in table-top exercises and group discussions focused on medical scenarios complicated by technology (eg, malfunctioning ventilators and malicious hacks on health care apps). Extensive notes from 5 scribes were retrospectively analyzed and a thematic analysis was performed to extract and synthesize data.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Clinicians reported novel forms of harm related to technology (eg, geofencing in domestic violence and errors related to interconnected fetal monitoring systems) and barriers impeding adverse event reporting (eg, time constraints and postmortem device disposal). Challenges to providing effective patient care included a lack of clinical suspicion of device failures, unfamiliarity with equipment, and an absence of digitally tailored clinical protocols. Participants agreed that cyberattacks should be classified as major incidents, with the repurposing of existing crisis resources. Treatment of patients was determined by the role technology played in clinical management, such that those reliant on potentially compromised laboratory or radiological facilities were prioritized.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Here, we have framed digital events through a clinical lens, described in terms of their end-point impact on the patient. In doing so, we have developed a series of recommendations for ensuring responses to digital events are tailored to clinical needs and center patient care.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>digital health</kwd>
        <kwd>clinical medicine</kwd>
        <kwd>biotechnology</kwd>
        <kwd>medical device</kwd>
        <kwd>device regulation</kwd>
        <kwd>medical education</kwd>
        <kwd>eHealth</kwd>
        <kwd>digital medicine</kwd>
        <kwd>health care</kwd>
        <kwd>health care cybersecurity</kwd>
        <kwd>internet of medical things</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The patient who seeks medical care due to a medical device fault, cybersecurity exploit, or failure in digital health infrastructure may encounter a clinical team that lacks an understanding of the nature of their condition [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. These digital events are often framed as computing issues, yet in practice they manifest as patient symptoms and signs and pose significant challenges to the treating clinicians at the point-of-care [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. In our digitized society, where health care provision is increasingly reliant on technological infrastructure, the “Internet of Medical Things,” and connected and intelligent medical devices, computing issues are increasingly translating into clinical complaints [<xref ref-type="bibr" rid="ref2">2</xref>-<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref16">16</xref>].</p>
      <sec>
        <title>The Landscape of Digital Health Technologies</title>
        <p>The proliferation of digital technologies in the health care sector has accelerated over the past decade, with new medical devices entering the market, the growth of consumer health technologies, and the introduction of novel digital tools to hospital workflows (eg, cloud-connected care platforms, digital assistants, and remote monitoring) [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref22">22</xref>]. These devices are connected to communication networks and the Internet to send, store, and process data in the cloud, forming integral components of the evolving “Internet of Medical Things” [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. A subset of medical devices comprise stand-alone software, known as Software as a Medical Device, which may incorporate varying degrees of artificial intelligence (AI) approaches and locked or adaptive machine learning [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. These novel digital tools present many opportunities for improving patient care, yet they have also introduced new vulnerabilities into the health care system that may impact patient safety [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref28">28</xref>].</p>
      </sec>
      <sec>
        <title>New Risks in the Digital Health Landscape</title>
        <p>Our increased reliance on digital infrastructure opens us up to new digital risks, exemplified by the increasing number of cyberattacks affecting the health care sector [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. Borycki et al [<xref ref-type="bibr" rid="ref29">29</xref>] have provided an overview of the new types of technology-induced errors that have arisen in the health care system with the introduction of health information technologies. The authors detailed the dangers of an overreliance on technology and explored the specific challenges faced by clinicians who are “digital natives,” including unrealistic expectations towards fault tolerance and the availability of digital systems [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. Sax et al [<xref ref-type="bibr" rid="ref30">30</xref>] consider the potential patient harm associated with a range of IT failures, including loss of system availability, loss of data, and loss of data integrity. Alemzadeh et al [<xref ref-type="bibr" rid="ref16">16</xref>] place technological events in their clinical context, linking adverse computer incidents to end-point clinical symptoms, uncovering a range of safety-critical computer failures that have resulted in significant patient harm and death.</p>
        <p>In the United Kingdom, the retrospective analyses of the National Health Service (NHS) WannaCry attack highlighted the importance of cybersecurity for patient safety; yet, many NHS hospitals still lack guidance regarding the incident response to a cyberattack [<xref ref-type="bibr" rid="ref28">28</xref>]. Furthermore, security researchers have sounded the alarm regarding the potential for individual-level health care attacks termed “MedJacking,” referring to the remote manipulation of patients’ medical devices such as insulin pumps and deep brain stimulators [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. When such adverse events occur, research has described the challenges encountered by clinicians for whom the clinical manifestations of technological failures may be unfamiliar [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. A recent review of patient illnesses stemming from digital technologies—termed “Biotechnological syndromes”—detailed a range of clinical presentations relating to implanted medical devices (eg, complications of neurostimulators) and technologies within the wider health care system (eg, harms from failures in drug delivery systems) [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>Clinical complications may also arise from digital technologies not traditionally thought of as “digital health” technologies. In particular, the rise in biohacking technologies has presented unexpected challenges to clinicians, as described by Fram et al [<xref ref-type="bibr" rid="ref7">7</xref>] and Gangadharbatla [<xref ref-type="bibr" rid="ref32">32</xref>] in their review of the clinical considerations of consumer implants and microchips. Clinical presentations may also be affected by technology through unexpected mechanisms, as highlighted in cases of technology-facilitated abuse in health care settings [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. Research from the domestic violence field has described the harms faced by patients encountering technology-facilitated abuse (eg, harm inflicted through the manipulation of smart devices) and the need for clinicians to update safeguarding protocols to encompass these risks [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p>
        <p>The introduction of health care AI has brought forward novel ethical questions regarding accountability and liability, with researchers raising concerns about the removal of the “human-in-the-loop” in clinical systems that embed autonomous functions [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Farhud and Zokaei [<xref ref-type="bibr" rid="ref35">35</xref>] and Habli et al [<xref ref-type="bibr" rid="ref36">36</xref>] discuss the challenges of determining moral accountability in complex sociotechnical systems involving AI software, and Fahrud and Zokaei frame these challenges through the traditional pillars of medical ethics (autonomy, beneficence, nonmaleficence, and justice). Dufour et al [<xref ref-type="bibr" rid="ref37">37</xref>] highlight the potential clinical dangers of autonomous systems in their report, which describes several cardiac arrests stemming from algorithmic errors in a series of ventilators. In addition to concerns surrounding AI autonomy, ethicists have illuminated further issues associated with these technologies, including the risks of bias and discrimination in AI-supported clinical decision tools [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref41">41</xref>].</p>
      </sec>
      <sec>
        <title>Clinical Medicine and Digital Health Risks</title>
        <p>Currently, clinicians receive little training on the emerging digital technologies that their patients rely on for care and that professionals depend on to perform their work [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. As detailed by Sally Adee in her comprehensive history of the life sciences and physical sciences, the separation of these 2 scientific domains over the past 200 years has resulted in distinct professional languages and expertise, which often struggle to understand one another [<xref ref-type="bibr" rid="ref42">42</xref>]. However, with the advance of biodigital convergence and the growing prevalence of digital health technologies, clinicians are increasingly likely to encounter patients that are no longer purely biological but rely on varied digital devices requiring an understanding of the physical sciences [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Furthermore, the government bodies tasked with overseeing digital health technologies have faced the challenge of understanding biomedical innovations arriving from overseas, requiring an alignment of domestic standards with the global market [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref44">44</xref>]. As a result, the technologies that play a key role in shaping a patient’s journey may be poorly understood by the health care practitioners and the governmental agencies responsible for public oversight. ‬‬‬‬‬</p>
      </sec>
      <sec>
        <title>Research Aim</title>
        <p>The disciplines of clinical medicine, cybersecurity, and engineering have long operated in silos, and as a result, we lack effective frameworks for patients whose health complaints emerge from the intersection of these domains. In this paper, we present the findings of a confidential multistakeholder workshop that bridged the gap between these professions, facilitating an interdisciplinary discussion on the key challenges affecting digitally dependent patients. We provide insights from frontline staff on the difficulties faced during digital events (eg, cyberattacks and device failures), detail differing perspectives from varied stakeholder groups, and present a series of recommendations for ensuring best clinical practice in the evolving digital health care infrastructure.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>The workshop titled “Emerging Digital Technologies in Patient Care: Dealing with connected, intelligent medical device vulnerabilities and failures in the health care sector” took place at Goodenough College, London, United Kingdom in February 2023. The workshop was part of an EPSRC-funded project investigating how health care systems, regulations, and standards are responding to the cybersecurity and algorithmic integrity challenges posed by the growing use of connected and intelligent medical devices.</p>
      </sec>
      <sec>
        <title>Participant Recruitment</title>
        <p>The workshop of 52 participants had representation from the European Union, the United Kingdom, and the United States, involving a wide range of stakeholder groups (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <p>All workshop participants were recruited based on their practical experience and expertise in digital health care. Limited snowball sampling was used to identify practitioners and experts in the field. Participants were recruited via email by the research team, leveraging the academic, clinical, and professional networks of IS, IB, and AM and their affiliated institutions. Thus, participants were aware of the researchers’ academic profiles prior to the workshop and were provided with detailed information in advance describing the goals of the research.</p>
        <p>No patient or health care data were used for the workshop, and all scenarios (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref> [<xref ref-type="bibr" rid="ref43">43</xref>]) were fictitious and informed by published research. Workshop discussions were held under the Chatham House Rule and neither the identity nor the organizational affiliation of participants will be disclosed in research outputs derived from the workshop. Participants were identified solely by broad stakeholder categories (<xref ref-type="table" rid="table1">Table 1</xref>) using different badge colors for note-taking purposes. No compensation was provided to workshop participants.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Details of workshop participants and their disciplinary backgrounds (N=52).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="500"/>
            <col width="500"/>
            <thead>
              <tr valign="top">
                <td>Stakeholder category</td>
                <td>Participants</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Health care professionals or clinicians</td>
                <td>20</td>
              </tr>
              <tr valign="top">
                <td>Public body representatives</td>
                <td>3</td>
              </tr>
              <tr valign="top">
                <td>Device manufacturers and developers</td>
                <td>6</td>
              </tr>
              <tr valign="top">
                <td>Standards bodies representatives</td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Regulatory consultants and advisers</td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>Academic professionals</td>
                <td>14</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <boxed-text id="box1" position="float">
          <title>Details of the clinical scenarios designed for table-top exercises specific to different specialties, all of which are based on published case reports.</title>
          <p>
            <bold>Acute medicine</bold>
          </p>
          <p>Caring for medical patients during a weekend cyberattack: In scenario 1, a hospital cyberattack compromised a (1) cloud-based platform that detailed chemotherapy regimens for oncology patients, (2) smart drug-delivery systems within the hospital, and (3) patient electronic health records (EHRs). The patients described within the scenario all required specific dosing of medications and careful fluid management; the group had to prioritize patients for care and design a wider hospital response.</p>
          <p>
            <bold>Acute medicine</bold>
          </p>
          <p>Managing unwell patients during a cyberattack on the acute medical unit (AMU): scenario 2 focused on clinical cases requiring careful management of acid-base conditions that necessitated effective blood gas analysis (diabetic ketoacidosis and renal failure) and attentive fluid management (decompensated heart failure); however, the laboratory, blood gas machine, and smart pumps were all compromised.</p>
          <p>
            <bold>Acute medicine</bold>
          </p>
          <p>Treating blind—patient care during a radiological cyberattack: scenario 3 focused on patient conditions where clinical decision-making relied on radiological information, including (1) identification of the pneumothorax for chest drain insertion, (2) use of a chest x-ray to confirm the position of the nasogastric tube, (3) magnetic resonance imaging to diagnose cauda equina syndrome, and (4) computed tomographic imaging to identify an intercranial bleed. In the scenario, the EHR system was unavailable, and the radiological imaging system was known to be compromised (although the impact on the integrity of scans was unclear).</p>
          <p>
            <bold>Surgery and obstetrics</bold>
          </p>
          <p>Mother, baby, and spinal cord stimulator: In scenario 4, the team needed to decide on the best management for a pregnant patient presenting with signs of labor, who reported having a closed-loop spinal cord stimulator in situ. The patient is likely to need a caesarean section due to the breech position of the baby but has not had a preanesthetic evaluation, and there is no available information regarding the spinal cord stimulator. The model of a spinal stimulator has artificial intelligence–integrated functionalities, including the self-adjustment of settings based on patient posture. The team must design a safe clinical care plan that accounts for the device and any complications.</p>
          <p>
            <bold>Emergency and intensive care</bold>
          </p>
          <p>Patient care and ventilator autonomy: scenario 5 was based on the intensive care unit, where a ventilator malfunction causes patients to go into cardiac arrest. The ventilators have integrated automated functions that allow them to update their own settings; however, the attending clinicians are unable to interpret the settings of the machine. The team was tasked with determining the immediate clinical response and discussing the wider implications of closed-loop life support systems in critical medical settings.</p>
          <p>
            <bold>General practice</bold>
          </p>
          <p>Seizure outbreaks in epilepsy management apps: In scenario 6, a teenager presents to her general practitioner with a relapse in seizure symptoms, having a known diagnosis of epilepsy that had been previously well controlled. It is suggested that the epilepsy management app on her phone has been compromised. The team was tasked with planning an appropriate response for this patient and the wider population’s health implications.</p>
        </boxed-text>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>Ethical approval was obtained from the UCL Research Ethics Committee (no 222137/001-0023A). A participant information sheet detailing the research project and a consent form were circulated in advance, and participants were asked to return the consent form via email. All participants provided written informed consent for their contributions to be used as anonymized research data.</p>
      </sec>
      <sec>
        <title>Workshop Structure</title>
        <p>The workshop consisted of two parts: (1) a series of expert talks followed by a Question and Answer (Q&amp;A) session and group discussion, and (2) breakout table-top exercises in which participants discussed and designed a response to a clinical scenario complicated by technology (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>). Clinical scenarios were written to account for the diversity of health care technologies and the disciplinary backgrounds represented in the room. All scenarios were based on published case reports and reported issues related to digital health technologies. The full case scenarios are provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> and detailed in the web-based workshop description [<xref ref-type="bibr" rid="ref45">45</xref>]. Notetakers were present throughout the workshop to record details of Q&amp;A sessions, group discussions, and table-top exercises (audio and visual recording was not used). Notetakers received in-person training in advance of the workshop to review the research materials, discuss the scenarios, address any questions, and agree on a framework for the data collection process.</p>
      </sec>
      <sec>
        <title>Research Data Analysis</title>
        <p>Extensive notes taken during the workshop were retrospectively analyzed and the data from the 5 note-takers was cross-referenced to ensure consistency in the reported results. Four of the researchers coded the qualitative data and undertook an inductive thematic analysis to extract major and minor themes present within the text. Anonymized examples of clinical cases involving technology provided by clinicians were collected as use cases and described in the results.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>Our results are divided into themes extracted from panel Q&amp;As and group discussions, and those identified from the breakout exercises on different clinical scenarios.</p>
      <sec>
        <title>Group Discussions: Identified Themes</title>
        <sec>
          <title>Digital infrastructure: “The Hospital Still Has Windows 10”</title>
          <p>The outdated IT infrastructure of the NHS in the United Kingdom is a known risk for cyberattacks, as these systems can more easily be exploited by malicious actors [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. Participants described the compounding effect that poor IT infrastructure has on their digital behavior, which may further exacerbate the risk of cyber-exploitation. For example, the fact that IT systems are often slow, broken, or unreliable results in clinicians sharing computers, logging in and engaging in risky cyber-hygiene practices. Additionally, the current pressure on NHS staff due to underfunding and staff shortages results in a lack of capacity for additional training on cybersecurity.</p>
          <p>Clinicians expressed that it was hard to get excited about the introduction of digital systems when the basic health care needs of their patients were not being met. Further, practitioners shared concerns regarding the impact of digital innovation on health care inequalities, as access to newer technologies is often mediated by wealth therefore deepening socioeconomic disparities in health outcomes. We heard examples of tech-poverty affecting patients, including accessibility issues related to the rise of telehealth, which is inaccessible to disadvantaged patient groups. Clinicians also raised concerns regarding technology-facilitated abuse, with one participant describing the malicious use of GPS tracking technologies to “Geofence” young women and girls within specific city boroughs, such that abusive parties would receive notifications if they left defined geographic areas (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>).</p>
          <boxed-text id="box2" position="float">
            <title>Anecdotes and examples of patient presentations related to technology that were disclosed by participants at the workshop.</title>
            <p>
              <bold>Hospital medicine</bold>
            </p>
            <p>In a case of a malfunctioning piece of radiological equipment, we had a case where 3 dozen patients were exposed with higher doses, above the diagnostic reference level.</p>
            <p>We know we have issues with pacemaker batteries, but we don’t know how many are affected. We need to understand how to manage that risk.</p>
            <p>Women who was a 35-year-old diabetic patient who died and it was a surprise to the clinical team. The patient had been on a pump and the clinician discussed with the coroner if the pump could have contributed? The husband had thrown the insulin pump in the bin, no one had looked at it so there was no clear cause. We need to collect devices after a death, maybe give them to the police.</p>
            <p>
              <bold>Surgery</bold>
            </p>
            <p>In Obstetrics and Gynecology, there was a case of the wrong woman being given an Emergency C-Section because the communication lines from 2 fetal CTGs overlapped, and one baby’s readings had been assigned to the wrong mother.</p>
            <p>
              <bold>Community care</bold>
            </p>
            <p>In general practice surgery, Apple watches causing patients to think their heart rhythms are abnormal.</p>
            <p>Seen issues in general practice with tech-abuse and GPS tracking. Young girls in some communities have to stay inside their borough, otherwise an alarm goes off to their family or partner.</p>
          </boxed-text>
        </sec>
        <sec>
          <title>Trust and Medical Devices: “The Device Should Be Considered Guilty Until Proven Otherwise”</title>
          <p>Clinicians expressed concerns regarding the often-unchallenged assumption that exists in the medical community regarding device functionality, with one practitioner sharing the view that “99.9% of clinicians wouldn’t expect a device to fail,” reinforced by peers stating that they’d be highly unlikely to suspect embedded technology as a source of pathology. In cases where medical devices do fail, manufacturers shared that it is not always easy to identify the cause. Companies may be able to take a piece of technology back and attempt to replicate the failure mode; however, often these faults are attributed to unknown internal or external factors.</p>
          <p>Manufacturers highlighted the risk of eroding patient trust when device malfunctions are poorly communicated, detailing the historic challenges that they have faced when communicating issues to patients, stating, “It is easy to spend millions on recalls when it is not necessary.” Workshop participants discussed that manufacturers are often cognizant that technologies fail but may feel that publicizing all of these events could cause unnecessary alarm, especially in cases where a fault (eg, a software bug) is likely inconsequential but causes fear due to its presence in a consequential technology (eg, a ventilator). Lastly, representatives from the policy domain highlighted the potential for fake news and disinformation that could result from misinterpreted reports of technological failures. Participants also raised issues of public versus private interests, exploring the role that financial incentives play when making decisions regarding device fault disclosures.</p>
        </sec>
        <sec>
          <title>Responsibility and Liability: “Clinicians Don’t Have Time to Report This”</title>
          <p>Views differed between clinicians and manufacturers on the topics of device failure reporting, post-market surveillance, and professional liability in cases of patient harm. Clinicians shared frustrations that they “don’t have time to report this” (referring to device malfunctions), stating that responsibility for consistent surveillance of deployed devices should be with the manufacturer. The issue of transparency was evident when discussing the communication between clinicians, manufacturers, and regulatory agencies, as manufacturers often found themselves limited in the information they could share due to commercial confidentiality. Furthermore, there was confusion as to whether reporting device errors was mandatory, with clinicians stating that this was a voluntary (and unfortunately often underperformed) action, and other participants stating this was an obligation.</p>
          <p>Workshop participants heard from representatives from the consumer implant industry, who described the increasing uptake of implanted radio frequency identification and near-field communication chips in younger generations. Such body modification technologies that are sited under the skin can cause medical complications (eg, infections, soft tissue injury); however, these technologies do not fall under medical device regulation. It manifested that members of the public occasionally approach these companies, expressing fears of being chipped by “the government” or “aliens”; yet, in the case of potentially serious mental health concerns, these individuals are not redirected to appropriate health care support. Additional ethically contentious cases were discussed, including requests from family members to “chip” older relatives with dementia, or younger children. There was a clearly identified need for improving safeguarding referral pathways.</p>
        </sec>
      </sec>
      <sec>
        <title>Clinical Scenarios</title>
        <p>The focused disciplinary table-top exercises facilitated a deeper dive into the specific clinical issues that may arise within each clinical domain.</p>
        <sec>
          <title>Medical Scenarios—“With Most Tech, we Don’t Know How it Works, so we Don’t Know How to Trust it”</title>
          <p>The 3 hospital-based medical scenarios described failures in cloud-based treatment platforms, laboratory equipment, radiological systems, and electronic health records. Clinicians initially drew parallels to previous experiences where IT had been compromised, referencing the WannaCry 2017 attack and climate events (eg, heat waves) affecting computer systems. Practitioners described the chaos of shifting to paper-based prescribing and note-taking during on-call and overnight hours, during which time they noted a lack of leadership and defined protocols for responding to the event clinically.</p>
          <p>In designing their response, all groups reached consensus that the cyberattack should be classified as a “major incident,” activating a chain of responses including the recruitment of additional staff, awareness at the national level, communication across sites, an effective PR response, and the allocation of roles to those with sufficient skills and seniority. Senior team members suggested the development of battle bags and action cards that are commonly used in other major incident events, citing Grenfell Tower and the Manchester Bombing as examples. Clinicians demonstrated some awareness of available resources, including NHS Digital and Chief Information Officers; however, these resources were relatively unheard of within the groups.</p>
          <p>The scenario suggested there were cybersecurity vulnerabilities in the drug delivery and laboratory systems present on the wards, to which health care staff reported a preference for shutting down technology entirely as a safety measure (while acknowledging that this could be unnecessary and cause delays and even more harm). When discussing plans to turn off digital systems, the groups shared their concerns about what disabling devices would do and whether there was a default safe mode that could protect patients. In shutting down digital equipment, participants decided to return to rudimentary clinical techniques, including dripping (the act of delivering intravenous medications based on drips of liquid). The teams raised concerns for younger generations of clinicians who may not have this nondigital foundation to fall back on.</p>
          <p>Lastly, practitioners identified the patients most at risk of harm in the context of IT manipulation in the hospital and developed a clinical hierarchy specific to digital threats. The patients with diabetic ketoacidosis and cauda equina were identified as likely to experience the worst outcomes due to their reliance on laboratory and radiological resources for treatment. By prioritizing the patients according to the role that technology played in their clinical management, participants framed the cyberattacks in clinical terms.</p>
        </sec>
        <sec>
          <title>Surgical Scenario—“Mother, Baby, and Spinal Cord Stimulator”—“There Is no Way of Knowing How the Body Is Communicating With the Device”</title>
          <p>The surgical group was tasked with managing a patient in active labor who had a potentially compromised implanted spinal cord stimulator. Through the discussion, it became apparent that there was a lack of clinical knowledge regarding the implications of the technology, and the health care staff opted to focus on the medical management that they did understand while putting the technical components to one side. In discussing the follow-up to the case, standard body representatives raised concerns that the incident would not be flagged as an adverse outcome, supported by clinicians who indicated that this would be unlikely to be reported.</p>
        </sec>
        <sec>
          <title>Emergency and Intensive Care Scenario—“Patient Care and Ventilator Autonomy”</title>
          <p>The clinicians first drew comparisons to historic crises events, including the 1952 Copenhagen crisis, in which medical students were recruited to manually ventilate patients [<xref ref-type="bibr" rid="ref47">47</xref>]. When discussing the initial response to the scenario, the team discussed disconnecting all patients from the ventilators while acknowledging the challenges of doing this in an intensive care unit where patients are dependent on life support systems. The group discussed the specific implications of AI and closed-loop systems within medical equipment, identifying the central issue of trust and a lack of understanding of the technological mechanisms. The lack of training in AI systems was felt to be compounded by the absence of training regarding cyberattacks, with clinicians sharing that they had “never had a training day on what would happen in this scenario.”</p>
        </sec>
        <sec>
          <title>Community Care and General Practice Scenario—“Seizure Outbreaks in Epilepsy Management Apps”</title>
          <p>The scenario based on community care described a teenage patient who experienced a relapse in seizure symptoms, suspected to be related to a malicious hack on an epilepsy app. The group began by identifying possible adverse health effects, including seizures, headaches, distress, loss of vision, loss of focus, visual effects, and airway compromise. At-risk patient groups were noted, including dementia patients and those with neurodiversity. For immediate clinical management, practitioners felt that staff were likely to tell the patient to avoid the app or their phone entirely, reiterating a theme heard in the other groups of completely disconnecting from the technology.</p>
          <p>In contrast to the other groups, the general practitioners discussed reporting the case to the police and ministry of defense due to the concern of a malicious attack and the implications this could have for a large number of people using the app. Participants also described the need to involve parents as this was a pediatric case and the role of the app company in protecting their users.</p>
        </sec>
      </sec>
      <sec>
        <title>Uncovered Examples</title>
        <p>During the workshop, practitioners provided anonymized anecdotes of patient harm where technology played a role. <xref ref-type="boxed-text" rid="box2">Textbox 2</xref> provides these example cases. In reflecting on a patient death, one participant discussed the lack of postmortem guidance, highlighting that the disposal of devices as medical waste precludes the evaluation of their involvement in a death.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>In a patient journey, the individual is likely to encounter various forms of technology, from their electronic health record, to advanced, interconnected, automated, and intelligent health care technologies [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]. In these journeys, health care staff are the immediate point of contact when clinical care goes wrong, and patient health deteriorates [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. In this paper, we have explored the points of digital vulnerability that may contribute to patient illness along these trajectories and discussed the issues of cybersecurity, device failures, and faulty AI systems from the perspective of treating clinicians.</p>
        <p>Clinicians from a diverse range of specialties responded in a similar manner when confronted with failures in digital devices, opting to immediately shut down the technology. Whether this was disconnecting patients from ventilators, disabling all medication smart pumps, or advising patients to turn off phones that were vulnerable to malicious hacks, the safest measure was often considered to be preventing any ongoing interaction between the technology and the patient’s physicality. The response is understandable given that clinicians receive little education on these tools and do not trust the systems or have the confidence to appropriately evaluate them.</p>
        <p>Yet when clinicians are not informed of a potential technological failure, the default position appears to be the opposite and to trust devices entirely, such that “99.9% of clinicians wouldn’t expect a device to fail.” Hence, an interesting dichotomy exists—when a clinician has not been given reason to doubt a device, they will often trust the device over the patient (eg, believing the patient’s blood glucose data, as opposed to their subjective symptoms); however, once doubt is introduced, the clinicians opt to disregard the technology completely. The polarity of these reactions mirrors the black-and-white nature of the black-box technology that remains opaque to clinicians using the digital tools. This delicate relationship reinforces the importance of effective communication around medical device failures with clinicians as well as with the public.</p>
        <p>The lack of reporting regarding digital adverse events is a regulatory and public policy concern. <xref ref-type="boxed-text" rid="box2">Textbox 2</xref> provides a list of events we collected in this workshop, of which several remained unreported and describe significant patient harm. Within these stories, we heard new examples of biotechnological syndromes and forms of technology-facilitated abuse that add to the existing literature reporting issues of technology in domestic violence and the risks posed to vulnerable patients [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>].</p>
        <p>We heard differing opinions on where responsibility and professional liability should lie when patient harm occurs because of a technology malfunction, with clinicians sharing the view that manufacturers are responsible for ongoing follow-up and manufacturers stating that clinicians are responsible for the outcomes of patients with embedded devices. Health care professionals advocated for a higher standard to be placed on manufacturers with regard to patient trust and transparency, citing parallels to the Hippocratic oath and fundamental medical ethics taught in medical school. These suggestions have previously been made by several health care cybersecurity researchers who developed a “Hippocratic Oath for Connected Medical Devices” [<xref ref-type="bibr" rid="ref39">39</xref>-<xref ref-type="bibr" rid="ref41">41</xref>].</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Our research has taken the unique approach of positioning digital health care technology failures in their medical context, viewed through the lens of the clinician at the point of care. In doing this, we demonstrate how health care staff can form tailored clinical hierarchies when faced with health care cyberattacks, such as prioritizing patients’ dependence on digitally vulnerable systems (eg, spinal injuries requiring radiological imaging) or identifying at-risk groups of mobile screen-based hacks (eg, patients with epilepsy, those who are neurodiverse, and those with dementia). Understanding cyberattacks as clinical attacks in this manner provides an opportunity to form the guidelines and major incident response protocols that our participants identified as urgent and lacking resources in hospital settings.</p>
        <p>Our findings illustrate gaps in clinical knowledge regarding medical technology and a lack of confidence in managing these scenarios, which can only be addressed with improved clinical education and training. To ensure effective patient care in our environment of evolving digital infrastructure, historic IT responses to cyberattacks and device failures must be married with the clinical needs and perspectives provided in this report. Our research shines a light on a critical and understudied area at the intersection of clinical medicine and digital health that requires greater research and professional guidance. We provide a series of recommendations based on our findings in <xref ref-type="boxed-text" rid="box3">Textbox 3</xref>.</p>
        <boxed-text id="box3" position="float">
          <title>Recommendations.</title>
          <list list-type="bullet">
            <list-item>
              <p>
                <bold>Hospital protocols and incident plans:</bold>
              </p>
              <p>Cyberattacks should be treated as clinical attacks, framed similarly to other major incidents such as terrorist and extreme weather events [<xref ref-type="bibr" rid="ref50">50</xref>]. To achieve this, cyberattack threat models should be developed with end-point clinical symptoms and signs in mind, necessitating input from clinicians and engineers. Hospitals and health care practices should develop major incident protocols that specify the clinical steps to be taken in a cyberattack, hierarchically prioritizing patient groups, and repurposing existing resources such as action cards, dedicated response teams, battle bags, and communication pathways for escalation.</p>
            </list-item>
            <list-item>
              <p>
                <bold>Medical education and clinical training:</bold>
              </p>
              <p>Health care practitioners require a fundamental understanding of the novel digital technologies that their patients rely on, in order to treat them effectively when digital complications arise. Software-based medical devices, especially those connected to communication networks and with AI-integrated functionalities, require continuous monitoring of their performance by hospital staff and their medical device inventory teams. Digitally themed professional courses through the UK Royal Colleges would incentivize an uptake of this training, in addition to integrating educational content into National Health Service Trust mandatory training modules, clinical orientation and induction weeks in hospitals, and medical school education curricula.</p>
            </list-item>
            <list-item>
              <p>
                <bold>Academia and research:</bold>
              </p>
              <p>Research focused on the health complications of digital technologies needs to advance at a parallel rate to the development and deployment of digital health care tools and devices. Future research focused on the symptoms and signs of digital failures and technological pathology would improve the ability of clinicians to diagnose these cases, and consequently report them to the appropriate bodies.</p>
            </list-item>
            <list-item>
              <p>
                <bold>Manufacturer training and support:</bold>
              </p>
              <p>An easily accessible interface between manufacturers and clinicians is required to ensure health care staff can find appropriate information about the performance of connected and intelligent medical devices in a timely manner. Manufacturers could develop “how-to” cards and clinically tailored resources about their digital medical devices, which would be more useful to health care staff than traditional user manuals.</p>
            </list-item>
            <list-item>
              <p>
                <bold>Regulation and reporting:</bold>
              </p>
              <p>Increased interaction is needed between regulatory agencies, such as the Medicines and Healthcare products Regulatory Agency, and clinical teams. Through events in medical schools, hospitals, and community health care practices, representatives of public and regulatory bodies may provide additional support to clinicians on the reporting processes and existing guidance regarding software-based and connected medical devices.</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>While we engaged a range of critical stakeholders in our workshop, we were limited by sample size and the representativeness of our participants. In future research, it would be beneficial to engage a wider range of clinical specialties, such as dermatologists, oncologists, radiologists, and neurologists, where digital health technologies are expanding rapidly. Furthermore, we have limited our focus to emerging digital technologies, with functionalities including telemetry, internet connectivity, and AI. As a result, we have not examined issues associated with static medical devices; for example, adverse reactions to materials used for hip implants.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Supplementary Material: Workshop Scenarios for Dealing with Connected, Intelligent Medical Device Vulnerabilities and Failures.</p>
        <media xlink:href="jmir_v26i1e50505_app1.docx" xlink:title="DOCX File , 42 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">Q&amp;A</term>
          <def>
            <p>Question and Answer</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to express their appreciation to the PETRAS team and all stakeholders who took part in our primary research and provided us with a wealth of information on this topic. Special thanks go to our project partners at BSI (the United Kingdom’s National Standards Body) for their guidance and support throughout this project, especially Rob Turpin, Paul Sim, Emma Glass, and Matthew Chiles. This research is funded by the PETRAS National Centre of Excellence in IoT Systems Cybersecurity (EPSRC grant number EP/S035362/1).</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The data and clinical scenarios generated during and analyzed during this study are available in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>The authorship contributions are listed as per the CRediT authorship criteria. The study was conceptualized by IS, IB, and AM; data were curated by IS, IB, IC, AS, and CS; formal analysis was conducted by IS, IB, IC, AS, and CS; the investigation was carried out by IS, IB, AM, IC, AS, and CS; the methodology was designed by IS, IB, and AM; resources were provided by IB and AM; IB supervised the study; validation was carried out by IB; writing—original draft preparation was carried out by IS; writing—review and editing was carried out by IS and IB. All authors reviewed and approved the final version. The details of the researchers, as per the COREQ (consolidated criteria for reporting qualitative research) checklist, are as follows. At the time of the research study and qualitative data collection, IS (female) was a medical doctor and PhD candidate in artificial intelligence–enabled health care at University College London (UCL); IB (female) was an associate professor of regulation, innovation and public policy at the Department of Science, Technology, Engineering and Public Policy (STEaPP) at UCL; AM (male) was a research fellow on the Regulation and Standardization of Connected, Intelligent Medical Devices (REG-MEDTECH) project at the STEaPP at UCL; and IC (female), AS (female), and CS (female) were candidates on the masters in public administration in digital technologies and policy at UCL and employed as research assistants in the REG-MEDTECH project.</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="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="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dameff</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Farah</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Killeen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Cyber disaster medicine: a new frontier for emergency medicine</article-title>
          <source>Ann Emerg Med</source>
          <year>2020</year>
          <volume>75</volume>
          <issue>5</issue>
          <fpage>642</fpage>
          <lpage>647</lpage>
          <pub-id pub-id-type="doi">10.1016/j.annemergmed.2019.11.011</pub-id>
          <pub-id pub-id-type="medline">31959537</pub-id>
          <pub-id pub-id-type="pii">S0196-0644(19)31381-2</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>Sommer</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stiksrud</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>von Eckardstein</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Rohde</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Paulus</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>When battery exhaustion lets the lame walk: a case report on the importance of long-term stimulator monitoring in deep brain stimulation</article-title>
          <source>BMC Neurol</source>
          <year>2015</year>
          <volume>15</volume>
          <fpage>113</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcneurol.biomedcentral.com/articles/10.1186/s12883-015-0365-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12883-015-0365-6</pub-id>
          <pub-id pub-id-type="medline">26187628</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12883-015-0365-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC4506586</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>Shao</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Cochlear implant electrode failure secondary to silicone touch-up during device manufacturing</article-title>
          <source>Otol Neurotol</source>
          <year>2013</year>
          <volume>34</volume>
          <issue>7</issue>
          <fpage>e72</fpage>
          <lpage>e75</lpage>
          <pub-id pub-id-type="doi">10.1097/MAO.0b013e318298aaaf</pub-id>
          <pub-id pub-id-type="medline">23921929</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>Straw</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Rees</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Nachev</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>21st century medicine and emerging biotechnological syndromes: a cross-disciplinary systematic review of novel patient presentations in the age of technology</article-title>
          <source>BMC Digit Health</source>
          <year>2023</year>
          <issue>1</issue>
          <fpage>41</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1186/s44247-023-00044-x"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s44247-023-00044-x</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Adashi</surname>
              <given-names>EY</given-names>
            </name>
            <name name-style="western">
              <surname>Thomasian</surname>
              <given-names>NM</given-names>
            </name>
          </person-group>
          <article-title>Medical devices in harm's way: medjacking</article-title>
          <source>JAMA Health Forum</source>
          <year>2020</year>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>e200007</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jamanetwork.com/article.aspx?doi=10.1001/jamahealthforum.2020.0007"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamahealthforum.2020.0007</pub-id>
          <pub-id pub-id-type="medline">36218531</pub-id>
          <pub-id pub-id-type="pii">2759776</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fram</surname>
              <given-names>BR</given-names>
            </name>
            <name name-style="western">
              <surname>Rivlin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Beredjiklian</surname>
              <given-names>PK</given-names>
            </name>
          </person-group>
          <article-title>On emerging technology: what to know when your patient has a microchip in his hand</article-title>
          <source>J Hand Surg Am</source>
          <year>2020</year>
          <volume>45</volume>
          <issue>7</issue>
          <fpage>645</fpage>
          <lpage>649</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jhsa.2020.01.008</pub-id>
          <pub-id pub-id-type="medline">32164995</pub-id>
          <pub-id pub-id-type="pii">S0363-5023(20)30033-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Straw</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Ashworth</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Radford</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>When brain devices go wrong: a patient with a malfunctioning deep brain stimulator (DBS) presents to the emergency department</article-title>
          <source>BMJ Case Rep</source>
          <year>2022</year>
          <volume>15</volume>
          <issue>12</issue>
          <fpage>e252305</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36572446"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bcr-2022-252305</pub-id>
          <pub-id pub-id-type="medline">36572446</pub-id>
          <pub-id pub-id-type="pii">15/12/e252305</pub-id>
          <pub-id pub-id-type="pmcid">PMC9806045</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <article-title>Guidance for manufacturers on reporting adverse incidents involving Software as a Medical Device under the vigilance system</article-title>
          <source>UK Government</source>
          <year>2023</year>
          <access-date>2023-06-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://tinyurl.com/5n85fj7k">https://tinyurl.com/5n85fj7k</ext-link>
          </comment>
        </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>Mkwashi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Brass</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>The future of medical device regulation and standards: dealing with critical challenges for connected, intelligent medical devices (September 7, 2022)</article-title>
          <year>2022</year>
          <conf-name>PETRAS National Centre of Excellent in IoT Systems Cybersecurity: London</conf-name>
          <conf-date>07 September 2027</conf-date>
          <conf-loc>London</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ssrn.com/abstract=4226057"/>
          </comment>
          <pub-id pub-id-type="doi">10.2139/ssrn.4226057</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patra</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ferrari</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Kraleva</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>The internet of medical thingsnabling technologies and emerging applications</article-title>
          <source>In Institution of Engineering and Technology (The IET)</source>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://air.unipr.it/handle/11381/2938191">https://air.unipr.it/handle/11381/2938191</ext-link>
          </comment>
        </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>Amato</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Internet of bodies: digital content directive, and beyond</article-title>
          <source>J Intell Property Inf Technol Electron Commerce Law</source>
          <year>2021</year>
          <volume>12</volume>
          <issue>2</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jipitec.eu/issues/jipitec-12-2-2021/5285"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>South</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Borkin</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Ethical considerations of photosensitive epilepsy in mixed reality</article-title>
          <source>OSF Preprints</source>
          <comment>Preprint posted online October 23, 2020</comment>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://osf.io/y32td/"/>
          </comment>
          <pub-id pub-id-type="doi">10.31219/osf.io/y32td</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nishihama</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Eguchi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Maki</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Okano</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Tanaka</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Inoue</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Uchida</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Uemura</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Suzuki</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Yasuma</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>D'Alessandro-Gabazza</surname>
              <given-names>CN</given-names>
            </name>
            <name name-style="western">
              <surname>Gabazza</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Yano</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Sudden death associated with severe hypoglycemia in a diabetic patient during sensor-augmented pump therapy with the predictive low glucose management system</article-title>
          <source>Am J Case Rep</source>
          <year>2021</year>
          <volume>22</volume>
          <fpage>e928090</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/33462171/"/>
          </comment>
          <pub-id pub-id-type="doi">10.12659/ajcr.928090</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Straw</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Dobbin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Reaver</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Tanczer</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Medical cyber crises and biotechnological syndromes: a multisite clinical simulation study focused on digital health complaints</article-title>
          <source>Lancet</source>
          <year>2023</year>
          <volume>402</volume>
          <issue>Suppl 1</issue>
          <fpage>S88</fpage>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(23)02082-2</pub-id>
          <pub-id pub-id-type="medline">37997134</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(23)02082-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alemzadeh</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Iyer</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Kalbarczyk</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Raman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Analysis of safety-critical computer failures in medical devices</article-title>
          <source>IEEE Secur Privacy</source>
          <year>2013</year>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>14</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.1109/msp.2013.49</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ronte</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Medtech and the internet of medical things: how connected medical devices are transforming health care</article-title>
          <source>Deloitte</source>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www2.deloitte.com/content/dam/Deloitte/global/Documents/Life-Sciences-Health-Care/gx-lshc-medtech-iomt-brochure.pdf">https://www2.deloitte.com/content/dam/Deloitte/global/Documents/Life-Sciences-Health-Care/gx-lshc-medtech-iomt-brochure.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Afolabi</surname>
              <given-names>BA</given-names>
            </name>
          </person-group>
          <source>Remote monitoring of patients with implanted cardiac devices—a review</source>
          <year>2012</year>
          <access-date>2012-04-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ecrjournal.com/articles/remote-monitoring-patients-implanted-cardiac-devices-review">https://www.ecrjournal.com/articles/remote-monitoring-patients-implanted-cardiac-devices-review</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nurshod</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khujamatov</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lazarev</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Remote monitoring system architectures in healthcare</article-title>
          <year>2021</year>
          <conf-name>International Conference on Information Science and Communications Technologies (ICISCT). 2021</conf-name>
          <conf-date>2023 Nov 03</conf-date>
          <conf-loc>Tashkent, Uzbekistan</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icisct52966.2021.9670405</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>Tarakji</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Zaidi</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Zweibel</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Varma</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Sears</surname>
              <given-names>SF</given-names>
            </name>
            <name name-style="western">
              <surname>Allred</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>PR</given-names>
            </name>
            <name name-style="western">
              <surname>Shaik</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Silverstein</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Maher</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mittal</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patwala</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schoenhard</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Emert</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Molon</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Augello</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Seide</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Porfilio</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Maus</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Di Jorio</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Holloman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Natera</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Turakhia</surname>
              <given-names>MP</given-names>
            </name>
          </person-group>
          <article-title>Performance of first pacemaker to use smart device app for remote monitoring</article-title>
          <source>Heart Rhythm O2</source>
          <year>2021</year>
          <volume>2</volume>
          <issue>5</issue>
          <fpage>463</fpage>
          <lpage>471</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2666-5018(21)00125-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.hroo.2021.07.008</pub-id>
          <pub-id pub-id-type="medline">34667961</pub-id>
          <pub-id pub-id-type="pii">S2666-5018(21)00125-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC8505204</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Turpin</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hoefer</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lewelling</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Baird</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Adapting regulatory frameworks and standards to ensure safety and performance. Association for the Advancement of Medical Instrumentation (AAMI), British Standards Institute (BSI)</article-title>
          <source>Machine Learning AI in Medical Devices</source>
          <year>2020</year>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bsigroup.com/en-US/medical-devices/resources/Whitepapers-and-articles/machine-learning-ai-in-medical-devices/">https://www.bsigroup.com/en-US/medical-devices/resources/Whitepapers-and-articles/machine-learning-ai-in-medical-devices/</ext-link>
          </comment>
        </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>Garg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>NL</given-names>
            </name>
            <name name-style="western">
              <surname>Ip</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dicker</surname>
              <given-names>AP</given-names>
            </name>
          </person-group>
          <article-title>Clinical integration of digital solutions in health care: an overview of the current landscape of digital technologies in cancer care</article-title>
          <source>JCO Clin Cancer Inform</source>
          <year>2018</year>
          <volume>2</volume>
          <fpage>1</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ascopubs.org/doi/10.1200/CCI.17.00159?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.1200/CCI.17.00159</pub-id>
          <pub-id pub-id-type="medline">30652580</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <source>Artificial Intelligence and Machine Learning (AI/ML)—Software as a Medical Device: Action Plan</source>
          <year>2021</year>
          <publisher-loc>USA</publisher-loc>
          <publisher-name>Food and Drug Administration (FDA)</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="web">
          <article-title>The Regulation of Artificial Intelligence as a Medical Device</article-title>
          <source>Regulatory Horizons Council, UK Government</source>
          <access-date>2023-11-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/1120503/RHC_regulation_of_AI_as_a_Medical_Device_report.pdf">https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/1120503/RHC_regulation_of_AI_as_a_Medical_Device_report.pdf</ext-link>
          </comment>
        </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>Ghafur</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Grass</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Jennings</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The challenges of cybersecurity in health care: the UK national health service as a case study</article-title>
          <source>Lancet Digit Health</source>
          <year>2019</year>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>e10</fpage>
          <lpage>e12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(19)30005-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(19)30005-6</pub-id>
          <pub-id pub-id-type="medline">33323235</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(19)30005-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ghafur</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fontana</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Grass</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Goodman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Improving Cyber Security in the NHS</source>
          <access-date>2024-05-30</access-date>
          <publisher-loc>London</publisher-loc>
          <publisher-name>Imperial College London</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.imperial.ac.uk/media/imperial-college/institute-of-global-health-innovation/Cyber-report-2020.pdf">https://www.imperial.ac.uk/media/imperial-college/institute-of-global-health-innovation/Cyber-report-2020.pdf</ext-link>
          </comment>
        </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>O’Brien</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ghafur</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Durkin</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in health is an urgent patient safety concern: we can learn from existing patient safety improvement strategies to address it</article-title>
          <source>J Patient Saf Risk Manag</source>
          <year>2021</year>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.1177/2516043520975926</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>Ghafur</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kristensen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Honeyford</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Aylin</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A retrospective impact analysis of the wannaCry cyberattack on the NHS</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <volume>2</volume>
          <fpage>98</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0161-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0161-6</pub-id>
          <pub-id pub-id-type="medline">31602404</pub-id>
          <pub-id pub-id-type="pii">161</pub-id>
          <pub-id pub-id-type="pmcid">PMC6775064</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>Borycki</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Dexheimer</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Hullin Lucay Cossio</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gong</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kaipio</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kennebeck</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kirkendall</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Kushniruk</surname>
              <given-names>AW</given-names>
            </name>
            <name name-style="western">
              <surname>Kuziemsky</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Marcilly</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Röhrig</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Saranto</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Senathirajah</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Takeda</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Methods for addressing technology-induced errors: the current state</article-title>
          <source>Yearb Med Inform</source>
          <year>2016</year>
          <issue>1</issue>
          <fpage>30</fpage>
          <lpage>40</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.15265/IY-2016-029"/>
          </comment>
          <pub-id pub-id-type="doi">10.15265/IY-2016-029</pub-id>
          <pub-id pub-id-type="medline">27830228</pub-id>
          <pub-id pub-id-type="pii">me2016-029</pub-id>
          <pub-id pub-id-type="pmcid">PMC5171580</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>Sax</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Lipprandt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Röhrig</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The rising frequency of IT blackouts indicates the increasing relevance of IT emergency concepts to ensure patient safety</article-title>
          <source>Yearb Med Inform</source>
          <year>2016</year>
          <issue>1</issue>
          <fpage>130</fpage>
          <lpage>137</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.15265/IY-2016-038"/>
          </comment>
          <pub-id pub-id-type="doi">10.15265/IY-2016-038</pub-id>
          <pub-id pub-id-type="medline">27830241</pub-id>
          <pub-id pub-id-type="pii">me2016-038</pub-id>
          <pub-id pub-id-type="pmcid">PMC5171553</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pycroft</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Boccard</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Owen</surname>
              <given-names>SLF</given-names>
            </name>
            <name name-style="western">
              <surname>Stein</surname>
              <given-names>JF</given-names>
            </name>
            <name name-style="western">
              <surname>Fitzgerald</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Aziz</surname>
              <given-names>TZ</given-names>
            </name>
          </person-group>
          <article-title>Brainjacking: implant security issues in invasive neuromodulation</article-title>
          <source>World Neurosurg</source>
          <year>2016</year>
          <volume>92</volume>
          <fpage>454</fpage>
          <lpage>462</lpage>
          <pub-id pub-id-type="doi">10.1016/j.wneu.2016.05.010</pub-id>
          <pub-id pub-id-type="medline">27184896</pub-id>
          <pub-id pub-id-type="pii">S1878-8750(16)30272-8</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>Gangadharbatla</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Biohacking: an exploratory study to understand the factors influencing the adoption of embedded technologies within the human body</article-title>
          <source>Heliyon</source>
          <year>2020</year>
          <volume>6</volume>
          <issue>5</issue>
          <fpage>e03931</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2405-8440(20)30776-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.heliyon.2020.e03931</pub-id>
          <pub-id pub-id-type="medline">32426543</pub-id>
          <pub-id pub-id-type="pii">S2405-8440(20)30776-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7226663</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Straw</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Tanczer</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Safeguarding patients from technology-facilitated abuse in clinical settings: a narrative review</article-title>
          <source>PLoS Digit Health</source>
          <year>2023</year>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e0000089</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36812593"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pdig.0000089</pub-id>
          <pub-id pub-id-type="medline">36812593</pub-id>
          <pub-id pub-id-type="pii">PDIG-D-22-00204</pub-id>
          <pub-id pub-id-type="pmcid">PMC9931347</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tanczer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>López-Neira</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Parkin</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>'I feel like we're really behind the game': perspectives of the United Kingdom's intimate partner violence support sector on the rise of technology-facilitated abuse</article-title>
          <source>J Gender-Based Violence</source>
          <year>2021</year>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>431</fpage>
        </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>Farhud</surname>
              <given-names>DD</given-names>
            </name>
            <name name-style="western">
              <surname>Zokaei</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Ethical issues of artificial intelligence in medicine and healthcare</article-title>
          <source>Iran J Public Health</source>
          <year>2021</year>
          <volume>50</volume>
          <issue>11</issue>
          <fpage>i</fpage>
          <lpage>v</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35223619"/>
          </comment>
          <pub-id pub-id-type="doi">10.18502/ijph.v50i11.7600</pub-id>
          <pub-id pub-id-type="medline">35223619</pub-id>
          <pub-id pub-id-type="pii">IJPH-50-i</pub-id>
          <pub-id pub-id-type="pmcid">PMC8826344</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>Habli</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Lawton</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Porter</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence in health care: accountability and safety</article-title>
          <source>Bull World Health Organ</source>
          <year>2020</year>
          <volume>98</volume>
          <issue>4</issue>
          <fpage>251</fpage>
          <lpage>256</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32284648"/>
          </comment>
          <pub-id pub-id-type="doi">10.2471/BLT.19.237487</pub-id>
          <pub-id pub-id-type="medline">32284648</pub-id>
          <pub-id pub-id-type="pii">BLT.19.237487</pub-id>
          <pub-id pub-id-type="pmcid">PMC7133468</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dufour</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Fadel</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gelée</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Dubost</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>Ardiot</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Di Donato</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Ricard</surname>
              <given-names>JD</given-names>
            </name>
          </person-group>
          <article-title>When a ventilator takes autonomous decisions without seeking approbation nor warning clinicians: a case series</article-title>
          <source>Int Med Case Rep J</source>
          <year>2020</year>
          <volume>13</volume>
          <fpage>521</fpage>
          <lpage>529</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33116944"/>
          </comment>
          <pub-id pub-id-type="doi">10.2147/IMCRJ.S266969</pub-id>
          <pub-id pub-id-type="medline">33116944</pub-id>
          <pub-id pub-id-type="pii">266969</pub-id>
          <pub-id pub-id-type="pmcid">PMC7571577</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Straw</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Investigating for bias in healthcare algorithms: a sex-stratified analysis of supervised machine learning models in liver disease prediction</article-title>
          <source>BMJ Health Care Inform</source>
          <year>2022</year>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>e100457</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://informatics.bmj.com/lookup/pmidlookup?view=long&amp;pmid=35470133"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjhci-2021-100457</pub-id>
          <pub-id pub-id-type="medline">35470133</pub-id>
          <pub-id pub-id-type="pii">bmjhci-2021-100457</pub-id>
          <pub-id pub-id-type="pmcid">PMC9039354</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Sylolypavan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wild</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Quantifying health inequalities induced by data and AI models</source>
          <year>2022</year>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ijcai.org/proceedings/2022/721">https://www.ijcai.org/proceedings/2022/721</ext-link>
          </comment>
        </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>Obermeyer</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Powers</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Vogeli</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mullainathan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Dissecting racial bias in an algorithm used to manage the health of populations</article-title>
          <source>Science</source>
          <year>2019</year>
          <volume>366</volume>
          <issue>6464</issue>
          <fpage>447</fpage>
          <lpage>453</lpage>
          <pub-id pub-id-type="doi">10.1126/science.aax2342</pub-id>
          <pub-id pub-id-type="medline">31649194</pub-id>
          <pub-id pub-id-type="pii">366/6464/447</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>Straw</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>The automation of bias in medical artificial intelligence (AI): decoding the past to create a better future</article-title>
          <source>Artif Intell Med</source>
          <year>2020</year>
          <volume>110</volume>
          <fpage>101965</fpage>
          <pub-id pub-id-type="doi">10.1016/j.artmed.2020.101965</pub-id>
          <pub-id pub-id-type="medline">33250145</pub-id>
          <pub-id pub-id-type="pii">S0933-3657(20)31230-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="book">
          <source>We are electric: the new science of our body's electrome</source>
          <year>2023</year>
          <publisher-loc>UK</publisher-loc>
          <publisher-name>Canongate Books</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <source>Exploring biodigital convergence : what happens when biology and digital technology merge?</source>
          <year>2020</year>
          <access-date>2023-10-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://horizons.gc.ca/wp-">https://horizons.gc.ca/wp-</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <article-title>Medical technology strategy</article-title>
          <source>UK Government</source>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.gov.uk/government/publications/medical-technology-strategy/medical-technology-strategy">https://www.gov.uk/government/publications/medical-technology-strategy/medical-technology-strategy</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Brass</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Straw</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Mkwashi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Charles</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Soares</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Steer</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Emerging digital technologies in patient care: dealing with connected, intelligent medical device vulnerabilities and failures in the healthcare sector</article-title>
          <source>Workshop Report</source>
          <year>2023</year>
          <conf-name>PETRAS National Centre of Excellence in IoT Systems Cybersecurity</conf-name>
          <conf-date>June 6 2023</conf-date>
          <conf-loc>London</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://zenodo.org/record/8011139"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharma</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Outdated IoT healthcare devices pose major security threats</article-title>
          <source>CSO Online</source>
          <access-date>2024-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.csoonline.com/article/3648592/outdated-iot-healthcare-devices-pose-major-security-threats.html">https://www.csoonline.com/article/3648592/outdated-iot-healthcare-devices-pose-major-security-threats.html</ext-link>
          </comment>
        </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>Awad</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Trenfield</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Pollard</surname>
              <given-names>TD</given-names>
            </name>
            <name name-style="western">
              <surname>Ong</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Elbadawi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>McCoubrey</surname>
              <given-names>LE</given-names>
            </name>
            <name name-style="western">
              <surname>Goyanes</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Gaisford</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Basit</surname>
              <given-names>AW</given-names>
            </name>
          </person-group>
          <article-title>Connected healthcare: improving patient care using digital health technologies</article-title>
          <source>Adv Drug Deliv Rev</source>
          <year>2021</year>
          <volume>178</volume>
          <fpage>113958</fpage>
          <pub-id pub-id-type="doi">10.1016/j.addr.2021.113958</pub-id>
          <pub-id pub-id-type="medline">34478781</pub-id>
          <pub-id pub-id-type="pii">S0169-409X(21)00351-3</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>Mitchell</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kan</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Digital technology and the future of health systems</article-title>
          <source>Health Syst Reform</source>
          <year>2019</year>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>113</fpage>
          <lpage>120</lpage>
          <pub-id pub-id-type="doi">10.1080/23288604.2019.1583040</pub-id>
          <pub-id pub-id-type="medline">30908111</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Coravos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Corman</surname>
              <given-names>JD</given-names>
            </name>
          </person-group>
          <article-title>The case for a hippocratic oath for connected medical devices: viewpoint</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>e12568</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/3/e12568/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12568</pub-id>
          <pub-id pub-id-type="medline">30888323</pub-id>
          <pub-id pub-id-type="pii">v21i3e12568</pub-id>
          <pub-id pub-id-type="pmcid">PMC6444210</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>NHS England</collab>
          </person-group>
          <source>Clinical guidelines for major incidents and mass casualty events</source>
          <access-date>2023-05-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.england.nhs.uk/publication/clinical-guidelines-for-major-incidents-and-mass-casualty-events/">https://www.england.nhs.uk/publication/clinical-guidelines-for-major-incidents-and-mass-casualty-events/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
