TRV-2026-1570Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1570 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-16T10:42:07.265185Z status: published lens: g_space sector: health headline: Machine Learning Prediction of Anterior Open-Bite Development After Stabilization Splint Treatment in Temporomandibular Disorder dek: Objectives To develop interpretable machine learning (ML) models for risk stratification of clinically meaningful anterior overbite decrease after stabilization splint therapy in temporomandibular disorder (TMD) patients, and to compare ML performance with conventional logistic regression. Materials and methods This retrospective cohort included 87 TMD patients treated with stabilization splints, physical therapy, and pharmacologic therapy. Thirty-five pre-treatment cephalometric and demographic features were us… gain_title: Interpretable machine learning on pre-treatment cephalometric data separated higher-risk from lower-risk TMD patients better than logistic regression, which could support counseling and closer monitoring. problem_title: (none) trace_subject: (none) gain_reading: Interpretable machine learning on pre-treatment cephalometric data separated higher-risk from lower-risk TMD patients better than logistic regression, which could support counseling and closer monitoring. gain_evidence: support individualized counseling and closer monitoring for patients at higher risk of open-bite development problem_reading: (none) problem_evidence: (none) quick_read: Researchers built machine learning models using 35 pre-treatment cephalometric and demographic features from 87 temporomandibular disorder patients. All had been treated with stabilization splints, physical therapy and medication. The models were trained to flag patients whose anterior overbite later decreased in a clinically meaningful way. The result matters because splint therapy can lead to open-bite development, and an early risk flag could shape how patients are counseled and followed. Discrimination was moderate, the sample was small and retrospective, and the models could not forecast the exact amount of bite change, so clinical use would need further validation. limitation: Regression models had near-zero or negative cross-validated R2 values, so exact overbite change could not be predicted from pre-treatment cephalometrics alone. The cohort was also small and retrospective. tag: Evidence-backed gain key_points: In fivefold cross-validation, XGBoost reached an AUC of 0.734, against 0.611 for conventional logistic regression. | With SMOTE oversampling, a random forest reached a comparable AUC of 0.735 and improved sensitivity. | SHAP analysis ranked pre-treatment overbite, ramus height, upper occlusal plane to SN angle, sella-to-condylion distance and condylar positional indices among the most influential predictors. | Regression models for the exact magnitude of overbite change had near-zero or negative cross-validated R2 values. rundown: The study was a retrospective cohort of 87 patients. The primary outcome was overbite difference, defined as post-treatment minus pre-treatment overbite. Patients were then labeled as Decrease or not for classification. Classification performance was best with XGBoost, and the random forest with SMOTE matched its AUC while improving sensitivity. SHAP was used to make the models interpretable and to rank which baseline measures drove predictions. Regression analyses showed that baseline variables alone could not estimate how much the overbite would change. The authors conclude the models support risk stratification, not precise quantitative prediction. sources: - peer_reviewed | Clinical and Experimental Dental Research | https://doi.org/10.1002/cre2.70447 | 2026-10-01 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 9c4e455e8eb57d7178eda8a75269d470c53fb21381d07a629f1ad2ed238d2c93
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1570 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace