A novel, patented, system for identifying hypoglycemic unawareness in patients. Through creating a simple way for patients to document their symptoms the HypoMap system allows doctors to identify diabetes patients who exhibit moderate to acute hypoglycemic unawareness like never before.
I was the Lead Designer on this project and responsible for wires, user testing, prototyping, and all design. I worked alongside one Product Manager to make sure all goals were reached.
Patient & Doctor Flows
Working closely with Joslin Diabetes Center we were able to rely on their deep wealth of knowledge regarding current hypoglycemia diagnosis techniques and treatment plans. Using this research the Product Manager and I sat down and hammered out a basic flow of what a new hypoglycemia treatment would look like.
In this step of the process the doctor identifies several hypoglycemia events with the patient. The doctor prescribes HypoMap to the patient using some of our marketing collateral that guides the patient through the process of either becoming a new Glooko user or adding the HypoMap to their existing account.
Once the patient is up and running with the Glooko app and syncing their meter with Glooko all they have to do is log some information into the app every time they're hypoglycemic. Using the Glooko Web Platform the doctor always has access to a patients data as it's entered into the app. The length of the monitoring period is determined by the doctor.
After the monitoring period is over the patient and doctor either meet in person or over the phone to discuss the results. This is where the HypoMap web views come in. They take all the patient reports and create simple visualizations to identify hypoglycemic unawareness, frequency of events, and any patterns around their events.
We focused on solving two main problems with the app. Prompting people to complete a hypo report when we detect low blood sugar and making completing a report a breeze.
When the patient syncs their meter with Glooko they get a notification of all the hypo events they have had. This leads the user to the HypoMap section of their Glooko App where they can fill out a Hypo report.
After selecting a particular hypo event a patient can fill out a hypo report that goes through the symptoms, causes, and treatments for each hypo event.
I started with the base data we needed to display: blood glucose, symptoms, causes, treatments and time. Using this data and hierarchy of needs I gleaned from talks with several doctors I put together basic wires of how to display this information.
After getting everyone on the team to agree on the wires I mocked up a quick version of the web views and a version of the mobile app in InVision. From now on when the Product Manager and I ran user testing we would have something concrete to show and get feedback on. We followed a weekly feedback schedule with nurses, and doctors from Joslin Clinic to make sure the web product was headed in the right direction. We also ran parallel feedback sessions with current Glooko users at our office with the InVision prototype.
Everyone is part of the solution
Having only one clinic providing the majority of the feedback proved to be a hindrance to mass adoption. Every clinic & health care provider has a method, a unifying method would include them in the conversation.
Stop the creep
A successful product cycle must be setup to identify and prevent scope creep . Setting hard stop dates on project features while prioritizing a more iterative process minimizes resource waste and unproven solutions.