ArticleCureus2024
Robotic Cholecystectomy Remains Safe and Effective After Regular Staffing Hours.
Article in Cureus, 2024. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 4 papers, 2 of them syntheses that pooled it.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
4 citing papers in PubMed, 2 syntheses or guidelines pooled it, 3 citations in OpenAlex.
- Technology-enhanced training in basic robotic surgical skills: a systematic review.Journal of robotic surgery · 2026Pooled it
- Current evidence and reported experiences for robot-assisted emergency general surgery: systematic review.Journal of robotic surgery · 2025Pooled it
- Establishment of a 24/7 robotic acute care surgery program at a large academic medical center.Surgical endoscopy · 2024Article
- Robotic Cholecystectomy Remains Safe and Effective After Regular Hours: A 3-Year Update.JSLS : Journal of the Society of Laparoendoscopic SurgeonsArticle
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
7 authors at 4 institutions in 1 country.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Background Robotic-assisted surgery continues to grow in popularity. Access during evenings and weekends for non-elective operations can be restricted out of safety concerns. We sought to analyze and compare outcomes of patients undergoing robotic cholecystectomy, a common urgent procedure for acute calculous cholecystitis, during regular hours versus evenings or weekends. Based on this comparison, we sought to determine if this restriction is justified. Methods We performed a retrospective analysis of 46 patients who underwent robotic cholecystectomy for acute calculous cholecystitis per 2018 Tokyo criteria by a single surgeon at a single institution between 2021 and 2022. Patients were grouped as undergoing "after-hours" cholecystectomy if the operation started at five pm or later, or anytime during the weekend (Saturday, Sunday). Demographic, perioperative, and outcome variables were tabulated and analyzed. For illustrative purposes, the data presented as median ± standard deviation were applicable. Results After-hours cholecystectomy occurred in 26 patients and regular-hours cholecystectomy occurred in 20 patients. There were no significant differences in perioperative variables between the two cohorts in terms of body mass index, age, gender, cirrhotic status, American Society of Anesthesiology score, white blood cell count, or neutrophil percentage. The after-hours group had more prior abdominal operations. There were no significant differences between the two groups in terms of operative time, estimated blood loss, or length of stay. There were no mortalities. There was one readmission in the after-hours cohort unrelated to the operation. Conclusion Robotic cholecystectomy can be safely performed on the weekends and evenings. Hospitals should make the robotic platform available during this time.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.