TRV-2026-1046Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1046 version: 1 kind: certified reason: Certified into the record timestamp: 2026-09-10T06:05:33.630877Z status: published lens: trace sector: health headline: Stakeholder perspectives on artificial intelligence in schizophrenia care dek: Background Artificial intelligence (AI) is explored as a tool to expand access to mental health care, offering support and self-disclosure. To date, the perspectives of individuals with schizophrenia on AI have been absent from the medical literature. This exploratory study represents an effort to report schizophrenia patient perspectives on AI chatbots through a focus group. Methods We conducted an exploratory, cross-sectional, qualitative study using semi-structured focus groups at a large academic health cent… gain_title: Participants with schizophrenia recognized an AI companion as a potentially accessible source of support between clinical visits. problem_title: Participants identified trust as the central barrier to using an AI companion, driven by privacy concerns and vulnerabilities specific to schizophrenia. trace_subject: use of a hypothetical AI companion tool for people with schizophrenia spectrum disorders gain_reading: Participants with schizophrenia recognized an AI companion as a potentially accessible source of support between clinical visits. gain_evidence: 'Available When No One Else Is', reflecting participants' recognition of AI as a potentially accessible source of between-visit support problem_reading: Participants identified trust as the central barrier to using an AI companion, driven by privacy concerns and vulnerabilities specific to schizophrenia. problem_evidence: 'How Can I Trust It?' highlighting trust as the central barrier, shaped by privacy concerns and schizophrenia-specific vulnerabilities | AI is perceived as both a promising adjunct to care and a potential risk in schizophrenia quick_read: Researchers conducted exploratory focus groups at a large academic health center in New York City with 17 patients with schizophrenia spectrum disorders, 7 caregivers, and 4 providers to discuss a hypothetical AI companion tool. Thematic analysis identified five themes about accessibility, uncertainty about role, trust, supplementing human care, and limiting use to low-risk support. The findings matter because perspectives of people with schizophrenia have been absent from medical literature on AI mental health tools, yet this group faces specific privacy and trust vulnerabilities. Uncertainty remains about whether perceived acceptability would translate into safe, effective use outside this small exploratory sample and single-site context. limitation: Findings are exploratory and based on a small, single-site qualitative sample, limiting generalizability beyond this New York City academic center. tag: Dual reading key_points: Focus groups included 17 patients with schizophrenia spectrum disorders, 7 caregivers, and 4 providers. | Discussions explored familiarity with AI, privacy, and perceived utility of a hypothetical AI companion tool. | Theme 'A Tool, Not a Therapist' emphasized AI was acceptable only as a supplement to, not a replacement for, human care. | Theme 'Keep It Low-Risk' limited acceptable uses to supportive functions. rundown: The study used semi-structured focus groups and thematic analysis of transcripts to elicit views on familiarity with AI, privacy, and utility. Five themes emerged, including uncertainty captured as 'What Would It Do?' and a preference for low-risk supportive functions. Authors conclude implementation should emphasize transparency, trust, and clear boundaries, with AI designed to support, not replace, existing care, reflecting the 'A Tool, Not a Therapist' theme. sources: - peer_reviewed | Psychological Medicine | https://doi.org/10.1017/s0033291726105728 | 2026-09-09 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 582765e2b7a6a72de6237a3d45f7e6dbadc604e1df40f69a0591c91b3d6e16fc
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1046 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.
ace