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: 14 hours 18 min ago

Rare case of Bouveret syndrome

October 13, 2017 - 17:25

Laparoscopic ventral hernia repair using only 5-mm ports

October 13, 2017 - 14:35
Background

The technique of laparoscopic ventral hernia repair has been evolving since it was first described over 20 years ago. We report a new technique where polyester mesh was back loaded through a 5-mm port site, coming into contact with the skin. This avoids the need for any 10–12-mm ports.

Methods

A prospective database of laparoscopic ventral hernia repairs was examined. A single surgeon performed 344 laparoscopic ventral hernia repairs using this technique over 60 months. Follow-up was conducted by both clinical and independent phone review. Surgical technique: Laparoscopic access was achieved via a 5-mm optical port, adding two, or occasionally three, 5-mm extra ports. Hernia contents were reduced and the extra-peritoneal fat excised; 5-mm tooth graspers were placed through the lateral port and then in a retrograde fashion through the uppermost port. The port was removed, and the mesh pulled back into the abdominal cavity and positioned with a minimum of 3-cm overlap. The mesh was fixed using absorbable tacks and sutures.

Results

Most patients had primary umbilical hernias. There was one case of mesh infection due to enteric organisms. This occurred in a patient undergoing repair of a stoma site hernia, resulting from a Hartmann's procedure for perforated diverticulitis. There was no other evidence of acute or chronic mesh infection despite cutaneous contact with the mesh. In this series, there was an overall hernia recurrence rate of 2.4%.

Conclusion

Laparoscopic ventral hernia repair using only 5-mm ports is a safe, effective technique with no extra risk of infection.

Littoral cell angioma of spleen

October 12, 2017 - 08:51

Hepatic cystic echinococcosis in Australia: an update on diagnosis and management

October 12, 2017 - 08:51
Background

Echinococcosis is an uncommonly encountered zoonotic disease caused by the taeniid Echinococcus. The only endemic species in Australia, Echinococcus granulosus, forms cysts in the liver in 70% of cases. The aim of this study was to review the literature to provide an evidence-based narrative update on the diagnosis and management of hepatic cystic echinococcosis in Australia.

Methods

We reviewed the literature, utilizing multiple research databases and citation tracking. Original research and review articles examining the diagnosis and management of hydatid disease in adults, published prior to 2016 and in the English language were included in our review.

Results

Ultrasound is the gold-standard screening test, whilst computed tomography has a role in emergency presentations and screening for multi-organ involvement. Magnetic resonance imaging is the preferred second-line imaging and better demonstrates biliary involvement. Medical therapy or PAIR (percutaneous aspiration, irrigation with scolicide and re-aspiration) may be appropriate in selected cases; however, surgery remains the definitive treatment for active, large (>5 cm), symptomatic or complicated cysts. A variety of surgical techniques have been described, including conservative, radical and minimally invasive procedures. There is currently no consensus approach; surgical modality should be tailored to patient factors, relevant anatomy, local facilities and surgeons’ expertise.

Conclusion

Diagnosis and therapy in hepatic hydatid cysts have been significantly advanced by imaging, interventional radiology and surgical approaches in recent years. Surgery remains the mainstay of treatment for large, active, complicated or symptomatic hepatic hydatid cysts.

Revision gastric bypass after laparoscopic adjustable gastric band: a 10-year experience at a public teaching hospital

October 12, 2017 - 08:50
Background

In Australia, there is limited access to public revisional bariatric procedures. However, the need for such procedures is rising. We investigated the safety and efficacy of band-to-bypass procedures in our experience at a public teaching hospital over a period of 10 years.

Methods

Using a prospectively maintained bariatric surgical database, we analysed 91 consecutive planned band-to-bypass procedures from 2007 to November 2016. All patients had prior laparoscopic adjustable gastric bands removed and formation of Roux-en-Y gastric bypass, in one or two stages. Primary outcomes were 30-day complication rate and excess weight loss from 12 months. The impact of fellows as primary operators on these outcomes was assessed.

Results

