Development of a telehealth monitoring service after colorectal surgery: A feasibility study

Abstract

AIM

To evaluate the feasibility of a text-messaging system to remotely monitor and support patients after discharge following elective colorectal surgery, within an enhanced recovery protocol.

METHODS

Florence (FLO) is a National Health Service telehealth solution utilised for monitoring chronic health conditions, such as hypertension, using text-messaging. New algorithms were designed to monitor the well-being, basic physiological observations and any patient-reported symptoms, and provide support messages to patients undergoing colorectal surgery within an enhanced recovery after surgery protocol for 30 d after discharge. All interactions with FLO and physiological readings were recorded and patients were invited to provide feedback.

RESULTS

Over a four-week period, 16 out of 17 patients used the FLO telehealth service at home. These patients did not receive telephone follow-up at three days, as per our standard protocol, unless they reported being unwell or did not make use of the technology. Three patients were readmitted within 30 d, and two of these were identified as being unwell by FLO prior to readmission. No adverse events attributable to the use of the technology were encountered.

CONCLUSION

The utilisation of telehealth in the early follow-up of patients who have undergone major colorectal surgery after discharge is feasible. The use of this technology may assist in the early recognition and management of complications after discharge.

Key Words: Telehealth, Remote monitoring, Colorectal surgery, Telephone follow up, Readmission

Core tip: Remote follow-up in the immediate post-discharge period utilising telehealth is feasible, and may help identify patients at risk of developing complications sooner, leading to earlier proactive management.

INTRODUCTION

Unplanned readmissions to hospital in the United Kingdom increased by 52% between 1992-1999 and 2007-2008[1]. The National Health Service (NHS) faces a predicted disparity between resources and patient need of nearly 30 billion by 2020-2021[2]. Introduced in 2011, the financial penalties (Payment by Results) apportioned to NHS Hospital Trusts for patients readmitted within 30 d of discharge have created concern for health care providers, who face the challenge of balancing timely discharge against the risk of early readmission.

In 2013, a telephone follow-up call was provided to patients between two and four days following discharge for patients undergoing colorectal surgery as part of an enhanced recovery after surgery (ERAS) protocol at Nottingham University Hospitals (NUH)[3]. The telephone call is designed to provide emotional and psychological support to patients following discharge, but also to identify and address any symptoms and to reiterate advice about successful recovery[3].

A number of telehealth solutions are now available for healthcare providers, including telephone follow up[3], text messaging[4,5], mobile applications[6], video conferencing[7], and automated device transmission[8]. FLO, short for “Florence”, is an NHS telehealth solution (in collaboration with Mediaburst Ltd., Manchester, United Kingdom) that has been shown to be effective in helping to manage hypertension[4], and is an acceptable modality of healthcare provision for patients[7]. The aim of this feasibility study was to investigate FLO in the early follow-up of patients who have been discharged from hospital after colorectal surgery within an ERAS protocol, and to assess patients’ perceptions of this modality of short-term follow-up.

MATERIALS AND METHODS

Setting

This evaluation was conducted at an 1100-bedded United Kingdom teaching hospital, where around 380 major colorectal procedures are performed each year within an ERAS protocol. Target lengths of stay for patients on ERAS pathways for laparoscopic and open procedures are 3 and 5 d, respectively[9].

Design

This service evaluation was conducted over a four-week period. Patients were identified at their pre-operative assessment, and provided with a brief explanation and an information leaflet about the trial. Following surgery, patients were approached 24-48 h prior to their predicted discharge date, by either the ERAS nurse or ERAS fellow, and a more detailed explanation of the service was offered (Figure 1). Those who opted in to use FLO were followed-up remotely by FLO every day for 30 d after discharge.

Figure 1 Recruitment on to Florence. FLO: Florence.

At any stage during the follow-up period, the patient would be able to text in the word “stop” and the service would terminate. Patients who declined to participate, and those who were ineligible, or failed to opt-in or utilise the telehealth service having opted in, received a telephone call from the ERAS nurse practitioner between 2 and 4 d following discharge, as per the usual care[3]. Telephone follow-up was not performed if patients had reported being well to FLO for 4 d, but subsequently opted out of the service prior to completing 30 days’ follow-up.

Patient population

Eligible participants were those who had undergone a colorectal procedure as part of an ERAS protocol, had mental capacity, were willing to participate, possessed a mobile phone and had experience with sending and receiving text messages. Patients who required reoperation or who were admitted to the intensive care or high dependency units were not invited to participate.

Ethics and consent

