46/100

Emerging evidence

ProblemPublished recordSportsProblem Space

Artificial Intelligence in the Urology Residency Match: Use, Perceptions, and Implications

Truvace record
TRV-2026-2982raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
6062aacb55c2…check it

Objective: To evaluate artificial intelligence (AI) use and perceptions among urology applicants during the 2025 to 2026 residency match cycle. Methods: An anonymous survey was distributed to all applicants at a single academic urology residency program after rank list submission and before match day. A 29-item subset of the survey was analyzed, which assessed applicant demographics, application components, AI use patterns, and perceptions regarding various AI-related issues. Both descriptive and between-group c…

The problem

In a survey of 70 urology residency applicants, 86% had encountered inaccurate or misleading AI-generated information, yet only 44% always verified AI outputs.

What this doesn’t fix

The survey covered applicants to a single academic urology program and drew 70 complete responses, a 45% response rate, so results may not represent all urology applicants.

Sources

1 on file
  1. Journal of Surgical Educationdoi:10.1016/j.jsurg.2026.104254
    Peer-reviewed2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-2982, v1: “Artificial Intelligence in the Urology Residency Match: Use, Perceptions, and Implications.” Truvace, 2026-11-17. /record/TRV-2026-2982 (accessed on the day you copy it). sha256 6062aacb55c2a516…

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. Publishedv16062aacb55c2…

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