Eighty-two patients met the inclusion criteria. Seventy-one (84.5%) were females. Mean age was 48.8 years (SD: 8.85). Immediate post-operative complications included six (7.3%) patients with gastrojejunostomy leak, three of whom required conversion to laparotomy, with one mortality (1.22%). Fifty-two patients had follow-up of 1 year or more (median: 2.36, range: 1–9.24). Mean excess weight loss at the end of follow-up was 52.79% (SD: 46.46). Twenty-eight (34.14%) cases were performed primarily by a fellow under the guidance of an experienced bariatric surgeon, with equivalent results.

Conclusion

Revisional band-to-bypass in the public setting is an effective but complex procedure associated with morbidity. Some risk may be ameliorated by development of selection criteria to exclude certain high-risk groups. We hope discussion amongst other bariatric groups will further refine this approach.

Effect of a See and Treat clinic on skin cancer treatment time

October 12, 2017 - 08:50
Background

Many plastic surgery departments in Australasia have experienced increasing referrals for management of skin lesions. This has driven a demand for new strategies to decrease patient waiting time and administrative costs. The aim of this study was to determine if a purpose-built See and Treat skin cancer clinic could provide a faster skin cancer treatment pathway with comparable clinical outcomes and acceptability to patients.

Methods

This was a prospective observational study of patients treated through the See and Treat clinic with a retrospective control cohort. The prospective ‘See and Treat’ cohort included a consecutive series of 106 patients, while the retrospective cohort included a consecutive series of 200 patients. Patient demographics, time from referral to surgery and operative measures were analysed. One hundred patients in the prospective cohort completed an anonymous satisfaction survey regarding their treatment.

Results

The average time from referral to surgery was reduced from 121 days in the retrospective cohort to 60 days in the See and Treat cohort (P < 0.001). Rates of complete excision of malignant and premalignant lesions were not different between the two groups, being 93% (178/191) and 91% (76/84), respectively (P = 0.609). Ninety-five percent (95/100) of patients were satisfied with their See and Treat experience overall.

Conclusion

We show that a considerable reduction in the time between referral and surgery can be achieved through a See and Treat clinic without compromise of the success of surgical treatment. Moreover, such a treatment pathway has been shown to be acceptable, and largely preferable, to patients.

Laparoscopic pancreaticoduodenectomy in Brisbane, Australia: an initial experience

October 12, 2017 - 08:50
Background

The role of minimally invasive approach for pancreaticoduodenectomy has not yet been well defined in Australia. We present our early experience with laparoscopic pancreaticoduodenectomy (LPD) from Brisbane, Australia.

Methods

Retrospective review in a prospectively collected database of patients undergoing LPD between 2006 and 2016 was performed. Patients who underwent a hybrid LPD (HLPD) mobilization approach and resection followed by open reconstruction and totally LPD (TLPD) approach were included in this study. Operative characteristics, perioperative outcomes, pathological and survival data were collected.

Results

Twenty-seven patients underwent LPD including 17 HLPD (63%) and 10 TLPD (37%) patients. HLPD patients were mostly converted to open for planned reconstruction or vascular resection. With increasing experience, more TLPDs were performed, including laparoscopic anastomoses. Median operating time was 462 min (504 min for TLPD). Median length of hospital stay was 10 days. Histology showed 21 invasive malignancies, two neuroendocrine tumours, two intraductal papillary mucinous neoplasms and two benign lesions. Median nodal harvest was 22. Margin negative resection was achieved in 84% of patients. Twenty-two percent of patients developed a Grade 3/4 complication, including 19% clinically significant pancreatic fistula. There was one perioperative mortality (4%) due to pancreatic fistula, post-operative haemorrhage and sepsis.

Conclusions

LPD is a technically challenging operation with a steep learning curve. The early oncological outcomes appear satisfactory. It remains to be determined whether the minimally invasive approach to pancreaticoduodenectomy offers benefits to patients

Review of appendicectomies over a decade in a tertiary hospital in New Zealand

October 10, 2017 - 12:21
Background

Acute appendicectomy is the most common emergency operation for patients with abdominal pain. In the last decade, computed tomography (CT) scans have increasingly been used to aid in the diagnosis in order to reduce the negative appendicectomy rate. The aim of this study was to evaluate our institution's negative appendicectomy rate and the use of pre-operative imaging.

Methods

