70/100

Moderate evidence

GainPublished recordHealthGood Space

Exploring the Potential of Parent Report for Autism/Developmental Screening at the 18-Month Visit

Truvace record
TRV-2026-1218raw data (JSON)
Version
v2Revised
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
ff1680c0cc7f…check it

Purpose To develop optimal algorithms of parent-administered items to improve the detection of autism and other developmental disorders at the 18-month visit. Methods Parents of 11,878 children aged 16-20 months completed the M-CHAT-R/F ™ , Q-CHAT-10-O, and ASQ-3 R at scheduled 18-month pediatric visits via an online system. Ninety-six children with positive screens and 314 matched controls completed additional items, including the POSI; items from the FYI and POEM data banks, and the MacArthur-Bates Communicati…

The gain

In a test on 202 children, a parent-report model using vocabulary and joint attention items reached over 0.7 sensitivity and specificity for autism and developmental delay, about twice the sensitivity of M-CHAT-R/F for autism.

What this doesn’t fix

Model training relied heavily on synthetic data generated from a small authentic subset and was evaluated on a limited holdback sample, constraining generalizability.

Sources

1 on file
  1. Peer-reviewed2026-09-28

Cite this record

v2

Truvace Impact Record TRV-2026-1218, v2: “Exploring the Potential of Parent Report for Autism/Developmental Screening at the 18-Month Visit.” Truvace, 2026-11-04. /record/TRV-2026-1218 (accessed on the day you copy it). sha256 ff1680c0cc7f9b4b…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2ff1680c0cc7f…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Publishedv1d2c17dd89898…

    Certified into the record

Check this record hasn’t been altered

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

Download any version from /api/record/TRV-2026-1218 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.