ANZ Journal of Surgery

  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Australia/Melbourne' for 'AEDT/11.0/DST' instead in /home/lambertn/public_html/content/modules/aggregator/aggregator.pages.inc on line 259.
Syndicate content
Wiley Online Library : ANZ Journal of Surgery
Updated: 2 hours 10 min ago

Gait speed predicts post-operative medical complications in elderly gastric cancer patients undergoing gastrectomy

December 12, 2017 - 09:42
Background

Gait speed is a clinical outcome that can measure the physical performance of elderly gastric patients. The purpose of this study was to determine the importance of gait speed in predicting post-operative morbidities in elderly patients undergoing curative gastrectomy.

Methods

We conducted a prospective study of 357 elderly patients (≥65 years old) undergoing curative gastrectomy. Preoperative gait speed was measured in a 6-m well-lit and unobstructed hallway. Patients were followed up for the post-operative clinical outcomes. Factors contributing to the post-operative morbidities were analysed using univariate and multivariate analyses.

Results

Slow gait speed was present in 95 out of 357 patients (26.61%) which was significantly associated with age (P < 0.001), gender (P = 0.016), plasma albumin (P < 0.001), American Society of Anesthesiologists grade (P = 0.012), tumour-node-metastasis grade (P = 0.007), sarcopenia (P < 0.001), handgrip (P < 0.001) and post-operative medical complications (P = 0.022). In univariate analysis, age (P = 0.015) and slow gait speed (P = 0.029) were risk factors of post-operative complications. In multivariate analysis, we found that age (P < 0.001) and slow gait speed (P = 0.029) were independent predictors of post-operative medical complications.

Conclusion

Slow gait speed is an independent predictor of post-operative medical complications in elderly patients undergoing curative gastrectomy. Those patients should be managed with appropriate perioperative nutritional support and physical exercise which can improve gait speed and reduce the risk of post-operative medical complications.

Surgical management decreases disease recurrence risk in recurrent pyogenic cholangitis

December 12, 2017 - 09:40
Background

Recurrent pyogenic cholangitis (RPC) has a high risk of disease recurrence. We present our experience with RPC and examine the factors associated with disease recurrence.

Methods

We performed a retrospective review of all patients with RPC treated at two tertiary institutions between January 1990 and December 2013. Patients with liver atrophy and/or abscess were categorized as being associated with parenchymal disease (PD).

Results

We studied 157 patients with a median age of 59.0 (interquartile range (IQR): 47.0–70.0) years and a median follow-up duration of 71.0 (IQR: 26.0–109.0) months. There were 64 (40.8%) and 93 (59.2%) patients with and without associated PD, respectively. Disease recurrence rate was 43.9% in our overall cohort through the course of follow-up. Surgical treatment was an independent prognostic factor for decreased disease recurrence risk (hazard ratio (HR) 0.40, 95% confidence interval (CI) 0.18–0.87, P = 0.021). Stratified analysis revealed that liver resection was prognostic for lower risk of disease recurrence among patients with PD (HR 0.38, 95% CI 0.15–0.94, P = 0.036), while biliary bypass was prognostic for lower risk of disease recurrence among patients without PD (HR 0.30, 95% CI 0.15–0.61, P = 0.001). The overall post-operative complication rate among surgically treated patients was 31.1%, and the presence of bilobar stones was found to be independently associated with higher odds of post-operative complications (odds ratio 3.51, 95% CI 1.26–9.81, P = 0.017).

Conclusion

Surgical treatment is associated with decreased recurrence risk in RPC, but with significant post-operative morbidity. Where surgery is deemed appropriate, patients with and without PD are likely to benefit from liver resection and biliary bypass, respectively.

Personalized stepwise vascular control during complex hepatectomy involving hepatocaval confluence

December 11, 2017 - 09:41
Background

This study introduces an innovative stepwise vascular control technique to address the high risk of massive bleeding from main hepatic veins and the retro-hepatic inferior vena cava during hepatectomy involving hepatocaval confluence.

Methods

From January 2010 to July 2016, 80 patients underwent stepwise vascular occlusion during complex liver resection involving hepatocaval confluence. Relevant clinical data were collected and compared with those obtained in parallel studies. The protocol has been registered in the Protocol Registration and Results System as protocol NCT02996006.

Results

All 80 patients underwent portal triad (PT), infra-hepatic inferior vena cava (IIVC) and supra-hepatic inferior vena cava (SIVC) preparation for occlusion in that order; PT, PT + SIVC and PT + IIVC + SIVC occlusions were performed during liver resection for six, 42 and 32 patients, respectively. The PT, IIVC and SIVC clamping times were 12.9 ± 2.5, 9.1 ± 2.1 and 5.1 ± 1.4 min, respectively. The mean blood loss was 504.1 ± 234.5 mL. Sixteen patients received blood transfusions. Haemodynamic parameters remained stable. No patients had life-threatening complications or died (Clavien-Dindo grade IV or V). Compared with other techniques used in parallel studies, this technique has the advantage of decreased blood loss in less warm ischaemia time.

