A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_session4fgp6v6l98666hu47afmbbpll5n5uvtf): Failed to open stream: No space left on device

Filename: drivers/Session_files_driver.php

Line Number: 177

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Failed to read session data: user (path: /var/lib/php/sessions)

Filename: Session/Session.php

Line Number: 137

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated

Filename: models/Detail_model.php

Line Number: 71

Backtrace:

File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos

File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated

Filename: helpers/my_audit_helper.php

Line Number: 8919

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace

File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

Laparoscopic pyeloplasty with concomitant pyelolithotomy. | LitMetric

AI Article Synopsis

Article Abstract

Purpose: We present our experience with laparoscopic pyeloplasty plus pyelolithotomy in patients in whom stones were not the cause of ureteropelvic junction obstruction.

Materials And Methods: A transperitoneal approach was used for laparoscopic pyeloplasty and pyelolithotomy in 19 patients (20 renal units). Before ureteropelvic junction repair stones were extracted through a small pyelotomy that was eventually incorporated into the final pyeloplasty incision. Stones in the renal pelvis were removed with rigid graspers under direct laparoscopic vision. A flexible cystoscope introduced through a port was used to extract stones in the calices. The renal pelvis was reconstructed based on the anatomy of the ureteropelvic junction.

Results: A median of 1 stone (range 1 to 28) was recovered. In 11, 8 and 1 patients the Anderson-Hynes dismembered pyeloplasty, Y-V plasty and the Heinecke Mickulicz procedure were performed, respectively. At 3 months 2 patients had residual calculi for a procedural stone-free rate of 90%. There was no evidence of obstruction in 18 of the 20 cases (90%), as confirmed by negative diuretic scan or radiological improvement of hydronephrosis. At a mean followup of 12 months (range 3 to 57) 2 additional patients had recurrent stones for an overall long-term stone-free rate of 80% (16 of 20).

Conclusions: Laparoscopic pyelolithotomy is feasible when combined with pyeloplasty. Our results are comparable to those of stone removal during open pyeloplasty or percutaneous endopyelotomy. The advantages of open surgery appear to be maintained in this minimally invasive approach.

Download full-text PDF

Source

Publication Analysis

Top Keywords

laparoscopic pyeloplasty
12
pyeloplasty pyelolithotomy
8
pyelolithotomy patients
8
ureteropelvic junction
8
renal pelvis
8
stone-free rate
8
pyeloplasty
6
laparoscopic
5
patients
5
stones
5

Similar Publications

A case of redo pyeloplasty using robot-assisted retroperitoneoscopic pyeloplasty (RARP) for failed primary laparoscopic pyeloplasty (LP) for ureteropelvic junction obstruction (UPJO) is reported. A 12-year-old boy had LP elsewhere. He was referred for management of persistent left hydronephrosis, but was managed conservatively due to minimal symptoms and stable radioisotopic renography.

View Article and Find Full Text PDF

Objectives: Previous studies on Enhanced Recovery After Surgery (ERAS) in pediatric Laparoscopic Pyeloplasty (LP) lacked clear control cases and discussed the obstacles in the implementation process. This article details the obstacles and lessons learned during the implementation of ERAS in patients with ureteropelvic junction obstruction (UPJO).

Methods: An ERAS protocol was implemented in the UPJO population undergoing LP, which included preoperative, intraoperative, and postoperative management.

View Article and Find Full Text PDF

The current study aimed to investigate the feasibility and safety of robot-assisted laparoscopic resection of the isthmus in patients with symptomatic horseshoe kidney. A retrospective analysis of clinical data from four patients with symptomatic horseshoe kidney treated between January 1, 2021 and December 31, 2023 at Guizhou Provincial People's Hospital was conducted. The main surgical procedures included robot-assisted laparoscopic resection of the isthmus, kidney fixation, pyeloplasty, and pyelolithotomy.

View Article and Find Full Text PDF

Introduction: We describe a method of robotic ureterocalicostomy (RALUC) with the Da Vinci Single Port (SP) platform and present clinical outcomes in our cohort of patients.

Materials And Methods: We retrospectively reviewed all patients undergoing RALUC with the SP platform in a single-institution, IRB-approved database between 2020-2023. Demographics, preoperative, intraoperative, and postoperative outcomes were collated.

View Article and Find Full Text PDF

A 16-year-old male presented to OPD with right-sided flank pain associated with lower urinary tract symptoms. CT scan and ultrasound findings demonstrated a 12.9 mm renal stone in the lower calyx and moderate hydronephrosis, respectively.

View Article and Find Full Text PDF

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!