Moderate evidence
Published recordHealthGood Space
More
A Machine Learning Model Based on Ultrasound Radiomics and Multi-modal Clinical Features for Predicting Lymph Node Metastasis of Papillary Thyroid Carcinoma in the Setting of Hashimoto's Thyroiditis
- Truvace record
- TRV-2026-3002raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- aca42b45c334…check it
To investigate the value of multi-modal features (ultrasound characteristics, BRAF V600E mutation, and TPO-Ab) in predicting lymph node metastasis (LNM) of papillary thyroid carcinoma (PTC) in the context of Hashimoto's thyroiditis (HT), and to construct machine learning models for individualized risk assessment. A retrospective cohort of 377 patients with pathologically confirmed PTC and concurrent HT was enrolled and divided into LNM n=186 and non-LNM n=191 groups. Preoperative ultrasound features (e.g., Minim…
The gain
In a study of 377 patients with papillary thyroid cancer and Hashimoto's thyroiditis, an XGBoost model combining ultrasound radiomics and clinical markers reached 0.879 accuracy at predicting lymph node metastasis in an independent external cohort of 107 patients.
What this doesn’t fix
The model was built from a retrospective cohort of 377 patients and checked in an external cohort of only 107 patients.
Sources
1 on file- Ultrasound in Medicine & Biologydoi:10.1016/j.ultrasmedbio.2026.10.008
Cite this record
v1Truvace Impact Record TRV-2026-3002, v1: “A Machine Learning Model Based on Ultrasound Radiomics and Multi-modal Clinical Features for Predicting Lymph Node Metastasis of Papillary Thyroid Carcinoma in the Setting of Hashimoto's Thyroiditis.” Truvace, 2026-11-17. /record/TRV-2026-3002 (accessed on the day you copy it). sha256 aca42b45c3343f42…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
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-3002 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.
ace