<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="news"><front><journal-meta><journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id><journal-id journal-id-type="publisher-id">jmir</journal-id><journal-id journal-id-type="index">1</journal-id><journal-title>Journal of Medical Internet Research</journal-title><abbrev-journal-title>J Med Internet Res</abbrev-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">v28i1e116091</article-id><article-id pub-id-type="doi">10.2196/116091</article-id><article-categories><subj-group subj-group-type="heading"><subject>News and Perspectives</subject></subj-group></article-categories><title-group><article-title>One Patient, Five Apps: Is This Really Better Care?</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Peters</surname><given-names>Vincent</given-names></name><role>JMIR Correspondent</role></contrib></contrib-group><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Clegg</surname><given-names>Kayleigh-Ann</given-names></name></contrib></contrib-group><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>11</day><month>11</month><year>2026</year></pub-date><volume>28</volume><elocation-id>e116091</elocation-id><history><date date-type="received"><day>03</day><month>11</month><year>2026</year></date><date date-type="accepted"><day>03</day><month>11</month><year>2026</year></date></history><copyright-statement>&#x00A9; JMIR Publications. Originally published in the Journal of Medical Internet Research (<ext-link ext-link-type="uri" xlink:href="https://www.jmir.org">https://www.jmir.org</ext-link>), 11.11.2026. </copyright-statement><copyright-year>2026</copyright-year><self-uri xlink:type="simple" xlink:href="https://www.jmir.org/2026/1/e116091"/><abstract><p>Mobile health apps can facilitate monitoring, communication, and administration in health care settings, but their accumulation may also create app overload for both patients and professionals. In this <italic>News and Perspectives</italic> article, JMIR Correspondent and health care digitalization researcher Vincent Peters reports on the increasing complexity of navigating digital health care.</p></abstract><kwd-group><kwd>digital health</kwd><kwd>apps</kwd><kwd>fragmentation</kwd><kwd>interoperability</kwd><kwd>patient perspective</kwd><kwd>professional perspective</kwd></kwd-group></article-meta></front><body><boxed-text id="IB1"><p><bold>Key Takeaways:</bold></p><list list-type="bullet"><list-item><p>More apps result in a fragmented digital landscape.</p></list-item><list-item><p>Not every digital functionality needs its own app.</p></list-item><list-item><p>The goal may be one front door, not one app, that hides technical complexity.</p></list-item></list></boxed-text><p><italic>Vincent Peters, PhD, is an assistant professor at the Department of Information Systems and Operations Management at Tilburg University. His research is focused on the organization/delivery of (digital) health care. In this op-ed, he draws on a series of unstructured interviews he conducted with a range of relevant stakeholders across the hospital ecosystem, including physicians, patients, health care managers, and innovators, from three hospitals and one clinic in the Netherlands.</italic></p><p>There seems to be an app for almost every aspect of our health. Apps can help us monitor symptoms, recover from injuries, communicate with health care professionals, schedule appointments, and manage chronic conditions, among other things. Each app promises to make health care a little bit better. Taken together, however, they may be doing the opposite.</p><p>Take the following example. A patient leaves the health care organization after treatment. They already have access to the organization&#x2019;s patient portal containing their appointments, medical correspondence, and test results. Before going home, the patient is asked to download a separate app to guide their recovery. Yet another app is needed for questionnaires and for monitoring health status. Each app in itself may work perfectly fine, but each app also introduces another interface, another account, another source of information, and potentially another workflow for the health care professionals taking care of that patient.</p><p>For patients recovering from a single injury, one additional app might not seem burdensome. As a patient in episodic care noted, &#x201C;What is wrong with downloading an app? I also do this when a new mobile game releases, so I do not see an issue here.&#x201D; But the situation looks different from the perspective of someone living with chronic diseases who receives care from several departments or health care organizations that each have their own app. As one chronic care patient said, &#x201C;By now I have four apps on my phone which are not linked and require action at various moments in time. I am starting to lose track of it all.&#x201D; In this context, the burden of managing and scheduling remote monitoring activities across apps compounds for patients.</p><p>Health care professionals experience similar issues on the other side. Digital tools require them to monitor various dashboards, move between apps, and document information in more than one place. This introduces a paradox: while each distinct app can simplify individual parts of care, they make the overall care trajectory more complex.</p><sec id="s1"><title>We Have Been Here Before</title><p>The proliferation of apps is hardly new. <ext-link ext-link-type="uri" xlink:href="https://link.springer.com/article/10.1007/s12445-017-0274-6">Loohuis and Chavannes</ext-link> described the rapid growth of apps; by 2016, more than 250,000 health-related apps were already available across the three largest app platforms at the time: iOS, Android, and Windows. Their concerns focused mainly on whether these rapidly emerging apps were effective, reliable, and sufficiently user centric.</p><p>But the number of available apps continued to grow. In 2019, Dutch public broadcaster NOS reported <ext-link ext-link-type="uri" xlink:href="https://nos.nl/artikel/2290281-zorgen-over-wildgroei-van-gezondheidsapps-er-is-veel-zooi-op-de-markt">more than 350,00 health-related apps</ext-link> in the App Store and Google Play Store. This fragmented landscape of apps that often fail to connect with one another&#x2014;what one innovation manager at the Sint Maartens Clinic calls &#x201C;the Wild Wild West of apps&#x201D;&#x2014;may be <ext-link ext-link-type="uri" xlink:href="https://www.bnr.nl/nieuws/tech-innovatie/10598682/digitale-zorg-in-nederland-stagneert-door-wildgroei-aan-apps-wel-80-zorgapps">holding back digital care in the Netherlands</ext-link>.</p><p>The concern now is different from the one raised almost a decade ago. Even if every individual app works as intended, how do patients and professionals deal with their <ext-link ext-link-type="uri" xlink:href="https://journals.plos.org/digitalhealth/article?id=10.1371/journal.pdig.0001107">accumulation</ext-link>?</p></sec><sec id="s2"><title>Accumulating Apps</title><p>For an individual app to work in daily life, using it must become part of someone&#x2019;s routine. Patients need to know when and how to use the app. Professionals need to know where information enters, when it needs to be checked, and what action is expected. This is already complicated in itself&#x2014;even more so when you start adding apps up.</p><fig position="float" id="figureWL1"><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e116091_fig01.png"/></fig><p>In conversations with health care professionals, a recurring concern was not necessarily that individual apps were difficult to work with. Rather, they described the issue of having to look in different places and work across different systems: when, in their already busy workdays, are they to navigate multiple systems?</p><p>&#x201C;These apps are great when they work,&#x201D; said one gastroenterologist at the Franciscus Hospital Rotterdam. &#x201C;But they also put a burden on me as a professional in order to figure out where to find the required data in the short amount of time I have for a patient.&#x201D; This relates to the growing discussion on <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/2026/1/e104196">digital fatigue</ext-link>, where the accumulation of digital demands can create an additional and sometimes invisible layer of work for health care professionals.</p></sec><sec id="s3"><title>What if the App Did Not Need to Be an App?</title><p>Before wondering which app to use or suggest, we should first check if the specific functionality needs to exist in a separate app at all and weigh potential trade-offs.</p><p>Stand-alone apps can be valuable. They can focus on a specific clinical problem, provide a specialized functionality, and sometimes offer a more tailored user experience. As one patient noted, there&#x2019;s often an element of simplicity: &#x201C;I just download the app and remove it when I don&#x2019;t need it anymore. It is just like using a non-health app like my bank account.&#x201D;</p><p>One trauma surgeon described a stand-alone app for fracture aftercare as &#x201C;super clear and very user friendly.&#x201D; Moving the same functionality into a patient portal, <ext-link ext-link-type="uri" xlink:href="https://www.etz.nl/actueel/patient-met-licht-letsel-hoeft-niet-meer-terug-naar-ziekenhuis-voor-controle/">as they did at Elisabeth-TweeSteden Hospital</ext-link>, can result in integration gains. As a senior health care technology advisor at the hospital remarked, &#x201C;I think that having everything in one place makes it much easier and more accessible in terms of patient and consumer experience.&#x201D; However, it could also introduce additional barriers, like two-factor authentication, which is considered frustrating by some patients. As one patient noted, &#x201C;Two-factor authentication is so annoying; as a result, I sometimes simply refuse to look into the patient portal.&#x201D;</p><p>Both can be true: a stand-alone app can provide an excellent user experience in isolation, but the fifth excellent app is still a <italic>fifth</italic> app. To avoid adding burden, what matters is how the app fits into everything that patients and professionals are already expected to use.</p></sec><sec id="s4"><title>One Front Door</title><p>The alternative to this fragmentation is not one app that does everything. A more realistic ambition may be one <ext-link ext-link-type="uri" xlink:href="https://www.sciencedirect.com/science/article/pii/S0277953626006489?via%3Dihub">digital front door</ext-link>.</p><p>This ambition is beginning to take shape in the Netherlands. Initiatives around <ext-link ext-link-type="uri" xlink:href="https://www.icthealth.nl/nieuws/pgo-moet-centraal-punt-worden-voor-digitale-zorgtaken">personal health environments</ext-link> aim to give patients a central place to access information and care tasks from different health care providers and organizations. Other integration efforts allow health care professionals to review and manage patient information without switching between multiple apps. For example, at <ext-link ext-link-type="uri" xlink:href="https://www.zorgbijjou.nl/artikel/minder-schakelen-tussen-systemen-door-integratie-patient-journey-app-op-zorg-bij-jou-platform">OLVG, a hospital in Amsterdam</ext-link>, one initiative aims to centralize relevant information from different digital apps, including the Patient Journey App, into a single remote patient monitoring platform. These are examples of progress toward a front door, suggesting that such a thing can be built.</p><p>As one software developer put it, digital care should provide &#x201C;one front door&#x201D; for the patient and one for the health care professional and, as such, &#x201C;take &#x2018;care&#x2019; [of] both the patient AND the professional.&#x201D; This front door would allow apps to continue to run behind the scenes, allowing the technical ecosystem to remain diverse while the user experience becomes less fragmented.</p><p>Rather than a discussion of &#x201C;which app to use,&#x201D; the fundamental challenge now is <ext-link ext-link-type="uri" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S1386505623003532?via%3Dihub">interoperability</ext-link>, that is, integrating across different apps for a more cohesive experience in which the future question may be &#x201C;does the user have to know how many apps are involved at all?&#x201D;</p></sec></body><back/></article>