Skip to main content

Surgery Intellect - Usage Report

How to Navigate and Analyse your Surgery Intellect Usage Report Dashboard

Introduction

This report provides a detailed breakdown of how your team is utilising our AI scribe for clinical documentation. Refreshing over night it tracks the volume of "Intellects", the resulting clinical outputs, and the estimated time saved by your staff

What does this report show?

  • Total use of Intellect and when it is being used

  • Estimated staff time saved from using Intellect

  • The methods used to start Intellect

  • The number of transcriptions, clinical codes and medical notes generated

  • Individual user activity

Find our reports navigation guide here


Overview

Intellect by Date

This bar chart measures the daily volume of activity over time. It tracks how many Intellects (conversations) were processed each day allowing you to identify usage spikes and lulls

Estimated Time Saving

A summary measuring operational efficiency, estimating the total amount of time saved for the team, derived as 15% of the total audio duration processed by the platform

Intellects by Top 10 Users

Measures individual engagement, it ranks the top ten most active staff members based on their total number of completed "Intellects," highlighting who is utilising the tool most frequently

Intellects by Method

Categorises how users are accessing the service, specifically tracking the frequency of different entry points such as:

  • Live Call - used during a phone call

  • Face to Face - used during a face to face consultation

  • Standalone - used without a patient

  • Audio File - used with an uploaded audio file, e.g. call recording

  • Desktop - used with a desktop or web app, outside of Surgery Connect & Phonebar

  • Embedded - other use from Surgery Connect & Phonebar

Usage Tree

This measures feature adoption and output variety. It breaks down the total "Intellects" into specific categories of work produced, specifically:

  • Clinical Notes

  • Medical Codes

  • Letters


Intellect Visuals

Workflow Process

Shows the conversion of data through the system's pipeline, it tracks the journey from raw input to finished documentation, specifically measuring:

  • Input volume: Total audio length and word count

  • Processing speed: Average audio process duration

  • Output volume: Total counts for Transcriptions, Medical Codes, Clinical Notes, and Letters

Outcomes by Date

The bar chart measures specific output productivity over time. It breaks down daily activity into four distinct categories of work product:

  • Letters Generated

  • Medical Codes Generated

  • Clinical Notes Generated

  • Transcription Generated


Intellect Data

A line-by-line record of every system event, tracking the following specific metrics for each entry

Audit Identity

Measures the exact timing (Date and Time), unique system identifiers (Tortus ID/Intellect ID), and the specific User Name responsible for the session

Input Effort

Measures the Physical scale of the work via Audio Length and Transcription Word Count

System Performance

Measures the Transcription Processing Duration to track how long the AI took to process that specific file

Output Totals

Measures the yield per session, specifically counting how many Clinical Notes, Medical Codes, and Letters were generated in that single instance


User Data

Provides a detailed breakdown for every staff member across the following categories:

Intellect Date

Measures the Earliest and Latest Intellect Dates

Total Output

Measures the volume of work through total Intellects, Transcription Word Count, and specific documents created (Clinical Notes, Medical Codes, and Letters Generated)

Time Consumption

Measures the raw input effort in both Audio Duration (Seconds) and Audio Length (Hours)

Session Averages: Measures efficiency and density per session using

  • Word Count Per Intellect: The average length of the resulting documentation per session

  • Audio Length (Seconds) Per Intellect: The average length of the audio recording per session


Did this answer your question?