The Nottingham ethics committee deemed this study to be a service evaluation, and formal ethical committee review was not warranted. Informed, written consent was obtained from all patients.

Development

The algorithms were designed utilising FLO editing software. These were based on the telephone algorithms currently used by the ERAS nurse practitioner, and were categorised as well-being checks, support messages, physiological observations and self-reported symptoms. For the purposes of this evaluation, the algorithms were designed to provide automated advice.

A trial run of the algorithms was performed by clinical staff; feedback from this process allowed us to modify and streamline the algorithms. A workshop day was organised through the NHS patient and public involvement, and volunteers provided feedback on the equipment, information packs and text-messaging. Despite some of the volunteers having never sent a text message before, they could communicate proficiently with FLO after a brief tutorial.

The well-being checks followed an algorithm, outlined in Figure 2. If patients reported feeling unwell, FLO would proceed to ask the patients for more specific information, limited to the symptoms set out in Table 1. An alert would also be highlighted on the clinicians’ FLO dashboard (Figure 3) for patients reporting feeling unwell, any complications, or abnormal physiological readings. Patients who developed an alert on the FLO dashboard were telephoned by the ERAS nurse practitioner within office hours. FLO has the capability to email or text the health care professional when an alert has been triggered. For this evaluation, alert forwarding to the ERAS team was not utilised.

Table 1 Symptoms recognised by Florence.

Symptoms
Nausea and vomiting	Stoma - constipation	Fever
Urinary	Emptying stoma bag	Generally unwell
Wound appearance	Bowels - loose stools	Tired
Painful wound	Bowels - constipated	Swollen leg
Stoma - loose motion	Pain	Shortness of breath/chest pain

Figure 2 Overview of algorithm. HCP: Health care practitioner.

Figure 3 Example of heart rate dashboard.

Algorithms were programmed to respond to symptoms that patients could text in to obtain advice. Each symptom required a separate algorithm to be constructed. The list of symptoms was provided as part of an information booklet that patients received, including a brief explanation of each symptom.

Upon receipt of a symptom, FLO proceeds to ask the patient clinical questions to identify a diagnosis. If the symptoms aligned with expected self-limiting problems, reassurance was provided, otherwise, advice was sent and an alert would be created on the clinician’s FLO dashboard.

As an example, for symptoms related to bowel movements, the patients would be asked to provide Bristol Stool Scale ratings. These are plotted on the FLO online dashboard, and management options are automatically sent to patients, for example, reduce opioid intake, contact the stoma nurses or increase fluid intake.

During the first 10 d after discharge, several reminder messages were sent to patients, including the timing of removal of surgical skin clips, the importance of regular mobilisation, dietary advice, and the nature of erratic bowel movement after colonic resections. It is also possible to remind patients to take medications at specific times, for example, extended venous thro­mboembolism prophylaxis.

Lead clinicians in local primary care and in the emergency department were consulted as to the nature of the service being evaluated. It was agreed that certain “trigger” conditions should inform the patient to present either to the colorectal department, the emergency department or to the patient’s general practitioner (Table 2).

Table 2 List of diagnoses and care team responsible.

Colorectal team	Emergency department	General practitioner
Small bowel obstruction, postoperative ileus, retention of urine, hernia, surgical site infection, stoma problems, high output stoma, SIRS, fever, DVT, hypotension	Breathlessness, chest pain	Analgesia review, urinary tract infection

SIRS: Systemic inflammatory response syndrome; DVT: Deep vein thrombosis.

Implementation and information gathering

Patients were given packs consisting of: (1) Consent form; (2) generic FLO information leaflet; (3) colorectal ERAS FLO information booklet; (4) blood pressure cuff (providing blood pressure and pulse rate); (5) thermometer; and (6) evaluation forms (Likert 5-point scale[10]) included the statements: I feel comfortable using a mobile phone with FLO; I feel confident that sending my symptoms and readings to FLO makes a difference; Regular contact with FLO means I need to visit my GP less often; Using computers and text-messages to follow-up patients following discharge from hospital is beneficial; I would recommend FLO to a friend or family member; FLO is easy to use; FLO is helping me manage my own recovery better.

