Moderate evidence
Published recordHealthGood Space
More
Beyond chronological age: uncovering disease-dependent variability in AI-driven pediatric bone age assessment
- Truvace record
- TRV-2026-2966raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 0a41c1c522a0…check it
Objectives To assess performance and agreement of a commercial artificial intelligence (AI) tool relative to routine pediatric radiologists' bone age assessments in a large pediatric cohort, with focus on different groups of growth disorders. Materials and methods One thousand five hundred sixteen anterior-posterior hand radiographs of pediatric patients (50.6% boys, mean age 10.84 ± 3.66 years) were retrospectively analyzed using the AI tool BoneAge. AI results were compared with board-certified pediatric radio…
The gain
In a retrospective study of 1,516 children's hand X-rays, the BoneAge AI tool differed from pediatric radiologists' bone age readings by a mean of 6.4 months, with correlation of 0.980 and intraclass correlation above 0.9.
What this doesn’t fix
The study was retrospective and compared the AI with radiologists' routine reports, and the orthopedic (n = 152) and oncologic (n = 185) subgroups were small relative to the genetic/neuroendocrine group (n = 1,179).
Sources
1 on file- Insights into Imagingdoi:10.1186/s13244-026-02477-0
Cite this record
v1Truvace Impact Record TRV-2026-2966, v1: “Beyond chronological age: uncovering disease-dependent variability in AI-driven pediatric bone age assessment.” Truvace, 2026-11-16. /record/TRV-2026-2966 (accessed on the day you copy it). sha256 0a41c1c522a0fc9c…
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-2966 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