By A
What it has done for FISH, and what it can do for Molecular
Errors, popups and workflow snags in SCC happen every shift Reports lived in emails, hallway conversations and personal screenshot folders No single list of what was open, who saw it, or what SCC was told The same problem got reported twice, or not at all
One small desktop app
A single Windows program that opens in under a second, no admin rights needed
One shared folder
Every issue is saved as its own file on the lab network share
Two views
Log an Issue for anyone, and a password-gated Dashboard for super users
Nothing else touched
No LIS interface, no patient results, no internet connection
Tech logs it
About a minute, from any workstation
Shared folder
One file per issue on the lab share
Super user triages
Status, ticket and notes on the dashboard
SCC fixes it
The HEMAT ticket is tracked until resolved
Six screens, from the bench to SCC
Initials and department fill themselves in Pick the issue type and priority Scan or type the HLID, tasklist, slide or probe
Sample data shown
Paste a screenshot with Ctrl+V Circle the problem and add a note Required for error popups, so the message is never paraphrased
Sample data shown
Techs only see the logging form Super users enter the department password The department manages its own passwords
Sample data shown
Every issue with its priority and status Record the HEMAT ticket sent to SCC Watchlist and notes auto-save for everyone
Sample data shown
Link related issues by ID Linked Shading colors them as a group One SCC defect hitting many slides stands out
Sample data shown
Description, steps, module and stack trace The marked-up screenshot beside it Copy for TigerText or email in one click
Sample data shown
One source of truth
Every FISH SCC problem is on one list instead of scattered inboxes
Better tickets to SCC
Screenshots, steps to reproduce and exact IDs travel with every report
Nothing falls through
Open items stay visible until a super user marks them resolved
Patterns show up
Linked issues reveal when one SCC defect is hitting many cases
Bench time protected
Techs log it and get back to work; super users handle the follow-up
Formal software validation record (CG-VAL-2026-001), risk assessed as LOW Automated end-to-end test suite passed on the final build Functional test cases cover every form option, barcode scanning and dashboard accuracy Microsoft Defender scan clean; confirmed to make zero outbound network connections Security review document prepared for IT
Same app
Molecular is already a department option on the form
Own folder
Point it at a Molecular Issues folder on the share
Own super users
Molecular sets its own dashboard passwords
Own columns
Add the fields Molecular cares about, no code changes
Day one
Mol techs start logging SCC issues immediately
What stays the same
The validated app and its file format The logging form and screenshot markup Auto-save, per-field merging, no internet access
What Molecular configures
Shared Issues folder location Dashboard passwords for Mol super users Watchlist people and custom columns Default department on each workstation
Week 1
Create the Molecular Issues folder and pick super users
Week 1
Install on Mol workstations (one-click, no admin rights)
Week 2
Short walkthrough for techs and super users
Ongoing
Super users triage weekly and send HEMAT tickets to SCC
One form. One folder. One list.
Easy to use
If logging takes a minute, people actually log
Easy to trust
Low risk, validated, no connection to results or the LIS
Easy to support
No server, no database, no subscription, just files on the share
Easy to copy
What worked for FISH works for Molecular with a folder and a password