Summary

Zamplo is a connected health platform empowering individuals to manage their health and researchers to gather participant data.

My Health Journey is designed to secure, store and export health events. Listed in chronological order all medications, symptoms, surgeries, appointment dates can be stored, searched, filtered, and shared directly through the Zamplo app.

My Role

During my time at Zamplo, we had a small product team consisting of myself and one other UX designer. This project began when I was given the responsibility of enhancing the profile page. After studying the problem space I presented a chronological health timeline that became its own feature.
‍
While I led the design process, I collaborated with our development, marketing and sales teams to revise, and refine the feature.

Image of two screens open to Figma software and colour palette swatches.

Image of a diabetic taking a blood glucose reading

Problem Space

Managing a chronic condition, can mean numerous medical appointments across a range of services. The patient has a responsibility to specify and provide information regarding medications, treatment dates, surgeries, symptoms etc. Along with managing a condition, keeping a detailed record of health events can be an exasperating task.

If we cannot disrupt the current systems that place the responsibility of information on the patient...How might we empower patients and caregivers to efficiently track, store, and share relevant health information across various health services?

Research & Exploration

Prior to interviews, I began with desk research to gain some perspective on managing chronic conditions.

In this time, I learned that a growing number of people are diagnosed with multiple chronic conditions and the current fragmented health system creates barriers in the quality of their care.

One of these barriers, is the lack of clinical research on clusters of MCC's. This point unveiled an opportunity space, as electronic data capture and research is a large focus for the Zamplo platform.

Interviews

I conducted interviews with 9 individuals, combined of health professionals, researchers, caregivers and people with various chronic conditions.

Constructive insights from these interviews included the challenges of understanding and keeping track of medical jargon, the increased risk of adverse drug events for MCC's, and the ineffective methods of recording (and accurately describing) pain symptoms.

Next Steps

Gather insights on existing methods used by individuals to track and store their health information. Use these insights to inform the most intuitive paths.
Analysis of direct and indirect competitors to inform existing friction points and opportunity spaces.
Journey maps and user flows to guide wireframe paths.

image of three different user flows created during the research process

A sitemap built for the health journey feature. Main branches are search, date filter, sorting filter, advanced filter and new health event.

A series of wireframe sketches demonstrating a step by step flow to add health events.

User Experience Goals - Based on Findings

Export and share customized health history reports relevant to specific providers.
Quickly locate and share details from recorded events and saved documents.
Provide or revoke permission to view and contribute to health events with trusted caregivers and health professionals.
Categorize, organize and filter events according to custom preferences.

Process & Iterations -
V1 Prototype

In version 1, I experimented with nesting related health events. I put several rapid mockups to the test. Results showed that the feature worked for less detailed health histories, but quickly became limiting for others.

With the target audience being those with MCC's, I had to find new methods to link related events.

V2 Prototype

In version 2, I brought the timeline back to the health profile. The idea being that users would be onboarded through the profile and information populated in the profile would automatically create health events.

Automatic events were a success, however the feature overshadowed the profile page. Instead, a link to the health journey would be added to the profile page.

During this time we were in the process of updating the design system to improve accessibility. (ie. removing orange text & buttons). These changes were implemented prior to launching the MVP.

V3 Prototypes

In Version 3, the tagging and attachment features were optimized to ensure users could intuitively organize and find related health events.

Once testing was successful, the Health Journey feature was stripped down to its essentials and implemented in stages.

Implementation - MVP

My Health Journey was introduced in its MVP form. Notably, the initial version excludes the search function, two event categories, and the export feature.

Further iterations are planned to incorporate these elements, with ongoing development guided by insights from user research and testing.

Takeaways

This project was a complex mix of interactions and broad possibilities, emphasizing the need for continued exploration. While my aspirations for the project exceeded its limited timeframe, I learned valuable lessons in discernment - knowing when to broaden possibilities and when to hone in on focus.

My Health Journey - Zamplo