Search

Objective: In 2019, the Society for Enhanced Recovery After Cardiac Surgery (ERAS-CS) published perioperative guidelines to optimize the care of patients undergoing cardiac surgery. For centers with limited capacity, a sequential approach to the implementation of the full guidelines may be more feasible. Therefore, we aimed to explore the priority of implementation of the ERAS-CS guideline recommendations from a patient and caregiver perspective. Methods: Using a modified nominal group technique, individuals who previously underwent cardiac surgery and their caregivers ranked ERAS-CS recommendations within 3 time points (ie, preoperative, intraoperative, and postoperative) and across 2 to 3 voting rounds. Final round rankings (median, mean and first quartile) were used to determine relative priorities. Results: Seven individuals (5 patients and 2 caregivers) participated in the study. Patient engagement tools (2, 2.29, and 1.50), surgical site infection reduction (2, 1.67, and 1.25), and postoperative systematic delirium screening (1, 2.43, and 1.00) were the top-ranked ERAS-CS recommendations in the preoperative, intraoperative, and postoperative time points, respectively. Conclusions: Exploration of patient and caregiver priorities may provide important insights to guide the healthcare team with clinical pathway development and implementation. Further study is needed to understand the impact of the integration of patient and caregiver values on effective and sustainable clinical pathway implementation.

BackgroundDespite the importance of their perspectives, end users (eg, patients, caregivers) are not typically engaged by academic researchers in the development of mobile health (mHealth) apps for perioperative cardiac surgery settings. ObjectiveThe aim of this study was to describe a process for and the impact of patient engagement in the development of an mHealth app that supports patient and caregiver involvement with enhanced recovery protocols during the perioperative period of cardiac surgery. MethodsEngagement occurred at the level of consultation and took the form of an advisory panel. Patients who underwent cardiac surgery (2017-2018) at St. Boniface Hospital (Winnipeg, Manitoba) and their caregivers were approached for participation. A qualitative exploration determined the impact of patient engagement on the development (ie, design and content) of the mHealth app. This included a description of (1) the key messages generated by the advisory panel, (2) how key messages were incorporated into the development of the mHealth app, and (3) feedback from the developers of the mHealth app about the key messages generated by the advisory panel. ResultsThe advisory panel (N=10) generated 23 key messages to guide the development of the mHealth app. Key design-specific messages (n=7) centered around access, tracking, synchronization, and reminders. Key content-specific messages (n=16) centered around medical terms, professional roles, cardiac surgery procedures and recovery, educational videos, travel, nutrition, medications, resources, and physical activity. This information was directly incorporated into the design of the mHealth app as long as it was supported by the existing functionalities of the underlying platform. For example, the platform did not support the scheduling of reminders by users, identifying drug interactions, or synchronizing with other devices. The developers of the mHealth app noted that key messages resulted in the integration of a vast range and volume of information and resources instead of ones primarily focused on surgical information, content geared toward expectations management, and an expanded focus to include caregivers and other family members, so that these stakeholders may be directly included in the provision of information, allowing them to be better informed, prepare along with the patient, and be involved in recovery planning. ConclusionsPatient engagement may facilitate the development of a detail-oriented and patient-centered mHealth app whose design and content are driven by the lived experiences of end users.