TRV-2026-1692Certified recordPeer-reviewed

Conversational diagnostic artificial intelligence in ambulatory primary care: a prospective feasibility study

Background Artificial intelligence (AI)-based systems show promise for assisting primary care providers (PCPs) with patient care. We aimed to evaluate the safety and quality of clinical conversations of a patient-facing conversational AI system, which engaged in real-world urgent primary care appointments. Methods In this prospective, single-centre, single-arm feasibility study, English-speaking patients aged at least 18 years interacted with the Articulate Medical Intelligence Explorer (AMIE) up to 5 days befor…

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

Current reading — gain

In supervised pre-visit chats with AMIE, no conversation needed a safety stop, and clinicians rated the conversations favourably on most criteria. Primary care physicians who read the transcripts often found them helpful for visit preparation.

What this doesn’t fix

This was a single-centre, single-arm feasibility study with physician supervision. The authors state that further research is needed, and the evidence covers safety, conversation quality and acceptance rather than clinical outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1692, v1: “Conversational diagnostic artificial intelligence in ambulatory primary care: a prospective feasibility study.” Truvace, 2026-10-17. /record/TRV-2026-1692 (accessed at citation time). sha256 77ee6bb9161aa265…

Calibration history

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

  1. Certifiedv177ee6bb9161a…

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