37/100

Emerging evidence

Trace: a gain and a problemPublished recordHealthThe Trace

Artificial intelligence and clinical reasoning - a qualitative study with general practice trainees in Germany

Truvace record
TRV-2026-2917raw data (JSON)
Version
v1Published
First published
Evidence type
Interviews or qualitative study
Sources
1 sourcePeer-reviewed
sha256
55cf72833f20…check it

Abstract Background General practitioners face high complexity in clinical decision-making. Large language models (LLMs) may support clinical reasoning, but their impact on decision-making processes and postgraduate medical training remains unclear. This qualitative study aims to explore General Practice (GP) trainee’s use of LLMs in clinical reasoning and their educational needs. Materials and methods GP trainees were recruited and interviewed with semi-structured interview-guide. Interviews were transcribed ve…

50Gain side

How the two sides scoreClose call

52Problem side

The gain

In interviews with 17 GP trainees in Germany, participants said AI helped augment and accelerate clinical decision-making and improved access to medical knowledge.

The problem

In interviews with 17 GP trainees in Germany, participants identified overreliance on AI-generated information and deskilling as risks, and reported no structured AI education in their training.

A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.

What the scores mean

G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.

P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.

Sources

1 on file
  1. BMC Medical Educationdoi:10.1186/s12909-026-10736-3
    Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2917, v1: “Artificial intelligence and clinical reasoning - a qualitative study with general practice trainees in Germany.” Truvace, 2026-11-14. /record/TRV-2026-2917 (accessed on the day you copy it). sha256 55cf72833f20fc27…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv155cf72833f20…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2917 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.