TRV-2026-2415Published recordPeer-reviewed

Multiple Machine Learning Algorithms for Predicting Postoperative Residual Tumor in Pituitary Neuroendocrine Tumors

Aims To develop and validate an interpretable machine learning (ML) model for predicting radiologically confirmed postoperative residual tumor (RT) in pituitary neuroendocrine tumors (PitNETs). Methods We retrospectively analyzed 584 surgically treated patients with PitNETs from a single center, using a random 7:3 training-test split and internal cross-validation. The primary endpoint was radiologically confirmed postoperative RT, assessed using MRI obtained within 48 h after surgery and longitudinal follow-up M…

Health · Good Space (a documented gain) · first published 2026-11-07 · v1 · read the full story · raw data (JSON)

The gain

In a single-center study of 584 pituitary tumor patients, a random forest model predicted residual tumor after surgery with an AUC of 0.945 in internal testing, versus 0.715 for logistic regression.

What this doesn’t fix

Evaluation used only a single-center random split and internal cross-validation, so generalizability to other centers and future patients is unproven and internal performance may be overstated.

Sources

Your take

What do you make of this one?

Cite this record

Truvace Impact Record TRV-2026-2415, v1: “Multiple Machine Learning Algorithms for Predicting Postoperative Residual Tumor in Pituitary Neuroendocrine Tumors.” Truvace, 2026-11-07. /record/TRV-2026-2415 (accessed on the day you copy it). sha256 34845b6ef3d35c72…

Change history

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv134845b6ef3d3…

    Certified into the record

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2415 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.