A retrospective review was undertaken for all adult patients (>16 years), who underwent an appendicectomy on emergency basis in the years 2004, 2009 and 2014. Cases were identified from the hospital electronic theatre record system. Data were also obtained from the patients records and laboratory reports.

Results

A total of 874 patients were included, 227 in 2004, 308 in 2009 and 339 in 2014. The negative appendicectomy rate was 29.1% in 2004, 20.1% in 2009 and 19.5% in 2014 (P = 0.014). Negative appendicectomies were more common in women (P = <0.001), patients between the ages of 16–30 years (P = <0.001) and were associated with low inflammatory markers (median white cell count of 10.2, C-reactive protein of 8, P = <0.001). The use of CT scan prior to operation increased between 2009 and 2014 (34 (11.0%) versus 64 (18.9%), P = <0.001).

Conclusion

Though the number of appendicectomies being performed in our institution has increased over the last decade, the negative appendicectomy rate remains fairly static and the increased use of CT scans did not further decrease the proportion of negative appendicectomies between 2009 and 2014.

Natural history of endoscopically detected hiatus herniae at late follow-up

October 10, 2017 - 12:20
Background

Hiatus herniae are commonly seen at endoscopy. Many patients with a large hiatus hernia are endoscoped for symptoms associated with the hernia and many of these will progress to surgical treatment. However, little is known about the natural history of small to medium size hiatus herniae, and their risk of progressing to a larger hernia requiring surgery. This study aims to determine the need for subsequent surgery in these patients.

Methods

A retrospective audit of the endoscopy database at Flinders Medical Centre and the Repatriation General Hospital in Adelaide, South Australia for the 2-year period 2002–2003 was performed to identify all patients with a hiatus hernia. Patients under the age of 65 and with a sliding hiatus hernia <5 cm in length were selected for this study, and sent a questionnaire which determines the long-term (>10 years) outcome of these herniae.

Results

Small- to medium-sized hiatus herniae (<5 cm length) were found at 10% of endoscopies performed. In this group, 38% had reflux as the indication for endoscopy. 1.5% subsequently progressed to anti-reflux surgery or hiatus hernia repair. Thirty-nine percent reported being on proton pump inhibitors for symptom control. No patients required emergency surgical repair of their hiatus hernia.

Conclusion

While patients with small- to medium-sized sliding hiatus hernia commonly have symptomatic reflux, an acute problem requiring emergency surgery is unlikely over long-term follow-up.

Primary salivary gland malignancies: a review of clinicopathological evolution, molecular mechanisms and management

October 6, 2017 - 09:41

Salivary gland cancers are a complex group of tumours with variations in location, type and grade, all of which influence their biological behaviour. The understanding of salivary gland pathology has evolved at the molecular level in the last decade leading to identification of distinct entities, development of improved methods of diagnosis as well as identifying therapeutic targets for selected high-grade tumours. This article focuses on these advances and their impact on the management of primary salivary gland cancers.

Study on the time taken for patients to achieve the ability to self-care their new stoma

October 6, 2017 - 09:41
Background

Stoma formation in colorectal surgery is a recognized independent cause of prolonged hospital stay. It has been shown that preoperative stoma education and siting leads to a reduction in the length of hospital stay. Despite this, the length of time to independent stoma management and the variables that affect this has not been well studied. We conducted a prospective case series to analyse this.

Methods

A total of 107 consecutive colorectal surgery patients undergoing stoma formation at two separate large metropolitan hospitals, one private funded and the other government funded, were enrolled in a prospective case series. The primary outcome evaluated was independent management of stoma at discharge from hospital. Logistic regression analysis was performed to determine the factors associated with achieving independent stoma management at discharge.

Results

The median length of stay was 9 days (range: 4–71). In our study, 71% of patients achieved self-care at the time of discharge from hospital (76/107 patients). The median length of time taken to achieve independent management of a stoma was 7 days (interquartile range: 6–9). Factors associated with increased chance of independent management of stoma at discharge included younger age, male, preoperative siting and treatment in a public hospital.

Conclusion

Our study supports that preoperative stoma education in combination with post-operative stoma education is superior to post-operative stoma education alone. Interestingly, treatment in a private hospital is associated with a higher likelihood of failure to achieve independent stoma management at discharge. This is unexpected and not explained by our data.