<?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">JMIR Res Protoc</journal-id><journal-id journal-id-type="publisher-id">ResProt</journal-id><journal-id journal-id-type="index">5</journal-id><journal-title>JMIR Research Protocols</journal-title><abbrev-journal-title>JMIR Res Protoc</abbrev-journal-title><issn pub-type="epub">1929-0748</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">v15i1e93754</article-id><article-id pub-id-type="doi">10.2196/93754</article-id><article-categories><subj-group subj-group-type="heading"><subject>Protocol</subject></subj-group></article-categories><title-group><article-title>Technology Platform (Peer PLUS) Supporting the Work of Peer Recovery Coaches and the Communication Needs of Individuals in Recovery From Substance Use Disorder: Protocol for an R21 Development and Usability Trial</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Coupe</surname><given-names>Amanda</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Pater</surname><given-names>Jessica</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Pfafman</surname><given-names>Rachel</given-names></name><degrees>MBA, MPH</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Cornet</surname><given-names>Victor P</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Andrews</surname><given-names>Elisabeth</given-names></name><degrees>MSW</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Flanagan</surname><given-names>Mindy</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Albright</surname><given-names>Dana</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Balasani</surname><given-names>Abhinay</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Becker</surname><given-names>Christopher</given-names></name><degrees>BS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Parise</surname><given-names>Brian</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hess</surname><given-names>Erik</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Toscos</surname><given-names>Tammy</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib></contrib-group><aff id="aff1"><institution>Parkview Mirro Center for Research and Innovation</institution><addr-line>10622 Parkview Plaza Drive</addr-line><addr-line>Fort Wayne</addr-line><addr-line>IN</addr-line><country>United States</country></aff><aff id="aff2"><institution>Parkview Behavioral Health Institute, Parkview Health</institution><addr-line>Fort Wayne</addr-line><addr-line>IN</addr-line><country>United States</country></aff><aff id="aff3"><institution>Emergency Medicine, Vanderbilt University Medical Center</institution><addr-line>Nashville</addr-line><addr-line>TN</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Schwartz</surname><given-names>Amy</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Szlyk</surname><given-names>Hannah</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Amanda Coupe, MA, Parkview Mirro Center for Research and Innovation, 10622 Parkview Plaza Drive, Fort Wayne, IN, 46845, United States, 1 260-266-5586; <email>amanda.coupe@parkview.com</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>28</day><month>7</month><year>2026</year></pub-date><volume>15</volume><elocation-id>e93754</elocation-id><history><date date-type="received"><day>19</day><month>02</month><year>2026</year></date><date date-type="rev-recd"><day>10</day><month>06</month><year>2026</year></date><date date-type="accepted"><day>15</day><month>06</month><year>2026</year></date></history><copyright-statement>&#x00A9; Amanda Coupe, Jessica Pater, Rachel Pfafman, Victor P Cornet, Elisabeth Andrews, Mindy Flanagan, Dana Albright, Abhinay Balasani, Christopher Becker, Brian Parise, Erik Hess, Tammy Toscos. Originally published in JMIR Research Protocols (<ext-link ext-link-type="uri" xlink:href="https://www.researchprotocols.org">https://www.researchprotocols.org</ext-link>), 28.7.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 JMIR Research Protocols, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.researchprotocols.org">https://www.researchprotocols.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.researchprotocols.org/2026/1/e93754"/><abstract><sec><title>Background</title><p>Substance use disorder (SUD) represents a significant public health concern in the United States. SUD recovery is complex and individualized, and support provided by peer recovery coaches (PRCs) can improve outcomes. The PRC-client relationship requires bidirectional mediated communication that is often informal but should be trackable, efficient, and aligned with health care privacy and security regulations. Current workflows and available apps do not meet these needs, illustrating the opportunity for client-centered technology tools. We have developed Peer PLUS (People Leveraging Urgent Support; Parkview Health System, Inc), a HIPAA (Health Insurance Portability and Accountability Act)-compliant mobile app and client management system, to address this need; however, the platform has not yet been tested in a clinical setting.</p></sec><sec><title>Objective</title><p>We describe the protocol for the evaluation of our digital health platform to identify its perceived usability, potential sustained use, and potential impact on treatment-related outcomes, as well as to assess its feasibility for a future randomized controlled trial and develop an implementation tool kit to facilitate use by other organizations.</p></sec><sec sec-type="methods"><title>Methods</title><p>Our evaluation leveraged user-centered design (UCD) and implementation science frameworks (Reach, Effectiveness, Adoption, Implementation, and Maintenance [RE-AIM]). We conducted prelaunch ethnographic observations of 3 PRCs&#x2019; workflows for an understanding of user needs. During subsequent in-the-wild testing, PRC-client dyads will use the platform for asynchronous communication within their standard support relationship. We will deploy periodic electronic surveys, including the System Usability Scale (SUS) to assess perceived usability during beta testing, and additional validated measures assessing specific treatment-related outcomes (ie, recovery, quality of care, and therapeutic alliance) during pilot testing. App use log data will be leveraged to assess the likelihood of sustained use. After each test, UCD-focused stakeholder engagements will further elucidate opportunities for platform refinement and implementation tool kit development. Feasibility targets include SUS scores of 68 or more, 25% client eligibility and enrollment rate, and 20% increased contacts between PRCs and enrolled vs nonenrolled clients.</p></sec><sec sec-type="results"><title>Results</title><p>This project was funded in March 2023. Beta test recruitment began in January 2024, with 3 tests completed by November 2024 (3 PRCs and 7 clients). Pilot recruitment began in August 2025. Pilot testing and analyses will continue in 2026. If feasibility metrics are met, the platform will be tested in a later study phase that will include a randomized controlled trial and a second pilot trial to test implementation at a different organization.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Our evaluation assesses whether Peer PLUS is an efficient and usable tool that meets identified communication and documentation needs of clients and PRCs while fostering increased connection, which could suggest the likelihood of sustained use and improved treatment outcomes. This project contributes to the UCD and implementation science fields by demonstrating the importance of merging these frameworks during the design and evaluation of novel digital health solutions.</p></sec><sec sec-type="registered-report"><title>International Registered Report Identifier (IRRID)</title><p>DERR1-10.2196/93754</p></sec></abstract><kwd-group><kwd>user-centered design</kwd><kwd>implementation science</kwd><kwd>peer recovery support specialist</kwd><kwd>mobile app</kwd><kwd>human-computer interaction</kwd><kwd>mobile computing</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Background</title><p>Substance use disorders (SUDs) represent a significant public health concern in the United States, with overdose rates increasing continuously over the past 2 decades and, in particular, since the start of the COVID-19 pandemic [<xref ref-type="bibr" rid="ref1">1</xref>]. The Centers for Disease Control reported a nearly 50% increase in mortality from drug overdose from 2019 to 2021, resulting in a record high of more than 111,000 deaths (age-adjusted rate of 33.6 per 100,000 residents), which remained stable in 2022 before declining slightly in 2023 [<xref ref-type="bibr" rid="ref2">2</xref>]. Although provisional data suggest a notable drop in overdose deaths in 2024 [<xref ref-type="bibr" rid="ref3">3</xref>], the spike in mortality during this period of pandemic-related isolation highlighted the importance of social connection in SUD treatment and underscored the need to develop new digital support services to supplement face-to-face care [<xref ref-type="bibr" rid="ref4">4</xref>]. This is particularly important given that health care systems already struggle to allocate adequate financial and staffing resources to treat individuals with this chronic medical condition, who are additionally at greater risk of other health problems [<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref6">6</xref>].</p><p>Recovery from SUD is a complex, personal, and individualized process taking place within multiple clinical, social, and interpersonal contexts and necessitating multifaceted, client-centered, and person-focused care [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. In recent years, peer recovery coaches (PRCs) have been increasingly implemented in treatment programs to help address the broad array of challenges faced by individuals in recovery and actively engage them in treatment, which is critical for their long-term success [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. These nonclinical staff members extend the reach of treatment into clients&#x2019; everyday lives, leveraging their own lived experiences to provide clients with frequent and ongoing tailored support across the 4 dimensions of recovery [<xref ref-type="bibr" rid="ref8">8</xref>], including emotional and social support as well as connection to clinical resources (eg, medication-assisted treatment) or community agencies that address social determinants of health (<xref ref-type="fig" rid="figure1">Figure 1</xref>) [<xref ref-type="bibr" rid="ref13">13</xref>]. Systematic reviews [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref14">14</xref>-<xref ref-type="bibr" rid="ref16">16</xref>] suggest positive impacts of peer recovery coaching, such as decreased emergency service use, increased treatment retention, reduced relapse rates, and improved therapeutic alliance; however, these studies also highlight challenges associated with discerning the effects of peer support from other treatment activities that occur in parallel, along with the lack of standardized definitions and outcome measures used across the relevant literature. Given the challenges with sustained funding for PRC programs [<xref ref-type="bibr" rid="ref17">17</xref>], high-quality research on the effectiveness of PRCs on quality of care and health outcomes is paramount to understanding the impacts of these investments, ensuring their continued financial support.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Peer recovery coach&#x2013;client connection across 4 dimensions of recovery. PRC: peer recovery coach.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="resprot_v15i1e93754_fig01.png"/></fig></sec><sec id="s1-2"><title>Context</title><p>A key tenet of the PRC-client relationship is ongoing connection, often as mediated communication occurring through personal devices [<xref ref-type="bibr" rid="ref18">18</xref>], especially with the rise of &#x201C;digital peer support&#x201D; during the COVID-19 pandemic [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. However, while guidelines emphasize the importance of communication, they do not suggest specific means, methods, or tools [<xref ref-type="bibr" rid="ref14">14</xref>]. Existing digital recovery support services are limited in that they are either static and nonindividualized or connect clients to informal peer networks but do not provide urgent support integrated with formal care delivery or referrals [<xref ref-type="bibr" rid="ref21">21</xref>]. Relatedly, while mental health and wellness apps have proliferated in recent years, most are not empirically based, are not specific to SUD, and/or focus too narrowly on relapse rate as a recovery metric [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. Few are successfully integrated into care settings, as this requires intentional execution of usability and implementation strategies (eg, co-design processes, creation of guidelines, and training), as well as a thorough understanding of existing clinical workflows and broader health system contexts (eg, staff buy-in, leadership support, financial considerations, adherence to privacy, and security regulations), and careful consideration of how these factors facilitate or create barriers to uptake and sustained engagement [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]. As such, there is an opportunity for a specialized technology tool to facilitate PRC-client communication, with demonstrable efficacy, designed in partnership with users and with implementation and privacy considerations in mind.</p><p>To address these challenges and needs, our team proposed the development of a novel platform: Peer PLUS (People Leveraging Urgent Support; Parkview Health System, Inc). PRCs need informal but secure bidirectional communication channels to provide rapid support, along with formal channels to coordinate 24/7 care coverage and document treatment-related data across the PRC team. Peer PLUS meets both of these needs (<xref ref-type="fig" rid="figure2">Figure 2</xref>) through a stand-alone HIPAA (Health Insurance Portability and Accountability Act)-compliant mobile app (<xref ref-type="fig" rid="figure3">Figure 3</xref>) and its associated web-based client management system (<xref ref-type="fig" rid="figure4">Figure 4</xref>). This fills a critical need for a point-of-care mechanism that facilitates and enhances individualized PRC-client communication to foster therapeutic alliance, while also providing an electronic medium to effectively track client engagement and outcomes (eg, referrals to community resources, transfer of information, engagement in treatment, and referral services), as well as allow self-reported client follow-up with external agencies, addressing the legal barrier associated with information sharing between organizations. Our proposal won the 2018 American Hospital Association Innovation Challenge. Funded by this award, we developed wireframes and a low-fidelity prototype of Peer PLUS through an iterative user-centered design (UCD) process involving PRCs and clients, resulting in a functional mobile app that is ready for further evaluation [<xref ref-type="bibr" rid="ref32">32</xref>]. <xref ref-type="table" rid="table1">Table 1</xref> provides a list of key platform features and whether they are available on the client management system, the mobile app, or both.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Functions of Peer PLUS platform within the context of the peer recovery coach&#x2013;client relationship. PLUS: People Leveraging Urgent Support.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="resprot_v15i1e93754_fig02.png"/></fig><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Design prototypes for Peer PLUS mobile app. PLUS: People Leveraging Urgent Support.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="resprot_v15i1e93754_fig03.png"/></fig><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Design prototype for Peer PLUS client management system. PLUS: People Leveraging Urgent Support.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="resprot_v15i1e93754_fig04.png"/></fig><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Peer PLUS<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup> platform functionality.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Functionality</td><td align="left" valign="bottom" colspan="3">Availability</td></tr><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Client management system</td><td align="left" valign="bottom">Mobile app</td><td align="left" valign="bottom">Both</td></tr></thead><tbody><tr><td align="left" valign="top">Add client</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Client information (display and edit)</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top">Share resources</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top">Add new resources</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top">View resource details</td><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Track use of resources</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Appointment (add, edit, and delete)</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top">Message (send and receive)</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top">Add encounter notes and data</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Track required surveys and data collection</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Adding grants into the system</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Attaching coaches to grants</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Attach coach to a client</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top"/></tr><tr><td align="left" valign="top">Provide technical support and/or documentation</td><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td></tr><tr><td align="left" valign="top">Send system messages</td><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>PLUS: People Leveraging Urgent Support.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s1-3"><title>Design and Implementation Frameworks</title><p>In this study, we will apply an innovative approach that combines frameworks from 2 fields&#x2014;UCD and implementation science&#x2014;in the evaluation and refinement of our platform and the development of a robust implementation tool kit. UCD is a design philosophy that promotes early involvement of stakeholders in an iterative process over formative research, design, evaluation, and validation stages [<xref ref-type="bibr" rid="ref33">33</xref>-<xref ref-type="bibr" rid="ref35">35</xref>] until a &#x201C;safe, sound, and desirable&#x201D; solution is produced [<xref ref-type="bibr" rid="ref36">36</xref>]. Our team has already taken Peer PLUS through the UCD processes of innovation, understanding users, defining interaction, and design [<xref ref-type="bibr" rid="ref32">32</xref>]; with this protocol, we now aim to validate Peer PLUS, although we may repeat elements of earlier phases in our refinement of the platform due to the iterative nature of UCD. Implementation science is the study of methods to foster the adoption and integration of evidence-based practices (EBPs), interventions, and other research findings into routine practice, thus enhancing the quality and effectiveness of health care delivery [<xref ref-type="bibr" rid="ref37">37</xref>]. The Reach, Effectiveness, Adoption, Implementation, and Maintenance (RE-AIM) framework (<xref ref-type="fig" rid="figure5">Figure 5</xref>) provides guidance for implementing and evaluating the impact of interventions on health-related behavioral changes across 5 dimensions [<xref ref-type="bibr" rid="ref38">38</xref>]. The Reach and Effectiveness components focus on recipients of an intervention, while Adoption and Implementation focus on provider and health setting, and Maintenance includes both. We will leverage select elements from each RE-AIM domain to enhance our evaluation, using the RE-AIM Planning Tool to define and operationalize [<xref ref-type="bibr" rid="ref39">39</xref>]. In addition, we will use the Expert Recommendations for Implementing Change (ERIC) [<xref ref-type="bibr" rid="ref40">40</xref>] to map barriers to implementation strategies and apply UCD strategies to iteratively refine the design of the app (eg, interviews, think-aloud sessions, and task analysis).</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>RE-AIM processes. RE-AIM: Reach, Effectiveness, Adoption, Implementation, and Maintenance.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="resprot_v15i1e93754_fig05.png"/></fig><p>Merging of frameworks for a more comprehensive account of the steps involved in successful implementation has been encouraged, as implementation research is important for identifying factors related to integrating EBPs, but inventive strategies (ie, UCD) are often needed to improve the fit of those practices within the real-world clinical context [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], such as to address the often-overlooked innovation or intervention domain in implementation frameworks [<xref ref-type="bibr" rid="ref43">43</xref>]. As such, we aim to identify key UCD strategies that can enhance existing implementation science models to accelerate technology adoption in health care, which will offer a broad contribution to improving the integration and sustained effect of health technology [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>].</p></sec><sec id="s1-4"><title>Aims and Contributions</title><p>In this study, we propose a robust &#x201C;in-the-wild&#x201D; evaluation of our novel technology tool by the platform&#x2019;s intended users&#x2014;PRCs and their clients&#x2014;to assess its usability and its impact on specific client-centered recovery outcomes. Based on the findings of this real-world testing, we will subsequently refine the platform design and develop an implementation tool kit for future deployment. Specific study aims are displayed in <xref ref-type="table" rid="table2">Table 2</xref>.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Aims and milestones to be accomplished by the end of the R21 study period.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Aims and objectives</td><td align="left" valign="bottom">Milestone</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Aim 1: Determine if Peer PLUS<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> is perceived as usable and has sustained use by PRCs<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup> and their clients.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Refine: Apply UCD<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup> methods and RE-AIM<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup> [<xref ref-type="bibr" rid="ref38">38</xref>] to refine Peer PLUS and develop an implementation tool kit.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Revised Peer PLUS app</p></list-item><list-item><p>Draft implementation tool kit</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Usability and feasibility: Validate that Peer PLUS is easy to use and determine if it is likely to have uptake and sustained use in the proposed R33 phase.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Clients and PRCs evaluate Peer PLUS with an average SUS<sup><xref ref-type="table-fn" rid="table2fn5">e</xref></sup> [<xref ref-type="bibr" rid="ref44">44</xref>] &#x2265;68</p></list-item><list-item><p>25% of clients approached to participate in the pilot will have a smartphone and consent to participate</p></list-item><list-item><p>PRCs connect to clients who are using Peer PLUS 20% more than clients who are not</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">Aim 2: Evaluate the potential impact of Peer PLUS on recovery, quality of care, and therapeutic alliance between clients and their peer recovery coach during care for SUD<sup><xref ref-type="table-fn" rid="table2fn6">f</xref></sup>.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Impact: Demonstrate Peer PLUS impact and ability to robustly evaluate the app in the proposed R33 phase.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The following metrics are collected from all clients participating in the pilot</p></list-item></list><list list-type="bullet"><list-item><p>SURE<sup><xref ref-type="table-fn" rid="table2fn7">g</xref></sup> [<xref ref-type="bibr" rid="ref45">45</xref>]</p></list-item><list-item><p>CAHPS<sup><xref ref-type="table-fn" rid="table2fn8">h</xref></sup> ECHO<sup><xref ref-type="table-fn" rid="table2fn9">i</xref></sup> [<xref ref-type="bibr" rid="ref40">40</xref>]</p></list-item><list-item><p>WAI-SR<sup><xref ref-type="table-fn" rid="table2fn10">j</xref></sup> [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>PLUS: People Leveraging Urgent Support.</p></fn><fn id="table2fn2"><p><sup>b</sup>PRC: peer recovery coach.</p></fn><fn id="table2fn3"><p><sup>c</sup>UCD: user-centered design.</p></fn><fn id="table2fn4"><p><sup>d</sup>RE-AIM: Reach, Effectiveness, Adoption, Implementation, and Maintenance.</p></fn><fn id="table2fn5"><p><sup>e</sup>SUS: System Usability Scale.</p></fn><fn id="table2fn6"><p><sup>f</sup>SUD: substance use disorder.</p></fn><fn id="table2fn7"><p><sup>g</sup>SURE: Substance Use Recovery Evaluator.</p></fn><fn id="table2fn8"><p><sup>h</sup>CAHPS: Consumer Assessment of Healthcare Providers and Systems.</p></fn><fn id="table2fn9"><p><sup>i</sup>ECHO: Experience of Care and Health Outcomes.</p></fn><fn id="table2fn10"><p><sup>j</sup>WAI-SR: Working Alliance Inventory.</p></fn></table-wrap-foot></table-wrap><p>This work addresses existing gaps in evidence by (1) collecting outcome data that are indicators of clients&#x2019; perspectives of their recovery through standardized instruments [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref48">48</xref>] and (2) using app interaction logs and the Working Alliance Inventory (WAI-SR) [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>] to discern the impact of PRCs from other recovery treatments [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref14">14</xref>] and to quantify PRC work in support for reimbursement of PRC services [<xref ref-type="bibr" rid="ref17">17</xref>].</p><p>Peer PLUS provides an important alternative to existing recovery apps in 2 ways. For clients, the app uses minimal cellular data and does not require onerous engagement for success; rather, therapeutic alliance with the PRC is the key motivator. For agencies, the platform is not tethered to any clinical group or electronic health record (EHR); rather, the agile modular software architecture and implementation tool kit facilitate integration into site-specific custom workflows, and the companion website allows integrated management of a client panel for care coordination across the PRC team, limiting manual or disparate data tracking and increasing workflow and reporting efficiency. Thus, achievement of the proposed aims will help propel a much-needed, timely method for enhancing communication and connection between PRCs and clients, improving care while also providing an electronic medium to effectively track client engagement and outcomes [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Feasibility Objectives and Outcome Measures</title><p>This work constitutes the first phase (R21; 2 years) of a 5-year federal research grant from the Agency for Healthcare Research and Quality (AHRQ) to test Peer PLUS, develop an implementation tool kit, and determine whether the tool has sufficient usability and impact to move to the final phase of the grant (R33; randomized clinical trial). The study aims and associated objectives and outcome measures for the present phase are summarized in <xref ref-type="table" rid="table2">Table 2</xref>.</p><p>To accomplish these objectives, in year 1, we will conduct a series of UCD activities, refine the platform, and deploy it with a small sample during beta testing. In year 2, we will continue UCD work, complete further refinement, develop an implementation tool kit, and conduct a pilot study.</p><p>For aim 1, we will use UCD methods to refine the functionality of Peer PLUS (eg, develop new features) and apply implementation science frameworks to develop an implementation tool kit. We will validate usability with the 10-item System Usability Scale (SUS) [<xref ref-type="bibr" rid="ref44">44</xref>] and our own custom user experience survey incorporating RE-AIM elements. We will also measure frequency of use through app interaction logs as a proxy to determine likelihood of sustained use in the proposed R33 phase. Primary outcome measures for the pilot study will include usability ratings (SUS score &#x2265;68; ie, above average) and app usage statistics (20% more connections to clients using the app, compared to contacts with nonparticipating clients, which is documented as standard of care). Based on the client population of the health system, we will target 25% as the proportion of clients approached who are eligible and consent to determine the feasibility of recruiting the target sample size (n=200) for the trial proposed in the R33 phase.</p><p>In aim 2, we will assess the platform&#x2019;s impact on clients through several validated instruments, including the Substance Use Recovery Evaluator (SURE) [<xref ref-type="bibr" rid="ref45">45</xref>] to assess recovery, the Consumer Assessment of Healthcare Providers and Systems (CAHPS) Experience of Care and Health Outcomes (ECHO) [<xref ref-type="bibr" rid="ref48">48</xref>] to assess experience with receiving PRC services, and the WAI-SR [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>] to assess therapeutic alliance. This will demonstrate the ability to robustly evaluate the app in the proposed R33 trial.</p></sec><sec id="s2-2"><title>Setting</title><p>The study is being conducted within a mid-sized not-for-profit learning health system in the Midwestern United States. The system serves an area with significant need for SUD support and has a robust network of existing treatment pathways, including the largest behavioral health hospital and medication-assisted treatment (MAT) facilities in the region, and has employed PRCs for more than 8 years. The multidisciplinary study team is based at the health system&#x2019;s embedded Center for Research and Innovation and has prior experience creating digital solutions to support clients while maintaining health information privacy. The team includes researchers specializing in UCD, human-computer interaction, health technologies, clinical psychology, and addiction recovery, including peer recovery coaching. The PRC participants in the present phase of the study are also employed by this health system and are embedded within its emergency departments, MAT clinic, rural health centers, or mobile overdose response teams. These PRCs focus on providing emotional support and connection to treatment-related and community resources, and undergo relevant trainings such as cardiopulmonary resuscitation (CPR), suicide prevention (QPR; Question, Persuade, Refer), and naloxone administration. The PRC team&#x2019;s manager has an existing collaborative relationship with the research team and has been involved with the project since its initial proposal and design phases.</p></sec><sec id="s2-3"><title>Intervention</title><p>The primary study intervention, as described in the study design below, involves end-user trials of a novel platform (Peer PLUS) previously developed by our research center. This platform consists of a web-based client management system for use by PRCs, and an associated mobile app to facilitate PRC-client communication, intended to be used throughout the duration of each client&#x2019;s engagement with PRC services. The initial prototype of the app was developed following the 3 phases, using UCD, to ensure it reflected the needs of our health system, its PRCs, and the clients they support [<xref ref-type="bibr" rid="ref32">32</xref>]. In the formative research phase, we consulted with SUD recovery professionals within our health system to establish an initial set of user needs, which included the ability to establish potentially urgent contact and to schedule and monitor appointments. We then assessed existing mobile apps marketed for recovery support, finding that none met these needs. Subsequently, we conducted 2 stakeholder focus groups. In the first, individuals in recovery discussed their needs in the early stages of recovery, establishing that they would value a tool that both facilitated supportive communication and connected them to additional resources. In the second focus group, which included both PRCs and clients, we used a card sorting activity to rate proposed concepts and features based on the previously identified sets of needs. Next, in the design phase, we devised requirements based on these findings, which we then implemented in a high-fidelity prototype. In the evaluation phase, we evaluated this prototype with PRCs and clients in one-on-one usability sessions where participants explored the app, performed specific tasks, rated its usability, and discussed its potential benefits. Leveraging these results, we refined the platform into a fully functional prototype to be tested in this study.</p><p>During the beta testing and pilot phases of this study, clients and their PRCs will use the app for asynchronous communication when possible over a period of up to 6 months. Clients and PRCs will be given an instructional overview of the various functions of the app (eg, sending messages, accessing and sharing resources, and setting appointments), and PRCs will send their client a sample message during this introduction, but the dyads will otherwise be instructed to use the app naturally within the context of their existing support relationship. PRCs will additionally use the client management portion of the platform for their existing tasks related to documentation in lieu of their prior workflow, which consisted of a Microsoft Excel spreadsheet. During and after this usage, participants will be surveyed and interviewed about their experience, as detailed below.</p></sec><sec id="s2-4"><title>Overview of Study Design</title><p>The primary study phases broadly consist of (1) prelaunch ethnographic observations, (2) iterative beta testing of the platform, and (3) a pilot trial. Throughout these phases, data will be collected to support the listed objectives via direct participant feedback (ie, electronic surveys, interviews and/or focus groups, and UCD sessions) as well as through observation of workflows and platform usage logs. Iterative platform refinements based on these data will be completed throughout each phase, with the implementation tool kit finalized at study conclusion. Each of these phases is described further under their respective headings below, with definitions of study activities provided in <xref ref-type="other" rid="box1">Textbox 1</xref> and a planned timeline for study activities in <xref ref-type="table" rid="table3">Table 3</xref>.</p><boxed-text id="box1"><title> Study activities defined.</title><list list-type="bullet"><list-item><p>Ethnography involves direct observation of users in their natural environment. We will use prelaunch and post-beta test and pilot ethnography to observe workflows and identify breakdowns and opportunities for technology refinement. [<xref ref-type="bibr" rid="ref49">49</xref>]</p></list-item><list-item><p>Stakeholder engagement includes focus groups or interviews using semistructured prompts modeled from RE-AIM (Reach, Effectiveness, Adoption, Implementation, and Maintenance) constructs and/or from ethnographic findings. We will use a variety of user-centered design strategies to engage end users to ascertain preferences, experiences, and priorities for using Peer PLUS (People Leveraging Urgent Support), including barriers and facilitators. Findings will inform updates to the platform and implementation tool kit.</p></list-item><list-item><p>Surveys will be used to capture various measures of usability, user experience, and impact on recovery, client-PRC (peer recovery coach) alliance, and health outcomes, as well as participant demographics, and are detailed in <xref ref-type="other" rid="box2">Textbox 2</xref>.</p></list-item><list-item><p>Semistructured interviews will focus on 2 critical components for predicting adoption of new technologies: perceived usefulness and relative advantage. [<xref ref-type="bibr" rid="ref50">50</xref>] As our PRCs already use technology for both communication and tracking, the perceived usefulness and relative advantage of Peer PLUS for each of these uses will be explored.</p></list-item><list-item><p>PRC client tracking sheet is a spreadsheet currently used by PRCs to track certain client data as part of standard practice. We will leverage this to gather demographic data related to this overall client population and characterize nonparticipating clients.</p></list-item><list-item><p>Peer PLUS use log data will be collected automatically by the app. Data points include (1) user-specific logins, (2) number and type of messages sent (eg, standard, appointment, and referral), (3) number of resources viewed and uploaded, (4) number of calendar appointments added, (5) number of client profile edits, (6) time elapsed between message received and read, and (7) time elapsed between notification sent and app opened. We will not collect message content, names, or other personal identifiers; data stored and analyzed will use participant ID numbers, and dates will be represented as time elapsed since study initiation.</p></list-item><list-item><p>Implementation tool kit development includes definitions, policies, and procedures for both setup and usage of the platform. This will be developed iteratively throughout the study using findings from all phases.</p></list-item></list></boxed-text><boxed-text id="box2"><title> Inclusion and exclusion criteria.</title><p><bold>All participants: inclusion criteria</bold></p><list list-type="bullet"><list-item><p>Aged 18 years or older</p></list-item><list-item><p>Lives in the United States</p></list-item><list-item><p>Reads, speaks, and understands English</p></list-item><list-item><p>Agrees to voice and video recording during interviews and/or focus groups</p></list-item><list-item><p>Consents to participate in the study</p></list-item></list><p><bold>Client: inclusion criteria</bold></p><list list-type="bullet"><list-item><p>Has a substance use disorder (SUD) diagnosis</p></list-item><list-item><p>Receives SUD support from a peer recovery coach (PRC)</p></list-item><list-item><p>Has access to a functioning Android or Apple smartphone with the ability to receive and send texts</p><list list-type="bullet"><list-item><p>For clients with Android smartphones only, must have a Gmail account or be willing to set up a Gmail account</p></list-item></list></list-item><list-item><p>Able to download apps from their smartphone&#x2019;s app store</p></list-item><list-item><p>Has an accessible email address or is willing to set up an email account</p></list-item><list-item><p>Per PRC&#x2019;s professional judgment, is an appropriate candidate to participate in the study</p></list-item></list><p><bold>Client: exclusion criteria (pilot only)</bold></p><list list-type="bullet"><list-item><p>Has been engaged in the program for more than 6 months</p></list-item></list><p><bold>PRC: inclusion criteria</bold></p><list list-type="bullet"><list-item><p>Employed as a PRC</p></list-item><list-item><p>Uses an Android or Apple smartphone as part of their PRC duties</p><list list-type="bullet"><list-item><p>For PRCs with Android smartphones only, they must have a Gmail account or be willing to set up a Gmail account</p></list-item></list></list-item><list-item><p>Able to download apps from the smartphone&#x2019;s app store</p></list-item></list><p><bold>PRC manager: inclusion criteria</bold></p><list list-type="bullet"><list-item><p>Employed as a PRC manager or supervisor</p></list-item></list></boxed-text><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Breakdown of the activities as it relates to the initial timeline.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Months</td><td align="left" valign="bottom">Activities</td></tr></thead><tbody><tr><td align="left" valign="top">0&#x2010;3</td><td align="left" valign="top">Prelaunch ethnography</td></tr><tr><td align="left" valign="top">4&#x2010;8</td><td align="left" valign="top">Beta testing</td></tr><tr><td align="left" valign="top">9&#x2010;12</td><td align="left" valign="top">Platform and tool kit refinement</td></tr><tr><td align="left" valign="top">13&#x2010;20</td><td align="left" valign="top">Pilot</td></tr><tr><td align="left" valign="top">21&#x2010;22</td><td align="left" valign="top">Platform and tool kit refinement</td></tr><tr><td align="left" valign="top">23&#x2010;24</td><td align="left" valign="top">Final analysis and Go/No Go R33</td></tr></tbody></table></table-wrap><p>The beta tests and pilot will involve app usage by clients and PRC participants as part of their existing support relationship and in addition to standard care, with PRCs additionally using the platform&#x2019;s client management system. All client participants will be clients of a PRC who is also enrolled in the study, and each PRC participant may have multiple clients enrolled. Participants will be asked to use the app for asynchronous communication outside of in-person meetings, when possible. The length of participant engagement for a beta test or pilot trial was planned to last up to 3 or 6 months, respectively.</p><p>During and immediately after their trial period, participants&#x2019; perceptions and experiences will be assessed through periodic deployment of electronic surveys along with posttest engagement. During beta testing, these surveys will be focused primarily on the usability of the platform; during the pilot, clients will be additionally surveyed regarding certain treatment outcomes. Descriptions of survey measures are listed in <xref ref-type="other" rid="box3">Textbox 3</xref>. Further, after each phase, additional user observations, interviews and/or focus groups, and UCD sessions will be conducted. Feedback from participants throughout all phases, in addition to application usage logs, will be used to iteratively refine the app and contribute to the development of a finalized implementation tool kit at study completion (<xref ref-type="table" rid="table4">Table 4</xref>). Any updates to software functionality or improvement opportunities identified during the beta testing and pilot phases will be implemented and tested by our development and user experience team until the app is stabilized.</p><boxed-text id="box3"><title> Survey instruments.</title><list list-type="bullet"><list-item><p>System Usability Scale (SUS) [<xref ref-type="bibr" rid="ref44">44</xref>] is a 10-item validated instrument for measuring usability of a variety of products, including software. Scores range from 0 to 100. A score above 68 is considered above average.</p></list-item><list-item><p>Substance Use Recovery Evaluator (SURE) [<xref ref-type="bibr" rid="ref45">45</xref>] is a 21-question psychometrically valid instrument measuring recovery from drug and alcohol dependence. Respondents use a 5-point response set to indicate frequency of use and cravings, self-care, material resources, outlook on life, and relationships. Each item is scored as 1&#x2010;3 and scores are summed. A higher score indicates greater recovery.</p></list-item><list-item><p>CAHPS Experience of Care and Health Outcomes (ECHO) [<xref ref-type="bibr" rid="ref48">48</xref>] is a 37-question instrument that has been validated to assess an individual&#x2019;s experience with behavioral health care and services. We will use the 6-item Communication Quality subscale to evaluate the clients&#x2019; experience with peer recovery support, replacing the word &#x201C;Clinicians&#x201D; with &#x201C;Peer Coach<italic>.&#x201D;</italic></p></list-item><list-item><p>Working Alliance Inventory (WAI-SR) [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>] is a 12-item survey that will be used with both client and PRC participants to assess 3 aspects of therapeutic alliance: (1) agreement on tasks of therapy, (2) agreement on goals of therapy, and (3) development of an affective bond. &#x201C;Recovery&#x201D; will replace &#x201C;therapy&#x201D; to align with the study setting, as PRCs do not provide therapy but rather provide support during recovery.</p></list-item><list-item><p>Custom user experience (UX) survey questions will be shaped by stakeholder engagements and will incorporate RE-AIM (Reach, Effectiveness, Adoption, Implementation, and Maintenance) elements [<xref ref-type="bibr" rid="ref38">38</xref>] and the technology acceptance model frameworks adapted for health care [<xref ref-type="bibr" rid="ref51">51</xref>].</p></list-item><list-item><p>Demographics will be collected through a custom survey at the time of enrollment.</p></list-item></list></boxed-text><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Study data points. Data points collected for research operations are not included.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Participant types and study data points</td><td align="left" valign="bottom" colspan="2">Applies to</td><td align="left" valign="bottom">Source</td></tr><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Beta tests</td><td align="left" valign="bottom">Pilot</td><td align="left" valign="bottom"/></tr></thead><tbody><tr><td align="left" valign="top" colspan="4">All client participants</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Demographic data</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Enrollment survey</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>WAI-SR<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup></td><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Postenrollment surveys</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SUS<sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup> and/or Custom UX<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup></td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Postenrollment surveys</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SURE<sup><xref ref-type="table-fn" rid="table4fn4">d</xref></sup> and ECHO<sup><xref ref-type="table-fn" rid="table4fn5">e</xref></sup></td><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Postenrollment surveys</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Peer PLUS<sup><xref ref-type="table-fn" rid="table4fn6">f</xref></sup> use data</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Application server</td></tr><tr><td align="left" valign="top" colspan="4">All or select client participants</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Data from stakeholder engagements</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Posttest UCD<sup><xref ref-type="table-fn" rid="table4fn7">g</xref></sup> activities</td></tr><tr><td align="left" valign="top" colspan="4">All PRC<sup><xref ref-type="table-fn" rid="table4fn8">h</xref></sup> participants</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Demographic data</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Enrollment survey</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>WAI-SR</td><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Postenrollment surveys</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SUS and/or Custom UX</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Postenrollment surveys</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Peer PLUS use data</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Application server</td></tr><tr><td align="left" valign="top" colspan="4">All or select PRC and PRC manager participants</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Data from stakeholder engagements</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Posttest UCD activities</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Data from prelaunch ethnography</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top"/><td align="left" valign="top">Prelaunch ethnography</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Data from post-beta test and pilot ethnography</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Posttest ethnography</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Data from post-beta test and pilot semistructured interviews</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Posttest interviews</td></tr><tr><td align="left" valign="top" colspan="4">Study-wide (not participant-specific)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Nonidentifying data: clients not asked to participate, for example, race, ethnicity, and age group</td><td align="left" valign="top"/><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">PRC client tracking sheet</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Nonidentifying data: clients declining to participate, for example, race, ethnicity, age group, and reason for declining (collected as general qualitative feedback)</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">&#x2713;</td><td align="left" valign="top">Screen failure log</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>WAI-SR: Working Alliance Inventory.</p></fn><fn id="table4fn2"><p><sup>b</sup>SUS: System Usability Scale.</p></fn><fn id="table4fn3"><p><sup>c</sup>UX: user experience.</p></fn><fn id="table4fn4"><p><sup>d</sup>SURE: Substance Use Recovery Evaluator.</p></fn><fn id="table4fn5"><p><sup>e</sup>ECHO: Experience of Care and Health Outcomes.</p></fn><fn id="table4fn6"><p><sup>f</sup>PLUS: People Leveraging Urgent Support.</p></fn><fn id="table4fn7"><p><sup>g</sup>UCD: user-centered design.</p></fn><fn id="table4fn8"><p><sup>h</sup>PRC: peer recovery coach.</p></fn></table-wrap-foot></table-wrap><p>Study activities involving direct interaction with participants (eg, informed consent meetings, observations, interviews, and UCD activities) will generally take place at a health system facility or via videoconferencing, but could also occur in a private community-based setting. Surveys will be deployed virtually using REDCap, a HIPAA-compliant web-based survey platform, and distributed via text, email, and/or Peer PLUS. Client participants will complete surveys on their personal devices, and PRC and manager participants will complete them during work hours on the device they use for work.</p></sec><sec id="s2-5"><title>Prelaunch Rapid Ethnography</title><p>Prior to user testing, we planned to conduct a prelaunch rapid ethnography [<xref ref-type="bibr" rid="ref52">52</xref>] of up to 4 PRCs to document workflows and process requirements that may be altered with the integration of the platform, including direct interaction with clients, caseload management, resource sharing, and report generation. Through these observations, we sought to understand opportunities for improved productivity and client connection, including day-to-day work that is not quantified in existing workflow documentation. This served as the initial foundation for the development of implementation tool kit components.</p><p>Several months prior to beta testing, the study team observed 3 PRCs who represented the different types of coaches within our specific program&#x2014;maternal, community, and emergency department&#x2014;over a period of approximately 8 hours each. PRCs were identified by their manager as they represented the different types of coaches. The research team reached out to PRCs to assess their interest in participating and obtained verbal agreement to participate. At the beginning of each observation, the researchers explained the procedure and made sure that any questions they might have were answered. Observations were recorded through detailed written notes with time stamps and descriptions. During these observation sessions, paper-based documents containing resources that may be provided to clients were reviewed and copied in preparation for integration into the Peer PLUS platform. To validate and inform the translation of these ethnographic findings into the development of the platform, we subsequently engaged in follow-up discussions with PRCs and managers to provide clarity regarding our observations in a series of co-design sessions. In particular, we collated resources that were collected during these observations and met with 3 PRCs to discuss how to optimally organize and present them in the mobile app. Once the initial version of the app was finalized, we began recruitment for beta testing.</p></sec><sec id="s2-6"><title>Beta Testing and Pilot Trial</title><sec id="s2-6-1"><title>Sample Size and Planned Recruitment Rate</title><p>We planned to conduct up to 3 incremental beta tests of Peer PLUS, with up to 4 PRCs and up to 4 clients per PRC (n=16 clients) per test. After beta testing is completed, up to 15 PRCs and up to 40 clients will pilot Peer PLUS, which is in line with HCI testing practices [<xref ref-type="bibr" rid="ref53">53</xref>]. After each test phase, select clients and PRCs will participate in stakeholder engagements to reflect on their experiences. The PRC manager will be involved throughout all phases of the study; in the context of our existing collaborative relationship, the manager has provided design input and serves as an intermediary between the research team and PRCs rather than being enrolled as a consented participant. However, the protocol was written to allow for manager participants (eg, in the case of changes to staffing or location). In total, up to 4 PRC managers, 16 PRCs, and 88 clients may participate across both phases; refer to <xref ref-type="table" rid="table5">Table 5</xref>.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Maximum number of participants per study activity.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Peer PLUS<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup> use</td><td align="left" valign="bottom">Stakeholder engagements</td><td align="left" valign="bottom" colspan="3">Surveys</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top"/><td align="left" valign="top">WAI-SR<sup><xref ref-type="table-fn" rid="table5fn2">b</xref></sup></td><td align="left" valign="top">SUS<sup><xref ref-type="table-fn" rid="table5fn3">c</xref></sup> and/or Custom UX<sup><xref ref-type="table-fn" rid="table5fn4">d</xref></sup></td><td align="left" valign="top">SURE<sup><xref ref-type="table-fn" rid="table5fn5">e</xref></sup> and ECHO<sup><xref ref-type="table-fn" rid="table5fn6">f</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top" colspan="6">Each beta test</td></tr><tr><td align="left" valign="top">&#x2003;Clients</td><td align="left" valign="top">16</td><td align="left" valign="top">8</td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table5fn7">g</xref></sup></td><td align="left" valign="top">16</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">&#x2003;PRCs<sup><xref ref-type="table-fn" rid="table5fn8">h</xref></sup></td><td align="left" valign="top">4</td><td align="left" valign="top">4</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">4</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">&#x2003;&#x2003;&#x2003;&#x2003;PRC managers or<break/>&#x2003;&#x2003;&#x2003;&#x2003;supervisors</td><td align="left" valign="top">4</td><td align="left" valign="top">4</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">4</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top" colspan="6">Pilot</td></tr><tr><td align="left" valign="top">&#x2003;Clients</td><td align="left" valign="top">40</td><td align="left" valign="top">8</td><td align="left" valign="top">40</td><td align="left" valign="top">40</td><td align="left" valign="top">40</td></tr><tr><td align="left" valign="top">&#x2003;PRCs</td><td align="left" valign="top">15</td><td align="left" valign="top">15</td><td align="left" valign="top">15</td><td align="left" valign="top">15</td><td align="left" valign="top">&#x2014;</td></tr><tr><td align="left" valign="top">&#x2003;PRC managers/ or supervisors</td><td align="left" valign="top">4</td><td align="left" valign="top">4</td><td align="left" valign="top">&#x2014;</td><td align="left" valign="top">4</td><td align="left" valign="top">&#x2014;</td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>PLUS: People Leveraging Urgent Support.</p></fn><fn id="table5fn2"><p><sup>b</sup>WAI-SR: Working Alliance Inventory.</p></fn><fn id="table5fn3"><p><sup>c</sup>SUS: System Usability Scale.</p></fn><fn id="table5fn4"><p><sup>d</sup>UX: user experience.</p></fn><fn id="table5fn5"><p><sup>e</sup>SURE: Substance Use Recovery Evaluator.</p></fn><fn id="table5fn6"><p><sup>f</sup>ECHO: Experience of Care and Health Outcomes.</p></fn><fn id="table5fn7"><p><sup>g</sup>Not applicable.</p></fn><fn id="table5fn8"><p><sup>h</sup>PRC: peer recovery coach.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-6-2"><title>Eligibility Criteria</title><p>Study participants were included based on the criteria listed in <xref ref-type="other" rid="box2">Textbox 2</xref>. In this study, PRCs were employed by the health system of the study, although their clients may not be patients of that health system, as they may have been referred through another pathway. This participant population is appropriate for the subject of study due to their status as intended real-world users of the mobile app engaged in a peer support relationship. For the pilot test in particular, we updated the criteria to exclude clients who had been engaged in the peer recovery program for more than 6 months, based on feedback from initial beta test participants regarding the specific utility of the Peer PLUS platform in building the PRC-client relationship and introducing new resources during the early stages of treatment.</p></sec><sec id="s2-6-3"><title>Screening, Recruitment, and Enrollment</title><p>Screening for participant recruitment will occur in multiple steps. In each testing phase, PRCs will be contacted prior to clients. Once each PRC has agreed to participate, they will provide information for qualifying clients for the research team to contact, based on their knowledge of the recruitment criteria in relation to their client population. The research team will confirm that participants meet the criteria during this initial contact.</p></sec></sec><sec id="s2-7"><title>Recruitment Methods</title><sec id="s2-7-1"><title>Beta Testing Phase</title><p>During beta testing, engagement is key to success; as such, we sought to enroll participants who would be particularly interested and invested in helping evaluate and identify problems in platform design and/or processes. To enroll PRCs, the study team asked the PRC manager to recommend PRCs they believed would fit this description. Once enrolled, PRCs then recommended clients. In each case, after receiving these recommendations, the study team contacted potential participants to assess interest and set up an initial meeting.</p></sec><sec id="s2-7-2"><title>Pilot Phase</title><p>In the pilot phase, we will seek to enroll PRCs in a more naturalistic manner. As such, the study team will obtain a list of all currently employed PRCs from the manager and contact them to assess interest. Once enrolled, their clients will form the pool of eligible participants. The trust between the PRC and the client is key. Thus, a purely naturalistic recruitment strategy for clients is not feasible, as we wanted to ensure that trust in the program had been developed before approaching newer clients to participate in the study, and we did not want to disrupt the health system&#x2019;s existing processes for engaging clients in the program. The study team will provide recruitment flyers and training on inclusion and exclusion criteria to PRCs so that they can introduce the study to their clients. If an eligible client expresses interest, the PRC will check &#x201C;Yes&#x201D; in the &#x201C;informed about study&#x201D; section in the client management system. The study team will run reports to identify which clients have been informed about the study and thus need to be contacted for recruitment. For all recruitment activities, participants may be initially contacted by phone and/or email (and/or Microsoft Teams, in the case of PRCs). Institutional review board (IRB)&#x2013;approved scripts for emails and calls will be used but may be adapted as necessary for clarity and/or to answer participant questions or concerns.</p></sec></sec><sec id="s2-8"><title>Consent</title><p>Prior to participation in a beta test or pilot trial, all participants (ie, clients and PRCs) will complete the informed consent process during a meeting scheduled with a member of the research team. A team member will review the consent form with participants, who will be given adequate time to ask questions before deciding to participate. Consent will be documented via virtual signature in REDCap, wherein participants indicate their agreement and enter a unique study ID number assigned to them by the research team. Consenting online is a common practice in minimal-risk social behavioral research. Although the study procedures do not involve collecting data from the EHR, client participants will also sign a HIPAA authorization, as the research team will encounter identifying information through surveys and review of client data collected by PRCs. For the beta test phase, the study team will request that participating PRCs also attend their clients&#x2019; meetings, although PRCs will exit the room (virtual or physical) during the actual consent process. During this meeting or a separate meeting after consent has been obtained, all participants will be instructed on how to install and uninstall the app, and the process to connect the PRC and client within the app will be completed, along with brief training on the functions and resources available within the app.</p></sec><sec id="s2-9"><title>Participant Incentives</title><p>Client participants are compensated via an electronic gift card after completion of each qualifying study activity. PRCs complete study activities during normal work hours and do not receive additional compensation. <xref ref-type="table" rid="table6">Table 6</xref> illustrates the maximum compensation clients could obtain.</p><table-wrap id="t6" position="float"><label>Table 6.</label><caption><p>Maximum compensation for participation in each phase of research.</p></caption><table id="table6" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Phase</td><td align="left" valign="bottom" colspan="2">Surveys</td><td align="left" valign="bottom" colspan="2">Stakeholder engagements (including interviews)</td><td align="left" valign="bottom">Total (US $)</td></tr><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Count</td><td align="left" valign="bottom">Compensation (US $)</td><td align="left" valign="bottom">Count</td><td align="left" valign="bottom">Compensation (US $)</td><td align="left" valign="bottom"/></tr></thead><tbody><tr><td align="left" valign="top">Beta test</td><td align="left" valign="top">4</td><td align="left" valign="top">$15/survey</td><td align="left" valign="top">1</td><td align="left" valign="top">$25/engagement</td><td align="left" valign="top">$85</td></tr><tr><td align="left" valign="top">Pilot</td><td align="left" valign="top">12</td><td align="left" valign="top">$15/survey</td><td align="left" valign="top">1</td><td align="left" valign="top">$25/engagement</td><td align="left" valign="top">$205</td></tr></tbody></table></table-wrap><p>Compensation amounts reflect the time and effort commitment required of participants. It is expected that each survey will take 5&#x2010;10 minutes to complete, though some could take up to 60 minutes. Interviews will last approximately 30 to 60 minutes. Estimated time spent using Peer PLUS during their trial period will vary. As such, for the beta tests, we anticipate that participants may spend up to 3 hours taking surveys and participating in an interview, not including travel, and for the pilot, this may be up to 10 hours.</p></sec><sec id="s2-10"><title>Beta Testing Procedure</title><p>During each beta test, PRCs and clients were instructed to use the platform for the asynchronous communication that would occur as part of their existing support relationship; that is, participants were encouraged to use the app if they liked it and felt that it met their needs, but there was no minimum amount of app usage required for participation. PRCs were instructed to use the client management system for documentation. Participants were surveyed at regular intervals during their period of usage (eg, 15 and 30 days postenrollment) to assess perceptions on ease of use (SUS and/or our custom user experience survey; refer to <xref ref-type="other" rid="box2">Textbox 2</xref>).</p><p>At the end of each beta test, we applied UCD methods (eg, contextual inquiry and think-aloud exercises) in stakeholder engagements with enrolled participants to further establish usability issues and facilitate rapid evaluation to inform app and tool kit refinement. This included both virtual and in-person meetings where the team asked specific questions following up on their individual use patterns, doing think-aloud walk-throughs of the mobile app features, and rank weighting of feature changes. The findings from these sessions were collated and presented back to the research team for discussion and potential translation into the next iteration of the platform. During this process, we used RE-AIM Planning and Evaluation Framework constructs [<xref ref-type="bibr" rid="ref38">38</xref>] to identify implementation barriers and ERIC strategies [<xref ref-type="bibr" rid="ref40">40</xref>] and UCD methods to resolve them.</p></sec><sec id="s2-11"><title>Pilot Procedure</title><p>During the pilot study, PRCs and clients will again be asked to use the platform for asynchronous communication and will be surveyed about their experience. Postenrollment surveys will be deployed at multiple time points: quality of working alliance (WAI-SR) will be assessed twice (eg, 30 and 60 days), and perceptions on ease of use (SUS and/or our custom user experience survey) will be assessed at 2 time points (eg, 20 and 80 days). Clients will additionally be queried on self-reported recovery outcomes (SURE) at baseline and at up to 3 time points post enrollment (eg, 30, 60, and 90 days), and on client experience (ECHO) up to 2 times (eg, 30 and 60 days).</p><p>We will additionally conduct semistructured interviews with a subset of clients and PRCs, applying UCD methodology and focusing on perceived usefulness and relative advantage of the Peer PLUS platform. An example interview guide is provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. We will conduct post-pilot ethnographic observations with PRC and manager participants to note changes in workflows as a result of the platform (eg, distribution of resources and report generation).</p></sec><sec id="s2-12"><title>Platform and Implementation Tool Kit Development and Refinement</title><p>The protocol was designed to allow for iterative refinement of the Peer PLUS platform based on feedback elicited in each study phase. For example, ethnographic observations highlighted the need to digitize a variety of paper-based resources so that they could be easily shared within the app. Based on beta testing findings, the platform was enhanced considerably. Examples include streamlining the login process by allowing the email address (login ID) to be saved and not having to be reentered each time the app is opened, allowing more than 1 PRC to be attached to a client, and creating alerts in the client management system for individuals such as maternal clients who were timing out of being a maternal patient, allowing for a more seamless transition to a nonmaternal PRC if desired by the client. Findings of the postpilot trial interviews and observations will be leveraged to refine the app and update user guides, workflows, and other items for the implementation tool kit as needed.</p><p>The implementation tool kit will similarly be developed iteratively throughout study phases, leveraging findings and feedback, with the ultimate intent of facilitating seamless integration of Peer PLUS for other organizations. The tool kit will include recommended departmental policies to consider, instruments and UCD methods to apply in advance of Peer PLUS adoption to understand the unique context and workflow, instruments to evaluate implementation success, and user guides. This approach is intended to provide the necessary information for end users (including both clients and recovery staff) as well as other relevant stakeholders (eg, organizational technology support specialists) to use when implementing this platform into clinical workflows. Resources may include frequently asked questions, detailed instructions for use (eg, screenshots), definitions of terminology, and other information that facilitates understanding of what to expect during this process.</p></sec><sec id="s2-13"><title>Ethical Considerations</title><p>The study protocol and all applicable documents and amendments were approved by the Parkview Health Institutional Review Board (PRC21-0707 PLUS). The minimal risks associated with participation are outlined in the consent form, which all participants will electronically sign prior to participation in a beta test or pilot during the informed consent process detailed in the &#x201C;Consent&#x201D; section above. IRB-approved scripts will be used during recruitment and consent processes to describe study procedures, rights as research participants, and compensation. Participants will be compensated between US $15 and US $25 per study engagement, as approved by the IRB and described further in the &#x201C;Participant Incentives&#x201D; section above. Due to the sensitive nature of health data and the vulnerable population included in this study, measures will be taken to protect participants&#x2019; privacy and confidentiality, including storing data securely, coding participant data with unique identifiers stored separately from a password-protected code key, and encrypting exchanges of data between participant devices and the server to prevent unauthorized interception. The client management system is not available for download and follows data safety protocols as established by the health system. The mobile app will undergo extensive penetration testing by a third party to identify any security issues prior to the pilot launch. Issues identified will be addressed prior to PRC and client use of the app. During the study, access to the Peer PLUS mobile app will be restricted to participants and the research team; researchers will not review messages exchanged by participants. If a participant leaves the study for any reason, their access to Peer PLUS will be removed. If a PRC withdraws, their clients will be offered the option to either withdraw or be reassigned to another participating PRC, who will have access to all information visible to their previous PRC. Any data or findings shared outside of the research team will be deidentified and/or aggregated. Additional measures to protect participant safety are detailed under &#x201C;Safety Protocols&#x201D; below.</p></sec><sec id="s2-14"><title>Safety Protocols</title><p>Given the complexity of the SUD recovery journey, it is possible that participants may experience emotional discomfort when discussing or reflecting on their experiences during surveys or interviews. To minimize this risk, participants will be informed that participation is voluntary and they may decline to answer any questions. The consent form also outlines safety protocols that will be followed in relation to mental health concerns or other emergent situations. If a client expresses discomfort during a study engagement, researchers will refer them for follow-up with their PRC, as they will continue to receive standard-of-care treatment. Additionally, the research team will distribute a resource guide to each participant at enrollment with contact information for both local and national mental health helplines and facilities; this list of resources will also be accessible within the Peer PLUS platform. If during their period of participation clients do not receive a response from their PRC through Peer PLUS, or if they are having a medical emergency, they will be instructed to reach out as applicable to one of these additional resources. If a participant expresses suicidal thoughts, researchers will direct them to the health system&#x2019;s 24/7 hotline as well as the Suicide and Crisis Lifeline (988). Further, all research team members have completed QPR suicide prevention training. Although participation itself is not expected to have physical health risks, clients in recovery are vulnerable to emergent situations. In the case of an adverse health event during a study engagement, emergency health services will be called. Client participants may also be withdrawn from the study if their PRC believes it is not in their best interest to continue.</p></sec><sec id="s2-15"><title>Data Analysis</title><p>Quantitative and qualitative analyses will be conducted as described below. Findings from stakeholder engagements, focus groups, interviews, and evaluation surveys will be synthesized to develop the implementation tool kit, with iterative platform refinement largely relying on feedback derived from qualitative data. However, the primary study outcomes and feasibility metrics will rely on quantitative data, as described below.</p></sec><sec id="s2-16"><title>Statistical Analysis Plan</title><p>Data will be analyzed at the aggregate level. To address aim 1 (usability and potential for sustained use), descriptive statistics will be computed on the SUS and recruitment rates to assess whether feasibility targets are met (ie, SUS score &#x2265;68, 25% client eligibility and recruitment rate). Using data collected from the Peer PLUS user log, we will conduct a general categorical analysis as a proxy for end-user engagement. To assess our primary outcome related to client contact, in the pilot trial, we will compare the number and rate of connections to clients using the platform to PRCs&#x2019; documentation of contact with nonparticipating clients to determine whether the target of 20% more contacts with enrolled clients was met. Further, to address aim 2 (evaluating the impact of Peer PLUS on treatment-related outcomes), descriptive statistics will be calculated for the SURE, CAHPS ECHO, and WAI-SR survey measures deployed during the pilot trial, which will demonstrate potential improvement related to recovery, quality of care, and therapeutic alliance, as well as the feasibility of using these measures to evaluate the app in the R33 phase.</p></sec><sec id="s2-17"><title>Qualitative Data Analysis</title><p>The RE-AIM Planning Tool will be leveraged to shape qualitative data collection and analysis [<xref ref-type="bibr" rid="ref39">39</xref>]. Interviews will be recorded for anonymized transcription. Iterative inductive thematic analysis will be performed on the interview transcripts, along with ethnography field notes, user study notes, and open-ended survey responses [<xref ref-type="bibr" rid="ref54">54</xref>]. Analysis will include the following steps: (1) data immersion, (2) development of codes to represent concepts, (3) axial coding to identify subcodes and patterns across interviews, and (4) summarization of barriers and enablers for Peer PLUS adoption. RE-AIM elements will be mapped accordingly. At least 2 research team members are involved in all analysis activities and discussions. Reflexivity was built into the process through the process of consensus coding [<xref ref-type="bibr" rid="ref55">55</xref>]&#x2014;all coding was done collaboratively so that similar codes could be consolidated and any misalignments or disagreements on theme placement or meaning were discussed within the team and clarifications from PRCs sought if required. The positive outcomes of this approach are well documented within the development and use of health-related technologies [<xref ref-type="bibr" rid="ref56">56</xref>-<xref ref-type="bibr" rid="ref58">58</xref>]. Due to the iterative nature of the project design, we were able to get confirmation related to the formulation of the findings and how that was translated into the actual platform design.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><p>Prelaunch ethnography was conducted in 2023 and included workflow observations of 3 PRCs. Notable findings related to the significant need for integration and organization of paper-based resource documents into a centralized digital platform, as well as the opportunity for reducing the unnecessarily complicated nature of the existing workflow due to its multiple siloed sources of information and varied communication modalities. Additionally, the lack of documentation with respect to PRC tasks completed was noted. These observations, along with subsequent co-design sessions, informed the design of the Peer PLUS app, which was ultimately deployed in the initial beta test, along with the initial version of the implementation tool kit.</p><p>Our planned iterative design work continued through 2024 and 2025 with the completion of 3 beta tests in the field and a formal heuristic evaluation of the Peer PLUS platform (mobile app and client management system). A total of 3 PRCs and 7 clients were enrolled across the 3 beta tests. The first included 2 PRCs and 4 clients. In the second, we elected to focus on the client management system, enrolling the 2 PRCs from the first test along with 1 additional PRC. The third test included these 3 PRCs and 6 clients, 3 of whom had participated in the prior test. Beta testing culminated in a refined HIPAA-compliant minimal viable product that will be evaluated in the planned pilot study, for which recruitment began in late 2025. The beta tests allowed us to expand and refine the design, including allowing for more complex case management (more than 1 PRC attached to a client), integrating functionality between the online and mobile apps (sending messages, sharing resources, and creating appointments), and providing a way to create customized data snapshots for reporting (tracking grants associated with each PRC). Throughout the co-design work with PRCs, we found the client management system covered a wide gap in technology-supported documentation of client engagement. Thus, we have deployed the client management system broadly across the entire PRC team as part of standard care and will be deriving learnings from a separate program evaluation component of this project.</p><p>Once the 6-month pilot is completed, we will iterate on the platform as needed based on feedback and learnings from the pilot. With the updated tool, we will then move forward with a randomized controlled trial of Peer PLUS vs a control app. The primary outcome of this study will be self-reported recovery outcomes on the SURE scale, hypothesizing that clients using the app will have higher scores compared to a control group. During this time, the platform will also be piloted at a second site to determine the feasibility of scaling and implementing the tool at another organization.</p></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This paper describes the protocol for the evaluation of a novel technological platform, including a client management system and HIPAA-compliant mobile app to facilitate communication within the unique context of substance use recovery. We expect that our app will be perceived as usable, as measured by the SUS, in the pilot trial after refinements are implemented in line with the findings from our beta test phases. Furthermore, we believe the app will increase client connection with their PRC, and, in turn, boost engagement in recovery treatment, which will suggest potential for sustained use of the platform. As such, we hypothesize that usage of the app will strengthen therapeutic alliance and result in improved treatment outcomes for clients, as assessed on the SURE, ECHO, and WAI-SR measures. Ultimately, by considering the feedback from the PRC team and tailoring the client management system closely to their needs, we also expect that they will qualitatively report increased efficiency in managing their client pool, potentially resulting in other indirect positive outcomes for clients as well.</p><p>In the development and evaluation of this platform, we leveraged both UCD and implementation science frameworks to create a platform that considers the specific needs of PRC and client users engaged together in this complex journey, as well as the important practical aspects of implementing such a tool into clinical workflows in our own health system and beyond. As technical issues and lack of personalization are common barriers to uptake of digital support tools [<xref ref-type="bibr" rid="ref51">51</xref>], we sought to create and refine our platform to map directly to the identified needs of its intended end users. Additionally, as social connectedness and feelings of being in control of one&#x2019;s health journey are associated with increased use of such tools, we focused the platform on facilitating the PRC-client relationship and providing clients with resources that can directly support their recovery. These needs, though grounded in extant literature, were directly expressed by our study participants and informed the choice of specific features that were included or refined in the platform throughout our prelaunch ethnography and beta testing phases, informing the app that will be used in the pilot trial.</p><p>Ethnographic methodology was applied due to its increasingly recognized value within the field of implementation science [<xref ref-type="bibr" rid="ref59">59</xref>], allowing the research team to more thoroughly understand the context in which the platform would be deployed and informing its initial design. Through this, we identified a wide range of &#x201C;invisible&#x201D; work tasks completed by PRCs and devised a technological solution that would streamline these processes. Much of the day-to-day work of PRCs was not centrally documented or easily summarized, existing outside what is captured in existing literature [<xref ref-type="bibr" rid="ref60">60</xref>,<xref ref-type="bibr" rid="ref61">61</xref>] and furthering the lack of understanding surrounding the important nature of this role and emphasizing the need for a technological tool to mitigate these tensions. To this point, we integrated a PRC checklist from the literature [<xref ref-type="bibr" rid="ref62">62</xref>], and throughout the beta and pilot studies will obtain feedback during the participant engagements on what is working and what is missing. At the culmination of the pilot test, we will identify changes in workflows resulting from using the technology, which is an integral aspect of iterative design and implementation processes [<xref ref-type="bibr" rid="ref63">63</xref>].</p><p>By combining UCD and implementation science, we make a unique contribution to both fields within the context of digital health, enhancing existing implementation frameworks to accelerate the design, adoption, integration, and sustained effect of health technologies [<xref ref-type="bibr" rid="ref37">37</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. The clinical contribution of this project is 3-fold. First, it meets a need to improve the quality of aftercare among a population that faces a unique set of serious challenges related to their health condition, including stigma, chronicity, and potential for overdose death. Second, it tests a novel digital solution that captures dynamic processes of aftercare treatment, an integration model that can be generalized to other conditions wherein aftercare is a key component of client recovery. Third, it examines the feasibility of using informal communication data to further discern the impact of PRCs from other treatment modalities that occur in parallel, providing important data to support the necessity of these programs.</p><p>This project was proposed due to the limited understanding of the impact of technology-facilitated communication between PRCs and their clients. The unique role of the PRC as nonclinical staff who provide support to clients in a manner that is both formal (ie, as employees of a health system, with a need to document and track various data for operational and reporting purposes in a manner that is compliant with legal regulations and company policies) and informal (ie, as peers, with communication often occurring through personal devices) presents many challenges to both communication and documenting client engagements. Prior to study initiation, our health system&#x2019;s PRCs relied on face-to-face meetings, text messaging, paper mail, and voice calls to communicate with hundreds of existing and potential clients per month, a system that is inefficient and limits topics of discussion due to privacy and security concerns. Moreover, tracking these interactions was done manually, which is prone to errors and disrupts workflow, displacing time that could be spent engaging in meaningful client interaction. A system that offers secure communication that can be tracked with background analytics is a solution to this problem. As engagement with community resources and treatment providers is an additional goal of client support, a digital solution to track referrals and completion of activities will also help to elucidate the most used and helpful nodes in the ecosystem of support surrounding clients.</p></sec><sec id="s4-2"><title>Limitations</title><p>Limitations of this study include a small sample size and working with PRCs from only one program. Additionally, participants skewed toward White or Caucasian females (for both PRC and client participants). However, the skew in gender and ethnicity reflects the makeup of the PRCs and clients in this context. More broadly, qualitative data are inherently open to varying interpretation and thus provide their own specific set of limitations. To address this, we ensured that the research team was interdisciplinary and time was provided for thorough conversations related to process and analysis. A key limitation to qualitative studies is generalizability; however, through the extensive balancing of reporting the research process and the contextually rich outcomes that come from that can still provide valuable insights for the research community [<xref ref-type="bibr" rid="ref64">64</xref>].</p></sec><sec id="s4-3"><title>Conclusions</title><p>The overall goal of this project is to evaluate and refine a novel technology tool that was developed with the intention of providing a solution to a set of needs and constraints existing within the multifaceted context of peer recovery support services. The inclusion of individuals in recovery and their PRCs in the UCD and testing process was paramount to identifying specific workflows, functionality, and resources for inclusion in the platform and its corresponding implementation tool kit. This evaluation demonstrates the usage of ethnographic observations, UCD activities, validated survey measures, and data on the uptake and use of Peer PLUS in refining this digital health platform prototype and evaluating its feasibility for future trials. More broadly, this work also emphasizes the importance of merging UCD and implementation science frameworks in the design and evaluation of health technologies that can be integrated at scale into the workflow of this specialized peer workforce. Ultimately, our aim is that this work will help further illuminate the potential for technology support to help those in recovery from SUD thrive.</p></sec></sec></body><back><ack><p>We confirm that there was no use of generative AI in the development of this manuscript, including text, figures, or other informational content.</p></ack><notes><sec><title>Funding</title><p>This project was funded by the Agency for Healthcare Research and Quality (AHRQ; award number 5R21HS028880-02). The views expressed are those of the authors and not necessarily those of the AHRQ.</p></sec><sec><title>Data Availability</title><p>No complete datasets were generated or analyzed during the development of this protocol paper. While we have no plans to commercialize Peer PLUS, we do plan to publish the results of the study activities described in this protocol paper and to share our software designs through open-source platforms once the project is complete.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: TT, JP, VPC, MF, DA</p><p>Data curation: VPC, BP, TT, JP</p><p>Formal analysis: JP, TT, MF</p><p>Funding acquisition: TT</p><p>Investigation: TT, JP, RP, DA</p><p>Methodology: TT, JP, MF</p><p>Project administration: RP, AC</p><p>Resources: TT, EA, JP</p><p>Software: BP, AB, CB, VPC</p><p>Supervision: TT, JP</p><p>Validation: TT, EA</p><p>Visualization: TT, JP, AC</p><p>Writing &#x2013; original draft: AC, TT, JP, RP</p><p>Writing &#x2013; review &#x0026; editing: AC, TT, JP, RP, VPC, EA, MF, DA, AB, CB, BP, EH</p></fn><fn fn-type="conflict"><p>JP declares membership in the ACM SIGCHI Research Ethics Committee. All other authors (AC, RP, VPC, EA, MF, DA, AB, CB, BP, EH, TT) declare no conflicts of interest.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AHRQ</term><def><p>Agency for Healthcare Research and Quality</p></def></def-item><def-item><term id="abb2">CAHPS ECHO</term><def><p>Consumer Assessment of Healthcare Providers and Systems Experience of Health Outcomes</p></def></def-item><def-item><term id="abb3">CPR</term><def><p>cardiopulmonary resuscitation</p></def></def-item><def-item><term id="abb4">EBP</term><def><p>evidence-based practice</p></def></def-item><def-item><term id="abb5">EHR</term><def><p>electronic health record</p></def></def-item><def-item><term id="abb6">ERIC</term><def><p>Expert Recommendations for Implementing Change</p></def></def-item><def-item><term id="abb7">HIPAA</term><def><p>Health Insurance Portability and Accountability Act</p></def></def-item><def-item><term id="abb8">IRB</term><def><p>Institutional Review Board</p></def></def-item><def-item><term id="abb9">MAT</term><def><p>medication-assisted treatment</p></def></def-item><def-item><term id="abb10">PLUS</term><def><p>People Leveraging Urgent Support</p></def></def-item><def-item><term id="abb11">PRC</term><def><p>peer recovery coach</p></def></def-item><def-item><term id="abb12">QPR</term><def><p>Question, Persuade, Refer</p></def></def-item><def-item><term id="abb13">RE-AIM</term><def><p>Reach, Effectiveness, Adoption, Implementation, and Maintenance</p></def></def-item><def-item><term id="abb14">SUD</term><def><p>substance use disorder</p></def></def-item><def-item><term id="abb15">SURE</term><def><p>Substance Use Recovery Evaluator</p></def></def-item><def-item><term id="abb16">SUS</term><def><p>System Usability Scale</p></def></def-item><def-item><term id="abb17">UCD</term><def><p>user-centered design</p></def></def-item><def-item><term id="abb18">UX</term><def><p>user experience</p></def></def-item><def-item><term id="abb19">WAI-SR</term><def><p>Working Alliance Inventory</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>Friedman</surname><given-names>J</given-names> </name><name name-style="western"><surname>Akre</surname><given-names>S</given-names> </name></person-group><article-title>COVID-19 and the drug overdose crisis: uncovering the deadliest months in the United States, January&#x2012;July 2020</article-title><source>Am J Public Health</source><year>2021</year><month>07</month><volume>111</volume><issue>7</issue><fpage>1284</fpage><lpage>1291</lpage><pub-id pub-id-type="doi">10.2105/AJPH.2021.306256</pub-id><pub-id pub-id-type="medline">33856885</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="web"><article-title>National Vital Statistics System, Mortality 2018-2023. CDC WONDER online database multiple cause of death files, 2018-2023, as compiled from data provided by the 57 vital statistics jurisdictions through the Vital Statistics Cooperative Program</article-title><source>Centers for Disease Control and Prevention, National Center for Health Statistics</source><year>2024</year><access-date>2026-01-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="http://wonder.cdc.gov/ucd-icd10-expanded.html">http://wonder.cdc.gov/ucd-icd10-expanded.html</ext-link></comment></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="web"><article-title>U.S. overdose deaths decrease almost to 27% in 2024</article-title><source>US Centers for Disease Control and Prevention</source><year>2024</year><access-date>2026-01-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="https:///www.cdc.gov/nchs/pressroom/releases/20250514.html">https:///www.cdc.gov/nchs/pressroom/releases/20250514.html</ext-link></comment></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>L&#x00F3;pez-Pelayo</surname><given-names>H</given-names> </name><name name-style="western"><surname>Aubin</surname><given-names>HJ</given-names> </name><name name-style="western"><surname>Drummond</surname><given-names>C</given-names> </name><etal/></person-group><article-title>&#x201C;The post-COVID era&#x201D;: challenges in the treatment of substance use disorder (SUD) after the pandemic</article-title><source>BMC Med</source><year>2020</year><month>07</month><day>31</day><volume>18</volume><issue>1</issue><fpage>241</fpage><pub-id pub-id-type="doi">10.1186/s12916-020-01693-9</pub-id><pub-id pub-id-type="medline">32731868</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="web"><article-title>Opioid overdoses costing US hospitals an estimated $11 billion annually</article-title><source>Premier inc</source><year>2019</year><access-date>2026-07-03</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://premierinc.com/newsroom/press-releases/opioid-overdoses-costing-u-s-hospitals-an-estimated-11-billion-annually">https://premierinc.com/newsroom/press-releases/opioid-overdoses-costing-u-s-hospitals-an-estimated-11-billion-annually</ext-link></comment></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>Welty</surname><given-names>LJ</given-names> </name><name name-style="western"><surname>Harrison</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Abram</surname><given-names>KM</given-names> </name><etal/></person-group><article-title>Health disparities in drug- and alcohol-use disorders: a 12-year longitudinal study of youths after detention</article-title><source>Am J Public Health</source><year>2016</year><month>05</month><volume>106</volume><issue>5</issue><fpage>872</fpage><lpage>880</lpage><pub-id pub-id-type="doi">10.2105/AJPH.2015.303032</pub-id><pub-id pub-id-type="medline">26985602</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>Bassuk</surname><given-names>EL</given-names> </name><name name-style="western"><surname>Hanson</surname><given-names>J</given-names> </name><name name-style="western"><surname>Greene</surname><given-names>RN</given-names> </name><name name-style="western"><surname>Richard</surname><given-names>M</given-names> </name><name name-style="western"><surname>Laudet</surname><given-names>A</given-names> </name></person-group><article-title>Peer-delivered recovery support services for addictions in the United States: a systematic review</article-title><source>J Subst Abuse Treat</source><year>2016</year><month>04</month><volume>63</volume><fpage>1</fpage><lpage>9</lpage><pub-id pub-id-type="doi">10.1016/j.jsat.2016.01.003</pub-id><pub-id pub-id-type="medline">26882891</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="web"><article-title>SAMHSA&#x2019;s working definition of recovery</article-title><source>Substance Abuse and Mental Health Services Administration</source><year>2012</year><access-date>2026-07-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://store.samhsa.gov/sites/default/files/pep12-recdef.pdf">https://store.samhsa.gov/sites/default/files/pep12-recdef.pdf</ext-link></comment></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="web"><article-title>Drugs, brains, and behavior: the science of addiction: treatment and recovery</article-title><source>National Institute on Drug Abuse</source><year>2020</year><month>07</month><access-date>2026-06-30</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://nida.nih.gov/publications/drugs-brains-behavior-science-addiction/treatment-recovery">https://nida.nih.gov/publications/drugs-brains-behavior-science-addiction/treatment-recovery</ext-link></comment></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>Wangensteen</surname><given-names>T</given-names> </name><name name-style="western"><surname>Hystad</surname><given-names>J</given-names> </name></person-group><article-title>A comprehensive approach to understanding substance use disorder and recovery: former patients&#x2019; experiences and reflections on the recovery process four years after discharge from SUD treatment</article-title><source>J Psychosoc Rehabil Ment Health</source><year>2022</year><volume>9</volume><issue>1</issue><fpage>45</fpage><lpage>54</lpage><pub-id pub-id-type="doi">10.1007/s40737-021-00233-9</pub-id><pub-id pub-id-type="medline">34466372</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="web"><article-title>Peer support workers for those in recovery</article-title><source>Substance Abuse and Mental Health Services Administration</source><year>2024</year><access-date>2026-07-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.samhsa.gov/brss-tacs/recovery-support-tools/peers">https://www.samhsa.gov/brss-tacs/recovery-support-tools/peers</ext-link></comment></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Gagne</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Finch</surname><given-names>WL</given-names> </name><name name-style="western"><surname>Myrick</surname><given-names>KJ</given-names> </name><name name-style="western"><surname>Davis</surname><given-names>LM</given-names> </name></person-group><article-title>Peer workers in the behavioral and integrated health workforce: opportunities and future directions</article-title><source>Am J Prev Med</source><year>2018</year><month>06</month><volume>54</volume><issue>6 Suppl 3</issue><fpage>S258</fpage><lpage>S266</lpage><pub-id pub-id-type="doi">10.1016/j.amepre.2018.03.010</pub-id><pub-id pub-id-type="medline">29779550</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="web"><article-title>What are peer recovery support services?</article-title><source>Substance Abuse and Mental Health Services Administration</source><year>2009</year><access-date>2026-07-21</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://store.samhsa.gov/sites/default/files/sma09-4454.pdf">https://store.samhsa.gov/sites/default/files/sma09-4454.pdf</ext-link></comment></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Eddie</surname><given-names>D</given-names> </name><name name-style="western"><surname>Hoffman</surname><given-names>L</given-names> </name><name name-style="western"><surname>Vilsaint</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Lived experience in new models of care for substance use disorder: a systematic review of peer recovery support services and recovery coaching</article-title><source>Front Psychol</source><year>2019</year><volume>10</volume><fpage>1052</fpage><pub-id pub-id-type="doi">10.3389/fpsyg.2019.01052</pub-id><pub-id pub-id-type="medline">31263434</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Wheeler</surname><given-names>J</given-names> </name><name name-style="western"><surname>Matthews</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Murry</surname><given-names>A</given-names> </name><name name-style="western"><surname>Matlin</surname><given-names>K</given-names> </name></person-group><article-title>Measuring outcomes of peer recovery support services: a literature review</article-title><year>2020</year><month>07</month><access-date>2026-06-30</access-date><publisher-name>The OMNI Institute</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://archive.hshsl.umaryland.edu/entities/publication/a23297dd-989a-451d-aa69-c827134c181b">https://archive.hshsl.umaryland.edu/entities/publication/a23297dd-989a-451d-aa69-c827134c181b</ext-link></comment></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>Marchand</surname><given-names>K</given-names> </name><name name-style="western"><surname>Beaumont</surname><given-names>S</given-names> </name><name name-style="western"><surname>Westfall</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Conceptualizing patient-centered care for substance use disorder treatment: findings from a systematic scoping review</article-title><source>Subst Abuse Treat Prev Policy</source><year>2019</year><month>09</month><day>11</day><volume>14</volume><issue>1</issue><fpage>37</fpage><pub-id pub-id-type="doi">10.1186/s13011-019-0227-0</pub-id><pub-id pub-id-type="medline">31511016</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>Wallis</surname><given-names>R</given-names> </name><name name-style="western"><surname>Signorelli</surname><given-names>M</given-names> </name><name name-style="western"><surname>Linn</surname><given-names>H</given-names> </name><name name-style="western"><surname>Bias</surname><given-names>T</given-names> </name><name name-style="western"><surname>Allen</surname><given-names>L</given-names> </name><name name-style="western"><surname>Davis</surname><given-names>SM</given-names> </name></person-group><article-title>Lessons learned from employing Medicaid-funded peer recovery support specialists in residential substance use treatment settings: an exploratory analysis</article-title><source>J Subst Use Addict Treat</source><year>2023</year><month>11</month><volume>154</volume><fpage>209136</fpage><pub-id pub-id-type="doi">10.1016/j.josat.2023.209136</pub-id><pub-id pub-id-type="medline">37544511</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>Fortuna</surname><given-names>K</given-names> </name><name name-style="western"><surname>Hill</surname><given-names>J</given-names> </name><name name-style="western"><surname>Chalker</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ferron</surname><given-names>J</given-names> </name></person-group><article-title>Certified peer support specialists training in technology and delivery of digital peer support services: cross-sectional study</article-title><source>JMIR Form Res</source><year>2022</year><month>12</month><day>7</day><volume>6</volume><issue>12</issue><fpage>e40065</fpage><pub-id pub-id-type="doi">10.2196/40065</pub-id><pub-id pub-id-type="medline">36476983</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>Fortuna</surname><given-names>KL</given-names> </name><name name-style="western"><surname>Solomon</surname><given-names>P</given-names> </name><name name-style="western"><surname>Rivera</surname><given-names>J</given-names> </name></person-group><article-title>An update of peer support/peer provided services underlying processes, benefits, and critical ingredients</article-title><source>Psychiatr Q</source><year>2022</year><month>06</month><volume>93</volume><issue>2</issue><fpage>571</fpage><lpage>586</lpage><pub-id pub-id-type="doi">10.1007/s11126-022-09971-w</pub-id><pub-id pub-id-type="medline">35179660</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chandra</surname><given-names>J</given-names> </name><name name-style="western"><surname>Charpignon</surname><given-names>ML</given-names> </name><name name-style="western"><surname>Bhaskar</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Excess fatal overdoses in the United States during the COVID-19 pandemic by geography and substance type: March 2020-August 2021</article-title><source>Am J Public Health</source><year>2024</year><month>06</month><volume>114</volume><issue>6</issue><fpage>599</fpage><lpage>609</lpage><pub-id pub-id-type="doi">10.2105/AJPH.2024.307618</pub-id><pub-id pub-id-type="medline">38718338</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ashford</surname><given-names>RD</given-names> </name><name name-style="western"><surname>Bergman</surname><given-names>BG</given-names> </name><name name-style="western"><surname>Kelly</surname><given-names>JF</given-names> </name><name name-style="western"><surname>Curtis</surname><given-names>B</given-names> </name></person-group><article-title>Systematic review: digital recovery support services used to support substance use disorder recovery</article-title><source>Human Behav Emerg Tech</source><year>2020</year><month>01</month><access-date>2026-06-30</access-date><volume>2</volume><issue>1</issue><fpage>18</fpage><lpage>32</lpage><pub-id pub-id-type="doi">10.1002/hbe2.148</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Baxter</surname><given-names>C</given-names> </name><name name-style="western"><surname>Carroll</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Keogh</surname><given-names>B</given-names> </name><name name-style="western"><surname>Vandelanotte</surname><given-names>C</given-names> </name></person-group><article-title>Assessment of mobile health apps using built-in smartphone sensors for diagnosis and treatment: systematic survey of apps listed in international curated health app libraries</article-title><source>JMIR Mhealth Uhealth</source><year>2020</year><month>02</month><day>3</day><volume>8</volume><issue>2</issue><fpage>e16741</fpage><pub-id pub-id-type="doi">10.2196/16741</pub-id><pub-id pub-id-type="medline">32012102</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>Jordan</surname><given-names>HR</given-names> </name><name name-style="western"><surname>Sahni</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ahmed</surname><given-names>MM</given-names> </name><etal/></person-group><article-title>A comprehensive literature review of digital health interventions in the treatment of substance use disorder with special focus on mobile applications</article-title><source>Cureus</source><year>2023</year><month>10</month><volume>15</volume><issue>10</issue><fpage>e47639</fpage><pub-id pub-id-type="doi">10.7759/cureus.47639</pub-id><pub-id pub-id-type="medline">38021738</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Tice</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Whittington</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Fluetsch</surname><given-names>N</given-names> </name><etal/></person-group><article-title>Digital health technologies as an adjunct to medication assisted therapy for opioid use disorder</article-title><year>2020</year><month>12</month><day>11</day><access-date>2026-07-15</access-date><publisher-name>Institute for Clinical and Economic Review (ICER)</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="http://resource.nlm.nih.gov/9918230986906676">http://resource.nlm.nih.gov/9918230986906676</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>Hagaman</surname><given-names>A</given-names> </name><name name-style="western"><surname>Warren</surname><given-names>HL</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>R</given-names> </name><name name-style="western"><surname>Henderson</surname><given-names>C</given-names> </name></person-group><article-title>Peer support service activity prevalence by setting: a nine-state survey of peer workers</article-title><source>Front Public Health</source><year>2025</year><month>03</month><day>5</day><volume>13</volume><fpage>1533051</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2025.1533051</pub-id><pub-id pub-id-type="medline">40109427</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Eddie</surname><given-names>D</given-names> </name><name name-style="western"><surname>O&#x2019;Connor</surname><given-names>JB</given-names> </name><name name-style="western"><surname>George</surname><given-names>SS</given-names> </name><etal/></person-group><article-title>Peer recovery support services and recovery coaching for substance use disorder: a systematic review</article-title><source>Curr Addict Rep</source><year>2025</year><volume>12</volume><issue>1</issue><fpage>40</fpage><pub-id pub-id-type="doi">10.1007/s40429-025-00645-8</pub-id><pub-id pub-id-type="medline">41551498</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tofighi</surname><given-names>B</given-names> </name><name name-style="western"><surname>Chemi</surname><given-names>C</given-names> </name><name name-style="western"><surname>Ruiz-Valcarcel</surname><given-names>J</given-names> </name><name name-style="western"><surname>Hein</surname><given-names>P</given-names> </name><name name-style="western"><surname>Hu</surname><given-names>L</given-names> </name></person-group><article-title>Smartphone apps targeting alcohol and illicit substance use: systematic search in in commercial app stores and critical content analysis</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>04</month><day>22</day><volume>7</volume><issue>4</issue><fpage>e11831</fpage><pub-id pub-id-type="doi">10.2196/11831</pub-id><pub-id pub-id-type="medline">31008713</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Connolly</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Kuhn</surname><given-names>E</given-names> </name><name name-style="western"><surname>Possemato</surname><given-names>K</given-names> </name><name name-style="western"><surname>Torous</surname><given-names>J</given-names> </name></person-group><article-title>Digital clinics and mobile technology implementation for mental health care</article-title><source>Curr Psychiatry Rep</source><year>2021</year><month>05</month><day>7</day><volume>23</volume><issue>7</issue><fpage>38</fpage><pub-id pub-id-type="doi">10.1007/s11920-021-01254-8</pub-id><pub-id pub-id-type="medline">33961135</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ford</surname><given-names>JH</given-names> </name><name name-style="western"><surname>Alagoz</surname><given-names>E</given-names> </name><name name-style="western"><surname>Dinauer</surname><given-names>S</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>KA</given-names> </name><name name-style="western"><surname>Pe-Romashko</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gustafson</surname><given-names>DH</given-names> </name></person-group><article-title>Successful organizational strategies to sustain use of A-CHESS: a mobile intervention for individuals with alcohol use disorders</article-title><source>J Med Internet Res</source><year>2015</year><month>08</month><day>18</day><volume>17</volume><issue>8</issue><fpage>e201</fpage><pub-id pub-id-type="doi">10.2196/jmir.3965</pub-id><pub-id pub-id-type="medline">26286257</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>Torous</surname><given-names>J</given-names> </name><name name-style="western"><surname>Bucci</surname><given-names>S</given-names> </name><name name-style="western"><surname>Bell</surname><given-names>IH</given-names> </name><etal/></person-group><article-title>The growing field of digital psychiatry: current evidence and the future of apps, social media, chatbots, and virtual reality</article-title><source>World Psychiatry</source><year>2021</year><month>10</month><volume>20</volume><issue>3</issue><fpage>318</fpage><lpage>335</lpage><pub-id pub-id-type="doi">10.1002/wps.20883</pub-id><pub-id pub-id-type="medline">34505369</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>Scialanca</surname><given-names>M</given-names> </name><name name-style="western"><surname>Alexander</surname><given-names>K</given-names> </name><name name-style="western"><surname>Tofighi</surname><given-names>B</given-names> </name></person-group><article-title>Digital psychosocial interventions tailored for people in opioid use disorder treatment: scoping review</article-title><source>J Med Internet Res</source><year>2025</year><month>07</month><day>11</day><volume>27</volume><fpage>e69538</fpage><pub-id pub-id-type="doi">10.2196/69538</pub-id><pub-id pub-id-type="medline">40644708</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>Pater</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Phelan</surname><given-names>C</given-names> </name><name name-style="western"><surname>Cornet</surname><given-names>VP</given-names> </name><etal/></person-group><article-title>User-centered design of a mobile app to support peer recovery in a clinical setting</article-title><source>Proc ACM Hum-Comput Interact</source><year>2021</year><month>04</month><day>13</day><volume>5</volume><issue>CSCW1</issue><fpage>1</fpage><lpage>31</lpage><pub-id pub-id-type="doi">10.1145/3449186</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>Gould</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Lewis</surname><given-names>C</given-names> </name></person-group><article-title>Designing for usability: key principles and what designers think</article-title><source>Commun ACM</source><year>1985</year><month>03</month><volume>28</volume><issue>3</issue><fpage>300</fpage><lpage>311</lpage><pub-id pub-id-type="doi">10.1145/3166.3170</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Norman</surname><given-names>D</given-names> </name></person-group><source>The Design of Everyday Things: Revised and Expanded Edition</source><year>2013</year><publisher-name>Basic Books</publisher-name><pub-id pub-id-type="other">9780465050659</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="web"><article-title>Ergonomics of human-system interaction: part 210: human-centered design for interactive systems</article-title><source>International Organization for Standardization</source><year>2010</year><access-date>2026-07-04</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.iso.org/standard/52075.html">https://www.iso.org/standard/52075.html</ext-link></comment></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Albrecht</surname><given-names>UV</given-names> </name><name name-style="western"><surname>von Jan</surname><given-names>U</given-names> </name></person-group><article-title>Safe, sound and desirable: development of mHealth apps under the stress of rapid life cycles</article-title><source>Mhealth</source><year>2017</year><volume>3</volume><fpage>27</fpage><pub-id pub-id-type="doi">10.21037/mhealth.2017.06.05</pub-id><pub-id pub-id-type="medline">28828374</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>Eccles</surname><given-names>MP</given-names> </name><name name-style="western"><surname>Mittman</surname><given-names>BS</given-names> </name></person-group><article-title>Welcome to implementation science</article-title><source>Implement Sci</source><year>2006</year><month>12</month><volume>1</volume><issue>1</issue><fpage>1748</fpage><lpage>5908</lpage><pub-id pub-id-type="doi">10.1186/1748-5908-1-1</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>Glasgow</surname><given-names>RE</given-names> </name><name name-style="western"><surname>Harden</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Gaglio</surname><given-names>B</given-names> </name><etal/></person-group><article-title>RE-AIM planning and evaluation framework: adapting to new science and practice with a 20-year review</article-title><source>Front Public Health</source><year>2019</year><volume>7</volume><fpage>64</fpage><pub-id pub-id-type="doi">10.3389/fpubh.2019.00064</pub-id><pub-id pub-id-type="medline">30984733</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="web"><article-title>Planning tool</article-title><source>RE-AIM Improving Public Health Relevance and Population Health Impact</source><access-date>2026-06-30</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://re-aim.org/applying-the-re-aim-framework/re-aim-guidance/use-when-planning-a-project/planning-tool/">https://re-aim.org/applying-the-re-aim-framework/re-aim-guidance/use-when-planning-a-project/planning-tool/</ext-link></comment></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Powell</surname><given-names>BJ</given-names> </name><name name-style="western"><surname>Waltz</surname><given-names>TJ</given-names> </name><name name-style="western"><surname>Chinman</surname><given-names>MJ</given-names> </name><etal/></person-group><article-title>A refined compilation of implementation strategies: results from the Expert Recommendations for Implementing Change (ERIC) project</article-title><source>Implement Sci</source><year>2015</year><month>02</month><day>12</day><volume>10</volume><fpage>21</fpage><pub-id pub-id-type="doi">10.1186/s13012-015-0209-1</pub-id><pub-id pub-id-type="medline">25889199</pub-id></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dopp</surname><given-names>AR</given-names> </name><name name-style="western"><surname>Parisi</surname><given-names>KE</given-names> </name><name name-style="western"><surname>Munson</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Lyon</surname><given-names>AR</given-names> </name></person-group><article-title>Integrating implementation and user-centred design strategies to enhance the impact of health services: protocol from a concept mapping study</article-title><source>Health Res Policy Syst</source><year>2019</year><month>01</month><day>8</day><volume>17</volume><issue>1</issue><fpage>1</fpage><pub-id pub-id-type="doi">10.1186/s12961-018-0403-0</pub-id><pub-id pub-id-type="medline">30621706</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dopp</surname><given-names>AR</given-names> </name><name name-style="western"><surname>Parisi</surname><given-names>KE</given-names> </name><name name-style="western"><surname>Munson</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Lyon</surname><given-names>AR</given-names> </name></person-group><article-title>A glossary of user-centered design strategies for implementation experts</article-title><source>Transl Behav Med</source><year>2019</year><month>11</month><day>25</day><volume>9</volume><issue>6</issue><fpage>1057</fpage><lpage>1064</lpage><pub-id pub-id-type="doi">10.1093/tbm/iby119</pub-id><pub-id pub-id-type="medline">30535343</pub-id></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>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><issue>1</issue><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="ref44"><label>44</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Brooke</surname><given-names>J</given-names> </name></person-group><article-title>SUS: a retrospective</article-title><source>J Usability Stud</source><year>2013</year><access-date>2026-07-15</access-date><volume>8</volume><issue>2</issue><fpage>29</fpage><lpage>40</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/publication/285811057_SUS_a_retrospective?__cf_chl_f_tk=O9azalUQOvAUp6BhA1Z4u6zlLUVQBs4slJlkwbWM2ic-1783454319-1.0.1.1-Joos_JaIv.NabTY2W72io79AKKbThW0V9wrdXUfb63M">https://www.researchgate.net/publication/285811057_SUS_a_retrospective?__cf_chl_f_tk=O9azalUQOvAUp6BhA1Z4u6zlLUVQBs4slJlkwbWM2ic-1783454319-1.0.1.1-Joos_JaIv.NabTY2W72io79AKKbThW0V9wrdXUfb63M</ext-link></comment></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Neale</surname><given-names>J</given-names> </name><name name-style="western"><surname>Vitoratou</surname><given-names>S</given-names> </name><name name-style="western"><surname>Finch</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Development and validation of &#x201C;SURE&#x201D;: a patient reported outcome measure (PROM) for recovery from drug and alcohol dependence</article-title><source>Drug Alcohol Depend</source><year>2016</year><month>08</month><day>1</day><volume>165</volume><fpage>159</fpage><lpage>167</lpage><pub-id pub-id-type="doi">10.1016/j.drugalcdep.2016.06.006</pub-id><pub-id pub-id-type="medline">27344196</pub-id></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Horvath</surname><given-names>AO</given-names> </name><name name-style="western"><surname>Greenberg</surname><given-names>LS</given-names> </name></person-group><article-title>Development and validation of the Working Alliance Inventory</article-title><source>J Couns Psychol</source><year>1989</year><month>08</month><volume>36</volume><issue>2</issue><fpage>223</fpage><lpage>233</lpage><pub-id pub-id-type="doi">10.1037/0022-0167.36.2.223</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hatcher</surname><given-names>RL</given-names> </name><name name-style="western"><surname>Gillaspy</surname><given-names>JA</given-names> </name></person-group><article-title>Development and validation of a revised short version of the Working Alliance Inventory</article-title><source>Psychother Res</source><year>2006</year><month>01</month><volume>16</volume><issue>1</issue><fpage>12</fpage><lpage>25</lpage><pub-id pub-id-type="doi">10.1080/10503300500352500</pub-id></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Daniels</surname><given-names>AS</given-names> </name><name name-style="western"><surname>Shaul</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Greenberg</surname><given-names>P</given-names> </name><name name-style="western"><surname>Cleary</surname><given-names>PD</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Maruish</surname><given-names>ME</given-names> </name></person-group><article-title>The experience of care and health outcomes survey (ECHO): a consumer survey to collect ratings of behavioral health care treatment, outcomes and plans</article-title><source>The Use of Psychological Testing for Treatment Planning and Outcomes Assessment: Instruments for Adults</source><year>2004</year><edition>3</edition><publisher-name>Lawrence Erlbaum Associates Publishers</publisher-name><fpage>839</fpage><lpage>866</lpage><pub-id pub-id-type="doi">10.4324/9781410610614</pub-id><pub-id pub-id-type="other">9781410610614</pub-id></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Washington</surname><given-names>L</given-names> </name></person-group><article-title>Analyzing workflow for a health IT implementation. An often short-shrifted step is essential in successful IT deployments</article-title><source>J AHIMA</source><year>2008</year><month>01</month><volume>79</volume><issue>1</issue><fpage>64</fpage><lpage>65</lpage><pub-id pub-id-type="medline">18254407</pub-id></nlm-citation></ref><ref id="ref50"><label>50</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Wang</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Meister</surname><given-names>D</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>Y</given-names> </name></person-group><article-title>Relative advantage and perceived usefulness: the adoption of competing ICTs</article-title><access-date>2026-07-15</access-date><conf-name>DIGIT 2008 Proceedings</conf-name><conf-date>Dec 14, 2008</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://aisel.aisnet.org/digit2008/6">https://aisel.aisnet.org/digit2008/6</ext-link></comment></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Holden</surname><given-names>RJ</given-names> </name><name name-style="western"><surname>Karsh</surname><given-names>BT</given-names> </name></person-group><article-title>The technology acceptance model: its past and its future in health care</article-title><source>J Biomed Inform</source><year>2010</year><month>02</month><volume>43</volume><issue>1</issue><fpage>159</fpage><lpage>172</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2009.07.002</pub-id><pub-id pub-id-type="medline">19615467</pub-id></nlm-citation></ref><ref id="ref52"><label>52</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Millen</surname><given-names>DR</given-names> </name></person-group><article-title>Rapid ethnography: time deepening strategies for HCI field research</article-title><conf-name>DIS &#x2019;00: Proceedings of the 3rd Conference on Designing Interactive Systems: Processes, Practices, Methods, and Techniques</conf-name><conf-date>Aug 17-19, 2000</conf-date><conf-loc>New York City, NY</conf-loc><fpage>280</fpage><lpage>286</lpage><pub-id pub-id-type="doi">10.1145/347642.347763</pub-id></nlm-citation></ref><ref id="ref53"><label>53</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Caine</surname><given-names>K</given-names> </name></person-group><article-title>Local standards for sample size at CHI</article-title><conf-name>CHI &#x2019;16: Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems</conf-name><conf-date>May 7-12, 2026</conf-date><conf-loc>San Jose, CA</conf-loc><fpage>981</fpage><lpage>992</lpage><pub-id pub-id-type="doi">10.1145/2858036.2858498</pub-id></nlm-citation></ref><ref id="ref54"><label>54</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Clarke</surname><given-names>V</given-names> </name><name name-style="western"><surname>Braun</surname><given-names>V</given-names> </name></person-group><article-title>Thematic analysis</article-title><source>J Posit Psychol</source><year>2017</year><month>05</month><day>4</day><volume>12</volume><issue>3</issue><fpage>297</fpage><lpage>298</lpage><pub-id pub-id-type="doi">10.1080/17439760.2016.1262613</pub-id></nlm-citation></ref><ref id="ref55"><label>55</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>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>Reflecting on reflexive thematic analysis</article-title><source>Qual Res Sport Exerc Health</source><year>2019</year><month>08</month><day>8</day><volume>11</volume><issue>4</issue><fpage>589</fpage><lpage>597</lpage><pub-id pub-id-type="doi">10.1080/2159676X.2019.1628806</pub-id></nlm-citation></ref><ref id="ref56"><label>56</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jacobs</surname><given-names>M</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>J</given-names> </name><name name-style="western"><surname>Mynatt</surname><given-names>E</given-names> </name></person-group><article-title>MyPath: investigating breast cancer patients&#x2019; use of personalized health information</article-title><source>Proc ACM Hum-Comput Interact</source><year>2018</year><month>11</month><day>1</day><issue>CSCW</issue><fpage>1</fpage><lpage>21</lpage><pub-id pub-id-type="doi">10.1145/3274347</pub-id></nlm-citation></ref><ref id="ref57"><label>57</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Lukoff</surname><given-names>K</given-names> </name><name name-style="western"><surname>Lyngs</surname><given-names>U</given-names> </name><name name-style="western"><surname>Shirokova</surname><given-names>K</given-names> </name><etal/></person-group><article-title>SwitchTube: a proof-of-concept system introducing &#x201C;adaptable commitment interfaces&#x201D; as a tool for digital wellbeing</article-title><conf-name>CHI &#x2019;23: Proceedings of the 2023 CHI Conference on Human Factors in Computing Systems</conf-name><conf-date>Apr 23-28, 2023</conf-date><pub-id pub-id-type="doi">10.1145/2858036.2858498</pub-id></nlm-citation></ref><ref id="ref58"><label>58</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sawyer</surname><given-names>C</given-names> </name><name name-style="western"><surname>Carney</surname><given-names>R</given-names> </name><name name-style="western"><surname>Hassan</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Digital lifestyle interventions for young people with mental illness: a qualitative study among mental health care professionals</article-title><source>JMIR Hum Factors</source><year>2024</year><month>06</month><day>5</day><volume>11</volume><fpage>e53406</fpage><pub-id pub-id-type="doi">10.2196/53406</pub-id><pub-id pub-id-type="medline">38837191</pub-id></nlm-citation></ref><ref id="ref59"><label>59</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Faro</surname><given-names>EZ</given-names> </name><name name-style="western"><surname>Taber</surname><given-names>P</given-names> </name><name name-style="western"><surname>Seaman</surname><given-names>AT</given-names> </name><etal/></person-group><article-title>Implicit and explicit: a scoping review exploring the contribution of anthropological practice in implementation science</article-title><source>Implement Sci</source><year>2024</year><month>02</month><day>12</day><volume>19</volume><issue>1</issue><fpage>12</fpage><pub-id pub-id-type="doi">10.1186/s13012-024-01344-0</pub-id><pub-id pub-id-type="medline">38347574</pub-id></nlm-citation></ref><ref id="ref60"><label>60</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Salzer</surname><given-names>MS</given-names> </name><name name-style="western"><surname>Schwenk</surname><given-names>E</given-names> </name><name name-style="western"><surname>Brusilovskiy</surname><given-names>E</given-names> </name></person-group><article-title>Certified peer specialist roles and activities: results from a national survey</article-title><source>Psychiatr Serv</source><year>2010</year><month>05</month><volume>61</volume><issue>5</issue><fpage>520</fpage><lpage>523</lpage><pub-id pub-id-type="doi">10.1176/ps.2010.61.5.520</pub-id><pub-id pub-id-type="medline">20439376</pub-id></nlm-citation></ref><ref id="ref61"><label>61</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cronise</surname><given-names>R</given-names> </name><name name-style="western"><surname>Teixeira</surname><given-names>C</given-names> </name><name name-style="western"><surname>Rogers</surname><given-names>ES</given-names> </name><name name-style="western"><surname>Harrington</surname><given-names>S</given-names> </name></person-group><article-title>The peer support workforce: results of a national survey</article-title><source>Psychiatr Rehabil J</source><year>2016</year><month>09</month><volume>39</volume><issue>3</issue><fpage>211</fpage><lpage>221</lpage><pub-id pub-id-type="doi">10.1037/prj0000222</pub-id><pub-id pub-id-type="medline">27618458</pub-id></nlm-citation></ref><ref id="ref62"><label>62</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Byrne</surname><given-names>KA</given-names> </name><name name-style="western"><surname>Mericle</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Litwin</surname><given-names>AH</given-names> </name></person-group><article-title>Development and initial findings from the Peer Recovery Coach (PRC) checklist: a new tool to assess the nature of peer recovery coaching service delivery</article-title><source>Am J Drug Alcohol Abuse</source><year>2023</year><month>03</month><day>4</day><volume>49</volume><issue>2</issue><fpage>159</fpage><lpage>169</lpage><pub-id pub-id-type="doi">10.1080/00952990.2022.2164504</pub-id><pub-id pub-id-type="medline">36745742</pub-id></nlm-citation></ref><ref id="ref63"><label>63</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Simonsen</surname><given-names>J</given-names> </name></person-group><article-title>The role of ethnography in the design and implementation of IT systems</article-title><source>Des Princ Pract</source><year>2009</year><volume>3</volume><issue>3</issue><fpage>253</fpage><lpage>264</lpage><pub-id pub-id-type="doi">10.18848/1833-1874/CGP/v03i03/37664</pub-id></nlm-citation></ref><ref id="ref64"><label>64</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ali</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Yusof</surname><given-names>H</given-names> </name></person-group><article-title>Quality in qualitative studies: the case of validity, reliability and generalizability</article-title><source>ISEA</source><year>2011</year><volume>5</volume><issue>1</issue><fpage>25</fpage><pub-id pub-id-type="doi">10.22164/isea.v5i1.59</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Supplementary data</label><p>Semistructured interview guide.</p><media xlink:href="resprot_v15i1e93754_app1.docx" xlink:title="DOCX File, 26 KB"/></supplementary-material></app-group></back></article>