HOSPITAL PILOT

AI Surgical Consumables Counting System

IN PROGRESS · UNITED KINGDOM

iCount is an AI-assisted surgical consumables counting system being tested through a UK hospital pilot. The app analyses captured images to identify and count visible consumables, compares the detected count with the expected count recorded by staff, and presents the result for human confirmation or correction.

The system is being built to support count verification. It does not replace the established manual count, make autonomous clinical decisions or provide a result that can be accepted without staff review.

Discuss Your Pilot
iCount pilot-app safety disclosure explaining that AI-assisted counts require staff verificationiCount pilot-app screen for recording the expected surgical consumables count
Authentic supplied pilot-app screenshot showing the safety disclosure. Hospital pilot in progress; human verification remains required.
On-device and offline
AI processing
Android APK/AAB and iOS TestFlight
Supported platforms
Staff confirmation or correction required
Human role
Stored locally in the app/on the device
Current data location
Human verification required: Every result must be reviewed and confirmed or corrected by an authorised staff member. iCount is a pilot system in progress and is not presented as clinically validated or ready for clinical reliance.

Clinical-content note: Some supplied pilot-app screenshots show used swabs with visible red staining. They do not show patient identity or procedure imagery.

iCount

Healthcare AI / Surgical Safety / Medical Technology

AI Surgical Consumables Counting System

Hospital pilot / In progress
Project type
AI-assisted surgical consumables count verification app
Location
United Kingdom
AI processing
On-device and offline
Supported platforms
Android APK/AAB and iOS TestFlight
Human role
Staff confirmation or correction required
Current data location
Stored locally in the app/on the device
Problem and Context

Supporting a Manual, Safety-Critical Count

Surgical consumables are counted manually before, during and after procedures. Staff must record expected quantities and check that the count is complete.

iCount is being developed as an additional visual count-verification tool. It uses image analysis to detect visible supported items and compare the result with the expected count entered in the app. Any displayed result remains subject to staff review.

The pilot is exploring whether this workflow can provide useful count information for human verification. It is not testing the removal of the manual count or the transfer of clinical responsibility to an AI system.

iCount pilot-app screen for recording the expected surgical consumables count
Authentic supplied pilot-app screenshot showing expected-count entry before image analysis.
What We Are Testing

What We Are Testing in the Hospital Pilot

The hospital pilot is testing an AI-assisted workflow in which staff record an expected count, capture images, review detected items and confirm or correct the result in the app.

  1. 01

    whether supported consumables can be identified in captured test images;

  2. 02

    how detected quantities can be compared with the expected count recorded by staff; and

  3. 03

    how staff can review, confirm or correct the displayed result.

These are pilot objectives, not achieved clinical outcomes. The available evidence does not establish clinical validation, safety performance, workflow improvement or readiness for clinical reliance.

Documented Six-Step Workflow

How the Pilot Workflow Operates

Step 01

Record the expected count

A staff member records the expected quantity of supported surgical consumables in the app.

Step 02

Capture images during or after the procedure

The user uses the app’s camera workflow to capture images of the consumables during or after the procedure.

Step 03

Analyse the image

The app processes the captured image using the on-device ONNX model.

Step 04

Identify and count visible items

The model identifies and counts visible supported consumables in the image. Detection is limited by the model, image conditions, item visibility and the supported item classes. No guarantee is made that every item will be detected.

Step 05

Compare the detected and expected counts

The app compares the detected count with the expected count previously recorded by staff.

Step 06

Show the result for confirmation or correction

The app displays the comparison for the user to review. The user must confirm or correct the result in the app. The exact confirmation and correction interaction is not fully documented.

Workflow Boundary The displayed comparison is decision-support information for staff review. It is not an autonomous clinical decision and does not replace the established manual count or other required clinical procedures.

Supported Items

Items Currently Included

The current app work covers these documented item types:

01Spongetapes
02Raytecs
03clips
04trays

The listed item types do not represent all surgical consumables. Equal performance across item types has not been established. An item-class breakdown for the available engineering test figure has not been supplied.

AI and On-Device Architecture

On-Device Image Analysis

