Database
TGAge: A Phenotypic Aging Clock Based on Tabular Foundation Models and the Gompertz Law for Assisted Living Facility Residents
arXiv stat.ML0 views
arXiv:2610.32994v1 Announce Type: cross Abstract: Biological age captures overall health status beyond chronological age, yet existing biological aging clocks are difficult to apply to assisted living facility (ALF) residents due to scarce epigenetic data. We propose TGAge, a second-generation phenotypic aging clock that estimates risk-equivalent biological age from routinely collected clinical measurements. TGAge employs a tabular foundation model to predict all-cause mortality risks over discrete time-to-death intervals and converts the resulting mortality-risk ratio into biological age acceleration via the Gompertz law. We develop and evaluate TGAge on a large cohort of ALF residents curated from a proprietary, multi-state long-term care database. TGAge outperforms clinical indices and established biological aging clocks in survival prediction. Moreover, TGAge-derived age acceleration is significantly associated with multiple aging-related comorbidities. These findings support TGAge as a practical, interpretable, and highly predictive biological aging clock for vulnerable ALF populations using only routinely collected clinical measurements.
Source:https://arxiv.org/abs/2610.32994PreviousGoCo: structure-guided conformal calibration for error-controlled Gene Ontology annotation releaseNextNot All Mislabels Are Equal: Efficient Task-Aware Auditing with Confidence Sequences
Related posts
How to upgrade Postgres in Docker to 18, and be ready for 19: dump and restore or pg_upgrade --link
0dev.to Docker
Docker Compose: Run Your App and Its Dependencies Together
0dev.to Docker
Show HN: Vaire, Self-Hosting Postgres Through the One Glorious CLI
0Hacker News Show
Gabriele Bartolini: CloudNativePG reaches CNCF Incubation: another rung on the ladder
0Planet PostgreSQL
pandas chunks fixed my memory error, then quietly broke my averages
0dev.to
Postgres LISTEN/NOTIFY vs Redis Pub/Sub: Latency, Write Cost and Failure Cases, Tested
0dev.to Node