<?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">
<?covid-19-tum?>
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JFR</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id>
      <journal-title>JMIR Formative Research</journal-title>
      <issn pub-type="epub">2561-326X</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">v7i1e38555</article-id>
      <article-id pub-id-type="pmid">36649223</article-id>
      <article-id pub-id-type="doi">10.2196/38555</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>mHealth App to Facilitate Remote Care for Patients With COVID-19: Rapid Development of the DrCovid+ App</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kwan</surname>
            <given-names>Yu Heng</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Tian</surname>
            <given-names>Yu</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chaudhry</surname>
            <given-names>Beenish</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>Jamaica Pei Ying</given-names>
          </name>
          <degrees>MPH</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2373-4747</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>Michelle W J</given-names>
          </name>
          <degrees>MMed</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <xref rid="aff02" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0766-2501</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Towle</surname>
            <given-names>Rachel Marie</given-names>
          </name>
          <degrees>DNP</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <xref rid="aff03" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5266-7574</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Joanne Sze Win</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9133-0379</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Lei</surname>
            <given-names>Xiaofeng</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff04" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9290-9198</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Liu</surname>
            <given-names>Yong</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff04" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1590-2029</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Goh</surname>
            <given-names>Rick Siow Mong</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff04" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9116-1595</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Chee Ping</surname>
            <given-names>Franklin Tan</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff05" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8991-7645</ext-link>
        </contrib>
        <contrib id="contrib9" contrib-type="author">
          <name name-style="western">
            <surname>Tan</surname>
            <given-names>Teck Choon</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff05" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4746-5668</ext-link>
        </contrib>
        <contrib id="contrib10" contrib-type="author">
          <name name-style="western">
            <surname>Ting</surname>
            <given-names>Daniel Shu Wei</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff06" ref-type="aff">6</xref>
          <xref rid="aff07" ref-type="aff">7</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2264-7174</ext-link>
        </contrib>
        <contrib id="contrib11" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Chen Ee</given-names>
          </name>
          <degrees>MBA, MA</degrees>
          <xref rid="aff08" ref-type="aff">8</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1237-6377</ext-link>
        </contrib>
        <contrib id="contrib12" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Low</surname>
            <given-names>Lian Leng</given-names>
          </name>
          <degrees>MMed</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <address>
            <institution>Population Health and Integrated Care Office</institution>
            <institution>Singapore General Hospital</institution>
            <addr-line>10 Hospital Boulevard, SingHealth Tower Level 7</addr-line>
            <addr-line>Singapore, 168582</addr-line>
            <country>Singapore</country>
            <phone>65 69703018</phone>
            <email>low.lian.leng@singhealth.com.sg</email>
          </address>
          <xref rid="aff02" ref-type="aff">2</xref>
          <xref rid="aff09" ref-type="aff">9</xref>
          <xref rid="aff10" ref-type="aff">10</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4228-2862</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff01">
        <label>1</label>
        <institution>Population Health and Integrated Care Office</institution>
        <institution>Singapore General Hospital</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff02">
        <label>2</label>
        <institution>Family Medicine and Continuing Care</institution>
        <institution>Singapore General Hospital</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff03">
        <label>3</label>
        <institution>Nursing</institution>
        <institution>Singapore General Hospital</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff04">
        <label>4</label>
        <institution>Institute of High Performance Computing</institution>
        <institution>Agency for Science, Technology and Research</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff05">
        <label>5</label>
        <institution>Office for Service Transformation</institution>
        <institution>Singapore Health Services</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff06">
        <label>6</label>
        <institution>Department of Ophthalmology</institution>
        <institution>Singapore National Eye Centre</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff07">
        <label>7</label>
        <institution>Duke-NUS Medical School</institution>
        <institution>National University of Singapore</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff08">
        <label>8</label>
        <institution>Innovation and Transformation</institution>
        <institution>Singapore Health Services</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff09">
        <label>9</label>
        <institution>Outram Community Hospital</institution>
        <institution>SingHealth Community Hospitals</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <aff id="aff10">
        <label>10</label>
        <institution>Centre for Population Health Research and Implementation</institution>
        <institution>SingHealth Regional Health System</institution>
        <addr-line>Singapore</addr-line>
        <country>Singapore</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Lian Leng Low <email>low.lian.leng@singhealth.com.sg</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>7</day>
        <month>2</month>
        <year>2023</year>
      </pub-date>
      <volume>7</volume>
      <elocation-id>e38555</elocation-id>
      <history>
        <date date-type="received">
          <day>3</day>
          <month>5</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>14</day>
          <month>10</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>23</day>
          <month>12</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>10</day>
          <month>1</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Jamaica Pei Ying Tan, Michelle W J Tan, Rachel Marie Towle, Joanne Sze Win Lee, Xiaofeng Lei, Yong Liu, Rick Siow Mong Goh, Franklin Tan Chee Ping, Teck Choon Tan, Daniel Shu Wei Ting, Chen Ee Lee, Lian Leng Low. Originally published in JMIR Formative Research (https://formative.jmir.org), 07.02.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on https://formative.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://formative.jmir.org/2023/1/e38555" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The 2019 novel COVID-19 has severely burdened the health care system through its rapid transmission. Mobile health (mHealth) is a viable solution to facilitate remote monitoring and continuity of care for patients with COVID-19 in a home environment. However, the conceptualization and development of mHealth apps are often time and labor-intensive and are laden with concerns relating to data security and privacy. Implementing mHealth apps is also a challenging feat as language-related barriers limit adoption, whereas its perceived lack of benefits affects sustained use. The rapid development of an mHealth app that is cost-effective, secure, and user-friendly will be a timely enabler.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This project aimed to develop an mHealth app, <italic>DrCovid+</italic>, to facilitate remote monitoring and continuity of care for patients with COVID-19 by using the rapid development approach. It also aimed to address the challenges of mHealth app adoption and sustained use.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The Rapid Application Development approach was adopted. Stakeholders including decision makers, physicians, nurses, health care administrators, and research engineers were engaged. The process began with requirements gathering to define and finalize the project scope, followed by an iterative process of developing a working prototype, conducting User Acceptance Tests, and improving the prototype before implementation. Co-designing principles were applied to ensure equal collaborative efforts and collective agreement among stakeholders.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p><italic>DrCovid+</italic> was developed on Telegram Messenger and hosted on a cloud server. It features a secure patient enrollment and data interface, a multilingual communication channel, and both automatic and personalized push messaging. A back-end dashboard was also developed to collect patients’ vital signs for remote monitoring and continuity of care. To date, 400 patients have been enrolled into the system, amounting to 2822 hospital bed–days saved.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The rapid development and implementation of <italic>DrCovid+</italic> allowed for timely clinical care management for patients with COVID-19. It facilitated early patient hospital discharge and continuity of care while addressing issues relating to data security and labor-, time-, and cost-effectiveness. The use case for <italic>DrCovid+</italic> may be extended to other medical conditions to advance patient care and empowerment within the community, thereby meeting existing and rising population health challenges.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>mobile health</kwd>
        <kwd>mHealth</kwd>
        <kwd>rapid development</kwd>
        <kwd>remote care</kwd>
        <kwd>COVID-19</kwd>
        <kwd>hospital-at-home</kwd>
        <kwd>mobile app</kwd>
        <kwd>app development</kwd>
        <kwd>virtual care</kwd>
        <kwd>Telegram service</kwd>
        <kwd>clinical care</kwd>
        <kwd>continuity of care</kwd>
        <kwd>digital health</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The 2019 novel COVID-19 is an infectious disease resulting from the severe acute respiratory syndrome coronavirus 2 [<xref ref-type="bibr" rid="ref1">1</xref>]. Declared by the World Health Organization as a pandemic, COVID-19 has both high transmissibility and case fatality rates with more than 250 million reported cases and 5.1 million deaths recorded globally [<xref ref-type="bibr" rid="ref2">2</xref>]. This has severely burdened the existing health care system by posing additional health care demands; requiring the diversion of resources to diagnose, quarantine, and treat cases; disrupting medical supply chains; and causing a personnel crunch [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
      <p>Current evidence suggests that approximately 80% of patients with COVID-19 experienced mild clinical symptoms suitable for home recovery [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. However, widespread concern surrounding the uncertainty of its pathology and symptoms has resulted in a surge of demand for hospital care [<xref ref-type="bibr" rid="ref6">6</xref>]. Notwithstanding, at the beginning of the outbreak, hospitals were being used to isolate patients with COVID-19 who were unable to effectively isolate themselves at home, further exerting pressure on global health care resources and systems [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. This called for a sustainable solution to alleviate demands for institutional care for COVID-19 through early inpatient discharge and home isolation while ensuring continuity of care for patients.</p>
      <p>Mobile Health (mHealth) is gaining traction as a promising way to advance remote and continuous care during the COVID-19 pandemic [<xref ref-type="bibr" rid="ref8">8</xref>]. Equipped with various communication features, such as instant text messages and voice and video calls, mHealth allows for telemedicine via real-time individual or group communication [<xref ref-type="bibr" rid="ref9">9</xref>]. Patients can continue to receive standard clinical care while reducing physical crowding in hospital premises. Likewise, clinicians can provide remote care while minimizing exposure to COVID-19 [<xref ref-type="bibr" rid="ref10">10</xref>]. Moreover, the use of artificial intelligence in mHealth can potentially alleviate existing clinical loads while ensuring optimal care for patients [<xref ref-type="bibr" rid="ref11">11</xref>]. For instance, mobile artificial intelligence apps such as <italic>Babylon Health</italic> offers around-the-clock digital tools to help patients monitor their health, obtain health information instantly, and schedule appointments and video calls with clinicians [<xref ref-type="bibr" rid="ref12">12</xref>]. Chatbots, such as <italic>BotMD</italic>, allow clinicians to have 24/7 access to instant information on drugs, hospital protocols, and clinical tools [<xref ref-type="bibr" rid="ref13">13</xref>]. Tele-social apps have also been developed to allow for remote patient monitoring and education for patients with COVID-19 [<xref ref-type="bibr" rid="ref11">11</xref>]. For example, in Singapore, <italic>Doctor Covid,</italic> a chatbot developed on Telegram Messenger, was developed to cater to the country’s multiethnic culture through multilingual capabilities. It can also broadcast critical information and reminders to patients and provide clinical and psychosocial surveillance [<xref ref-type="bibr" rid="ref14">14</xref>]. This serves to facilitate timely and effective information dissemination and provide remote clinical and social care digitally. Taken together, mHealth apps offer an unprecedented opportunity for remote monitoring and continuity of care and the potential to alleviate existing pressure on hospitals’ resources exacerbated by the COVID-19 pandemic [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      <p>Attempts to use technology for pandemic response and continuity of care for patients with COVID-19 have been met with various challenges. First, the development of innovations is both costly and labor-intensive. With the high transmission rate of COVID-19, many health care resources were diverted to impede the further spread of the virus, leaving little to invest in innovative solutions to support remote care [<xref ref-type="bibr" rid="ref16">16</xref>]. Second, the use of innovations is laden with concerns relating to data security and privacy, thus often requiring a state-of-art secure platform to preserve the integrity of the highly protected patient information and may not be feasible in resource-limited countries [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. Third, communication-related barriers such as poor language and digital literacy and the potential breakdown of patient-provider communication may impede the uptake of innovations [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Collectively, although it is essential to develop an mHealth app for remote and continuity of care for patients with COVID-19, it is imperative to ensure cost and time efficiency, security, and intuitiveness with sustained engagement and use by the patients.</p>
      <p>We aimed to rapidly develop a tele-social app to facilitate the remote monitoring and continuity of care for patients with COVID-19. This paper describes the rapid development process and the app prototype. We will also critically reflect on the development process and the potential expansion of its use case for the wider population.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Design</title>
        <p>The conceptualization of the tele-social app began in September 2021 at the Singapore General Hospital (SGH). It stemmed from the Singapore Ministry of Health’s effort to facilitate the COVID-19 Home Recovery Programme [<xref ref-type="bibr" rid="ref22">22</xref>], an initiative in Singapore where eligible patients with COVID-19 who have mild to no symptoms were to self-isolate and receive remote care from home. The app was designed to complement the health services in the SGH COVID Virtual Ward (CVW) program, where medically complex patients with COVID-19 who would otherwise isolate in an acute hospital receive remote care and recover at home. To implement the app effectively and efficiently, the Rapid Application Development (RAD) process was adopted (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The RAD emphasized an incremental and prototyping approach wherein the continual engagement of stakeholders to obtain user feedback contributes to the generation of further discussion for enhancement; this process continues until a satisfactory system is attained [<xref ref-type="bibr" rid="ref23">23</xref>]. Collectively, the RAD aims to develop cost-effective yet high-quality innovations in a short duration [<xref ref-type="bibr" rid="ref23">23</xref>].</p>
        <p>The project began with the preparatory phase, where stakeholders engaged in discussions to scope the project. The RAD process then took place with a series of requirements gathering sessions with the relevant stakeholders to define and finalize the project requirements, including the project goals and expectations, timeline, and budget. This information was communicated to research engineers from the Agency for Science, Technology, and Research (A*STAR) for the initial prototype development, followed by an iterative process of User Acceptance Tests and improvement works with key stakeholders before the actual development and implementation.</p>
        <p>Co-designing principles were applied throughout the RAD process. Key stakeholders were encouraged to participate actively to understand their needs, opinions, and experiences to ensure the app’s usability and relevance [<xref ref-type="bibr" rid="ref24">24</xref>] and were respected as equal collaborators, sharing their expertise and having an agreement on the eventual product [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>].</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Rapid Application Development process.</p>
          </caption>
          <graphic xlink:href="formative_v7i1e38555_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Recruitment</title>
        <p>Stakeholder engagement began in September 2021. Interdisciplinary and multiprofessional stakeholders—including decision makers, physicians, nurses, and health care administrators operating the SGH CVW and SGH Hospital-at-Home program (a home-hospital program designed to encourage early inpatient discharge and home care)—were invited to join the project team to leverage their knowledge and expertise in home care for patients. Local research engineers from A*STAR, who had prior skills and knowledge in developing the <italic>Doctor Covid</italic> chatbot [<xref ref-type="bibr" rid="ref14">14</xref>], were also engaged to assist with the designing and development of this mHealth app.</p>
      </sec>
      <sec>
        <title>Data Collection and Analysis</title>
        <p>The RAD process involved constant iterations of discussions to capture the requirements, needs, and opinions of key stakeholders. These sessions were conducted via a web-based videoconference platform, Zoom (Zoom Video Communications), in a work group meeting format. <xref ref-type="table" rid="table1">Table 1</xref> documents the overview of the discussions, key questions, and outcomes held throughout the RAD phases. All key points were recorded on pen and paper and simultaneously analyzed by 2 research engineers from A*STAR at the end of each work group meeting to facilitate the rapid development. Thematic analysis methodology was adopted wherein similar points were identified and grouped to form themes that informed the features to be included in the mHealth app [<xref ref-type="bibr" rid="ref27">27</xref>]. This was followed by a series of discussions within the team on the feasibility (ie, whether the feature can be built with existing skills, technology, and time), usability (ie, how user-friendly the features are), and viability (ie, if the feature can be scaled and operated on other similar apps) of the ideas [<xref ref-type="bibr" rid="ref28">28</xref>].</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Overview of Rapid Application Development (RAD) discussions.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="180"/>
            <col width="200"/>
            <col width="220"/>
            <col width="370"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Phase, session, and format</td>
                <td>Objectives</td>
                <td>Key questions</td>
                <td>Outputs</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Preparatory phase</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Sessions 1 and 2 (October 6 and 11, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Conceptualize requirements for the app</p>
                    </list-item>
                    <list-item>
                      <p>Understand the existing use case and explore the enhancement of Doctor Covid to meet the current needs</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>What are the existing pain points in the workflow processes?</p>
                    </list-item>
                    <list-item>
                      <p>What are these pain points that can be addressed by digital tools?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>A shared understanding of the basic requirements for the tele-social app</p>
                    </list-item>
                    <list-item>
                      <p>A shared understanding of the use case of Doctor Covid</p>
                    </list-item>
                    <list-item>
                      <p>The decision to enhance the use case of Doctor Covid for the current project</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Phase 1 (requirements gathering)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 3 (October 18, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Key stakeholders meeting to deep dive into specific user requirements</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>What are the specific requirements of users?</p>
                    </list-item>
                    <list-item>
                      <p>What are some important considerations in the app (eg, data security and usability)?</p>
                    </list-item>
                    <list-item>
                      <p>How and by who is the system being used?</p>
                    </list-item>
                    <list-item>
                      <p>What are the patient’s health parameters to track?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Confirmation of digital platform to be leveraged:</p>
                      <list>
                        <list-item>
                          <p>
                    Telegram Messenger
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Back-end user dashboard
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                    <list-item>
                      <p>Preliminary user requirements:</p>
                      <list>
                        <list-item>
                          <p>
                    Automatic push messaging function to communicate medically related information
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Platform for patients’ daily vital signs uploads
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    User dashboard for health care providers to track patients’ daily vital signs, vaccination status, duration of isolation, discharge date, polymerase chain reaction status, meeting details, and health care provider in charge
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Security features (eg, secure enrollment and messaging and eligibility requirements)
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 4 (October 19, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Discuss the patient onboarding process</p>
                    </list-item>
                    <list-item>
                      <p>Further discussion on the user requirements</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>What is the patient flow process?</p>
                    </list-item>
                    <list-item>
                      <p>What are some key considerations in remote monitoring?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>A shared agreement on the patient workflow (see <xref rid="figure1" ref-type="fig">Figure 1</xref>)</p>
                    </list-item>
                    <list-item>
                      <p>Additional user requirements:</p>
                      <list>
                        <list-item>
                          <p>
                    Automatic push reminders to alert patients to upload daily vital signs
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 5 (October 21, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Presentation of mock-up dashboard by A*STAR<sup>a</sup></p>
                    </list-item>
                    <list-item>
                      <p>Further discussion on the user requirements</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>How are patients’ data being tracked and stored?</p>
                    </list-item>
                    <list-item>
                      <p>What are some other user requirements?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Additional user’s requirements:</p>
                      <list>
                        <list-item>
                          <p>
                    Dashboard: enable sorting of patient lists according to demographic variables and a color-coding system to highlight abnormal patients’ vital signs
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Telegram services: multilingual options
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Logistics: types of educational videos to be shared with patients
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Phase 2a (developing a working prototype)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 6 (October 22, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Confirmation of messaging templates, issuing of administrative accounts, and scheduling of UAT<sup>b</sup> dates</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>What is your feedback on the translated messaging template?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Messaging templates (eg, onboarding instructions) were confirmed</p>
                    </list-item>
                    <list-item>
                      <p>Administrators were issued a testing account</p>
                    </list-item>
                    <list-item>
                      <p>Confirmation of UAT dates</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Phase 2b (UAT)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 7 (October 29, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>UAT</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>What are your feedbacks about the prototype?</p>
                    </list-item>
                    <list-item>
                      <p>How do you think this can be further improved?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feedback for improvements from the UAT:</p>
                      <list>
                        <list-item>
                          <p>
                    Dashboard: include an overview of the patient list with the total number of patients enrolled and include an export function for patient data
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Telegram services: messaging reminder timings to be revised
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Phase 2c (improvement works)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 8 (November 2, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Presentation of improvement works based on feedback received from the UAT</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Users to provide any feedbacks</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Confirmation of working prototype</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Phase 3 (development and implementation)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 9 (November 5, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Go live session</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>N/A<sup>c</sup></p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>N/A</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 10 (November 8, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>User’s feedback session</p>
                    </list-item>
                    <list-item>
                      <p>Discussion of new features</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Is there any feedback on the app after initial implementation?</p>
                    </list-item>
                    <list-item>
                      <p>What are some new features that are good to have for the next phase?</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>User’s feedback:</p>
                      <list>
                        <list-item>
                          <p>
                    Color-coding of patients’ vital signs may not accurately reflect the patient’s existing health status
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                    <list-item>
                      <p>New features:</p>
                      <list>
                        <list-item>
                          <p>
                    Dashboard: include a read-only function to prevent unnecessary edits made to the dashboard, color-coding system for nonmandatory patient vital signs, and a password option in the user log-in platform
                  </p>
                        </list-item>
                        <list-item>
                          <p>
                    Telegram services: include pop-up messages
                  </p>
                        </list-item>
                      </list>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 11 (November 8, 2021); group meetings</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Upgraded go-live version to be released</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>N/A</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>N/A</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>A*STAR: Agency for Science, Technology and Research.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>UAT: User Acceptance Test.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>N/A: not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>No ethics review was required for the project as no patients were involved in the design and development of the app. Only health care personnel (ie, physicians, nurses, and health care administrators) and software engineers were involved throughout the process. Moreover, the <italic>DrCovid+</italic> app was incorporated as part of an established home care program (ie, SGH CVW) to provide complementary remote care to patients with COVID-19 and is not part of a human subject research study. The privacy and confidentiality of patient data were ensured, with these data collected only for routine patient care purposes.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>Through a systematic and iterative RAD approach, <italic>DrCovid+</italic>, an expansion of the <italic>Doctor Covid</italic> use case [<xref ref-type="bibr" rid="ref14">14</xref>], was developed. Decision makers, physicians, nurses, health care administrators, and research engineers were involved in the RAD process. <xref ref-type="table" rid="table2">Table 2</xref> shows the demographics of the stakeholders involved.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Participant information.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="330"/>
            <col width="0"/>
            <col width="150"/>
            <col width="0"/>
            <col width="330"/>
            <col width="0"/>
            <col width="160"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Phase, session, and format</td>
                <td colspan="2">Sample size, n</td>
                <td colspan="2">Profession</td>
                <td>Institution</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="8">
                  <bold>Preparatory phase</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Sessions 1 and 2; group meetings (via Zoom)</td>
                <td colspan="2">18</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Decision makers (n=3)</p>
                    </list-item>
                    <list-item>
                      <p>Physicians (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=3)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR<sup>a</sup>, OST<sup>b</sup>, SHP<sup>c</sup>, and SGH<sup>d</sup> HaH<sup>e</sup> team</td>
              </tr>
              <tr valign="top">
                <td colspan="8">
                  <bold>Phase 1 (requirements gathering)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 3; group meetings (via Zoom)</td>
                <td colspan="2">5</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Nurse (n=1)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=2)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 4; group meetings (via Zoom)</td>
                <td colspan="2">11</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physician (n=1)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=3)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 5; group meetings (via Zoom)</td>
                <td colspan="2">9</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=2)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td colspan="8">
                  <bold>Phase 2a (developing a working prototype)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 6; group meetings (via Zoom)</td>
                <td colspan="2">10</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physicians (n=2)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=2)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=4)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td colspan="8">
                  <bold>Phase 2b (UAT<sup>f</sup>)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 7; group meetings (via Zoom)</td>
                <td colspan="2">14</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physicians (n=2)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=4)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=3)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td colspan="8">
                  <bold>Phase 2c (improvement works)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 8; group meetings (via Zoom)</td>
                <td colspan="2">14</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physician (n=1)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=4)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=4)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td colspan="8">
                  <bold>Phase 3 (development and implementation)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 9; group meetings (via Zoom)</td>
                <td colspan="2">17</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physicians (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=6)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=4)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 10; group meetings (via Zoom)</td>
                <td colspan="2">13</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physicians (n=2)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=4)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Session 11; group meetings (via Zoom)</td>
                <td colspan="2">14</td>
                <td colspan="2">
                  <list list-type="bullet">
                    <list-item>
                      <p>Physicians (n=3)</p>
                    </list-item>
                    <list-item>
                      <p>Nurses (n=5)</p>
                    </list-item>
                    <list-item>
                      <p>Health care administrators (n=4)</p>
                    </list-item>
                    <list-item>
                      <p>Research engineers (n=2)</p>
                    </list-item>
                  </list>
                </td>
                <td colspan="2">A*STAR, OST, and SGH HaH team</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>A*STAR: Agency for Science, Technology and Research.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>OST: Office for Service Transformation.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>SHP: SingHealth Polyclinic.</p>
            </fn>
            <fn id="table2fn4">
              <p><sup>d</sup>SGH: Singapore General Hospital.</p>
            </fn>
            <fn id="table2fn5">
              <p><sup>e</sup>HaH: Hospital-at-Home.</p>
            </fn>
            <fn id="table2fn6">
              <p><sup>f</sup>UAT: User Acceptance Test.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Phase 1 of the RAD Process: Requirements Gathering</title>
        <p>The project scope, key requirements and challenges were gathered in phase 1.</p>
        <p>Given the widespread transmission and the need for close medical attention for patients with COVID-19, <italic>DrCovid+</italic> had to be developed and implemented efficiently and effectively. To achieve this, collaborative decisions were made to develop <italic>DrCovid+</italic> through an expansion of the <italic>Doctor Covid</italic> use case and to incorporate <italic>DrCovid+</italic> into the established work processes of the SGH CVW (<xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Overview of the Singapore General Hospital COVID Virtual Ward (SGH CVW) workflow.</p>
          </caption>
          <graphic xlink:href="formative_v7i1e38555_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>Three priorities were highlighted in phase 1. First, <italic>DrCovid+</italic> would have to be translated into a functional and acceptable prototype, suitable for older adults who were expected to form the majority of the patients in SGH CVW. Second, <italic>DrCovid+</italic> should serve as a remote monitoring app where patients would perform self-reporting of daily vital signs through a web link. Adherence to self-reporting was hence essential and had to be achieved without increasing the existing workload of health care providers. Third, health care providers should be informed at a glance of patients’ latest health status and be able to provide timely follow-up actions where necessary. This resulted in a prototype featuring a multilingual secure communication platform for the remote monitoring and timely dissemination of clinical and social interventions for patients with COVID-19.</p>
      </sec>
      <sec>
        <title>Phase 2 of the RAD process: User Design</title>
        <sec>
          <title>Overview</title>
          <p><italic>DrCovid+</italic> consists of 2 broad components: an interactive channel where information exchange can occur between the patient and the health care provider via a tele-social app, Telegram Messenger; and a back-end dashboard where health care providers track patients’ health data and send push messages. The app features a secure enrollment platform, automatic push messaging of health reminders and scheduling of web-based conferences, personalized push messaging, and a back-end patient monitoring system.</p>
          <p>Telegram Messenger was chosen because of its widespread and ease of use by patients, coupled with its privacy and encryption capabilities and its open-source application programming interface [<xref ref-type="bibr" rid="ref29">29</xref>]. In addition, Telegram Messenger allows for the flexible customization of bots that facilitates the ease of modification and communication between users and from users to computers. Notwithstanding, Telegram IDs that are unique to users also facilitate the identification of patients without the need to collect patient’s mobile numbers, thereby reducing the risk of information leakage. Moreover, data collected through Telegram Messenger are not integrated with the hospital’s electronic medical records to minimize the risk of data linkages.</p>
          <p>The app and back-end servers are hosted on a commercially available cloud server, Amazon Web Services. As the cloud server is readily available, it can be deployed efficiently, and the content and storage can be scaled easily to meet the actual demands without the need to invest in physical infrastructure, which can be costly and time intensive. In addition, security measures are improved with the data security services provided by the commercial cloud vendor (eg, Web application firewire). Notwithstanding, data can be backed up and recovered effectively and efficiently on a cloud storage compared to on-premises storage [<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        </sec>
        <sec>
          <title>Enrollment</title>
          <p>To overcome data security issues, eligible patients enrolled in the project are required to register for <italic>DrCovid+</italic> via FormSG, a Singapore government–led web-based data collection form for public officers’ use to preserve the integrity of all patient data [<xref ref-type="bibr" rid="ref30">30</xref>]. Patients are only required to register for enrollment with the last 4 characters of their National Registration Identity Card number and their last name (<xref rid="figure3" ref-type="fig">Figure 3</xref>) for data security purposes. Upon registration, nurses are required to verify and confirm the patient’s enrollment via a corresponding dashboard (<xref rid="figure4" ref-type="fig">Figure 4</xref>).</p>
          <p>Patients who successfully registered for <italic>DrCovid+</italic> will receive a welcome message through the Telegram app with an automatic prompt to select their preferred communication language. This caters to the multiethnic population as health care providers can tailor messages in a language best understood by the patients (<xref rid="figure5" ref-type="fig">Figure 5</xref>).</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Registration for <italic>DrCovid</italic>+ via FormSG. FIN: Foreign Identification Number; NRIC: National Registration Identity Card; SGH: Singapore General Hospital.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Dashboard for verification and confirmation of enrollment. NRIC: National Registration Identity Card.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure5" position="float">
            <label>Figure 5</label>
            <caption>
              <p>Welcome message on <italic>DrCovid</italic>+. SGH: Singapore General Hospital.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Telegram Services App Interface—Automatic Push Messaging</title>
          <p><italic>DrCovid+</italic> serves as a remote monitoring app by prompting patients to measure and report their vital signs daily. An automatic push messaging function on Telegram Messenger is used to send regular reminders at 8 AM, 12 PM, and 4:30 PM to remind patients to monitor and submit the following vital signs through a Home Monitoring Form (<xref rid="figure6" ref-type="fig">Figures 6</xref> and <xref rid="figure7" ref-type="fig">7</xref>): body temperature, heart rate, oxygen level, and blood pressure. The reminders are automatically triggered 30 minutes before the submission time. The care team’s contact information is also included in the reminders, should patients have any queries or concerns. Collectively, this reduced the need for manual prompting from health care providers while ensuring adherence to medical instructions.</p>
          <fig id="figure6" position="float">
            <label>Figure 6</label>
            <caption>
              <p>Reminder push message for vital signs submission. SGH: Singapore General Hospital.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure7" position="float">
            <label>Figure 7</label>
            <caption>
              <p>Vital sign updating form on FormSG. NRIC: National Registration Identity Card.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Back-end Dashboard—Patient Monitoring System</title>
          <p>Patients’ daily submissions of vital sign readings are sent to a back-end cloud dashboard, monitored by health care providers. The dashboard captures patients’ vital signs and is embedded with logic to highlight abnormal readings in yellow or red, whereas normal and nonmandatory readings are highlighted in green and grey, respectively. This allows for ease of interpretation and timely follow-up actions by the health care providers (<xref rid="figure8" ref-type="fig">Figure 8</xref>).</p>
          <fig id="figure8" position="float">
            <label>Figure 8</label>
            <caption>
              <p>Clinician dashboard for patient's vital signs tracking. BP: blood pressure; HR: heart rate; I/C: in charge; NRIC: National Registration Identity Card; SPO2: oxygen saturation.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Back-end Dashboard—Personalized Push Messaging</title>
          <p>As part of the SGH CVW workflow, patients are engaged in 2 to 3 daily web-based consultations with their health care providers. This requires scheduling of web-based consultations and sending the meeting details to the patients. Moreover, health care providers may also need to convey tailored messages or multimedia documents to patients. The back-end dashboard allows health care providers to send these tailored messages to patients at a scheduled time and frequency (<xref rid="figure9" ref-type="fig">Figures 9</xref>-<xref rid="figure12" ref-type="fig">12</xref>), hence increasing the efficiency of communication with patients and decreasing the workload of health care providers.</p>
          <fig id="figure9" position="float">
            <label>Figure 9</label>
            <caption>
              <p>(Test message) Interface for drafting tailored messages.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig9.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure10" position="float">
            <label>Figure 10</label>
            <caption>
              <p>(Test message) Interface for scheduling tailored virtual meetings. NRIC: National Registration Identity Card; SGH: Singapore General Hospital.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig10.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure11" position="float">
            <label>Figure 11</label>
            <caption>
              <p>Example of a tailored message on Telegram services. SGH: Singapore General Hospital.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig11.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <fig id="figure12" position="float">
            <label>Figure 12</label>
            <caption>
              <p>Example of a scheduled ZOOM meeting on Telegram services. SGH: Singapore General Hospital.</p>
            </caption>
            <graphic xlink:href="formative_v7i1e38555_fig12.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Phase 3 of the RAD process: Development and Implementation</title>
        <p><italic>DrCovid+</italic> has been developed and incorporated into the SGH CVW workflow to complement the remote care services (<xref rid="figure2" ref-type="fig">Figure 2</xref>) since October 2021 and has enrolled 400 patients with COVID-19 to date. These are patients who would otherwise be isolated as inpatients and receive care from the hospital premises in the absence of <italic>DrCovid+</italic>. <xref ref-type="table" rid="table3">Table 3</xref> illustrates the demographics of the patients. The <italic>DrCovid+</italic> app caters to older adults who are deemed medically stable to receive remote care for their existing medical conditions beyond COVID-19. To date, 94.5% (378/400) of patients enrolled onto the <italic>DrCovid+</italic> app has been discharged, with only 5.5% (22/400) of cases being escalated due to unforeseen medical conditions such as abnormal vital signs readings or the patient having died due to other medical conditions. With <italic>DrCovid+</italic> providing complementary care to the SGH CVW workflow, this has resulted in a shorter total length of stay (LOS), despite an average LOS of 0.64 days more as compared to patients enrolled in the SGH CVW only. The LOS for patients in the <italic>DrCovid+</italic> has contributed to an equivalence of 2822 hospital bed–days saved. Additionally, the remote care capability also reduced the need for routine home visits, contributing to productivity and person-days saved.</p>
        <p>Ongoing enhancements and feedback sessions were conducted routinely to ensure the system’s reliability and usability. Although minor technical issues including downtime and crashes were recorded, these issues were escalated and rectified immediately by the research engineering support team.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Patient characteristics (n=400).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="670"/>
            <col width="300"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Characteristic</td>
                <td>Value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="2">Mean age in years (SD)</td>
                <td>51.45 (15.1)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Gender, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Male</td>
                <td>184 (46)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Female</td>
                <td>216 (54)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Case escalation<sup>a</sup> during enrollment in <italic>DrCovid+</italic>, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Yes</td>
                <td>22 (5.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>No</td>
                <td>378 (94.5)</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Total LOS<sup>b</sup> (days), n</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SGH<sup>c</sup> CVW<sup>d</sup> only</td>
                <td>3816</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SGH CVW with <italic>DrCovid+</italic></td>
                <td>2822</td>
              </tr>
              <tr valign="top">
                <td colspan="3">
                  <bold>Average LOS (days)</bold>
                  <bold>, mean (SD)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SGH CVW only</td>
                <td>6.45 (3.69)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>SGH CVW with <italic>DrCovid+</italic></td>
                <td>7.09 (3.53)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>Case escalation refers to patients who require inpatient readmission or have died.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>LOS: length of stay.</p>
            </fn>
            <fn id="table3fn3">
              <p><sup>c</sup>SGH: Singapore General Hospital.</p>
            </fn>
            <fn id="table3fn4">
              <p><sup>d</sup>CVW: COVID Virtual Ward.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>To further cope with the growing care demands of patients with COVID-19, <italic>DrCovid+</italic> was implemented at Changi General Hospital (CGH), another acute hospital in Singapore since March 2022. CGH was selected as the second site for implementation as it is an academic medical institution located in Eastern Singapore that serves a community of more than 1 million citizens in Singapore. Moreover, the process and requirements for early inpatient discharge and home care for patients with COVID-19 were similar at both CGH and SGH. The implementation process including development, vulnerability assessment test, and security assessment at CGH took only 2 weeks, highlighting the adaptability and flexibility of the app and its capacity for rapid deployment and implementation in a similar setting.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>As part of the response plan to the COVID-19 crisis in Singapore, this paper documents the RAD process of a tele-social app, <italic>DrCovid+</italic>. Equipped with essential functions such as secure tele-social communication and back-end patient monitoring, the app was codeveloped with key stakeholders to allow for timely remote monitoring and continuity of care for existing patients with COVID-19.</p>
        <p>The implementation of <italic>DrCovid+</italic> served to address many of the unprecedented challenges posed by the COVID-19 pandemic. Knowing that COVID-19 spreads predominantly through droplets, there was a need to support early hospital discharge and home recovery as the default care management model for suitable patients to minimize the spread [<xref ref-type="bibr" rid="ref31">31</xref>] without compromising the quality of care delivery. <italic>DrCovid+</italic> was developed to ensure that patients are adequately cared for remotely, with a corresponding platform to track, monitor, and communicate with patients. Moreover, given the need to divert resources to meet the needs of existing patients and curb the spread of the virus, innovative solutions to manage and care for patients had to be developed efficiently [<xref ref-type="bibr" rid="ref16">16</xref>]. <italic>DrCovid+</italic> leveraged existing program workflows and processes and the use case of <italic>Doctor Covid</italic> and its engineering team’s expertise to assist with its development and implementation. This expedited the development process, resulting in the completion of <italic>DrCovid+</italic> within a short duration. <italic>DrCovid+</italic> also serves to reduce the personnel required to care for patients. Compared to an inpatient setting where approximately 1 consultant, 5 junior doctors, and 5 nurses are required to care for 20-30 patients, the same number of health care professionals can now care for over 100 patients with such remote monitoring system [<xref ref-type="bibr" rid="ref32">32</xref>]<italic>.</italic> In addition, this can also contribute to substantial cost savings in the form of bed-days saved, hence improving issues relating to bed crunch. Notwithstanding, with any patient data storage platform, security issues must be addressed to safeguard confidential patient data. Given the need for rapid development and implementation, an elaborate and sophisticated security system may be challenging and inefficient to achieve. Nevertheless, <italic>DrCovid+</italic> has various security measures such as collecting only enrolled patients’ last names and the last 4 characters of their National Registration Identity Card number during registration, restricted access to the back-end dashboard, and manual verification for onboarded patients to minimize any possible security breaches and leakage of patient data. With a large majority of patients enrolled for SGH CVW being older adults, <italic>DrCovid+</italic> is also equipped with multilingual communication functions to prevent communication breakdown and enhance the usability of the app.</p>
        <p>mHealth solutions are gaining traction among health care professionals, especially for remote monitoring during the pandemic to manage the increasing caseloads, and this is evident from the existing literature. For instance, <italic>e-CoVig</italic>, a system featuring a mobile app, web/cloud platform, and a device for acquiring patient’s vital signs, was developed, and it allows for real-time monitoring of patients with COVID-19 without the need for direct phone calls and has demonstrated high flexibility, modularity, and accuracy and positive feedbacks from users [<xref ref-type="bibr" rid="ref33">33</xref>]. Another program, <italic>GetWellLoop</italic>, a remote patient monitoring solution consisting of patient engagement and educational materials, has also been implemented to monitor the symptoms of patients with COVID-19, send daily check-in questions and reminders, and serve as a platform for queries [<xref ref-type="bibr" rid="ref34">34</xref>]. Similar to the <italic>DrCovid+</italic> app, these programs were designed to be developed rapidly and cost-effectively, serving the needs of the population and the urgent demand for remote care amid the pandemic. However, <italic>DrCovid+</italic> is unique in that it tapped and expanded on existing resources to develop an innovation that serves existing needs. Moreover, despite the limited time frame for development and implementation, a systematic RAD process was in place to ensure that the final prototype adheres to the needs and requirements of its end users.</p>
      </sec>
      <sec>
        <title>Use Case of DrCovid+</title>
        <p>The ubiquitous nature of mobile technology coupled with the increasing acceptance of mHealth has provided new windows of opportunity to augment its use in population health. Shifting from the COVID-19 pandemic to other pressing global public health issues such as the aging population, where increasing chronic and complex health care needs are pertinent and care needs extend beyond the hospital walls [<xref ref-type="bibr" rid="ref35">35</xref>], a concerted effort has to be invested to empower patients and increase access to resources within the community to ensure a sustainable health care system [<xref ref-type="bibr" rid="ref36">36</xref>]. Tele-social apps such as <italic>DrCovid+</italic> can be a promising innovation to advance patient care and empowerment [<xref ref-type="bibr" rid="ref37">37</xref>]. Designed to ensure modularity and flexibility, the app can be tailored to suit various use cases, such as sending text reminders for vaccination or medication intake, providing health education materials, and teleconsultations [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref40">40</xref>]. This also addresses the concern on sustained engagement given that <italic>DrCovid+</italic> engages the patient on multiple fronts with different use cases. The adaptation of the use case for <italic>DrCovid+</italic> can potentially minimize unnecessary waiting time and travel expenses for clinic visits and contribute to the reduction in hospital-acquired infection [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], making it a promising way forward.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>The development and implementation of <italic>DrCovid</italic>+ had to be rapid to cope with the increasing COVID-19 caseloads. Despite this constraint, the process of developing the app used systematic RAD processes and co-designing principles such as continual engagement and taking the stance of equal collaboration to ensure the relevance and adoption of the eventual product. Regular meetings were also conducted to gather feedback and suggestions on the grounds for further modifications of the app. The current project, however, requires an evaluation of the cost-effectiveness and overall efficacy as more patients are enrolled. It will also be appropriate to assess time savings for health care providers and the difference in the characteristics of patients who onboarded the <italic>DrCovid+</italic> app compared to controls.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The impetus to provide remote care and support to the increasing home recovery of COVID-19 cases and the urgency of the COVID-19 situation prompted the need to leverage mHealth technologies and rapid deployment. However, this was met with various challenges including cost-, labor-, and time-intensive requirements in developing an app; data security issues; and poor adoption rates due to communication-related barriers. The <italic>DrCovid+</italic> app was developed to address the pressing demands for remote patient management and support the existing cost and technological bottlenecks. The rapid, cost-effective, yet strategical development of a tele-social app efficiently reaches out to a large number of patients while ensuring timely care provision, and this use case can also be scaled and expanded to meet other population health needs to tackle rising health care challenges.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">A*STAR</term>
          <def>
            <p>Agency for Science, Technology and Research</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CGH</term>
          <def>
            <p>Changi General Hospital</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CVW</term>
          <def>
            <p>COVID Virtual Ward</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">LOS</term>
          <def>
            <p>length of stay</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">RAD</term>
          <def>
            <p>Rapid Application Development</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">SGH</term>
          <def>
            <p>Singapore General Hospital</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank all the Singapore General Hospital COVID Virtual Ward and Hospital-at-Home teams for their time and valuable contributions to this project. This work was supported by the Healthy, Empowered and Active Living (HEAL) Population Health Programme Fund (03/FY2021/EX/136-A191) and Clinical &#38; Systems Innovation Support, Innovation Seed Grant (14/FY2021/P1/13-A28).</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>COVID-19</article-title>
          <source>Centers for Disease Control and Prevention</source>
          <year>2020</year>
          <access-date>2021-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/coronavirus/2019-nCoV/index.html">https://www.cdc.gov/coronavirus/2019-nCoV/index.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <article-title>Coronavirus disease (COVID-19) pandemic</article-title>
          <source>World Health Organization</source>
          <year>2021</year>
          <access-date>2021-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/emergencies/diseases/novel-coronavirus-2019">https://www.who.int/emergencies/diseases/novel-coronavirus-2019</ext-link>
          </comment>
        </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>Haleem</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Javaid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Vaishya</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Effects of COVID-19 pandemic in daily life</article-title>
          <source>Curr Med Res Pract</source>
          <year>2020</year>
          <month>03</month>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>78</fpage>
          <lpage>79</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32292804"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cmrp.2020.03.011</pub-id>
          <pub-id pub-id-type="medline">32292804</pub-id>
          <pub-id pub-id-type="pii">S2352-0817(20)30038-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC7147210</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>Bagi</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>Soleimanpour</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abdollahi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Soleimanpour</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Evaluation of clinical outcomes of patients with mild symptoms of coronavirus disease 2019 (COVID-19) discharged from the emergency department</article-title>
          <source>PLoS One</source>
          <year>2021</year>
          <month>10</month>
          <day>21</day>
          <volume>16</volume>
          <issue>10</issue>
          <fpage>e0258697</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0258697"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0258697</pub-id>
          <pub-id pub-id-type="medline">34673806</pub-id>
          <pub-id pub-id-type="pii">PONE-D-21-20101</pub-id>
          <pub-id pub-id-type="pmcid">PMC8530279</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>Wu</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>McGoogan</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Characteristics of and important lessons from the coronavirus disease 2019 (COVID-19) outbreak in China: summary of a report of 72 314 cases from the Chinese Center for Disease Control and Prevention</article-title>
          <source>JAMA</source>
          <year>2020</year>
          <month>04</month>
          <day>07</day>
          <volume>323</volume>
          <issue>13</issue>
          <fpage>1239</fpage>
          <lpage>1242</lpage>
          <pub-id pub-id-type="doi">10.1001/jama.2020.2648</pub-id>
          <pub-id pub-id-type="medline">32091533</pub-id>
          <pub-id pub-id-type="pii">2762130</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>Rees</surname>
              <given-names>EM</given-names>
            </name>
            <name name-style="western">
              <surname>Nightingale</surname>
              <given-names>ES</given-names>
            </name>
            <name name-style="western">
              <surname>Jafari</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Waterlow</surname>
              <given-names>NR</given-names>
            </name>
            <name name-style="western">
              <surname>Clifford</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>B Pearson</surname>
              <given-names>Carl A</given-names>
            </name>
            <name name-style="western">
              <surname>Group</surname>
              <given-names>CW</given-names>
            </name>
            <name name-style="western">
              <surname>Jombart</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Procter</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>GM</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 length of hospital stay: a systematic review and data synthesis</article-title>
          <source>BMC Med</source>
          <year>2020</year>
          <month>09</month>
          <day>03</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>270</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/s12916-020-01726-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12916-020-01726-3</pub-id>
          <pub-id pub-id-type="medline">32878619</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12916-020-01726-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7467845</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>Chen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhai</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Bärnighausen</surname>
              <given-names>Till</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Fangcang shelter hospitals: a novel concept for responding to public health emergencies</article-title>
          <source>Lancet</source>
          <year>2020</year>
          <month>04</month>
          <day>18</day>
          <volume>395</volume>
          <issue>10232</issue>
          <fpage>1305</fpage>
          <lpage>1314</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32247320"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(20)30744-3</pub-id>
          <pub-id pub-id-type="medline">32247320</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(20)30744-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC7270591</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>Iyengar</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Upadhyaya</surname>
              <given-names>GK</given-names>
            </name>
            <name name-style="western">
              <surname>Vaishya</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 and applications of smartphone technology in the current pandemic</article-title>
          <source>Diabetes Metab Syndr</source>
          <year>2020</year>
          <month>09</month>
          <volume>14</volume>
          <issue>5</issue>
          <fpage>733</fpage>
          <lpage>737</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32497963"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.dsx.2020.05.033</pub-id>
          <pub-id pub-id-type="medline">32497963</pub-id>
          <pub-id pub-id-type="pii">S1871-4021(20)30152-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7248636</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rouhani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Marsh</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Rimpel</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Edmond</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Julmisse</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Checkett</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Social messaging for global health: lessons from Haiti</article-title>
          <source>J Glob Health</source>
          <year>2019</year>
          <month>06</month>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>010308</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31217950"/>
          </comment>
          <pub-id pub-id-type="doi">10.7189/jogh.09.010308</pub-id>
          <pub-id pub-id-type="medline">31217950</pub-id>
          <pub-id pub-id-type="pii">jogh-09-010308</pub-id>
          <pub-id pub-id-type="pmcid">PMC6551485</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Woolliscroft</surname>
              <given-names>JO</given-names>
            </name>
          </person-group>
          <article-title>Innovation in response to the COVID-19 pandemic crisis</article-title>
          <source>Acad Med</source>
          <year>2020</year>
          <month>08</month>
          <volume>95</volume>
          <issue>8</issue>
          <fpage>1140</fpage>
          <lpage>1142</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32282372"/>
          </comment>
          <pub-id pub-id-type="doi">10.1097/ACM.0000000000003402</pub-id>
          <pub-id pub-id-type="medline">32282372</pub-id>
          <pub-id pub-id-type="pii">00001888-202008000-00023</pub-id>
          <pub-id pub-id-type="pmcid">PMC7188042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ting</surname>
              <given-names>DSW</given-names>
            </name>
            <name name-style="western">
              <surname>Carin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dzau</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>TY</given-names>
            </name>
          </person-group>
          <article-title>Digital technology and COVID-19</article-title>
          <source>Nat Med</source>
          <year>2020</year>
          <month>04</month>
          <day>27</day>
          <volume>26</volume>
          <issue>4</issue>
          <fpage>459</fpage>
          <lpage>461</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32284618"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-020-0824-5</pub-id>
          <pub-id pub-id-type="medline">32284618</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-020-0824-5</pub-id>
          <pub-id pub-id-type="pmcid">PMC7100489</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <source>Babylon Health</source>
          <year>2021</year>
          <access-date>2021-12-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.babylonhealth.com/en-us">https://www.babylonhealth.com/en-us</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <source>BotMD</source>
          <year>2021</year>
          <access-date>2021-12-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.botmd.io/en/home.html">https://www.botmd.io/en/home.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <article-title>SingHealth and A*STAR co-develop smart chatbot to enhance care for COVID-19 patients at community care facilities</article-title>
          <source>SingHealth</source>
          <year>2020</year>
          <month>06</month>
          <day>24</day>
          <access-date>2021-11-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.singhealth.com.sg/news/patient-care/doctor-covid-chatbot">https://www.singhealth.com.sg/news/patient-care/doctor-covid-chatbot</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Paglialonga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Pinto</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mugambi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Keshavjee</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Andreoni</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Perego</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Frumento</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The healthcare system perspective in mHealth</article-title>
          <source>m_Health Current and Future Applications</source>
          <year>2019</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>127</fpage>
          <lpage>142</lpage>
        </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>Houlding</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mate</surname>
              <given-names>KKV</given-names>
            </name>
            <name name-style="western">
              <surname>Engler</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ortiz-Paredes</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Pomey</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cox</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hijal</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lebouché</surname>
              <given-names>Bertrand</given-names>
            </name>
          </person-group>
          <article-title>Barriers to use of remote monitoring technologies used to support patients with COVID-19: rapid review</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2021</year>
          <month>04</month>
          <day>20</day>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>e24743</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2021/4/e24743/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24743</pub-id>
          <pub-id pub-id-type="medline">33769943</pub-id>
          <pub-id pub-id-type="pii">v9i4e24743</pub-id>
          <pub-id pub-id-type="pmcid">PMC8059785</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ford</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>McElligott</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>King</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Simpson</surname>
              <given-names>KN</given-names>
            </name>
            <name name-style="western">
              <surname>Valenta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Warr</surname>
              <given-names>EH</given-names>
            </name>
            <name name-style="western">
              <surname>Walsh</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Debenham</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Teasdale</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Meystre</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Obeid</surname>
              <given-names>JS</given-names>
            </name>
            <name name-style="western">
              <surname>Metts</surname>
              <given-names>Christopher</given-names>
            </name>
            <name name-style="western">
              <surname>Lenert</surname>
              <given-names>Leslie A</given-names>
            </name>
          </person-group>
          <article-title>Leveraging health system telehealth and informatics infrastructure to create a continuum of services for COVID-19 screening, testing, and treatment</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>12</month>
          <day>09</day>
          <volume>27</volume>
          <issue>12</issue>
          <fpage>1871</fpage>
          <lpage>1877</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32602884"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa157</pub-id>
          <pub-id pub-id-type="medline">32602884</pub-id>
          <pub-id pub-id-type="pii">5865271</pub-id>
          <pub-id pub-id-type="pmcid">PMC7337763</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Krausz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Westenberg</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Vigo</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Spence</surname>
              <given-names>RT</given-names>
            </name>
            <name name-style="western">
              <surname>Ramsey</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Emergency response to COVID-19 in Canada: platform development and implementation for eHealth in crisis management</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>05</month>
          <day>15</day>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>e18995</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/2/e18995/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18995</pub-id>
          <pub-id pub-id-type="medline">32401218</pub-id>
          <pub-id pub-id-type="pii">v6i2e18995</pub-id>
          <pub-id pub-id-type="pmcid">PMC7236607</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Ren</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Tian</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Qiu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A COVID-19 risk assessment decision support system for general practitioners: design and development study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>06</month>
          <day>29</day>
          <volume>22</volume>
          <issue>6</issue>
          <fpage>e19786</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/6/e19786/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19786</pub-id>
          <pub-id pub-id-type="medline">32540845</pub-id>
          <pub-id pub-id-type="pii">v22i6e19786</pub-id>
          <pub-id pub-id-type="pmcid">PMC7332157</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>Hong</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Xiong</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Telemedicine during the COVID-19 pandemic: experiences from Western China</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>05</month>
          <day>08</day>
          <volume>22</volume>
          <issue>5</issue>
          <fpage>e19577</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/5/e19577/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/19577</pub-id>
          <pub-id pub-id-type="medline">32349962</pub-id>
          <pub-id pub-id-type="pii">v22i5e19577</pub-id>
          <pub-id pub-id-type="pmcid">PMC7212818</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thulesius</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Increased importance of digital medicine and eHealth during the COVID-19 pandemic</article-title>
          <source>Scand J Prim Health Care</source>
          <year>2020</year>
          <month>06</month>
          <day>02</day>
          <volume>38</volume>
          <issue>2</issue>
          <fpage>105</fpage>
          <lpage>106</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32484725"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/02813432.2020.1770466</pub-id>
          <pub-id pub-id-type="medline">32484725</pub-id>
          <pub-id pub-id-type="pmcid">PMC8570755</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <article-title>Eligible for Home Recovery Programme</article-title>
          <source>Ministry of Health Singapore</source>
          <year>2022</year>
          <access-date>2022-02-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.covid.gov.sg/unwell/hrp">https://www.covid.gov.sg/unwell/hrp</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pawar</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A comparative study of agile software development methodology and traditional waterfall model</article-title>
          <source>IOSR J Comput Eng</source>
          <year>2015</year>
          <volume>1</volume>
          <fpage>18</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iosrjournals.org/iosr-jce/papers/NCIEST/Volume%202/01.01-08.pdf"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>EBN</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Co-creation and the new landscapes of design</article-title>
          <source>CoDesign</source>
          <year>2008</year>
          <month>03</month>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1080/15710880701875068"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710880701875068</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jessup</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Osborne</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Buchbinder</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Beauchamp</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Using co-design to develop interventions to address health literacy needs in a hospitalised population</article-title>
          <source>BMC Health Serv Res</source>
          <year>2018</year>
          <month>12</month>
          <day>20</day>
          <volume>18</volume>
          <issue>1</issue>
          <fpage>989</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmchealthservres.biomedcentral.com/articles/10.1186/s12913-018-3801-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12913-018-3801-7</pub-id>
          <pub-id pub-id-type="medline">30572887</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12913-018-3801-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6302392</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>EBN</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>PJ</given-names>
            </name>
          </person-group>
          <article-title>Co-creation and the new landscapes of design</article-title>
          <source>CoDesign</source>
          <year>2008</year>
          <month>03</month>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.1080/15710880701875068</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Hayfield</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <article-title>Thematic analysis</article-title>
          <source>A Practical Guide to Research Methods. 3rd ed</source>
          <year>2015</year>
          <publisher-loc>Qualitative psychology</publisher-loc>
          <publisher-name>SAGE Publications</publisher-name>
          <fpage>222</fpage>
          <lpage>248</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Menold</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Simpson</surname>
              <given-names>TW</given-names>
            </name>
            <name name-style="western">
              <surname>Jablokow</surname>
              <given-names>KW</given-names>
            </name>
          </person-group>
          <article-title>The prototype for X (PFX) framework: assessing the impact of PFX on desirability, feasibility, and viability of end designs</article-title>
          <year>2016</year>
          <month>12</month>
          <day>05</day>
          <conf-name>ASME 2016 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference</conf-name>
          <conf-date>August 21-24, 2-16</conf-date>
          <conf-loc>Charlotte, NC</conf-loc>
          <fpage>DETC2016-60225, V007T06A040</fpage>
          <pub-id pub-id-type="doi">10.1115/detc2016-60225</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>Abashev</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Grigoryev</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Grigorian</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Boyko</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Programming tools for messenger-based chatbot system organization: implication for outpatient and translational medicines</article-title>
          <source>BioNanoScience</source>
          <year>2016</year>
          <month>11</month>
          <day>22</day>
          <volume>7</volume>
          <issue>2</issue>
          <fpage>403</fpage>
          <lpage>407</lpage>
          <pub-id pub-id-type="doi">10.1007/s12668-016-0376-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>FormSG</article-title>
          <source>Open Government Products, Government Technology Agency Singapore</source>
          <year>2022</year>
          <access-date>2022-01-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://form.gov.sg/#!/">https://form.gov.sg/#!/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <article-title>Home care for patients with COVID-19 presenting with mild symptoms and management of their contacts</article-title>
          <source>World Health Organization</source>
          <year>2020</year>
          <month>08</month>
          <day>13</day>
          <access-date>2022-01-07</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/home-care-for-patients-with-suspected-novel-coronavirus-(ncov)-infection-presenting-with-mild-symptoms-and-management-of-contacts">https://www.who.int/publications/i/item/home-care-for-patients-with-suspected-novel-coronavirus-(ncov)-infection-presenting-with-mild-symptoms-and-management-of-contacts</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>Health manpower</article-title>
          <source>Ministry of Health Singapore</source>
          <year>2020</year>
          <access-date>2022-01-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.moh.gov.sg/resources-statistics/singapore-health-facts/health-manpower">https://www.moh.gov.sg/resources-statistics/singapore-health-facts/health-manpower</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Raposo</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marques</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Correia</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Melo</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Valente</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Rosário</surname>
              <given-names>Luis Brás</given-names>
            </name>
            <name name-style="western">
              <surname>Froes</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Sanches</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>HPD</given-names>
            </name>
          </person-group>
          <article-title>e-CoVig: a novel mHealth system for remote monitoring of symptoms in COVID-19</article-title>
          <source>Sensors (Basel)</source>
          <year>2021</year>
          <month>05</month>
          <day>13</day>
          <volume>21</volume>
          <issue>10</issue>
          <fpage>3397</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=s21103397"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/s21103397</pub-id>
          <pub-id pub-id-type="medline">34068131</pub-id>
          <pub-id pub-id-type="pii">s21103397</pub-id>
          <pub-id pub-id-type="pmcid">PMC8152780</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>Annis</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Pleasants</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hultman</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lindemann</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Billecke</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Badlani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Melton</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Rapid implementation of a COVID-19 remote patient monitoring program</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>08</month>
          <day>01</day>
          <volume>27</volume>
          <issue>8</issue>
          <fpage>1326</fpage>
          <lpage>1330</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32392280"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa097</pub-id>
          <pub-id pub-id-type="medline">32392280</pub-id>
          <pub-id pub-id-type="pii">5835871</pub-id>
          <pub-id pub-id-type="pmcid">PMC7239139</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bøen</surname>
              <given-names>Hege</given-names>
            </name>
            <name name-style="western">
              <surname>Dalgard</surname>
              <given-names>OS</given-names>
            </name>
            <name name-style="western">
              <surname>Bjertness</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The importance of social support in the associations between psychological distress and somatic health problems and socio-economic factors among older adults living at home: a cross sectional study</article-title>
          <source>BMC Geriatr</source>
          <year>2012</year>
          <month>06</month>
          <day>08</day>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>27</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcgeriatr.biomedcentral.com/articles/10.1186/1471-2318-12-27"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2318-12-27</pub-id>
          <pub-id pub-id-type="medline">22682023</pub-id>
          <pub-id pub-id-type="pii">1471-2318-12-27</pub-id>
          <pub-id pub-id-type="pmcid">PMC3464708</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>Czaja</surname>
              <given-names>SJ</given-names>
            </name>
          </person-group>
          <article-title>Can technology empower older adults to manage their health</article-title>
          <source>Generations: Journal of the American Society on Aging</source>
          <year>2015</year>
          <volume>39</volume>
          <issue>1</issue>
          <fpage>46</fpage>
          <lpage>51</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/26556097"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rathbone</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Prescott</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The use of mobile apps and SMS messaging as physical and mental health interventions: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>08</month>
          <day>24</day>
          <volume>19</volume>
          <issue>8</issue>
          <fpage>e295</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/8/e295/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7740</pub-id>
          <pub-id pub-id-type="medline">28838887</pub-id>
          <pub-id pub-id-type="pii">v19i8e295</pub-id>
          <pub-id pub-id-type="pmcid">PMC5590007</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>Tang</surname>
              <given-names>YH</given-names>
            </name>
            <name name-style="western">
              <surname>Chong</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Chua</surname>
              <given-names>YP</given-names>
            </name>
            <name name-style="western">
              <surname>Chui</surname>
              <given-names>PL</given-names>
            </name>
            <name name-style="western">
              <surname>Tang</surname>
              <given-names>LY</given-names>
            </name>
            <name name-style="western">
              <surname>Rahmat</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>The effect of mobile messaging apps on cardiac patient knowledge of coronary artery disease risk factors and adherence to a healthy lifestyle</article-title>
          <source>J Clin Nurs</source>
          <year>2018</year>
          <month>12</month>
          <day>30</day>
          <volume>27</volume>
          <issue>23-24</issue>
          <fpage>4311</fpage>
          <lpage>4320</lpage>
          <pub-id pub-id-type="doi">10.1111/jocn.14538</pub-id>
          <pub-id pub-id-type="medline">29777560</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Crozier-Shaw</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hughes</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cashman</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Synnott</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Instant messaging apps and data protection: combining to improve hip fracture care?</article-title>
          <source>Ir J Med Sci</source>
          <year>2022</year>
          <month>04</month>
          <day>05</day>
          <volume>191</volume>
          <issue>2</issue>
          <fpage>765</fpage>
          <lpage>769</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33818739"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s11845-021-02612-4</pub-id>
          <pub-id pub-id-type="medline">33818739</pub-id>
          <pub-id pub-id-type="pii">10.1007/s11845-021-02612-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC8020372</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Esteban-Vasallo</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Domínguez-Berjón</surname>
              <given-names>M F</given-names>
            </name>
            <name name-style="western">
              <surname>García-Riolobos</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zoni</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Aréjula Torres</surname>
              <given-names>J L</given-names>
            </name>
            <name name-style="western">
              <surname>Sánchez-Perruca</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Astray-Mochales</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Effect of mobile phone text messaging for improving the uptake of influenza vaccination in patients with rare diseases</article-title>
          <source>Vaccine</source>
          <year>2019</year>
          <month>08</month>
          <day>23</day>
          <volume>37</volume>
          <issue>36</issue>
          <fpage>5257</fpage>
          <lpage>5264</lpage>
          <pub-id pub-id-type="doi">10.1016/j.vaccine.2019.07.062</pub-id>
          <pub-id pub-id-type="medline">31353257</pub-id>
          <pub-id pub-id-type="pii">S0264-410X(19)30970-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <source>Doctor Everywhere</source>
          <year>2021</year>
          <access-date>2023-01-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doctoranywhere.com/">https://doctoranywhere.com/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
          <article-title>Smart health video consultation</article-title>
          <source>Integrated Health Information Systems (IHIS)</source>
          <year>2021</year>
          <access-date>2023-01-17</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ihis.com.sg/vc">https://www.ihis.com.sg/vc</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
