TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0867Certified recordPeer-reviewed

Targeting GLS and LPIN2 in renal fibroblasts: potential therapeutic targets for kidney stone disease identified by integrated multi-omics analysis

Kidney stones (KS) are a common urological condition, the aetiology of which remains incompletely understood. This study aimed to investigate the key cell types involved in the formation of kidney stones and the molecular mechanisms associated with calcium metabolism. Single-cell and bulk RNA-seq datasets related to kidney stones were downloaded from the GEO database. Single-cell analysis was performed to explore the heterogeneity of kidney stones and identify differentially expressed genes (DEGs). Candidate gen…

Health · G Space — documented gain · certified 2026-08-24 · v1 · article view · machine-readable

Current reading — gain

Integrated single-cell analysis and three machine learning algorithms identified GLS and LPIN2 as upregulated key genes in kidney stones that promote fibroblast-to-myofibroblast transition, ROS production, calcium deposition and osteogenic-like differentiation, supporting a risk prediction nomogram and drug prediction.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0867, v1: “Targeting GLS and LPIN2 in renal fibroblasts: potential therapeutic targets for kidney stone disease identified by integrated multi-omics analysis.” Truvace, 2026-08-24. /record/TRV-2026-0867 (accessed at citation time). sha256 4f202974420f3f4a

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv14f202974420f

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0867 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.