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

An unsupervised machine learning analysis of biopsychosocial characteristics and treatment outcome of alcohol use disorder

Background: Alcohol Use Disorder is a heterogeneous condition where standard severity measures often fail to predict individual treatment responses. Precision medicine requires identifying distinct biopsychosocial profiles to guide targeted interventions.Objectives: To identify clinically meaningful Alcohol Use Disorder profiles using k-means clustering based on eight baseline biopsychosocial variables and validate their prognostic utility by comparing treatment outcomes.Methods: A retrospective observational st…

Health · The Trace — both readings · certified 2026-08-08 · v1 · article view · machine-readable

Current reading — gain

K-means clustering of eight biopsychosocial variables identified three distinct AUD profiles that predicted 3-month abstinence, with Late-Onset achieving 65.8% abstinence, supporting stratified front-loaded intervention.

Current reading — problem

Patients classified as Severe profile with early onset, 73.3% co-occurring psychiatric conditions and intense craving had poorer 3-month outcomes with only 36.7% abstinence and steep return to use.

What this doesn’t fix

Single-center retrospective design with 102 patients at a tertiary care center in India limits generalizability and causal inference for broader AUD populations.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0687, v1: “An unsupervised machine learning analysis of biopsychosocial characteristics and treatment outcome of alcohol use disorder.” Truvace, 2026-08-08. /record/TRV-2026-0687 (accessed at citation time). sha256 0d137fa2fdffe185

Calibration history

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

  1. Certifiedv10d137fa2fdff

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