Conclusion

For complex hepatectomy involving hepatocaval confluence, this newly described stepwise vascular control technique was efficacious and feasible for controlling intraoperative bleeding.

Similar length of colon is removed regardless of localization in right-sided colonic cancer surgery

December 8, 2017 - 21:30
Background

Colorectal cancers represent a heterogenous group of tumours. While left segmental colectomy is an accepted and oncologically safe practice for left-sided colonic cancer (CC), some authors suggest that limited segmental resection of right-sided cancer should be debated in order to preserve length of the resected colon. To our knowledge, caecum and ascending CC have not been analysed as different groups of tumours. The objective of this study was to assess if, retrospectively, surgical treatment of caecal cancer differed from ascending CC.

Methods

A review of all consecutive patients with right colonic resection for cancer admitted to the University hospital of Grenoble from January 2005 to August 2016 was performed. Length of resected colon was compared between caecal primary and ascending CC. Other technical and pathological aspects were analysed such as minimal invasive surgery and number of harvested lymph nodes from anatomic specimens.

Results

Among operated patients, tumour was localized pre-operatively on caecum in 110 cases and on the right ascending colon in 119 cases. Pre-operative localization had no effect on resected colon length (mean 24.5 cm, 24 ± 10.34 versus 25 cm ± 7.28, P = 0.95), on the number of harvested lymph nodes with a mean of 15 (±7.6) nodes in the caecal group versus 15.2 (±7.3) (P = 0.72). We noticed 15 cases of discordance between pre- and post-operative localization (4 versus 11, P = 0.08).

Conclusion

Length of resected colon does not differ depending on localization of tumour in our center.

Patient compliance with surveillance colonoscopy: patient factors and the use of a graded recall system

December 8, 2017 - 10:05
Background

Surveillance colonoscopy allows for the early detection and improved treatment outcomes in colorectal neoplasms but compliance rates and factors require further investigation.

Methods

This is a retrospective cohort study examining 816 patients recalled for surveillance colonoscopy at an Australian colorectal practice over a 6-month period. Primary outcome was compliance with colonoscopy within 12 months of recall. The secondary outcome of this study was to identify factors affecting compliance including patient factors and the practices’ graded recall system.

Results

A total of 715 patients (87.6%) were compliant with recall requests for repeat colonoscopy. Significantly higher compliance rates were noted with a personal history of adenomatous polyps (90.9% versus 85.6%, P = 0.025). Those with private insurance or Department of Veterans Affairs were more likely to be compliant than those publicly funded (89.0% versus 93.3% versus 79.0%, P = 0.007). No statistically significant difference in compliance was shown with a personal history of colorectal cancer, diverticular disease, perianal disease, National Health and Medical Research Council risk category, gender, time associated with the practice or the clinician. There was a significant positive correlation between the number of letters sent and compliance with recall, with 61.8% being compliant after a single letter, and a final cumulative compliance after five letters of 87.6% (R = 0.882, P = 0.048).

Conclusion

A graded recall system can achieve compliance rates as high as 87.6% compared to a single letter only achieving 61.8% compliance. A history of adenomatous polyps and insurance status were the only factors shown to result in higher recall compliance.

Post-operative telephone review is safe and effective: prospective study – Monash outpatient review by phone trial

December 5, 2017 - 16:16
Introduction

Studies have shown that post-operative telephone follow-up is satisfactory and effective. As high quality evidence is scant, we conducted a randomized controlled trial to compare it against outpatient clinic review for emergency laparoscopic appendicectomy or cholecystectomy.

Method

Patients who received emergency laparoscopic appendicectomy or cholecystectomy were eligible for this study. Once recruited, they were randomly allocated to either clinic review or telephone follow-up on discharge. Participants were reviewed at 2 weeks after operation and contacted again at 4 weeks after initial follow-up for satisfaction survey.

Results

One hundred and seventy-nine participants were recruited with one withdrawn consent and six excluded. Ninety-six underwent laparoscopic appendicectomy and 76 had laparoscopic cholecystectomy. Ninety-six attended clinic review and 76 had telephone follow-up. The two groups were similar in baseline variables. Non-attendance rate was higher for clinic review cohort (24% vs 6.6%, P = 0.002). Participants who received telephone review reported higher satisfaction level (9.31 vs 8.85, P = 0.002), and most patients prefer telephone follow-up (73.1%, P < 0.0001). No difference was detected for missed complications (P = 0.354).

Conclusion

Telephone follow-up post laparoscopic appendicectomy or cholecystectomy is safe, satisfying and effective.

Issue information - TOC

December 5, 2017 - 09:28

Medicine in small doses

December 5, 2017 - 09:28

Referees

December 5, 2017 - 09:28