aceModerate evidence
Published recordHealthGood Space
More
Predicting Inactive Disease in Juvenile Idiopathic Arthritis: A Dynamic Machine Learning Approach
- Truvace record
- TRV-2026-2455raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 8b0b510622a7…check it
Background Optimal management of juvenile idiopathic arthritis (JIA) remains challenging. The ability to predict disease progression in JIA can improve personalized treatment decisions, but few reliable predictors have been identified. Methods Using data from the Childhood Arthritis and Rheumatology Research Alliance (CARRA) Registry (years 2015-2024), we developed machine learning models to predict attainment of inactive disease in children with non-systemic JIA. We compared three structurally distinct algorith…
The gain
In a registry study of 8,093 children with non-systemic juvenile arthritis, machine learning models predicted whether a child would reach inactive disease about six months later with an AUC of 0.76 to 0.79 on an independent test set.
What this doesn’t fix
Substantial missing data affected key predictors such as ESR, CRP and morning stiffness, and the registry lacks details like specific joints involved; retrospective data reflecting reactive care limit what models can learn about treatment effects.
Sources
1 on file- Arthritis & Rheumatologydoi:10.1002/art.70394
Cite this record
v1Truvace Impact Record TRV-2026-2455, v1: “Predicting Inactive Disease in Juvenile Idiopathic Arthritis: A Dynamic Machine Learning Approach.” Truvace, 2026-11-10. /record/TRV-2026-2455 (accessed on the day you copy it). sha256 8b0b510622a7c5a6…
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-2455 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.