<?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 Hum Factors</journal-id><journal-id journal-id-type="publisher-id">humanfactors</journal-id><journal-id journal-id-type="index">6</journal-id><journal-title>JMIR Human Factors</journal-title><abbrev-journal-title>JMIR Hum Factors</abbrev-journal-title><issn pub-type="epub">2292-9495</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">v12i1e60585</article-id><article-id pub-id-type="doi">10.2196/60585</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Oncology Clinicians' Perspectives of a Remote Patient Monitoring Program: Multi-Modal Case Study Approach</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Mazzella-Ebstein</surname><given-names>Ann Marie</given-names></name><degrees>RN, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Daly</surname><given-names>Robert</given-names></name><degrees>MBA, MD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Huang</surname><given-names>Jennie</given-names></name><degrees>BA</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bernal</surname><given-names>Camila</given-names></name><degrees>MPH</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Wilhelm</surname><given-names>Clare</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Panageas</surname><given-names>Katherine S</given-names></name><degrees>Dr PH</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Holland</surname><given-names>Jessie</given-names></name><degrees>RN, MSN, NE-BC</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Salvaggio</surname><given-names>Rori</given-names></name><degrees>RN, MS, NEA-BC</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Ackerman</surname><given-names>Jill</given-names></name><degrees>MBA</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Cracchiolo</surname><given-names>Jennifer</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kuperman</surname><given-names>Gilad</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff8">8</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Mao</surname><given-names>Jun</given-names></name><degrees>MSCE, MD</degrees><xref ref-type="aff" rid="aff9">9</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Begue</surname><given-names>Aaron</given-names></name><degrees>RN, MS, CNP</degrees><xref ref-type="aff" rid="aff10">10</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Barton-Burke</surname><given-names>Margaret</given-names></name><degrees>RN, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib></contrib-group><aff id="aff1"><institution>Nursing Research, Department of Nursing, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff2"><institution>Thoracic Services, Department of Medicine, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff3"><institution>Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff4"><institution>Hospital Administration, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff5"><institution>Department of Surgery, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff6"><institution>Epidemiology - Biostatistics, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff7"><institution>Nursing Ambulatory Services, Department of Nursing, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff8"><institution>Digital Informatics &#x0026; Technology Solutions (DigITs), Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff9"><institution>Integrative Medicine Services, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><aff id="aff10"><institution>Hospital Administration, Advanced Practice Providers, Memorial Sloan Kettering Cancer Center</institution><addr-line>New York</addr-line><addr-line>NY</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Kushniruk</surname><given-names>Andre</given-names></name></contrib><contrib contrib-type="editor"><name name-style="western"><surname>Borycki</surname><given-names>Elizabeth</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Sharp</surname><given-names>John</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Zheng</surname><given-names>Lu</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Ann Marie Mazzella-Ebstein, RN, PhD, Nursing Research, Department of Nursing, Memorial Sloan Kettering Cancer Center, 1275 York Avenue, New York, NY, 10065, United States, 1 646-449-1077; <email>mazzella@mskcc.org</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>24</day><month>1</month><year>2025</year></pub-date><volume>12</volume><elocation-id>e60585</elocation-id><history><date date-type="received"><day>03</day><month>06</month><year>2024</year></date><date date-type="accepted"><day>23</day><month>09</month><year>2024</year></date></history><copyright-statement>&#x00A9; Ann Marie Mazzella-Ebstein, Robert Daly, Jennie Huang, Camila Bernal, Clare Wilhelm, Katherine S Panageas, Jessie Holland, Rori Salvaggio, Jill Ackerman, Jennifer Cracchiolo, Gilad Kuperman, Jun Mao, Aaron Begue, Margaret Barton-Burke. Originally published in JMIR Human Factors (<ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>), 24.1.2025. </copyright-statement><copyright-year>2025</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<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 Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://humanfactors.jmir.org">https://humanfactors.jmir.org</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2025/1/e60585"/><abstract><sec><title>Background</title><p>Remote patient monitoring (RPM) aims to improve patient access to care and communication with clinical providers. Overall, understanding the usability of RPM applications and their influence on clinical care workflows is limited from the perspectives of clinician end users at a cancer center in the Northeastern United States.</p></sec><sec><title>Objective</title><p>This study aims to explore the usability and functionality of RPM and elicit the perceptions and experiences of oncology clinicians using RPM for oncology patients after hospital discharge.</p></sec><sec sec-type="methods"><title>Methods</title><p>The sample included 30 of 98 clinicians (31% response rate) managing at least 5 patients in the RPM program and responding to the mHealth usability between March 2021 and October 2021. Overall, clinicians responded positively to the survey. Item responses with the highest proportion of disagreement were explored further. A nested sample of 5 clinicians who responded to the study survey (30% response rate) participated in interview sessions conducted from November 2021 to February 2022, averaging 60 minutes each.</p></sec><sec sec-type="results"><title>Results</title><p>Survey responses highlighted that RPM was easy to use and learn and verified symptom alerts during follow-up phone calls. Areas to improve identified practice changes from reporting RPM alerts through digital portals and its influence on clinicians&#x2019; workload burden. Interview sessions revealed 3 main themes: clinician understanding and usability constraints, patient constraints, and suggestions for improving the program. Subthemes for each theme were explored, characterizing technical and functional limitations that could be addressed to enhance efficiency, workflow, and user experience.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Clinicians support the value of RPM for improving symptom management and engaging with providers. Improvements to address RPM challenges include functional changes to enhance the program&#x2019;s utility, such as input from patients about temporal changes in their symptoms and technical resources for home monitoring devices.</p></sec></abstract><kwd-group><kwd>cancer</kwd><kwd>oncology</kwd><kwd>clinician end users</kwd><kwd>remote patient monitoring</kwd><kwd>digital health</kwd><kwd>implementation science</kwd><kwd>patient monitoring</kwd><kwd>patient access</kwd><kwd>care</kwd><kwd>communication</kwd><kwd>usability</kwd><kwd>functionality</kwd><kwd>survey</kwd><kwd>interview</kwd><kwd>efficiency</kwd><kwd>workflow</kwd><kwd>user</kwd><kwd>clinician support</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Improving the patient&#x2019;s access to care and enhancing their quality of life by preventing readmission is the primary goal of posthospital care delivery, yet traditional oncology care models often lack communication and monitoring after discharge [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. Consequently, re-admissions for oncology patients within 30 days of discharge for symptoms that could be mitigated with proactive, remote patient monitoring (RPM) is an opportunity for advancing oncology patient care [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. Our prior research at Memorial Sloan Kettering Cancer Center (MSK) highlights the potential of RPM to facilitate transitions of care through optimized patient-provider communication and proactive engagement through digital technology [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref8">8</xref>]. The RPM program was designed to reduce unplanned care visits following discharge from the hospital by proactively monitoring patient status via daily questionnaires. Electronic patient-reported outcome (ePRO) assessments generated alerts for patients enrolled in the RPM that were sent to the patient&#x2019;s primary oncology care clinician team. Details regarding the early development and integration of the organizational RPM project, as well as the patients recruited have been previously published [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. However, limited research exists describing the perspectives and experiences of the clinician end users regarding how digital interventions are integrated into clinical care and the influence of technological health care models on patient care workflows.</p><p>To address this gap, our team developed this study to gain a greater understanding of the influence of RPM on clinical workflows in daily practice as part of a larger institutional initiative supporting center-wide symptom management during the transition of care from the inpatient to the outpatient setting [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. The purpose of this study is to explore the usability of the RPM program and the perceptions and experiences of oncology clinicians using RPM to care for patients in practice after hospital discharge. The broader aim was to identify the impact, perceived usefulness ease of use, user control of the RPM, and barriers and facilitators experienced during the initial RPM implementation. The Consolidated Framework for Implementation Research [<xref ref-type="bibr" rid="ref12">12</xref>] guided this study to query oncology clinicians, the key contributors to this management strategy, about their experiences, satisfaction, usefulness, and value of RPM.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Overview</title><p>The study&#x2019;s design used a multi-modal case study approach, using quantitative (survey) and qualitative (interviews and focus groups) to characterize the phenomenon and context of integrating RPM into the practice setting [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref18">18</xref>]. This approach encourages multiple sources of evidence to understand the clinician&#x2019;s perspectives about the use and function of RPM in real-world clinical practice and its influence on patient care workflows.</p><p>Initially, survey methods assessed clinicians&#x2019; responses to the overall usability, functionality, and value of RPM. Second, clinicians participated in semistructured interviews and focus group sessions to elicit feedback and explanations about items of concern found in the survey responses [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. The interview sessions aimed to delve deeper into the survey concerns and examine the use of the RPM application from a clinical perspective.</p></sec><sec id="s2-2"><title>Setting and Clinician Sample</title><p>This study focused on clinician end users, specifically nurses involved in clinical office practices that integrated the initial organization&#x2019;s RPM initiative [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>] from October 15, 2018, to July 10, 2019, at MSK in the Northeastern United States. The clinicians in this study were the first group of end users involved in caring for oncology patients using RPM. The RPM program was rolled out sequentially, beginning with the oncology services that care for patients with the highest symptom burden (<xref ref-type="table" rid="table1">Table 1</xref>). Clinicians from physician office practice settings, who had experience in caring for at least 5 patients enrolled in RPM, were invited to participate in the usability survey. This criterion ensured that the clinicians had ample experience with using the RPM program. Additionally, a nested sample of clinicians who completed the survey were recruited to take part in semistructured interviews to provide further information about the challenges of the RPM identified from the survey [<xref ref-type="bibr" rid="ref19">19</xref>-<xref ref-type="bibr" rid="ref22">22</xref>].</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Description of practice clinicians by percent of the sample. Clinicians: registered nurse in practice settings; responses (n=30; response rate 31%).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Oncology specialty disease management service</td><td align="left" valign="top">m-Adapted health questionnaire disseminated, n (%)<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">Thoracic (THR)</td><td align="left" valign="top">23 (24)</td></tr><tr><td align="left" valign="top">Gastro-intestinal (GI)</td><td align="left" valign="top">30 (31)</td></tr><tr><td align="left" valign="top">Breast (BR)</td><td align="left" valign="top">15 (15)</td></tr><tr><td align="left" valign="top">Sarcoma (SAR)</td><td align="left" valign="top">6 (6)</td></tr><tr><td align="left" valign="top">Genito-urinary (GU)</td><td align="left" valign="top">6 (6)</td></tr><tr><td align="left" valign="top">General medicine oncology (GMO)</td><td align="left" valign="top">5 (5)</td></tr><tr><td align="left" valign="top">Head &#x0026; neck (HN)</td><td align="left" valign="top">4 (4)</td></tr><tr><td align="left" valign="top">Melanoma (MEL)</td><td align="left" valign="top">2 (2)</td></tr><tr><td align="left" valign="top">Myeloma (MYL)</td><td align="left" valign="top">2 (2)</td></tr><tr><td align="left" valign="top">Bone marrow transplant (BMT)</td><td align="left" valign="top">1 (1)</td></tr><tr><td align="left" valign="top">Lymphoma (LYMP)</td><td align="left" valign="top">1 (1)</td></tr><tr><td align="left" valign="top">Leukemia (LEU)</td><td align="left" valign="top">1 (1)</td></tr><tr><td align="left" valign="top">Covering clinicians/no specific service</td><td align="left" valign="top">2 (2)</td></tr><tr><td align="left" valign="top">Total surveys sent</td><td align="left" valign="top">98 (100)</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Percentage of the sample.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-3"><title>Data Collection</title><sec id="s2-3-1"><title>Survey</title><p>Eligible clinicians in this study who met the study criteria were identified using the RPMs dashboard. Clinicians were recruited using the organization&#x2019;s email with a link to a web-based consent and m-Adapted Health Usability Questionnaire from March 2021 to October 2021. To maintain the anonymity of the clinicians, broad demographic data were collected to quantify clinicians&#x2019; years of experience in their current organizational roles and use RPMs within electronic health record systems.</p><p>The m-Adapted Health Usability Questionnaire [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>], is a 29-item self-report survey, that assessed an overall understanding of the functionality of the RPM from the perspectives of the clinician end users including the quality of work life, perceived usefulness, and ease of use, and user control of RPM in a 7-point Likert Scale (1 [strongly disagree] to 7 [strongly agree]). The questionnaire takes about 13 minutes to complete in REDCap (research electronic data capture; Vanderbilt University) [<xref ref-type="bibr" rid="ref25">25</xref>]. The Cronbach &#x03B1; for all scale values was &#x003E;0.7 with scores ranging from 0.85 to 0.92. Permission to use the questionnaire was not required [<xref ref-type="bibr" rid="ref24">24</xref>].</p></sec><sec id="s2-3-2"><title>Interview Sessions and Guide</title><p>Clinicians who completed the study&#x2019;s survey were also recruited through the organization&#x2019;s email to take part in 60-minute interviews or focus group sessions. The interview guide was developed by the research team based on understanding areas where the usability of RPM was challenging for the clinicians. Items from the usability survey where the percentage of responders who disagree, disagree, and strongly disagree exceeded 44%, informed the interview and focus group guide. Topics in the guide were broad enough to elicit narrative data describing the background and contextual characteristics related to the clinician&#x2019;s experience with RPM [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. The interview guide was organized into four topics: (1) General understanding and information about the RPM; (2) Experiences, barriers, and challenges with using the RPM; (3) The Influence of the RPM on the current workflow; and (4) Suggestions for improvement (<xref ref-type="table" rid="table2">Table 2</xref>). Interviews and focus groups were conducted via the web by the PI (AMME) and the qualitative methods specialist (MBB) from November 2021 to February 2022. Verbal consent was obtained from clinicians to record sessions.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Interview guide.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Topic</td><td align="left" valign="top">Main statements</td><td align="left" valign="bottom">Probe questions</td><td align="left" valign="top">Aligns survey</td></tr></thead><tbody><tr><td align="left" valign="top">Topic 1: provide general information about the topic of study and ask questions related to the specific service and the specific patient needs.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Where do you work?</p></list-item><list-item><p>Can you tell me about your work with RPM<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup>?</p></list-item><list-item><p>What can you tell us/each other about RPM?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Can you briefly describe the patient group in your office practices (patient symptom burden, any factors in this group that need to be addressed through RPM)?</p></list-item><list-item><p>Can you describe your workflow and the technology systems used in your daily work activities?</p></list-item><list-item><p>Can you describe the workflow, and the systems used when providing care?</p></list-item><list-item><p>How does the RPM fit into the care workflow?</p></list-item></list></td><td align="left" valign="top">Q<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup> 3,4</td></tr><tr><td align="left" valign="top">Topic 2: issues and barriers that are specific to using the RPM.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>What are the strengths/barriers to using RPM from the nursing perspective?</p></list-item><list-item><p>What are the strengths/barriers to using RPM from the patient&#x2019;s perspective?</p></list-item><list-item><p>Do you think RPM is valuable: to nurses the patients?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>What functionality is found in the current systems and applications used during patient care activities to make caring for patients easy?</p></list-item><list-item><p>What functionality in the RPM is not working? Describe?</p></list-item><list-item><p>Do you think the patients like using the RPM?</p></list-item><list-item><p>Does the RPM provide value for the patients? Care?</p></list-item><list-item><p>Do you think patient education about the RPM helps?</p></list-item></list></td><td align="left" valign="top">Q 7,9,10,13</td></tr><tr><td align="left" valign="top">Topic 3: practice workflow; getting to the issue about the RPM, frequency of using the toolkit, and the influence of workflow.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>How does the RPM toolkit work with your workflow?</p></list-item><list-item><p>How do you use the RPM apps to provide care?</p></list-item><list-item><p>How do you use the RPM toolkit using the digital apps?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Describe how you use the RPM (and patients with remote monitoring devised, ie, pulse oximetry)</p></list-item><list-item><p>How do you use the information in caring for your patients?</p></list-item><list-item><p>Can you describe the communication among practitioners using the RPM?</p></list-item></list></td><td align="left" valign="top">Q 18&#x2010;20</td></tr><tr><td align="left" valign="top">Topic 4: functionality, if modified, would be meaningful and helpful for the RPM, improved workflow, user satisfaction, and improved patient outcomes.</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>What are your thoughts about how RPM functions?</p></list-item></list><list list-type="bullet"><list-item><p>How could it be improved?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>If you could fix anything about the RPM, what would it be?</p></list-item><list-item><p>To what extent do you think the modifications described could influence patient outcomes that patient care?</p></list-item><list-item><p>What current functionality has the greatest influence on workflow?</p></list-item></list></td><td align="left" valign="top">Q 23&#x2010;25</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>RPM: remote patient monitoring.</p></fn><fn id="table2fn2"><p><sup>b</sup>Q: question.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s2-4"><title>Data Analysis</title><sec id="s2-4-1"><title>Survey</title><p>Survey response data were extracted from REDCap [<xref ref-type="bibr" rid="ref25">25</xref>] to a deidentified Excel spreadsheet before analysis. To ensure anonymity, demographic information was only provided for clinicians who were sent the surveys and not collected for clinicians who responded. Data responses were initially scored in REDCap [<xref ref-type="bibr" rid="ref25">25</xref>] for the frequency and proportion of agreement or disagreement with survey items consistent with the 7-point response scale. The scale responses were then collapsed into 3 groups, disagreement (strongly disagree, disagree), neutral (neither agree nor disagree), and agreement (agree and strongly agree). The Strengthening the Reporting of Observational Studies in Epidemiology guidelines were used to report the study&#x2019;s quantitative findings [<xref ref-type="bibr" rid="ref28">28</xref>].</p></sec><sec id="s2-4-2"><title>Interviews Sessions</title><p>Data from the interviews and focus groups followed the Consolidated Criteria for Reporting Qualitative Research guidelines and were used to report the study&#x2019;s findings [<xref ref-type="bibr" rid="ref29">29</xref>]. The rigor and validity of the data were supported by clarifying participants&#x2019; statements during interview sessions. The transcripts were audio recorded, transcribed verbatim, and independently reviewed by 2 reviewers using thematic content analysis [<xref ref-type="bibr" rid="ref30">30</xref>]. Themes and subthemes were constructed based on the verbal responses from the clinicians. Team consensus was determined by agreeing upon the best representation of the data [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p></sec></sec><sec id="s2-5"><title>Ethical Considerations</title><p>This research is part of an ongoing organizational program of RPM initiatives. This research obtained ethical approval from the MSK Institutional Review Board (X20-086) as exempt research and follows the ethical principles and guidelines of the Belmont Report. All responders to surveys completed web-based informed consent to participate. Participants in focus groups and interviews provided informed verbal consent.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overview</title><p>A total of 35 clinicians participated in this study from both survey and interview sessions. Of the 98 clinicians who had experiences with at least 5 patients enrolled in RPM and received the study&#x2019;s survey, 30 responded (31% response rate). A nested sample of 5 clinicians (17% response rate) from this original group of 30 clinicians who completed the survey, also agreed to take part in 4 sessions (3 interviews; 1 focus group of 2 clinicians). Demographic data were not collected with the survey to maintain the anonymity of the clinician responders. However, the majority of clinicians who responded to the survey and interview sessions represented the Gastrointestinal, Thoracic, and Breast oncology services known to have the highest symptom burden. Of the clinicians who took part in the interview sessions, 3 clinicians had 5 or more years of organizational work experience, while 2 clinicians had 2 years or less of experience.</p></sec><sec id="s3-2"><title>Survey Responses</title><p>Overall, the clinicians reported that the RPM was easy to use and learn and that symptoms communicated through the RPM program were confirmed during follow-up phone calls. Suggested areas for improvement included communication and practice changes related to symptom management and the clinicians&#x2019; workload burden. Findings highlighting survey items with the highest frequency and proportion of survey responses are presented (<xref ref-type="table" rid="table3">Table 3</xref>).</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Frequency distribution of m-Adapted health questionnaire responses (n=30)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup>.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom" colspan="2">Statements about remote patient monitoring (RPM)</td><td align="left" valign="bottom">Total responses, n</td><td align="left" valign="bottom">Agree/somewhat agree/strongly agree, n (%)<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup></td><td align="left" valign="bottom">Neither agree nor disagree, n (%)</td><td align="left" valign="bottom">Disagree/somewhat disagree/strongly disagree, n (%)</td><td align="left" valign="bottom">Unknown, n</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="6">Ease of use and functionality as easy to learn</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">1. RPM is easy to use</td><td align="left" valign="top">27</td><td align="left" valign="top">18 (67)</td><td align="left" valign="top">2 (7)</td><td align="left" valign="top">7 (26)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">2. RPM is easy for me to learn</td><td align="left" valign="top">27</td><td align="left" valign="top">18 (67)</td><td align="left" valign="top">7 (15)</td><td align="left" valign="top">5 (18)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">3. Liked the digital interface of the patient data received through portal secure message alerts</td><td align="left" valign="top">26</td><td align="left" valign="top">8 (31)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">14 (54)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">4. I liked the digital interface of the patient data received through the Splunk/summary dashboard</td><td align="left" valign="top">26</td><td align="left" valign="top">7 (27)</td><td align="left" valign="top">12 (46)</td><td align="left" valign="top">7 (27)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">5. Information in the Splunk/summary dashboard was well-organized</td><td align="left" valign="top">25</td><td align="left" valign="top">12 (48)</td><td align="left" valign="top">9 (36)</td><td align="left" valign="top">4 (16)</td><td align="left" valign="top">5</td></tr><tr><td align="left" valign="top" colspan="6">Integrating the RPM into workflows</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">6. RPM has usable functions and capabilities</td><td align="left" valign="top">27</td><td align="left" valign="top">14 (52)</td><td align="left" valign="top">6 (22)</td><td align="left" valign="top">7 (26)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">7. RPM has been appropriate for me to care for patients</td><td align="left" valign="top">27</td><td align="left" valign="top">11 (44)</td><td align="left" valign="top">1 (4)</td><td align="left" valign="top">14 (52)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">8. Easy to integrate into my current clinical workflow</td><td align="left" valign="top">27</td><td align="left" valign="top">11 (41)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">12 (44)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top" colspan="6">Acceptable for practice</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">9. An acceptable way to coordinate health care services</td><td align="left" valign="top">26</td><td align="left" valign="top">9 (35)</td><td align="left" valign="top">5 (19)</td><td align="left" valign="top">12 (46)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">10. Improved communication between my colleague&#x2019;s office practice teams for patient symptoms</td><td align="left" valign="top">26</td><td align="left" valign="top">10 (38)</td><td align="left" valign="top">1 (4)</td><td align="left" valign="top">15 (58)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">11. Prompts me to refer patients to a specialist for symptom management</td><td align="left" valign="top">25</td><td align="left" valign="top">9 (36)</td><td align="left" valign="top">5 (20)</td><td align="left" valign="top">11 (44)</td><td align="left" valign="top">5</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">12. RPM is useful for my health care practice</td><td align="left" valign="top">26</td><td align="left" valign="top">12 (46)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">10 (39)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">13. Improved my ability to deliver health care services</td><td align="left" valign="top">27</td><td align="left" valign="top">7 (26)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">16 (59)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">14. Helped me manage my patient&#x2019;s symptoms effectively</td><td align="left" valign="top">27</td><td align="left" valign="top">11 (41)</td><td align="left" valign="top">5 (18)</td><td align="left" valign="top">11 (41)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top" colspan="6">RPM convenience</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">15. Is convenient for me to communicate with patients</td><td align="left" valign="top">26</td><td align="left" valign="top">10 (39)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">12 (46)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">16. Had many more opportunities to interact with patients</td><td align="left" valign="top">27</td><td align="left" valign="top">11 (41)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">12 (44)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">17. Felt comfortable communicating with my patients about symptoms using portal secure messaging</td><td align="left" valign="top">26</td><td align="left" valign="top">12 (46)</td><td align="left" valign="top">1 (4)</td><td align="left" valign="top">13 (50)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top" colspan="6">Devices and symptom management</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">18. Highlighted the high-risk symptoms (not pulse oximetry) provided the correct corresponding severity level for the patient-reported symptoms</td><td align="left" valign="top">27</td><td align="left" valign="top">10 (37)</td><td align="left" valign="top">5 (19)</td><td align="left" valign="top">12 (44)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">19. Highlighted symptoms related to pulse oximetry appropriately</td><td align="left" valign="top">27</td><td align="left" valign="top">10 (37)</td><td align="left" valign="top">9 (33)</td><td align="left" valign="top">8 (30)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">20. Patients were appropriately identified for pulse oximeter monitoring.</td><td align="left" valign="top">27</td><td align="left" valign="top">12 (44)</td><td align="left" valign="top">7 (26)</td><td align="left" valign="top">8 (30)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">21. Pulse oximeter monitoring enabled me to more effectively manage my patient&#x2019;s symptoms</td><td align="left" valign="top">26</td><td align="left" valign="top">10 (38)</td><td align="left" valign="top">8 (31)</td><td align="left" valign="top">8 (31)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">22. High-risk symptom alerts were confirmed upon communication with the patient by telephone</td><td align="left" valign="top">27</td><td align="left" valign="top">20 (74)</td><td align="left" valign="top">2 (7)</td><td align="left" valign="top">5 (19)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top" colspan="6">Satisfaction, value, and recommendations</td><td align="left" valign="top">&#x2003;</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">23. Using RPM has improved my job satisfaction</td><td align="left" valign="top">27</td><td align="left" valign="top">3 (11)</td><td align="left" valign="top">9 (33)</td><td align="left" valign="top">15 (56)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">24. Using RPM decreased my workload</td><td align="left" valign="top">26</td><td align="left" valign="top">2 (11)</td><td align="left" valign="top">2 (8)</td><td align="left" valign="top">21 (81)</td><td align="left" valign="top">4</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">25. Adds value to how I can care for my patients</td><td align="left" valign="top">27</td><td align="left" valign="top">8 (30)</td><td align="left" valign="top">7 (26)</td><td align="left" valign="top">12 (44)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">26. Patients reported the value of participating in RPM</td><td align="left" valign="top">27</td><td align="left" valign="top">8 (30)</td><td align="left" valign="top">7 (26)</td><td align="left" valign="top">12 (44)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">27. Overall, I am satisfied with the using RPM</td><td align="left" valign="top">27</td><td align="left" valign="top">9 (33)</td><td align="left" valign="top">4 (15)</td><td align="left" valign="top">14 (52)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">28. I would use RPM again to monitor the symptoms of patients</td><td align="left" valign="top">27</td><td align="left" valign="top">10 (37)</td><td align="left" valign="top">6 (22)</td><td align="left" valign="top">11 (41)</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top"/><td align="left" valign="top">29. I would recommend the RPM to my colleagues</td><td align="left" valign="top">26</td><td align="left" valign="top">8 (31)</td><td align="left" valign="top">5 (19)</td><td align="left" valign="top">13 (50)</td><td align="left" valign="top">4</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>Number of participants who answered the survey.</p></fn><fn id="table3fn2"><p><sup>b</sup>Percentage of the group responses.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-3"><title>Usability</title><p>The RPM was easy for clinicians to use but was influenced by a shift in basic assumptions with patients now instructed to report symptoms through portal messages rather than calling the medical offices (14/26, 54%).</p></sec><sec id="s3-4"><title>Integrated Workflows</title><p>The proportion of responses was fairly divided between agreement and disagreement. While 14 (52%) clinicians agreed that the RPM had usable functions and capabilities, 14 (52%) clinicians disagreed that the RPM was suitable for their patient care needs.</p></sec><sec id="s3-5"><title>Acceptability in Practice</title><p>A total of 16 (59%) clinicians reported a disagreement with the notion that RPM improved their ability to care for their patients and, 12 (46%) clinicians reported that the RPM was useful in their practice.</p></sec><sec id="s3-6"><title>Convenience in Patient Care</title><p>Despite similar proportions of agreement and disagreement overall, a higher proportion of clinicians (13/26, 50%) disagreed with feeling comfortable communicating with patients about symptoms through portal messages.</p></sec><sec id="s3-7"><title>Symptom Management</title><p>Clinicians reported that devices were appropriately used for 12 (44%) patients and that high-risk symptoms were confirmed during follow-up phone calls to 20 (74%) patients. The responses were fairly split between agreement (10/27, 37%) and disagreement (12/27, 44%) on how well the devices provided severity levels. Additionally, 10 (38%) patients agreed that RPM helped them manage their patients.</p></sec><sec id="s3-8"><title>Satisfaction and Value</title><p>A total of 21 (81%) clinicians reported that the RPM did not decrease their workload and 15 (56%) clinicians reported it did not improve job satisfaction. In addition, 14 (52%) of the clinicians were not satisfied with RPM, and 13 (50%) clinicians would not recommend the RPM to colleagues. The proportion of clinicians who neither agreed nor disagreed was similar to those who reported disagreement and was further explored in the interview sessions.</p></sec><sec id="s3-9"><title>Interview Sessions</title><p>The interviews and focus group sessions consistently provided similar information about the RPM thus achieving thematic saturation [<xref ref-type="bibr" rid="ref30">30</xref>]. All clinicians reported a limited understanding of the RPM during its implementation and suggested that ongoing educational modules and supporting technical support would enhance the RPM program for the clinician end users. Three major themes emerged from the interviews: clinician understanding and usability constraints, patient constraints, and suggestions for improvement. Subthemes were further explored (<xref ref-type="table" rid="table4">Table 4</xref>).</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Themes and subthemes.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="top">Theme</td><td align="left" valign="top">Subthemes</td></tr></thead><tbody><tr><td align="left" valign="top">Theme 1: Clinician understanding and usability constraints</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Clinician uncertainty</p></list-item><list-item><p>Repetitive alerts</p></list-item><list-item><p>Alignment with clinician workflows</p></list-item><list-item><p>Program value</p></list-item></list></td></tr><tr><td align="left" valign="top">Theme 2: Patient constraints</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Appropriate patient enrollment</p></list-item><list-item><p>Timing of enrollment</p></list-item><list-item><p>Communication during and after enrollment</p></list-item></list></td></tr><tr><td align="left" valign="top">Theme 3: Suggestions for improvement</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Clinical champions needed</p></list-item><list-item><p>Program modifications</p></list-item><list-item><p>Information technology support for end users</p></list-item></list></td></tr></tbody></table></table-wrap></sec><sec id="s3-10"><title>Theme 1: Clinician Understanding and Usability Constraints</title><sec id="s3-10-1"><title>Overview</title><p>Theme 1 encompasses the information given to the clinicians during their RPM orientation and how they applied the application to their current workflow. Three subthemes included clinician uncertainty, repetitive alerts, alignment with clinician workflows, and program value.</p></sec><sec id="s3-10-2"><title>Subtheme: Clinician Uncertainty</title><p>The RPM was rolled out in stages starting with oncology services known to have patients with high symptom burdens. The clinicians involved in the initial rollout reported more knowledge and understanding about the RPM compared with clinicians who were involved later in the rollout. Clinicians joining later in the rollout reported having little training about the RPM. However, they reported that the increased frequency of using the RPM helped them navigate the program for addressing symptom management alerts and functionality.</p><disp-quote><p>I have only worked with it (RPM) for a couple of patients in the outpatient setting, but I get a notification (through) the portal &#x2026; to notify us that the patient has enrolled in the RPM program&#x2026;During this timeframe patients (complete) a survey every day about their symptoms and how they feel.</p><attrib>R32</attrib></disp-quote></sec><sec id="s3-10-3"><title>Subtheme: Repetitive Alerts</title><p>All clinicians reported concerns about repetitive alerts from daily patient surveys. Each day that a patient reported a symptom and generated an alert [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref10">10</xref>], clinicians called the patient to verify it and confirm if the symptom was worse, better, or the same as the previous survey. Although they could see past patient response trends in the system, this required substantial effort and did improve the patient&#x2019;s care for symptoms. When alerts were consistently reported, the clinicians used their judgment to decide when to call patients for verification.</p><disp-quote><p>There are a couple of categories that we feel were a little monotonous. ie, was (the pain/symptom) worse? If they are at stage four lung cancer, (the patient) is on treatment and they have fatigue, every day&#x2026; (the patient cannot modify) their answers, (for example) moderate fatigue; I am having trouble doing my activities of daily living, so they are clicking that every day.</p><attrib>R11</attrib></disp-quote></sec><sec id="s3-10-4"><title>Subtheme: Aligning With Clinician Workflow</title><p>Clinicians reported that before implementing the RPM, patients were instructed to call the physician&#x2019;s medical offices to report symptoms. Although none of the clinicians reported significant changes to their clinical workflows, they all raised concerns about the shift from patients calling the medical oncology office for unrelieved symptoms through a digital portal. This change made clinicians apprehensive about potentially missing symptoms reported in patient portals.</p><disp-quote><p>Before RPM, patients were not supposed to report symptoms through the portal, but a lot of patients, ended up just doing that because they were home.</p><attrib>R11</attrib></disp-quote></sec><sec id="s3-10-5"><title>Subtheme: Program Value</title><p>Clinicians reported that the RPM was of immense value to them and their patients and supported its inclusion in the organization&#x2019;s future care delivery. Patients liked that their office practice clinician proactively contacted and interacted with them after they were discharged from the hospital.</p><disp-quote><p>I do not think they (the patients) mind and love to be followed up closely, I mean my patients would love for me, a call them every day. I think patients prefer (clinicians) calling them over calling the office.</p><attrib>R41</attrib></disp-quote></sec></sec><sec id="s3-11"><title>Theme 2: Patient Constraints</title><sec id="s3-11-1"><title>Overview</title><p>The patient constraint themes involved the transition of care from the inpatient setting to RPM following discharge. Three subthemes emerged: the appropriate patient enrollment, the timing of enrollment, and communication during and after enrollment.</p></sec><sec id="s3-11-2"><title>Subtheme: Appropriate Patient Enrollment</title><p>Nurses from the discharging inpatient unit were responsible for educating patients about using RPM and program enrollment. However, office practice clinicians stated that not all patients enrolled by the discharge team were appropriate due to a lack of technical proficiency, ability, and understanding of the purpose of the RPM. Clinicians consistently reported that they should be included in RPM enrollment decisions for their patients.</p><disp-quote><p>There is a disconnect, (between enrolling the patient and educating them about the program) and sending symptoms via the portal messaging using the patient portal. The policy is that we are given two business days to answer portal messages&#x2026;clearly, we cannot do that when it is a separate message. We need to speak to that person (By phone).</p><attrib>R21</attrib></disp-quote></sec><sec id="s3-11-3"><title>Subtheme: Timing of Enrollment</title><p>Office practice clinicians reported that the time of discharge is overwhelming for patients and inpatient unit teams have limited time to prepare the patients to leave the hospital. During this study, pandemic-related social distancing restrictions prevented caregivers and family members from taking part in the discharge process, further complicated RPM enrollment.</p><disp-quote><p>The second thing that I wanted to suggest for patients wanting to quickly leave the hospital and be discharged and suddenly just get bombarded with all this information, is to discuss the RPM program the day (before) discharge.</p><attrib>R32</attrib></disp-quote></sec><sec id="s3-11-4"><title>Subtheme: Communication During and After Enrollment</title><p>Clinicians reported that a patient&#x2019;s age was not a factor in RPM enrollment, as older adults familiar with technology could engage digitally with providers. However, patients with language barriers or limited access to electronic devices needed assistance from caregivers or family members similar to findings in a prior study [<xref ref-type="bibr" rid="ref8">8</xref>]. The RPM assessments were intended to be completed during weekday work hours, from 9 AM to 5 PM Monday through Friday. Clinicians described receiving the surveys late in the day, or after hours added stress for the nursing team to address alerts.</p><disp-quote><p>We have a lot of foreign-speaking patients ---, you know it is not them who are filling out the survey ... and it may be one of their relatives or their daughter. But the daughter may not live with them ... so how do you know what is going on?</p><attrib>R11</attrib></disp-quote></sec></sec><sec id="s3-12"><title>Theme 3: Suggestions for Improvement</title><sec id="s3-12-1"><title>Overview</title><p>The Clinicians supported using RPM to sustain patient care posthospital discharge. From their perspective, 3 subthemes emerged, the need for clinical champions, technology support for end users (clinicians and patients), and specific RPM modifications.</p></sec><sec id="s3-12-2"><title>Subtheme: Clinical Champions Needed</title><p>Clinicians expressed the need for continuing education and updates on RPM improvements, infrequent use required relearning the system for each new patient. While there were few Clinical Champions during the initial rollout, additional experts would have helped them navigate the program and supported novice clinicians. They also suggested developing informative slides or videos addressing specific program issues.</p><disp-quote><p>I think nursing (clinician end-user) &#x2026; needs more education on the portal because it (the portal) is such a big part of our job. More training is needed for using (connecting) pulse ox to an iPhone (or other devices ie, Android).</p><attrib>R11</attrib></disp-quote></sec><sec id="s3-12-3"><title>Subtheme: Program Modifications</title><p>Clinicians reported that patient enrollment before hospitalization or early in their hospital admission would improve the transition from inpatient to outpatient care. They also requested allowing patients to change or clarify their symptom responses within the assessment. Frequent patient alerts were seen as potentially problematic [<xref ref-type="bibr" rid="ref31">31</xref>] and suggested that enabling patients the option to modify their assessment responses would provide more accurate symptom information to the clinical team.</p><disp-quote><p>There should be a way for them (patients) to say (respond in the survey) no changes or something&#x2026; so that we don&#x2019;t get the same exact thing (response) that we spoke to the patient yesterday---about because it&#x2019;s not realistic, that I call the patient every day to talk to them about the same time (symptom).</p><attrib>R42</attrib></disp-quote></sec><sec id="s3-12-4"><title>Subtheme: Information Technology Support for End Users</title><p>Clinicians raised concerns about the lack of integrated IT systems they use for delivering patient care. Additionally, clinicians expressed the need for greater IT support for both patients and staff. Clinicians conveyed concern about the difficulty in resolving connectivity issues and requested dedicated assistance from IT teams.</p><disp-quote><p>The patients are calling in a panic and you are trying to walk them through over the phone how to set up the device (RPM on patient&#x2019;s device ie, phone, tablet). If it was not set up correctly on discharge, or the device is just not working. (These issues) add more stress to the patient, but it also adds stress to you (the clinician) This becomes the added work.</p><attrib>R11</attrib></disp-quote></sec></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Results</title><p>This study presented the perceptions and experiences of oncology clinicians when caring for their patients using RPM after hospital discharge. Initially, clinician survey responses highlighted concerns about their understanding, perceptions, and challenges when using RPM as well as its influence on their clinical workflows. These topics were further explored in interview sessions and revealed 3 themes: clinician understanding and usability constraints, patient constraints, and suggestions for improvement. Most clinicians found the RPM easy to use and learn, allowing them to confirm the patient&#x2019;s reported symptoms during follow-up phone calls. They supported RPM&#x2019;s value for both clinicians and patients as a care delivery method in oncology practice, aligning with findings from other organizational studies using ePROs [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref36">36</xref>], as well as the challenges and limitations of addressing symptom alerts after the patient transitions from an inpatient to the home setting [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>].</p></sec><sec id="s4-2"><title>Challenges and Opportunities From the Clinical Setting</title><p>This research further emphasized multiple challenges faced by clinicians during the initial RPM roll-out. A major concern was the practice change in clinical workflows whereby patients reported symptoms through electronic portals rather than contacting the medical offices by phone. Despite this change, clinicians felt their comfort level would improve with more experience, and as RPMs aligned with their workflows [<xref ref-type="bibr" rid="ref7">7</xref>]. An opportunity to improve clinician confidence includes continuing educational tutorials from the initial RPM orientation and more technical and clinical support for both patients and clinicians. These efforts would facilitate aligning clinician workflows with clinical practice, thus leading to reduced stress and improved job satisfaction when caring for oncology patients using RPM [<xref ref-type="bibr" rid="ref7">7</xref>].</p><p>Another challenge was patient constraints and their lack of understanding of RPM, which clinicians suggested might contribute to their uncertainty in digital symptom management reporting. Some patients completed surveys late in the clinic hours making it difficult to address symptoms. In many instances, clinicians reported that family members completed the surveys instead of the patients which raised concerns about the integrity of the symptom alerts. Further research could enhance the understanding of logistical limitations involving patients and caregivers with completing postdischarge symptom assessments at home. A similar study recommended that concerns revealed by patients and caregivers postdischarge could be included in future clinical outcomes [<xref ref-type="bibr" rid="ref37">37</xref>]. Additionally, the timeframe for enrolling patients in RPM was another constraint identified by clinicians. Although older patients were comfortable using the RPM [<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref39">39</xref>], enrollment at discharge was considered suboptimal. They suggested educating patients in a relaxed environment or office practices before hospitalizations would benefit patients and improve the enrollment process.</p><p>A major opportunity for RPM improvement involves addressing repetitive alerts from the daily ePRO assessments, also identified in other ePRO studies [<xref ref-type="bibr" rid="ref23">23</xref>]. Clinicians verify all patient-reported symptom alerts. When prior symptoms are stable, these alerts could be averted to reduce their workflow burden [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. To enhance effective communication with the patients, clinicians recommended adding context about symptom changes relative to the prior day&#x2019;s ePRO assessment to improve the integrity of alerts.</p><p>The perspectives of all clinicians involved in this study expressed a need for additional resources to improve the effectiveness of RPM and their ability to clinically support it. The RPM was initially implemented using a core team of designated clinicians for addressing patient alerts. Studies of RPM cited the inclusion of core teams for this purpose which may be a preferred approach for clinicians in other studies [<xref ref-type="bibr" rid="ref42">42</xref>]. However, clinicians in this research preferred a hybrid RPM program with primary care clinicians in the clinical practices addressing alerts on weekdays and centralized after-hours and on weekends. Clinicians proposed that leaders provide consistent status updates and education about RPM functionality through tutorial videos in an accessible location. Additional technological support could improve data collection and relieve clinicians of the burden of providing technical support for patients at home [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], which is not the best use of their skills [<xref ref-type="bibr" rid="ref43">43</xref>].</p></sec><sec id="s4-3"><title>Strengths and Limitations</title><p>The consistent reports from survey responses and interviewed clinicians strengthen the study&#x2019;s findings and provide pragmatic recommendations for workflow redesign and enhancing access to care for oncology patients postdischarge [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref31">31</xref>], As a result of this study, selected modifications were implemented into practice to improve the program&#x2019;s experience for both clinicians and patients. These results provide important foundational work for future pragmatic trials and implementation science to enhance the usability and value of RPM in oncology practice.</p><p>The sample was limited to only clinicians who had experiences with at least 5 patients enrolled in the RPM, but typical for case studies [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref18">18</xref>]. They expressed strong positive or negative experiences with the RPM which may have created a selection bias. The study&#x2019;s design was multi-modal which could have included both interviewer and report biases. Clinicians were also employees of the organization and therefore specific demographics were not collected to ensure their anonymity. This study was conducted at one comprehensive cancer center, limiting the generalizability of results. However, the perspectives of clinician end users from oncology services with known symptom burdens can apply to similar RPM implementation initiatives in other organizations worldwide.</p></sec><sec id="s4-4"><title>Conclusion</title><p>The National Cancer Institute calls for studies about cancer-related interventions, which also include program effectiveness from the perspectives of both patients and clinician end users [<xref ref-type="bibr" rid="ref44">44</xref>]. This study contributes to the National Cancer Institute&#x2019;s initiatives, demonstrating that RPM is a valuable method for communicating with clinical providers and managing patient symptoms during transitions of care from inpatient to the home setting.</p></sec></sec></body><back><ack><p>The authors want to thank the clinicians who participated in this study for their insight and dedication to oncology practice.</p></ack><fn-group><fn fn-type="con"><p>AMME drafted the nursing perspective aspect of the proposal and conducted the interviews, transcribed and analyzed the interview data, and drafted the original manuscript. MBB conducted interviews with AMME, reviewed the transcript data, and edited the manuscript. RD is the principal investigator of the organizational protocol involving remote patient monitoring and reviewed and edited the manuscript. J Huang, CB, and JA are involved in providing protocol support for the daily activities of this study. CW was involved with drafting the manuscript and editing the study proposal. KSP, GK, and JM were involved with the organizational protocol and its development, and manuscript review. J Holland, RS, JC, and AB are involved with the organizational project development and review of the manuscript.</p></fn><fn fn-type="conflict"><p>RD reports grant support from the National Institutes of Health and the Emerson Collective, participation on a data safety monitoring board or advisory board with Varian Medical Systems, and stock or stock options in Roche. The remaining authors do not have conflicts of interest to declare.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">ePRO</term><def><p>electronic patient-reported outcome</p></def></def-item><def-item><term id="abb2">MSK</term><def><p>Memorial Sloan Kettering Cancer Center</p></def></def-item><def-item><term id="abb3">REDCap</term><def><p>research electronic data capture</p></def></def-item><def-item><term id="abb4">RPM</term><def><p>remote patient monitoring</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>Basch</surname><given-names>E</given-names> </name><name name-style="western"><surname>Deal</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Kris</surname><given-names>MG</given-names> </name><etal/></person-group><article-title>Symptom monitoring with patient-reported outcomes during routine cancer treatment: a randomized controlled trial</article-title><source>J Clin Oncol</source><year>2016</year><month>02</month><day>20</day><volume>34</volume><issue>6</issue><fpage>557</fpage><lpage>565</lpage><pub-id pub-id-type="doi">10.1200/JCO.2015.63.0830</pub-id><pub-id pub-id-type="medline">26644527</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Basch</surname><given-names>E</given-names> </name><name name-style="western"><surname>Deal</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Dueck</surname><given-names>AC</given-names> </name><etal/></person-group><article-title>Overall survival results of a trial assessing patient-reported outcomes for symptom monitoring during routine cancer treatment</article-title><source>JAMA</source><year>2017</year><month>07</month><day>11</day><volume>318</volume><issue>2</issue><fpage>197</fpage><pub-id pub-id-type="doi">10.1001/jama.2017.7156</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Daly</surname><given-names>B</given-names> </name><name name-style="western"><surname>Kuperman</surname><given-names>G</given-names> </name><name name-style="western"><surname>Zervoudakis</surname><given-names>A</given-names> </name><etal/></person-group><article-title>InSight care pilot program: redefining seeing a patient</article-title><source>JCO Oncol Pract</source><year>2020</year><month>10</month><volume>16</volume><issue>10</issue><fpage>e1050</fpage><lpage>e1059</lpage><pub-id pub-id-type="doi">10.1200/OP.20.00214</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Denis</surname><given-names>F</given-names> </name><name name-style="western"><surname>Basch</surname><given-names>E</given-names> </name><name name-style="western"><surname>Septans</surname><given-names>AL</given-names> </name><etal/></person-group><article-title>Two-year survival comparing web-based symptom monitoring vs routine surveillance following treatment for lung cancer</article-title><source>JAMA</source><year>2019</year><month>01</month><day>22</day><volume>321</volume><issue>3</issue><fpage>306</fpage><lpage>307</lpage><pub-id pub-id-type="doi">10.1001/jama.2018.18085</pub-id><pub-id pub-id-type="medline">30667494</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mooney</surname><given-names>KH</given-names> </name><name name-style="western"><surname>Beck</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Wong</surname><given-names>B</given-names> </name><etal/></person-group><article-title>Automated home monitoring and management of patient-reported symptoms during chemotherapy: results of the symptom care at home RCT</article-title><source>Cancer Med</source><year>2017</year><month>03</month><volume>6</volume><issue>3</issue><fpage>537</fpage><lpage>546</lpage><pub-id pub-id-type="doi">10.1002/cam4.1002</pub-id><pub-id pub-id-type="medline">28135050</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="web"><article-title>Innovation: oncology care first model: informal request for information</article-title><source>Centers for Medicare and Medicaid Services</source><year>2021</year><access-date>2024-12-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://innovation.cms.gov/files/x/ocf-informalrfi.pdf">https://innovation.cms.gov/files/x/ocf-informalrfi.pdf</ext-link></comment></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>Hassett</surname><given-names>MJ</given-names> </name><name name-style="western"><surname>Cronin</surname><given-names>C</given-names> </name><name name-style="western"><surname>Tsou</surname><given-names>TC</given-names> </name><etal/></person-group><article-title>eSyM: an electronic health record-integrated patient-reported outcomes-based cancer symptom management program used by six diverse health systems</article-title><source>JCO Clin Cancer Inform</source><year>2022</year><month>01</month><volume>6</volume><fpage>e2100137</fpage><pub-id pub-id-type="doi">10.1200/CCI.21.00137</pub-id><pub-id pub-id-type="medline">34985914</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Doolin</surname><given-names>JW</given-names> </name><name name-style="western"><surname>Berry</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Forbath</surname><given-names>NS</given-names> </name><etal/></person-group><article-title>Implementing electronic patient-reported outcomes for patients with new oral chemotherapy prescriptions at an academic site and a community site</article-title><source>JCO Clin Cancer Inform</source><year>2021</year><month>12</month><volume>5</volume><issue>5</issue><fpage>631</fpage><lpage>640</lpage><pub-id pub-id-type="doi">10.1200/CCI.20.00191</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Daly</surname><given-names>RM</given-names> </name><name name-style="western"><surname>Cracchiolo</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Huang</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Remote symptom monitoring after hospital discharge</article-title><source>JCO</source><year>2022</year><month>06</month><day>1</day><volume>40</volume><issue>16_suppl</issue><fpage>1517</fpage><lpage>1517</lpage><pub-id pub-id-type="doi">10.1200/JCO.2022.40.16_suppl.1517</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Simon</surname><given-names>BA</given-names> </name><name name-style="western"><surname>Assel</surname><given-names>MJ</given-names> </name><name name-style="western"><surname>Tin</surname><given-names>AL</given-names> </name><etal/></person-group><article-title>Association between electronic patient symptom reporting with alerts and potentially avoidable urgent care visits after ambulatory cancer surgery</article-title><source>JAMA Surg</source><year>2021</year><month>08</month><day>1</day><volume>156</volume><issue>8</issue><fpage>740</fpage><lpage>746</lpage><pub-id pub-id-type="doi">10.1001/jamasurg.2021.1798</pub-id><pub-id pub-id-type="medline">34076691</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Daly</surname><given-names>B</given-names> </name><name name-style="western"><surname>Cracchiolo</surname><given-names>J</given-names> </name><name name-style="western"><surname>Holland</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Digitally enabled transitional care management in oncology</article-title><source>JCO Oncol Pract</source><year>2024</year><month>05</month><volume>20</volume><issue>5</issue><fpage>657</fpage><lpage>665</lpage><pub-id pub-id-type="doi">10.1200/OP.23.00565</pub-id><pub-id pub-id-type="medline">38382002</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>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="ref13"><label>13</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Yin</surname><given-names>RK</given-names> </name></person-group><article-title>Case study evaluations: a decade of progress?</article-title><source>Evaluation Models: Viewpoints on Educational and Human Services Evaluation</source><year>2000</year><publisher-name>Dordrecht: Springer Netherlands</publisher-name><fpage>185</fpage><lpage>193</lpage><pub-id pub-id-type="doi">10.1007/0-306-47559-6_11</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Yin</surname><given-names>RK</given-names> </name></person-group><source>Case Study Research and Applications</source><year>2018</year><publisher-name>Sage</publisher-name></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hoon</surname><given-names>C</given-names> </name></person-group><article-title>Meta-synthesis of qualitative case studies: an approach to theory building</article-title><source>Org Res Methods</source><year>2013</year><month>10</month><volume>16</volume><issue>4</issue><fpage>522</fpage><lpage>556</lpage><pub-id pub-id-type="doi">10.1177/1094428113484969</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hollweck</surname><given-names>T</given-names> </name></person-group><article-title>Robert K. Yin. (2014). Case Study Research Design and Methods (5th ed.)</article-title><source>Can J Program Eval</source><year>2016</year><volume>30</volume><issue>1</issue><fpage>282</fpage><pub-id pub-id-type="doi">10.3138/cjpe.30.1.108</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Moss</surname><given-names>S</given-names> </name></person-group><article-title>Case studies - the YIN approach</article-title><source>Charles Darwin University</source><year>2020</year><access-date>2024-04-30</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.cdu.edu.au/files/2020-07/Introduction%20to%20case%20studies%20-%20the%20Yin%20approach.docx">https://www.cdu.edu.au/files/2020-07/Introduction%20to%20case%20studies%20-%20the%20Yin%20approach.docx</ext-link></comment></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>Ba&#x0161;karada</surname><given-names>S</given-names> </name></person-group><article-title>Qualitative case study guidelines</article-title><source>TQR</source><year>2014</year><volume>19</volume><issue>40</issue><fpage>1</fpage><lpage>25</lpage><pub-id pub-id-type="doi">10.46743/2160-3715/2014.1008</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>Sargeant</surname><given-names>J</given-names> </name></person-group><article-title>Qualitative research part II: participants, analysis, and quality assurance</article-title><source>J Grad Med Educ</source><year>2012</year><month>03</month><volume>4</volume><issue>1</issue><fpage>1</fpage><lpage>3</lpage><pub-id pub-id-type="doi">10.4300/JGME-D-11-00307.1</pub-id><pub-id pub-id-type="medline">23451297</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>Boddy</surname><given-names>CR</given-names> </name></person-group><article-title>Sample size for qualitative research</article-title><source>QMR</source><year>2016</year><month>09</month><day>12</day><volume>19</volume><issue>4</issue><fpage>426</fpage><lpage>432</lpage><pub-id pub-id-type="doi">10.1108/QMR-06-2016-0053</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Ayton</surname><given-names>D</given-names> </name></person-group><article-title>Choose your qualitative study qualitative research&#x2013;a practical guide for health and social care researchers and practitioners</article-title><source>Open Educational Resources Collective</source><year>2023</year><access-date>2024-04-17</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://oercollective.caul.edu.au/qualitative-research/chapter/__unknown__-s2/">https://oercollective.caul.edu.au/qualitative-research/chapter/__unknown__-s2/</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pirani</surname><given-names>SA</given-names> </name></person-group><article-title>Navigating the complexity of sample size determination for robust and reliable results</article-title><source>IJMRR</source><year>2024</year><volume>3</volume><issue>2</issue><fpage>73</fpage><lpage>86</lpage><pub-id pub-id-type="doi">10.56815/IJMRR.V3I2.2024/73-86</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>Schnall</surname><given-names>R</given-names> </name><name name-style="western"><surname>Cho</surname><given-names>H</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>J</given-names> </name></person-group><article-title>Health information technology usability evaluation scale (Health-ITUES) for usability assessment of mobile health technology: validation study</article-title><source>JMIR Mhealth Uhealth</source><year>2018</year><month>01</month><day>5</day><volume>6</volume><issue>1</issue><fpage>e4</fpage><pub-id pub-id-type="doi">10.2196/mhealth.8851</pub-id><pub-id pub-id-type="medline">29305343</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhou</surname><given-names>L</given-names> </name><name name-style="western"><surname>Bao</surname><given-names>J</given-names> </name><name name-style="western"><surname>Setiawan</surname><given-names>IMA</given-names> </name><name name-style="western"><surname>Saptono</surname><given-names>A</given-names> </name><name name-style="western"><surname>Parmanto</surname><given-names>B</given-names> </name></person-group><article-title>The mHealth app usability questionnaire (MAUQ): development and validation study</article-title><source>JMIR Mhealth Uhealth</source><year>2019</year><month>04</month><day>11</day><volume>7</volume><issue>4</issue><fpage>e11500</fpage><pub-id pub-id-type="doi">10.2196/11500</pub-id><pub-id pub-id-type="medline">30973342</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Harris</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>R</given-names> </name><name name-style="western"><surname>Thielke</surname><given-names>R</given-names> </name><name name-style="western"><surname>Payne</surname><given-names>J</given-names> </name><name name-style="western"><surname>Gonzalez</surname><given-names>N</given-names> </name><name name-style="western"><surname>Conde</surname><given-names>JG</given-names> </name></person-group><article-title>Research electronic data capture (REDCap)--a metadata-driven methodology and workflow process for providing translational research informatics support</article-title><source>J Biomed Inform</source><year>2009</year><month>04</month><volume>42</volume><issue>2</issue><fpage>377</fpage><lpage>381</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2008.08.010</pub-id><pub-id pub-id-type="medline">18929686</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Roller</surname><given-names>MR</given-names> </name></person-group><article-title>The in-depth interview methods: 12 articles on design and implementation</article-title><source>Roller Research</source><access-date>2024-12-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="http://rollerresearch.com/MRR%20WORKING%20PAPERS/IDI%20Text%20April%202020.pdf">http://rollerresearch.com/MRR%20WORKING%20PAPERS/IDI%20Text%20April%202020.pdf</ext-link></comment></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Creswell</surname><given-names>JW</given-names> </name><name name-style="western"><surname>Creswell</surname><given-names>JD</given-names> </name></person-group><source>Research Design: Qualitative, Quantitative, and Mixed-Methods Approaches</source><year>2014</year><publisher-name>Sage</publisher-name></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>Vandenbroucke</surname><given-names>JP</given-names></name><name name-style="western"><surname>von Elm</surname><given-names>E</given-names></name><name name-style="western"><surname>Altman</surname><given-names>DG</given-names></name><etal/></person-group><article-title>Strengthening the Reporting of Observational Studies in Epidemiology (STROBE): explanation and elaboration</article-title><source>Epidemiology (Sunnyvale)</source><year>2007</year><month>11</month><volume>18</volume><issue>6</issue><fpage>805</fpage><lpage>35</lpage><pub-id pub-id-type="doi">10.1097/EDE.0b013e3181577511</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>Tong</surname><given-names>A</given-names> </name><name name-style="western"><surname>Sainsbury</surname><given-names>P</given-names> </name><name name-style="western"><surname>Craig</surname><given-names>J</given-names> </name></person-group><article-title>Consolidated criteria for reporting qualitative research (COREQ): a 32-item checklist for interviews and focus groups</article-title><source>Int J Qual Health Care</source><year>2007</year><month>12</month><volume>19</volume><issue>6</issue><fpage>349</fpage><lpage>357</lpage><pub-id pub-id-type="doi">10.1093/intqhc/mzm042</pub-id><pub-id pub-id-type="medline">17872937</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>Cernasev</surname><given-names>A</given-names> </name><name name-style="western"><surname>Axon</surname><given-names>DR</given-names> </name></person-group><article-title>Research and scholarly methods: thematic analysis</article-title><source>J Am Coll Clin Pharm</source><year>2023</year><month>07</month><volume>6</volume><issue>7</issue><fpage>751</fpage><lpage>755</lpage><pub-id pub-id-type="doi">10.1002/jac5.1817</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>Basch</surname><given-names>E</given-names> </name><name name-style="western"><surname>Stover</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Schrag</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Clinical utility and user perceptions of a digital system for electronic patient-reported symptom monitoring during routine cancer care: findings from the PRO-TECT trial</article-title><source>JCO Clin Cancer Inform</source><year>2020</year><month>10</month><volume>4</volume><issue>4</issue><fpage>947</fpage><lpage>957</lpage><pub-id pub-id-type="doi">10.1200/CCI.20.00081</pub-id><pub-id pub-id-type="medline">33112661</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>Daly</surname><given-names>B</given-names> </name><name name-style="western"><surname>Lauria</surname><given-names>TS</given-names> </name><name name-style="western"><surname>Holland</surname><given-names>JC</given-names> </name><etal/></person-group><article-title>Oncology patients&#x2019; perspectives on remote patient monitoring for COVID-19</article-title><source>JCO Oncol Pract</source><year>2021</year><month>09</month><volume>17</volume><issue>9</issue><fpage>e1278</fpage><lpage>e1285</lpage><pub-id pub-id-type="doi">10.1200/OP.21.00269</pub-id><pub-id pub-id-type="medline">34085536</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>Daly</surname><given-names>B</given-names> </name><name name-style="western"><surname>Nicholas</surname><given-names>K</given-names> </name><name name-style="western"><surname>Flynn</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Analysis of a remote monitoring program for symptoms among adults with cancer receiving antineoplastic therapy</article-title><source>JAMA Netw Open</source><year>2022</year><month>03</month><day>1</day><volume>5</volume><issue>3</issue><fpage>e221078</fpage><pub-id pub-id-type="doi">10.1001/jamanetworkopen.2022.1078</pub-id><pub-id pub-id-type="medline">35244701</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sandhu</surname><given-names>S</given-names> </name><name name-style="western"><surname>King</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Wong</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Implementation of electronic patient-reported outcomes in routine cancer care at an academic center: identifying opportunities and challenges</article-title><source>JCO Oncol Pract</source><year>2020</year><month>11</month><volume>16</volume><issue>11</issue><fpage>e1255</fpage><lpage>e1263</lpage><pub-id pub-id-type="doi">10.1200/OP.20.00357</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Keith</surname><given-names>RE</given-names> </name><name name-style="western"><surname>Crosson</surname><given-names>JC</given-names> </name><name name-style="western"><surname>O&#x2019;Malley</surname><given-names>AS</given-names> </name><name name-style="western"><surname>Cromp</surname><given-names>D</given-names> </name><name name-style="western"><surname>Taylor</surname><given-names>EF</given-names> </name></person-group><article-title>Using the consolidated framework for implementation research (CFIR) to produce actionable findings: a rapid-cycle evaluation approach to improving implementation</article-title><source>Implement Sci</source><year>2017</year><month>02</month><day>10</day><volume>12</volume><issue>1</issue><fpage>15</fpage><pub-id pub-id-type="doi">10.1186/s13012-017-0550-7</pub-id><pub-id pub-id-type="medline">28187747</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lawrence</surname><given-names>K</given-names> </name><name name-style="western"><surname>Singh</surname><given-names>N</given-names> </name><name name-style="western"><surname>Jonassen</surname><given-names>Z</given-names> </name><etal/></person-group><article-title>Operational implementation of remote patient monitoring within a large ambulatory health system: multimethod qualitative case study</article-title><source>JMIR Hum Factors</source><year>2023</year><volume>10</volume><fpage>e45166</fpage><pub-id pub-id-type="doi">10.2196/45166PMID</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>Dowzicky</surname><given-names>PM</given-names> </name><name name-style="western"><surname>Shah</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Barg</surname><given-names>FK</given-names> </name><name name-style="western"><surname>Eriksen</surname><given-names>WT</given-names> </name><name name-style="western"><surname>McHugh</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Kelz</surname><given-names>RR</given-names> </name></person-group><article-title>An assessment of patient, caregiver, and clinician perspectives on the post-discharge phase of care</article-title><source>Ann Surg</source><year>2021</year><volume>273</volume><issue>4</issue><fpage>719</fpage><lpage>724</lpage><pub-id pub-id-type="doi">10.1097/SLA.0000000000003479</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>Melstrom</surname><given-names>LG</given-names> </name><name name-style="western"><surname>Zhou</surname><given-names>X</given-names> </name><name name-style="western"><surname>Kaiser</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Feasibility of perioperative remote monitoring of patient-generated health data in complex surgical oncology</article-title><source>J Surg Oncol</source><year>2023</year><month>01</month><volume>127</volume><issue>1</issue><fpage>192</fpage><lpage>202</lpage><pub-id pub-id-type="doi">10.1002/jso.27106</pub-id><pub-id pub-id-type="medline">36169200</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Beaney</surname><given-names>T</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>J</given-names> </name></person-group><article-title>Home oxygen monitoring and therapy: learning from the pandemic</article-title><source>Curr Opin Crit Care</source><year>2023</year><month>02</month><day>1</day><volume>29</volume><issue>1</issue><fpage>34</fpage><lpage>39</lpage><pub-id pub-id-type="doi">10.1097/MCC.0000000000001010</pub-id><pub-id pub-id-type="medline">36539965</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Handley</surname><given-names>NR</given-names> </name><name name-style="western"><surname>Schuchter</surname><given-names>LM</given-names> </name><name name-style="western"><surname>Bekelman</surname><given-names>JE</given-names> </name></person-group><article-title>Best practices for reducing unplanned acute care for patients with cancer</article-title><source>J Oncol Pract</source><year>2018</year><month>05</month><volume>14</volume><issue>5</issue><fpage>306</fpage><lpage>313</lpage><pub-id pub-id-type="doi">10.1200/JOP.17.00081</pub-id><pub-id pub-id-type="medline">29664697</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>Penedo</surname><given-names>FJ</given-names> </name><name name-style="western"><surname>Oswald</surname><given-names>LB</given-names> </name><name name-style="western"><surname>Kronenfeld</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Garcia</surname><given-names>SF</given-names> </name><name name-style="western"><surname>Cella</surname><given-names>D</given-names> </name><name name-style="western"><surname>Yanez</surname><given-names>B</given-names> </name></person-group><article-title>The increasing value of eHealth in the delivery of patient-centred cancer care</article-title><source>Lancet Oncol</source><year>2020</year><month>05</month><volume>21</volume><issue>5</issue><fpage>e240</fpage><lpage>e251</lpage><pub-id pub-id-type="doi">10.1016/S1470-2045(20)30021-8</pub-id><pub-id pub-id-type="medline">32359500</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>Coffey</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Christopherson</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Glasgow</surname><given-names>AE</given-names> </name><etal/></person-group><article-title>Implementation of a multisite, interdisciplinary remote patient monitoring program for ambulatory management of patients with COVID-19</article-title><source>NPJ Digit Med</source><year>2021</year><month>08</month><day>13</day><volume>4</volume><issue>1</issue><fpage>123</fpage><pub-id pub-id-type="doi">10.1038/s41746-021-00490-9</pub-id><pub-id pub-id-type="medline">34389787</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>Offodile</surname><given-names>AC</given-names>  <suffix>II</suffix></name><name name-style="western"><surname>Seitz</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Peterson</surname><given-names>SK</given-names> </name></person-group><article-title>Digital health navigation: an enabling infrastructure for optimizing and integrating virtual care into oncology practice</article-title><source>JCO Clin Cancer Inform</source><year>2021</year><month>12</month><volume>5</volume><issue>5</issue><fpage>1151</fpage><lpage>1154</lpage><pub-id pub-id-type="doi">10.1200/CCI.21.00111</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="web"><article-title>Division of cancer control and population sciences</article-title><source>National Cancer Institute</source><access-date>2024-05-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://cancercontrol.cancer.gov/">https://cancercontrol.cancer.gov/</ext-link></comment></nlm-citation></ref></ref-list></back></article>