RELIEF: A Digital Health Tool for the Remote Self-Reporting of Symptoms in Patients with Cancer to Address Palliative Care Needs and Minimize Emergency Department Visits.

The lack of timely symptom reporting remains a barrier to effective symptom management and comfort for patients with cancer-related palliative care needs. Poor symptom management at home can lead to unwanted outcomes, such as emergency department visits and death in hospital. We developed and evaluated RELIEF, a remote symptom self-reporting app for community patients with palliative care needs. A pilot feasibility study was conducted at a large, community hospital in Ontario, Canada. Patients self-reported their symptoms each morning using validated clinical symptom measures and RELIEF would alert for worsening or severe symptoms. RELIEF alerts were monitored by palliative care nurses who would then contact patients to determine if appropriate clinical intervention could be initiated to avoid unnecessary emergency department visits. A total of 20 patients were recruited to use RELIEF for two months. Patients completed 80% of daily self-report assessments; 133 alerts were trigged, half of which required clinical intervention. No patient visited the emergency department for symptom management during the study. Clinical staff estimated five emergency department visits were avoided because of RELIEF-saving an estimated cost of over CAD 60,000. RELIEF is a feasible and acceptable method for the remote monitoring of patients with palliative care needs through regular symptom self-reporting.

A Clinical Communication Tool (Loop) for Team-Based Care in Pediatric and Adult Care Settings: Hybrid Mixed Methods Implementation Study.

BACKGROUND: Communication within the circle of care is central to coordinated, safe, and effective care; yet patients, caregivers, and health care providers often experience poor communication and fragmented care. Through a sequential program of research, the Loop Research Collaborative developed a web-based, asynchronous clinical communication system for team-based care. Loop assembles the circle of care centered on a patient, in private networking spaces called Patient Loops. The patient, their caregiver, or both are part of the Patient Loop. The communication is threaded, it can be filtered and sorted in multiple ways, it is securely stored, and can be exported for upload to a medical record. OBJECTIVE: The objective of this study was to implement and evaluate Loop. The study reporting adheres to the Standards for Reporting Implementation Research. METHODS: The study was a hybrid type II mixed methods design to simultaneously evaluate Loop's clinical and implementation effectiveness, and implementation barriers and facilitators in 6 health care sites. Data included monthly user check-in interviews and bimonthly surveys to capture patient or caregiver experience of continuity of care, in-depth interviews to explore barriers and facilitators based on the Consolidated Framework for Implementation Research (CFIR), and Loop usage extracted directly from the Loop system. RESULTS: We recruited 25 initiating health care providers across 6 sites who then identified patients or caregivers for recruitment. Of 147 patient or caregiver participants who were assessed and met screening criteria, 57 consented and 52 were enrolled on Loop, creating 52 Patient Loops. Across all Patient Loops, 96 additional health care providers consented to join the Loop teams. Loop usage was followed for up to 8 months. The median number of messages exchanged per team was 1 (range 0-28). The monthly check-in and CFIR interviews showed that although participants acknowledged that Loop could potentially fill a gap, existing modes of communication, workflows, incentives, and the lack of integration with the hospital electronic medical records and patient portals were barriers to its adoption. While participants acknowledged Loop's potential value for engaging the patient and caregiver, and for improving communication within the patient's circle of care, Loop's relative advantage was not realized during the study and there was insufficient tension for change. Missing data limited the analysis of continuity of care. CONCLUSIONS: Fundamental structural and implementation challenges persist toward realizing Loop's potential as a shared system of asynchronous communication. Barriers include health information system integration; system, organizational, and individual tension for change; and a fee structure for health care provider compensation for asynchronous communication.