The pilot app uses YOLO26 segmentation through an ONNX model named recent_best.onnx. Inference runs on the device and can operate offline.

The documented processing path is:

  1. 01Flutter camera
  2. 02Image preparation
  3. 03YOLO26 segmentation
  4. 04recent_best.onnx
  5. 05onnxruntime_v2
  6. 06On-device/offline inference
  7. 07Count comparison
  8. 08User confirmation or correction
  9. 09Local app/device storage
iCount pilot-app detection overlay identifying visible supported surgical consumables
Authentic supplied pilot-app screenshot showing the detection overlay on visible consumables. Clinical-content note: used swabs with visible red staining may appear; no patient identity or procedure imagery is shown.

1. capture or select an image in the Flutter app;

2. prepare the image for analysis;

3. run recent_best.onnx on the device through onnxruntime_v2;

4. identify and count visible supported items;

5. compare the detected count with the expected count; and

6. present the result for required user review.

On-device processing describes where the current inference runs. On-device processing alone does not establish clinical safety, data security, regulatory compliance or model performance.

Human Verification and Clinical Boundary

Human Verification Is Required

iCount is an AI-assisted pilot tool. A staff member must review the detected items and count comparison, then confirm or correct the result in the app.

The system:

  • does not replace the established manual count;
  • does not make an autonomous clinical decision;
  • does not remove staff responsibility for verification;
  • is not presented as a production medical device;
  • is not presented as clinically validated, certified or approved;
  • is not presented as ready for clinical reliance;
  • does not guarantee that all items will be detected; and
  • is not shown in this case study to prevent retained items or achieve safer outcomes.

A displayed match only means that the app’s detected count and recorded expected count align at that point in the workflow. It is not proof that a procedure is safely complete. User confirmation remains required.

Staff verification screen in the iCount pilot app for reviewing and correcting an AI-assisted count
Authentic supplied pilot-app screenshot showing the required staff-verification stage. Clinical-content note: used swabs with visible red staining may appear; no patient identity or procedure imagery is shown.
Engineering Testing Evidence

Engineering Test Evidence,
Not Clinical Validation

The team reported 92% detection accuracy across 100 test images during engineering testing.

This is engineering test evidence. It is not clinical validation.

The available information does not document:

  • the test conditions;
  • the dataset composition;
  • the number of images for each item type;
  • performance for Spongetapes, Raytecs, clips or trays individually;
  • count accuracy;
  • sensitivity or specificity;
  • safety performance;
  • clinical efficacy; or
  • performance in patients, procedures or clinical cases.

The 100 samples were test images, not 100 patients or 100 surgical cases. The reported detection figure does not establish performance for every supported item, every image condition or clinical use.

Pilot Scope, Not Results

Pilot Scope, Not Clinical Results

The current work covers a hospital-pilot workflow for expected-count entry, image capture, on-device item detection, count comparison and required staff verification.

/ 02

A matched result can show that the detected count aligns with the recorded expected count

Authentic supplied pilot-app screenshot showing a matched comparison. A match is not proof of safe completion; staff confirmation remains required. Clinical-content note: used swabs with visible red staining may appear; no patient identity or procedure imagery is shown.

iCount pilot-app screen showing a detected count matching the recorded expected count
/ 03

A mismatch can be flagged for manual review and correction

Authentic supplied pilot-app screenshot showing a discrepancy path for manual verification. Clinical-content note: used swabs with visible red staining may appear; no patient identity or procedure imagery is shown.

iCount pilot-app mismatch screen directing the user to manual verification

These screens demonstrate the intended pilot workflow. They do not establish improved safety, fewer count errors, clinical effectiveness or successful completion of a surgical count.

Core Pilot Features

01

Count Setup

2 features

Expected-count entry

Users can record the expected quantity of supported consumables before comparison.

Camera-based image capture

The Flutter camera workflow supports image capture during or after the procedure.

02

Image Analysis

2 features

Visible-item identification

The AI model identifies supported items that are visible in the captured image, subject to model and image limitations.

On-device inference

The ONNX model runs on the device and can process images offline.

03

