TRV-2026-2256Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2256 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-26T04:23:54.346576Z status: published lens: g_space sector: health headline: Exploring clinician interpretability of AI decision support systems for surgical anatomy recognition dek: Abstract Artificial intelligence (AI) decision support systems for surgery hold promise but face barriers to adoption, particularly around the interpretability of their outputs. We conducted an international cross-sectional survey of 47 neurosurgeons to evaluate perspectives on literature-derived explanatory techniques for AI-generated anatomical segmentations, using endoscopic pituitary surgery as a high-risk exemplar. Participants ranked certainty scores, certainty maps, saliency maps, scene similarity scores,… gain_title: Surgeons ranked and rated certainty scores and certainty maps highest because they match surgical decision-making, suggesting a workable route to more interpretable AI-assisted anatomical navigation. problem_title: (none) trace_subject: (none) gain_reading: Surgeons ranked and rated certainty scores and certainty maps highest because they match surgical decision-making, suggesting a workable route to more interpretable AI-assisted anatomical navigation. gain_evidence: Certainty-based techniques were consistently ranked and rated highest | certainty-based techniques appear most acceptable to surgeons for improving the interpretability of AI-assisted anatomical navigation systems problem_reading: (none) problem_evidence: (none) quick_read: An international cross-sectional survey asked 47 neurosurgeons to evaluate five ways of explaining AI-generated anatomical segmentations in endoscopic pituitary surgery. Participants ranked and rated certainty scores, certainty maps, saliency maps, scene similarity scores and nearest-neighbour illustrations, and also gave free-text feedback. The findings matter because limited interpretability is a barrier to adopting surgical AI, and the survey indicates which explanation styles clinicians find usable. What remains unknown is whether these preferences actually improve trust calibration or surgical performance, since that has not yet been tested prospectively. limitation: The study measured surgeons' stated preferences, not outcomes; the effect of these explanations on trust calibration and performance still needs prospective evaluation across surgical domains. tag: Evidence-backed gain key_points: The survey covered 47 neurosurgeons internationally, with endoscopic pituitary surgery used as a high-risk example. | Certainty scores and certainty maps were ranked and rated highest by respondents. | Certainty scores convey confidence, while certainty maps convey anatomical boundaries, which surgeons saw as fitting their decision-making. | Saliency and similarity-based methods were judged less clinically relevant and better suited to educational use. rundown: Researchers used a modified Explanation Satisfaction Scale together with ranking tasks to compare literature-derived explanatory techniques for AI anatomical segmentation. Free-text comments supplemented the quantitative ratings. Surgeons valued certainty-based approaches because they present confidence levels and anatomical boundaries in a form aligned with intraoperative decisions. Saliency maps and similarity-based methods were seen as better for teaching than for clinical use. The authors conclude that certainty-based techniques are the most acceptable option for improving interpretability, while noting that their effect on trust and performance needs prospective evaluation across surgical domains. sources: - peer_reviewed | Scientific Reports | https://doi.org/10.1038/s41598-026-74953-y | 2026-10-24 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 6722bbcdbdb479a079c53d57f36a138f88e13afeb536b21bee776f334495494b
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2256 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.
ace