TRV-2026-0630Certified recordPeer-reviewed

From machine learning to deep learning in attention deficit hyperactivity disorder diagnosis: A bibliometric analysis of global trends (2011-2024)

Background The diagnosis of attention deficit hyperactivity disorder (ADHD) has traditionally relied on subjective clinical interviews. Recent years have witnessed a paradigm shift toward objective, data-driven diagnostics powered by artificial intelligence (AI). Objective This study provides a comprehensive bibliometric review of AI and machine learning (ML) applications in ADHD prediction to map the field's evolution, current trends, and future directions. Methods A structured search of the Scopus database ret…

Health · The Trace — both readings · certified 2026-08-03 · v2 · article view · machine-readable

Current reading — gain

A bibliometric review of 722 papers found AI research on ADHD prediction grew exponentially, peaking in 2023, with a shift from SVMs to deep learning and EEG.

Current reading — problem

High algorithmic accuracy in AI models for ADHD has not yet translated into routine clinical utility without advances in explainability and multimodal fusion.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0630, v2: “From machine learning to deep learning in attention deficit hyperactivity disorder diagnosis: A bibliometric analysis of global trends (2011-2024).” Truvace, 2026-10-26. /record/TRV-2026-0630 (accessed at citation time). sha256 1f9a60e2c53feee5…

Calibration history

Every change to this record since certification, in the open.

  1. Revisedv21f9a60e2c53f…

    Direction audit: the gain line described the method, not an outcome; restated as the finding.

  2. Certifiedv181a27964afa6…

    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-0630 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.