The Intelligence Engine
50 surgeries a day. A principal ophthalmologist who needed to stay focused on the patient. Custom software built from scratch when the market had no answer.
Client
University of Toronto, Department of Ophthalmology
Background
Kensington Eye Institute · One of Canada's top ophthalmology centres
Type
Custom Software Development
Year
2014
The Challenge
The Kensington Eye Institute, affiliated with the University of Toronto and one of Canada's top ophthalmology centres, was running four operating rooms simultaneously, performing up to 50 cataract surgeries per day. At the centre of it all was the principal ophthalmologist: the senior surgeon responsible for both operating on patients and training the residents.
No software on the market could track exactly what this environment needed. Off-the-shelf solutions were built for generic clinical workflows, not the specific data points required for resident training and surgical case logging. The options were: pay for an enterprise system that didn't fit, or build something that did.
The second challenge was focus. When a principal surgeon is responsible for a patient on the table, their attention cannot be split. Every minute spent wrestling with software is a minute not spent taking care of the patient.
Our Approach
The goal was a tool that felt invisible — one that made documentation effortless so the people using it could keep their focus where it belonged: on the patient.
01
Before writing a single line of code, we mapped the full clinical workflow. What did the principal ophthalmologist need to track? What did the resident need to log? What was the most logical sequence from pre-op to post-op so the user never had to go backwards through the system? The requirements came from the people doing the work, not assumptions.
02
Patient health information is among the most sensitive data that exists. Security was designed into the software from day one, not patched in later. The system was deployed exclusively on a local network, protected by firewalls, with zero external access points. Every measure was taken to ensure patient records could not be accessed, intercepted, or compromised.
03
We deployed a standard software development lifecycle with continuous feedback loops: establish requirements, build version one, gather feedback, deliver version two, obtain further feedback, deploy to live environment. This wasn't a one-size-fits-all solution. It was shaped by the people using it in the operating room. The result was a tool that fit the real workflow, not a theoretical one.
04
The best software disappears into the workflow. Nobody talks about it. Nobody complains about it. The job gets done, the patient is safe, and the surgeon never has to think twice. Every design decision was made with that standard in mind — if it added friction, it didn't make the cut.
The Results
The principal ophthalmologist could walk into the OR and stay focused on the patient and the resident beside them. The resident could log their cases in a structured system designed for their training. The software did its job by staying out of the way.
Fully custom software built from scratch when no market solution existed or could meet the clinic's requirements.
Local network deployment, firewall-protected, zero external access. Full patient data protection and compliance.
The principal ophthalmologist freed entirely from administrative burden to focus on surgery and resident training.
Resident ophthalmologists gained a structured digital system to log and track their cases as they learned and improved.
Work With Us
We work with a select group of clients. If you’re serious about growth, we’d like to hear from you.
Apply to Work Together