z-logo
Premium
Postoperative emesis after laparoscopic pyloromyotomy in infantile hypertrophic pyloric stenosis
Author(s) -
Castellani C,
Peschaut T,
Schippinger M,
Saxena AK
Publication year - 2014
Publication title -
acta paediatrica
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.772
H-Index - 115
eISSN - 1651-2227
pISSN - 0803-5253
DOI - 10.1111/apa.12460
Subject(s) - pyloromyotomy , medicine , hypertrophic pyloric stenosis , myotomy , pyloric stenosis , surgery , reflux , pediatrics , pylorus , achalasia , stomach , esophagus , disease
Aim This study aimed to determine the causes of postoperative emesis ( PE ) in neonates with infantile hypertrophic pyloric stenosis ( IHPS ) after laparoscopic pyloromyotomy ( LP ). Methods Retrospective review of the hospital database for infants with IHPS managed between 2000 and 2010 was performed. Relevant data were collected from the clinical records in the Medocs ® system and used for statistical analysis. Results During the 10‐year period, 95 patients with IHPS were identified and 43 (36 boys and seven girls) fulfilled the inclusion criteria. PE occurred in 21 infants (48.8%), of which nine presented with manifestations of enteric infections, with confirmed diagnosis in four. PE was significantly higher in the fast track feeding protocol ( FTFP ) group 12/15 compared with the conventional slow feeding protocol ( CSFP ) group 8/21 (p  =  0.019). Gastro‐oesophageal reflux ( GER ) confirmed by 24‐h impedance monitoring was responsible for PE in three. Operative revision for suspected incomplete pyloromyotomy was performed in five infants. However, incomplete myotomy could only be confirmed in two infants during surgery. Conclusion Postoperative emesis in IHPS after LP requires careful evaluation as it can be a result of enteric viral infections, aggressive feeding protocols or GER . Decisions to perform reoperations for incomplete myotomy after LP due to PE are challenging.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here