TRV-2026-1951Certified recordPeer-reviewed

Establishing Diagnosis Models for Autism Spectrum Disorder With Auditory Brainstem Response Using Machine Learning Methods

This study aimed to develop and validate models built using machine learning methods for the diagnosis of autism spectrum disorder (ASD). A total of 851 children with suspected ASD were enrolled. Related features were acquired using the Autism Behavior Checklist and Auditory Brainstem Response (ABR) outcomes. The Shapley additive explanation (SHAP) values were used to explain the feature impact used in the models with the best performance. In addition, different methods were used to depict group differences. Our…

Health · Good Space — documented gain · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

Machine learning models combining Autism Behavior Checklist and auditory brainstem response features could classify children with suspected autism, with XGBoost reaching 85.9% accuracy and Waves III and V as the strongest features.

What this doesn’t fix

The source describes the pathway link as something that 'may be associated' with autistic behaviors, and the AUROC of 0.779 indicates only moderate discrimination, so the findings do not establish clinical readiness.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1951, v1: “Establishing Diagnosis Models for Autism Spectrum Disorder With Auditory Brainstem Response Using Machine Learning Methods.” Truvace, 2026-10-19. /record/TRV-2026-1951 (accessed at citation time). sha256 906c81aff5fa0bc3…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1906c81aff5fa…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1951 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.