Successful Conservative Treatment of Ovulation-Related Hemoperitoneum in a Patient With Congenital Hypofibrinogenemia: A Case Report and Review of Literature
Bibliographic record
Abstract
Intraperitoneal bleeding provoked by rupture of an ovarian follicle at ovulation or a corpus-luteum-cyst is not uncommon among women of reproductive-age. Usually, this is minimal and passes unnoticed. Massive hemoperitoneum is rare and is commonly associated with an underlying pathology. Patients with coagulation disorders or receiving anticoagulation therapy are exceptionally prone to develop massive hemoperitoneum that could at times be life-threatening if not identified and treated early. Very few cases of ovulation-related massive hemoperitoneum among afibrinogenemic/hypofibrinogenemic patients were reported to the literature. We present a case of congenital hypofibrinogenemia who presented with acute abdominal pain due to massive hemoperitoneum identified on ultrasonography. As the patient continued to be hemodynamically stable, on close monitoring of vital signs and serial hematologic parameters, conservative management with fresh frozen plasma (FFP) was started. This treatment modality was successful in inhibiting bleeding and ameliorating the clinical condition. The possibility of coagulation defects should be entertained in the differential diagnosis of acute abdomen with massive hemoperitoneum especially when no identifiable direct cause could be elicited. Conservative treatment aiming at conserving ovarian integrity and function has been successful in the management of cases with afibrinogenemic/hypofibrinogenemic and other bleeding disorders, thereby averting the need for surgical intervention. It should be the modality of choice in hemodynamically stable patients. Optimal management can be attained through careful clinical assessment and close follow-up by a multidisciplinary team including gynecologists, hematologists, surgeons and intensive care specialists. Ways to prevent recurrence should be accurately introduced to patients. J Clin Gynecol Obstet. 2020;9(4):112-118 doi: https://doi.org/10.14740/jcgo628
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".