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

Artificial Intelligence Can Direct Patients Toward a Complaint-specific Musculoskeletal Provider

Introduction Patients with musculoskeletal complaints often search online to identify an appropriate healthcare provider. With the increasing availability of large language models (LLMs), these artificial intelligence (AI) tools can direct patients to providers. This study evaluated the ability of LLMs to recommend appropriate providers based on representative patient musculoskeletal queries. Methods Three LLMs (ChatGPT, DeepSeek, and Gemini) were prompted with standardized musculoskeletal queries for two US cit…

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

Current reading — gain

Large language models directed patients with musculoskeletal complaints to currently practicing, specialty-appropriate providers in the requested city, with ChatGPT achieving 100% appropriateness in the tested queries.

Current reading — problem

When recommending musculoskeletal providers, LLMs at times provided inaccurate phone numbers and contact information, potentially preventing patients from reaching the appropriate clinic.

What this doesn’t fix

Findings are limited to standardized queries for two US cities and three specific LLMs, restricting generalizability to other locations, complaints, or models.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0752, v1: “Artificial Intelligence Can Direct Patients Toward a Complaint-specific Musculoskeletal Provider.” Truvace, 2026-08-14. /record/TRV-2026-0752 (accessed at citation time). sha256 38e1e49b1c6a01f0

Calibration history

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

  1. Certifiedv138e1e49b1c6a

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