TRV-2026-1235Certified recordPeer-reviewed

Artificial intelligence-assisted digital thyroid FNA cytology: Improved agreement and sensitivity for higher-risk Bethesda categories with enhanced screening efficiency

Background Accurate cytologic classification of thyroid nodules is essential for clinical management, but interobserver variability and indeterminate interpretations remain persistent challenges. The clinical feasibility of AIxTHY, a disease-specific deep-learning algorithm integrated into a digital cytology platform, was evaluated for assisting thyroid fine-needle aspiration (FNA) diagnosis using whole-slide imaging (WSI). Methods Two cytopathologists and one cytologist independently reviewed 100 archival ThinP…

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

Current reading — gain

AIxTHY-assisted digital cytology increased sensitivity for higher-risk Bethesda categories and improved agreement with expert consensus while cutting slide review time.

Current reading — problem

AI assistance reduced specificity because of increased false-positive classifications, particularly among indeterminate thyroid cases.

What this doesn’t fix

Specificity decreased with AI assistance due to false positives in indeterminate lesions, indicating need for further refinement before routine clinical use.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1235, v1: “Artificial intelligence-assisted digital thyroid FNA cytology: Improved agreement and sensitivity for higher-risk Bethesda categories with enhanced screening efficiency.” Truvace, 2026-10-01. /record/TRV-2026-1235 (accessed at citation time). sha256 f5505f9586a7b2a4…

Calibration history

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

  1. Certifiedv1f5505f9586a7…

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