<?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="research-article"><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">v28i1e105987</article-id><article-id pub-id-type="doi">10.2196/105987</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Implementation and Evaluation of the Stroke Triage App Among Paramedics in Prehospital Emergency Care: Sequential Mixed Methods Study</article-title></title-group><contrib-group><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Kremers</surname><given-names>Femke</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name name-style="western"><surname>Hu</surname><given-names>Ellen</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Silkens</surname><given-names>Milou</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>de Ruijter</surname><given-names>Naomi</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>van de Wijdeven</surname><given-names>Ruben M.</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Venema</surname><given-names>Esmee</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kerkhoff</surname><given-names>Henk</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>S&#x00FC;lz</surname><given-names>Sandra</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Roozenbeek</surname><given-names>Bob</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><collab>On behalf of the PRESTO-2 Investigators</collab><xref ref-type="aff" rid="aff5">5</xref><xref ref-type="aff" rid="aff6">6</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Neurology, Erasmus MC University Medical Center</institution><addr-line>Rotterdam</addr-line><addr-line>Zuid-Holland</addr-line><country>The Netherlands</country></aff><aff id="aff2"><institution>Department of Health Services Management &#x0026; Organization, Erasmus School of Health Policy &#x0026; Management, Erasmus University Rotterdam</institution><addr-line>Burgemeester Oudlaan 50</addr-line><addr-line>Rotterdam</addr-line><addr-line>Zuid-Holland</addr-line><country>The Netherlands</country></aff><aff id="aff3"><institution>Department of Emergency Medicine, Erasmus MC University Medical Center</institution><addr-line>Rotterdam</addr-line><addr-line>Zuid-Holland</addr-line><country>The Netherlands</country></aff><aff id="aff4"><institution>Department of Neurology, Albert Schweitzer Hospital</institution><addr-line>Dordrecht</addr-line><addr-line>Zuid-Holland</addr-line><country>The Netherlands</country></aff><aff id="aff5"><institution>See Acknowledgments</institution></aff><aff id="aff6">Duijvenbooden Jasper van, Beekers Ines, Kruyt Nyika, Dusseljee-Peute Linda, Smeekes Martin, Dippel Diederik, Dorresteijn Kirsten, Wijnhoud Annemarie, IJzermans Jim, Geest Patrick van der, Willeboer Merel</aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Cardoso</surname><given-names>Taiane de Azevedo</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Svendsen</surname><given-names>Edel Jannecke</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Guterud</surname><given-names>Mona</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Ellen Hu, MSc, Department of Health Services Management &#x0026; Organization, Erasmus School of Health Policy &#x0026; Management, Erasmus University Rotterdam, Burgemeester Oudlaan 50, Rotterdam, Zuid-Holland, 3062 PA, The Netherlands, 31 0619673391; <email>hu@eshpm.eur.nl</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>3</day><month>11</month><year>2026</year></pub-date><volume>28</volume><elocation-id>e105987</elocation-id><history><date date-type="received"><day>02</day><month>07</month><year>2026</year></date><date date-type="rev-recd"><day>22</day><month>09</month><year>2026</year></date><date date-type="accepted"><day>25</day><month>09</month><year>2026</year></date></history><copyright-statement>&#x00A9; Femke Kremers, Ellen Hu, Milou Silkens, Naomi de Ruijter, Ruben M. van de Wijdeven, Esmee Venema, Henk Kerkhoff, Sandra S&#x00FC;lz, Bob Roozenbeek. 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>), 3.11.2026. </copyright-statement><copyright-year>2026</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 (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), 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 <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/">https://www.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://www.jmir.org/2026/1/e105987"/><abstract><sec><title>Background</title><p>Digital decision-support tools, such as the Stroke Triage App (STA), may enhance prehospital triage and clinical decision-making for suspected patients with stroke. However, implementation of decision-support tools and their impact on clinical practice remains insufficiently studied.</p></sec><sec><title>Objective</title><p>This study aimed to investigate paramedics&#x2019; experiences with the implementation of the STA in prehospital practice by evaluating the implementation process, the implementation outcomes, and its impact on clinical workflows, while considering contextual factors that may have influenced these dimensions.</p></sec><sec sec-type="methods"><title>Methods</title><p>STA implementation was evaluated among paramedics in 2 emergency medical services regions in the Netherlands using a sequential mixed methods approach. Actual usage data were extracted from the STA dashboard. Usability, perceived impact, and contextual factors were explored using an online survey and semistructured interviews.</p></sec><sec sec-type="results"><title>Results</title><p>Monthly triages ranged from 52 to 153 (median 120, IQR 107&#x2010;131). Paramedics&#x2019; individual STA use ranged from 1 to 47 times (median 7, IQR 3&#x2010;13). Out of 246 paramedics with an account, 76 (31%) completed the survey, and 9 (4%) participated in semistructured interviews. The STA was generally well accepted, supporting structured neurological assessment and communication. Swift technical support, frequent promotion, and use of local ambassadors facilitated STA use. Clinical urgency, poor workflow integration, and limited perceived added value hampered STA use. Users recommended improvements in mobile interface, login features, and additional explanation with triage advice.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>This study demonstrates that the STA achieved substantial reach and initial adoption within the prehospital setting. However, widespread acceptance did not consistently translate into routine integration in daily practice. Successful implementation depends as much on addressing organizational and human factors as on technical performance.</p></sec></abstract><kwd-group><kwd>telehealth usability</kwd><kwd>stroke</kwd><kwd>prehospital triage</kwd><kwd>mixed methods</kwd><kwd>impact</kwd><kwd>implementation</kwd><kwd>telehealth tools</kwd><kwd>digital health technology</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Digital health technologies are increasingly developed and introduced into health care systems to support clinical decision-making, enhance efficiency, and improve patient outcomes [<xref ref-type="bibr" rid="ref1">1</xref>]. To date, research has predominantly focused on the technical validation of these tools, often underexploring the broader sociotechnical dimensions that determine implementation success [<xref ref-type="bibr" rid="ref2">2</xref>]. Consequently, translating technological promises into real-world clinical impact remains challenging, as the complex interplay of organizational, clinical, and human factors often influences success beyond mere technical performance [<xref ref-type="bibr" rid="ref3">3</xref>].</p><p>This challenge is particularly evident in the setting of prehospital emergency care, where paramedics must make time-critical decisions under rapidly changing clinical and logistical circumstances [<xref ref-type="bibr" rid="ref4">4</xref>]. When introducing digital decision-support tools in this setting, specific barriers often emerge. For instance, the time investment required for data entry and device interaction creates a burden that competes directly with urgent patient care [<xref ref-type="bibr" rid="ref5">5</xref>]. Furthermore, technical limitations, such as unreliable connectivity or environmental constraints limiting device usability, frequently disrupt established clinical workflows [<xref ref-type="bibr" rid="ref6">6</xref>]. Beyond these practical hurdles, concerns over professional autonomy often hinder trust [<xref ref-type="bibr" rid="ref7">7</xref>]. Paramedics may perceive such tools as a threat to their expertise, particularly when recommendations lack transparent reasoning or fail to account for the intuitive judgment required in the field.</p><p>Such challenges are especially relevant for acute ischemic stroke, where the time sensitivity of reperfusion therapies underscores the negative impact of any technical or operational delay [<xref ref-type="bibr" rid="ref4">4</xref>]. Traditionally, stroke care has followed a &#x201C;drip-and-ship&#x201D; model, with patients transported to the nearest hospital regardless of stroke subtype [<xref ref-type="bibr" rid="ref8">8</xref>]. However, as eligibility for endovascular treatment (EVT) continues to expand, the need for rapid triage of patients with a suspected large vessel occlusion (LVO) to EVT-capable hospitals has become increasingly urgent [<xref ref-type="bibr" rid="ref9">9</xref>]. Since treatment delays are strongly associated with poorer patient outcomes, optimizing prehospital triage has emerged as a key strategy to address the logistical challenges of regional stroke networks, thereby reducing unnecessary transfers and accelerating EVT for eligible patients [<xref ref-type="bibr" rid="ref10">10</xref>].</p><p>Within the Dutch health care network, the proximity of general hospitals and EVT-capable hospitals poses a triaging dilemma. Paramedics must balance the benefit of immediate intravenous thrombolysis (IVT) at a nearby general hospital against the risk of delayed EVT or the need for secondary transfer [<xref ref-type="bibr" rid="ref11">11</xref>]. This decision is further complicated by the diagnostic uncertainty of prehospital screening tools and unknown hospital workflow times [<xref ref-type="bibr" rid="ref12">12</xref>]. To optimize prehospital triage, digital decision-support tools such as the Stroke Triage App (STA) have been developed and introduced by a multidisciplinary team of clinical stroke experts, paramedics, and technical developers [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. With the aim to assist paramedics in the complex decision-making process, the app integrates neurological clinical assessment via the Rapid Arterial Occlusion Evaluation (RACE) score (used to estimate the probability of an LVO) with contextual data, including symptom onset time, real-time GPS-based driving times, time-dependent treatment effects, and hospital workflow metrics [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref13">13</xref>]. The app combines these variables to estimate the probability of a good functional outcome at 3 months and recommends the optimal transport destination to the paramedic: the nearest general hospital or direct transfer to a more distant EVT-capable hospital.</p><p>Achieving the clinical value of the STA and ultimately improving patient outcomes requires not only technical accuracy but also successful implementation, integration into clinical workflows, and acceptance by paramedics, within the context in which the implementation takes place [<xref ref-type="bibr" rid="ref11">11</xref>]. Evaluating such implementation efforts requires answering 3 complementary questions: how was the tool introduced and perceived by its users, to what extent was it adopted and used in practice, and what was its downstream effect on daily clinical routines? This study investigates paramedics&#x2019; experiences with the implementation of the STA in the prehospital practice by evaluating the implementation process, the implementation outcomes, and its impact on clinical workflows while considering contextual factors that may have influenced these dimensions. By integrating quantitative and qualitative data, we aim to generate actionable insights for optimizing the implementation of digital health tools in prehospital emergency care.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Setting</title><p>The study was conducted within 2 emergency medical service (EMS) regions in the Netherlands: Rotterdam-Rijnmond and Zuid-Holland Zuid. This region consists of 2 EVT-capable hospitals and 7 general hospitals, where only IVT is available. Together, these EMS organizations cover a population of approximately 1.7 million inhabitants in an area of 863 km<sup>2</sup> (Rotterdam-Rijnmond) and 720 km<sup>2</sup> (Zuid-Holland Zuid), with a total estimated 5000 suspected strokes yearly [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. Approximately 250 licensed ambulance paramedics were employed across these 2 regions. The STA was implemented in January 2024 in both regions as part of the Prehospital Triage of Patients With a Suspected Acute Stroke (PRESTO-2) study and formally introduced as the standard of care for prehospital stroke triage [<xref ref-type="bibr" rid="ref15">15</xref>]. The STA is registered as a Conformit&#x00E9; Europ&#x00E9;enne (CE)-compliant medical device and as a Medical Device Regulation (MDR) class I software (The European Database on Medical Devices [EUDAMED], unique device identification-device identifier [UDI-DI]: 08720892217905).</p></sec><sec id="s2-2"><title>Study Design</title><p>Embedded within the PRESTO-2 study, this study used a sequential explanatory mixed methods design [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. The quantitative phase integrated objective dashboard analytics with survey data (<xref ref-type="fig" rid="figure1">Figure 1</xref>). The dashboard was used to monitor actual STA engagement throughout the implementation period by tracking longitudinal data (eg, monthly triage volumes and active user rates). These insights provided a baseline of system usage, while the survey captured paramedics&#x2019; initial perceptions of the implementation process, perceived usability, and attitudes toward long-term sustainability. Combined, these quantitative findings provided preliminary insights into potential implementation challenges, which informed the subsequent qualitative phase. This second phase consisted of semistructured interviews designed to contextualize and nuance the quantitative results by exploring the contextual factors shaping the implementation process, outcomes, and workflow impact.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Schematic overview of the study design.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e105987_fig01.png"/></fig><p>To evaluate paramedics&#x2019; experiences with the implementation of the STA, the study focused on 3 core concepts: the implementation process, the implementation outcomes, and the impact on clinical workflow (<xref ref-type="table" rid="table1">Table 1</xref>). These concepts were informed by established implementation science frameworks, including the Non-adoption, Abandonment, Scale-up, Spread, Sustainability (NASSS) Framework [<xref ref-type="bibr" rid="ref3">3</xref>], Consolidated Framework for Implementation Research (CFIR) [<xref ref-type="bibr" rid="ref17">17</xref>], and the Unified Theory of Acceptance and Use of Technology (UTAUT) [<xref ref-type="bibr" rid="ref18">18</xref>] (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>), which guided the operationalization of both the survey items and the interview guide. Methodological rigor was ensured by adhering to the Good Reporting of a Mixed Methods Study (GRAMMS) checklist [<xref ref-type="bibr" rid="ref19">19</xref>], which provides a structured framework for transparent and comprehensive reporting of mixed methods research (<xref ref-type="supplementary-material" rid="app5">Checklist 1</xref>).</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Operationalization of implementation dimensions.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Dimension</td><td align="left" valign="bottom">Definition</td><td align="left" valign="bottom">Key elements explored</td></tr></thead><tbody><tr><td align="left" valign="top">Implementation process</td><td align="left" valign="top">The execution of the introduction strategy and how it was perceived by the users</td><td align="left" valign="top">Training and instruction, perceived technical support, promotion, and organizational communication</td></tr><tr><td align="left" valign="top">Implementation outcomes</td><td align="left" valign="top">The measurable results and future potential of the implementation effort</td><td align="left" valign="top">Actual usage rates (dashboard data), system usability, and perspectives on sustainability</td></tr><tr><td align="left" valign="top">Impact on workflow</td><td align="left" valign="top">The perceived effect of the STA<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup> on paramedics&#x2019; daily professional practice and routines</td><td align="left" valign="top">Integration into prehospital clinical workflows, perceived system usability</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>STA: Stroke Triage App.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-3"><title>Implementation Strategy</title><p>The introduction of the STA took place through intranet announcements, e-mail, and local ambassadors, both prior to and during the initial implementation phase. Paramedics were required to complete an online e-learning module, consisting of an instructional video and text on the STA website, as a prerequisite for account activation and clinical use. Implementation was further supported by promotional activities, including monthly newsletters, incentives (eg, cake or gift cards for every 100th patient triaged), and regular visits to ambulance stations, alongside branded promotional materials (eg, branded candy jars) to enhance visibility. Local ambassadors were appointed in each ambulance region to provide support, promote the app among colleagues, and to redirect questions to the research team. In addition, a user council consisting of paramedics was regularly consulted before and during the implementation to provide practical input on development and operational aspects. Throughout the implementation process, the use of the STA was communicated as part of the standard protocol. Although nonuse did not result in formal consequences, medical managers and the research team encouraged its use. However, use of the STA remained entirely voluntary, and paramedics were never obligated to use the app.</p></sec><sec id="s2-4"><title>Study Sample</title><p>The study population consisted of all licensed paramedics employed within the participating EMS regions. For the dashboard analysis, all active STA users during the implementation period were included. Eligibility for participation in the survey and interviews was restricted to paramedics active in clinical practice, regardless of their frequency of STA use.</p></sec><sec id="s2-5"><title>Quantitative Phase: Dashboard Analytics and Digital Survey</title><sec id="s2-5-1"><title>Dashboard Analytics</title><p>Objective STA usage parameters were obtained from real-time longitudinal dashboard data for both ambulance regions from the start of STA implementation until the closing of the survey (January 22, 2024, until June 17, 2025). This included the number of active accounts, the number of unique users per month, monthly triages, and number of STA usage per paramedic.</p></sec><sec id="s2-5-2"><title>Digital Survey</title><p>A custom digital survey was developed by FK and EH. The survey&#x2019;s functionality and content were tested in iterative rounds in which feedback was obtained from this project group, as well as the PRESTO-2 Advisory Board (consisting of regional EMS managers, paramedics, implementation researchers, and the STA software developer). Additional input was gathered during meetings within a research group focused on stroke research [<xref ref-type="bibr" rid="ref20">20</xref>]. These review rounds led to refinements in the survey interface, item wording, and inclusion of context-specific content. The final Dutch formulated survey was hosted in Qualtrics survey software (version XM; Qualitrics LLC) [<xref ref-type="bibr" rid="ref21">21</xref>].</p><p>The survey consisted of 39 validated as well as self-developed questions, using 5-point Likert scales (strongly agree to strongly disagree), multiple-choice questions, and open-ended fields for textual feedback (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>). A detailed overview of the survey constructs, item counts, and psychometric properties is available (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). A key component of the survey was the validated Dutch version of the Digital System Usability Scale (D-SUS), which was used to assess the technical usability of the STA with a score ranging from 0 to 100, indicating poor usability for scores below 50, moderate usability for scores between 50 and 68, and good usability for scores above 68 [<xref ref-type="bibr" rid="ref22">22</xref>]. Additionally, the survey collected demographic data, including sex, age, employment status, education level, and professional experience. The survey was filled in anonymously, and participants were invited at the end to provide contact details for follow-up interviews.</p><p>From March 27 to June 17, 2025, all licensed ambulance paramedics employed across the 2 study regions (~250 paramedics) were invited to participate. Recruitment was conducted through a multichannel approach. The survey was initially distributed by regional medical managers via e-mail, using their complete staff mailing lists, followed by a notice posted on the regional intranet. Subsequently, FK, EH, and NdR visited 3 ambulance stations per participating region to further promote the study, distributing flyers containing a QR code linking directly to the survey. A total of 2 push notifications inviting participation were additionally issued within the STA.</p></sec></sec><sec id="s2-6"><title>Qualitative Phase: Semistructured Interviews</title><p>The interview guide was grounded in the study&#x2019;s core concepts (<xref ref-type="table" rid="table1">Table 1</xref>) and further informed by survey results. Iterative revisions within the project group led to further specification of topics and rephrasing of questions. The interview guide was pilot tested between EH and NdR to evaluate the completeness and clarity of the questions, resulting in the final version (<xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>).</p><p>Participants were recruited via voluntary self-selection, following an open invitation through newsletters and the on-site visits described above, in addition to an invitation at the end of the digital survey. Snowball sampling was additionally used by asking interview participants at the end of each interview to suggest colleagues with potentially different perspectives [<xref ref-type="bibr" rid="ref23">23</xref>], though it yielded no additional participants. Data collection continued until thematic saturation was reached, assessed through interim analysis and team discussions, after which subsequent interviews yielded no new insights.</p><p>Interviews were conducted between July 8 and September 1, 2025, by either FK or EH as the primary interviewer, with NdR present in a supporting and moderating role. MS, a trained qualitative interviewer, was present during the first 4 interviews to provide support. The interviews were conducted online in Microsoft Teams, held in Dutch, and audio-recorded, pseudonymized, and transcribed verbatim in Microsoft Word by FK, EH, NdR, and RvdW. FK, NdR, and RvdW hold a medical background (MD) and were involved in the primary PRESTO-2 clinical validation study. EH and MS have a background in implementation science and were not involved in the primary clinical trial. Interviews lasted on average 39.6 (SD 6.7; range 30.6-51.6) minutes.</p></sec><sec id="s2-7"><title>Data Analysis and Integration</title><p>Survey data and dashboard metrics were analyzed descriptively using R Studio (Posit, PBC; version 4.4.2) [<xref ref-type="bibr" rid="ref24">24</xref>] to summarize participant characteristics, system usability (D-SUS scores), and actual usage patterns. If data were distributed normally, means and SDs were calculated. Otherwise, medians with IQR values were derived. Open-text survey responses were analyzed thematically to identify recurring topics. For cross-analysis between subgroups, such as years of experience or attitude toward technology, the Pearson chi-square test was used to assess statistical significance.</p><p>Interview transcripts were analyzed in ATLAS.ti (version 24; ATLAS.ti Scientific Software Development GmbH) using an inductive approach to thematic analysis, consisting of the following phases: familiarization with the data, generation of initial codes, searching for themes, reviewing themes, defining and naming themes, and producing the report [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Codes were derived directly from the data, while the study&#x2019;s 3 core concepts (<xref ref-type="table" rid="table1">Table 1</xref>) served as a sensitizing framework informing theme development. The first 2 interviews were independently coded by EH and MS. Discrepancies were discussed until consensus was reached to calibrate the coding approach, after which EH coded the remaining transcripts. Emerging themes and subthemes were iteratively reviewed within the project group, with MS providing additional verification of the interpretations.</p><p>Data integration was performed by FK and EH. Findings from the quantitative and qualitative phases were integrated to identify convergence (confirmation), complementarity (expansion), or dissonance (divergence) between the data sources. This process facilitated the development of integrated insights from both methods. The visualization of this integration is presented in a joint display, aligning the quantitative metrics with corresponding qualitative themes.</p></sec><sec id="s2-8"><title>Ethical Considerations</title><p>This study was approved by the Medical Ethics Review Committee of Erasmus Medical Center, Rotterdam, the Netherlands (MEC-2024&#x2010;0760). Informed consent was obtained electronically prior to completion. Respondents who expressed interest in follow-up interviews provided their contact details in a separate, unlinked section of the survey, and written informed consent was obtained prior to the interviews. Survey participants did not receive compensation. Interview participants each received a coffee voucher worth &#x20AC;10 (US $11.19) as a token of appreciation for their time. Survey data were anonymized, and interview data were pseudonymized. All data were handled in compliance with Dutch data protection regulations.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Study Population</title><p>A total of 2075 patients were triaged using the STA before the survey ended (1679 in ambulance region Rotterdam-Rijnmond and 396 in region Zuid-Holland Zuid), corresponding with approximately 28% (2075/7500) of the expected 7500 suspected strokes within the study period of 18 months. During this period, 1855 patients were advised to go to the nearest general hospital. In 220 (11%) cases, the STA advised bypassing the general hospital and transporting the patient directly to an EVT-capable center. In 1448 (70%) cases, paramedics mentioned that they followed the advice. STA advice was not followed in 87 (4%) cases. In 540 (26%) cases, paramedics did not mention whether the STA advice was followed, since this question in the STA was not mandatory.</p><p>On June 17, 2025, 246 of the &#x00B1;250 employed paramedics had an STA account. In total, 85 (&#x00B1;34%) paramedics responded to the survey, of which 76 consented to participate, 24 agreed to being approached for an interview, and 9 ultimately participated in the semistructured interviews (<xref ref-type="fig" rid="figure2">Figure 2</xref>). A total of 7 (78%) participants that participated in the semistructured interviews were male, and the mean age was 39 (SD 7) years. Overall, 4 (44%) paramedics worked full-time, and median years of experience was 6 (IQR 6&#x2010;8). Survey demographics showed that most paramedics held a neutral to positive attitude toward technology and considered themselves average or advanced in their technology experience (<xref ref-type="table" rid="table2">Table 2</xref>).</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Flowchart of participant flow through the questionnaire and interviews.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e105987_fig02.png"/></fig><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Baseline characteristics of participants.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">Survey participants (n=76)</td></tr></thead><tbody><tr><td align="left" valign="top">Male, n (%)</td><td align="left" valign="top">30 (46)</td></tr><tr><td align="left" valign="top">Age (years), mean (SD)</td><td align="left" valign="top">43 (8)</td></tr><tr><td align="left" valign="top" colspan="2">Education level, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Senior vocational education</td><td align="left" valign="top">27 (36)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Higher professional education</td><td align="left" valign="top">31 (41)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>University</td><td align="left" valign="top">2 (3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Doctorate (PhD)</td><td align="left" valign="top">0</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Other</td><td align="left" valign="top">5 (7)</td></tr><tr><td align="left" valign="top">Full-time (&#x2265;36 hours/week), n (%)</td><td align="left" valign="top">26 (34)</td></tr><tr><td align="left" valign="top">Years of experience, median (IQR)</td><td align="left" valign="top">6 (4-14)</td></tr><tr><td align="left" valign="top" colspan="2">Device used for STA<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup>, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Smartphone</td><td align="left" valign="top">35 (46)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Tablet</td><td align="left" valign="top">34 (45)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No answer</td><td align="left" valign="top">7 (9)</td></tr><tr><td align="left" valign="top" colspan="2">Attitude toward health technology, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Very positive</td><td align="left" valign="top">11 (15)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Positive</td><td align="left" valign="top">32 (42)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Neutral</td><td align="left" valign="top">18 (24)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Negative</td><td align="left" valign="top">4 (5)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Very negative</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No answer</td><td align="left" valign="top">11 (15)</td></tr><tr><td align="left" valign="top" colspan="2">Experience level with health technology, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Beginner</td><td align="left" valign="top">2 (3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Average</td><td align="left" valign="top">37 (49)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Advanced</td><td align="left" valign="top">23 (30)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Expert</td><td align="left" valign="top">3 (4)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No answer</td><td align="left" valign="top">11 (15)</td></tr><tr><td align="left" valign="top" colspan="2">Use of technology in daily life, n (%)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Daily</td><td align="left" valign="top">63 (83)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Regular (3&#x2010;5 times/week)</td><td align="left" valign="top">2 (3)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Sometimes (1&#x2010;2 times/week)</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Rarely (&#x003C;1 time/week)</td><td align="left" valign="top">0 (0)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No answer</td><td align="left" valign="top">11 (15)</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>STA: Stroke Triage App.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Main Results</title><sec id="s3-2-1"><title>Overview</title><p>To investigate paramedics&#x2019; experiences with the implementation of the STA in prehospital practice, this study evaluated the implementation process, the implementation outcomes, and the tool&#x2019;s impact on clinical workflows, while considering contextual factors that may have influenced these dimensions. The concurrent analysis of both quantitative and qualitative data identified 6 key themes that structure the presentation of the results. These themes are (1) onboarding and engagement, (2) usability and practicality, (3) adoption attitudes, (4) actual usage, (5) assessment and handover, and (6) future perspectives. Findings are discussed according to these themes, integrating insights from both the quantitative survey and qualitative interviews (<xref ref-type="table" rid="table3">Table 3</xref>).</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Integration of quantitative and qualitative findings and the mixed methods meta-inference.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Theme</td><td align="left" valign="bottom">Quantitative results</td><td align="left" valign="bottom">Qualitative results</td><td align="left" valign="bottom">Integrated findings</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="4">Onboarding and engagement</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Introduction</td><td align="left" valign="top">Most paramedics heard of the STA<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup> through their management (24/76, 32%), a colleague (14/76, 18%), training (11/76, 14%), or a combination of the above (15/76, 20%).</td><td align="left" valign="top">Many recalled multiple channels including e-mail, personal messages and intranet. The introduction was positively received. Early informal communication occasionally led to misconceptions.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: multichannel exposure increases visibility of health device introduction.</p></list-item><list-item><p>Expansion: clear, uniform message important.</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Training</td><td align="left" valign="top">57% (43/76) mentioned receiving minimal training; 17% (13/76) did not remember any training. 41% (31/76) found training relevant; most were neutral regarding training (36/76, 47%).</td><td align="left" valign="top">The flexibility of digital modules was appreciated, in addition to practicing with test cases. The training provided was considered minimal but sufficient. However, some paramedics expressed a preference for in-person instruction and more in-depth information.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: digital health devices training tools must be accessible, concise, yet informative.</p></list-item><list-item><p>Expansion: In-person versus digital training preference varies per participant.</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Promotion</td><td align="left" valign="top">Most paramedics found promotion somewhat helpful (25/76, 33%). 13% (10/76) found it very helpful. Promotion was widely visible.</td><td align="left" valign="top">Promotion was seen by all interviewed paramedics and was overall deemed as helpful for visibility. Feedback, case discussions, and acknowledgment of users&#x2019; efforts were considered essential for maintaining awareness and reinforcing involvement.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: Repetitive promotion, timely feedback from support team, and acknowledgment of efforts are essential for visibility of digital health tool and implementation.</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="4">Usability and practicality</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Usability and practicality</td><td align="left" valign="top">Median D-SUS<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup> score was 67.5 (IQR 57.50&#x2010;77.50), corresponding with average usability, with a range of 35 to 92.5. 79% (60/76) found the STA easy or very easy to understand. 63% (48/76) found the STA accurate or very accurate.</td><td align="left" valign="top">The app was perceived as easy and intuitive to use. Its use in acute situations was sometimes challenging, as immediate patient care took priority. The tool was reported to be less suitable for patients with atypical or subtle symptoms.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: Ease of use and understandability is important. Minimization of technical barriers for app usage is crucial, such as login or mobile compatibility.</p></list-item><list-item><p>Contradiction: Even with ease of use, there may still be technical and clinical barriers in urgent settings that decrease digital health tool usability.</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="4">Adoption attitudes</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Demotivating and motivating factors</td><td align="left" valign="top">69% (52/76) had no or very few fears regarding STA use. 16% (12/76) were neutral; 1% (1/76) did have fears regarding STA use. Overall trust in the STA was high.</td><td align="left" valign="top">Confidence in the tool increased with repeated use. Limited understanding of the rationale underlying STA advice sometimes led to frustration and reduced confidence, which could be restored after consultation from the research team.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: No fear regarding usage of STA. Transparency and explanation with the given advice is crucial for confidence.</p></list-item></list></td></tr><tr><td align="left" valign="top">Actual usage</td><td align="left" valign="top">2075 triages were performed until survey completion. The total number of monthly triages ranged from 52 to 153 (IQR 107&#x2010;131). 246 active accounts were registered. Frequency of STA use ranged from 1 to 47, median 7 times (IQR 3&#x2010;13). Unique users per month ranged from 40 to 94, median 81 (IQR 74&#x2010;83).<break/>96% (73/76) had used the STA at the time of survey completion. Median duration of use was 12 months (IQR 10 to 12; range 3&#x2010;14). In the month prior to the survey, 40% (30/76) used the STA in more than 60% of eligible cases, 20% (15/76) in 40% to 60%, 13% (10/76) in 20% to 40%, and 17% (13/76) in less than 20%. Regarding completion, 33 paramedics (43%) reported that they often completed all STA steps, 27 (36%) indicated that they always did so. STA use remained stable for 43 respondents (57%), increased for 11 (15%), and decreased for 15 (20%). Smartphones (35/76, 46%) and tablets (34/76, 45%) were used almost equally to access the application.</td><td align="left" valign="top">During early phases of implementation, app usage was not yet routine practice. It was sometimes unclear whether STA use was standard protocol or optional for research purposes. Paramedics were less likely to use the STA when an LVO<sup><xref ref-type="table-fn" rid="table3fn3">c</xref></sup> was clinically apparent or when they considered their own clinical judgment sufficient.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Expansion: STA usage varies greatly among paramedics, as well as varying in time. These factors are dependent on the integration of workflow routine, practical and technical barriers, and perceived added value.</p></list-item></list></td></tr><tr><td align="left" valign="top">Assessment and handover</td><td align="left" valign="top">Median reported STA use was 5 minutes (IQR 3&#x2010;5). 73 participants used the STA (73/76, 96%). 57% (43/76) of paramedics&#x2019; use has stayed equal during STA deployment. 15% (11/76) reported increased STA use; 20% (15/76) reported decreased STA use. Most often, they completed or always completed all STA steps (60/76, 79%). 34% (25/76) found their workflow improved or improved greatly, 47% (36/76) found their workflow stayed the same. 5% (4/76) found their workflow had gotten worse.</td><td align="left" valign="top">Interview respondents generally perceived the STA as a small component within their broader tasks of responsibilities, which did not substantially alter their workflow. STA provided support in communication with neurologists, reducing discussion time in accordance with regional care agreements, and paramedics appreciated the systematic overview of the patient.<break/>Paramedics felt that the STA use contributed to improved patient outcomes and fewer interhospital transfers.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: The STA had minimal impact on clinical workflow.</p></list-item><list-item><p>Expansion: The STA may save time through more effective communication, less discussion, and a more systematic neurological examination, leading to better clinical understanding.</p></list-item></list></td></tr><tr><td align="left" valign="top">Future perspectives</td><td align="left" valign="top">59% (45/76) of paramedics were likely or very likely to use the STA in the future. 17% (13/76) were neutral, 8% (6/76) were not likely to use the STA in the future.</td><td align="left" valign="top">Continued use was considered acceptable only if the tool provides clear added clinical value and is easy to use. For future implementation, paramedics emphasized the importance of improved usability and workflow integration.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Confirmation: Positive intentions for future use, but is conditional on added clinical value, workflow integration, and technical ease of use.</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>STA: Stroke Triage App.</p></fn><fn id="table3fn2"><p><sup>b</sup>D-SUS: Digital System Usability Scale.</p></fn><fn id="table3fn3"><p><sup>c</sup>LVO: large vessel occlusion</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2-2"><title>Theme 1: Onboarding and Engagement</title><p>Most respondents reported in the survey that they first learned about the STA through their management (24/76, 32%). In the interviews, however, several respondents described learning about the STA through multiple channels, including e-mail, personal messages, and the intranet. Survey respondents perceived the promotion of the STA generally as helpful: 25 (33%) rated it as somewhat helpful, 22 (29%) were neutral, and 10 (13%) found it very positive. Interviewees generally spoke positively about the introduction, noting that repeated promotion (including newsletters, dashboard access, posters, on-site visits, and rapid responses from the research team) helped them remain engaged with the STA.</p><disp-quote><p>In the beginning, the app sparked a lot of conversation among colleagues. However, as it was used for a longer period, it became less special and everyone developed their own way of working with it. The promotion was very well done and showed that the research team genuinely put in effort. Still, over time, we found our own routine with STA, and promotion became less impactful once everyone was already familiar.</p><attrib>P4</attrib></disp-quote><p>Early informal communication during the implementation process occasionally caused misunderstandings. For example, some interviewees reported fears that using the STA would be mandatory or would reduce their autonomy. Respondents described that clear and timely communication between regional medical managers, research nurses, and the research team helped prevent these misunderstandings and increased their acceptance of the STA.</p><disp-quote><p>It felt like we had to fill in something for every neurological patient, which made me worry about losing autonomy and turning exams into a rigid step-by-step process.</p><attrib>P8</attrib></disp-quote><p>Regarding training, survey respondents reported varying experiences. A total of 43 (57%) respondents reported following minimal training, while 13 (17%) did not remember receiving any training. Most respondents found the training relevant (31/76, 41%) and 24 (32%) considered it efficient, whereas 36 (47%) were neutral. Interviewees appreciated the flexibility of digital modules and the opportunity to practice with test cases, although some mentioned that they would have preferred in-person training for a deeper practical understanding.</p><disp-quote><p>'I found the training clear. Everything was fine. It was clear what needed to be scored and how. So technologically, it was straightforward.</p><attrib>P3</attrib></disp-quote><disp-quote><p>I remember completing the training, but I felt the background information could have been more comprehensive; it was minimal. I would have liked to understand why we needed to perform the tests within the RACE score.</p><attrib>P4</attrib></disp-quote><p>Interviewees emphasized that feedback, case discussions, and acknowledgment of their efforts through small tokens of appreciation (eg, candy or gift cards) were essential for maintaining awareness of the STA and reinforcing engagement. Respondents noted that their interest tended to fade once the initial novelty wore off. Case-based learning and real-world examples further motivated paramedics by demonstrating the STA&#x2019;s added clinical value. Interviewees explained that local ambassadors at ambulance posts supported colleagues and encouraged uptake, but highlighted that familiarization took time, and periods without stroke cases sometimes led to forgetting the STA. Some paramedics admitted postponing practice with the STA despite encouragement, which occasionally resulted in difficulties during real encounters.</p><disp-quote><p>In the early phase, colleagues could open the app, but no one was really using it yet. It took a little time before people thought, &#x2018;Oh right, let&#x2019;s fill in the app.&#x2019;</p><attrib>P4</attrib></disp-quote></sec><sec id="s3-2-3"><title>Theme 2: Usability and Practicality</title><p>Survey respondents generally reported that the STA was easy to understand: 37 paramedics (49%) rated it as easy, and 23 ( 30%) rated it as very easy. Regarding accuracy, 41 respondents (54%) considered the STA advice accurate, with 7 (9%) rating it as very accurate. These survey findings were supported by interviewees, who described the STA as intuitive, quick, and straightforward to use, highlighting its practical value in everyday clinical situations.</p><disp-quote><p>And when I tried it once during a slow shift, it worked fine, so I didn&#x2019;t have any problems with it.</p><attrib>P1</attrib></disp-quote><p>However, interviewees also emphasized that STA use in acute situations could be challenging, as immediate patient care took priority. They described practical and technical barriers, including short transport times, hygiene constraints, multitasking, login difficulties, and complex patient presentations, that sometimes led to delayed or postponed STA use after initial treatment. Several respondents noted that the tool was less suitable for patients with atypical or subtle symptoms. In some cases, these barriers resulted in nonuse altogether, for instance in unstable patients, very short transport times, or proximity to an intervention center.</p><disp-quote><p>It&#x2019;s an extra step, which usually isn&#x2019;t a problem, but we typically want to do it once we&#x2019;re in the ambulance and on the way to the hospital, that&#x2019;s when we handle the paperwork. If it&#x2019;s a suspected stroke, do we really want to open the app before leaving to decide where to go? It adds time, especially if you must find your password, and it&#x2019;s not ideal when the patient has vomited, a head wound, or any other urgent issue. That&#x2019;s not the best moment to pull out your phone and look for a password.</p><attrib>P1</attrib></disp-quote><disp-quote><p>The times I don&#x2019;t use the app are usually when I already know it will be a general hospital, or the situation is difficult: it&#x2019;s dark, which makes assessing the patient difficult, the patient is vomiting, or the communication with the family is challenging. That makes it extra hard. Most of the time, it ends up being a general hospital anyway. When I do fill it in, it usually doesn&#x2019;t surprise me.</p><attrib>P3</attrib></disp-quote><p>The median D-SUS score was 67.5 (IQR 57.5&#x2010;77.5; range 35&#x2010;92.5), indicating average usability. Individual item scores (<xref ref-type="fig" rid="figure3">Figure 3</xref>) showed that survey respondents generally found the STA easy to use and felt able to learn how to operate the tool quickly. No statistically significant difference was found between D-SUS scores and attitude toward technology (<italic>P</italic>=.11) and D-SUS scores and years of experience (<italic>P</italic>=.36).</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Overview of Digital System Usability Scale scores per item. STA: Stroke Triage App.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e105987_fig03.png"/></fig></sec><sec id="s3-2-4"><title>Theme 3: Adoption Attitudes</title><p>Survey respondents reported generally low levels of fear when using the STA: 33 (44%) respondents indicated no fear, while 19 (25%) respondents reported only minor concerns. In contrast, 12 respondents were neutral (16%), and 1 (1%) reported to be very worried. Interviewees similarly described a high level of trust in the STA. They explained that confidence in the tool increased with repeated use, particularly when its recommendations aligned with their own clinical judgment, which strengthened their understanding of the STA&#x2019;s predictions. Interviewees also noted that the scientific foundation of the STA and the involvement of the research team further contributed to their trust.</p><p>However, interviewees reported that limited understanding of the rationale and the contextual factors underlying the STA&#x2019;s recommendations sometimes led to uncertainty and frustration, particularly when the advice conflicted with their intuitive clinical judgment, occasionally resulting in reduced confidence and decreased use. They indicated that consultation with the research team and clarification of the advice generally helped to restore their confidence.</p><disp-quote><p>You also get answers very quickly when you ask questions, which makes you notice, even on a shift, that the study group is involved and that your concerns are heard. For example, if a case didn&#x2019;t go perfectly with another hospital, you can find out exactly what happened and where things went wrong.</p><attrib>P8</attrib></disp-quote><p>At the same time, interviewees emphasized that the STA was still often associated with a research context, leading some respondents to perceive it as optional rather than as part of routine care. More experienced users sometimes viewed the STA as an additional step rather than a clear benefit, making them less likely to use the app when an LVO was clinically apparent or when they considered their own clinical judgment sufficient. In contrast, others reported being more inclined to use the STA when they suspected an LVO, as it enabled direct bypass to an intervention center without the need for further discussion during handover.</p><p>Overall, interviewees regarded the STA as a supportive tool that enhanced, rather than replaced, their clinical decision-making.</p></sec><sec id="s3-2-5"><title>Theme 4: Actual Usage</title><p>Dashboard data showed that the monthly number of STA triages ranged from 52 to 153, with a median of 120 (IQR 107&#x2010;131; <xref ref-type="fig" rid="figure4">Figure 4</xref>). Individual STA use ranged from 1 to 47 times, with a median of 7 (IQR 3&#x2010;13). The number of monthly unique users varied between 40 to 94, with a median of 81 (IQR 74&#x2010;83).</p><p>Most survey respondents reported having used the STA at the time of the survey (73/76, 96%), with a median duration of use of 12 months (IQR 10&#x2010;12). In terms of frequency, 30 (40%) respondents reported using the STA in more than 60% of eligible cases, whereas only 13 participants used it in less than 20% (n=13, 17%) of cases. Regarding completion, most paramedics indicated that they often (n=33, 43%) or always (n=27, 36%) completed all required triage steps. For the majority, STA use remained stable (n=43, 57%) or increased over time (n=11, 15%). To access the app in the field, paramedics were almost equally divided between the use of smartphones (n=35, 46%) and tablets (n=34, 45%)</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Overview of number of Stroke Triage App triages per month from January 2024 until end of survey collection in June 2025.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e105987_fig04.png"/></fig><p>Interviewees provided additional context to these usage patterns. They mentioned that they sometimes forgot to use the app in acute situations, primarily because it was not yet routine, patients were unstable, technical issues arose, or due to partial postponement of use. Additionally, for some paramedics it was initially unclear whether STA use was standard protocol or optional for research purposes.</p><disp-quote><p>I have to admit, it took me a while to use the app for the first time, I kept forgetting. For the first 10 thrombolysis cases, I didn&#x2019;t use it at all. It wasn&#x2019;t on my radar yet, and I went on autopilot straight to the nearest hospital. Afterwards I thought, &#x2018;Oh right, I should have filled it in,&#x2019; but by then it didn&#x2019;t really make sense because I was already there. Now it&#x2019;s part of my routine, but it took some time to get there.</p><attrib>P6</attrib></disp-quote><p>Interviewees mentioned that reminders from neurologists at the emergency department helped reinforce routine use of the STA. They described that use was more likely in lower-urgency situations, where there was sufficient time for decision-making.</p></sec><sec id="s3-2-6"><title>Theme 5: Assessment and Handover</title><p>Survey respondents reported mixed perceptions regarding the impact of the STA on their workflow: 23 (30%) respondents indicated that the STA improved their workflow, 2 (3%) reported a substantial improvement. In contrast, 36 (47%) respondents reported no impact, and 4 (5%) reported a worsened workflow. Interviewees generally described the STA as a small component within their broader tasks of responsibilities, which did not substantially alter their workflow. However, they noted that the STA increased their awareness of patient urgency, particularly in cases involving large neurological deficits, and supported the identification of LVOs. Interviewees further explained that the STA supported neurological assessment by providing a structured approach to clinical evaluation. Interviewees reported that the tool also facilitated communication with neurologists by streamlining handovers (eg, through clear reporting of RACE scores) and reducing the need for discussion, thereby minimizing time lost in the acute care phase. In addition, interviewees valued the clear overview of patients&#x2019; neurological status provided by the STA. Overall, interviewees felt that STA use contributed to improved patient outcomes and fewer interhospital transfers.</p><disp-quote><p>&#x2026; the fact that the app makes the decision for you by giving the advice, it really helps. You don&#x2019;t have to decide yourself if you&#x2019;re unsure, which makes it easier. Filling in the app gives you an immediate overview of the patient (especially since the RACE score can sometimes be tricky) and clearly shows where to go. I think that reduces a lot of uncertainty. In addition, the app helps with the neurological assessment itself, allowing you to hand over your findings more effectively to the neurologist.</p><attrib>P2</attrib></disp-quote></sec><sec id="s3-2-7"><title>Theme 6: Future Perspectives</title><p>Most survey respondents indicated that they were likely (26/76, 34%), or very likely (19/76, 25%) to use the STA in the future. No statistically significant effect was found between years of experience and the likelihood to use the STA in the future (<italic>P</italic>=.68), and attitude toward technology and the likelihood to use the STA in the future (<italic>P</italic>=.38). Interviewees emphasized that continued use would only be acceptable if the tool provided clear added clinical value and remained easy to use. Several interviewees suggested a more selective application of the STA, noting that its recommendations often aligned with their own clinical judgment, which made its added value difficult to assess. They also perceived the STA as less useful for patients with a low likelihood of stroke or in cases with an obvious LVO, where destination decisions were already clear. For example, when the nearest hospital was already an EVT-capable center, interviewees reported no added clinical value of the STA, except for clear communication during handover.</p><p>For future implementation, interviewees highlighted the importance of improved usability and workflow integration. Suggested improvements included minimizing the number of required actions, simplifying or eliminating login procedures, integrating the STA with the electronic ambulance ride form to avoid duplicate data entry, and implementing a feedback loop with hospital diagnoses to validate paramedics&#x2019; triage decisions. Finally, participants mentioned that enabling automatic transfer of information (eg, RACE scores) to hospitals would be recommended. Enhancing mobile compatibility was also recommended for ease of use.</p><disp-quote><p>It needs to be practical, easy to use, and genuinely add value. So, if your conclusion is that it does provide real benefits, the next step should be to make the app as accessible as possible. If the added value is limited, we should seriously reconsider whether it&#x2019;s worth continuing.</p><attrib>P1</attrib></disp-quote><p>In addition, interviewees expressed a clear preference for brief explanations underlying the STA&#x2019;s recommendations, which they felt would support understanding and legitimize decision-making, particularly when the advice diverged from their clinical intuition. They emphasized that sustained implementation would depend on consistent communication, clarifying that the STA is not optional, and maintaining realistic expectations regarding paramedics&#x2019; roles and responsibilities in acute stroke care.</p></sec></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This study aimed to investigate paramedics&#x2019; experiences with the implementation of the STA in real-world prehospital practice by evaluating the implementation process, the implementation outcomes, and its impact on clinical workflows, while considering contextual factors that may have influenced these dimensions. Despite the identified barriers in usability and clinical added value, the STA achieved substantial initial reach supported by a structured implementation strategy. However, the high self-reported acceptability in the survey did not automatically translate into consistent, routine integration into daily prehospital workflows. Instead, actual usage varied with practical and contextual factors and paramedics&#x2019; perceived added value. While the STA facilitated structured neurological assessments and enhanced communication during handovers, it simultaneously induced workflow friction for experienced users who viewed the app as an additional step in high-stakes environments.</p><p>Dashboard data indicated a decline in usage after an initial peak, reflecting the &#x201C;novelty fade&#x201D; phenomenon in digital health implementation [<xref ref-type="bibr" rid="ref27">27</xref>]. This suggests that initial engagement was driven more by novelty than by structural integration. Qualitative insights indicate that the low frequency of stroke cases during shifts formed a structural barrier, consistent with reports that fewer than 5% of ambulance rides involve suspected stroke cases [<xref ref-type="bibr" rid="ref28">28</xref>]. Literature on habit formation suggests that this lack of exposure limits paramedics from moving past the initial learning phase to an automated workflow integration before the novelty fades [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. Moreover, trust in clinical decision support systems is typically built through consistent positive reinforcement over time [<xref ref-type="bibr" rid="ref31">31</xref>]. In a low-frequency setting, a technical barrier or ambiguous clinical results may therefore carry disproportionate weight, undermining perceived reliability and long-term use [<xref ref-type="bibr" rid="ref31">31</xref>]. This aligns with comparable findings on the operational burden of screen-based tools in time-critical prehospital settings, where balancing digital support with the demands of acute care has similarly been identified as a barrier [<xref ref-type="bibr" rid="ref32">32</xref>]. This concern was further reinforced by the misconception that the STA was a temporary research tool, rather than standard care, creating a sense of perceived optionality, a known barrier to long-term adoption [<xref ref-type="bibr" rid="ref33">33</xref>]. Together, these factors point to a structural tension in acute-care digital health implementation, in which reinforcement needed to build trust and routine use is inherently difficult to achieve in a low-frequency clinical context.</p><p>The findings of this study reflect a common, yet complex trajectory in digital health implementation, where high levels of acceptability and perceived appropriateness do not automatically ensure long-term sustainability [<xref ref-type="bibr" rid="ref34">34</xref>]. However, the emergence of a core group of persistent users, the early adopters, indicates that the STA has reached a level of routinization for a subset of the population [<xref ref-type="bibr" rid="ref35">35</xref>]. Yet, the observed decline in usage suggests that the tipping point for the early majority has not yet been fully reached [<xref ref-type="bibr" rid="ref35">35</xref>], as members of this group may have been more sensitive to the structural barriers identified in this study. Our findings also point to a pattern of selective, strategic use across users, where the STA is reserved for cases of clinical uncertainty rather than applied universally. Rather than viewing this as a lack of adherence, this selective approach aligns with the concept of professional autonomy in high-stakes environments, where clinical decision-support tools are reserved for complex decision-making scenarios [<xref ref-type="bibr" rid="ref36">36</xref>]. However, this approach assumes that paramedics can accurately identify a case as &#x201C;unmistakable&#x201D; before deciding to bypass the STA. Such judgments may be less reliable in atypical presentations, where the STA is likely to provide the greatest added value. This tension is not unique to the STA: in the ParaNASPP study [<xref ref-type="bibr" rid="ref2">2</xref>], which evaluated a comparable prehospital stroke-recognition tool, paramedics similarly reported relying on their own clinical judgment when classic stroke symptoms were clearly present, while placing greater reliance on the tool in more ambiguous presentations.</p></sec><sec id="s4-2"><title>Practical Implications</title><p>To ensure long-term sustainability of the STA, several practical implications must be addressed. First, technical complexity should be minimized by embedding the STA directly within existing prehospital information systems, to eliminate repetitive login procedures and facilitate automatic data transfers to receiving hospitals. More broadly, this illustrates that decision-support tools are more likely to be sustained when they are embedded within existing clinical systems rather than operating as stand-alone apps. Second, the clinical relevance of the STA can be strengthened by establishing a feedback loop that provides paramedics with formal confirmation of hospital diagnoses, addressing the need for paramedics to validate both the app&#x2019;s recommendations and their own clinical triage decisions against actual outcomes in order to calibrate their trust in the tool. Increasing the transparency of the STA by providing the clinical rationale underlying its recommendations could help mitigate the &#x201C;black box&#x201D; effect, particularly when in situations where the app&#x2019;s advice differs from a paramedic&#x2019;s initial judgment. Lastly, given the low frequency of stroke cases per shift, sustained promotion of the tool remains essential. Future implementation efforts should explicitly frame the STA as a specialized resource for cases of diagnostic uncertainty rather than a replacement for professional judgment. This may be particularly important, as infrequent exposure to decision-support tools may limit opportunities for paramedics to develop a clear understanding of their intended role and limitations.</p></sec><sec id="s4-3"><title>Future Recommendations</title><p>Future research should prioritize longitudinal studies to evaluate the effectiveness of diverse feedback mechanisms, such as providing paramedics with real-time data on hospital diagnoses and more detailed insights into the underlying clinical rationale of the STA advice. Such feedback is essential to determine whether it enhances the perceived relative advantage and long-term adherence to the tool. Furthermore, since this study was primarily conducted in an urban setting with high hospital density, future research should explore whether the utility of the STA is more evident in rural areas, where longer transport times and fewer hospital options might lead to a larger impact on treatment times. Finally, further investigation into the receiving end of the acute stroke chain is needed to assess how neurologists perceive and use the STA data during the handover. Exploring potential changes in inter-professional dynamics and the perceived clinical authority of app-generated recommendations is needed for optimizing the integration of the STA into the broader acute care pathway.</p></sec><sec id="s4-4"><title>Strengths and Limitations</title><p>A key strength of this study is the evaluation of the STA within a real-world prehospital setting over an extended period of 1.5 years. Digital health interventions in prehospital care are frequently evaluated in testing or development settings rather than in routine clinical practice, leaving evidence on real-world implementation and sustained use relatively scarce [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref37">37</xref>]. The longitudinal approach in this study captured long-term usage patterns and perspectives, providing a nuanced insight into the sustainability of the implementation process. The credibility of the results is supported by the fact that 96% of survey respondents and all interview participants had actively used the STA, ensuring that the findings reflect actual clinical experience rather than hypothetical expectations. Furthermore, because the results of the primary clinical validation study were not yet available during data collection, the risk of participants altering their feedback based on the STA&#x2019;s proven clinical efficacy was minimized. Moreover, the study&#x2019;s grounding in multiple implementation science frameworks enabled comprehensive operationalization of both instruments. For instance, the UTAUT provided measurable items, while CFIR&#x2019;s implementation process domain structured the qualitative exploration of training, communication, and support. Ultimately, this study addresses the current lack in prehospital implementation research by providing a detailed end-user perspective on prehospital implementation through a comprehensive mixed methods approach [<xref ref-type="bibr" rid="ref38">38</xref>].</p><p>Several limitations should be considered when interpreting our findings. First, despite efforts to include a diverse range of perspectives, selection bias may have occurred, potentially overrepresenting paramedics with a positive attitude toward the STA. A consequence of the high participation rate among active users is the potential omission of critical insights from nonusers, whose reasons for nonuse remain largely unexplored. Although the survey was actively promoted with an emphasis that feedback from all viewpoints was essential, no responses were received from this subgroup, leaving the dedicated nonuser section of the survey entirely uncompleted. Similarly, while snowball sampling was used to recruit critical users for the qualitative interviews, this subgroup remained underrepresented. Consequently, our understanding of the barriers faced by those who did not use the STA remains limited. Second, the involvement of some researchers in both this study and the primary clinical validation trial could have introduced a risk of confirmation bias, potentially leading to an overinterpretation of positive findings. To mitigate this risk, researchers who were independent of the main clinical trial were involved in conducting interviews and performing the thematic analysis. This approach brought an outsider perspective to the data, enhancing the reflexivity and interpretive rigor in the analysis. Finally, the urban geographical context of the current study regions may limit the generalizability of our results to more rural settings. In areas where the intervention center was the closest hospital, the perceived urgency of the clinical decision problem was likely reduced. This proximity may have led to lower STA compliance compared to regions with longer transport times and more complex triage choices, where the relative advantage of a decision-support tool might be more apparent.</p></sec><sec id="s4-5"><title>Conclusion</title><p>This study demonstrates that the STA achieved substantial reach and initial adoption within a prehospital setting, facilitating structured neurological assessments and establishing a shared clinical language between paramedics and neurologists. However, the widespread acceptance did not consistently translate into routine, sustained integration into daily practice. Usage remained selective, influenced by paramedics&#x2019; professional judgment in situations of clinical uncertainty rather than applied universally. Beyond its immediate findings, this study contributes to the STA&#x2019;s ongoing development and to broader efforts toward sustainable digital health implementation in prehospital emergency care. Ultimately, successful implementation depends as much on addressing organizational and human factors as on technical performance.</p></sec></sec></body><back><ack><p>We gratefully acknowledge study participants who took their valuable time to participate in this study. The authors would like to thank Jasper van Duijvenbooden, Ines Beekers, Nyika Kruyt, Linda Dusseljee-Peute, and Martin Smeekes from the PRESTO-2 Advisory Board, and Diederik Dippel, Kirsten Dorresteijn, Annemarie Wijnhoud, Jim IJzermans, Patrick van der Geest, and Merel Willeboer from the PRESTO-2 Executive Committee for their contributions during the developmental phase of this study. Furthermore, the authors would like to acknowledge Daniel Bos, Sandra Cornelissen, Govert van der Gun, Lisa Hoogendam, Peter van Hulst, Xi Li, Hester Lingsma, Frank te Nijenhuis, Danny Ruijters, Ruud Selles, Ruisheng Su, and Theo van Walsum from the Innovation Center for Artificial Intelligence (ICAI) Stroke Lab Study Group for their contribution to the collaborative research environment. Additionally, the authors would like to thank Kees Ahaus from Erasmus University Rotterdam for his valuable feedback on the manuscript.</p></ack><notes><sec><title>Generative AI Use</title><p>Generative AI (GenAI) tools were used in the writing process. According to the GAIDeT taxonomy (2025), the following tasks were delegated to GenAI tools under full human supervision: proofreading and editing and improving the academic writing style of the manuscript. These tools were applied exclusively to text already drafted by the authors for the purpose of language refinement and stylistic improvement. No research data, participant information, or unpublished results were entered into these tools at any stage. The GenAI tools used were Gemini and Microsoft Copilot. Responsibility for the content, accuracy, and integrity of the final manuscript lies entirely with the authors. GenAI tools are not listed as authors and do not bear responsibility for the final outcomes.</p></sec><sec><title>Funding</title><p>This work was funded by the Dutch Research Council (NWO), the Dutch Heart Foundation, Philips Medical Systems Nederland B.V., and the Dutch Ministry of Economic Affairs and Climate Policy (EZK) under the project ROBUST: Trustworthy AI-based Systems for Sustainable Growth (project number KICH3.LTP.20.006), as part of the LTP KIC 2020&#x2010;2023 program. The funders played no role in the study design, data collection, data analysis, data interpretation, formulation of the conclusions, or manuscript preparation.</p></sec><sec><title>Data Availability</title><p>The datasets generated and analyzed during the current study are not publicly available due to the qualitative nature of the interview data and the potential for deductive re-identification of participants within the specific prehospital setting. However, anonymized quantitative survey data, pseudonymized transcripts, and the coding framework are available from the corresponding author on reasonable request.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: FK (lead), EH (equal), MS (supporting), NR (supporting), EV (supporting), SS (supporting), BR (supporting)</p><p>Formal analysis: FK (lead), EH (equal), MS (supporting), NR (supporting), RvdW (supporting), EV (supporting), SS (supporting), BR (supporting)</p><p>Investigation: FK (lead), EH (equal)</p><p>Methodology: FK (lead), EH (equal), MS (supporting), NR (supporting), EV (supporting), SS (supporting), BR (supporting)</p><p>Project administration: FK (lead), EH (equal)</p><p>Supervision: MS, EV, SS, BR</p><p>Writing&#x2013;original draft: FK (lead), EH (equal)</p><p>Writing&#x2013;review &#x0026; editing: FK (lead), EH (equal), MS (supporting), NR (supporting), RvdW (supporting), EV (supporting), HK (supporting), SS (supporting), BR (supporting)</p><p>FK and EH contributed equally and share first authorship.</p><p>SS and BR contributed equally as senior authors and share last authorship.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">CE</term><def><p>Conformit&#x00E9; Europ&#x00E9;enne</p></def></def-item><def-item><term id="abb2">CFIR</term><def><p>Consolidated Framework for Implementation Research</p></def></def-item><def-item><term id="abb3">D-SUS</term><def><p>Digital System Usability Scale</p></def></def-item><def-item><term id="abb4">EMS</term><def><p>emergency medical service</p></def></def-item><def-item><term id="abb5">EUDAMED</term><def><p>The European Database on Medical Devices</p></def></def-item><def-item><term id="abb6">EVT</term><def><p>endovascular treatment</p></def></def-item><def-item><term id="abb7">GRAMMS</term><def><p>Good Reporting of a Mixed Methods Study</p></def></def-item><def-item><term id="abb8">IVT</term><def><p>intravenous thrombolysis</p></def></def-item><def-item><term id="abb9">LVO</term><def><p>large vessel occlusion</p></def></def-item><def-item><term id="abb10">MDR</term><def><p>medical device regulation</p></def></def-item><def-item><term id="abb11">NASSS</term><def><p>Non-adoption, Abandonment, Scale-up, Spread, Sustainability Framework</p></def></def-item><def-item><term id="abb12">PRESTO-2</term><def><p>Prehospital Triage of Patients With a Suspected Acute Stroke</p></def></def-item><def-item><term id="abb13">RACE</term><def><p>Rapid Arterial Occlusion Evaluation</p></def></def-item><def-item><term id="abb14">STA</term><def><p>Stroke Triage App</p></def></def-item><def-item><term id="abb15">UDI-DI</term><def><p>unique device identification-device identifier</p></def></def-item><def-item><term id="abb16">UTAUT</term><def><p>Unified Theory of Acceptance and Use of Technology</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pyper</surname><given-names>E</given-names> </name><name name-style="western"><surname>McKeown</surname><given-names>S</given-names> </name><name name-style="western"><surname>Hartmann-Boyce</surname><given-names>J</given-names> </name><name name-style="western"><surname>Powell</surname><given-names>J</given-names> </name></person-group><article-title>Digital health technology for real-world clinical outcome measurement using patient-generated data: systematic scoping review</article-title><source>J Med Internet Res</source><year>2023</year><month>10</month><day>11</day><volume>25</volume><fpage>e46992</fpage><pub-id pub-id-type="doi">10.2196/46992</pub-id><pub-id pub-id-type="medline">37819698</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>Guterud</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hardeland</surname><given-names>C</given-names> </name><name name-style="western"><surname>Bugge</surname><given-names>HF</given-names> </name><name name-style="western"><surname>Sandset</surname><given-names>EC</given-names> </name><name name-style="western"><surname>Svendsen</surname><given-names>EJ</given-names> </name><name name-style="western"><surname>Hov</surname><given-names>MR</given-names> </name></person-group><article-title>Experiences from a cluster-randomized trial (ParaNASPP) exploring triage and diagnostic accuracy in paramedic-suspected stroke: a qualitative interview study</article-title><source>Eur J Neurol</source><year>2024</year><month>05</month><volume>31</volume><issue>5</issue><fpage>e16252</fpage><pub-id pub-id-type="doi">10.1111/ene.16252</pub-id><pub-id pub-id-type="medline">38404142</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>Greenhalgh</surname><given-names>T</given-names> </name><name name-style="western"><surname>Wherton</surname><given-names>J</given-names> </name><name name-style="western"><surname>Papoutsi</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Beyond adoption: a new framework for theorizing and evaluating nonadoption, abandonment, and challenges to the scale-up, spread, and sustainability of health and care technologies</article-title><source>J Med Internet Res</source><year>2017</year><month>11</month><day>1</day><volume>19</volume><issue>11</issue><fpage>e367</fpage><pub-id pub-id-type="doi">10.2196/jmir.8775</pub-id><pub-id pub-id-type="medline">29092808</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>AT</given-names> </name><name name-style="western"><surname>Ramasamy</surname><given-names>RK</given-names> </name><name name-style="western"><surname>Subbarao</surname><given-names>A</given-names> </name></person-group><article-title>Barriers to and facilitators of technology adoption in emergency departments: a comprehensive review</article-title><source>Int J Environ Res Public Health</source><year>2025</year><month>03</month><day>23</day><volume>22</volume><issue>4</issue><fpage>479</fpage><pub-id pub-id-type="doi">10.3390/ijerph22040479</pub-id><pub-id pub-id-type="medline">40283708</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sittig</surname><given-names>DF</given-names> </name><name name-style="western"><surname>Singh</surname><given-names>H</given-names> </name></person-group><article-title>A new sociotechnical model for studying health information technology in complex adaptive healthcare systems</article-title><source>Qual Saf Health Care</source><year>2010</year><month>10</month><volume>19 Suppl 3</volume><issue>Suppl 3</issue><fpage>i68</fpage><lpage>74</lpage><pub-id pub-id-type="doi">10.1136/qshc.2010.042085</pub-id><pub-id pub-id-type="medline">20959322</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>Zhang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Bai</surname><given-names>E</given-names> </name><name name-style="western"><surname>Xu</surname><given-names>Y</given-names> </name><etal/></person-group><article-title>A smart glass telemedicine application for prehospital communication: user-centered design study</article-title><source>J Med Internet Res</source><year>2024</year><month>11</month><day>29</day><volume>26</volume><fpage>e53157</fpage><pub-id pub-id-type="doi">10.2196/53157</pub-id><pub-id pub-id-type="medline">39612486</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>Kelly</surname><given-names>CJ</given-names> </name><name name-style="western"><surname>Karthikesalingam</surname><given-names>A</given-names> </name><name name-style="western"><surname>Suleyman</surname><given-names>M</given-names> </name><name name-style="western"><surname>Corrado</surname><given-names>G</given-names> </name><name name-style="western"><surname>King</surname><given-names>D</given-names> </name></person-group><article-title>Key challenges for delivering clinical impact with artificial intelligence</article-title><source>BMC Med</source><year>2019</year><month>10</month><day>29</day><volume>17</volume><issue>1</issue><fpage>195</fpage><pub-id pub-id-type="doi">10.1186/s12916-019-1426-2</pub-id><pub-id pub-id-type="medline">31665002</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="report"><person-group person-group-type="author"><collab>Richtlijnendatabase</collab></person-group><article-title>Herseninfarct en hersenbloeding</article-title><year>2024</year><access-date>2026-10-26</access-date><publisher-name>Federatie Medisch Specialisten</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://richtlijnendatabase.nl/richtlijn/herseninfarct_en_hersenbloeding/acute_opvang_bij_rl_herseninfarct_en_hersenboeding.html">https://richtlijnendatabase.nl/richtlijn/herseninfarct_en_hersenbloeding/acute_opvang_bij_rl_herseninfarct_en_hersenboeding.html</ext-link></comment></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>Jadhav</surname><given-names>AP</given-names> </name><name name-style="western"><surname>Desai</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Jovin</surname><given-names>TG</given-names> </name></person-group><article-title>Indications for mechanical thrombectomy for acute ischemic stroke: current guidelines and beyond</article-title><source>Neurology</source><year>2021</year><month>11</month><day>16</day><volume>97</volume><issue>20 Suppl 2</issue><fpage>S126</fpage><lpage>S136</lpage><pub-id pub-id-type="doi">10.1212/WNL.0000000000012801</pub-id><pub-id pub-id-type="medline">34785611</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Saver</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Goyal</surname><given-names>M</given-names> </name><name name-style="western"><surname>van der Lugt</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Time to treatment with endovascular thrombectomy and outcomes from ischemic stroke: a meta-analysis</article-title><source>JAMA</source><year>2016</year><month>09</month><day>27</day><volume>316</volume><issue>12</issue><fpage>1279</fpage><lpage>1288</lpage><pub-id pub-id-type="doi">10.1001/jama.2016.13647</pub-id><pub-id pub-id-type="medline">27673305</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Duvekot</surname><given-names>MHC</given-names> </name><name name-style="western"><surname>Garcia</surname><given-names>BL</given-names> </name><name name-style="western"><surname>Dekker</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Prehospital stroke triage: a modeling study on the impact of triage tools in different regions</article-title><source>Prehosp Emerg Care</source><year>2023</year><volume>27</volume><issue>5</issue><fpage>630</fpage><lpage>638</lpage><pub-id pub-id-type="doi">10.1080/10903127.2023.2215859</pub-id><pub-id pub-id-type="medline">37219931</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>Duvekot</surname><given-names>MHC</given-names> </name><name name-style="western"><surname>Venema</surname><given-names>E</given-names> </name><name name-style="western"><surname>Rozeman</surname><given-names>AD</given-names> </name><etal/></person-group><article-title>Comparison of eight prehospital stroke scales to detect intracranial large-vessel occlusion in suspected stroke (PRESTO): a prospective observational study</article-title><source>Lancet Neurol</source><year>2021</year><month>03</month><volume>20</volume><issue>3</issue><fpage>213</fpage><lpage>221</lpage><pub-id pub-id-type="doi">10.1016/S1474-4422(20)30439-7</pub-id><pub-id pub-id-type="medline">33422191</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>Venema</surname><given-names>E</given-names> </name><name name-style="western"><surname>Lingsma</surname><given-names>HF</given-names> </name><name name-style="western"><surname>Chalos</surname><given-names>V</given-names> </name><etal/></person-group><article-title>Personalized prehospital triage in acute ischemic stroke</article-title><source>Stroke</source><year>2019</year><month>02</month><volume>50</volume><issue>2</issue><fpage>313</fpage><lpage>320</lpage><pub-id pub-id-type="doi">10.1161/STROKEAHA.118.022562</pub-id><pub-id pub-id-type="medline">30661502</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="report"><article-title>Regionale kerncijfers Nederland</article-title><year>2025</year><access-date>2026-10-26</access-date><publisher-name>CBS</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.cbs.nl/nl-nl/cijfers/detail/70072ned">https://www.cbs.nl/nl-nl/cijfers/detail/70072ned</ext-link></comment></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>van de Wijdeven</surname><given-names>RM</given-names> </name><name name-style="western"><surname>de Ruijter</surname><given-names>NS</given-names> </name><name name-style="western"><surname>Kremers</surname><given-names>FCC</given-names> </name><etal/></person-group><article-title>Prehospital triage of patients with suspected acute stroke (PRESTO-2): protocol for a controlled before-and-after intervention trial</article-title><source>Eur Stroke J</source><year>2026</year><month>09</month><day>5</day><volume>11</volume><issue>9</issue><fpage>aakag106</fpage><pub-id pub-id-type="doi">10.1093/esj/aakag106</pub-id><pub-id pub-id-type="medline">42703715</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>Ivankova</surname><given-names>NV</given-names> </name><name name-style="western"><surname>Creswell</surname><given-names>JW</given-names> </name><name name-style="western"><surname>Stick</surname><given-names>SL</given-names> </name></person-group><article-title>Using mixed-methods sequential explanatory design: from theory to practice</article-title><source>Field methods</source><year>2006</year><month>02</month><volume>18</volume><issue>1</issue><fpage>3</fpage><lpage>20</lpage><pub-id pub-id-type="doi">10.1177/1525822X05282260</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Damschroder</surname><given-names>LJ</given-names> </name><name name-style="western"><surname>Aron</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Keith</surname><given-names>RE</given-names> </name><name name-style="western"><surname>Kirsh</surname><given-names>SR</given-names> </name><name name-style="western"><surname>Alexander</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Lowery</surname><given-names>JC</given-names> </name></person-group><article-title>Fostering implementation of health services research findings into practice: A consolidated framework for advancing implementation science</article-title><source>Implement Sci</source><year>2009</year><month>08</month><day>7</day><volume>4</volume><fpage>50</fpage><pub-id pub-id-type="doi">10.1186/1748-5908-4-50</pub-id><pub-id pub-id-type="medline">19664226</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>Venkatesh</surname><given-names>V</given-names> </name><name name-style="western"><surname>Morris</surname><given-names>MG</given-names> </name><name name-style="western"><surname>Davis</surname><given-names>GB</given-names> </name><name name-style="western"><surname>Davis</surname><given-names>FD</given-names> </name></person-group><article-title>User acceptance of information technology: toward a unified view</article-title><source>Manag Inf Syst Q</source><year>2003</year><month>09</month><day>1</day><volume>27</volume><issue>3</issue><fpage>425</fpage><lpage>478</lpage><pub-id pub-id-type="doi">10.2307/30036540</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Cathain</surname><given-names>A</given-names> </name><name name-style="western"><surname>Murphy</surname><given-names>E</given-names> </name><name name-style="western"><surname>Nicholl</surname><given-names>J</given-names> </name></person-group><article-title>The quality of mixed methods studies in health services research</article-title><source>J Health Serv Res Policy</source><year>2008</year><month>04</month><volume>13</volume><issue>2</issue><fpage>92</fpage><lpage>98</lpage><pub-id pub-id-type="doi">10.1258/jhsrp.2007.007074</pub-id><pub-id pub-id-type="medline">18416914</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="web"><article-title>A collaboration between the erasmus university of rotterdam, erasmus MC and philips</article-title><source>ICAI Innovation center for artfiicial intelligence</source><access-date>2026-10-08</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://icai.ai/lab/icai-stroke-lab/">https://icai.ai/lab/icai-stroke-lab/</ext-link></comment></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><article-title>The leading experience management software, version XM</article-title><source>Qualtrics</source><access-date>2026-10-16</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.qualtrics.com">https://www.qualtrics.com</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ensink</surname><given-names>CJ</given-names> </name><name name-style="western"><surname>Keijsers</surname><given-names>NLW</given-names> </name><name name-style="western"><surname>Groen</surname><given-names>BE</given-names> </name></person-group><article-title>Translation and validation of the system usability scale to a Dutch version: D-SUS</article-title><source>Disabil Rehabil</source><year>2024</year><month>01</month><volume>46</volume><issue>2</issue><fpage>395</fpage><lpage>400</lpage><pub-id pub-id-type="doi">10.1080/09638288.2022.2160837</pub-id><pub-id pub-id-type="medline">36573399</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Biernacki</surname><given-names>P</given-names> </name><name name-style="western"><surname>Waldorf</surname><given-names>D</given-names> </name></person-group><article-title>Snowball sampling: problems and techniques of chain referral sampling</article-title><source>Sociol Methods Res</source><year>1981</year><month>11</month><volume>10</volume><issue>2</issue><fpage>141</fpage><lpage>163</lpage><pub-id pub-id-type="doi">10.1177/004912418101000205</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="web"><article-title>The trusted IDE for r data scientists, now with AI that knows your data</article-title><source>posit</source><access-date>2026-10-08</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://posit.co/products/open-source/rstudio">https://posit.co/products/open-source/rstudio</ext-link></comment></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Braun</surname><given-names>V</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>V</given-names> </name></person-group><article-title>Using thematic analysis in psychology</article-title><source>Qual Res Psychol</source><year>2006</year><month>01</month><volume>3</volume><issue>2</issue><fpage>77</fpage><lpage>101</lpage><pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="web"><article-title>Master your research projects with the power of AI</article-title><source>ATLAS.ti</source><access-date>2026-10-08</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://atlasti.com/">https://atlasti.com/</ext-link></comment></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Eysenbach</surname><given-names>G</given-names> </name></person-group><article-title>The law of attrition</article-title><source>J Med Internet Res</source><year>2005</year><month>03</month><day>31</day><volume>7</volume><issue>1</issue><fpage>e11</fpage><pub-id pub-id-type="doi">10.2196/jmir.7.1.e11</pub-id><pub-id pub-id-type="medline">15829473</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="web"><article-title>Sectorkompas ambulancezorg tabellen en grafieken 2021</article-title><source>Ambulancezorg Nederland</source><year>2022</year><access-date>2026-10-26</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.ambulancezorg.nl/static/upload/raw/baf8e8e5-7431-41b7-820f-0790133065dc/221114+tabellenboek+2021+totaal.pdf">https://www.ambulancezorg.nl/static/upload/raw/baf8e8e5-7431-41b7-820f-0790133065dc/221114+tabellenboek+2021+totaal.pdf</ext-link></comment></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Venkatesh</surname><given-names>V</given-names> </name><name name-style="western"><surname>Morris</surname><given-names>MG</given-names> </name><name name-style="western"><surname>Davis</surname><given-names>GB</given-names> </name><name name-style="western"><surname>Davis</surname><given-names>FD</given-names> </name></person-group><article-title>User acceptance of information technology: toward a unified view</article-title><source>MIS Q</source><year>2003</year><month>09</month><day>1</day><volume>27</volume><issue>3</issue><fpage>425</fpage><lpage>478</lpage><pub-id pub-id-type="doi">10.2307/30036540</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>May</surname><given-names>C</given-names> </name><name name-style="western"><surname>Finch</surname><given-names>T</given-names> </name></person-group><article-title>Implementing, embedding, and integrating practices: an outline of normalization process theory</article-title><source>Sociology</source><year>2009</year><month>06</month><volume>43</volume><issue>3</issue><fpage>535</fpage><lpage>554</lpage><pub-id pub-id-type="doi">10.1177/0038038509103208</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hoff</surname><given-names>KA</given-names> </name><name name-style="western"><surname>Bashir</surname><given-names>M</given-names> </name></person-group><article-title>Trust in automation: integrating empirical evidence on factors that influence trust</article-title><source>Hum Factors</source><year>2015</year><month>05</month><volume>57</volume><issue>3</issue><fpage>407</fpage><lpage>434</lpage><pub-id pub-id-type="doi">10.1177/0018720814547570</pub-id><pub-id pub-id-type="medline">25875432</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>Andersson Hagiwara</surname><given-names>M</given-names> </name><name name-style="western"><surname>Lundberg</surname><given-names>L</given-names> </name><name name-style="western"><surname>Sj&#x00F6;qvist</surname><given-names>BA</given-names> </name><name name-style="western"><surname>Maurin S&#x00F6;derholm</surname><given-names>H</given-names> </name></person-group><article-title>The effects of integrated IT support on the prehospital stroke process: results from a realistic experiment</article-title><source>J Healthc Inform Res</source><year>2019</year><month>09</month><volume>3</volume><issue>3</issue><fpage>300</fpage><lpage>328</lpage><pub-id pub-id-type="doi">10.1007/s41666-019-00053-4</pub-id><pub-id pub-id-type="medline">35415430</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>Murray</surname><given-names>E</given-names> </name><name name-style="western"><surname>Treweek</surname><given-names>S</given-names> </name><name name-style="western"><surname>Pope</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Normalisation process theory: a framework for developing, evaluating and implementing complex interventions</article-title><source>BMC Med</source><year>2010</year><month>10</month><day>20</day><volume>8</volume><fpage>63</fpage><pub-id pub-id-type="doi">10.1186/1741-7015-8-63</pub-id><pub-id pub-id-type="medline">20961442</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Proctor</surname><given-names>E</given-names> </name><name name-style="western"><surname>Silmere</surname><given-names>H</given-names> </name><name name-style="western"><surname>Raghavan</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Outcomes for implementation research: conceptual distinctions, measurement challenges, and research agenda</article-title><source>Adm Policy Ment Health</source><year>2011</year><month>03</month><volume>38</volume><issue>2</issue><fpage>65</fpage><lpage>76</lpage><pub-id pub-id-type="doi">10.1007/s10488-010-0319-7</pub-id><pub-id pub-id-type="medline">20957426</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Turner</surname><given-names>RJ</given-names> </name></person-group><article-title>Diffusion of innovations</article-title><source>J Minim Invasive Gynecol</source><year>2007</year><volume>14</volume><issue>6</issue><fpage>776</fpage><pub-id pub-id-type="doi">10.1016/j.jmig.2007.07.001</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shortliffe</surname><given-names>EH</given-names> </name><name name-style="western"><surname>Sep&#x00FA;lveda</surname><given-names>MJ</given-names> </name></person-group><article-title>Clinical decision support in the era of artificial intelligence</article-title><source>JAMA</source><year>2018</year><month>12</month><day>4</day><volume>320</volume><issue>21</issue><fpage>2199</fpage><lpage>2200</lpage><pub-id pub-id-type="doi">10.1001/jama.2018.17163</pub-id><pub-id pub-id-type="medline">30398550</pub-id></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wu</surname><given-names>TC</given-names> </name><name name-style="western"><surname>Nguyen</surname><given-names>C</given-names> </name><name name-style="western"><surname>Ankrom</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Prehospital utility of rapid stroke evaluation using in-ambulance telemedicine: a pilot feasibility study</article-title><source>Stroke</source><year>2014</year><month>08</month><volume>45</volume><issue>8</issue><fpage>2342</fpage><lpage>2347</lpage><pub-id pub-id-type="doi">10.1161/STROKEAHA.114.005193</pub-id><pub-id pub-id-type="medline">24938842</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Brazil</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ozkaynak</surname><given-names>M</given-names> </name><name name-style="western"><surname>Desanto</surname><given-names>K</given-names> </name></person-group><article-title>Evaluative research of technologies for prehospital communication and coordination: a systematic review</article-title><source>J Med Syst</source><year>2020</year><month>04</month><day>3</day><volume>44</volume><issue>5</issue><fpage>100</fpage><pub-id pub-id-type="doi">10.1007/s10916-020-01556-z</pub-id><pub-id pub-id-type="medline">32246206</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Theoretical approaches informing survey and interview guide design.</p><media xlink:href="jmir_v28i1e105987_app1.docx" xlink:title="DOCX File, 35 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Semisemistructured interview guide on experiences with the STA, including main questions and probes (English version).</p><media xlink:href="jmir_v28i1e105987_app2.docx" xlink:title="DOCX File, 45 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Overview of survey constructs, item characteristics, scoring, and psychometric properties.</p><media xlink:href="jmir_v28i1e105987_app3.docx" xlink:title="DOCX File, 18 KB"/></supplementary-material><supplementary-material id="app4"><label>Multimedia Appendix 4</label><p>Semistructured survey on experiences with Stroke Triage App, including all questions and response options (English version).</p><media xlink:href="jmir_v28i1e105987_app4.docx" xlink:title="DOCX File, 45 KB"/></supplementary-material><supplementary-material id="app5"><label>Checklist 1</label><p>Good Reporting of A Mixed Methods Study (GRAMMS) checklist.</p><media xlink:href="jmir_v28i1e105987_app5.docx" xlink:title="DOCX File, 20 KB"/></supplementary-material></app-group></back></article>