<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="review-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v27i1e68344</article-id>
      <article-id pub-id-type="pmid">40228239</article-id>
      <article-id pub-id-type="doi">10.2196/68344</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Review</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Review</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Developing the Digital Health Communication Maturity Model: Systematic Review</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>Pilabré</surname>
            <given-names>Hermann</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Deiters</surname>
            <given-names>Wolfgang</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Kim</surname>
            <given-names>Grace Jeonghyun</given-names>
          </name>
          <degrees>BA, MA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution/>
            <institution>Department of Communication</institution>
            <institution>University of Maryland, College Park</institution>
            <addr-line>Skinner Building</addr-line>
            <addr-line>4300 Chapel Ln</addr-line>
            <addr-line>College Park, MD, 20782</addr-line>
            <country>United States</country>
            <phone>1 2028920233</phone>
            <email>jkim0501@umd.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0007-8000-4341</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Namkoong</surname>
            <given-names>Kang</given-names>
          </name>
          <degrees>BA, MA, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2246-6210</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Communication</institution>
        <institution>University of Maryland, College Park</institution>
        <addr-line>College Park, MD</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Grace Jeonghyun Kim <email>jkim0501@umd.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>14</day>
        <month>4</month>
        <year>2025</year>
      </pub-date>
      <volume>27</volume>
      <elocation-id>e68344</elocation-id>
      <history>
        <date date-type="received">
          <day>4</day>
          <month>11</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>9</day>
          <month>12</month>
          <year>2024</year>
        </date>
        <date date-type="rev-recd">
          <day>17</day>
          <month>12</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>29</day>
          <month>1</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Grace Jeonghyun Kim, Kang Namkoong. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 14.04.2025.</copyright-statement>
      <copyright-year>2025</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2025/1/e68344" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Digital health has become integral to public health care, advancing how services are accessed, delivered, and managed. Health organizations increasingly assess their digital health maturity to leverage these innovations fully. However, existing digital health maturity models (DHMMs) primarily focus on technology and infrastructure, often neglecting critical communication components.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This systematic review addresses gaps in DHMMs by identifying deficiencies in user communication elements and proposing the digital health communication maturity model (DHCMM). The DHCMM integrates critical health communication dimensions such as satisfaction, engagement, personalization, and customization to provide a comprehensive evaluation framework.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We followed the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) guidelines to conduct a systematic review of studies selected from 3 databases: EBSCO, PubMed, and ProQuest. Studies were screened and included based on their focus on digital health maturity and communication elements, with the final selection limited to English-language research addressing DHMMs.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Of the 1138 initially identified studies, 31 (2.72%) met the inclusion criteria. Current DHMMs heavily emphasize infrastructure while overlooking user engagement and communication; for instance, only 35% (11/31) of the reviewed models incorporated user satisfaction, and less than one-fifth (6/31, 19%) addressed personalization or customization. The DHCMM addresses these gaps with 7 maturity levels, ranging from <italic>initial</italic> to <italic>engaged</italic>, and emphasizes user-centered metrics and governance. Quantitative analysis showed substantial variations in communication metrics, with satisfaction metrics incorporated at an average rate of 22% (7/31) across the reviewed models.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The DHCMM shifts the focus of digital health maturity assessments by emphasizing communication and user engagement. This model provides health care organizations with a structured framework to enhance digital health initiatives, leading to better patient outcomes and system-wide efficiencies. The model delivers actionable insights for organizations aiming to achieve advanced digital maturity by addressing underrepresented dimensions. Future research should implement and refine the DHCMM across diverse health care contexts to enhance its effectiveness. The adoption of this model could result in more equitable, user-centered health care systems that integrate technological advancements with human-centered care.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>digital health</kwd>
        <kwd>maturity model</kwd>
        <kwd>integrated model</kwd>
        <kwd>digital health communication</kwd>
        <kwd>health communication</kwd>
        <kwd>systematic review</kwd>
        <kwd>model development</kwd>
        <kwd>health care innovation</kwd>
        <kwd>digital transformation</kwd>
        <kwd>organizational readiness</kwd>
        <kwd>evaluation metrics</kwd>
        <kwd>health care technology</kwd>
        <kwd>digital strategy</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Advancements in digital technology have ushered in an era characterized by rapid digital transformations across various sectors. This progress has led to the emergence of digital health as a pivotal force in the public health arena, fundamentally reshaping the accessibility, delivery, and management of health care services [<xref ref-type="bibr" rid="ref1">1</xref>]. Digital media technology enables patient monitoring and facilitates communication between health care providers and patients, representing a revolutionary shift that transcends geographic and temporal limitations [<xref ref-type="bibr" rid="ref2">2</xref>]. Digital health, also known as eHealth or health IT, holds immense potential to improve patient outcomes, streamline health care processes, and redefine the physician-patient relationship [<xref ref-type="bibr" rid="ref3">3</xref>].</p>
        <p>Digital health encompasses various applications, including mobile health, wearable devices, telemedicine platforms, and electronic health records [<xref ref-type="bibr" rid="ref4">4</xref>]. These technological advancements enable real-time data exchange, remote patient monitoring, personalized treatment plans, and evidence-based decision-making. Consequently, digital health offers significant benefits, such as enhanced patient engagement and adherence, while providing health care providers with data-driven insights for more precise diagnoses and treatment recommendations [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>]. Beyond the mere incorporation of gadgets and software, digital health represents a profound shift in health care delivery, extending into daily lives through wearables, health apps, and web-based consultations [<xref ref-type="bibr" rid="ref7">7</xref>]. This approach allows patients to conveniently access medical advice, monitor their health conditions, and manage chronic illnesses from their homes. At the same time, health care providers gain access to a wealth of data, potentially reducing errors and enhancing patient outcomes [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
        <p>However, digital health also introduces new challenges, including data security, privacy concerns, system interoperability, regulatory compliance issues, and the need for fair access to health care technology. These issues are paramount in the health care industry [<xref ref-type="bibr" rid="ref9">9</xref>]. Moreover, health care organizations and stakeholders need a structured framework to evaluate their maturity and ensure the effective adoption and integration of these technologies. The rapid pace of technological innovation has led to a fragmented landscape, with various digital health solutions operating on disparate standards and protocols [<xref ref-type="bibr" rid="ref10">10</xref>]. The key challenge lies in facilitating seamless communication and data exchange between these systems while safeguarding patient privacy, representing no small feat.</p>
        <p>To overcome these challenges, health care organizations aim to enhance their preparedness in the rapidly evolving digital health space. One path forward is to improve maturity. Maturity encompasses technological capabilities and the organization’s readiness to adapt and communicate effectively in this digital era [<xref ref-type="bibr" rid="ref10">10</xref>]. This is where the digital health maturity model (DHMM) concept becomes significant [<xref ref-type="bibr" rid="ref11">11</xref>]. Maturity models are currently used in many sectors, such as financial services and manufacturing [<xref ref-type="bibr" rid="ref12">12</xref>]. These models offer a structured framework for assessing an organization’s readiness, progress, and effectiveness in adopting digital health solutions through the stages of maturation to optimize implementation and outcomes.</p>
        <p>Typically, DHMMs consist of stages or levels that assess an organization’s capabilities in key areas such as technological infrastructure, data management, interoperability, clinical workflows, and patient engagement [<xref ref-type="bibr" rid="ref10">10</xref>]. They help stakeholders identify gaps, prioritize needs, and determine a strategic and effective course for digital health implementation. However, existing DHMMs often fail due to technological, organizational, and social factors [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. This results in a lack of a standardized DHMM for use in academia and public health practice.</p>
      </sec>
      <sec>
        <title>Objectives</title>
        <p>To explore DHMMs more deeply, this review seeks to answer the following questions:</p>
        <list list-type="order">
          <list-item>
            <p>Which DHMMs have been used in research?</p>
          </list-item>
          <list-item>
            <p>What are the common components among these models?</p>
          </list-item>
          <list-item>
            <p>What technological, organizational, and social factors are insufficiently addressed by existing DHMMs?</p>
          </list-item>
        </list>
        <p>On the basis of the findings, this study aims to propose a more comprehensive DHMM that addresses the limitations of current models and captures the dynamic nature of digital health.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Systematic Review</title>
        <p>A systematic literature review was conducted based on the methodological frameworks of Arksey and O’Malley [<xref ref-type="bibr" rid="ref15">15</xref>] and the JBI [<xref ref-type="bibr" rid="ref16">16</xref>] to examine the existing literature on DHMMs. The PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) checklist [<xref ref-type="bibr" rid="ref17">17</xref>] was applied to maintain methodological rigor, reduce bias, and ensure reliability (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Following the approach outlined by Moosapour et al [<xref ref-type="bibr" rid="ref18">18</xref>], the review synthesizes existing knowledge, addressing challenges related to technological advancements and varying digital health standards. It examines current DHMMs; identifies gaps in technological, organizational, and social factors; and outlines a framework for use in public health practice and academic contexts [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
      </sec>
      <sec>
        <title>Search Strategy</title>
        <p>To identify relevant articles covering DHMMs, an extensive search strategy was used across EBSCO, PubMed, and ProQuest databases using the search term “Digital Health and Maturity” for publications from January 2000 to May 2024 (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref19">19</xref>-<xref ref-type="bibr" rid="ref49">49</xref>]). These databases were selected due to their established status in fields related to digital health [<xref ref-type="bibr" rid="ref50">50</xref>]. Their prominence stems from several factors, including their extensive coverage of the literature, sophisticated cataloging systems, and user-friendly interfaces. Consequently, they are widely recognized and used by researchers, clinicians, and practitioners in digital health–related fields [<xref ref-type="bibr" rid="ref51">51</xref>]. Furthermore, these databases offer advanced search options, access to full-text articles, and seamless integration with citation management tools, enhancing their utility when conducting focused reviews and meta-analyses in digital health research. Their credibility is bolstered by their long-standing presence in the academic and health communities, as well as their partnerships with reputable publishers, organizations, and networks [<xref ref-type="bibr" rid="ref52">52</xref>]. <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> outlines the search strategy and terms used to identify relevant studies on DHMMs.</p>
        <boxed-text id="box1" position="float">
          <title>Overview of the search strategy used to identify relevant digital health maturity models in this systematic review.</title>
          <p>
            <bold>Steps and research terms</bold>
          </p>
          <list list-type="order">
            <list-item>
              <p>(“Digital Health AND Maturity” [Title/Abstract])</p>
            </list-item>
            <list-item>
              <p>(“Maturity Model” [Title/Abstract] OR “Maturity Index” [Title/Abstract] OR “Maturity assessment” [Title/Abstract] OR “Model in Digital Health” [Title/Abstract])</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Inclusion and Exclusion Criteria</title>
        <p>The articles were reviewed and assessed based on their relevance to digital maturity in the development of a comprehensive framework tailored to the digital health landscape. In addition, only articles published in English were selected. Specific exclusion criteria were also used to refine article selection. The research excluded those articles that (1) did not contemplate maturity levels or categories, (2) were not related to the objectives of this study, (3) studied biological maturity, (4) focused on only IT implementation, and (5) were not full-text articles. In cases where multiple versions of a report were available, only the most recent version was included (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>).</p>
        <boxed-text id="box2" position="float">
          <title>Inclusion and exclusion criteria used in this systematic review to identify relevant digital health maturity models from the selected databases.</title>
          <p>
            <bold>Inclusion criteria</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Article type: peer-reviewed journal articles, systematic reviews, and theoretical models</p>
            </list-item>
            <list-item>
              <p>Language: English</p>
            </list-item>
            <list-item>
              <p>Publication year: January 2000 to May 2024</p>
            </list-item>
            <list-item>
              <p>Keywords: must include terms such as “digital health,” “maturity model,” and “maturity index”</p>
            </list-item>
            <list-item>
              <p>Study population: studies on health care technologies or digital health</p>
            </list-item>
            <list-item>
              <p>Study design: observational, experimental, or review studies</p>
            </list-item>
            <list-item>
              <p>Outcome: studies focusing on digital health and communication models</p>
            </list-item>
          </list>
          <p>
            <bold>Exclusion criteria</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Article type: conference abstracts, editorials, and non–peer-reviewed articles</p>
            </list-item>
            <list-item>
              <p>Language: non-English</p>
            </list-item>
            <list-item>
              <p>Publication year: articles published before 2000</p>
            </list-item>
            <list-item>
              <p>Keywords: articles lacking relevance to digital health or maturity-related terms</p>
            </list-item>
            <list-item>
              <p>Study population: studies unrelated to health or technology</p>
            </list-item>
            <list-item>
              <p>Study design: case reports or anecdotal evidence</p>
            </list-item>
            <list-item>
              <p>Outcome: studies unrelated to digital health and communication models</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Data Extraction</title>
        <p>During the screening stages, articles were categorized into 2 dimensions. First, reference information, such as study title, publication year, journal, and authorship, was recorded. Second, each publication was evaluated for its relevance to the study’s objectives, methodology, outcomes, and recommendations regarding inclusion or exclusion. Each paper was thoroughly reviewed during the analysis to ensure alignment with this investigation’s objectives. The search results were then meticulously analyzed and reviewed using Microsoft Excel for further assessment. Rigorous data collection techniques were used, with trained personnel conducting data extraction. Any discrepancies that arose were resolved through discussions.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>The results section presents a systematic analysis of DHMMs, evaluating their key components, effectiveness, and limitations. The findings highlight gaps in technological, organizational, and social dimensions, and propose a new integrated model.</p>
      </sec>
      <sec>
        <title>Study Selection</title>
        <p>Initial searches yielded 1138 articles that were “relevant,” of which after excluding 157 (13.8%) duplicate and non-English articles, 981 (86.2%) remained for further evaluation. Of these 981 articles, 810 (82.6%) were excluded based on the absence of the key term “maturity” in their titles or abstracts, leaving 171 (17.4%) for continued assessment. Further refinement was applied to include only articles featuring terms such as “maturity model,” “maturity index,” “maturity assessment,” or “model in digital health,” resulting in a final selection of 62 articles, of which 15 (24%) unrelated studies, 13 (21%) studies on biological maturity, and 10 (16%) studies on implementation were excluded, leaving 24 (39%) studies eligible for inclusion in the review. The screening process is illustrated in the PRISMA flowchart (<xref rid="figure1" ref-type="fig">Figure 1</xref>). In total, 7 studies identified from the reference lists were also included, bringing the total number of studies for review to 31 (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flow diagram of the study selection process. The databases searched included EBSCO, PubMed, and ProQuest, using the search term “Digital Health and Maturity” for the period from January 2000 to May 2024. The process involved identification, screening, and inclusion phases. Inclusion criteria emphasized relevance to digital health maturity, health care frameworks, and full-text availability in the English language, while exclusion criteria ruled out non–health care studies, lack of empirical data, and non-English publications. The final selection included 31 studies for qualitative synthesis.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e68344_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>The characteristics and key findings of studies on digital health maturity models (DHMMs) included in the systematic review.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="430"/>
            <col width="320"/>
            <thead>
              <tr valign="top">
                <td>Study</td>
                <td>Methods</td>
                <td>Source</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Williams et al [<xref ref-type="bibr" rid="ref19">19</xref>], 2019</td>
                <td>Operational framework</td>
                <td>
                  <italic>JMIR Medical Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Martin et al [<xref ref-type="bibr" rid="ref20">20</xref>], 2019</td>
                <td>Multivariable regression model</td>
                <td>
                  <italic>NPJ Digital Medicine</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Gomes and Romão [<xref ref-type="bibr" rid="ref21">21</xref>], 2018</td>
                <td>State-of-the-art review</td>
                <td>
                  <italic>Journal of Medical Systems</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Shaygan and Daim [<xref ref-type="bibr" rid="ref22">22</xref>], 2019</td>
                <td>Exploratory multicriteria approach</td>
                <td>
                  <italic>IEEE Xplore</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>van Dyk and Schutte [<xref ref-type="bibr" rid="ref23">23</xref>], 2013</td>
                <td>Iterative process</td>
                <td>
                  <italic>Intech Open</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>van Dyk and Schutte [<xref ref-type="bibr" rid="ref24">24</xref>], 2011</td>
                <td>Iterative process</td>
                <td>
                  <italic>South African Journal of Industrial Engineering</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Jami Pour and Jafari [<xref ref-type="bibr" rid="ref25">25</xref>], 2019</td>
                <td>Mixed methods</td>
                <td>
                  <italic>Emerald Insight</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Alexander et al [<xref ref-type="bibr" rid="ref26">26</xref>], 2022</td>
                <td>National survey</td>
                <td>
                  <italic>JMIR Aging</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Duncan et al [<xref ref-type="bibr" rid="ref27">27</xref>], 2013</td>
                <td>Used various artifacts</td>
                <td>
                  <italic>Online Journal of Public Health Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Duncan et al [<xref ref-type="bibr" rid="ref28">28</xref>], 2022</td>
                <td>Systematic review</td>
                <td>
                  <italic>Journal of Medical Internet Research</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Eysenbach [<xref ref-type="bibr" rid="ref29">29</xref>], 2007</td>
                <td>Theoretical</td>
                <td>
                  <italic>Studies in Health Technology and Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Grasser et al [<xref ref-type="bibr" rid="ref30">30</xref>], 2018</td>
                <td>Innovative, multidimensional, and human-centered socioeconomic capability model</td>
                <td>
                  <italic>Studies in Health Technology and Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Jansen-Kosterink et al [<xref ref-type="bibr" rid="ref31">31</xref>], 2022</td>
                <td>Technology-readiness levels</td>
                <td>
                  <italic>Digital Health</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Johnston [<xref ref-type="bibr" rid="ref32">32</xref>], 2017</td>
                <td>Digital maturity assessments</td>
                <td>
                  <italic>Journal of Medical Internet Research</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Kayser et al [<xref ref-type="bibr" rid="ref33">33</xref>], 2022</td>
                <td>Narrative overview identifying health technology assessment–inspired models</td>
                <td>
                  <italic>Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Kouroubali et al [<xref ref-type="bibr" rid="ref34">34</xref>], 2019</td>
                <td>Interoperability maturity model</td>
                <td>
                  <italic>Studies in Health Technology and Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Kutza et al [<xref ref-type="bibr" rid="ref35">35</xref>], 2022</td>
                <td>Literature review and derivation of maturity objects</td>
                <td>
                  <italic>Studies in Health Technology and Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Liaw et al [<xref ref-type="bibr" rid="ref36">36</xref>], 2017</td>
                <td>Mixed methods evaluation</td>
                <td>
                  <italic>International Journal of Medical Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Liaw et al [<xref ref-type="bibr" rid="ref37">37</xref>], 2021</td>
                <td>Literature review</td>
                <td>
                  <italic>Journal of the American Medical Informatics Association</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Nyangena et al [<xref ref-type="bibr" rid="ref38">38</xref>], 2021</td>
                <td>Health information system interoperability maturity toolkit, developed by MEASURE Evaluation and the Health Data Collaborative’s digital health and interoperability working group</td>
                <td>
                  <italic>BMJ Health &#38; Care Informatics</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Occelli and Scelfo [<xref ref-type="bibr" rid="ref39">39</xref>], 2020</td>
                <td>Survey</td>
                <td>
                  <italic>International Journal of E-Planning Research</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Peytremann-Bridevaux et al [<xref ref-type="bibr" rid="ref40">40</xref>], 2021</td>
                <td>Scaling Integrated Care in Context maturity model tool</td>
                <td>
                  <italic>BMJ Open</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Pumplun et al [<xref ref-type="bibr" rid="ref41">41</xref>], 2021</td>
                <td>Qualitative interview study</td>
                <td>
                  <italic>Journal of Medical Internet Research</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Reifegerste et al [<xref ref-type="bibr" rid="ref42">42</xref>], 2022</td>
                <td>Telemedicine community readiness model</td>
                <td>
                  <italic>Journal of Public Health</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Richmond et al [<xref ref-type="bibr" rid="ref43">43</xref>], 2022</td>
                <td>Novel maturity index for assessing medical device start-ups</td>
                <td>
                  <italic>Journal of Clinical and Translational Science</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Stahl et al [<xref ref-type="bibr" rid="ref44">44</xref>], 2022</td>
                <td>Questionnaire study</td>
                <td>
                  <italic>JMIR Formative Research</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Kolukısa Tarhan et al [<xref ref-type="bibr" rid="ref45">45</xref>], 2020</td>
                <td>Multivocal literature review</td>
                <td>
                  <italic>Digital Health</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Tom-Aba et al [<xref ref-type="bibr" rid="ref46">46</xref>], 2020</td>
                <td>Evaluation of surveillance outbreak response management and analysis system using the global good maturity model version 1.0 indicators</td>
                <td>
                  <italic>JMIR Public Health and Surveillance</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Flott et al [<xref ref-type="bibr" rid="ref47">47</xref>], 2016</td>
                <td>Systematic review</td>
                <td>
                  <italic>Journal of Medical Internet Research</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Vogel et al [<xref ref-type="bibr" rid="ref48">48</xref>], 2024</td>
                <td>Used digital maturity data from the German DigitalRadar project (2021) and financial statement data from the Hospital Rating Report (2017-2019; n=860); performed linear regressions with the DigitalRadar score</td>
                <td>
                  <italic>Health Policy</italic>
                </td>
              </tr>
              <tr valign="top">
                <td>Vogel et al [<xref ref-type="bibr" rid="ref49">49</xref>], 2024</td>
                <td>Performed multivariate linear regressions with the respective quality indicators as dependent variables and various digitalization subdimensions as independent variables</td>
                <td>
                  <italic>Ruhr Economic Papers</italic>
                </td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Quality Evaluation</title>
        <p>The selected articles were evaluated based on the quality of the scholarly publication using the Scimago Journal Rank indicator as the primary tool. This approach aligns with the one adopted by Oshni Alvandi et al [<xref ref-type="bibr" rid="ref53">53</xref>]. Furthermore, each included paper underwent 2 assessment rounds, with the majority (22/31, 71%) being reviewed by a different researcher to ensure additional quality assurance (<xref ref-type="table" rid="table2">Table 2</xref>).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Quality assessment of the included journals and articles using the Scimago Journal Rank indicator.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="340"/>
            <col width="330"/>
            <col width="330"/>
            <thead>
              <tr valign="top">
                <td>Rankings</td>
                <td>Journals (n=30), n (%)</td>
                <td>Studies (n=31), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Quartile 1</td>
                <td>18 (60)</td>
                <td>18 (58)</td>
              </tr>
              <tr valign="top">
                <td>Quartile 2</td>
                <td>4 (13)</td>
                <td>4 (13)</td>
              </tr>
              <tr valign="top">
                <td>Quartile 3</td>
                <td>3 (10)</td>
                <td>4 (13)</td>
              </tr>
              <tr valign="top">
                <td>Quartile 4</td>
                <td>0 (0)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td>Not yet assigned a rank</td>
                <td>1 (3)</td>
                <td>1 (3)</td>
              </tr>
              <tr valign="top">
                <td>Not ranked</td>
                <td>4 (13)</td>
                <td>4 (13)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Review of the Existing Maturity Models</title>
        <p>The systematic review identified 8 commonly used DHMMs: the capability maturity model (CMM), CMM integration (CMMI), electronic medical record adoption model (EMRAM), continuity of care maturity model (CCMM), clinical digital maturity index (CDMI), interoperability maturity model (IMM), telemedicine service maturity model (TMSMM), and DigitalRadar maturity model (DRMM). These models were compared to discern how they evaluate digital health maturity levels and identify gaps and improvement opportunities. Combining various features from these models resulted in a new and more comprehensive model capable of providing detailed insights into an organization’s maturity level and highlighting avenues for growth. Detailed explanations of each of the models are provided in the following subsections.</p>
      </sec>
      <sec>
        <title>Detailed Explanations of DHMMs</title>
        <sec>
          <title>CMM Framework</title>
          <p>The CMM is a software engineering framework that outlines a 5-level path for systematically and incrementally improving software engineering processes. It was developed by the Software Engineering Institute at Carnegie Mellon University in the 1980s. It is widely used to assess the maturity of an organization’s software processes [<xref ref-type="bibr" rid="ref53">53</xref>]. The model helps organizations identify and prioritize improvement areas based on their current level of process maturity. Organizations have few defined processes at level 1 (ie, the lowest level of process maturity). By contrast, at level 5 (ie, the highest level of process maturity), organizations have well-defined, highly optimized processes that are continually improved. The CMM focuses on process improvement and process maturity domains and subdomains, making it a valuable tool for organizations seeking to improve their software engineering processes [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>] (<xref ref-type="boxed-text" rid="box3">Textbox 3</xref> [<xref ref-type="bibr" rid="ref53">53</xref>]).</p>
          <boxed-text id="box3" position="float">
            <title>An overview of the 5 maturity levels of the capability maturity model, which represent an organization’s process maturity.</title>
            <p>
              <bold>Levels and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Level 1 (<italic>initial</italic>): the <italic>initial</italic> level is characterized by ad hoc and individualized processes. There is little or no process documentation, and processes are often not repeatable. At this level, the organization does not provide a stable environment for its software development activities.</p>
              </list-item>
              <list-item>
                <p>Level 2 (<italic>repeatable</italic>): the use of basic project management techniques characterizes the <italic>repeatable</italic> level. The organization begins to develop a set of repeatable standard processes from one project to the next and establish a project management infrastructure.</p>
              </list-item>
              <list-item>
                <p>Level 3 (<italic>defined</italic>): the use of formalized and standardized processes characterizes the <italic>defined</italic> level. All processes are well documented and approved by management. The organization has a clear and concise definition of the process used in all projects.</p>
              </list-item>
              <list-item>
                <p>Level 4 (<italic>managed</italic>): the active management of processes characterizes the <italic>managed</italic> level. The organization monitors and controls its processes using quantitative methods. Processes are continually improved and routinely audited.</p>
              </list-item>
              <list-item>
                <p>Level 5 (<italic>optimized</italic>): the proactive management of processes characterizes the <italic>optimized</italic> level. The organization continually strives to improve its processes based on a quantitative understanding and is constantly looking for ways to improve the efficiency and effectiveness of its software development processes.</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>CMMI Framework</title>
          <p>The CMMI is a framework devised by the Software Engineering Institute at Carnegie Mellon University in the early 2000s. It offers a structured approach to enhancing software engineering processes [<xref ref-type="bibr" rid="ref56">56</xref>]. It outlines a 5-level path for enhancing the processes incrementally (<xref ref-type="boxed-text" rid="box4">Textbox 4</xref> [<xref ref-type="bibr" rid="ref56">56</xref>]). The first 3 levels correspond to the capability levels of the CMM, and the fourth and fifth levels represent advanced improvement [<xref ref-type="bibr" rid="ref57">57</xref>]. The CMMI has 4 main domains: <italic>process</italic>, <italic>project</italic>, <italic>engineering</italic>, and <italic>support</italic>. Each domain is further divided into subdomains [<xref ref-type="bibr" rid="ref58">58</xref>]. The <italic>process</italic> domain includes planning, resourcing, deploying, implementing, monitoring, controlling, apprising, measuring, and improving processes.</p>
          <boxed-text id="box4" position="float">
            <title>Overview of the 5 maturity levels of the capability maturity model integration, which reflect an organization’s process improvement and performance optimization capabilities.</title>
            <p>
              <bold>Levels and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Level 1 (<italic>initial</italic>): this level is the starting point for an organization’s journey toward process improvement. At this level, processes are typically ad hoc and chaotic, with little management.</p>
              </list-item>
              <list-item>
                <p>Level 2 (<italic>managed</italic>): the processes at this level are beginning to be more controlled and managed. There is now some standardization and documentation of processes, and teams have started to track and monitor their work more systematically.</p>
              </list-item>
              <list-item>
                <p>Level 3 (<italic>defined</italic>): the use of formalized and standardized processes characterizes the <italic>defined</italic> level. All processes are well documented and approved by management. The organization has a clear and concise definition of the processes used in all projects.</p>
              </list-item>
              <list-item>
                <p>Level 4 (<italic>quantitatively managed</italic>): the processes are not only well defined and standardized, but they are also quantitatively managed. This means that teams are monitored and controlled to ensure that they follow the defined processes and that performances are measured and analyzed to identify areas for improvement.</p>
              </list-item>
              <list-item>
                <p>Level 5 (<italic>optimized</italic>): the processes are continuously improved. This means that performances are measured and analyzed to identify areas for improvement, with changes then made to the processes to improve them.</p>
              </list-item>
            </list>
          </boxed-text>
          <p>The <italic>project</italic> domain encompasses project design, development, and validation, while the <italic>engineering</italic> domain covers system and software engineering activities, including development and maintenance. Finally, the <italic>support</italic> domain focuses on support product development and maintenance [<xref ref-type="bibr" rid="ref57">57</xref>]. The CMMI framework helps organizations improve their processes and expand their capabilities.</p>
        </sec>
        <sec>
          <title>EMRAM Framework</title>
          <p>The EMRAM, created by the Healthcare Information and Management Systems Society (HIMSS), offers a comprehensive framework for evaluating the maturity of electronic medical record (EMR) systems within health care institutions [<xref ref-type="bibr" rid="ref19">19</xref>]. Comprising 8 stages ranging from <italic>preadoption</italic> to <italic>EMR optimization</italic>, the model delineates the evolution of EMR adoption and use (<xref ref-type="boxed-text" rid="box5">Textbox 5</xref> [<xref ref-type="bibr" rid="ref59">59</xref>]). Developed in collaboration with clinicians and health care IT experts worldwide, the EMRAM integrates seamlessly into clinical workflows. It facilitates comparative assessments of EMR progress across organizations. Consequently, it serves as a vital tool for health care entities to gauge and enhance their EMR implementation, ultimately elevating the standard of patient care.</p>
          <boxed-text id="box5" position="float">
            <title>An overview of the 7 maturity stages of the electronic medical record adoption model, a framework developed by the Healthcare Information and Management Systems Society to evaluate the adoption and implementation of electronic medical record (EMR) systems in health care organizations.</title>
            <p>
              <bold>Stages and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Stage 0 (<italic>no EMR system in place</italic>): this represents a stage where no EMR system is in place. This is the baseline level; all other levels are judged against it.</p>
              </list-item>
              <list-item>
                <p>Stage 1 (<italic>EMR adoption—incomplete</italic>): at this stage, the organization has started implementing EMRs but has not yet reached full adoption. The organization may be in the process of selecting an EMR system or may have already implemented an EMR system but is still in the process of training staff and integrating the EMR into the clinical workflow.</p>
              </list-item>
              <list-item>
                <p>Stage 2 (<italic>EMR adoption—partial</italic>): the organization has fully adopted EMRs in the clinical workflow at this stage. All staff members are trained on how to use the EMR system, and they use it daily to support patient care. The EMR is integrated into all aspects of the organization’s clinical workflow.</p>
              </list-item>
              <list-item>
                <p>Stage 3 (<italic>EMR adoption—complete</italic>): the EMR is used to track patient data and trends over time and is used to support evidence-based decision-making. All clinicians use the system for patient data storage, clinical decision support, electronic prescribing, and other features.</p>
              </list-item>
              <list-item>
                <p>Stage 4 (<italic>EMR optimization—incomplete</italic>): at this stage, EMRs are being used to improve patient safety. The EMR tracks patient safety data and trends and supports efforts to improve patient safety; for example, the system may be used for patient data storage, clinical decision support, electronic prescribing, and other features. However, there may be duplicate data entry issues, or the user interface could be improved.</p>
              </list-item>
              <list-item>
                <p>Stage 5 (<italic>EMR optimization—partial</italic>): at this stage, the EMR system is in place and being used to its full potential. Some improvements have been made in areas identified as needing improvement; for example, the system may be used for patient data storage, clinical decision support, electronic prescribing, and other features. The user interface may have been improved, or duplicate data entry may have been eliminated.</p>
              </list-item>
              <list-item>
                <p>Stage 6 (<italic>EMR optimization—complete</italic>): at this stage, EMRs are being used to transform health care. The EMR supports efforts to transform health care delivery through data-driven quality improvement initiatives.</p>
              </list-item>
              <list-item>
                <p>Stage 7 (<italic>complete EMR; external health information exchange; and data analytics, governance, disaster recovery, privacy, and security</italic>): organizations at this stage assess their experience with EMRs and make plans for their continued use or expansion. EMR systems are used for clinical care, with full functionality, integration across the care continuum, and evidence-based decision support.</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>CCMM Framework</title>
          <p>The CCMM is a powerful framework that helps health care organizations deliver seamless patient care across multiple care sites and health care providers [<xref ref-type="bibr" rid="ref21">21</xref>]. Developed by the HIMSS, the CCMM builds on the EMRAM, enhancing patient care by ensuring effective communication and teamwork among health care professionals. The CCMM delegates responsibility for coordinated care to administrators and governance leadership, clinical leadership, and IT and technology leadership, enhancing interoperability, governance, workforce efficiency, and predictive analytics within digital health [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
          <p>The CCMM comprises the 5 domains of <italic>governance</italic>, <italic>engagement</italic>, <italic>processes</italic>, <italic>information</italic>, and <italic>technology</italic>, each with several subdomains that indicate the corresponding maturity level (<xref ref-type="boxed-text" rid="box6">Textbox 6</xref> [<xref ref-type="bibr" rid="ref59">59</xref>]). The <italic>governance</italic> domain includes organizational structure, policies and procedures, and risk management. The <italic>engagement</italic> domain covers values, beliefs, communication, training, and education. The <italic>processes</italic> domain focuses on care coordination, care transitions, and disease management. The <italic>information</italic> domain includes data collection, management, decision support, and reporting and analytics. Finally, the <italic>technology</italic> domain covers system architecture, security and privacy, and interoperability [<xref ref-type="bibr" rid="ref60">60</xref>].</p>
          <boxed-text id="box6" position="float">
            <title>An overview of the 7 maturity stages of the continuity of care maturity model, a framework for assessing the maturity of health care organizations in providing seamless and coordinated care across different health care settings.</title>
            <p>
              <bold>Stages and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Stage 0 (<italic>limited or no electronic communication</italic>): at this stage, there is little to no electronic communication between health care providers. This can make it challenging to coordinate care because health care providers may not have access to critical patient information.</p>
              </list-item>
              <list-item>
                <p>Stage 1 (<italic>basic peer-to-peer data exchange</italic>): at this stage, health care providers can exchange basic patient information electronically. This allows for better care coordination because health care providers can access vital patient information more easily.</p>
              </list-item>
              <list-item>
                <p>Stage 2 (<italic>patient-centered clinical data exchanged using basic system-to-system exchanges</italic>): at this stage, patient-centered clinical data are exchanged between health care providers using basic system-to-system exchanges.</p>
              </list-item>
              <list-item>
                <p>Stage 3 (<italic>normalized patient record using structural interoperability</italic>): at this stage, a normalized patient record is used to exchange patient information between health care providers, enabling better care coordination.</p>
              </list-item>
              <list-item>
                <p>Stage 4 (<italic>care coordination based on actionable data using a semantic interoperable patient record</italic>): at this stage, care coordination is based on actionable data using a semantically interoperable patient record where health care providers can access essential information.</p>
              </list-item>
              <list-item>
                <p>Stage 5 (<italic>community-wide patient records using applied information with patient engagement focus</italic>): community-wide patient records are used at this stage to exchange patient information between health care providers. This allows for better care coordination because health care providers can access important patient information more easily.</p>
              </list-item>
              <list-item>
                <p>Stage 6 (<italic>closed-loop care coordination across care team members</italic>): at this stage, closed-loop care coordination is used to exchange patient information for better care coordination.</p>
              </list-item>
              <list-item>
                <p>Stage 7 (<italic>knowledge-driven engagement for a dynamic, multivendor, and multiorganizational interconnected health care delivery model</italic>): at this stage, knowledge-driven engagement is used for dynamic, multivendor, and multiorganizational interconnected health care delivery, and health care providers access information.</p>
              </list-item>
            </list>
          </boxed-text>
          <p>Unlike the EMRAM, which focuses on specific aspects of EMRs, the CCMM takes a holistic approach to measuring maturity, emphasizing continuity of care and seamless patient information sharing among diverse health care providers. Developed collaboratively by the HIMSS and health care professionals worldwide, the CCMM is a valuable tool for health care organizations to assess, implement, and scale coordinated care.</p>
        </sec>
        <sec>
          <title>CDMI Tool</title>
          <p>The CDMI is a valuable tool introduced by the National Health Service in 2013. It was updated in 2016 to measure and track the progress of digital maturity within health care organizations in the United Kingdom [<xref ref-type="bibr" rid="ref20">20</xref>]. It encompasses 3 key dimensions: <italic>capability</italic>, <italic>technological readiness</italic>, and <italic>infrastructure</italic>. The <italic>capability</italic> dimension assesses whether an organization possesses a well-defined digitalization strategy, effective governance structures, and adequately trained staff. The <italic>technological</italic> <italic>readiness</italic> dimension assesses the availability, effectiveness, and adaptability of technology to support digitalization efforts. Finally, the <italic>infrastructure</italic> dimension evaluates physical data and information management as well as the security infrastructure within the organization [<xref ref-type="bibr" rid="ref20">20</xref>]. Each CDMI dimension is further divided into 14 sections, enabling a comprehensive assessment of an organization’s digital maturity level. With the CDMI, organizations can identify their strengths and weaknesses in terms of digital readiness and devise strategic improvement plans [<xref ref-type="bibr" rid="ref60">60</xref>]. While the HIMSS maturity model may not be directly applicable in the UK context, the CDMI serves as a tailored and invaluable tool specifically designed for the UK market, offering a robust framework for assessing and advancing digital maturity within health care organizations. Furthermore, the framework facilitates monitoring progress and changes over time, fostering transparency and accountability (<xref ref-type="boxed-text" rid="box7">Textbox 7</xref> [<xref ref-type="bibr" rid="ref20">20</xref>]).</p>
          <boxed-text id="box7" position="float">
            <title>An overview of the 7 maturity levels of the clinical digital maturity index, a tool designed to evaluate the maturity of clinical data management systems in health care organizations, with a focus on data collection, integration, and use for decision-making.</title>
            <p>
              <bold>Levels and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Level 0 (<italic>digital maturity self-assessment</italic>): organizations can assess their digital maturity using this tool. It is also possible to obtain independent assessments from an external organization to provide an objective view of an organization’s digital maturity and guidance on how to improve it.</p>
              </list-item>
              <list-item>
                <p>Level 1 (<italic>themes</italic>): various aspects of digital maturity are assessed, including readiness, capabilities, and infrastructure.</p>
              </list-item>
              <list-item>
                <p>Level 2.1 (<italic>basic digital capabilities</italic>): organizations typically have no formal processes for managing or improving their digital capabilities. They may have some digital capabilities, but these are not used effectively or efficiently.</p>
              </list-item>
              <list-item>
                <p>Level 2.2 (<italic>developing digital capabilities</italic>): organizations use digital technologies to improve patient care and clinical outcomes and develop digital capabilities.</p>
              </list-item>
              <list-item>
                <p>Level 2.3 (<italic>advanced digital capabilities</italic>): advanced digital technologies are used to improve patient care, and organizations adopt these technologies to transform how they work.</p>
              </list-item>
              <list-item>
                <p>Level 2.4 (<italic>transforming digital capabilities</italic>): organizations have formalized processes for transforming digital capabilities. They use data analytics to drive continuous improvements.</p>
              </list-item>
              <list-item>
                <p>Level 2.5 (<italic>standardizing digital capabilities</italic>): organizations are using digital technologies to standardize how they work and improve population health, which results in continuous improvements.</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>IMM Framework</title>
          <p>The IMM was developed by the National E-Health Transition Authority of Australia to aid health care organizations in evaluating their level of interoperability maturity. Primarily, the IMM is structured around 5 stages of the CMMI, accompanied by a set of interoperability goals and an evaluation model geared toward the national level [<xref ref-type="bibr" rid="ref21">21</xref>]. These stages are intricately linked to <italic>organizational</italic>, <italic>informational</italic>, and <italic>technical</italic> dimensions at various levels, including local, corporate, and national scales. The model delineates interoperability targets to enhance scalability, scope, and configurability across these dimensions [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
          <p>The <italic>organizational</italic> dimension addresses business and governance considerations, ensuring alignment with strategic objectives. The <italic>informational</italic> dimension focuses on data format and semantics, ownership and rights, and standard building blocks, facilitating effective data exchange. Finally, the <italic>technical</italic> dimension encompasses specifications related to interface, functional decomposition, and communication protocols, which are vital for seamless interoperability. Although the IMM does not explicitly address architectural and technical policy separation, it furnishes health care organizations with a comprehensive framework to navigate their interoperability goals effectively [<xref ref-type="bibr" rid="ref22">22</xref>]. By emphasizing these aspects, the IMM enables the development of robust interoperability strategies aligned with business objectives. Overall, it is a valuable tool for health care organizations to assess their interoperability maturity and devise plans for continuous improvement [<xref ref-type="bibr" rid="ref52">52</xref>] (<xref ref-type="boxed-text" rid="box8">Textbox 8</xref> [<xref ref-type="bibr" rid="ref61">61</xref>]).</p>
          <boxed-text id="box8" position="float">
            <title>An overview of the 5 maturity levels of the infrastructure maturity model, a framework designed to evaluate the maturity of an organization’s IT infrastructure in supporting digital transformation and operational efficiency.</title>
            <p>
              <bold>Levels and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Level 1 (<italic>initial</italic>): there is no interoperability.</p>
              </list-item>
              <list-item>
                <p>Level 2 (<italic>managed</italic>): the processes of this level are beginning to be more controlled and managed—a more customized approach aids in connecting technology to community specifications or standards.</p>
              </list-item>
              <list-item>
                <p>Level 3 (<italic>defined</italic>): interoperability at the data-sharing level is characterized by documenting and formalizing technologies in the community.</p>
              </list-item>
              <list-item>
                <p>Level 4 (<italic>quantitively managed</italic>): interoperability at this process level and sharing lessons with other communities do not require customization, given the existing pre-established standardization.</p>
              </list-item>
              <list-item>
                <p>Level 5 (<italic>optimized</italic>): purchasers of connected technology shall benefit from an improved interoperability performance language, and interoperability lessons will be implemented for continued improvements.</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>TMSMM Tool</title>
          <p>The TMSMM is a comprehensive assessment tool designed to evaluate a telemedicine program’s readiness to implement and sustain a successful telemedicine initiative [<xref ref-type="bibr" rid="ref23">23</xref>]. Developed by telemedicine practitioners from 5 South African provincial health departments, it focuses on various aspects of telemedicine application, particularly during the patient treatment stage [<xref ref-type="bibr" rid="ref24">24</xref>]. This model encompasses 5 key characteristics—man, machine, material, method, and money—providing a holistic view of implementing a telemedicine service. The assessment is conducted through micro- and macro-level processes, with the maturity scale based on the generic-level indicators of the CMM.</p>
          <p>However, the TMSMM consists of 5 levels, each representing a different stage of maturity in telemedicine service delivery. These stages are based on the program’s ability to provide telemedicine services effectively and efficiently and its readiness to expand and sustain these services over time. The 5 levels are the <italic>initial stage</italic>, the <italic>experimental stage</italic>, the <italic>expansion stage</italic>, the <italic>consolidation stage</italic>, and the <italic>transformation stage</italic>. At the <italic>initial stage</italic>, telemedicine services are in their infancy phase, with limited reach. Progressing to the <italic>experimental stage</italic>, services are tested and evaluated for effectiveness [<xref ref-type="bibr" rid="ref62">62</xref>]. In the <italic>expansion stage</italic>, services are scaled up, extending their reach to more patients and health care providers. Upon entering the <italic>consolidation stage</italic>, telemedicine services are fully integrated into the health care system. They are becoming an integral part of the health care delivery model. Finally, the <italic>transformation stage</italic> represents the highest level of maturity, where telemedicine services have transformed the health care system and have led to significant improvements in patient outcomes, provider efficiency, and cost savings (<xref ref-type="boxed-text" rid="box9">Textbox 9</xref> [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]).</p>
          <boxed-text id="box9" position="float">
            <title>An overview of the 5 maturity levels of the telemedicine services maturity model, a tool for assessing the maturity of telemedicine services within health care organizations, focusing on the implementation, integration, and optimization of telehealth solutions.</title>
            <p>
              <bold>Levels and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Level 1 (<italic>initial</italic> [<italic>ad hoc</italic>]): telemedicine is used as needed, but no formal structure or governance exists.</p>
              </list-item>
              <list-item>
                <p>Level 2 (<italic>managed</italic>): telemedicine is used regularly, and some formal structures and governance are in place.</p>
              </list-item>
              <list-item>
                <p>Level 3 (<italic>standard</italic>): telemedicine is integrated into the health care delivery system, with strong stakeholder coordination.</p>
              </list-item>
              <list-item>
                <p>Level 4 (<italic>quantitively managed</italic>): telemedicine services have well-defined and managed processes in place. Processes are monitored, controlled, and continually improved.</p>
              </list-item>
              <list-item>
                <p>Level 5 (<italic>optimized</italic>): optimization is in place, and the telemedicine service is continuously monitored and improved. The goal is to achieve the highest level of efficiency and effectiveness possible.</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>DRMM Framework</title>
          <p>The DRMM is a framework designed to assess digital transformation in hospitals, primarily focusing on health care institutions in Germany. It evaluates digital maturity by analyzing organizational processes, clinical applications, and technology infrastructure [<xref ref-type="bibr" rid="ref63">63</xref>]. The model uses a structured web-based self-assessment through which hospitals evaluate their capabilities in clinical, administrative, and IT processes. These assessments generate individual scores, offer benchmarking insights, and guide strategies for digital transformation to improve patient care and hospital operations [<xref ref-type="bibr" rid="ref63">63</xref>].</p>
          <p>A key feature of the DRMM is its alignment with the funding requirements of Germany’s Hospital Future Act, linking digital maturity directly to external funding opportunities. This alignment incentivizes hospitals to engage in the self-assessment process. The model’s comprehensive methodology thoroughly evaluates IT performance, clinical workflows, system resilience, and telehealth capabilities [<xref ref-type="bibr" rid="ref63">63</xref>].</p>
          <p>The DRMM incorporates feedback from diverse stakeholders, including clinical staff, information management teams, and administrators, ensuring a broader representation of perspectives within the hospital’s digital ecosystem [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]. In addition, it provides a public dashboard for transparency, enabling hospitals to compare their scores against national benchmarks. This feature promotes competition and collaboration to improve health care delivery [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref63">63</xref>].</p>
          <p>Despite its strengths, the DRMM has limitations. It is designed to closely align with Germany’s health care policies, which may restrict applicability in countries with different regulatory frameworks or digital infrastructures [<xref ref-type="bibr" rid="ref63">63</xref>-<xref ref-type="bibr" rid="ref65">65</xref>]. The reliance on self-reported data can introduce bias because hospitals might exaggerate their capabilities to meet funding criteria or performance targets [<xref ref-type="bibr" rid="ref63">63</xref>]. Furthermore, while the model emphasizes technical and procedural dimensions, it gives limited attention to social and cultural factors, such as staff adoption of digital tools, which are crucial for effective digital transformation [<xref ref-type="bibr" rid="ref63">63</xref>].</p>
          <p>The DRMM outlines 7 maturity levels, describing the progression from basic infrastructure to fully integrated digital health systems. These levels are summarized in <xref ref-type="boxed-text" rid="box10">Textbox 10</xref> [<xref ref-type="bibr" rid="ref63">63</xref>], detailing critical aspects of digital health implementation [<xref ref-type="bibr" rid="ref48">48</xref>,<xref ref-type="bibr" rid="ref49">49</xref>,<xref ref-type="bibr" rid="ref63">63</xref>].</p>
          <boxed-text id="box10" position="float">
            <title>An overview of the 7 maturity levels of the DigitalRadar maturity model, a framework for assessing digital transformation progress in health care organizations by evaluating capabilities in digitalization, resilience, clinical processes, patient engagement, and interoperability.</title>
            <p>
              <bold>Levels and detailed descriptions</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Level 1 (<italic>structures and systems</italic>): focus on establishing the foundational IT infrastructure, including key performance indicators and software applications</p>
              </list-item>
              <list-item>
                <p>Level 2 (<italic>resilience management and performance</italic>): emphasis on IT security, resilience, and improving employee performance and satisfaction</p>
              </list-item>
              <list-item>
                <p>Level 3 (<italic>organizational control and data management</italic>): strengthening organizational control systems and enhancing data management processes</p>
              </list-item>
              <list-item>
                <p>Level 4 (<italic>clinical processes</italic>): integration of clinical processes, including decision support, order management, quality management, and flexible work processes</p>
              </list-item>
              <list-item>
                <p>Level 5 (<italic>exchange of information</italic>): implementing interoperability standards to facilitate information exchange between clinical staff, patients, and external entities</p>
              </list-item>
              <list-item>
                <p>Level 6 (<italic>telehealth</italic>): use of telemedicine technologies for remote consultations, emergency room connectivity, and telehealth networks</p>
              </list-item>
              <list-item>
                <p>Level 7 (<italic>patient participation</italic>): enabling patient access to information, participation opportunities, and use metrics to facilitate active patient engagement in their care</p>
              </list-item>
            </list>
          </boxed-text>
        </sec>
      </sec>
      <sec>
        <title>Relationship of Maturity Models in Digital Health</title>
        <p>The review of maturity models has identified several frameworks, including CMMI, IMM, CDMI, TMSMM, and DRMM, which are influenced by the foundational CMM. These models adapt and expand CMM’s principles to address specific domains and needs within digital health. Meanwhile, the CCMM is influenced by EMRAM, as it extends the model’s focus on health information sharing among stakeholders to ensure continuity of care. These frameworks (CMMI, IMM, CDMI, TMSMM, and DRMM) collectively provide a structured approach to improving processes by aligning people, processes, and technology. The CMM serves as the conceptual foundation, while subsequent models enhance its scope to offer tailored strategies for digital health transformation. <xref rid="figure2" ref-type="fig">Figure 2</xref> presents a detailed overview of the interrelationships among these DHMMs, illustrating how they build upon and complement each other to advance process improvement and digital health integration.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>A comprehensive overview of the interrelationships among the 8 digital health maturity models, highlighting connections and interactions between frameworks, overlapping domains, complementary functionalities, and unique focus areas. CCMM: continuity of care maturity model; CDMI: clinical digital maturity index; CMM: capability maturity model; CMMI: capacity maturity model integration; DRMM: DigitalRadar maturity model; EMRAM: electronic medical record adoption model; HIMSS: Healthcare Information and Management Systems Society; IMM: interoperability maturity model; NEHTA: National E-Health Transition Authority of Australia; NHS: National Health Service; SEI: Software Engineering Institute; TMSMM: telemedicine service maturity model.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e68344_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>While the CMM was not initially designed for digital health, the EMRAM has emerged as one of the most widely adopted models due to its emphasis on assessing the maturity of EMRs, a critical component of digital health. The CCMM further extends this focus by facilitating health information sharing among stakeholders to ensure continuity of care. Similarly, the DRMM, which draws on the principles of the EMRAM, evaluates hospitals’ digital transformation by measuring progress in digitalization, system resilience, clinical processes, patient engagement, and information exchange.</p>
        <p>Despite their widespread use, existing maturity models provide only a general framework for understanding the evolving digital health system. This broad focus on process improvement often limits their ability to fully capture the complexities and dynamic requirements of digital health system maturity [<xref ref-type="bibr" rid="ref51">51</xref>]. As a result, these models may fall short of delivering the precise assessments needed for effective digital transformation in health care.</p>
        <p>There is a pressing need for the refinement and further development of maturity models to ensure their continued relevance and efficacy. Enhanced models could provide a more comprehensive and detailed approach, better supporting the digital transformation efforts of health care systems.</p>
      </sec>
      <sec>
        <title>Analyzing the Maturity Levels and Domains of the 8 DHMMs</title>
        <p><xref ref-type="table" rid="table3">Table 3</xref> presents an overview of the components and shared elements of the 8 maturity models, highlighting their differences and scope. The 5 maturity levels in these models are referred to here as <italic>initial</italic>, <italic>managed</italic>, <italic>defined</italic>, <italic>qualitatively managed</italic>, and <italic>optimized</italic> (<xref rid="figure3" ref-type="fig">Figure 3</xref>). The first 3 levels are capability stages focused on developing the capabilities of the digital health system. The remaining 2 levels are advanced stages focused on using basic capabilities. Each model’s domains can be separated into 5 categories: <italic>process</italic>, <italic>information</italic>, <italic>technology</italic>, <italic>governance</italic>, and <italic>engagement</italic>. These domains help to measure the organization’s execution of strategies, processes, and initiatives.</p>
        <p>On the basis of a comprehensive review of this repository, insights into the detailed mechanisms of DHMM functionality are provided in response to the second research question. This involved aggregating information from diverse studies and models that rely on institutions such as the HIMSS and the World Health Organization as their sources, providing a clearer understanding of the key attributes of digital health maturity assessment. In addition, this review provides knowledge about how DHMMs have seemingly overlooked technologies, organizations, and societal issues. We also shed light on areas such as cybersecurity, governance structure development, the social determinants of health, and change management, which existing models overlook.</p>
        <p>It is necessary to establish process documentation and digital systems stabilization at the <italic>initial</italic> level, followed by the <italic>managed</italic> level, which formalizes and standardizes the process. Subsequently, the <italic>quantitatively managed</italic> level enables the monitoring and control of standardized processes. Finally, the <italic>optimized</italic> level involves active monitoring and enhancing the process to maximize efficiency and effectiveness. The domains in each model have distinct categories. However, they can be separated into 5 categories, each critical for digital health maturity. Governance is essential to digital health maturity because collaborative agreements between stakeholders, legal frameworks, and regulations must be established as new processes emerge.</p>
        <p>However, only half (4/8, 50%) of the existing models address the aspect of governance. The <italic>engagement</italic> domain components focus on the interaction between people and the degree of community involvement, with only 3 (38%) of the 8 models focusing on this domain. This research indicates that existing maturity models in digital health lack comprehensive coverage of critical aspects such as governance and engagement, which are essential for assessing maturity levels effectively. Therefore, developing a new integrated model is necessary to close these gaps and provide a more accurate digital health system maturity assessment.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>A summary of key characteristics, domains, and maturity levels of 8 digital health maturity models, including the capability maturity model (CMM), CMM integration (CMMI), electronic medical record adoption model (EMRAM), continuity of care maturity model (CCMM), clinical digital maturity index (CDMI), interoperability maturity model (IMM), telemedicine service maturity model (TMSMM), and DigitalRadar maturity model (DRMM).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="200"/>
            <col width="230"/>
            <col width="370"/>
            <thead>
              <tr valign="top">
                <td>Name of the model (developer; launch time frame)</td>
                <td>Characteristics</td>
                <td>Domains</td>
                <td>Levels of process maturity</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>CMM (Software Engineering Institute at Carnegie Mellon University; 1980s)</td>
                <td>A process improvement model that provides a framework for improving the quality of the software development process</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Process improvement</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Initial</p>
                    </list-item>
                    <list-item>
                      <p>Repeatable</p>
                    </list-item>
                    <list-item>
                      <p>Defined</p>
                    </list-item>
                    <list-item>
                      <p>Managed</p>
                    </list-item>
                    <list-item>
                      <p>Optimized</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>CMMI (Software Engineering Institute at Carnegie Mellon University; 2000s)</td>
                <td>A process improvement approach that provides a framework for organizations to improve their processes</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Process</p>
                    </list-item>
                    <list-item>
                      <p>Project</p>
                    </list-item>
                    <list-item>
                      <p>Engineering</p>
                    </list-item>
                    <list-item>
                      <p>Support</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Initial</p>
                    </list-item>
                    <list-item>
                      <p>Managed</p>
                    </list-item>
                    <list-item>
                      <p>Defined</p>
                    </list-item>
                    <list-item>
                      <p>Quantitatively managed</p>
                    </list-item>
                    <list-item>
                      <p>Optimized</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>EMRAM (Healthcare Information and Management Systems Society; 2006)</td>
                <td>A framework for the implementation and use of EMRs<sup>a</sup> in health care organizations</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>EMR adoption</p>
                    </list-item>
                    <list-item>
                      <p>EMR use</p>
                    </list-item>
                    <list-item>
                      <p>EMR data</p>
                    </list-item>
                    <list-item>
                      <p>EMR workflow</p>
                    </list-item>
                    <list-item>
                      <p>EMR decision support</p>
                    </list-item>
                    <list-item>
                      <p>EMR reporting</p>
                    </list-item>
                    <list-item>
                      <p>EMR optimization</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>No EMR system in place</p>
                    </list-item>
                    <list-item>
                      <p>EMR adoption—incomplete</p>
                    </list-item>
                    <list-item>
                      <p>EMR adoption—partial</p>
                    </list-item>
                    <list-item>
                      <p>EMR adoption—complete</p>
                    </list-item>
                    <list-item>
                      <p>EMR optimization—incomplete</p>
                    </list-item>
                    <list-item>
                      <p>EMR optimization—partial</p>
                    </list-item>
                    <list-item>
                      <p>EMR optimization—complete</p>
                    </list-item>
                    <list-item>
                      <p>Complete EMR; external HIE<sup>b</sup>; and data analytics, governance, disaster recovery, privacy, and security</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>CCMM (Healthcare Information and Management Systems Society; 2007; updated in 2012 and 2017)</td>
                <td>A framework for measuring the maturity of an organization’s continuity of care processes</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Governance</p>
                    </list-item>
                    <list-item>
                      <p>Engagement</p>
                    </list-item>
                    <list-item>
                      <p>Processes</p>
                    </list-item>
                    <list-item>
                      <p>Information</p>
                    </list-item>
                    <list-item>
                      <p>Technology</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Limited or no electronic communication</p>
                    </list-item>
                    <list-item>
                      <p>Basic peer-to-peer data exchange</p>
                    </list-item>
                    <list-item>
                      <p>Patient-centered clinical data using basic system-to-system exchange</p>
                    </list-item>
                    <list-item>
                      <p>Normalized patient record using structural interoperability</p>
                    </list-item>
                    <list-item>
                      <p>Care coordination based on actionable data using a semantic interoperable patient record</p>
                    </list-item>
                    <list-item>
                      <p>Community-wide patient records using applied information with patient engagement focus</p>
                    </list-item>
                    <list-item>
                      <p>Closed-loop care coordination</p>
                    </list-item>
                    <list-item>
                      <p>Knowledge-driven engagement for dynamic, multivendor, and multiorganizational interconnected health care delivery model</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>CDMI (UK National Health Service; 2013; updated in 2016)</td>
                <td>Measurement of the digital maturity of National Health Service organizations</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Capability</p>
                    </list-item>
                    <list-item>
                      <p>Technological readiness</p>
                    </list-item>
                    <list-item>
                      <p>Infrastructure components</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Digital maturity self-assessment</p>
                    </list-item>
                    <list-item>
                      <p>Readiness, capabilities, and infrastructure</p>
                    </list-item>
                    <list-item>
                      <p>Questions</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>IMM (National E-Health Transition Authority of Australia; 2010)</td>
                <td>Measurement of interoperability associated with the technical, informational, and organizational capacities of the different players involved in health services</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Data</p>
                    </list-item>
                    <list-item>
                      <p>Process</p>
                    </list-item>
                    <list-item>
                      <p>People</p>
                    </list-item>
                    <list-item>
                      <p>Technology</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Initial</p>
                    </list-item>
                    <list-item>
                      <p>Managed</p>
                    </list-item>
                    <list-item>
                      <p>Defined</p>
                    </list-item>
                    <list-item>
                      <p>Quantitively managed</p>
                    </list-item>
                    <list-item>
                      <p>Optimized</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>TMSMM (South African provincial departments of health; 2011)</td>
                <td>A tool used to assess the readiness of a telemedicine program to implement and sustain a successful telemedicine initiative</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Management</p>
                    </list-item>
                    <list-item>
                      <p>Machine</p>
                    </list-item>
                    <list-item>
                      <p>Material</p>
                    </list-item>
                    <list-item>
                      <p>Method</p>
                    </list-item>
                    <list-item>
                      <p>Money</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Initial (ad hoc)</p>
                    </list-item>
                    <list-item>
                      <p>Managed</p>
                    </list-item>
                    <list-item>
                      <p>Standard</p>
                    </list-item>
                    <list-item>
                      <p>Quantitatively managed</p>
                    </list-item>
                    <list-item>
                      <p>Optimized</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>DRMM (Healthcare Information and Management Systems Society Europe and partners, including Institute for Applied Health Services Research; 2021)</td>
                <td>A model for assessing digitalization in hospitals and evaluating funding impacts under the German Hospital Future Act</td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Evaluation of hospitals’ digitalization progress and resilience</p>
                    </list-item>
                    <list-item>
                      <p>Clinical processes</p>
                    </list-item>
                    <list-item>
                      <p>Patient participation</p>
                    </list-item>
                    <list-item>
                      <p>Information exchange</p>
                    </list-item>
                  </list>
                </td>
                <td>
                  <list list-type="order">
                    <list-item>
                      <p>Structures and systems</p>
                    </list-item>
                    <list-item>
                      <p>Resilience</p>
                    </list-item>
                    <list-item>
                      <p>Organizational control and data management</p>
                    </list-item>
                    <list-item>
                      <p>Clinical processes</p>
                    </list-item>
                    <list-item>
                      <p>Information exchange</p>
                    </list-item>
                    <list-item>
                      <p>Telehealth</p>
                    </list-item>
                    <list-item>
                      <p>Patient participation</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table3fn1">
              <p><sup>a</sup>EMR: electronic medical record.</p>
            </fn>
            <fn id="table3fn2">
              <p><sup>b</sup>HIE: health information exchange.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>A comprehensive overview of existing digital health maturity models, categorized by their maturity levels and health care domains and illustrating their respective coverage and focus areas.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e68344_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Principal Results</title>
        <sec>
          <title>Incorporating Communication Elements in DHMMs</title>
          <p>Digital communication components within the DHMM framework are crucial in completing assessments. Unlike traditional DHMMs focused on technical features, communication dimensions practically include user connectivity, acceptance, personalization, and customization, which are critical factors in digital health platforms [<xref ref-type="bibr" rid="ref51">51</xref>]. These elements can give DHMMs a coherent approach to evaluating a digital health management organization. They capture technical capabilities and examine the quality of patients’ and stakeholders’ interaction and communication experiences. This integration can uncover the benefits of digital health methods and progress regarding needs [<xref ref-type="bibr" rid="ref20">20</xref>]. The process lays the groundwork for digital health projects to align with users’ needs and preferences, leading to more efficient and popular digital health solutions.</p>
        </sec>
        <sec>
          <title>Introducing the Digital Health Communication Maturity Model</title>
          <p>The digital health communication maturity model (DHCMM) represents a paradigm shift in digital health maturity assessment. Unlike the other DHMMs, which tend to overlook the communication dimensions [<xref ref-type="bibr" rid="ref25">25</xref>], the DHCMM is unique in that it incorporates specific user-centered metrics such as satisfaction, engagement, personalization, and customization into its framework (<xref rid="figure4" ref-type="fig">Figure 4</xref>).</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>An overview of the digital health communication maturity model, a newly developed framework for evaluating digital health maturity with a distinct focus on communication dimensions often overlooked by other digital health maturity models.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e68344_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>Therefore, the DHCMM is ultimately key to assessing an organization’s readiness and capabilities for successfully implementing its digital health communication strategies [<xref ref-type="bibr" rid="ref37">37</xref>]. By blending in communication models, the framework provides a more comprehensive take on the relationships among patients, digital health tools, and communication mediums, covering the aspects of channels, messaging, and user experience [<xref ref-type="bibr" rid="ref38">38</xref>].</p>
          <p>The core idea of the DHCMM is the dual requirement to have effective communication as a driver of technology and as the primary source of success in digital health initiatives [<xref ref-type="bibr" rid="ref39">39</xref>]. Hence, communication strategies should be custom tailored to suit different user profiles, adapting to the evolving needs and preferences of a diverse population [<xref ref-type="bibr" rid="ref40">40</xref>].</p>
          <p>For a range of health care settings, from private clinics to public health campaigns and consumer-facing digital health care platforms, the DHCMM provides a structured approach to assessing communication effectiveness and identifying areas for improvement [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
          <p>In other words, the DHCMM is a product of the latest digital technology development. Its introduction in digital health evaluation represents major progress because it offers a robust framework for assessing and improving communication practices in the digital age [<xref ref-type="bibr" rid="ref39">39</xref>]. By instilling collaboration, governance, and meaningful engagements with eHealth applications, the model offers paths to more efficient and user-centered digital health development.</p>
        </sec>
        <sec>
          <title>Enhancing Assessment and Optimization</title>
          <p>Effective communication is crucial for the success of digital health initiatives, irrespective of the technological infrastructure [<xref ref-type="bibr" rid="ref13">13</xref>]. At the same time, social factors such as user experience and communication significantly influence the acceptance and use of digital health solutions. Thus, overlooking these social capability aspects during digital health maturity assessments can undermine even the most advanced technological implementations [<xref ref-type="bibr" rid="ref14">14</xref>]. In response to this dynamic nature of digital health, this review introduces the DHCMM, which addresses the limitations of existing DHMMs. The proposed model integrates DHMMs, communication, engagement factors, and technological dimensions, offering a precise road map and addressing crucial gaps to provide a nuanced view of an organization’s digital health maturity in the complex digital health landscape.</p>
          <p>Current DHMM versions primarily focus on stabilizing the digital health system. However, it is imperative to incorporate bidirectional aspects such as the CCMM and DRMM to enhance user engagement at the community level. Such additions are expected to improve the operationalization of the digital health ecosystem, extending from hospital care to community care. In this context, an expanded maturity model, as depicted in <xref rid="figure4" ref-type="fig">Figure 4</xref>, introduces an <italic>engaged</italic> stage alongside the <italic>capability</italic> and <italic>advanced</italic> stages.</p>
          <p>Level 6, the <italic>integrated</italic> level, emphasizes coordinated data and governance procedures, actively involving health care professionals, patients, and community members. Level 7, the <italic>engaged</italic> level, underscores the importance of the active involvement of organizations, community members, and physicians throughout the health care system.</p>
          <p>A 7-level framework can be used to conceptualize digital health systems. The first 3 levels—<italic>initial</italic>, <italic>managed</italic>, and <italic>defined</italic> (<italic>standard</italic>)—constitute the <italic>capability</italic> stage. The <italic>qualitatively managed</italic> and <italic>optimized</italic> levels form the <italic>advanced</italic> stage. The <italic>integrated</italic> and <italic>engaged</italic> levels emphasize active user engagement and provide a platform for the active exchange of information while developing digital health capabilities in recently adopted areas and focusing on the effective use of advanced capabilities.</p>
          <p>Overall, the proposed integrated DHCMM offers a more comprehensive approach to measuring the maturity of digital health systems, incorporating communication and engagement aspects not addressed by DHMMs. This model provides a framework for actively engaging users and stakeholders in the digital health ecosystem, emphasizing the importance of collaboration, governance, and the effective use of digital health capabilities.</p>
        </sec>
        <sec>
          <title>The 7 Domains of Maturity for Optimal Outcomes</title>
          <p>The DHCMM offers a comprehensive approach to evaluating digital health systems, incorporating crucial communication and engagement aspects overlooked by DHMMs. This model emphasizes collaboration, governance, and the effective use of digital health capabilities to actively engage users and stakeholders in the digital health ecosystem.</p>
          <p>The 7 crucial domains of maturity—<italic>process</italic>, <italic>information</italic> (or <italic>data</italic>), <italic>technology</italic>, <italic>governance</italic>, <italic>management</italic>, <italic>engagement</italic>, and <italic>communication</italic>—collectively contribute to ensuring optimal outcomes in digital health systems. The <italic>process</italic> and <italic>technology</italic> domains focus on establishing the necessary infrastructure to support digital health initiatives. <italic>Governance</italic> and <italic>management</italic> are essential in efficiently applying digital health technology, encompassing organization-wide strategy, decision-making, and process management standards. Finally, the <italic>engagement</italic> and <italic>communication</italic> domains highlight the significance of social capabilities in successful digital health implementation. <italic>Engagement</italic> involves adapting to process changes, values, beliefs, attitudes, and behaviors, while <italic>communication</italic> emphasizes effective communication and cooperation within the process management framework.</p>
          <p>The integrated DHCMM offers a comprehensive assessment of digital health system maturity, encompassing all relevant domains. Through its thorough coverage of these domains, the model ensures that systems are optimized for success, with a strong emphasis on user engagement and personalized care.</p>
        </sec>
        <sec>
          <title>Evaluating Stakeholder Alignment</title>
          <p>The effective execution of digital health programs hinges on collaborating with various stakeholders, including patients, legislators, health care professionals, and technology developers. While DHMMs have achieved significant progress in evaluating technology capabilities, the integrated DHCMM critically emphasizes stakeholder alignment. Efficient communication and cooperation among different groups are vital for aligning stakeholders and ensuring that the digital health ecosystem meets the requirements and expectations of all stakeholders. The DHCMM acknowledges the importance of this alignment within its <italic>governance</italic> and <italic>engagement</italic> domains. <italic>Governance</italic> establishes the legal frameworks and collaborative agreements, creating an environment conducive to digital health initiatives. It ensures that policies and regulations evolve alongside emerging technologies [<xref ref-type="bibr" rid="ref13">13</xref>].</p>
          <p>Moreover, the <italic>engagement</italic> domain underscores the importance of community involvement, user interaction, and effective communication techniques. Unlike traditional DHMMs focusing solely on technology infrastructure, the DHCMM acknowledges the broader scope of digital health maturity, considering the social aspects involved. It emphasizes active engagement from patients, health care professionals, and communities, recognizing their significant role in the success of digital health initiatives. The stakeholder-centered strategy of the DHCMM bridges the communication gap among important actors to achieve optimal outcomes. Likewise, technological proficiency calls for recognizing and addressing stakeholders’ various requirements, values, and beliefs [<xref ref-type="bibr" rid="ref14">14</xref>]. This concept compels enterprises to consider the human factor in digital health, understanding that successful adoption requires more than cutting-edge technology.</p>
        </sec>
        <sec>
          <title>Driving the Effective Use of Digital Health Capabilities</title>
          <p>Furthermore, the integrated DHCMM expands on the topic beyond technology by emphasizing the role of stakeholder alignment in achieving digital health maturity. Through its assessment of the efficacy of communication, engagement, and governance frameworks, the model offers an all-inclusive road map for businesses to navigate the intricacies of the digital health terrain. While digital health technologies have revolutionized health care by improving communication and patient care, the lack of a standardized measure for digital health maturity presents a significant challenge. While existing maturity models are outlined in this review, a more detailed analysis is warranted.</p>
          <p>The DHCMM also stresses the significance of persistent monitoring and evaluation in achieving progress in digital health communication strategies and battling misinformation. By latching onto key performance indicators and altering the approaches, organizations can tweak the use of their digital health capabilities and eventually improve the overall effect on health care outcomes.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study explored the development of the DHCMM to address critical gaps in existing DHMMs. The DHCMM enhances traditional DHMMs by integrating communication, engagement, and governance as core metrics, bridging technical capabilities with user-centered dimensions. The findings support the study’s aim to propose a comprehensive model that captures the dynamic and multifaceted nature of digital health systems, emphasizing communication as a pivotal factor in achieving successful digital transformation. By incorporating stakeholder collaboration and advanced engagement strategies, the DHCMM goes beyond technical assessments to provide a framework for evaluating and advancing digital health maturity.</p>
        <p>Traditional DHMMs, such as the CMMI and EMRAM, primarily prioritize technical metrics, including interoperability and data management [<xref ref-type="bibr" rid="ref56">56</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref59">59</xref>]. However, their limited focus on user engagement and communication has restricted their applicability in addressing broader health care challenges. The inclusion of communication as a core domain within the DHCMM addresses this critical gap, aligning with research emphasizing the importance of patient-centered care and personalized health interventions [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref36">36</xref>].</p>
        <p>The emphasis on communication aligns with the findings on mobile health of Smith and Magnani [<xref ref-type="bibr" rid="ref14">14</xref>], which highlight the importance of enhancing digital health literacy and patient interaction to promote equitable access to digital health tools. Similarly, Alexander et al [<xref ref-type="bibr" rid="ref26">26</xref>] underscored the structural disparities in health IT maturity, which can be mitigated by prioritizing communication and stakeholder alignment. By integrating engagement and governance, the DHCMM ensures a more holistic approach to digital health maturity, addressing the needs of diverse health care settings and populations. The DHCMM framework reflects the increasing demand for user-centered digital health solutions, aligning with the conclusions of Shaw et al [<xref ref-type="bibr" rid="ref11">11</xref>] on the safety and quality benefits of digital interventions that incorporate patient portals and decision support systems. By emphasizing personalization and satisfaction, the DHCMM fosters improved adherence to digital health tools, as evidenced by Taj et al [<xref ref-type="bibr" rid="ref66">66</xref>], who demonstrated the effectiveness of behavior change technologies when aligned with user preferences.</p>
        <p>Moreover, the inclusion of governance and engagement in the DHCMM acknowledges the intricate relationship between technological capabilities and the social determinants of health. Nyangena et al [<xref ref-type="bibr" rid="ref38">38</xref>] emphasized that governance structures and standardized technical frameworks are crucial for achieving effective interoperability and health information exchange. By incorporating governance as a core domain, the DHCMM builds upon these findings, enabling seamless collaboration among stakeholders while ensuring compliance with regulatory standards. The DHCMM’s emphasis on engagement addresses the challenges of user adoption and behavior change highlighted by Jansen-Kosterink et al [<xref ref-type="bibr" rid="ref31">31</xref>]. Their work on continuous eHealth evaluation emphasizes the importance of iterative assessments that incorporate end-user, clinical, and societal perspectives [<xref ref-type="bibr" rid="ref32">32</xref>]. By integrating these dimensions, the DHCMM offers a comprehensive road map for fostering sustainable digital health ecosystems.</p>
        <p>The findings also reveal that existing DHMMs often lack specificity in evaluating communication and engagement, as noted by Duncan et al [<xref ref-type="bibr" rid="ref28">28</xref>], who criticized current maturity assessments for being inadequate in hospital settings. The DHCMM’s 7-level framework, with stages such as <italic>integrated</italic> and <italic>engaged,</italic> provides a more refined evaluation that captures the dynamic evolution of digital health systems. This approach aligns with the work of Kolukısa Tarhan et al [<xref ref-type="bibr" rid="ref45">45</xref>], who advocated for multicriteria maturity models to address the diverse and evolving needs of health care organizations.</p>
        <p>While the DHCMM provides a comprehensive framework for assessing digital health maturity, several limitations should be considered. This model’s emphasis on communication and engagement may require significant cultural adaptation to align with diverse health care practices and societal norms. This aligns with the findings of Liaw et al [<xref ref-type="bibr" rid="ref37">37</xref>], which highlighted the cognitive overload experienced by users when integrating complex digital health toolkits. Future iterations of the DHCMM should consider incorporating simplified pathways to mitigate these challenges and enhance usability. Furthermore, the model’s effectiveness in improving health outcomes depends on accurate and context-specific performance metrics. As Vogel et al [<xref ref-type="bibr" rid="ref49">49</xref>] noted, existing quality indicators often lack the statistical sensitivity needed to measure the impact of digital transformation. Developing robust, outcome-oriented metrics will be crucial for validating the DHCMM’s efficacy.</p>
        <p>The DHCMM represents a paradigm shift in digital health maturity assessment, emphasizing the critical role of communication, engagement, and governance in driving successful digital transformation. By integrating technical, social, and organizational dimensions, the model aligns with global efforts to enhance health care delivery through digital innovation.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The broader implications of this study highlight the importance of collaborative, user-centered approaches to digital health. The DHCMM provides a versatile framework that overcomes the limitations of traditional DHMMs, fostering sustainable digital ecosystems that prioritize patient satisfaction, stakeholder alignment, and regulatory compliance. As health care systems navigate the complexities of digital transformation, the DHCMM serves as a road map for achieving maturity that is not only technologically advanced but also socially and ethically grounded. Future research should aim to validate the model’s applicability across diverse health care settings and refine its metrics to ensure continued relevance in the evolving digital health landscape.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>PRISMA checklist.</p>
        <media xlink:href="jmir_v27i1e68344_app1.docx" xlink:title="DOCX File , 32 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Database search strategy.</p>
        <media xlink:href="jmir_v27i1e68344_app2.docx" xlink:title="DOCX File , 22 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CCMM</term>
          <def>
            <p>continuity of care maturity model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CDMI</term>
          <def>
            <p>clinical digital maturity index</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CMM</term>
          <def>
            <p>capability maturity model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">CMMI</term>
          <def>
            <p>capacity maturity model integration</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">DHCMM</term>
          <def>
            <p>digital health communication maturity model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">DHMM</term>
          <def>
            <p>digital health maturity model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">DRMM</term>
          <def>
            <p>DigitalRadar maturity model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">EMR</term>
          <def>
            <p>electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">EMRAM</term>
          <def>
            <p>electronic medical record adoption model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">HIMSS</term>
          <def>
            <p>Healthcare Information and Management Systems Society</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">IMM</term>
          <def>
            <p>interoperability maturity model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">PRISMA</term>
          <def>
            <p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">TMSMM</term>
          <def>
            <p>telemedicine service maturity model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <notes>
      <title>Data Availability</title>
      <p>All data generated or analyzed during this study are included in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>GJK developed the study design, selected articles for review, conducted data analysis, and drafted the manuscript. KN contributed to the design and execution of the study by validating the search queries and providing feedback on the systematic review and the structure of the manuscript. KN also assisted in refining the manuscript. Both GJK and KN reviewed and approved the final manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Abernethy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Shaywitz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Gundlapalli</surname>
              <given-names>AV</given-names>
            </name>
            <name name-style="western">
              <surname>Weinstein</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Doraiswamy</surname>
              <given-names>PM</given-names>
            </name>
            <name name-style="western">
              <surname>Schulman</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Madhavan</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Digital health COVID-19 impact assessment: lessons learned and compelling needs</article-title>
          <source>NAM Perspect</source>
          <year>2022</year>
          <volume>2022</volume>
          <fpage>25</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/35402858"/>
          </comment>
          <pub-id pub-id-type="doi">10.31478/202201c</pub-id>
          <pub-id pub-id-type="medline">35402858</pub-id>
          <pub-id pub-id-type="pii">202201c</pub-id>
          <pub-id pub-id-type="pmcid">PMC8970223</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aceto</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Persico</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Pescapé</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The role of information and communication technologies in healthcare: taxonomies, perspectives, and challenges</article-title>
          <source>J Netw Comput Appl</source>
          <year>2018</year>
          <month>04</month>
          <volume>107</volume>
          <fpage>125</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jnca.2018.02.008</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Desmedt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Pless</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dessers</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Vandijck</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Integrating and safeguarding care: the potential role of health information technologies</article-title>
          <source>Int J Care Coord</source>
          <year>2017</year>
          <month>06</month>
          <day>27</day>
          <volume>20</volume>
          <issue>3</issue>
          <fpage>112</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1177/2053434517715781</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>Senbekov</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Saliev</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bukeyeva</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Almabayeva</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zhanaliyeva</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Aitenova</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Toishibekov</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Fakhradiyev</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>The recent progress and applications of digital technologies in healthcare: a review</article-title>
          <source>Int J Telemed Appl</source>
          <year>2020</year>
          <month>12</month>
          <day>3</day>
          <volume>2020</volume>
          <fpage>8830200</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2020/8830200"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2020/8830200</pub-id>
          <pub-id pub-id-type="medline">33343657</pub-id>
          <pub-id pub-id-type="pmcid">PMC7732404</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>Abdolkhani</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Borda</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>DeSouza</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Patient-generated health data management and quality challenges in remote patient monitoring</article-title>
          <source>JAMIA Open</source>
          <year>2019</year>
          <month>12</month>
          <volume>2</volume>
          <issue>4</issue>
          <fpage>471</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32025644"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooz036</pub-id>
          <pub-id pub-id-type="medline">32025644</pub-id>
          <pub-id pub-id-type="pii">ooz036</pub-id>
          <pub-id pub-id-type="pmcid">PMC6993998</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>Gotz</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Borland</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Data-driven healthcare: challenges and opportunities for interactive visualization</article-title>
          <source>IEEE Comput Grap Appl</source>
          <year>2016</year>
          <month>5</month>
          <volume>36</volume>
          <issue>3</issue>
          <fpage>90</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1109/mcg.2016.59</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>Rowan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Hirten</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The future of telemedicine and wearable technology in IBD</article-title>
          <source>Curr Opin Gastroenterol</source>
          <year>2022</year>
          <month>07</month>
          <day>01</day>
          <volume>38</volume>
          <issue>4</issue>
          <fpage>373</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="doi">10.1097/MOG.0000000000000845</pub-id>
          <pub-id pub-id-type="medline">35762696</pub-id>
          <pub-id pub-id-type="pii">00001574-202207000-00008</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>Sakr</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Elgammal</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Towards a comprehensive data analytics framework for smart healthcare services</article-title>
          <source>Big Data Res</source>
          <year>2016</year>
          <month>06</month>
          <volume>4</volume>
          <fpage>44</fpage>
          <lpage>58</lpage>
          <pub-id pub-id-type="doi">10.1016/j.bdr.2016.05.002</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>Keshta</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Odeh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Security and privacy of electronic health records: concerns and challenges</article-title>
          <source>Egypt Inform J</source>
          <year>2021</year>
          <month>07</month>
          <volume>22</volume>
          <issue>2</issue>
          <fpage>177</fpage>
          <lpage>83</lpage>
          <pub-id pub-id-type="doi">10.1016/j.eij.2020.07.003</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>Liaw</surname>
              <given-names>Siaw-Teng</given-names>
            </name>
            <name name-style="western">
              <surname>Godinho</surname>
              <given-names>Myron Anthony</given-names>
            </name>
          </person-group>
          <article-title>Digital health and capability maturity models-a critical thematic review and conceptual synthesis of the literature</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2023</year>
          <month>01</month>
          <day>18</day>
          <volume>30</volume>
          <issue>2</issue>
          <fpage>393</fpage>
          <lpage>406</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36451257"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocac228</pub-id>
          <pub-id pub-id-type="medline">36451257</pub-id>
          <pub-id pub-id-type="pii">6855147</pub-id>
          <pub-id pub-id-type="pmcid">PMC9846694</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shaw</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Hines</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kielly</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Impact of digital health on the safety and quality of health care</article-title>
          <source>Analysis &#38; Policy Ovservatory</source>
          <year>2018</year>
          <month>01</month>
          <day>31</day>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://apo.org.au/node/245811?utm_campaign=rss-all&#38;utm_medium=RSS&#38;utm_source=APO-feed">https://apo.org.au/node/245811?utm_campaign=rss-all&#38;utm_medium=RSS&#38;utm_source=APO-feed</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cresswell</surname>
              <given-names>Kathrin</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>Aziz</given-names>
            </name>
            <name name-style="western">
              <surname>Krasuska</surname>
              <given-names>Marta</given-names>
            </name>
            <name name-style="western">
              <surname>Heeney</surname>
              <given-names>Catherine</given-names>
            </name>
            <name name-style="western">
              <surname>Franklin</surname>
              <given-names>Bryony Dean</given-names>
            </name>
            <name name-style="western">
              <surname>Lane</surname>
              <given-names>Wendy</given-names>
            </name>
            <name name-style="western">
              <surname>Mozaffar</surname>
              <given-names>Hajar</given-names>
            </name>
            <name name-style="western">
              <surname>Mason</surname>
              <given-names>Kathy</given-names>
            </name>
            <name name-style="western">
              <surname>Eason</surname>
              <given-names>Sally</given-names>
            </name>
            <name name-style="western">
              <surname>Hinder</surname>
              <given-names>Susan</given-names>
            </name>
            <name name-style="western">
              <surname>Potts</surname>
              <given-names>Henry W W</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>Robin</given-names>
            </name>
          </person-group>
          <article-title>Reconceptualising the digital maturity of health systems</article-title>
          <source>Lancet Digit Health</source>
          <year>2019</year>
          <month>09</month>
          <volume>1</volume>
          <issue>5</issue>
          <fpage>e200</fpage>
          <lpage>e201</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S2589-7500(19)30083-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S2589-7500(19)30083-4</pub-id>
          <pub-id pub-id-type="medline">33323267</pub-id>
          <pub-id pub-id-type="pii">S2589-7500(19)30083-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bhavnani</surname>
              <given-names>Sanjeev P</given-names>
            </name>
            <name name-style="western">
              <surname>Parakh</surname>
              <given-names>Kapil</given-names>
            </name>
            <name name-style="western">
              <surname>Atreja</surname>
              <given-names>Ashish</given-names>
            </name>
            <name name-style="western">
              <surname>Druz</surname>
              <given-names>Regina</given-names>
            </name>
            <name name-style="western">
              <surname>Graham</surname>
              <given-names>Garth N</given-names>
            </name>
            <name name-style="western">
              <surname>Hayek</surname>
              <given-names>Salim S</given-names>
            </name>
            <name name-style="western">
              <surname>Krumholz</surname>
              <given-names>Harlan M</given-names>
            </name>
            <name name-style="western">
              <surname>Maddox</surname>
              <given-names>Thomas M</given-names>
            </name>
            <name name-style="western">
              <surname>Majmudar</surname>
              <given-names>Maulik D</given-names>
            </name>
            <name name-style="western">
              <surname>Rumsfeld</surname>
              <given-names>John S</given-names>
            </name>
            <name name-style="western">
              <surname>Shah</surname>
              <given-names>Bimal R</given-names>
            </name>
          </person-group>
          <article-title>2017 Roadmap for Innovation-ACC Health Policy Statement on Healthcare Transformation in the Era of Digital Health, Big Data, and Precision Health: a report of the American College of Cardiology Task Force on Health Policy Statements and Systems of Care</article-title>
          <source>J Am Coll Cardiol</source>
          <year>2017</year>
          <month>11</month>
          <day>28</day>
          <volume>70</volume>
          <issue>21</issue>
          <fpage>2696</fpage>
          <lpage>2718</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0735-1097(17)41115-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jacc.2017.10.018</pub-id>
          <pub-id pub-id-type="medline">29169478</pub-id>
          <pub-id pub-id-type="pii">S0735-1097(17)41115-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>Benjamin</given-names>
            </name>
            <name name-style="western">
              <surname>Magnani</surname>
              <given-names>Jared W</given-names>
            </name>
          </person-group>
          <article-title>New technologies, new disparities: the intersection of electronic health and digital health literacy</article-title>
          <source>Int J Cardiol</source>
          <year>2019</year>
          <month>10</month>
          <day>01</day>
          <volume>292</volume>
          <fpage>280</fpage>
          <lpage>282</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31171391"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijcard.2019.05.066</pub-id>
          <pub-id pub-id-type="medline">31171391</pub-id>
          <pub-id pub-id-type="pii">S0167-5273(18)36997-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC6660987</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arksey</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>O'Malley</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Scoping studies: towards a methodological framework</article-title>
          <source>Int J Soc Res Method</source>
          <year>2005</year>
          <month>02</month>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>19</fpage>
          <lpage>32</lpage>
          <pub-id pub-id-type="doi">10.1080/1364557032000119616</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>MDJ</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>McInerney</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Munn</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Tricco</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Khalil</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Aromataris</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Munn</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Chapter 11: scoping reviews</article-title>
          <source>JBI Reviewer's Manual</source>
          <year>2020</year>
          <publisher-loc>Adelaide, South Australia</publisher-loc>
          <publisher-name>JBI</publisher-name>
        </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>Tricco</surname>
              <given-names>Andrea C</given-names>
            </name>
            <name name-style="western">
              <surname>Lillie</surname>
              <given-names>Erin</given-names>
            </name>
            <name name-style="western">
              <surname>Zarin</surname>
              <given-names>Wasifa</given-names>
            </name>
            <name name-style="western">
              <surname>O'Brien</surname>
              <given-names>Kelly K</given-names>
            </name>
            <name name-style="western">
              <surname>Colquhoun</surname>
              <given-names>Heather</given-names>
            </name>
            <name name-style="western">
              <surname>Levac</surname>
              <given-names>Danielle</given-names>
            </name>
            <name name-style="western">
              <surname>Moher</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>Micah D J</given-names>
            </name>
            <name name-style="western">
              <surname>Horsley</surname>
              <given-names>Tanya</given-names>
            </name>
            <name name-style="western">
              <surname>Weeks</surname>
              <given-names>Laura</given-names>
            </name>
            <name name-style="western">
              <surname>Hempel</surname>
              <given-names>Susanne</given-names>
            </name>
            <name name-style="western">
              <surname>Akl</surname>
              <given-names>Elie A</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>Christine</given-names>
            </name>
            <name name-style="western">
              <surname>McGowan</surname>
              <given-names>Jessie</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>Lesley</given-names>
            </name>
            <name name-style="western">
              <surname>Hartling</surname>
              <given-names>Lisa</given-names>
            </name>
            <name name-style="western">
              <surname>Aldcroft</surname>
              <given-names>Adrian</given-names>
            </name>
            <name name-style="western">
              <surname>Wilson</surname>
              <given-names>Michael G</given-names>
            </name>
            <name name-style="western">
              <surname>Garritty</surname>
              <given-names>Chantelle</given-names>
            </name>
            <name name-style="western">
              <surname>Lewin</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Godfrey</surname>
              <given-names>Christina M</given-names>
            </name>
            <name name-style="western">
              <surname>Macdonald</surname>
              <given-names>Marilyn T</given-names>
            </name>
            <name name-style="western">
              <surname>Langlois</surname>
              <given-names>Etienne V</given-names>
            </name>
            <name name-style="western">
              <surname>Soares-Weiser</surname>
              <given-names>Karla</given-names>
            </name>
            <name name-style="western">
              <surname>Moriarty</surname>
              <given-names>Jo</given-names>
            </name>
            <name name-style="western">
              <surname>Clifford</surname>
              <given-names>Tammy</given-names>
            </name>
            <name name-style="western">
              <surname>Tunçalp</surname>
              <given-names>Özge</given-names>
            </name>
            <name name-style="western">
              <surname>Straus</surname>
              <given-names>Sharon E</given-names>
            </name>
          </person-group>
          <article-title>PRISMA Extension for Scoping Reviews (PRISMA-ScR): checklist and explanation</article-title>
          <source>Ann Intern Med</source>
          <year>2018</year>
          <month>10</month>
          <day>02</day>
          <volume>169</volume>
          <issue>7</issue>
          <fpage>467</fpage>
          <lpage>473</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.acpjournals.org/doi/abs/10.7326/M18-0850?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.7326/M18-0850</pub-id>
          <pub-id pub-id-type="medline">30178033</pub-id>
          <pub-id pub-id-type="pii">2700389</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moosapour</surname>
              <given-names>Hamideh</given-names>
            </name>
            <name name-style="western">
              <surname>Saeidifard</surname>
              <given-names>Farzane</given-names>
            </name>
            <name name-style="western">
              <surname>Aalaa</surname>
              <given-names>Maryam</given-names>
            </name>
            <name name-style="western">
              <surname>Soltani</surname>
              <given-names>Akbar</given-names>
            </name>
            <name name-style="western">
              <surname>Larijani</surname>
              <given-names>Bagher</given-names>
            </name>
          </person-group>
          <article-title>The rationale behind systematic reviews in clinical medicine: a conceptual framework</article-title>
          <source>J Diabetes Metab Disord</source>
          <year>2021</year>
          <month>06</month>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>919</fpage>
          <lpage>929</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34178868"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s40200-021-00773-8</pub-id>
          <pub-id pub-id-type="medline">34178868</pub-id>
          <pub-id pub-id-type="pii">773</pub-id>
          <pub-id pub-id-type="pmcid">PMC8212290</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>Williams</surname>
              <given-names>Patricia Ah</given-names>
            </name>
            <name name-style="western">
              <surname>Lovelock</surname>
              <given-names>Brendan</given-names>
            </name>
            <name name-style="western">
              <surname>Cabarrus</surname>
              <given-names>Tony</given-names>
            </name>
            <name name-style="western">
              <surname>Harvey</surname>
              <given-names>Marlon</given-names>
            </name>
          </person-group>
          <article-title>Improving digital hospital transformation: development of an outcomes-based infrastructure maturity assessment framework</article-title>
          <source>JMIR Med Inform</source>
          <year>2019</year>
          <month>01</month>
          <day>11</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>e12465</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2019/1/e12465/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12465</pub-id>
          <pub-id pub-id-type="medline">30632973</pub-id>
          <pub-id pub-id-type="pii">v7i1e12465</pub-id>
          <pub-id pub-id-type="pmcid">PMC6329893</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>Martin</surname>
              <given-names>Guy</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>Jonathan</given-names>
            </name>
            <name name-style="western">
              <surname>Liew</surname>
              <given-names>Felicity</given-names>
            </name>
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>Sonal</given-names>
            </name>
            <name name-style="western">
              <surname>King</surname>
              <given-names>Dominic</given-names>
            </name>
            <name name-style="western">
              <surname>Aylin</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>Ara</given-names>
            </name>
          </person-group>
          <article-title>Evaluating the impact of organisational digital maturity on clinical outcomes in secondary care in England</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <volume>2</volume>
          <fpage>41</fpage>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0118-9</pub-id>
          <pub-id pub-id-type="medline">31304387</pub-id>
          <pub-id pub-id-type="pii">118</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550220</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>Gomes</surname>
              <given-names>Jorge</given-names>
            </name>
            <name name-style="western">
              <surname>Romão</surname>
              <given-names>Mário</given-names>
            </name>
          </person-group>
          <article-title>Information system maturity models in healthcare</article-title>
          <source>J Med Syst</source>
          <year>2018</year>
          <month>10</month>
          <day>16</day>
          <volume>42</volume>
          <issue>12</issue>
          <fpage>235</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-018-1097-0</pub-id>
          <pub-id pub-id-type="medline">30327955</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-018-1097-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shaygun</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Daim</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Technology management maturity assessment model: an exploratory multi-criteria approach for healthcare organizations</article-title>
          <year>2019</year>
          <conf-name>Portland International Conference on Management of Engineering and Technology</conf-name>
          <conf-date>August 25-29, 2019</conf-date>
          <conf-loc>Portland, OR</conf-loc>
          <pub-id pub-id-type="doi">10.23919/PICMET.2019.8893755</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Dyk</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schutte</surname>
              <given-names>CSL</given-names>
            </name>
          </person-group>
          <article-title>The telemedicine service maturity model: a framework for the measurement and improvement of telemedicine services</article-title>
          <source>Telemedicine</source>
          <year>2013</year>
          <publisher-loc>Rijeka, Croatia</publisher-loc>
          <publisher-name>InTech</publisher-name>
          <fpage>217</fpage>
          <lpage>238</lpage>
        </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>Van Dyk</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schutte</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Development of a maturity model for telemedicine</article-title>
          <source>S Afr J Industrial Eng</source>
          <year>2011</year>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>61</fpage>
          <lpage>72</lpage>
          <pub-id pub-id-type="doi">10.7166/23-2-330</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>Jami Pour</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jafari</surname>
              <given-names>Sm</given-names>
            </name>
          </person-group>
          <article-title>Toward a maturity model for the application of social media in healthcare</article-title>
          <source>Online Inf Rev</source>
          <year>2019</year>
          <month>06</month>
          <day>10</day>
          <volume>43</volume>
          <issue>3</issue>
          <fpage>404</fpage>
          <lpage>425</lpage>
          <pub-id pub-id-type="doi">10.1108/OIR-02-2018-0038</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>Alexander</surname>
              <given-names>Gregory L</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Jianfang</given-names>
            </name>
            <name name-style="western">
              <surname>Powell</surname>
              <given-names>Kimberly R</given-names>
            </name>
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>Patricia W</given-names>
            </name>
          </person-group>
          <article-title>Examining structural disparities in US nursing homes: national survey of health information technology maturity</article-title>
          <source>JMIR Aging</source>
          <year>2022</year>
          <month>08</month>
          <day>23</day>
          <volume>5</volume>
          <issue>3</issue>
          <fpage>e37482</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aging.jmir.org/2022/3/e37482/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/37482</pub-id>
          <pub-id pub-id-type="medline">35998030</pub-id>
          <pub-id pub-id-type="pii">v5i3e37482</pub-id>
          <pub-id pub-id-type="pmcid">PMC9449826</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>Jeffrey</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Wu</given-names>
            </name>
            <name name-style="western">
              <surname>Narus</surname>
              <given-names>Scott P</given-names>
            </name>
            <name name-style="western">
              <surname>Clyde</surname>
              <given-names>Stephen</given-names>
            </name>
            <name name-style="western">
              <surname>Nangle</surname>
              <given-names>Barry</given-names>
            </name>
            <name name-style="western">
              <surname>Thornton</surname>
              <given-names>Sid</given-names>
            </name>
            <name name-style="western">
              <surname>Facelli</surname>
              <given-names>Julio</given-names>
            </name>
          </person-group>
          <article-title>A focus area maturity model for a statewide master person index</article-title>
          <source>Online J Public Health Inform</source>
          <year>2013</year>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>210</fpage>
          <pub-id pub-id-type="doi">10.5210/ojphi.v5i2.4669</pub-id>
          <pub-id pub-id-type="medline">23923093</pub-id>
          <pub-id pub-id-type="pii">ojphi-05-e210</pub-id>
          <pub-id pub-id-type="pmcid">PMC3733754</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Eden</surname>
              <given-names>Rebekah</given-names>
            </name>
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>Leanna</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>Ides</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>Clair</given-names>
            </name>
          </person-group>
          <article-title>Synthesizing dimensions of digital maturity in hospitals: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>03</month>
          <day>30</day>
          <volume>24</volume>
          <issue>3</issue>
          <fpage>e32994</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/3/e32994/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/32994</pub-id>
          <pub-id pub-id-type="medline">35353050</pub-id>
          <pub-id pub-id-type="pii">v24i3e32994</pub-id>
          <pub-id pub-id-type="pmcid">PMC9008527</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>Eysenbach</surname>
              <given-names>Gunther</given-names>
            </name>
          </person-group>
          <article-title>From intermediation to disintermediation and apomediation: new models for consumers to access and assess the credibility of health information in the age of Web2.0</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2007</year>
          <volume>129</volume>
          <issue>Pt 1</issue>
          <fpage>162</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="medline">17911699</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grasser</surname>
              <given-names>Michael Georg</given-names>
            </name>
            <name name-style="western">
              <surname>Schlaipfer</surname>
              <given-names>Viktoria</given-names>
            </name>
            <name name-style="western">
              <surname>Priedl</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Sorantin</surname>
              <given-names>Erich</given-names>
            </name>
          </person-group>
          <article-title>Human based digital intelligence analyses for health care ecosystems</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2018</year>
          <volume>251</volume>
          <fpage>211</fpage>
          <lpage>214</lpage>
          <pub-id pub-id-type="medline">29968640</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jansen-Kosterink</surname>
              <given-names>Stephanie</given-names>
            </name>
            <name name-style="western">
              <surname>Broekhuis</surname>
              <given-names>Marijke</given-names>
            </name>
            <name name-style="western">
              <surname>van Velsen</surname>
              <given-names>Lex</given-names>
            </name>
          </person-group>
          <article-title>Time to act mature-gearing eHealth evaluations towards technology readiness levels</article-title>
          <source>Digit Health</source>
          <year>2022</year>
          <volume>8</volume>
          <fpage>20552076221113396</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/20552076221113396?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/20552076221113396</pub-id>
          <pub-id pub-id-type="medline">35847525</pub-id>
          <pub-id pub-id-type="pii">10.1177_20552076221113396</pub-id>
          <pub-id pub-id-type="pmcid">PMC9280845</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Duncan</surname>
              <given-names>Rhona</given-names>
            </name>
            <name name-style="western">
              <surname>Eden</surname>
              <given-names>Rebekah</given-names>
            </name>
            <name name-style="western">
              <surname>Woods</surname>
              <given-names>Leanna</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>Ides</given-names>
            </name>
            <name name-style="western">
              <surname>Sullivan</surname>
              <given-names>Clair</given-names>
            </name>
          </person-group>
          <article-title>Synthesizing dimensions of digital maturity in hospitals: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>03</month>
          <day>30</day>
          <volume>24</volume>
          <issue>3</issue>
          <fpage>e32994</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/3/e32994/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/32994</pub-id>
          <pub-id pub-id-type="medline">35353050</pub-id>
          <pub-id pub-id-type="pii">v24i3e32994</pub-id>
          <pub-id pub-id-type="pmcid">PMC9008527</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kayser</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Furstrand</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rasmussen</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Monberg</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Karnoe</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>GoTO: a process-navigation tool for telehealth and -care solutions, designed to ensure an efficient trajectory from goal setting to outcome evaluation</article-title>
          <source>Informatics</source>
          <year>2022</year>
          <month>09</month>
          <day>12</day>
          <volume>9</volume>
          <issue>3</issue>
          <fpage>69</fpage>
          <pub-id pub-id-type="doi">10.3390/informatics9030069</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>Kouroubali</surname>
              <given-names>Angelina</given-names>
            </name>
            <name name-style="western">
              <surname>Papastilianou</surname>
              <given-names>Anastasia</given-names>
            </name>
            <name name-style="western">
              <surname>Katehakis</surname>
              <given-names>Dimitrios G</given-names>
            </name>
          </person-group>
          <article-title>Preliminary assessment of the interoperability maturity of healthcare digital services vs public services of other sectors</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2019</year>
          <month>08</month>
          <day>21</day>
          <volume>264</volume>
          <fpage>654</fpage>
          <lpage>658</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI190304</pub-id>
          <pub-id pub-id-type="medline">31438005</pub-id>
          <pub-id pub-id-type="pii">SHTI190304</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>Kutza</surname>
              <given-names>Jan-Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Hübner</surname>
              <given-names>Ursula</given-names>
            </name>
            <name name-style="western">
              <surname>Holmgren</surname>
              <given-names>A Jay</given-names>
            </name>
            <name name-style="western">
              <surname>Esdar</surname>
              <given-names>Moritz</given-names>
            </name>
          </person-group>
          <article-title>Patient safety informatics: criteria development for assessing the maturity of digital patient safety in hospitals</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2022</year>
          <month>05</month>
          <day>25</day>
          <volume>294</volume>
          <fpage>885</fpage>
          <lpage>889</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI220618</pub-id>
          <pub-id pub-id-type="medline">35612236</pub-id>
          <pub-id pub-id-type="pii">SHTI220618</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>Liaw</surname>
              <given-names>Siaw-Teng</given-names>
            </name>
            <name name-style="western">
              <surname>Kearns</surname>
              <given-names>Rachael</given-names>
            </name>
            <name name-style="western">
              <surname>Taggart</surname>
              <given-names>Jane</given-names>
            </name>
            <name name-style="western">
              <surname>Frank</surname>
              <given-names>Oliver</given-names>
            </name>
            <name name-style="western">
              <surname>Lane</surname>
              <given-names>Riki</given-names>
            </name>
            <name name-style="western">
              <surname>Tam</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Dennis</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>Christine</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>Grant</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>Mark</given-names>
            </name>
          </person-group>
          <article-title>The informatics capability maturity of integrated primary care centres in Australia</article-title>
          <source>Int J Med Inform</source>
          <year>2017</year>
          <month>09</month>
          <volume>105</volume>
          <fpage>89</fpage>
          <lpage>97</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2017.06.002</pub-id>
          <pub-id pub-id-type="medline">28750915</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(17)30179-X</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liaw</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Rui</given-names>
            </name>
            <name name-style="western">
              <surname>Ansari</surname>
              <given-names>Sameera</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>Jun</given-names>
            </name>
          </person-group>
          <article-title>A digital health profile and maturity assessment toolkit: cocreation and testing in the Pacific Islands</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2021</year>
          <month>03</month>
          <day>01</day>
          <volume>28</volume>
          <issue>3</issue>
          <fpage>494</fpage>
          <lpage>503</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33249472"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa255</pub-id>
          <pub-id pub-id-type="medline">33249472</pub-id>
          <pub-id pub-id-type="pii">6010572</pub-id>
          <pub-id pub-id-type="pmcid">PMC7936524</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>Nyangena</surname>
              <given-names>Job</given-names>
            </name>
            <name name-style="western">
              <surname>Rajgopal</surname>
              <given-names>Rohini</given-names>
            </name>
            <name name-style="western">
              <surname>Ombech</surname>
              <given-names>Elizabeth Adhiambo</given-names>
            </name>
            <name name-style="western">
              <surname>Oloo</surname>
              <given-names>Enock</given-names>
            </name>
            <name name-style="western">
              <surname>Luchetu</surname>
              <given-names>Humphrey</given-names>
            </name>
            <name name-style="western">
              <surname>Wambugu</surname>
              <given-names>Sam</given-names>
            </name>
            <name name-style="western">
              <surname>Kamau</surname>
              <given-names>Onesmus</given-names>
            </name>
            <name name-style="western">
              <surname>Nzioka</surname>
              <given-names>Charles</given-names>
            </name>
            <name name-style="western">
              <surname>Gwer</surname>
              <given-names>Samson</given-names>
            </name>
            <name name-style="western">
              <surname>Ndiritu Ndirangu</surname>
              <given-names>Moses</given-names>
            </name>
          </person-group>
          <article-title>Maturity assessment of Kenya's health information system interoperability readiness</article-title>
          <source>BMJ Health Care Inform</source>
          <year>2021</year>
          <month>06</month>
          <volume>28</volume>
          <issue>1</issue>
          <fpage>e100241</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://informatics.bmj.com/lookup/pmidlookup?view=long&#38;pmid=34210718"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjhci-2020-100241</pub-id>
          <pub-id pub-id-type="medline">34210718</pub-id>
          <pub-id pub-id-type="pii">bmjhci-2020-100241</pub-id>
          <pub-id pub-id-type="pmcid">PMC8252685</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>Occelli</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Scelfo</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Can we enable digital transition in healthcare delivery?: insights from a survey of telemedicine services in the Piedmont Region</article-title>
          <source>Int J E Planning Res</source>
          <year>2020</year>
          <volume>9</volume>
          <issue>2</issue>
          <fpage>43</fpage>
          <lpage>65</lpage>
          <pub-id pub-id-type="doi">10.4018/IJEPR.2020040103</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>Peytremann-Bridevaux</surname>
              <given-names>Isabelle</given-names>
            </name>
            <name name-style="western">
              <surname>Schusselé Filliettaz</surname>
              <given-names>Séverine</given-names>
            </name>
            <name name-style="western">
              <surname>Berchtold</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Grossglauser</surname>
              <given-names>Michelle</given-names>
            </name>
            <name name-style="western">
              <surname>Pavlickova</surname>
              <given-names>Andrea</given-names>
            </name>
            <name name-style="western">
              <surname>Gilles</surname>
              <given-names>Ingrid</given-names>
            </name>
          </person-group>
          <article-title>Healthcare system maturity for integrated care: results of a Swiss nationwide survey using the SCIROCCO tool</article-title>
          <source>BMJ Open</source>
          <year>2021</year>
          <month>02</month>
          <day>23</day>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>e041956</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&#38;pmid=33622945"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2020-041956</pub-id>
          <pub-id pub-id-type="medline">33622945</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2020-041956</pub-id>
          <pub-id pub-id-type="pmcid">PMC7907879</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pumplun</surname>
              <given-names>Luisa</given-names>
            </name>
            <name name-style="western">
              <surname>Fecho</surname>
              <given-names>Mariska</given-names>
            </name>
            <name name-style="western">
              <surname>Wahl</surname>
              <given-names>Nihal</given-names>
            </name>
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>Felix</given-names>
            </name>
            <name name-style="western">
              <surname>Buxmann</surname>
              <given-names>Peter</given-names>
            </name>
          </person-group>
          <article-title>Adoption of machine learning systems for medical diagnostics in clinics: qualitative interview study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>10</month>
          <day>15</day>
          <volume>23</volume>
          <issue>10</issue>
          <fpage>e29301</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/10/e29301/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/29301</pub-id>
          <pub-id pub-id-type="medline">34652275</pub-id>
          <pub-id pub-id-type="pii">v23i10e29301</pub-id>
          <pub-id pub-id-type="pmcid">PMC8556641</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reifegerste</surname>
              <given-names>Doreen</given-names>
            </name>
            <name name-style="western">
              <surname>Harst</surname>
              <given-names>Lorenz</given-names>
            </name>
            <name name-style="western">
              <surname>Otto</surname>
              <given-names>Lena</given-names>
            </name>
          </person-group>
          <article-title>Sauerbruch, STARPAHC, and SARS: historical perspectives on readiness and barriers in telemedicine</article-title>
          <source>Z Gesundh Wiss</source>
          <year>2022</year>
          <volume>30</volume>
          <issue>1</issue>
          <fpage>11</fpage>
          <lpage>20</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33777654"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10389-021-01513-1</pub-id>
          <pub-id pub-id-type="medline">33777654</pub-id>
          <pub-id pub-id-type="pii">1513</pub-id>
          <pub-id pub-id-type="pmcid">PMC7987372</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Richmond</surname>
              <given-names>Frances J</given-names>
            </name>
            <name name-style="western">
              <surname>Zapotoczny</surname>
              <given-names>Grzegorz</given-names>
            </name>
            <name name-style="western">
              <surname>Green</surname>
              <given-names>Brian</given-names>
            </name>
            <name name-style="western">
              <surname>Lokappa</surname>
              <given-names>Sowmya</given-names>
            </name>
            <name name-style="western">
              <surname>Rudnick</surname>
              <given-names>Katy</given-names>
            </name>
            <name name-style="western">
              <surname>Espinoza</surname>
              <given-names>Juan</given-names>
            </name>
            <collab>ICRS-CTIP Collaborative for Regulatory Research</collab>
          </person-group>
          <article-title>A novel maturity index for assessing medical device startups</article-title>
          <source>J Clin Transl Sci</source>
          <year>2022</year>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>e99</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36106131"/>
          </comment>
          <pub-id pub-id-type="doi">10.1017/cts.2022.436</pub-id>
          <pub-id pub-id-type="medline">36106131</pub-id>
          <pub-id pub-id-type="pii">S2059866122004368</pub-id>
          <pub-id pub-id-type="pmcid">PMC9428664</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stahl</surname>
              <given-names>Melissa</given-names>
            </name>
            <name name-style="western">
              <surname>Cheung</surname>
              <given-names>James</given-names>
            </name>
            <name name-style="western">
              <surname>Post</surname>
              <given-names>Kevin</given-names>
            </name>
            <name name-style="western">
              <surname>Valin</surname>
              <given-names>James P</given-names>
            </name>
            <name name-style="western">
              <surname>Jacobs</surname>
              <given-names>Ira</given-names>
            </name>
          </person-group>
          <article-title>Accelerating virtual health implementation following the COVID-19 pandemic: questionnaire study</article-title>
          <source>JMIR Form Res</source>
          <year>2022</year>
          <month>05</month>
          <day>16</day>
          <volume>6</volume>
          <issue>5</issue>
          <fpage>e32819</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://formative.jmir.org/2022/5/e32819/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/32819</pub-id>
          <pub-id pub-id-type="medline">35323115</pub-id>
          <pub-id pub-id-type="pii">v6i5e32819</pub-id>
          <pub-id pub-id-type="pmcid">PMC9116483</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kolukısa Tarhan</surname>
              <given-names>Ayça</given-names>
            </name>
            <name name-style="western">
              <surname>Garousi</surname>
              <given-names>Vahid</given-names>
            </name>
            <name name-style="western">
              <surname>Turetken</surname>
              <given-names>Oktay</given-names>
            </name>
            <name name-style="western">
              <surname>Söylemez</surname>
              <given-names>Mehmet</given-names>
            </name>
            <name name-style="western">
              <surname>Garossi</surname>
              <given-names>Sonia</given-names>
            </name>
          </person-group>
          <article-title>Maturity assessment and maturity models in health care: a multivocal literature review</article-title>
          <source>Digit Health</source>
          <year>2020</year>
          <volume>6</volume>
          <fpage>2055207620914772</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/2055207620914772?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/2055207620914772</pub-id>
          <pub-id pub-id-type="medline">32426151</pub-id>
          <pub-id pub-id-type="pii">10.1177_2055207620914772</pub-id>
          <pub-id pub-id-type="pmcid">PMC7216018</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tom-Aba</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Silenou</surname>
              <given-names>Bernard Chawo</given-names>
            </name>
            <name name-style="western">
              <surname>Doerrbecker</surname>
              <given-names>Juliane</given-names>
            </name>
            <name name-style="western">
              <surname>Fourie</surname>
              <given-names>Carl</given-names>
            </name>
            <name name-style="western">
              <surname>Leitner</surname>
              <given-names>Carl</given-names>
            </name>
            <name name-style="western">
              <surname>Wahnschaffe</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Strysewske</surname>
              <given-names>Maté</given-names>
            </name>
            <name name-style="western">
              <surname>Arinze</surname>
              <given-names>Chinedu Chukwujekwu</given-names>
            </name>
            <name name-style="western">
              <surname>Krause</surname>
              <given-names>Gerard</given-names>
            </name>
          </person-group>
          <article-title>The Surveillance Outbreak Response Management and Analysis System (SORMAS): digital health global goods maturity assessment</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2020</year>
          <month>04</month>
          <day>29</day>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>e15860</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2020/2/e15860/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15860</pub-id>
          <pub-id pub-id-type="medline">32347809</pub-id>
          <pub-id pub-id-type="pii">v6i2e15860</pub-id>
          <pub-id pub-id-type="pmcid">PMC7221633</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Flott</surname>
              <given-names>Kelsey</given-names>
            </name>
            <name name-style="western">
              <surname>Callahan</surname>
              <given-names>Ryan</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>Ara</given-names>
            </name>
            <name name-style="western">
              <surname>Mayer</surname>
              <given-names>Erik</given-names>
            </name>
          </person-group>
          <article-title>A patient-centered framework for evaluating digital maturity of health services: a systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>04</month>
          <day>14</day>
          <volume>18</volume>
          <issue>4</issue>
          <fpage>e75</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2016/4/e75/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.5047</pub-id>
          <pub-id pub-id-type="medline">27080852</pub-id>
          <pub-id pub-id-type="pii">v18i4e75</pub-id>
          <pub-id pub-id-type="pmcid">PMC4850277</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vogel</surname>
              <given-names>Justus</given-names>
            </name>
            <name name-style="western">
              <surname>Hollenbach</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Haering</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>Augurzky</surname>
              <given-names>Boris</given-names>
            </name>
            <name name-style="western">
              <surname>Geissler</surname>
              <given-names>Alexander</given-names>
            </name>
          </person-group>
          <article-title>The association of hospital profitability and digital maturity - an explorative study using data from the German DigitalRadar project</article-title>
          <source>Health Policy</source>
          <year>2024</year>
          <month>04</month>
          <volume>142</volume>
          <fpage>105012</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0168-8510(24)00022-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.healthpol.2024.105012</pub-id>
          <pub-id pub-id-type="medline">38422802</pub-id>
          <pub-id pub-id-type="pii">S0168-8510(24)00022-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vogel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Haering</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kuklinski</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Geissler</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Is there a relationship between hospital process digitalization and quality of care? Observational study using data from hospital quality report cards and the DigitalRadar Project</article-title>
          <source>EconStor</source>
          <year>2024</year>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.econstor.eu/bitstream/10419/299234/1/1892275503.pdf">https://www.econstor.eu/bitstream/10419/299234/1/1892275503.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Harding</surname>
              <given-names>Louise</given-names>
            </name>
            <name name-style="western">
              <surname>Marra</surname>
              <given-names>Caterina J</given-names>
            </name>
            <name name-style="western">
              <surname>Illes</surname>
              <given-names>Judy</given-names>
            </name>
          </person-group>
          <article-title>Establishing a comprehensive search strategy for Indigenous health literature reviews</article-title>
          <source>Syst Rev</source>
          <year>2021</year>
          <month>04</month>
          <day>19</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>115</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://systematicreviewsjournal.biomedcentral.com/articles/10.1186/s13643-021-01664-y"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13643-021-01664-y</pub-id>
          <pub-id pub-id-type="medline">33874997</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13643-021-01664-y</pub-id>
          <pub-id pub-id-type="pmcid">PMC8056629</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Serrano</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A review of methods used on IT maturity models development: a systematic literature review and a critical analysis</article-title>
          <source>J Inf Technol</source>
          <year>2020</year>
          <month>02</month>
          <day>17</day>
          <volume>35</volume>
          <issue>2</issue>
          <fpage>161</fpage>
          <lpage>178</lpage>
          <pub-id pub-id-type="doi">10.1177/0268396219886874</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Erdal</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>İhtiyar</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mıstıkoğlu</surname>
              <given-names>ET</given-names>
            </name>
            <name name-style="western">
              <surname>Temur</surname>
              <given-names>FT</given-names>
            </name>
          </person-group>
          <article-title>Digital maturity assessment model development for health sector</article-title>
          <source>Proceedings of the 2021 International Conference on Digitizing Production Systems</source>
          <year>2021</year>
          <conf-name>DPS '21</conf-name>
          <conf-date>October 7-9, 2021</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <fpage>131</fpage>
          <lpage>147</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oshni Alvandi</surname>
              <given-names>Abraham</given-names>
            </name>
            <name name-style="western">
              <surname>Bain</surname>
              <given-names>Chris</given-names>
            </name>
            <name name-style="western">
              <surname>Burstein</surname>
              <given-names>Frada</given-names>
            </name>
          </person-group>
          <article-title>Understanding digital health ecosystem from Australian citizens' perspective: a scoping review</article-title>
          <source>PLoS One</source>
          <year>2021</year>
          <volume>16</volume>
          <issue>11</issue>
          <fpage>e0260058</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0260058"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0260058</pub-id>
          <pub-id pub-id-type="medline">34780547</pub-id>
          <pub-id pub-id-type="pii">PONE-D-21-30359</pub-id>
          <pub-id pub-id-type="pmcid">PMC8592460</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Paulk</surname>
              <given-names>MC</given-names>
            </name>
          </person-group>
          <article-title>A history of the capability maturity model for software</article-title>
          <source>The University of Texas at Dallas</source>
          <year>2008</year>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://personal.utdallas.edu/~mcp130030/papers/p2009c.pdf">https://personal.utdallas.edu/~mcp130030/papers/p2009c.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Paulk</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Curtis</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Chrissis</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>CV</given-names>
            </name>
          </person-group>
          <article-title>Capability Maturity Model for software, Version 1.1</article-title>
          <source>Carnegie Mellon University</source>
          <year>1997</year>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://insights.sei.cmu.edu/documents/1092/1993_005_001_16211.pdf">https://insights.sei.cmu.edu/documents/1092/1993_005_001_16211.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chrissis</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Konrad</surname>
              <given-names>MD</given-names>
            </name>
            <name name-style="western">
              <surname>Shrum</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>CMMI for Development: Guidelines for Process Integration and Product Improvement, 3rd Edition</article-title>
          <source>CMU Software Engineering Institute</source>
          <year>2006</year>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://insights.sei.cmu.edu/library/cmmi-for-development-guidelines-for-process-integration-and-product-improvement-third-edition/">https://insights.sei.cmu.edu/library/cmmi-for-development-guidelines-for-process-integration-and-product-improvement-third-edition/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>CMMI Product Team</collab>
          </person-group>
          <article-title>Capability Maturity Model® Integration (CMMI), Version 1.1--continuous representation</article-title>
          <source>KiltHub</source>
          <year>2002</year>
          <month>02</month>
          <day>28</day>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://kilthub.cmu.edu/articles/report/Capability_Maturity_Model_Integration_CMMI_Version_1_1--Continuous_Representation/6572141?file=12057173">https://kilthub.cmu.edu/articles/report/Capability_Maturity_Model_Integration_CMMI_Version_1_1--Continuous_Representation/6572141?file=12057173</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ahern</surname>
              <given-names>BDM</given-names>
            </name>
            <name name-style="western">
              <surname>Clouse</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wesley</surname>
              <given-names>PA</given-names>
            </name>
          </person-group>
          <article-title>CMMI Distilled: a practical introduction to integrated process improvement</article-title>
          <source>CMU Software Engineering Institute</source>
          <year>2003</year>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://insights.sei.cmu.edu/library/cmmi-distilled-a-practical-introduction-to-integrated-process-improvement/">https://insights.sei.cmu.edu/library/cmmi-distilled-a-practical-introduction-to-integrated-process-improvement/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="web">
          <article-title>Continuity of care maturity model (CCMM)</article-title>
          <source>Healthcare Information and Management Systems Society</source>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.himss.org/what-we-do-solutions/digital-health-transformation/maturity-models/continuity-care-maturity-model-ccmm">https://www.himss.org/what-we-do-solutions/digital-health-transformation/maturity-models/continuity-care-maturity-model-ccmm</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ochoa-Urrego</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Peña-Reyes</surname>
              <given-names>JI</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Schallmo</surname>
              <given-names>DRA</given-names>
            </name>
            <name name-style="western">
              <surname>Tidd</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digital maturity models: a systematic literature review</article-title>
          <source>Digitalization. Management for Professionals</source>
          <year>2021</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>71</fpage>
          <lpage>85</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="web">
          <article-title>Interoperability Framework v2.0</article-title>
          <source>Australian Government: Digital Health Developer Portal</source>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://developer.digitalhealth.gov.au/resources/interoperability-framework-v2-0">https://developer.digitalhealth.gov.au/resources/interoperability-framework-v2-0</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Syed</surname>
              <given-names>Rehan</given-names>
            </name>
            <name name-style="western">
              <surname>Eden</surname>
              <given-names>Rebekah</given-names>
            </name>
            <name name-style="western">
              <surname>Makasi</surname>
              <given-names>Tendai</given-names>
            </name>
            <name name-style="western">
              <surname>Chukwudi</surname>
              <given-names>Ignatius</given-names>
            </name>
            <name name-style="western">
              <surname>Mamudu</surname>
              <given-names>Azumah</given-names>
            </name>
            <name name-style="western">
              <surname>Kamalpour</surname>
              <given-names>Mostafa</given-names>
            </name>
            <name name-style="western">
              <surname>Kapugama Geeganage</surname>
              <given-names>Dakshi</given-names>
            </name>
            <name name-style="western">
              <surname>Sadeghianasl</surname>
              <given-names>Sareh</given-names>
            </name>
            <name name-style="western">
              <surname>Leemans</surname>
              <given-names>Sander J J</given-names>
            </name>
            <name name-style="western">
              <surname>Goel</surname>
              <given-names>Kanika</given-names>
            </name>
            <name name-style="western">
              <surname>Andrews</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Wynn</surname>
              <given-names>Moe Thandar</given-names>
            </name>
            <name name-style="western">
              <surname>Ter Hofstede</surname>
              <given-names>Arthur</given-names>
            </name>
            <name name-style="western">
              <surname>Myers</surname>
              <given-names>Trina</given-names>
            </name>
          </person-group>
          <article-title>Digital health data quality issues: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <month>03</month>
          <day>31</day>
          <volume>25</volume>
          <fpage>e42615</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e42615/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/42615</pub-id>
          <pub-id pub-id-type="medline">37000497</pub-id>
          <pub-id pub-id-type="pii">v25i1e42615</pub-id>
          <pub-id pub-id-type="pmcid">PMC10131725</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="web">
          <article-title>DigitalRadar Hospital</article-title>
          <source>Institute for Applied Health Services Research</source>
          <year>2022</year>
          <month>02</month>
          <day>14</day>
          <access-date>2024-03-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://inav-berlin.de/digitalradar-krankenhaus/?lang=en">https://inav-berlin.de/digitalradar-krankenhaus/?lang=en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carvalho</surname>
              <given-names>JV</given-names>
            </name>
            <name name-style="western">
              <surname>Rocha</surname>
              <given-names>Á</given-names>
            </name>
            <name name-style="western">
              <surname>van de Wetering</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Abreu</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A maturity model for hospital information systems</article-title>
          <source>J Business Res</source>
          <year>2019</year>
          <month>01</month>
          <volume>94</volume>
          <fpage>388</fpage>
          <lpage>399</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jbusres.2017.12.012</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref65">
        <label>65</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Haverinen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Keränen</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Falkenbach</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Maijala</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kolehmaninen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Reponen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Digi-HTA: health technology assessment framework for digital healthcare services</article-title>
          <source>Fin J Ehealth Ewelfare</source>
          <year>2023</year>
          <month>03</month>
          <day>31</day>
          <volume>25</volume>
          <fpage>e42615</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e42615/"/>
          </comment>
          <pub-id pub-id-type="doi">10.23996/fjhw.82538</pub-id>
          <pub-id pub-id-type="pii">v25i1e42615</pub-id>
          <pub-id pub-id-type="pmcid">PMC10131725</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref66">
        <label>66</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Taj</surname>
              <given-names>Fawad</given-names>
            </name>
            <name name-style="western">
              <surname>Klein</surname>
              <given-names>Michel C A</given-names>
            </name>
            <name name-style="western">
              <surname>van Halteren</surname>
              <given-names>Aart</given-names>
            </name>
          </person-group>
          <article-title>Digital health behavior change technology: bibliometric and scoping review of two decades of research</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>12</month>
          <day>13</day>
          <volume>7</volume>
          <issue>12</issue>
          <fpage>e13311</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/12/e13311/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13311</pub-id>
          <pub-id pub-id-type="medline">31833836</pub-id>
          <pub-id pub-id-type="pii">v7i12e13311</pub-id>
          <pub-id pub-id-type="pmcid">PMC6935048</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