Comparison & Review

3 features

Count comparison

The app compares the detected quantity with the expected count recorded by the user.

Match and mismatch display

The interface can display whether the detected and expected counts align or whether a discrepancy needs review.

Required staff review

The user confirms or corrects the displayed result in the app. The exact confirmation and correction interaction is not fully documented.

04

Device & Data

1 feature

Local app data

Current images and app data are stored locally in the app/on the device.

Current implementation

Current Local Storage and Privacy Boundary

In the current pilot implementation:

  • AI inference runs on the device and can operate offline;
  • images are stored locally in the app/on the device; and
  • no patient identity storage has been reported.

The supplied screenshots do not show patient identity or procedure imagery. Some show used swabs with visible red staining.

The available project information does not document:

  • encryption;
  • retention periods;
  • deletion controls;
  • access controls;
  • consent design;
  • anonymisation controls;
  • regulatory compliance controls; or
  • server security.

Local storage and offline processing alone do not establish security, privacy by design, encryption, compliance or anonymity.

Planned · Not Implemented

Planned Server Storage

Server-based storage is planned for future work but has not been implemented in the documented pilot.

No backend, hosting provider, server architecture or server security design has been supplied.

Also Fits

Where This Workflow May Also Fit

Subject to separate testing, governance and clinical review, the same type of human-verified image-analysis workflow may be explored for:

  • 01visual count support for other clearly defined consumable sets;
  • 02training or simulation environments using approved non-patient imagery; and
  • 03controlled inventory-verification workflows where a user reviews every result.

These are possible adjacent applications, not implemented deployments or validated clinical uses.

Technologies

Documented Technologies

01
Application
Flutter
Dart SDK 3.2.0+
MVC/MVVM-style application structure with GetX
GetX state management using Obx, RxList and controllers
GetX routing
flutter_screenutil
02
AI and Image Processing
YOLO object detection and instance segmentation
YOLO26 segmentation
onnxruntime_v2
recent_best.onnx
on-device/offline AI processing
image
Flutter camera
flutter_image_compress
03
Local Data and Assets
SQLite
path_provider
cached_network_image
04
Distribution
Android APK/AAB
iOS TestFlight

This technology list documents the current app stack. It does not establish regulatory status, clinical validation, security certification or production readiness.

Planning a Human-Verified Computer Vision Pilot?

We help teams design and build AI-assisted applications with clear workflows, documented technical boundaries and human review at important decision points.

Discuss Your Pilot

Tell us about the workflow, users, evidence requirements and verification steps your pilot needs.

FAQs

Frequently Asked Questions

What is the iCount AI surgical consumables counting system?

iCount is an AI-assisted pilot app that analyses captured images to identify and count visible supported surgical consumables. It compares the detected count with the expected count recorded by staff and shows the result for required confirmation or correction. It does not replace the established manual count.

Which surgical consumables does the current pilot include?

The documented item types are Spongetapes, Raytecs, clips and trays. The available evidence does not provide an accuracy breakdown for each item type or guarantee that every visible item will be detected.

Does iCount make an autonomous clinical decision?

No. The app presents AI-assisted detection and comparison information for staff review. A user must confirm or correct the result in the app. The system is not presented as ready for autonomous or unverified clinical use.

Is iCount clinically validated or approved as a medical device?

No such claim is supported. iCount is described as a hospital pilot in progress. The available engineering test evidence is not clinical validation, certification, approval or proof of clinical efficacy.

Does the iCount app work offline?

The documented ONNX inference runs on the device and can operate offline. Images are currently stored locally in the app/on the device. Offline operation alone does not establish security, privacy compliance or clinical safety.

What does the reported 92% detection accuracy mean?

The team reported 92% detection accuracy across 100 test images during engineering testing. The test conditions, dataset composition and item-level breakdown have not been supplied. The figure must not be interpreted as count accuracy, sensitivity, specificity, safety performance, clinical efficacy or evidence from 100 patients or procedures.

DMCA.com Protection Status  © Copyright 2003 - 2026 Softlabs Technologies & Development Pvt. Ltd. All Rights Reserved.