TRV-2026-1446Certified recordPeer-reviewed

A Conversational Agent for Providing Personalized Preexposure Prophylaxis (PrEP) Support: Protocol for Chatbot Implementation and Evaluation

Background Chatbots have the potential to reduce barriers to preexposure prophylaxis (PrEP), including lack of awareness, misconceptions, and stigma, by providing anonymous and continuous support. However, in the context of PrEP, chatbots are still nascent; they lack personalized informational expertise, peer experiential expertise, and human-like emotional support to facilitate future PrEP uptake. These personalized and relatable forms of support are crucial for increasing engagement, influencing health decisio…

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

Current reading — gain

In a blinded comparison, a retrieval-augmented PrEP chatbot was preferred over real-world user responses and matched or beat a general LLM on empathy and tone.

Current reading — problem

The specialized RAG chatbot was rated below a general LLM on most evaluation criteria, so its added value for PrEP support remains unproven.

What this doesn’t fix

The chatbot's potential is not yet validated: expert and user feedback is still to come, and the general LLM outperformed it on most criteria.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1446, v1: “A Conversational Agent for Providing Personalized Preexposure Prophylaxis (PrEP) Support: Protocol for Chatbot Implementation and Evaluation.” Truvace, 2026-10-15. /record/TRV-2026-1446 (accessed at citation time). sha256 b174d8259228c2de…

Calibration history

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

  1. Certifiedv1b174d8259228…

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