MétaCan
Menu
Back to cohort
Record W4293692837 · doi:10.1093/jscr/rjac388

Spontaneous perforation of pyometra—is hysterectomy required in the emergent setting? A case report and literature review

2022· article· en· W4293692837 on OpenAlexaff
Ikennah Browne

Bibliographic record

VenueJournal of Surgical Case Reports · 2022
Typearticle
Languageen
FieldMedicine
TopicEndometriosis Research and Treatment
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsMedicinePyometraHysterectomyHysteroscopyPerforationPeritonitisSurgerySeptic shockMalignancyUterine perforationSepsisUterusInternal medicine

Abstract

fetched live from OpenAlex

Spontaneous perforation of pyometra is a rare event associated with significant morbidity and mortality when diffuse peritonitis is present. While malignant lesions of the cervical tract are the most common cause of pyometra, several benign conditions can contribute to this diagnosis. Traditionally hysterectomy has been the surgical approach of choice for this clinical entity; however, in the setting of septic shock, temporizing techniques may offer the opportunity to stabilize patients and complete a thorough work up before committing to definitive resection. This report explores a case of septic shock secondary to spontaneous perforation of pyometra that was definitively managed with peritoneal lavage and wide drainage. Intraoperative hysteroscopy and uterine biopsy were performed, and no malignancy was identified on final pathology. Intraoperative hysteroscopy along with peritoneal lavage and wide drainage may reduce the morbidity and mortality associated with sepsis from spontaneous perforation of pyometra and potentially avoid unnecessary hysterectomy.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.002
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Case report · Consensus signal: Case report
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.004
Threshold uncertainty score0.008

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0000.002
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0040.004
Science and technology studies0.0010.002
Scholarly communication0.0020.003
Open science0.0020.001
Research integrity0.0030.002
Insufficient payload (model declined to judge)0.0020.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.024
GPT teacher head0.337
Teacher spread0.313 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designCase report
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations17
Published2022
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Surgical Case ReportsSame topicEndometriosis Research and TreatmentFrench-language works237,207