Patients and/or patient’s carers involved in the evaluation were shown how to perform and upload tem­perature, heart rate and blood pressure measurements to FLO and were asked to provide at least one reading per day. If they forgot to provide a reading, a text-message reminder was automatically sent by FLO to ask for this. Certain symptoms, for example, “generally unwell”, would also trigger FLO to request basic physiological readings from the patient. If readings were outside a predetermined range (which can be customised), a request was sent by FLO to repeat the readings. Depending on the readings received, advice was provided, and an alert would be created on the FLO dashboard. All communications between FLO and the patient are stored. If a patient texted in a message that was not understood by FLO, these can be seen and reviewed. This helped us to refine communications. It was also possible to send customised messages to patients and read any responses through the clinician’s dashboard.

Statistical analysis

The FLO dashboard is a web-based interface utilising 256-bit encryption. The dashboard (Figure 3) displays a list of all active patients (i.e., those who are still within their 30-d participation), and also those who have been “discharged” from the service, or had opted out. The dashboard has several tabs which display patients’ readings including: Well-being checks; basic observations; alerts generated; all support messages and any symptoms or free-text that the patient has sent.

RESULTS

Use of FLO

During the 4-wk trial period, 24 patients were approached. Twenty patients were eligible to use the service. Two patients were eligible but declined to participate. Eighteen patients agreed to trial the service, but 1 did not opt in via text message and did not participate any further. Out of the 17 who opted in, 16 reliably interacted with the service at home. The patient who did not use the service after opting in was readmitted within 24 h of discharge. At any time after 4 d, patients could opt out of the service with no further ERAS follow up.

Well-being, basic observations and symptoms

We subdivided the data into patients readmitted vs those not readmitted in Table 3. The mean follow up period is based on the number of days patients remained under FLO follow up before opting out. Patients were asked by FLO at noon daily whether they felt well or unwell. Whilst patients were opted in, the overall response rate to the well-being check was 83%, and the number of days patients were unwell in each category is demonstrated in Table 3. Abnormal observations of blood pressure, heart rate and temperature were defined according to the National Early Warning Score (NEWS)[11]. All symptoms reported by patients were recorded, including those not recognised by FLO (e.g., “anxiety shakes”). The number of symptoms reported are somewhat skewed in the readmitted group as one patient uploaded 50 symptoms (mainly due to pre-existing health conditions).

Table 3 Well-being, observations and symptoms: Readmitted vs non-readmitted.

	No. of Patients	Total follow-up period (d)	Mean follow-up (d)	No. of days unwell (%)	Abnormal observations, n (%)	Symptoms reported, n (n/d)
Not readmitted	14	390	27.9	9 (3)	21 (5)	37 (0.09)
	3	34	11.3	14 (54)	12 (18)	55 (1.62)

The numbers observed in this study are too small to draw any firm conclusions of any impact this technology could have. We did note that in the patients who were readmitted, more had uploaded abnormal observations (18% vs 5%), and reported being unwell on more of the days they were followed up for (54% vs 3%).

Patient feedback

Most patients felt that the text-messaging service was acceptable to them and patient feedback about the service is summarised in Figure 4.

Figure 4 Patient feedback. FLO: Florence; GP: General practitioner.

DISCUSSION

This investigation has demonstrated that it is feasible to develop an acceptable method of remotely monitoring patients who have undergone colorectal surgery after discharge. Using a basic telehealth solution, we designed advanced algorithms to monitor the daily well-being of patients, their physiological observations, and provided a method to respond and triage common postoperative symptoms and diagnoses. We also provided support messages for common postoperative problems. The method was feasible and acceptable to patients and reduced the number of telephone follow-up consultations required as part of our usual care.

Following discharge from hospital, patients’ care is effectively “handed back” to primary care services. However, despite the limited number of complications which can be dealt with in primary care (Table 2), there is a lack of incentive for secondary care teams to provide assistance for patients after discharge from hospital[12]. Patients discharged from hospital could thus be considered to be in “no-man’s land”. Advances in perioperative practice include strategies to reduce the magnitude and impact of surgical trauma, for example, by reducing inappropriate sympathetic response by thoracic epidural analgesia usage[13], and pre-loading patients with carbohydrate drinks to reduce postoperative insulin resistance[14]. Reducing the physiological burden that surgery places on patients permits a quicker recovery[15], reduced length of stay[16] and cost savings[17]. Although readmission to hospital may be viewed as a quality marker, the notion that patients are discharged prior to full recovery[1] more likely reflects advancements in treatment, as seen in ERAS programmes, where patients can be fit for discharge in as little as 23-48 h following major abdominal surgery[15,18].

Although no differences in readmission rates have been reported utilising ERAS pathways[19], the more serious complications, such as anastomotic leak, are reported to be diagnosed, on average, 12.7 d after surgery[20], and mortality resulting from this complication approaches 22%[21]. It is, therefore, important that signs of complications are recognised early, especially after discharge, to prevent patients from being readmitted in extremis.

