TRV-2026-2172Certified recordPeer-reviewed

Characterizing Cancer Symptom Experiences and Related Psychosocial Concerns Through Chinese Social Media Narratives: Computational Text Analysis

Background: Patients with cancer frequently experience complex and multidimensional symptom burdens. Standardized patient-reported outcome measures provide structured approaches to symptom assessment but may not capture the full range of symptom-related and psychosocial concerns expressed in patients' narratives. Patient-generated social media data offer a complementary source for examining how these concerns are expressed online. Objective: This study aimed to characterize cancer symptom-related narratives in C…

Health · Good Space — documented gain · certified 2026-10-22 · v1 · article view · machine-readable

Current reading — gain

LLM annotation and topic modeling of patient posts identified symptom patterns, coping strategies, and 13 experiential themes that may be underrepresented in conventional symptom assessment.

What this doesn’t fix

Differences in platform composition, uneven temporal coverage, and nonrepresentativeness of social media users limit generalizability, and the clinical utility of using such data in routine symptom assessment still requires evaluation.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2172, v1: “Characterizing Cancer Symptom Experiences and Related Psychosocial Concerns Through Chinese Social Media Narratives: Computational Text Analysis.” Truvace, 2026-10-22. /record/TRV-2026-2172 (accessed at citation time). sha256 1c82e0f20253880d…

Calibration history

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

  1. Certifiedv11c82e0f20253…

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