Endovascular coil embolization of inferior mesenteric artery to ileal-conduit fistula: a case report
Bibliographic record
Abstract
BACKGROUND: Uretero-arterial fistulas (UAFs) are uncommon and pose a diagnostic dilemma, making them life threatening if not recognized and treated expediently. UAFs to small arteries such as a branch of the inferior mesenteric artery (IMA) are very uncommon and present a further diagnostic and treatment challenge. There should be a high index of suspicion for UAFs when intervening on patients with history of treated pelvic cancers and long-standing ureteric stents experiencing hematuria not attributable to another cause. CASE PRESENTATION: We present a case of a fistula formed between a distal branch of the IMA-superior rectal artery-and an ileal-conduit in a patient with a long-standing reverse nephroureterostomy (Hobbs) catheter presenting with abdominal pain and hematuria through the conduit. During a tube exchange, contrast injection demonstrated a fistula with the superior rectal artery, multiple ileal intraluminal blood clots, and active extravasation. The patient became tachycardic and hypotensive, actively bleeding through the ileal-conduit, prompting a massive transfusion protocol. Successful endovascular coiling of the superior rectal artery was performed with resolution of active extravasation and stabilization of the patient. The patient recovered and was discharged in stable condition 10 days later. CONCLUSIONS: Although UAFs are uncommon, our case demonstrated key predisposing risk factors to fistula development; pelvic cancer surgery, pelvic radiation, and a prolonged ureteric stent through the ileal-conduit. Typically, UAFs arise from communication with the iliac arterial system, however in this instance we have demonstrated that fistulization to other arterial vessels is also possible. Endovascular management has become the preferred method of therapy, typically involving the placement of covered stents when involving the iliac arterial system. In this instance stent grafting was not possible due to the small caliber vessel and therefore had to be embolized.
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.004 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.005 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 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".