When serious complications, such as anastomotic leaks, occur when patients are at home, treatment can be delayed. The use of the technology described in this trial may assist in identifying and treating complications sooner. At NUH, we have recently introduced “surgical hot clinics”, where appointments can be made by clinicians to review patients on a “very urgent” outpatient basis. Although the numbers in this feasibility trial were small, we have demonstrated that remote monitoring of patients after major abdominal surgery is possible, in what could be viewed as a “virtual ward”. Utilising a telehealth service may permit a more integrated and supportive discharge from secondary care, and could help to bridge the gap to a full primary care hand-back.

Prolonging hospital stay for patients who have apparently recovered would inevitably reduce read­missions, but this approach does not make financial sense, and exposes patients to additional risks associated with prolonged stay. Although epidemiologists have evaluated methods of predicting patients at higher risk for readmission[22], the scoring systems have not been widely adopted in United Kingdom surgical practice.

Limitations

The algorithms in the current study were designed to be automated, but we felt the system was too complex given the limitations of the technology being utilised. For example, FLO can identify key words such as “bleeding” or “blood”, and an algorithm could be created to ask specific questions about where the bleeding is coming from, how much there is, and whether it’s mixed with anything else. The FLO “brain” has limited intelligence. It is not possible to program a “yes” or “no” response for individual symptom algorithms, as FLO cannot discriminate “yes” or “no” from other symptom algorithms. If bleeding was the symptom, FLO would have to ask: (1) Where the bleeding is coming from. Responses would have to be programmed and built in to the response sent to the patient (i.e., per rectal bleeding, per stomal bleeding, wound bleeding); (2) responses then must be carefully phrased in lay language, but are limited to 144 characters; and (3) for FLO to understand the reply, only specific phrases are understood, such as “B1” for rectal bleeding, “B2” for Stoma bleeding, or “B3” for Wound bleeding, which can be confusing, particularly if patients use phones where the previous messages are not on the same screen when they type their response.

FLO in its current guise requires patients to be precise in their responses; there is no “fuzzy matching”. For example, a patient may text in “lose bowls”, meaning loose bowels. FLO would respond to this with a generic “I didn’t understand that” or “that reading is too low”. It is possible to add additional keywords to individual algorithms to pick up potential misspellings or abbreviations, but this was not done during this short trial.

Finally, using FLO in an automated manner is not feasible. We felt that to comprehensively monitor patients remotely in this manner, a clinician is required to oversee the dashboard to ensure patients were not running into problems. Conversely, we did not have to make routine telephone calls to 13 of the 17 patients who utilised the service, which usually take approximately 20 min to complete. It is possible to provide shared cross-speciality access to the FLO dashboard, but since this was a small, short-term trial, we did not provide FLO access to individual GPs or the emergency department.

FLO could be used in other surgical practice including patients being sent home with drains - for example those with biliary or pancreatic fistulas, or after breast surgery in those with seromas.

The use of a modern technology was evaluated to remotely monitor patients who have undergone major abdominal surgery after discharge from hospital. The technology as it currently exists has limitations, and is not suitable for every patient. However, its use appears to be acceptable to those who did use it, and requires further evaluation as a method to bridge the gap between primary and secondary care services.

COMMENTS

Background

Patients can be fit for discharge in as little as 23-48 h following major abdominal surgery. However, serious complications, such as anastomotic leak, are reported to be diagnosed, on average, 12.7 d after surgery. It is therefore important that signs of complications are recognised early, to prevent patients from being readmitted in extremis. The aim of this telehealth evaluation was to monitor patients in the early follow up period after discharge.

Research frontiers

Traditional follow-up after surgery included a telephone call from a nurse between 2-4 d following discharge to patients at home. This method is fairly resource-intense and does not include basic physiological parameters.

Innovations and breakthroughs

Although this evaluation was not powered to detect changes in the ability to pick up postoperative changes earlier, we have demonstrated that this method of follow-up is acceptable to patients and may form the basis of a larger study, which may incorporate newer technologies, such as the internet of things (IoT).

Applications

The evaluation of this technology demonstrates that use of telehealth in the immediate postoperative period is feasible and may help identify postoperative complications sooner. Methods arising from this evaluation may assist in future medical applications, such as devices in the IoT.

Terminology

Telehealth is the provision of healthcare remotely by means of telecom­munications technology.

Peer-review

This is a very well written article reporting an innovative approach for following patients after discharge.