63/100

Moderate evidence

GainPublished recordHealthGood Space

Evaluating Age-Related Motor System Changes Using Gait as a Functionally Relevant Marker.

Truvace record
TRV-2026-3017raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
e82059554a4c…check it

BACKGROUND AND OBJECTIVES Aging causes gait and mobility decline, which often precedes cognitive impairment and dementia. Biological "age gaps" (the difference between biological and chronological age) are traditionally measured using neuroimaging and electroencephalography, quantified gait metrics have not been used for this purpose. We hypothesize that specific gait metrics can effectively quantify biological aging and predict future cognitive impairment risk. METHODS We analyzed gait data from the Mayo Clin…

The gain

In a Mayo Clinic Study of Aging analysis of 19,637 walk trials from 5,794 people, a machine-learning 'gait age gap' predicted conversion to cognitive impairment (hazard ratio 1.07 per year), while walking speed did not (0.99).

What this doesn’t fix

The cohort was relatively homogeneous and predominantly Caucasian, so the findings need replication in diverse cohorts to assess generalizability.

Sources

1 on file
  1. Neurologydoi:10.1212/wnl.0000000000218766
    Peer-reviewed2026-12-08

Cite this record

v1

Truvace Impact Record TRV-2026-3017, v1: “Evaluating Age-Related Motor System Changes Using Gait as a Functionally Relevant Marker..” Truvace, 2026-11-18. /record/TRV-2026-3017 (accessed on the day you copy it). sha256 e82059554a4c6b3f…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1e82059554a4c…

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