Back to Portfolio

TriggerPredict CDSS

Mount Sinai Hospital Systems Engineering / Python UI
January — April 2026

Overview

Over a rigorous 4-month period for the APS112 engineering design course, my team (me, Mateo Castano-Yepes, April Huynh, Ximena Saishio Garcia, Hui Ming Sun) partnered with Dr. Claire Jones, a leading infertility specialist at Mount Sinai Hospital. We were tasked with developing a Clinical Decision Support Software (CDSS) algorithm to optimize In-Vitro Fertilization (IVF) trigger shot timing. Working alongside my talented team members, we successfully engineered the TriggerPredict App—a streamlined, locally-hosted Python application that translates complex patient datasets into data-backed medical recommendations.

APS112 Engineering Team 128

Inspiration

An IVF cycle requires a strict 10-12 day monitoring period of numerous clinical factors. The critical step in this entire process is the "Trigger Shot," which prompts final egg maturation just before retrieval. Administering it too early or too late drastically reduces pregnancy success rates and can cause severe medical complications like Ovarian Hyperstimulation Syndrome (OHSS).

Currently, Mount Sinai physicians rely heavily on personal clinical judgment when reviewing complex spreadsheets (stim sheets) of hormone levels and follicle sizes, which often leads to disagreements among specialists. Our inspiration was to bridge this gap. We wanted to create a standardized, evidence-based framework that would seamlessly integrate into the clinic's daily meetings, reducing cognitive load for physicians while providing transparent, research-backed justifications for every trigger decision.

How We Built It

This project was an exercise in comprehensive systems engineering and the iterative design process. We constructed a rigorous decision-tree flowchart based on current medical literature, specifically evaluating the four key variables of IVF timing:

Using free brainstorming, SCAMPER, blue sky thinking, and morph charts, we generated 124 potential solutions. We filtered these ideas using feasibility checks and a Pugh Chart to evaluate our top designs against our core objectives (intuitiveness, system integration, justification provision, and human error minimization), ultimately culminating in the TriggerPredict Python UI.

Challenges & Solutions

Strict Legal & Ethical Constraints: The healthcare sector is highly regulated. Our solution had to comply with the Personal Health Information Protection Act (PHIPA) and Health Canada’s SaMD CDSS classification standards. Solution: We designed the app to run locally on a Python backend. It evaluates patient data instantly but purposefully does not store any personal identifiers between uses, ensuring total patient privacy.

Cognitive Load vs. Accuracy: One of our alternative designs was a highly accurate, massive physical flowchart poster. However, we realized that navigating a dense flowchart actually increases cognitive load in a fast-paced clinical setting. Solution: We opted for the app-based interface. It requires manual data entry (a slight trade-off), but it drastically simplifies the visual presentation and provides automatic, algorithm-driven evaluations with one-click references for the medical staff.

Accomplishments & Skills Learnt

This project was a massive leap forward in my understanding of professional engineering design.