<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v27i1e67328</article-id>
      <article-id pub-id-type="pmid">40408133</article-id>
      <article-id pub-id-type="doi">10.2196/67328</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Business Model Framework for Software as a Medical Device Startups in the European Union: Mixed Methods Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Sarvestan</surname>
            <given-names> Javad</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Walter</surname>
            <given-names>Johannes</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Aranda Ramos</surname>
            <given-names>Luis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Martjan</surname>
            <given-names>Rahel Sophie</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution/>
            <institution>Institute for Entrepreneurship, Technology Management and Innovation (EnTechnon)</institution>
            <institution>Karlsruhe Institute of Technology (KIT)</institution>
            <addr-line>Fritz-Erler-Str. 1-3</addr-line>
            <addr-line>Karlsruhe, 76133</addr-line>
            <country>Germany</country>
            <phone>49 721 608 47341</phone>
            <email>rahel.martjan@kit.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3768-7291</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Weimar</surname>
            <given-names>Sascha Noel</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0004-7912-5849</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Terzidis</surname>
            <given-names>Orestis</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7865-7190</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Institute for Entrepreneurship, Technology Management and Innovation (EnTechnon)</institution>
        <institution>Karlsruhe Institute of Technology (KIT)</institution>
        <addr-line>Karlsruhe</addr-line>
        <country>Germany</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Rahel Sophie Martjan <email>rahel.martjan@kit.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>23</day>
        <month>5</month>
        <year>2025</year>
      </pub-date>
      <volume>27</volume>
      <elocation-id>e67328</elocation-id>
      <history>
        <date date-type="received">
          <day>8</day>
          <month>10</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>1</day>
          <month>1</month>
          <year>2025</year>
        </date>
        <date date-type="rev-recd">
          <day>21</day>
          <month>3</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>11</day>
          <month>4</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Rahel Sophie Martjan, Sascha Noel Weimar, Orestis Terzidis. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 23.05.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/e67328" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>With the introduction of Regulation (EU) 2017/745, also known as the Medical Device Regulation (MDR), startups aiming to develop software as a medical device (SaMD) in the European Union are confronted with stringent and complex regulations, and many of them struggle with them. Complying with the MDR is a costly, time-consuming endeavor requiring expertise and substantial financial resources. However, it opens the door for new revenue models, such as reimbursement pathways. Consequently, the MDR significantly shapes the business model of startups. Early on, the regulation needs to be considered for business modeling to survive the conformity assessment process financially. Business model frameworks are tools that reduce complexity by focusing on the key aspects of a business model. Thereby, the risk of overlooking essential elements can be minimized. A framework directly integrating the MDR could alleviate the intricate circumstances in which SaMD startups are entangled.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study focused on deriving a business model framework for startups aiming to develop SaMD under the MDR. With the framework, we strived to facilitate business modeling for SaMD startups.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The study is based on a 3-step approach. First, a systematic literature review was carried out, resulting in a concept matrix and an overview of business model frameworks developed and applied in the digital health sector. Subsequently, 13 interviews were conducted with experts and startups in the SaMD industry. On the basis of the literature analysis and expert interviews, along with the MDR requirements for SaMD, we developed the SaMD business model framework.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The SaMD business model framework consists of 13 interrelated components, with the MDR being a pivotal component. The centerpiece of the framework is the “regulatory value arc,” which is the trio of intended purpose, value propositions, and customer segments. For each component, valuable input is provided, making the framework tailored to startups aiming to develop SaMD.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The findings highlight the crucial role of regulations in business modeling. Notably, the MDR is a central regulation for startups aiming to develop SaMD. The study uncovers the impact of the MDR on business modeling for SaMD startups. Our research provides a framework that integrates this regulation, thereby reducing its complexity and facilitating startups in deriving a sustainable business model. Concurrently, this research integrates the domains of business modeling and the MDR. Therefore, it contributes to the academic discourse in both fields and addresses a notable gap in the existing literature.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>digital health</kwd>
        <kwd>European Union</kwd>
        <kwd>Medical Device Regulation</kwd>
        <kwd>MDR</kwd>
        <kwd>software as a medical device</kwd>
        <kwd>entrepreneurship</kwd>
        <kwd>startup</kwd>
        <kwd>business model</kwd>
        <kwd>business model framework</kwd>
        <kwd>components</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Motivation and Objectives</title>
        <p>Regulation (EU) 2017/745, also known as the Medical Device Regulation (MDR), is highly debated. The focus of the literature concerning the MDR mainly centers on its challenges and complexity [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. The MDR is associated with strict regulatory requirements [<xref ref-type="bibr" rid="ref3">3</xref>], the involvement of multiple stakeholders [<xref ref-type="bibr" rid="ref4">4</xref>], delayed market access [<xref ref-type="bibr" rid="ref5">5</xref>], ambiguity [<xref ref-type="bibr" rid="ref6">6</xref>], and a financial burden [<xref ref-type="bibr" rid="ref7">7</xref>]. The expenses related to the MDR include costs for personnel undertaking activities to meet the requirements of the MDR. In addition, the setup, maintenance, and certification of the quality management system (QMS) are significant cost drivers. For products exceeding risk class I, fees for the conformity assessment conducted by a notified body must be considered [<xref ref-type="bibr" rid="ref8">8</xref>]. A significant cost driver is the clinical investigation [<xref ref-type="bibr" rid="ref9">9</xref>]. It requires a substantial amount of time, expertise, and potential fees for the study site. The MDR considerably impacts the business model of software as a medical device (SaMD) startups, which are challenged to incorporate the regulation into their business model. SaMD describes software intended to be used for at least 1 medical purpose, performing these purposes without being part of a hardware medical device [<xref ref-type="bibr" rid="ref10">10</xref>]. SaMD ranges from solutions primarily used by patients for treating medical conditions, such as depression, to solutions that support physicians in diagnosing and preparing treatment plans [<xref ref-type="bibr" rid="ref11">11</xref>]. SaMD also includes platforms used by physicians to monitor patients’ medical conditions [<xref ref-type="bibr" rid="ref11">11</xref>]. Simpler apps used by patients are often associated with lower risk compared to complex diagnostic tools used by physicians. For lower-risk devices, the regulatory burden under the MDR is reduced, such as in the postmarket surveillance process [<xref ref-type="bibr" rid="ref12">12</xref>] or the involvement of a notified body [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>].</p>
        <p>The requirements of the MDR apply to all medical device manufacturers irrespective of their company size [<xref ref-type="bibr" rid="ref14">14</xref>]. Consequently, they seem to disproportionately impact small-to-medium enterprises and startups [<xref ref-type="bibr" rid="ref9">9</xref>]. Often inexperienced and possessing limited resources, they face considerable barriers [<xref ref-type="bibr" rid="ref9">9</xref>]. Startups struggle with the complexity of the requirements and their lack of regulatory understanding [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. In addition, startups at an early stage find it difficult to grasp the implementation of a QMS that requires structured processes and extra effort [<xref ref-type="bibr" rid="ref14">14</xref>]. Finally, the clinical investigation, if required, is especially challenging for many startups due to its financial costs and time investments [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
        <p>Ironically, startups foster more radical innovation [<xref ref-type="bibr" rid="ref16">16</xref>] and are, therefore, a driving force in the SaMD industry. The flexibility and adaptability of startups are a door opener for digital innovations [<xref ref-type="bibr" rid="ref17">17</xref>]. The strict and complex MDR, on the one hand, and the innovative and flexible culture of startups, on the other, create the impression of a clash between 2 distinct cultures [<xref ref-type="bibr" rid="ref14">14</xref>]. Understandably, this confrontation puts startups with obstacles many cannot tackle, thereby jeopardizing innovations in the SaMD industry. According to Stern [<xref ref-type="bibr" rid="ref18">18</xref>], industry regulatory requirements are frequently linked to firms postponing or diminishing market entry due to increased time and costs. For smaller firms, it is more challenging to act as pioneers in medical device markets due to the relatively higher costs and the greater financial constraints compared to established companies [<xref ref-type="bibr" rid="ref18">18</xref>]. Nevertheless, the MDR plays a crucial role in shaping industry standards for medical devices in the EU and globally. Bradford [<xref ref-type="bibr" rid="ref19">19</xref>] describes the power of the EU to project its regulatory standards to the rest of the world as the “Brussels effect.” For example, Canada based its medical device regulations on the standards of the EU Medical Device Directives [<xref ref-type="bibr" rid="ref20">20</xref>], the predecessor of the relatively new MDR. The MDR aligns with international industry standards, facilitating market access beyond the EU.</p>
        <p>Although the literature on the challenges of the MDR, specifically for SaMD startups, is profound [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>], possible solutions to mitigate them are missing. Business model frameworks are tools that facilitate business modeling. By focusing on the key aspects only, they reduce complexity while ensuring that no crucial business components are missing. Consequently, especially in complex settings, business model frameworks are perceived as powerful tools. The situation in which startups aiming to develop SaMD are embedded is intricate, with the MDR being a significant challenge. A business model framework that directly incorporates the MDR might assist them in deriving a sustainable business model and mitigating the inherent complexity of the MDR.</p>
        <p>In the literature, a couple of business model frameworks can be found. A widely recognized [<xref ref-type="bibr" rid="ref21">21</xref>] and used tool [<xref ref-type="bibr" rid="ref22">22</xref>] is the Business Model Canvas by Osterwalder and Pigneur [<xref ref-type="bibr" rid="ref23">23</xref>]. Having no industry focus makes it a widely applicable but unspecific tool for business modeling. According to Albert and Van der Auwermeulen [<xref ref-type="bibr" rid="ref24">24</xref>], general business model frameworks, such as the Business Model Canvas, do not sufficiently account for the specifics of the health care sector. The nuances of the health care sector require a specialized business model framework [<xref ref-type="bibr" rid="ref24">24</xref>]. Therefore, there are increasing attempts to develop health-specific frameworks. One example is the framework for the telehealth sector by Velayati et al [<xref ref-type="bibr" rid="ref25">25</xref>], which is based on interviews suggesting key components of a telehealth business model. Mueller [<xref ref-type="bibr" rid="ref26">26</xref>] developed a mobile health business model framework that considers regulations. However, regulation is only included as a component and is not specified further. Outside of the digital health industry, regulations have been discussed. For example, Lindgren [<xref ref-type="bibr" rid="ref27">27</xref>] researched the impact of General Data Protection Regulations on business models, but did not derive a business model framework to work with. Ademi et al [<xref ref-type="bibr" rid="ref28">28</xref>] focused on the development of sustainable business models due to increased regulations and changing customer priorities. Still, literature regarding business modeling in regulated markets is in its infancy. More work is needed to understand the interplay between business models and regulations, particularly in highly regulated industries. To address this research gap, the primary objective of our work is to develop a comprehensive business model framework tailored for startups venturing into the development of SaMD in the EU. To achieve this pivotal goal, we formulated 3 research questions (RQs):</p>
        <list list-type="order">
          <list-item>
            <p>Which business model components and frameworks are mentioned in the digital health literature?</p>
          </list-item>
          <list-item>
            <p>Which aspects of SaMD business model are considered important by SaMD startups and experts?</p>
          </list-item>
          <list-item>
            <p>How can the results be synthesized into a conceptual framework considering the MDR?</p>
          </list-item>
        </list>
        <p>The conceptual business model framework developed in this work provides a condensed solution for startups developing SaMD. The framework incorporates the key components these startups need to consider while directly integrating the specifics of the MDR. Especially startups in the early stage tend to overlook key aspects [<xref ref-type="bibr" rid="ref14">14</xref>]. A business model framework can be instrumental in this context. Our work can assist SaMD startups in successfully entering the SaMD industry in the EU with a sustainable business model. The hurdle to entering the industry and the risk of failing during the Conformité Européenne (CE) marking process can be reduced. Theoretically, this work adds to the current discussions on the MDR by investigating its impact on business modeling and systematically incorporating it into a business model framework. In the literature on the MDR, the focus seems to be primarily on its challenges. Our work aims to develop solutions to tackle some of these challenges, thereby contributing to a rather unexplored research avenue.</p>
        <p>The remainder of this work is structured as follows: the subsequent section provides background information on the MDR and clarifies related terms. The Methods section presents the research methodology, followed by the study’s results, including the derived conceptual framework. Finally, the key findings are discussed before we conclude the work.</p>
      </sec>
      <sec>
        <title>Theoretical Background</title>
        <p>The World Health Organization defines <italic>digital health</italic> as the practice of using information and communication technology to meet health care needs [<xref ref-type="bibr" rid="ref29">29</xref>]. Digital health includes concepts such as eHealth and emerging areas such as artificial intelligence [<xref ref-type="bibr" rid="ref29">29</xref>]. Digital health technologies include SaMD [<xref ref-type="bibr" rid="ref30">30</xref>]. In the EU, SaMD, which is not an in vitro medical device, is regulated under the MDR.</p>
        <p>Aiming to increase the performance and safety of medical devices placed on the EU market [<xref ref-type="bibr" rid="ref31">31</xref>], the MDR entered into force in 2021 [<xref ref-type="bibr" rid="ref32">32</xref>], replacing the less stringent previous Medical Device Directive [<xref ref-type="bibr" rid="ref33">33</xref>]. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> provides the definition of a medical device according to article 2 of the MDR. SaMD is software intended to be used for at least 1 medical purpose, performing these purposes without being part of a hardware medical device [<xref ref-type="bibr" rid="ref10">10</xref>]. The software is intended to be used for medical purposes, such as diagnosing or treating diseases. The initial baseline for further steps in developing and approving medical devices is the determination of the intended purpose [<xref ref-type="bibr" rid="ref34">34</xref>]. The intended purpose describes the designated use of the device as intended by the manufacturer [<xref ref-type="bibr" rid="ref35">35</xref>]. For a device to qualify as a medical device, its intended purpose must be a medical purpose, in accordance with the definition of a medical device under the MDR (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <p>A startup with a product that falls within the scope of SaMD in the EU needs to fulfill the safety and performance requirements specified by the MDR. These requirements include a QMS and technical documentation, among others [<xref ref-type="bibr" rid="ref35">35</xref>]. The QMS captures processes and procedures to ensure the safety and performance of medical devices [<xref ref-type="bibr" rid="ref31">31</xref>]. The technical documentation demonstrates their compliance with the defined safety and performance requirements [<xref ref-type="bibr" rid="ref34">34</xref>]. Manufacturers are advised to apply harmonized standards and common specifications [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. This helps prove compliance with the requirements and provides guidance on the necessary actions for the CE marking. <xref ref-type="table" rid="table1">Table 1</xref> depicts the MDR’s key regulatory requirements and related standards relevant to SaMD startups. Notably, the standards mentioned in the table are not compulsory. However, they reflect the state of the art and are commonly used.</p>
        <p>Although the requirements illustrated in <xref ref-type="table" rid="table1">Table 1</xref> apply to all medical devices, the degree of detail is proportionate to the risk class. Medical devices can be classified into the following risk classes: I, IIa, IIb, and III [<xref ref-type="bibr" rid="ref34">34</xref>]. The higher the risk class, the more stringent regulatory scrutiny is required. Compared to higher-risk classes, risk class I devices do not require a notified body for conformity assessment [<xref ref-type="bibr" rid="ref13">13</xref>]. This saves the SaMD startup time and money. For risk classes III and implants, the MDR requires a clinical investigation [<xref ref-type="bibr" rid="ref35">35</xref>] to demonstrate the safety and performance of the medical device. In addition, risk class III devices require a scrutiny procedure, increasing the regulatory burden. Thus, the risk class determines the regulatory burden for SaMD startups. It also affects the business model, for example, in financial terms, due to the required clinical investigation. Furthermore, it is significant to note that the requirements of the MDR are highly interdependent. For example, risk management and software development impact each other and must, therefore, be closely integrated to fulfill the safety and performance requirements of SaMD.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Overview of key requirements regarding Regulation (EU) 2017/745, also known as the Medical Device Regulation (MDR), relevant for a software as a medical device startup.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="240"/>
            <col width="760"/>
            <thead>
              <tr valign="top">
                <td>Key requirement of the MDR</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>QMS<sup>a</sup></td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Encompasses elements such as quality planning, establishment of processes, and identification of resources [<xref ref-type="bibr" rid="ref31">31</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>ISO<sup>b</sup> 13485 is an international standard that formulates requirements for the QMS [<xref ref-type="bibr" rid="ref37">37</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Technical documentation</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Includes product-related information such as description and specification of the device, instructions for use, design, and manufacturing information [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Risk management</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Includes evaluation of identified risks and the adoption of risk control measures to eliminate or reduce risks [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>ISO 14971 formulates requirements for risk management for medical devices [<xref ref-type="bibr" rid="ref38">38</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Software life cycle</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Software needs to be developed according to the state of the art [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>IEC<sup>c</sup> 62304 reflects the state of the art for software development, from software planning to software release [<xref ref-type="bibr" rid="ref39">39</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Clinical evaluation</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Aims to generate, collect, examine, and evaluate clinical data to verify the safety and performance of a medical device [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>The basis for clinical evaluation is clinical data, which can be obtained from clinical investigations [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Usability engineering</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Aims to identify and minimize use errors and thereby reduce risks associated with the use of the device [<xref ref-type="bibr" rid="ref40">40</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>IEC 62366-1 reflects the state of the art in terms of usability engineering [<xref ref-type="bibr" rid="ref40">40</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Cyber security management</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>MDR requires IT security measures [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                    <list-item>
                      <p>IEC 81001-5-1 provides guidance on integrating IT security throughout the software life cycle [<xref ref-type="bibr" rid="ref41">41</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
              <tr valign="top">
                <td>Postmarket surveillance</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Covers activities after the medical device has been placed on the market</p>
                    </list-item>
                    <list-item>
                      <p>Includes activities such as updating clinical evaluation and identifying options to improve usability [<xref ref-type="bibr" rid="ref35">35</xref>]</p>
                    </list-item>
                  </list>
                </td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>QMS: quality management system.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>International Organization for Standardization.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>IEC: International Electrotechnical Commission.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>Our research design comprises 3 phases, as depicted in <xref rid="figure1" ref-type="fig">Figure 1</xref>. The basis for our study is the analysis of MDR requirements for SaMD. To understand MDR-related aspects, we mainly included the MDR itself [<xref ref-type="bibr" rid="ref35">35</xref>], the standards mentioned in <xref ref-type="table" rid="table1">Table 1</xref> [<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref41">41</xref>], and guidance documents provided by the Medical Device Coordination Group. The guidance documents covered the documents on clinical investigation [<xref ref-type="bibr" rid="ref42">42</xref>] and risk classification [<xref ref-type="bibr" rid="ref43">43</xref>]. Additional sources included the works of Baumgartner et al [<xref ref-type="bibr" rid="ref44">44</xref>] and Hastenteufel and Renaud [<xref ref-type="bibr" rid="ref34">34</xref>].</p>
        <p>Armed with the regulatory background information, we conducted a systematic literature review. We supplemented the results with qualitative data gathered through interviews with startups and experts in the EU SaMD industry. The input from the MDR, together with the results derived from the literature research and the expert interviews, served as the foundation for the development of the SaMD business model framework. An initial prototype was discussed within the research team, and feedback from potential users was gathered, which led to the framework presented in this work. <xref rid="figure1" ref-type="fig">Figure 1</xref> depicts the overall research design of our study.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Research design of the business model framework for software as a medical device (SaMD) startups. MDR: Medical Device Regulation (Regulation (EU) 2017/745).</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e67328_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Phase A: Systematic Literature Review</title>
        <p>A systematic literature review is a structured and transparent approach to synthesizing research [<xref ref-type="bibr" rid="ref45">45</xref>]. Kraus et al [<xref ref-type="bibr" rid="ref46">46</xref>] define 4 steps of a systematic literature review, which were followed in this work: planning the review, identifying and evaluating studies, extracting and synthesizing data, and disseminating the review findings.</p>
        <sec>
          <title>Planning the Review</title>
          <p>The main goal of the literature review was to identify business model components used in the digital health sector. Because the literature does not explicitly address the topic of SaMD business model components, we broadened our search for digital health business model components.</p>
        </sec>
        <sec>
          <title>Identifying Literature and Study Selection Strategy</title>
          <p><xref rid="figure2" ref-type="fig">Figure 2</xref> illustrates the study selection process. To identify relevant studies, we conducted a comprehensive search across four databases: Web of Science, Scopus, PubMed, and EBSCOhost. PubMed was selected because it covers medical topics. Web of Science and Scopus capture entrepreneurship literature. In EBSCOhost, the databases Academic Search Premier and Business Source Premier were chosen to account for academic and general business literature. The final search string encompasses the 2 core concepts of “digital health” and “business model,” along with related synonyms: (“digital health*” OR “electronic health*” OR ehealth* OR “e-health*” OR “mobile health*” OR mhealth* OR “m-health*” OR telehealth* OR “tele-health*” OR “connected health*” OR “connected-health*” OR medtech* OR “med-tech*” OR “medical technolog*” OR telemedic* OR “tele-medic*” OR “e-medic*” OR “electronic medic*” OR emedic* OR “digital medic*” OR “mobile medic*” OR “connected medic*”) AND (“Business Model*” OR “eBusiness Model*” OR “e-Business Model*”). After removing duplicates, we applied the inclusion and exclusion criteria to the title, abstract, and finally to the remaining full papers. Papers had to (1) be written in English, (2) be peer-reviewed articles, conference papers, or book chapters, and (3) mention business model components. Papers that presented a business model framework but did not specify the meaning of the components were excluded. This was done to avoid ambiguity and to prevent subsequent errors in the analysis. Furthermore, some papers developed business models for specific use cases. These models included components tailored to those cases and could not be generalized, making them irrelevant to our study. Papers identified in the databases that could not be accessed in full were also excluded from the study. The study selection process was conducted independently by 2 researchers. They discussed differences and reached a consensus to reduce selection bias. The systematic literature review resulted in 45 relevant papers [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref89">89</xref>] covering information about digital health business model components.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Overview of the systematic literature review on digital health business model components.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e67328_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Extracting and Synthesizing Data</title>
          <p>To synthesize the literature, we followed the approach by Webster and Watson [<xref ref-type="bibr" rid="ref90">90</xref>] and developed a concept matrix. According to Webster and Watson [<xref ref-type="bibr" rid="ref90">90</xref>], concepts define the organizational framework of a review. By reviewing the final set of papers, we gradually grouped business model components with similar meanings. To better understand the components, we looked for subcomponents and explanations for the respective constructs. Two researchers summarized the components with similar meanings and created definitions for the concepts. In case of discrepancies, 2 researchers discussed them to reach a consensus on the final concepts.</p>
          <p>We assessed the quality of the studies using the Critical Appraisal Skills Program checklist for qualitative research [<xref ref-type="bibr" rid="ref91">91</xref>]. It contains 10 questions with answer options including “yes,” “no,” and “can’t tell.” The quality of each study can be high (7-10), medium (4-6), or low (1-3). Two researchers independently filled out the checklist. Differences were discussed to reach a consensus. All studies scored 7 to 10, indicating high quality. The results are depicted in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref89">89</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>Phase B: Expert Interviews</title>
        <p>We conducted semistructured interviews to identify aspects of the business model that startups and experts in the EU SaMD industry perceived as important. The literature on business modeling for SaMD is a relatively new research avenue. Therefore, we had to expand the literature review to encompass literature on digital health in general. Interviews were crucial for our study to account for SaMD specifics. They were valuable in driving the development of the framework and enriched it with practical insights, including lessons learned and hints.</p>
        <p>We searched for interviewees through web searches. Our focus was on SaMD startups in the EU and experts, such as startup coaches in incubators or accelerators in the SaMD industry. We aimed for a well-balanced mix of founders and industry experts. Potential interviewees were contacted via email or professional networking platforms. For the interviews, we followed a semistructured approach [<xref ref-type="bibr" rid="ref92">92</xref>]. Semistructured interviews allow for flexibility in structure [<xref ref-type="bibr" rid="ref92">92</xref>,<xref ref-type="bibr" rid="ref93">93</xref>] and follow-up questions by the interviewer [<xref ref-type="bibr" rid="ref94">94</xref>]. Therefore, complex topics can be explored, and an in-depth investigation of a topic is possible. Most interviews were conducted with chief executive officers and founder or cofounders of SaMD startups, which was ideally suited for our study and significantly augmented its value. The product range of the respective startups included various solutions, such as software to monitor and treat eye diseases or software for tracking skin conditions. In addition, opinions from experts with experience across a wide range of SaMD were included. An overview of the interviewees is provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. The interviews were recorded and transcribed. Subsequently, they were inductively coded following the approach by Gioia et al [<xref ref-type="bibr" rid="ref95">95</xref>]. To ensure the objectivity of the coding, 2 researchers analyzed the transcripts and carried out the coding. Inconsistencies were discussed to derive common, aggregated dimensions.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>The interviews were conducted in accordance with the relevant ethics guidelines and were exempt from undergoing an ethical review. All participants provided informed consent and agreed to the interview. Data collected from the interviews were deidentified to ensure confidentiality.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Digital Health Business Model Components</title>
        <p>The analysis of the final 45 papers demonstrated a substantial number of papers that developed business models based on the Business Model Canvas by Osterwalder and Pigneur [<xref ref-type="bibr" rid="ref23">23</xref>], such as the papers by Bartels et al [<xref ref-type="bibr" rid="ref47">47</xref>], Chen et al [<xref ref-type="bibr" rid="ref48">48</xref>], and Christie et al [<xref ref-type="bibr" rid="ref49">49</xref>]. Apart from the Business Model Canvas, the service, technology, organization, and finance (STOF) model by Bouwman et al [<xref ref-type="bibr" rid="ref96">96</xref>] was applied to specific use cases [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. Only a few authors derived their own framework [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>]. Hwang and Christensen [<xref ref-type="bibr" rid="ref52">52</xref>] developed a business model framework for health care, incorporating 4 components: value proposition, resources, processes, and profit formula. Lin et al [<xref ref-type="bibr" rid="ref54">54</xref>] established a telemedicine framework and identified value proposition, partnership, resources, capability, service process, and cost structure as components. The remaining papers referred to other existing business model tools [<xref ref-type="bibr" rid="ref97">97</xref>-<xref ref-type="bibr" rid="ref102">102</xref>]. <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref> [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref89">89</xref>] provides an overview of the 45 papers, including their applied or derived business model frameworks.</p>
        <p>Following the approach of Webster and Watson [<xref ref-type="bibr" rid="ref90">90</xref>], we derived 14 business model components summarizing the constructs mentioned in the 45 papers. <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref> [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref89">89</xref>] depicts the concept matrix. <xref ref-type="table" rid="table2">Table 2</xref> describes the 14 derived business model components. Of the 45 papers identified, only the study by Mueller [<xref ref-type="bibr" rid="ref26">26</xref>] included regulation as a component, underlining its underrepresentation in the current digital health business model literature. The MDR, in particular, was not mentioned in any of the papers. Logically, no publication specifically focused on the business model of SaMD, underpinning the research gap. As shown in the concept matrix, value propositions and customer segments were frequently mentioned in the papers. This highlights their importance as key business model components.</p>
        <p>The general business model components identified through the systematic literature review, on their own, do not sufficiently account for the specifics of the health care system. As Albert and Van der Auwermeulen [<xref ref-type="bibr" rid="ref24">24</xref>] stated, the health care system is complex. Generic business model approaches, such as the Business Model Canvas, are inadequate to fully address its intricacies [<xref ref-type="bibr" rid="ref24">24</xref>]. Therefore, to derive a business model framework tailored to SaMD startups, we enriched the results from the systematic literature review with expert interviews from the SaMD industry in the EU.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Derived business model components from the systematic literature review and descriptions.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="750"/>
            <thead>
              <tr valign="top">
                <td>Business model component</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Customer segments</td>
                <td>Determines different groups of people the company seeks to reach and serve [<xref ref-type="bibr" rid="ref23">23</xref>].</td>
              </tr>
              <tr valign="top">
                <td>Value propositions</td>
                <td>Defines the products and services that provide value to customers [<xref ref-type="bibr" rid="ref23">23</xref>].</td>
              </tr>
              <tr valign="top">
                <td>Channels</td>
                <td>Describes the communication, distribution, and sales channels used to deliver the value propositions to customers [<xref ref-type="bibr" rid="ref23">23</xref>].</td>
              </tr>
              <tr valign="top">
                <td>Customer relationships</td>
                <td>Describes the type of relationship the company establishes with its customers [<xref ref-type="bibr" rid="ref23">23</xref>].</td>
              </tr>
              <tr valign="top">
                <td>Revenue model</td>
                <td>Explains ways to make money, including revenue streams, revenue sources, and pricing strategies.</td>
              </tr>
              <tr valign="top">
                <td>Core assets</td>
                <td>Describes the key resources required to create value.</td>
              </tr>
              <tr valign="top">
                <td>Core activities</td>
                <td>Defines the central tasks to be carried out to create and provide value to the customer.</td>
              </tr>
              <tr valign="top">
                <td>Cost structure</td>
                <td>Describes the expenses associated with running the business [<xref ref-type="bibr" rid="ref23">23</xref>].</td>
              </tr>
              <tr valign="top">
                <td>Stakeholders</td>
                <td>Groups or individuals that influence or are influenced by the fulfillment of an organization’s goals [<xref ref-type="bibr" rid="ref103">103</xref>].</td>
              </tr>
              <tr valign="top">
                <td>Digital solution</td>
                <td>Describes the key characteristics and features of the SaMD<sup>a</sup>.</td>
              </tr>
              <tr valign="top">
                <td>Key partners</td>
                <td>Delineates the collaboration with individuals or organizations.</td>
              </tr>
              <tr valign="top">
                <td>Capital and funding</td>
                <td>Describes the capital and funding needed to cover costs as well as the analysis of funding options.</td>
              </tr>
              <tr valign="top">
                <td>Market and competitors</td>
                <td>Describes the market to be entered, including its competitors.</td>
              </tr>
              <tr valign="top">
                <td>Regulation</td>
                <td>Describes the regulations to be considered.</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>SaMD: software as a medical device.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Key Aspects of Business Modeling for SaMD Startups</title>
        <p><xref ref-type="supplementary-material" rid="app6">Multimedia Appendix 6</xref> depicts the inductive coding results of the interviews, according to Gioia et al [<xref ref-type="bibr" rid="ref95">95</xref>]. The interviews made the MDR a focal aspect of SaMD business model (interviewee 10, interviewee 12, and interviewee 11). It was advised that the MDR should be considered from the beginning (interviewee 12). The interviews unequivocally demonstrated the impact of the MDR on other business model components, such as human resources, as part of core assets (interviewee 2 and interviewee 4). The MDR requires expertise that many startups lack. Therefore, ensuring the availability of human resources with the necessary knowledge to fulfill the requirements of MDR is crucial. In the interviews, the position of the quality manager was emphasized as essential (interviewee 6 and interviewee 4). It was recommended that a full-time position for a quality manager should be planned (interviewee 4). The MDR mandates the provision of “sufficient clinical evidence” [<xref ref-type="bibr" rid="ref35">35</xref>]. However, the term <italic>sufficient</italic> is left open to interpretation, leading to ambiguity (interviewee 8). In such cases, startups often find it beneficial to seek advice from experienced consultants. Consultants can provide valuable insights specific to their case. In addition, the immense financial burden of the MDR was highlighted (interviewee 5 and interviewee 10). The CE marking process is lengthy (interviewee 8). During this period, financial sustainability must be maintained. Furthermore, clinical investigations have been mentioned as significant cost drivers (interviewee 5 and interviewee 8). With its limited resources, startups often turn to consulting companies seeking assistance with the MDR (interviewee 8). This adds to the already high overall costs associated with the CE marking. A financial analysis (interviewee 11), including follow-up funding (interviewee 4), seems essential. In addition, securing follow-up funding early (interviewee 4) was mentioned to avoid falling into a financial gap. Finding investors is challenging due to the long CE marking process and the resulting delayed revenue generation (interviewee 10). Investors need “some element of faith or guided imagination of where it can go” (interviewee 7). Therefore, it is essential to start the search process early on (interviewee 7).</p>
        <p>Furthermore, the revenue model was emphasized as pivotal for the business model of SaMD startups (interviewee 8). Having the digital solution CE certified opens the door for additional revenue pathways, such as reimbursement by health insurance companies (interviewee 10). Because reimbursement systems are country specific, possible reimbursement pathways need to be considered for the target country (interviewee 10). Further revenue options are the self-payment market (interviewee 11), which is also country specific. For example, Germany was mentioned as a country with a low self-payment mentality (interviewee 10). On the contrary, Poland was named as one characterized by a relatively high self-payment mentality, where people are accustomed to spending money on their health care (interviewee 10). Thus, awareness of revenue sources and their potential in the target country is central to a viable revenue model.</p>
        <p>Understanding the health care market was described as challenging (interviewee 6). Comprehending how the market works and identifying the biggest players and their relations were mentioned as significant obstacles for startups entering the health care sector (interviewee 6). The intricate stakeholder constellation was noted by several interviewees (interviewee 10). Understanding the interests of stakeholders, together with operational dynamics, was recognized as an obstacle (interviewee 10). In this regard, health insurance companies were highlighted as stakeholders whose functioning, interests, and expectations toward SaMD startups were difficult to grasp (interviewee 10). As a result, startups struggle to derive a value proposition for health insurance companies (interviewee 10). Because value propositions are to be considered for each customer segment from all angles (interviewee 11), the health insurance company needs to be addressed in case of a reimbursement revenue model.</p>
        <p>Interviewee 9 highlighted the importance of competitor analysis. Distinct competitive advantages should be identified early (interviewee 9) to align the product accordingly. The complexity of the health care sector becomes evident once more when looking at customer segments. For SaMD startups, the user is often the patient, while the payer is the health insurance company (interviewee 6). This triangle of SaMD startup, health insurance company, and patient requires consideration. Interviewee 3 and interviewee 5 mentioned customer relationships, indicating the importance of reaching out to customers as early as possible to obtain feedback (interviewee 5). Interviewee 3 recommended creating a lock-in effect to bind the customer to the product. Key MDR-related activities mentioned were the QMS (interviewee 4) and the clinical evaluation (interviewee 5). The clinical evaluation was seen as unclearly formulated in the MDR. Terms such as “equivalent device” [<xref ref-type="bibr" rid="ref24">24</xref>] were insufficiently described and left room for interpretation (interviewee 10). Apart from MDR-related activities, further key activities mentioned included research (interviewee 9) and the setup of a sales team (interviewee 5).</p>
      </sec>
      <sec>
        <title>Phase C: Development of the SaMD Business Model Framework</title>
        <sec>
          <title>Overview</title>
          <p>In phase C (<xref rid="figure1" ref-type="fig">Figure 1</xref>), we developed the business model framework for startups aiming to develop SaMD, as shown in <xref rid="figure3" ref-type="fig">Figure 3</xref> (for a higher-quality version of the figure, please see <xref ref-type="supplementary-material" rid="app7">Multimedia Appendix 7</xref>). This was based on findings from the systematic literature review and expert interviews. It was further supplemented by MDR requirements, user feedback, and input from the research team on an initial prototype. In the following sections, we will initially address the visual layout of the framework. After that, the business model components of the SaMD business model framework will be discussed. This is followed by an analysis of the components’ interdependencies. Finally, the setting of the framework will be examined.</p>
          <fig id="figure3" position="float">
            <label>Figure 3</label>
            <caption>
              <p>Software as a medical device business model framework.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e67328_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Visual Layout</title>
          <p>The framework’s overall canvas-based structure resembles the Business Model Canvas by Osterwalder and Pigneur [<xref ref-type="bibr" rid="ref23">23</xref>]. We consciously chose this representation because familiarity with it might simplify the use of our framework. The SaMD business model framework consists of 13 components. The MDR is positioned at the top of the framework, with the remaining components being arranged below. This placement indicates that the MDR requirements emanate from above, that is, the government, and are imposed on SaMD startups. Graphically opposed to the MDR is the financial part of the business model. It encompasses the components of <italic>cost structure</italic>, <italic>revenue model,</italic> and <italic>capital and funding.</italic> The <italic>capital and funding</italic> component aims to close the gap between costs and revenues. The financial part of the business model is the basis of business operations. Metaphorically, the financial basis can be seen as the legs of the framework, which enable it to function.</p>
          <p>The centerpiece of the framework is the “regulatory value arc,” which is the trio consisting of <italic>value propositions</italic>, <italic>intended purpose</italic>, and <italic>customer segments</italic>. The dark gray color in <xref rid="figure3" ref-type="fig">Figure 3</xref> highlights the importance of this trio. Changes in the regulatory value arc would imply changes to the remaining business model components. For instance, if customer needs change, the value offering might require adjustments to fit them. The intended purpose of the device should be adjusted according to the desired value offering. An adapted intended purpose can lead to a different risk class of the device, which could potentially require a clinical investigation. With the regulatory value arc being the centerpiece of the framework, radiating in all directions, the surrounding components need to be reconsidered in case of changes. The link between <italic>value propositions</italic> and <italic>customer segments</italic> is well known through the Value Proposition Canvas by Osterwalder et al [<xref ref-type="bibr" rid="ref104">104</xref>]. The goal of the Value Proposition Canvas is to achieve a fit between customers on the one hand and the value offered by the product on the other hand [<xref ref-type="bibr" rid="ref104">104</xref>]. We identified the <italic>intended purpose</italic> as a central aspect of the MDR in this relationship. The intended purpose can be seen as the connection between <italic>value propositions</italic> and <italic>customer segments</italic>. The intended purpose of the SaMD should reflect the value offering desired by the customer. Claims regarding the clinical and nonclinical benefits of the digital solution should include values specified in the value propositions. Once clinically validated, such claims may be used for marketing purposes to raise awareness of the SaMD. The value offering can be brought to customers through <italic>channels</italic> and <italic>customer relationships</italic>.</p>
          <p>The framework has been visually designed so that its left side covers company-internal aspects of the business model, while its right side encompasses external elements. With <italic>value propositions</italic> being delivered from the company to <italic>customer segments</italic>, the internal and external sides are linked by the <italic>intended purpose</italic> from a regulatory perspective and by <italic>channels</italic> and <italic>customer relationships</italic> from a business perspective. <italic>Digital solution</italic>, <italic>core assets</italic>, and <italic>core activities</italic> are located on the company side, whereas <italic>market and competitors</italic> are placed on the external side. <italic>Stakeholders and partner network</italic> reflect both the internal and external sides. The stakeholder landscape in the SaMD industry has been described as complex and challenging to penetrate (interviewee 10). Furthermore, forming partnerships in the digital health sector is crucial (interviewee 6). The size of the component reflects its significance in the SaMD industry. Structurally, from top to bottom, <italic>core activities</italic> are positioned below the MDR. The requirements specified in the MDR directly cause a string of activities that contribute to developing the digital solution in conjunction with core assets.</p>
        </sec>
        <sec>
          <title>Description of the Business Model Components</title>
          <sec>
            <title>Regulation (EU) 2017/745 on Medical Devices</title>
            <p>The interviews highlighted the MDR as a hurdle for startups aiming to develop SaMD business model (interviewee 10). Therefore, the MDR was added as a separate business model component to the components derived in <xref ref-type="table" rid="table2">Table 2</xref> of the systematic literature review. The MDR component replaces the general regulation component. The main goal of the MDR component is to strategically consider the MDR in business modeling. Becoming aware of the key points of the MDR and its impact on the business model, not only from a financial but a comprehensive strategic perspective, is crucial for SaMD startups.</p>
            <p>The intended purpose, the cornerstone of the MDR, comprises elements such as medical purposes and claims. The medical purpose lays the foundation for subsequent regulatory steps and should be carefully and tactically considered. Furthermore, the user and the use environment are central parts of the intended purpose, which need to be addressed deliberately. Frequently, claims related to the intended medical purpose are formulated. These claims can be used for marketing once CE marking is obtained, provided they are supported by clinical evidence.</p>
          </sec>
          <sec>
            <title>Core Activities</title>
            <p>Fulfilling the requirements of the MDR covers a significant part of the core activities of SaMD startups. Standards representing the state-of-the-art approaches can be used to implement the requirements specified in the MDR (<xref ref-type="table" rid="table1">Table 1</xref>). Apart from the QMS (interviewee 4), clinical evaluation is a central activity in the life cycle management of a medical device, along with software development. Risk management and the collection of customer feedback are ongoing activities during the CE marking process and after the launch of the SaMD. After the market launch, marketing and sales add to the postmarket surveillance activities. Activities can be outsourced. However, interviewee 8 recommended doing so with caution and building knowledge internally. Putting everything in the hands of external consultancies leaves startups at their mercy (interviewee 8). Startups need to engage with the MDR internally to be able to speak to consultancies at an equal level and ask qualified questions (interviewee 8).</p>
          </sec>
          <sec>
            <title>Core Assets</title>
            <p>Interviews and the literature highlighted human resources as a core asset (interviewee 5 and interviewee 4). The composition of the internal team is central to the success of SaMD startups (interviewee 6). Early on, it was recommended that the required qualifications and competencies be identified and compared with those existing in the internal team. If gaps are identified, additional human resources are hired or qualifications are outsourced. Key roles identified were the quality manager, responsible for the QMS (interviewee 6); the risk manager; the clinical investigator; and the person responsible for regulatory compliance. The role of the person responsible for regulatory compliance received particular consideration and is actively mentioned in the MDR [<xref ref-type="bibr" rid="ref35">35</xref>].</p>
          </sec>
          <sec>
            <title>Digital Solution</title>
            <p>The <italic>digital solution</italic> component aims to describe the key aspects of the SaMD on a high level, primarily to facilitate the identification of the value offering. <italic>Digital solution</italic> includes the characteristics of the SaMD in terms of its features, design, and structure, as well as the type of digital technology and the identification of devices on which the SaMD is supposed to run.</p>
          </sec>
          <sec>
            <title>Customer Segments</title>
            <p>There are different ways of segmenting customers of SaMD startups. Possibly, the differentiation between user and payer is applicable (interviewee 6). In many cases, for SaMD startups, the payer is the health insurance company, and the user is the individual patient. Nevertheless, other options are possible, such as the self-payment market, with the user and payer being the same. Alternatively, the corporate employer could be the payer, and the employees the users of the SaMD. The needs and problems are to be determined for each identified customer segment to ensure a fit between customer needs and value offerings.</p>
          </sec>
          <sec>
            <title>Value Propositions</title>
            <p>To successfully capture the market for each customer segment, the SaMD must provide value. SaMD can provide value for individual patients by engaging them in self-treatment. Patients can be empowered, and their symptoms can be reduced. Although it seems challenging for SaMD startups to develop a value proposition for health insurance companies (interviewee 10), this is necessary if collaboration with health insurance companies is anticipated. In many cases, where there is a collaboration with the health insurance company, the latter is the payer of the product. Possible value offerings to health insurance companies are cost savings (interviewee 11) in the long term, attracting new customers with appealing products, and having satisfied customers who stay with the health insurance company. In addition, health insurance companies often require a clinical investigation that clinically proves the device’s safety and performance. Typical value offerings to physicians are time saving, additional income, and improved diagnosis or therapy.</p>
          </sec>
          <sec>
            <title>Customer Relationships</title>
            <p>A customer relationship strategy needs to be worked out for each customer segment [<xref ref-type="bibr" rid="ref15">15</xref>]. Potential customer relationships can be established and strengthened via customer hotlines, feedback management, or loyalty programs. Training on using the SaMD, for instance, at a physician’s location, can also nurture the customer relationship. Interviewee 3 recommended a lock-in effect for customer retention. Marketing is essential to customer relationship management and should be considered early on. Once the CE marking has been obtained, the SaMD does not sell itself; it needs to be advertised. For advertisement, the MDR prohibits providing misleading information concerning the device’s intended purpose. This prohibition includes suggesting uses for the device that are not specified in the intended purpose for the conformity assessment [<xref ref-type="bibr" rid="ref24">24</xref>]. Since all claims made in the intended purpose must be supported by clinical evidence, only those that are clinically validated may be used for marketing purposes on the website, social media platforms, and other marketing platforms.</p>
          </sec>
          <sec>
            <title>Channels</title>
            <p><italic>Channels</italic> encompasses sales, distribution, and communication channels [<xref ref-type="bibr" rid="ref23">23</xref>]. The channel type depends on the customer segment, customer needs and preferences, and the selected revenue model. Because many SaMDs are apps, common sales channels are app stores, such as Google Play Store and Apple App Store. In a reimbursement model with a health insurance company, the health insurance company can act as a distribution channel by sending activation codes for downloading the SaMD to the end user. Because physicians can prescribe SaMDs, such as digital health applications (DiGAs) in Germany, they can also be part of the distribution channel. Common communication channels for SaMD startups are the website or the health insurance company that promotes SaMD via their existing channels.</p>
          </sec>
          <sec>
            <title>Market and Competitors</title>
            <p>The health care market is described as being complex [<xref ref-type="bibr" rid="ref105">105</xref>]. Understanding how it functions is crucial before entering it. The target country’s market analysis should include an investigation of the established health insurance system. In addition, the target market segment needs to be thoroughly inspected. This inspection should include reviewing existing solutions and trends in the market segment, as well as determining the expected serviceable obtainable market. Notably, analyzing competitors is essential for both understanding the target market segment and developing product differentiation strategies. For the competitor analysis, not only current but also historic and potential future competitors should be investigated.</p>
            <p>The MDR has been perceived as a regulatory challenge for SaMD startups when developing SaMD (interviewee 10). Nevertheless, further regulations that might be specific to markets or products should be considered and checked for relevance. These regulations include, for example, the General Data Protection Regulation, the EU Artificial Intelligence Act, and country-specific regulations.</p>
          </sec>
          <sec>
            <title>Stakeholders and Partner Network</title>
            <p>Although the health care ecosystem is difficult to navigate, it is fundamental to identify its actors, their roles, and interests. Understanding the relationship between stakeholders is crucial for developing effective stakeholder management. In the interviews, health insurance companies were described as stakeholders that are difficult to understand (interviewee 10). Nevertheless, they are crucial to analyze. Once stakeholders have been analyzed for their roles and interests, their handling needs to be determined. Stakeholder management can vary between SaMD startups. For example, interviewee 11 mentioned their early collaboration with health insurance companies.</p>
            <p>Moreover, notified bodies are essential stakeholders for all medical devices with a risk class higher than risk class I. Given the long waiting times (interviewee 10) in some countries, identifying potential notified bodies early is crucial.</p>
            <p>The interviews highlighted the importance of having partners (interviewee 6). A partner network is crucial, especially in the digital health sector (interviewee 6). Potential partners could be local sales teams, health insurance companies, strategic investors, or clinics involved in the clinical investigation. Research institutions, pharmaceutical companies, and medical technology companies should also be considered possible collaborators. Partners can be essential stakeholders in accessing expertise and resources, such as patients, for clinical investigation and to increase credibility.</p>
          </sec>
          <sec>
            <title>Cost Structure</title>
            <p>The CE marking process is costly, especially for startups, which often lack financial resources. The required human resources represent a significant cost driver, including, for example, external consultants for support and, if necessary, the involvement of a notified body. Furthermore, the clinical investigation can be expensive. For SaMD startups, awareness of the additional investments incurred in conjunction with the CE marking is essential. Even after the CE marking has been obtained, costs will not diminish. With the postmarket surveillance activities, fulfilling the requirements of the MDR remains a significant cost driver. In addition, costs for marketing and sales are added. Interviewee 11 emphasized the considerable costs of building a sales team.</p>
          </sec>
          <sec>
            <title>Revenue Model</title>
            <p>The CE marking opens the door for new revenue models. The CE marking is not necessarily required for products in the self-payment market, provided that the product can be legitimately positioned in a way that it does not qualify as a medical device. Nevertheless, the decision to forgo the CE marking should be made carefully, as the CE marking is often perceived as a hallmark of quality and trust. For reimbursement with health insurance companies, the CE marking and a clinical investigation are often necessary for collaboration. The specific reimbursement options are specific to countries and products. In Germany, for example, DiGA is a possible reimbursement option for SaMDs that aim to get reimbursed by all statutory health insurance companies. To become a DiGA, the SaMD needs to fulfill additional national requirements.</p>
          </sec>
          <sec>
            <title>Capital and Funding</title>
            <p>Due to the delayed revenues and high expense levels, capital and funding should be well planned. Because small businesses often lack financial resources [<xref ref-type="bibr" rid="ref106">106</xref>], funding options, such as private equity and debt financing, should be considered. Funding options should be examined early on. Obtaining the CE marking is a lengthy process that delays revenue generation, making it difficult to identify investors (interviewee 10). Once funding is secured, follow-up funding options should be considered early on (interviewee 4) to avoid falling into a financial gap.</p>
          </sec>
          <sec>
            <title>Interdependencies</title>
            <p><xref rid="figure4" ref-type="fig">Figure 4</xref> depicts the interdependencies between each of the business model components. As shown in the figure, changing 1 component of the SaMD business model framework impacts the remaining components directly or indirectly via other components. For example, if <italic>customer segments</italic> change, likely <italic>value propositions</italic> will change due to the resulting alterations in the needs and preferences of the adapted customer segments. <italic>Customer relationships</italic> and <italic>channels</italic> are specific to each customer segment and need to be revised accordingly. With a changed value offering, the <italic>digital solution</italic> needs to be reconsidered, and therefore, <italic>core assets</italic> and <italic>core activities</italic> necessary to derive the value offering need to be reconsidered as well. An adapted SaMD translates into modified <italic>stakeholders and partner network</italic> and adjusted costs necessary to develop the solution. Revenues also depend on the type of digital solution, and funding, in turn, depends on costs and revenues. An adapted digital solution requires a modified market and competitor analysis. Likewise, an adapted digital solution might imply changes in the intended purpose, thereby requiring an adjustment of the risk class. In summary, the business model components of the SaMD business model framework are interdependent. It is noteworthy that the requirements, as listed in <xref ref-type="table" rid="table1">Table 1</xref>, remain consistent for each SaMD. However, what might change is the extent and precise implementation of the requirements, which depend on the risk class of the SaMD and are therefore driven by its intended purpose.</p>
            <fig id="figure4" position="float">
              <label>Figure 4</label>
              <caption>
                <p>Interdependencies of the software as a medical device business model components.</p>
              </caption>
              <graphic xlink:href="jmir_v27i1e67328_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
          </sec>
          <sec>
            <title>Setting</title>
            <p>The SaMD business model framework targets startups aiming to develop SaMD under the MDR. Startups experience different development phases. We followed the 4 development stages applied in the work by Santisteban and Mauricio [<xref ref-type="bibr" rid="ref107">107</xref>]: seed, early, growth, and expansion. In the seed stage, startups usually have a first product idea in mind and develop an initial draft of a business model. With a rough software product idea in the digital health sector in mind, startups assess whether their product falls under the MDR and fulfills the criteria of SaMD. In such a scenario, where the product fulfills the criteria of SaMD, startups begin using the SaMD business model framework. It assists in ensuring that all critical aspects of business modeling are considered early on while directly strategically integrating the central aspects of the MDR on a high level. Instead of being caught up in the intricate details of the MDR requirements, the framework provides a holistic picture and aims to strategically consider the MDR in business modeling. Often, startups in the seed and early stages lack regulatory expertise and are overwhelmed by the requirements of the MDR. The framework, with its strategically crafted guiding questions, supports SaMD startups in navigating the MDR. An additional use case of the framework is when startups decide which revenue model to choose. With a product idea in mind, the question of how to possibly earn money with it arises. For reimbursement by health insurance companies, such as through DiGA, the software must be SaMD and fulfill the requirements of the MDR. In these instances, the framework unfolds its strength. It showcases what the business model would look like, considering the MDR. Instead of focusing on financial implications, the framework provides a holistic picture of integrating the MDR in business modeling. <xref ref-type="supplementary-material" rid="app8">Multimedia Appendix 8</xref> shows an example filled-out version of the framework.</p>
            <p>Business models are not one-time concepts [<xref ref-type="bibr" rid="ref108">108</xref>]. Instead, they are derived iteratively over time and are subject to change. Especially in highly regulated sectors, such as the SaMD sector, startups need to remain agile, stay updated with regulatory developments, and adjust their business models as needed. This need for adaptability includes potential changes to the MDR and upcoming relevant regulations, such as the EU Artificial Intelligence Act.</p>
          </sec>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary</title>
        <p>The MDR is a complex and challenging topic, especially for startups with limited resources. As the expert interviews demonstrated, the impact of the MDR on business modeling for startups aiming to obtain the CE marking for their SaMD is vast; however, it is underresearched, as the systematic literature review has illustrated. Therefore, the objective of this study was to understand the relationship between MDR and business modeling and to derive a business model framework that supports SaMD startups in developing a business model. To achieve this goal, we followed a 3-step approach. First, we conducted a systematic literature review to identify business model components relevant to the digital health sector. In total, 45 papers were identified. The review highlighted the lack of analysis of business models specific to SaMD startups. To make our conceptual framework tailored to SaMD startups, we conducted, in a second step, 13 expert interviews with specialists in the EU SaMD industry. We enriched the results with feedback from potential users and the research team on an initial prototype. Furthermore, we supplemented the results with the requirements of the MDR, including related literature and state-of-the-art standards. On the basis of this input, we conceptualized the SaMD business model framework depicted in this work.</p>
      </sec>
      <sec>
        <title>Principal Findings</title>
        <p>The interviews and the literature unveiled that existing business model frameworks, such as the Business Model Canvas by Osterwalder and Pigneur [<xref ref-type="bibr" rid="ref23">23</xref>], reach their limits regarding industry-specific cases. SaMD startups are embedded in a complex digital health care system with multiple stakeholders and a tricky customer constellation. The situation of SaMD startups is challenging due to many factors, and implementing the MDR in addition to these factors makes the challenge even greater. For business modeling, the MDR can be seen as a driving force impacting the entire business model, while being a pivotal component itself. Therefore, the SaMD business model framework is designed from a startup’s perspective, with the aim of developing SaMD business model. The MDR is considered in each derived business model component, facilitating business modeling for SaMD startups. In addition, the visual layout of the framework delineates the relation between business model components and demonstrates how the MDR fits into this constellation.</p>
        <p>The MDR is not the only regulation that SaMD startups need to consider. Country-specific laws on marketing, taxes, or labor, as well as EU-wide regulations, such as the General Data Protection Regulation, need to be considered. Undoubtedly, these regulations have a ripple effect on business modeling as well. However, among all these regulations, the MDR seems to hold a special position because of its complexity, setting a series of consequential tasks. Evidently, in the interviews with SaMD startups and experts in this industry, the MDR has been highlighted as a hurdle in business modeling (interviewee 10 and interviewee 11). Furthermore, the regulatory value arc depicted in <xref rid="figure3" ref-type="fig">Figure 3</xref> illustrates the close interrelation between the <italic>intended purpose</italic>, <italic>value propositions</italic>, and <italic>customer segments</italic>, underlining the embeddedness of the MDR in the business model of SaMD startups. Consequently, the MDR’s pivotal role needs to be directly integrated into the business modeling of SaMD startups.</p>
        <p>Furthermore, we want to mention the identified regulatory value arc as another principal finding of our study. The trio of <italic>intended purpose</italic>, <italic>value propositions</italic>, and <italic>customer segments</italic> is the centerpiece of the framework and warrants particular attention. Although the link between <italic>value propositions</italic> and <italic>customer segments</italic> is well known, we identified the notable impact of the MDR on this duo, highlighting the extensive role of the MDR in business modeling. The intended purpose describes the designated use of the device as intended by the manufacturer and needs to cover at least 1 medical purpose to qualify as a medical device [<xref ref-type="bibr" rid="ref35">35</xref>]. The user, use environment, potential contraindications, and claims, along with possible disclaimers, are formulated apart from the medical purpose. The description of the users and the link to customer segments are evident. Besides, claims are statements that can be used to advertise SaMD. Claims should reflect the value offering desired by the customer to ensure customer needs are met with the SaMD. Therefore, the intended purpose, as the cornerstone of the MDR, is the pivotal element bridging value propositions and customer segments, forming the trio “regulatory value arc”<italic>.</italic> With the intended purpose, a connection between the company-internal side of the business model framework and the external side of the framework is established. Claims formed in the context of the intended purpose are carried out via channels and customer relationships from the company to the customers. Thus, for a startup aiming to develop SaMD, it is imperative to consider the regulatory value arc.</p>
        <p>In the interviews and the literature, the clinical investigation was mentioned as a significant hurdle in the context of the MDR (interviewee 10). Studies are expensive and time consuming. They slow down the launch of the SaMD on the market. Data from clinical investigations are mandatory for risk class III and implantable medical devices [<xref ref-type="bibr" rid="ref109">109</xref>]. For the remaining risk classes, a clinical investigation does not need to be undertaken if sufficient clinical data for performing the clinical evaluation can be obtained from literature or other sources from equivalent devices. Following this line of reasoning, innovative products are unlikely to refer to existing clinical data, requiring them to conduct their own clinical investigations. In that sense, startups with innovative products have ironically a disadvantage with the MDR compared to less innovative products. For less innovative products, clinical data are often already on the market.</p>
        <p>Each clinical benefit claim included in the intended purpose needs clinical evidence. Reflecting on the challenges of the clinical investigation mentioned earlier, it is worth trying to circumvent the clinical investigation by adapting the intended purpose. This consideration must be thoroughly evaluated. Possible advantages include cost and time savings, while potential disadvantages may involve an adjusted product focus and challenges in collaborating with health insurance companies.</p>
      </sec>
      <sec>
        <title>Theoretical and Practical Implications</title>
        <p>Our work has several theoretical and practical contributions. From a theoretical perspective, our work contributes to both digital health literature and business model literature. Although the literature on business models is vast, the impact of regulations on business modeling has not been sufficiently investigated. Business model frameworks, such as the Business Model Canvas by Osterwalder and Pigneur [<xref ref-type="bibr" rid="ref23">23</xref>], do not explicitly include regulation in the framework. This can be fatal when regulations such as the MDR occupy a pivotal role that significantly impacts the business modeling process. In our work, we investigated the impact of the MDR on business modeling for SaMD startups. Our work clearly showed that the MDR plays a central role in the business model of SaMD startups and needs to be considered from the beginning. This study lays a foundation for a research stream examining business modeling for SaMD startups specifically and the relationship between regulations and business models. Furthermore, the literature on SaMD startups mainly focuses on their challenges, especially in the context of the MDR. Concrete solutions for how these challenges can be tackled are missing. Our work provides a way to address some of these hurdles. This work lays the groundwork for a solution-oriented approach to tackling SaMD startups’ challenges by providing a SaMD business model framework.</p>
        <p>From a practical perspective, the derived SaMD business model framework provides a hands-on and all-in-one solution for business modeling. The framework enables the description and design of a business model for SaMD startups. The medical device industry is complex and is associated with hurdles for startups. Maintaining oversight in this complex setting is challenging. The framework can reduce complexity and minimize the risk of overlooking key aspects. It covers all factors relevant to developing a business model for SaMD. From the perspective of SaMD startups, each business model component directly incorporates MDR-specific information. Furthermore, with the visualization of the framework, an overall picture of business modeling for SaMD startups becomes evident. Business model frameworks provide a level of customizable abstraction that can be adjusted to fit the specific use case [<xref ref-type="bibr" rid="ref110">110</xref>]. They provide a common language [<xref ref-type="bibr" rid="ref110">110</xref>] supporting mutual understanding within the startup and its partner network. Moreover, business model frameworks are often used for pitching to investors. This framework can assist in pitching in front of them. In this way, the issue of attracting suitable investors in the SaMD industry is addressed in this work.</p>
        <p>Ideologically, the concepts of startups and MDR seem to be colliding [<xref ref-type="bibr" rid="ref14">14</xref>]. Startups, often young, dynamic, and packed with innovative ideas, see themselves confronted with a strict, documentary-rich MDR, which slows down innovation. Startups often lack regulatory experience and have limited resources, whereas the MDR requires expertise and substantial financial and human resources. The SaMD business model framework aims to bring these worlds together for the benefit of both parties. The framework assists startups in integrating the seemingly opposite MDR world into their daily business.</p>
        <p>The framework has been derived based on the needs of SaMD startups and, therefore, provides a tailored, practical solution to them. Beyond stand-alone SaMDs, hybrid models involving software and hardware are possible. Combining hardware with software makes it necessary to clarify whether hardware, software, or both fall under the category of medical devices. In addition, with a hardware component, the MDR requires the consideration of specific hardware standards, such as the International Electrotechnical Commission (IEC) 60601-1 on medical electrical equipment. Therefore, core activities in a hybrid model differ from pure stand-alone software. For example, hardware production must be considered, resulting in higher investments compared to stand-alone software. Distribution to customers is different for hybrid solutions as well. The derived SaMD business model framework, in its basic structure, can be applied to hybrid models that combine software and hardware. However, the guiding questions do not entirely align with the needs of startups working with hybrid models and would require adjustments.</p>
      </sec>
      <sec>
        <title>Limitations and Future Research</title>
        <p>This work is not without limitations. First, our work focused only on the EU region. The framework might not be applicable for startups aiming to bring SaMD to the market in non-EU countries. This is due to differences in the setting, such as a distinct regulatory environment. Second, our research focused on stand-alone software. Therefore, we did not incorporate cases that include hardware. Future research could adapt the derived framework to be tailored to hardware medical devices or embedded software. Third, our work focused on Regulation (EU) 2017/745. Regulation (EU) 2017/746 on in vitro diagnostic medical devices was not targeted. Fourth, the digital health sector is fast paced and changes rapidly. Our work provides a snapshot of the current setting for SaMD startups in the EU. Finally, the framework presented in this work has not been evaluated yet. Apart from experts in the EU SaMD industry, seed and early-stage SaMD startups, as the target users of the framework, should apply it in practice to validate its usefulness. The framework could, for example, be shared with accelerators, where startups develop the business model for their SaMD. An observation protocol could gather insights into how startups work with the framework. In addition, these startups could be interviewed to evaluate the framework based on predefined criteria. In addition, interviews could be conducted with startups that are in a later stage. These SaMD startups have already developed a business model for their SaMD and can offer valuable insights and feedback based on their experience. The validation of the framework could be a potential avenue for future research.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The field of SaMD is rapidly evolving and offers various opportunities. In our work, we analyzed business modeling in the EU SaMD industry, focusing on startups as a driving force in this industry. Initially, we conducted a systematic literature review and derived a concept matrix. The work was then supplemented with expert interviews. In addition, the requirements of the MDR relevant to SaMD startups and related state-of-the-art standards were considered to develop the SaMD business model framework. Our study is a first step toward mitigating the challenging situation of SaMD startups. Our contributions offer valuable insights into the relationship between MDR and business modeling. The work provides a hands-on solution for startups aiming to develop SaMD under the MDR. Our study could assist SaMD startups in their business modeling process and reduce complexity.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Definition of a medical device according to regulation 2017/745 on medical devices.</p>
        <media xlink:href="jmir_v27i1e67328_app1.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Critical appraisal skills program checklist.</p>
        <media xlink:href="jmir_v27i1e67328_app2.docx" xlink:title="DOCX File , 48 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Sample of experts interviewed.</p>
        <media xlink:href="jmir_v27i1e67328_app3.docx" xlink:title="DOCX File , 21 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Overview of final papers from the systematic literature review, including the mentioned business model frameworks applied or derived.</p>
        <media xlink:href="jmir_v27i1e67328_app4.docx" xlink:title="DOCX File , 36 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>Concept matrix based on the systematic literature review.</p>
        <media xlink:href="jmir_v27i1e67328_app5.docx" xlink:title="DOCX File , 35 KB"/>
      </supplementary-material>
      <supplementary-material id="app6">
        <label>Multimedia Appendix 6</label>
        <p>Overview of inductive coding according to Gioia et al [<xref ref-type="bibr" rid="ref52">52</xref>].</p>
        <media xlink:href="jmir_v27i1e67328_app6.docx" xlink:title="DOCX File , 141 KB"/>
      </supplementary-material>
      <supplementary-material id="app7">
        <label>Multimedia Appendix 7</label>
        <p>Software as a medical device business model framework.</p>
        <media xlink:href="jmir_v27i1e67328_app7.docx" xlink:title="DOCX File , 292 KB"/>
      </supplementary-material>
      <supplementary-material id="app8">
        <label>Multimedia Appendix 8</label>
        <p>Example of filled-out software as a medical device business model framework.</p>
        <media xlink:href="jmir_v27i1e67328_app8.docx" xlink:title="DOCX File , 543 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CE</term>
          <def>
            <p>Conformité Européenne</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">DiGA</term>
          <def>
            <p>digital health application</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">EU</term>
          <def>
            <p>European Union</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">IEC</term>
          <def>
            <p>International Electrotechnical Commission</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">MDR</term>
          <def>
            <p>Medical Device Regulation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">QMS</term>
          <def>
            <p>quality management system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">RQ</term>
          <def>
            <p>research question</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">SaMD</term>
          <def>
            <p>software as a medical device</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">STOF model</term>
          <def>
            <p>service, technology, organization, and finance model</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors acknowledge the support of the KIT-Publication Fund of the Karlsruhe Institute of Technology. The authors used the generative AI tool ChatGPT with GPT-4 [<xref ref-type="bibr" rid="ref111">111</xref>] for spelling, grammar, and style improvements.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kearney</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>McDermott</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>The challenges for manufacturers of the increased clinical evaluation in the European Medical Device Regulations: a quantitative study</article-title>
          <source>Ther Innov Regul Sci</source>
          <year>2023</year>
          <month>07</month>
          <day>17</day>
          <volume>57</volume>
          <issue>4</issue>
          <fpage>783</fpage>
          <lpage>96</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/37198369"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s43441-023-00527-z</pub-id>
          <pub-id pub-id-type="medline">37198369</pub-id>
          <pub-id pub-id-type="pii">10.1007/s43441-023-00527-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC10276779</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>Wagner</surname>
              <given-names>MV</given-names>
            </name>
            <name name-style="western">
              <surname>Schanze</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Challenges of medical device regulation for small and medium sized enterprises</article-title>
          <source>Curr Dir Biomed Eng</source>
          <year>2018</year>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>653</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1515/cdbme-2018-0157</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>Beckers</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Kwade</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zanca</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>The EU medical device regulation: implications for artificial intelligence-based medical device software in medical physics</article-title>
          <source>Phys Med</source>
          <year>2021</year>
          <month>03</month>
          <volume>83</volume>
          <fpage>1</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ejmp.2021.02.011</pub-id>
          <pub-id pub-id-type="medline">33657513</pub-id>
          <pub-id pub-id-type="pii">S1120-1797(21)00099-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mahalatchimy</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Orentlicher</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hervey</surname>
              <given-names>TK</given-names>
            </name>
          </person-group>
          <article-title>Regulating medical devices in the European Union</article-title>
          <source>The Oxford Handbook of Comparative Health Law</source>
          <year>2020</year>
          <publisher-loc>Oxford, UK</publisher-loc>
          <publisher-name>Oxford Academic Press</publisher-name>
        </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>Nüssler</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>The new European Medical Device Regulation: friend or foe for hospitals and patients?</article-title>
          <source>Injury</source>
          <year>2023</year>
          <month>10</month>
          <volume>54 Suppl 5</volume>
          <fpage>110907</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0020-1383(23)00593-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.injury.2023.110907</pub-id>
          <pub-id pub-id-type="medline">37414699</pub-id>
          <pub-id pub-id-type="pii">S0020-1383(23)00593-4</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>Carl</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Hochmann</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Impact of the new European medical device regulation: a two-year comparison</article-title>
          <source>Biomed Tech (Berl)</source>
          <year>2024</year>
          <month>06</month>
          <day>25</day>
          <volume>69</volume>
          <issue>3</issue>
          <fpage>317</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.degruyter.com/document/doi/10.1515/bmt-2023-0325"/>
          </comment>
          <pub-id pub-id-type="doi">10.1515/bmt-2023-0325</pub-id>
          <pub-id pub-id-type="medline">37948747</pub-id>
          <pub-id pub-id-type="pii">bmt-2023-0325</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>Maresova</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Rezny</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Peter</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hajek</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lefley</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Do regulatory changes seriously affect the medical devices industry? Evidence from the Czech Republic</article-title>
          <source>Front Public Health</source>
          <year>2021</year>
          <month>4</month>
          <day>28</day>
          <volume>9</volume>
          <fpage>666453</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33996732"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpubh.2021.666453</pub-id>
          <pub-id pub-id-type="medline">33996732</pub-id>
          <pub-id pub-id-type="pmcid">PMC8113379</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Agyei</surname>
              <given-names>EE</given-names>
            </name>
            <name name-style="western">
              <surname>Pohjolainen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Oinas-Kukkonen</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Impact of medical device regulation on developing health behavior change support systems</article-title>
          <source>Proceedings of the 17th International Conference on Persuasive Technology</source>
          <year>2022</year>
          <conf-name>PERSUASIVE '22</conf-name>
          <conf-date>March 29-31, 2022</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <fpage>29</fpage>
          <lpage>31</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-030-98438-0_1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-030-98438-0_1</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>Baines</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hoogendoorn</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Stevens</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chatterjee</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ashall-Payne</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Andrews</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Leigh</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Navigating medical device certification: a qualitative exploration of barriers and enablers amongst innovators, notified bodies and other stakeholders</article-title>
          <source>Ther Innov Regul Sci</source>
          <year>2023</year>
          <month>03</month>
          <day>04</day>
          <volume>57</volume>
          <issue>2</issue>
          <fpage>238</fpage>
          <lpage>50</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36194368"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s43441-022-00463-4</pub-id>
          <pub-id pub-id-type="medline">36194368</pub-id>
          <pub-id pub-id-type="pii">10.1007/s43441-022-00463-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC9531632</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <article-title>"Software as a medical device": possible framework for risk categorization and corresponding considerations</article-title>
          <source>International Medical Device Regulators Forum</source>
          <access-date>2024-05-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.imdrf.org/sites/default/files/docs/imdrf/final/technical/imdrf-tech-140918-samd-framework-risk-categorization-141013.pdf">https://www.imdrf.org/sites/default/files/docs/imdrf/final/technical/imdrf-tech-140918-samd-framework-risk-categorization-141013.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weimar</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Martjan</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Terzidis</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>Business venturing in regulated markets-taxonomy and archetypes of digital health business models in the European Union: mixed methods descriptive and exploratory study</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <month>01</month>
          <day>09</day>
          <volume>27</volume>
          <fpage>e65725</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e65725/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/65725</pub-id>
          <pub-id pub-id-type="medline">39787596</pub-id>
          <pub-id pub-id-type="pii">v27i1e65725</pub-id>
          <pub-id pub-id-type="pmcid">PMC11757981</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ben-Menahem</surname>
              <given-names>SM</given-names>
            </name>
            <name name-style="western">
              <surname>Nistor-Gallo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Macia</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>von Krogh</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Goldhahn</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>How the new European regulation on medical devices will affect innovation</article-title>
          <source>Nat Biomed Eng</source>
          <year>2020</year>
          <month>06</month>
          <volume>4</volume>
          <issue>6</issue>
          <fpage>585</fpage>
          <lpage>90</lpage>
          <pub-id pub-id-type="doi">10.1038/s41551-020-0541-x</pub-id>
          <pub-id pub-id-type="medline">32203280</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41551-020-0541-x</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>Peter</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Hajek</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Maresova</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Augustynek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Penhaker</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Medical devices: regulation, risk classification, and open innovation</article-title>
          <source>J Open Innov Technol Mark Complex</source>
          <year>2020</year>
          <month>06</month>
          <volume>6</volume>
          <issue>2</issue>
          <fpage>42</fpage>
          <pub-id pub-id-type="doi">10.3390/joitmc6020042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zajki-Zechmeister</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Baumgartner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Harer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schröttner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>A regulatory guide for medical device start-ups in Europe: challenges and pitfalls</article-title>
          <source>Medical Devices and In Vitro Diagnostics: Requirements in Europe</source>
          <year>2023</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>625</fpage>
          <lpage>49</lpage>
        </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>Svempe</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Exploring impediments imposed by the medical device regulation EU 2017/745 on software as a medical device</article-title>
          <source>JMIR Med Inform</source>
          <year>2024</year>
          <month>09</month>
          <day>05</day>
          <volume>12</volume>
          <fpage>e58080</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2024//e58080/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/58080</pub-id>
          <pub-id pub-id-type="medline">39235850</pub-id>
          <pub-id pub-id-type="pii">v12i1e58080</pub-id>
          <pub-id pub-id-type="pmcid">PMC11413540</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sengoku</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Innovation process and industrial system of US Food and Drug Administration-approved software as a medical device: review and content analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2023</year>
          <month>11</month>
          <day>24</day>
          <volume>25</volume>
          <fpage>e47505</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2023//e47505/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/47505</pub-id>
          <pub-id pub-id-type="medline">37999948</pub-id>
          <pub-id pub-id-type="pii">v25i1e47505</pub-id>
          <pub-id pub-id-type="pmcid">PMC10709785</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Goncalves</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bergquist</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>How startups utilize organizational adaptability in digital innovation</article-title>
          <source>Proceedings of the 55th Hawaii International Conference on System Sciences</source>
          <year>2022</year>
          <conf-name>HICSS 2022</conf-name>
          <conf-date>January 4-7, 2022</conf-date>
          <conf-loc>Virtual Event</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.diva-portal.org/smash/get/diva2:1632430/FULLTEXT01.pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.24251/hicss.2022.644</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>Stern</surname>
              <given-names>AD</given-names>
            </name>
          </person-group>
          <article-title>Innovation under regulatory uncertainty: evidence from medical technology</article-title>
          <source>J Public Econ</source>
          <year>2017</year>
          <month>01</month>
          <volume>145</volume>
          <fpage>181</fpage>
          <lpage>200</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28652646"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jpubeco.2016.11.010</pub-id>
          <pub-id pub-id-type="medline">28652646</pub-id>
          <pub-id pub-id-type="pmcid">PMC5482535</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bradford</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>The Brussels Effect: How the European Union Rules the World</source>
          <year>2020</year>
          <publisher-loc>Oxford, UK</publisher-loc>
          <publisher-name>Oxford Academic Press</publisher-name>
        </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>McAllister</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Jeswiet</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Medical device regulation for manufacturers</article-title>
          <source>Proc Inst Mech Eng H</source>
          <year>2003</year>
          <month>06</month>
          <day>01</day>
          <volume>217</volume>
          <issue>6</issue>
          <fpage>459</fpage>
          <lpage>67</lpage>
          <pub-id pub-id-type="doi">10.1243/09544110360729090</pub-id>
          <pub-id pub-id-type="medline">14702983</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Romero</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Villalobos</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sanchez</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Simulating the business model canvas using system dynamics</article-title>
          <source>Proceedings of the 10th Computing Colombian Conference</source>
          <year>2015</year>
          <conf-name>10CCC '15</conf-name>
          <conf-date>September 21-25, 2015</conf-date>
          <conf-loc>Bogota, Colombia</conf-loc>
          <fpage>527</fpage>
          <lpage>34</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/7333469"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/columbiancc.2015.7333469</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Joyce</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Paquin</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>The triple layered business model canvas: a tool to design more sustainable business models</article-title>
          <source>J Clean Prod</source>
          <year>2016</year>
          <month>11</month>
          <volume>135</volume>
          <fpage>1474</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jclepro.2016.06.067</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>Osterwalder</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pigneur</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <source>Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers</source>
          <year>2010</year>
          <publisher-loc>Hoboken, NJ</publisher-loc>
          <publisher-name>John Wiley &amp; Sons</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Albert</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Van der Auwermeulen</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Why classic business modelling doesn't work for complex business domains - a new business modelling approach for digital health</article-title>
          <source>Proceedings of the ISPIM Innovation Forum</source>
          <year>2017</year>
          <conf-name>ISPIM 2017</conf-name>
          <conf-date>March 19-22, 2017</conf-date>
          <conf-loc>Toronto, ON</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.proquest.com/openview/7fd696565a4a394331be650e6154e882/1?cbl=2040562&amp;pq-origsite=gscholar"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velayati</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ayatollahi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hemmat</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dehghan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Key components and critical factors for developing a telehealth business framework: a qualitative study</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2021</year>
          <month>12</month>
          <day>04</day>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>339</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-021-01707-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-021-01707-3</pub-id>
          <pub-id pub-id-type="medline">34863170</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-021-01707-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC8643120</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mueller</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>mHealth business model framework for the maternal and baby segment: a design science research approach</article-title>
          <source>Proceedings of the 32nd Bled eConference Humanizing Technology for a Sustainable Society</source>
          <year>2019</year>
          <conf-name>Bled eConference 2019</conf-name>
          <conf-date>June 16-19, 2019</conf-date>
          <conf-loc>Bled, Slovenia</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aisel.aisnet.org/bled2019/6/"/>
          </comment>
          <pub-id pub-id-type="doi">10.18690/978-961-286-280-0.55</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>Lindgren</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>GDPR regulation impact on different business models and businesses</article-title>
          <source>J Multi Bus Model Innov Technol</source>
          <year>2018</year>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>241</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.13052/jmbmit2245-456x.434</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>Ademi</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Sætre</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Klungseth</surname>
              <given-names>NJ</given-names>
            </name>
          </person-group>
          <article-title>Advancing the understanding of sustainable business models through organizational learning</article-title>
          <source>Bus Strat Env</source>
          <year>2024</year>
          <month>03</month>
          <day>26</day>
          <volume>33</volume>
          <issue>6</issue>
          <fpage>5174</fpage>
          <lpage>94</lpage>
          <pub-id pub-id-type="doi">10.1002/bse.3746</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <article-title>Recommendations on digital interventions for health system strengthening</article-title>
          <source>World Health Organization</source>
          <access-date>2024-04-02</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.who.int/publications/i/item/WHO-RHR-19.8">https://www.who.int/publications/i/item/WHO-RHR-19.8</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>ISO/TR 11147:2023: health informatics — personalized digital health — digital therapeutics health software systems</article-title>
          <source>International Organization for Standardization</source>
          <access-date>2024-04-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/83767.html">https://www.iso.org/standard/83767.html</ext-link>
          </comment>
        </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>Sharma</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Luthra</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Implementing a risk-based approach to quality management system ISO-13485 processes in compliance with EUMDR 2017/745 for medical device industry</article-title>
          <source>J Pharm Res Int</source>
          <year>2023</year>
          <month>05</month>
          <day>20</day>
          <volume>35</volume>
          <issue>13</issue>
          <fpage>8</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.9734/jpri/2023/v35i137365</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>Ludvigsen</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Nagaraja</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Daly</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>When is software a medical device? Understanding and determining the “intention” and requirements for software as a medical device in European Union law</article-title>
          <source>Eur J Risk Regul</source>
          <year>2021</year>
          <month>09</month>
          <day>20</day>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>78</fpage>
          <lpage>93</lpage>
          <pub-id pub-id-type="doi">10.1017/err.2021.45</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>Fink</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Akra</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Regulatory clearance: how are outcome measurements critical?</article-title>
          <source>Injury</source>
          <year>2020</year>
          <month>05</month>
          <volume>51 Suppl 2</volume>
          <fpage>S67</fpage>
          <lpage>70</lpage>
          <pub-id pub-id-type="doi">10.1016/j.injury.2019.10.071</pub-id>
          <pub-id pub-id-type="medline">31703963</pub-id>
          <pub-id pub-id-type="pii">S0020-1383(19)30678-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hastenteufel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Renaud</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Software als Medizinprodukt: Entwicklung und Zulassung von Software in der Medizintechnik</source>
          <year>2019</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <article-title>Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, amending Directive 2001/83/EC, Regulation (EC) No 178/2002 and Regulation (EC) No 1223/2009 and repealing Council Directives 90/385/EEC and 93/42/EEC (Text with EEA relevance. )</article-title>
          <source>European Union</source>
          <access-date>2024-02-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32017R0745">https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32017R0745</ext-link>
          </comment>
        </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>Keutzer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Simonsson</surname>
              <given-names>US</given-names>
            </name>
          </person-group>
          <article-title>Medical device apps: an introduction to regulatory affairs for developers</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2020</year>
          <month>06</month>
          <day>26</day>
          <volume>8</volume>
          <issue>6</issue>
          <fpage>e17567</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2020/6/e17567/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17567</pub-id>
          <pub-id pub-id-type="medline">32589154</pub-id>
          <pub-id pub-id-type="pii">v8i6e17567</pub-id>
          <pub-id pub-id-type="pmcid">PMC7381013</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <article-title>EVS-EN ISO 13485:2016: medical devices - quality management systems - requirements for regulatory purposes (ISO 13485:2016)</article-title>
          <source>EVS</source>
          <access-date>2024-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.evs.ee/en/evs-en-iso-13485-2016">https://www.evs.ee/en/evs-en-iso-13485-2016</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <article-title>EVS-EN ISO 14971:2019: medical devices - application of risk management to medical devices (ISO 14971:2019)</article-title>
          <source>EVS</source>
          <access-date>2024-05-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.evs.ee/en/evs-en-iso-14971-2019">https://www.evs.ee/en/evs-en-iso-14971-2019</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <article-title>EVS-EN 62304:2006/A1:2015: medical device software - software life-cycle processes</article-title>
          <source>EVS</source>
          <access-date>2024-05-21</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.evs.ee/en/evs-en-62304-2006-a1-2015">https://www.evs.ee/en/evs-en-62304-2006-a1-2015</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <article-title>EVS-EN 62366-1:2015+A1:2020: medical devices - part 1: application of usability engineering to medical devices (IEC 62366-1:2015 + IEC 62366-1:2015/A1:2020)</article-title>
          <source>EVS</source>
          <access-date>2024-05-08</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.evs.ee/en/evs-en-62366-1-2015-a1-2020-consolidated">https://www.evs.ee/en/evs-en-62366-1-2015-a1-2020-consolidated</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <article-title>EVS-EN 62366-1:2015+A1:2020: medical devices - part 1: application of usability engineering to medical devices (IEC 62366-1:2015 + IEC 62366-1:2015/A1:2020)</article-title>
          <source>EVS</source>
          <access-date>2024-05-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.evs.ee/en/evs-en-iec-81001-5-1-2022">https://www.evs.ee/en/evs-en-iec-81001-5-1-2022</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
          <article-title>Guidance on clinical evaluation (MDR)/ performance evaluation (IVDR) of medical device software</article-title>
          <source>Medical Device Coordination Group Document</source>
          <access-date>2025-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2020_1_guidance_clinic_eva_md_software_en_0.pdf">https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2020_1_guidance_clinic_eva_md_software_en_0.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <article-title>MDCG 2019-11: guidance on qualification and classification of software in regulation (EU) 2017/745 – MDR and regulation (EU)</article-title>
          <source>Medical Device Coordination Group Document</source>
          <year>2019</year>
          <access-date>2025-01-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2019_11_guidance_qualification_classification_software_en_0.pdf">https://health.ec.europa.eu/system/files/2020-09/md_mdcg_2019_11_guidance_qualification_classification_software_en_0.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baumgartner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Harer</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Schröttner</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Medical Devices and In Vitro Diagnostics: Requirements in Europe</source>
          <year>2023</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </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>Tranfield</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Denyer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Smart</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Towards a methodology for developing evidence‐informed management knowledge by means of systematic review</article-title>
          <source>Br J Manag</source>
          <year>2003</year>
          <month>09</month>
          <day>16</day>
          <volume>14</volume>
          <issue>3</issue>
          <fpage>207</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1111/1467-8551.00375</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>Kraus</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Breier</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dasí-Rodríguez</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>The art of crafting a systematic literature review in entrepreneurship research</article-title>
          <source>Int Entrep Manag J</source>
          <year>2020</year>
          <month>02</month>
          <day>01</day>
          <volume>16</volume>
          <issue>3</issue>
          <fpage>1023</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1007/S11365-020-00635-4</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>Bartels</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Johnsson</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Boersma</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Flink</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>McCracken</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Petersson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Christie</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Feldman</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Simons</surname>
              <given-names>LE</given-names>
            </name>
            <name name-style="western">
              <surname>Onghena</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Vlaeyen</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Wicksell</surname>
              <given-names>RK</given-names>
            </name>
          </person-group>
          <article-title>Development, evaluation and implementation of a digital behavioural health treatment for chronic pain: study protocol of the multiphase DAHLIA project</article-title>
          <source>BMJ Open</source>
          <year>2022</year>
          <month>04</month>
          <day>15</day>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>e059152</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmjopen.bmj.com/lookup/pmidlookup?view=long&amp;pmid=35428645"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjopen-2021-059152</pub-id>
          <pub-id pub-id-type="medline">35428645</pub-id>
          <pub-id pub-id-type="pii">bmjopen-2021-059152</pub-id>
          <pub-id pub-id-type="pmcid">PMC9014062</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>Chen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cheng</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Mehta</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>A review of telemedicine business models</article-title>
          <source>Telemed J E Health</source>
          <year>2013</year>
          <month>04</month>
          <volume>19</volume>
          <issue>4</issue>
          <fpage>287</fpage>
          <lpage>97</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2012.0172</pub-id>
          <pub-id pub-id-type="medline">23540278</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Christie</surname>
              <given-names>HL</given-names>
            </name>
            <name name-style="western">
              <surname>Boots</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Peetoom</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tange</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Verhey</surname>
              <given-names>FR</given-names>
            </name>
            <name name-style="western">
              <surname>de Vugt</surname>
              <given-names>ME</given-names>
            </name>
          </person-group>
          <article-title>Developing a plan for the sustainable implementation of an electronic health intervention (partner in balance) to support caregivers of people with dementia: case study</article-title>
          <source>JMIR Aging</source>
          <year>2020</year>
          <month>06</month>
          <day>25</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>e18624</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aging.jmir.org/2020/1/e18624/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/18624</pub-id>
          <pub-id pub-id-type="medline">32584261</pub-id>
          <pub-id pub-id-type="pii">v3i1e18624</pub-id>
          <pub-id pub-id-type="pmcid">PMC7380981</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Veld</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Fielt</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Hutten</surname>
              <given-names>MV</given-names>
            </name>
          </person-group>
          <article-title>Moving tele-monitoring and tele-treatment from promise to practice: a business model approach for a chronic lower back pain application</article-title>
          <source>Int J Healthc Technol Manag</source>
          <year>2011</year>
          <volume>12</volume>
          <issue>3/4</issue>
          <fpage>333</fpage>
          <lpage>49</lpage>
          <pub-id pub-id-type="doi">10.1504/ijhtm.2011.040483</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>Visser</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bloo</surname>
              <given-names>JK</given-names>
            </name>
            <name name-style="western">
              <surname>Grobbe</surname>
              <given-names>FA</given-names>
            </name>
            <name name-style="western">
              <surname>Vollenbroek-Hutten</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Video teleconsultation service: who is needed to do what, to get it implemented in daily care?</article-title>
          <source>Telemed J E Health</source>
          <year>2010</year>
          <month>05</month>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>439</fpage>
          <lpage>45</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2009.0101</pub-id>
          <pub-id pub-id-type="medline">20507199</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Christensen</surname>
              <given-names>CM</given-names>
            </name>
          </person-group>
          <article-title>Disruptive innovation in health care delivery: a framework for business-model innovation</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2008</year>
          <month>09</month>
          <volume>27</volume>
          <issue>5</issue>
          <fpage>1329</fpage>
          <lpage>35</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.27.5.1329</pub-id>
          <pub-id pub-id-type="medline">18780919</pub-id>
          <pub-id pub-id-type="pii">27/5/1329</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>YL</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Modeling a mobile health management business model for chronic kidney disease</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2016</year>
          <volume>225</volume>
          <fpage>1047</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="medline">27332476</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref54">
        <label>54</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>CC</given-names>
            </name>
          </person-group>
          <article-title>An analysis of telemedicine in Taiwan: a business model perspective</article-title>
          <source>Int J Gerontol</source>
          <year>2011</year>
          <month>12</month>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>189</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijge.2011.09.039</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref55">
        <label>55</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Acheampong</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Vimarlund</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Business models for telemedicine services: a literature review</article-title>
          <source>Health Syst</source>
          <year>2017</year>
          <month>12</month>
          <day>19</day>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>189</fpage>
          <lpage>203</lpage>
          <pub-id pub-id-type="doi">10.1057/hs.2014.20</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref56">
        <label>56</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Alnahdi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>An psychological mindset based stress free business model for digital health?</article-title>
          <source>J ReAtt Ther Dev Divers</source>
          <year>2023</year>
          <volume>6</volume>
          <issue>4s</issue>
          <fpage>401</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://jrtdd.com/index.php/journal/article/view/470"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref57">
        <label>57</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fachinger</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Schöpke</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Business model for sensor-based fall recognition systems</article-title>
          <source>Inform Health Soc Care</source>
          <year>2014</year>
          <volume>39</volume>
          <issue>3-4</issue>
          <fpage>305</fpage>
          <lpage>18</lpage>
          <pub-id pub-id-type="doi">10.3109/17538157.2014.931855</pub-id>
          <pub-id pub-id-type="medline">25148563</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref58">
        <label>58</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fife</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Digital home health and mHealth: prospects and challenges for adoption in the U.S</article-title>
          <source>Proceedings of the 50th International Conference on Bridging an Ever Shifting Digital Divide</source>
          <year>2011</year>
          <conf-name>FITCE '11</conf-name>
          <conf-date>August 31-September 3, 2011</conf-date>
          <conf-loc>Palermo, Italy</conf-loc>
          <fpage>1</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/6133431"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/fitce.2011.6133431</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref59">
        <label>59</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fusco</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Turchetti</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Interactive business models for telerehabilitation after total knee replacement</article-title>
          <source>Proceedings of the 3rd International Conference on Bioinformatics and Biomedical Engineering</source>
          <year>2015</year>
          <conf-name>IWBBIO '15</conf-name>
          <conf-date>April 15-17, 2015</conf-date>
          <conf-loc>Granada, Spain</conf-loc>
          <fpage>502</fpage>
          <lpage>11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-319-16480-9_49"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-319-16480-9_49</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref60">
        <label>60</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>García-Holgado</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Marcos-Pablos</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>García-Peñalvo</surname>
              <given-names>FJ</given-names>
            </name>
          </person-group>
          <article-title>A model to define an eHealth technological ecosystem for caregivers</article-title>
          <source>Proceedings of the 7th World Conference on Information Systems and Technologies</source>
          <year>2019</year>
          <conf-name>WorldCIST '19</conf-name>
          <conf-date>April 16-19, 2019</conf-date>
          <conf-loc>Galicia, Spain</conf-loc>
          <fpage>422</fpage>
          <lpage>32</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-030-16187-3_41"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-030-16187-3_41</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref61">
        <label>61</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grustam</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Vrijhoef</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Cordella</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Koymans</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Severens</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Care coordination in a business-to-business and a business-to-consumer model for telemonitoring patients with chronic diseases</article-title>
          <source>Int J Care Coord</source>
          <year>2017</year>
          <month>12</month>
          <volume>20</volume>
          <issue>4</issue>
          <fpage>135</fpage>
          <lpage>47</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/2053434517747908?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/2053434517747908</pub-id>
          <pub-id pub-id-type="medline">29276610</pub-id>
          <pub-id pub-id-type="pii">10.1177_2053434517747908</pub-id>
          <pub-id pub-id-type="pmcid">PMC5734380</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref62">
        <label>62</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grustam</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Vrijhoef</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Koymans</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hukal</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Severens</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Extending the business-to-business (B2B) model towards  a business-to-consumer B2C) model for telemonitoring  patients with chronic heart failure (CHF)</article-title>
          <source>J Bus Model</source>
          <year>2018</year>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>106</fpage>
          <lpage>29</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/330910206_Extending_the_Business-to-Business_B2B_Model_Towards_a_Business-to-Consumer_B2C_Model_for_Telemonitoring_Patients_with_Chronic_Heart_Failure_CHF"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref63">
        <label>63</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kho</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gillespie</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Horsham</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Snoswell</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Vagenas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Soyer</surname>
              <given-names>HP</given-names>
            </name>
            <name name-style="western">
              <surname>Janda</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Skin doctor consultations using mobile teledermoscopy: exploring virtual care business models</article-title>
          <source>Telemed J E Health</source>
          <year>2020</year>
          <month>11</month>
          <day>14</day>
          <volume>26</volume>
          <issue>11</issue>
          <fpage>1406</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2019.0228</pub-id>
          <pub-id pub-id-type="medline">32058835</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref64">
        <label>64</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kijl</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Nieuwenhuis</surname>
              <given-names>LJ</given-names>
            </name>
            <name name-style="western">
              <surname>Huis in 't Veld</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Hermens</surname>
              <given-names>HJ</given-names>
            </name>
            <name name-style="western">
              <surname>Vollenbroek-Hutten</surname>
              <given-names>MM</given-names>
            </name>
          </person-group>
          <article-title>Deployment of e-health services - a business model engineering strategy</article-title>
          <source>J Telemed Telecare</source>
          <year>2010</year>
          <volume>16</volume>
          <issue>6</issue>
          <fpage>344</fpage>
          <lpage>53</lpage>
          <pub-id pub-id-type="doi">10.1258/jtt.2010.006009</pub-id>
          <pub-id pub-id-type="medline">20798429</pub-id>
          <pub-id pub-id-type="pii">16/6/344</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>Kimble</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Business models for e‐health: evidence from ten case studies</article-title>
          <source>Glob Bus Org Exc</source>
          <year>2015</year>
          <month>04</month>
          <day>23</day>
          <volume>34</volume>
          <issue>4</issue>
          <fpage>18</fpage>
          <lpage>30</lpage>
          <pub-id pub-id-type="doi">10.1002/joe.21611</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>Korsgaard</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Hasenkam</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Vesterby</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Successful implementation of telemedicine depends on personal relations between company representatives and healthcare providers: a qualitative study of business models for Danish home telemonitoring</article-title>
          <source>Health Serv Manage Res</source>
          <year>2021</year>
          <month>11</month>
          <day>28</day>
          <volume>34</volume>
          <issue>4</issue>
          <fpage>223</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1177/0951484820988628</pub-id>
          <pub-id pub-id-type="medline">33508963</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref67">
        <label>67</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kriegel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Reckwitz</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Auinger</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tuttle-Weidinger</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Schmitt-Rüth</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kränzl-Nagl</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>New service excellence model for eHealth and AAL solutions - a framework for continuous new service development</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2017</year>
          <volume>236</volume>
          <fpage>275</fpage>
          <lpage>81</lpage>
          <pub-id pub-id-type="medline">28508807</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref68">
        <label>68</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>León</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Nieto-Hipólito</surname>
              <given-names>JI</given-names>
            </name>
            <name name-style="western">
              <surname>Garibaldi-Beltrán</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Amaya-Parra</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Luque-Morales</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Magaña-Espinoza</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Aguilar-Velazco</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Designing a model of a digital ecosystem for healthcare and wellness using the business model canvas</article-title>
          <source>J Med Syst</source>
          <year>2016</year>
          <month>06</month>
          <day>27</day>
          <volume>40</volume>
          <issue>6</issue>
          <fpage>144</fpage>
          <pub-id pub-id-type="doi">10.1007/s10916-016-0488-3</pub-id>
          <pub-id pub-id-type="medline">27118010</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-016-0488-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref69">
        <label>69</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>WH</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>HH</given-names>
            </name>
            <name name-style="western">
              <surname>Chiu</surname>
              <given-names>WT</given-names>
            </name>
          </person-group>
          <article-title>A business model analysis of telecardiology service</article-title>
          <source>Telemed J E Health</source>
          <year>2010</year>
          <month>12</month>
          <volume>16</volume>
          <issue>10</issue>
          <fpage>1067</fpage>
          <lpage>73</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2010.0059</pub-id>
          <pub-id pub-id-type="medline">21186990</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref70">
        <label>70</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Canu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Breda</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Jean</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>E-health deployment business model tele-expertise case study</article-title>
          <source>Proceedings of the 2018 IADIS International Conference ICT, Society and Human Beings</source>
          <year>2018</year>
          <conf-name>ICT '18</conf-name>
          <conf-date>July 17-19, 2018</conf-date>
          <conf-loc>Madrid, Spain</conf-loc>
          <fpage>17</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iadisportal.org/digital-library/e-health-deployment-business-model-tele-expertise-case-study"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref71">
        <label>71</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nikou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Mobile health and wellness applications: a business model ontology-based review</article-title>
          <source>Int J E Bus Res</source>
          <year>2017</year>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>24</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ideas.repec.org/a/igg/jebr00/v13y2017i1p1-24.html"/>
          </comment>
          <pub-id pub-id-type="doi">10.4018/ijebr.2017010101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref72">
        <label>72</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oderanti</surname>
              <given-names>FO</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Commercialization of eHealth innovations in the market of the UK healthcare sector: a framework for a sustainable business model</article-title>
          <source>Psychol Mark</source>
          <year>2018</year>
          <month>01</month>
          <day>10</day>
          <volume>35</volume>
          <issue>2</issue>
          <fpage>120</fpage>
          <lpage>37</lpage>
          <pub-id pub-id-type="doi">10.1002/mar.21074</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref73">
        <label>73</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Oderanti</surname>
              <given-names>FO</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Cubric</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Business models for sustainable commercialisation of digital healthcare (eHealth) innovations for an increasingly ageing population</article-title>
          <source>Technol Forecast Soc Change</source>
          <year>2021</year>
          <month>10</month>
          <volume>171</volume>
          <fpage>120969</fpage>
          <pub-id pub-id-type="doi">10.1016/j.techfore.2021.120969</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref74">
        <label>74</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pascarelli</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Colucci</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mitrano</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Corallo</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Business models in digital health: bibliometric analysis and systematic literature review</article-title>
          <source>Proceedings of the 2023 IEEE Symposium on Computers and Communications</source>
          <year>2023</year>
          <conf-name>ISCC '23</conf-name>
          <conf-date>July 9-12, 2023</conf-date>
          <conf-loc>Gammarth, Tunisia</conf-loc>
          <fpage>9</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/10218237"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/iscc58397.2023.10218237</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref75">
        <label>75</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>SG</given-names>
            </name>
            <name name-style="western">
              <surname>Medina</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gonçalves</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Da Silva</surname>
              <given-names>MT</given-names>
            </name>
          </person-group>
          <article-title>System thinking and business model canvas for collaborative business models design</article-title>
          <source>Proceedings of the 2016 International Conference on Advances in Production Management Systems, Initiatives for a Sustainable World</source>
          <year>2016</year>
          <conf-name>APMS '16</conf-name>
          <conf-date>September 3-7, 2016</conf-date>
          <conf-loc>Iguassu Falls, Brazil</conf-loc>
          <fpage>461</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-319-51133-7_55"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-319-51133-7_55</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref76">
        <label>76</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Peters</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Blohm</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Leimeister</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Anatomy of successful business models for complex services: insights from the telemedicine field</article-title>
          <source>J Manag Inf Syst</source>
          <year>2015</year>
          <month>12</month>
          <day>16</day>
          <volume>32</volume>
          <issue>3</issue>
          <fpage>75</fpage>
          <lpage>104</lpage>
          <pub-id pub-id-type="doi">10.1080/07421222.2015.1095034</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref77">
        <label>77</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pistorio</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Locatelli</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Cirilli</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Gestaldi</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Solvi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A business model for digital healthcare environments: an organic approach and a use case for handling cognitive impairment</article-title>
          <source>Proceedings of the 10th International Joint Conference on Biomedical Engineering Systems and Technologies</source>
          <year>2017</year>
          <conf-name>SCITEPRESS '17</conf-name>
          <conf-date>February 21-23, 2017</conf-date>
          <conf-loc>Porto, Portugal</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.scitepress.org/papers/2017/61688/61688.pdf"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-031-17037-9_5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref78">
        <label>78</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Schuhmacher</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Haefner</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Honsberg</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Goldhahn</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gassmann</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>The dominant logic of Big Tech in healthcare and pharma</article-title>
          <source>Drug Discov Today</source>
          <year>2023</year>
          <month>02</month>
          <volume>28</volume>
          <issue>2</issue>
          <fpage>103457</fpage>
          <pub-id pub-id-type="doi">10.1016/j.drudis.2022.103457</pub-id>
          <pub-id pub-id-type="medline">36427777</pub-id>
          <pub-id pub-id-type="pii">S1359-6446(22)00450-0</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref79">
        <label>79</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sprenger</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Supporting the viability of e-Health services with pattern-based business model design</article-title>
          <source>Proceedings of the 6th International Conference on Well-Being in the Information Society</source>
          <year>2016</year>
          <conf-name>WIS '16</conf-name>
          <conf-date>September 16-18, 2016</conf-date>
          <conf-loc>Tampere, Finland</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/chapter/10.1007/978-3-319-44672-1_14"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/978-3-319-44672-1_18</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref80">
        <label>80</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Steinhauser</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Network-based business models, the institutional environment, and the diffusion of digital innovations: case studies of telemedicine networks in Germany</article-title>
          <source>Schmalenbach Bus Rev</source>
          <year>2019</year>
          <month>5</month>
          <day>31</day>
          <volume>71</volume>
          <issue>3</issue>
          <fpage>343</fpage>
          <lpage>83</lpage>
          <pub-id pub-id-type="doi">10.1007/s41464-019-00076-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref81">
        <label>81</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sterling</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>LeRouge</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>On-demand telemedicine as a disruptive health technology: qualitative study exploring emerging business models and strategies among early adopter organizations in the United States</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>11</month>
          <day>15</day>
          <volume>21</volume>
          <issue>11</issue>
          <fpage>e14304</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/11/e14304/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/14304</pub-id>
          <pub-id pub-id-type="medline">31730038</pub-id>
          <pub-id pub-id-type="pii">v21i11e14304</pub-id>
          <pub-id pub-id-type="pmcid">PMC6884714</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref82">
        <label>82</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tageo</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Dantas</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Chronaki</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lowe</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Berler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Porcu</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Business Model Canvas insights for the adoption of international patient summary standards in the mHealth industry</article-title>
          <source>J Bus Model</source>
          <year>2020</year>
          <volume>8</volume>
          <issue>3</issue>
          <fpage>91</fpage>
          <lpage>106</lpage>
          <pub-id pub-id-type="doi">10.5278/jbm.v8i3.3428</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref83">
        <label>83</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thamjamrassri</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Tak</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kong</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hong</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Customer discovery as the first essential step for successful health information technology system development</article-title>
          <source>Healthc Inform Res</source>
          <year>2018</year>
          <month>01</month>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>79</fpage>
          <lpage>85</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29503756"/>
          </comment>
          <pub-id pub-id-type="doi">10.4258/hir.2018.24.1.79</pub-id>
          <pub-id pub-id-type="medline">29503756</pub-id>
          <pub-id pub-id-type="pmcid">PMC5820090</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref84">
        <label>84</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Limburg</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wentzel</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sanderman</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>van Gemert-Pijnen</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Business modeling to implement an eHealth portal for infection control: a reflection on co-creation with stakeholders</article-title>
          <source>JMIR Res Protoc</source>
          <year>2015</year>
          <month>08</month>
          <day>13</day>
          <volume>4</volume>
          <issue>3</issue>
          <fpage>e104</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchprotocols.org/2015/3/e104/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/resprot.4519</pub-id>
          <pub-id pub-id-type="medline">26272510</pub-id>
          <pub-id pub-id-type="pii">v4i3e104</pub-id>
          <pub-id pub-id-type="pmcid">PMC4736288</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref85">
        <label>85</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Meeuwen</surname>
              <given-names>DP</given-names>
            </name>
            <name name-style="western">
              <surname>van Walt Meijer</surname>
              <given-names>QJ</given-names>
            </name>
            <name name-style="western">
              <surname>Simonse</surname>
              <given-names>LW</given-names>
            </name>
          </person-group>
          <article-title>Care models of eHealth services: a case study on the design of a business model for an online precare service</article-title>
          <source>JMIR Res Protoc</source>
          <year>2015</year>
          <month>03</month>
          <day>24</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>e32</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchprotocols.org/2015/1/e32/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/resprot.3501</pub-id>
          <pub-id pub-id-type="medline">25831094</pub-id>
          <pub-id pub-id-type="pii">v4i1e32</pub-id>
          <pub-id pub-id-type="pmcid">PMC4389107</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref86">
        <label>86</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velayati</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ayatollahi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hemmat</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dehghan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The 4P telehealth business framework for Iran</article-title>
          <source>BMC Med Inform Decis Mak</source>
          <year>2022</year>
          <month>10</month>
          <day>09</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>266</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedinformdecismak.biomedcentral.com/articles/10.1186/s12911-022-02011-4"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s12911-022-02011-4</pub-id>
          <pub-id pub-id-type="medline">36210440</pub-id>
          <pub-id pub-id-type="pii">10.1186/s12911-022-02011-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC9548305</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref87">
        <label>87</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Velayati</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Ayatollahi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hemmat</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dehghan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Telehealth business models and their components: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>03</month>
          <day>29</day>
          <volume>24</volume>
          <issue>3</issue>
          <fpage>e33128</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/3/e33128/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/33128</pub-id>
          <pub-id pub-id-type="medline">35348471</pub-id>
          <pub-id pub-id-type="pii">v24i3e33128</pub-id>
          <pub-id pub-id-type="pmcid">PMC9006135</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref88">
        <label>88</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Viswanadham</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Ecosystem model for healthcare platform</article-title>
          <source>Sādhanā</source>
          <year>2021</year>
          <month>09</month>
          <day>13</day>
          <volume>46</volume>
          <issue>4</issue>
          <fpage>188</fpage>
          <pub-id pub-id-type="doi">10.1007/s12046-021-01708-y</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref89">
        <label>89</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Radić</surname>
              <given-names>Marija</given-names>
            </name>
            <name name-style="western">
              <surname>Vienken</surname>
              <given-names>Claudia</given-names>
            </name>
            <name name-style="western">
              <surname>Nikschat</surname>
              <given-names>Laurin</given-names>
            </name>
            <name name-style="western">
              <surname>Dietrich</surname>
              <given-names>Thore</given-names>
            </name>
            <name name-style="western">
              <surname>Koenig</surname>
              <given-names>Holger</given-names>
            </name>
            <name name-style="western">
              <surname>Laderick</surname>
              <given-names>Lorenz</given-names>
            </name>
            <name name-style="western">
              <surname>Radić</surname>
              <given-names>Dubravko</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bach Tobji</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Jallouli</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Strat</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Soares</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Davidescu</surname>
              <given-names>AA</given-names>
            </name>
          </person-group>
          <article-title>AI-based business models in healthcare: an empirical study of clinical decision support systems</article-title>
          <source>Digital Economy. Emerging Technologies and Business Innovation. ICDEc 2022. Lecture Notes in Business Information Processing, vol 461</source>
          <year>2022</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref90">
        <label>90</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Webster</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Watson</surname>
              <given-names>RT</given-names>
            </name>
          </person-group>
          <article-title>Analyzing the past to prepare for the future: writing a literature review</article-title>
          <source>MIS Q</source>
          <year>2002</year>
          <volume>26</volume>
          <issue>2</issue>
          <fpage>xiii</fpage>
          <pub-id pub-id-type="doi">10.2307/4132319</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref91">
        <label>91</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zeng</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Methodological quality (risk of bias) assessment tools for primary and secondary medical studies: what are they and which is better?</article-title>
          <source>Mil Med Res</source>
          <year>2020</year>
          <month>02</month>
          <day>29</day>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>7</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mmrjournal.biomedcentral.com/articles/10.1186/s40779-020-00238-8"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40779-020-00238-8</pub-id>
          <pub-id pub-id-type="medline">32111253</pub-id>
          <pub-id pub-id-type="pii">10.1186/s40779-020-00238-8</pub-id>
          <pub-id pub-id-type="pmcid">PMC7049186</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref92">
        <label>92</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rowley</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Conducting research interviews</article-title>
          <source>Manag Res Rev</source>
          <year>2012</year>
          <volume>35</volume>
          <issue>3/4</issue>
          <fpage>260</fpage>
          <lpage>71</lpage>
          <pub-id pub-id-type="doi">10.1108/01409171211210154</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref93">
        <label>93</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gill</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Treasure</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Chadwick</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Methods of data collection in qualitative research: interviews and focus groups</article-title>
          <source>Br Dent J</source>
          <year>2008</year>
          <month>03</month>
          <day>22</day>
          <volume>204</volume>
          <issue>6</issue>
          <fpage>291</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.1038/bdj.2008.192</pub-id>
          <pub-id pub-id-type="medline">18356873</pub-id>
          <pub-id pub-id-type="pii">bdj.2008.192</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref94">
        <label>94</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kallio</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Pietilä</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kangasniemi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Systematic methodological review: developing a framework for a qualitative semi-structured interview guide</article-title>
          <source>J Adv Nurs</source>
          <year>2016</year>
          <month>12</month>
          <volume>72</volume>
          <issue>12</issue>
          <fpage>2954</fpage>
          <lpage>65</lpage>
          <pub-id pub-id-type="doi">10.1111/jan.13031</pub-id>
          <pub-id pub-id-type="medline">27221824</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref95">
        <label>95</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gioia</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Corley</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Hamilton</surname>
              <given-names>AL</given-names>
            </name>
          </person-group>
          <article-title>Seeking qualitative rigor in inductive research</article-title>
          <source>Organ Res Methods</source>
          <year>2012</year>
          <month>07</month>
          <day>24</day>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>15</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.1177/1094428112452151</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref96">
        <label>96</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Faber</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Haaker</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kijl</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>De</surname>
              <given-names>RM</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>de Vos</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Haaker</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Conceptualizing the STOF model</article-title>
          <source>Mobile Service Innovation and Business Models</source>
          <year>2008</year>
          <publisher-loc>Heidelberg, Germany</publisher-loc>
          <publisher-name>Springer</publisher-name>
          <fpage>31</fpage>
          <lpage>70</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref97">
        <label>97</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maurya</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Running Lean: Iterate from Plan A to a Plan That Works</source>
          <year>2012</year>
          <publisher-loc>Sebastopol, CA</publisher-loc>
          <publisher-name>O'Reilly Media</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref98">
        <label>98</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Riley</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Our model</article-title>
          <source>Business Model Innovation for Healthcare</source>
          <access-date>2024-05-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://imaginego.com/modelh/">http://imaginego.com/modelh/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref99">
        <label>99</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El Sawy</surname>
              <given-names>OA</given-names>
            </name>
            <name name-style="western">
              <surname>Pereira</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <source>Business Modelling in the Dynamic Digital Space: An Ecosystem Approach</source>
          <year>2013</year>
          <publisher-loc>Berlin, Germany</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref100">
        <label>100</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gassmann</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Frankenberger</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Csik</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <source>The Business Model Navigator: 55 Models That Will Revolutionise Your Business</source>
          <year>2014</year>
          <publisher-loc>Berlin, Germany</publisher-loc>
          <publisher-name>FT Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref101">
        <label>101</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Steinberg</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Horwitz</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Zohar</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Building a business model in digital medicine</article-title>
          <source>Nat Biotechnol</source>
          <year>2015</year>
          <month>09</month>
          <day>01</day>
          <volume>33</volume>
          <issue>9</issue>
          <fpage>910</fpage>
          <lpage>20</lpage>
          <pub-id pub-id-type="doi">10.1038/nbt.3339</pub-id>
          <pub-id pub-id-type="medline">26348957</pub-id>
          <pub-id pub-id-type="pii">nbt.3339</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref102">
        <label>102</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Christensen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kagermann</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Reinventing your business model</article-title>
          <source>Harv Bus Rev</source>
          <year>2008</year>
          <volume>86</volume>
          <issue>12</issue>
          <fpage>57</fpage>
          <lpage>68</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref103">
        <label>103</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Freeman</surname>
              <given-names>RE</given-names>
            </name>
          </person-group>
          <source>Strategic Management: A Stakeholder Approach</source>
          <year>1984</year>
          <publisher-loc>Boston, MA</publisher-loc>
          <publisher-name>Pitman Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref104">
        <label>104</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Osterwalder</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Pigneur</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Bernarda</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Value Proposition Design: How to Create Products and Services Customers Want</source>
          <year>2014</year>
          <publisher-loc>Hoboken, NJ</publisher-loc>
          <publisher-name>John Wiley &amp; Sons</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref105">
        <label>105</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khalid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmad</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Word-of-mouth communications: a powerful contributor to consumers decision-making in healthcare market</article-title>
          <source>Int J Bus Manag Inven</source>
          <year>2013</year>
          <volume>2</volume>
          <issue>5</issue>
          <fpage>50</fpage>
          <lpage>9</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref106">
        <label>106</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weinrauch</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Mann</surname>
              <given-names>OK</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Pharr</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Dealing with limited financial resources: a marketing challenge for small businesses</article-title>
          <source>J Small Bus Manag</source>
          <year>1991</year>
          <volume>29</volume>
          <issue>4</issue>
          <fpage>44</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref107">
        <label>107</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Santisteban</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mauricio</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Systematic literature review of critical success factors of information technology startups</article-title>
          <source>Acad Entrep J</source>
          <year>2017</year>
          <volume>23</volume>
          <issue>2</issue>
          <fpage>1</fpage>
          <lpage>23</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref108">
        <label>108</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Doz</surname>
              <given-names>YL</given-names>
            </name>
            <name name-style="western">
              <surname>Kosonen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Embedding strategic agility: a leadership agenda for accelerating business model renewal</article-title>
          <source>Long Range Plan</source>
          <year>2010</year>
          <month>4</month>
          <volume>43</volume>
          <issue>2-3</issue>
          <fpage>370</fpage>
          <lpage>82</lpage>
          <pub-id pub-id-type="doi">10.1016/j.lrp.2009.07.006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref109">
        <label>109</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Saia</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Cavagna</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Beretta</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Pineau</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Martelli</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Economic and organisational impacts of medical device regulation in Europe: is the price too high for small and medium enterprises?</article-title>
          <source>Health Policy Technol</source>
          <year>2023</year>
          <month>12</month>
          <volume>12</volume>
          <issue>4</issue>
          <fpage>100789</fpage>
          <pub-id pub-id-type="doi">10.1016/j.hlpt.2023.100789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref110">
        <label>110</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Diderich</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Diderich</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Revisiting the business model canvas as a common language</article-title>
          <source>Design Thinking for Strategy: Management for Professional</source>
          <year>2020</year>
          <publisher-loc>Cham, Switzerland</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref111">
        <label>111</label>
        <nlm-citation citation-type="web">
          <article-title>GPT-4</article-title>
          <source>OpenAI</source>
          <access-date>2025-01-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openai.com/index/gpt-4/">https://openai.com/index/gpt-4/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
