TRV-2026-2109Certified recordPeer-reviewed

Automatic Detection and Counting of Surgical Instruments in Surgery Using AI-Based Computer Vision Model

IntroductionCounting surgical instruments during surgical procedures is critical for ensuring patient safety. Our goal is to develop a machine learning-based computer vision algorithm to create a reliable, automated surgical instrument counting support system. We hypothesize that our machine learning algorithm, based on the YOLO (You Only Look Once) model, can effectively perform instrument counting in surgery videos, providing real-time feedback to the surgical team.MethodsYOLO is a real-time object detection a…

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

Current reading — gain

A YOLO-based model detected and counted surgical instruments in simulated open surgery video, reaching a 72.7% success rate in validation and larger instruments were classified more reliably.

Current reading — problem

The model classified small instruments such as small hemostats and needles less successfully than large ones, and it was tested only in simulation, which limits confidence for real counting safeguards.

What this doesn’t fix

The system was evaluated only in a simulated open surgical environment within a predefined region of interest, and it performed worse on small instruments, so real operating room performance remains unvalidated.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2109, v1: “Automatic Detection and Counting of Surgical Instruments in Surgery Using AI-Based Computer Vision Model.” Truvace, 2026-10-21. /record/TRV-2026-2109 (accessed at citation time). sha256 f77480c1328b970a…

Calibration history

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

  1. Certifiedv1f77480c1328b…

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