aceModerate evidence
Published recordEducationProblem Space
More
Problematic generative AI use and mental health risks among Chinese university students: latent profiles, network structure, and health literacy as a modifiable resource
- Truvace record
- TRV-2026-2559raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- abb2b16bce7c…check it
Objective Generative artificial intelligence (GenAI) has become a routine academic tool for university students, but dysregulated use may co-occur with anxiety, sleep problems, psychological distress, and impaired academic functioning. This study examined GenAI-related digital behavior as a public health issue and assessed whether health literacy and self-regulated learning were associated with lower-risk profiles. Methods A cross-sectional survey was conducted among Chinese university students from six universi…
The problem
In a survey of 1,872 Chinese university students, 14.6% fell into a high-risk dysregulated group with the worst loss of control over generative AI use, academic anxiety, sleep problems and distress, and 60.1% of them used it daily or almost daily.
What this doesn’t fix
The cross-sectional design cannot establish causation or temporal order, all measures were self-reported, and the convenience sample of Chinese university students limits generalizability.
Sources
1 on file- Frontiers in Public Healthdoi:10.3389/fpubh.2026.1910408
Cite this record
v1Truvace Impact Record TRV-2026-2559, v1: “Problematic generative AI use and mental health risks among Chinese university students: latent profiles, network structure, and health literacy as a modifiable resource.” Truvace, 2026-11-12. /record/TRV-2026-2559 (accessed on the day you copy it). sha256 abb2b16bce7cf498…
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-2559 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.