Regimed -medicine reminder application

Constructing a dynamic, end-to-end mobile application that will effectively streamline medical information communication in a patient-centered format.

  • Role
    UX Research & Design
    Project Scope
    Constructing a dynamic, end-to-end mobile application that will effectively streamline medical information communication in a patient-centered format.
    Project details
    Group Project : Remote Collaboration Self Directed, with feedback from the peers.

    Duration : 4 weeks plus.

    Platform : Mobile Application

    Tools : Figma, Sketch, Miro, Illustrator, Airtable, Draw.io and iPad Pro.
    Target User
    Physicians.

Project Overview

The Problem

Regimed is a mobile application, designed from a physician’s perspective, focused on constructing a dynamic, customizable medication regimen that lays out important medical information in a patient-centered format. There is a significant issue regarding patients adhering to their medication regimens. In fact, 50% of patients do not take their medications as prescribed. Physicians do not have an effective process to relay important medication regimen instructions to their patients. Often times, the notes are overwhelming or misunderstood, and the patient portal is confusing or too hard to access.

Solution

Constructing a dynamic, end-to-end mobile application that will effectively streamline medical information communication in a patient-centered format.

Research

Challenge

A huge challenge of this project was to better understand the gap between physicians and patients when in regards to regimen adherence. As someone who is not in the medical field. It is quite known in the healthcare industry that there is a significant issue when it comes to patients adhering to their medicine regimens. In fact, 50% of patients do not take their medicines as prescribed. Unfortunately, there isn't an effective process today for physicians to relay important medication regimen instructions to their patients besides typing them up in their EMR systems. Oftentimes, the notes are overwhelming or misunderstood, and the patient portal is confusing or hard to access. I had to do a lot of research to get a holistic view of the challenges that are occurring from the initial patient interaction to a return visit by designing a mobile application that will effectively streamline communication from one user to the other.

Research Goals

Identify Regimed's target audience.

Identify Regimed's competitors.

Identify healthcare technology trends in regards to medication regimen tracking.

Understand the importance of taking medication regimens as prescribed.

Understand what medication regimen conversations between physicians and patients look like today (from the physician's POV).

Market Research

After doing market research to get a sense of what I know and don't know yet and what the recent trends or news are, The insights I gathered from market research will help me frame meaningful questions in research. As I am designing a dynamic, end-to-end mobile application for the healthcare sector, I am designing from the physician's perspective. I created a research plan to help pinpoint the scope of the project. I addressed the research goals, questions, and assumptions I would focus on. Because of the complexity of this challenge. I had to make quite a few assumptions, outlined below:
  • Project Assumption
    Regimed will not capture patients' personal information to make decisions about their medication regimens.

    Physicians will use Regimed solely to add/update medication regimens and track patient progress and adherence.

    Due to time constraints, I will identity MD professionals only as my users (with knowledge that other healthcare professionals can prescribe medication).

    Regimed will already be integrated with hospital EMR systems
    Prescription Medication statistics
    A report from the American Heart Association notes that nearly 60 percent of patients taking five or more medications take them improperly.

    Research shows that approximately 25% of prescriptions are left unfilled by patients and nearly 50% of patients are non-adherent to the medication once they have obtained it.

    Top reasons for nonadherence include fear, cost, misunderstanding, too many medications, lack of symptoms, worry, depression, and mistrust.

    A common theme in the top reasons for patient non-compliance to medications is the prevalence of inadequate health literacy.
    Healthcare Technology Trend statistics
    Personal Health wearables will be used by as many as 1 in 5 Americans by 2021.

    Cloud-based systems so physicians have access to large amounts of data quickly and can monitor patient’s data from elsewhere.

    Telemedicine - physicians will be able to communicate with patients quicker and easier.

Competitive Analysis

After conducting my market research, it is equally important to research other P2P payment apps, as their strengths and weaknesses will not only shed light on the key areas in which we should strive to maintain high quality, but also help me identify any opportunities for Venmo to emphasize. I analyzed direct competitors, who are major P2P payment service providers, and indirect competitors, who integrate P2P payment features into their services.
  • Strengths
    Most popular medicine reminder app.

    iOS health app integration.

    Apple watch compatible.

    Free to use.

    Share progress report with physician.

    Multiple accounts and medifriend feature.
    Weaknesses
    Premium version costs $40 a year.

    Self-managed.

    UI can be confusing.
    Strengths
    UI is clean and concise.

    Apple watch compatible.

    Easy walkthrough for adding medicine.

    Refill reminder feature.

    Free to use.
    Weaknesses
    No iOS health app integration.

    Self-managed.

    Only a single account.
    Strengths
    Free to use.

    A lot of positive reviews.

    Refill reminder feature.
    Weaknesses
    UI is outdated and confusing.

    Full version costs $1.99

    Self-managed.

    No iOS health app integration.
    Strengths
    Habit tracking.

    Apple watch compatible.

    Point system to reward user.

    My stats summary.

    Free to use.
    Weaknesses
    UI can be overwhelming with information.

    No iOS health app integration.

    Self-managed.

    Refill doesn't exist or is confusing.

User Interviews

Understanding the Physician's POV in more detail

A great way to build real connection and gain direct insights with users is through interviews. I conducted 4 physician interviews by setting up a screening questions document, asking them questions ranging from “What medications do you usually prescribe to your patients?” to “How do you keep track of your patient's progress with their medicine regimen?”. My goal was to understand different prescription medication use cases and physician patient interactions better.

Empathy Map

After transcribing all of my interview notes, I decided to use an empathy map to synthesize patterns and form insights that would help me uncover these individuals’ implicit needs.
  • Insights
    Physicians don't have an effective way of tracking a patient's medication regimen progress.

    Physicians often confuse their patients with too much or too little information.

    The current approach physicians use to communicate a patient's medicine regimen is often physically lost or mentally forgotten.
    Needs
    Physicians need a better way to track their patient's medication regimen progress once they leave their visit.

    Physicians need a more effective way to communicate medication regimens details to their patients.

    Physicians need a more effective approach for patients to access their medication regimen details.

User Persona

With the information gathered from the interviews and the insights & needs discovered through the empathy map, I constructed a user persona. Meet Dr. Stacey Mills, our champion. I created a user persona that accurately represented who we were designing for. This persona helped guide my decisions along the design process to make sure the solution I am designing is centered on our user.

Dr. Stacey Mills

Female 35 yrs old, Physicians, Married.
  • Goals
    Dr. Stacey doesn't have an effective way of tracking a patient's medication regimen progress.

    Dr. Stacey often confuses her patients with too much or too little information.

    The current approach Dr. Stacey uses to communicate a patients medicine regimen is often physically lost or mentally forgotten.
    Needs 
    Dr. Stacey needs a better way to track her patient's medication regimen progress once they leave their visit.

    Dr. Stacey needs a more effective way to communicate medication regimens details to her patients.

    Dr. Stacey needs a more effective approach for patients to access their medication regimen details.
    Motivations
    Empowering patients.

    Seeing improvements in patient outcomes.

    Empathizing with patients.
    Frustrations
    Not enough time interacting with patients.

    Patients not adhering to their medication regimens.

    Not getting an accurate patient medication history.

Defining the Problems

How might we reshape Dr. Morgan’s needs into actionable questions?

Now that I knew who I was defining for, I wanted to make Daniel goals and needs feel more personal. I was able to use the insights and needs gained from research to identify what the main problems are that I am trying to solve. I used those insights and needs to create POV statements to better understand the problem from the user’s perspective and then created HMW questions to come up with possible solutions for these problems.
  • Insights

    Physicians don't have an effective way of tracking a patient's medication regimen progress.

    Physicians often confuse their patients with too much or too little information.

    The current approach physicians use to communicate a patient's medicine regimen is often physically lost or mentally forgotten.

    Needs

    Physicians need a better way to track their patient's medication regimen progress once they leave their visit.

    Physicians need a more effective way to communicate medication regimens details to their patients.

    Physicians need a more effective approach for patients to access their medication regimen details.

    HMV Question

    How might we help Dr. Stacey communicate medicine regimen details to her patients more effectively.

    How might we help Dr. Stacey better track her patient's medicine regimen progress once they leave their visit.

    How might we help Dr. Stacey create a more effective approach for patients to access their medication regimen details.

Brainstorming

Based on the HMW questions, I started the brainstorming process with mind mapping. I spent 3 minutes on each HMW question, and moved on to the next HMW question when the time is up and quickly generated as many different ideas as possible.
How might we help Dr. Stacey communicate medicine regimen details to her patients more effectively?

How might we help Dr. Stacey better track her patient's medicine regimen progress once they leave their visit?

How might we help Dr. Stacey create a more effective approach for patients to access their medication regimen details?

Group Brainstorming

Apart from completing my own individual brainstorm, I facilitate a group brainstorm session with 4 participants. This activity helps me gather more solutions proposed from different minds of people. Before the group brainstorming, I sent out an agenda to each participant. These sessions were great because it allowed for creative freedom without fear of too many constraints.

Project Goals

With creative solutions at the front of my mind, I decided to list project goals that will both serve as a guide for the further development of the product and a rubric for determining what features to include in the application. I established business goals by summarized user goals from my user persona and empathy map. To make sure the product is both usable and sustainable, I identified mutual goals by aligning specific business goals with user goals.
  • Business goals

    Reduce the need for patients to revisit for the same diagnosis.

    Generate revenue for the hospital to continue to operate.

    Provide for their healthcare professionals.

    Provide the most pleasant experience while in the hospital.

    User goals

    Empowering their patients.

    See improvements in their patients outcomes.

    Empathize with patients.

    Communicate with patients effectively.

    Mutual goals

    Provide comfort for everyone in the hospital.

    Provide adequate treatment to patients.

    Build trust with patients.

Product Roadmap

I then started to put the solutions I brainstormed into a list of product features to create a comprehensive product roadmap.These features were sorted into four categories, including Must-have (P1), Nice-to-Have (P2), Surprising and Delightful (P3), and Can-come-later (P4) features. They were sorted based on on level of need and effort.

Application Map

After setting up the product goals and deciding what features to include, I want to continue building up the structure of the app using the application map. An Application map helps me to visualize the relationship between the content and examine the hierarchy. Knowing which features and sections would make it into the MVP helped establish the application map.

Task Flow

To decide what I am designing, identifying the main flow of users when completing a task helps me direct my focus on designing specific pages. By creating task flows that center on the new features I am adding, I was able to think through the necessary steps and examine the user experience in detail.
User Task 1: Create the medicine regimen and email it to jackson once created.

User Task 2: Figure out where to track Janet adherence.

User Task 3: Check if there are any patients who finish their medicine regimen on Nov .27th.

User Flow

Building on the task flow, Now I wanted to take an even deeper look into the overall user’s journey while interacting with the new features. In order to more deeply empathize with the user, I created a user flow to explore the scenarios the users would be in and the different paths and decisions they would encounter when trying to complete the key tasks defined. The decision trees were added for me to think through what actions users would take based on their feelings with app.

Lofi Wireframe Sketches

I sketched a few iterations of low-fidelity screens before landing on final lofi wireframes sketches with help of ipad. It also enables me to examine ideas or possibilities before putting everything in the daunting process of digitizing.

Sketches to Mid-Fidelity Wireframes

It was time to whip up the Mid-Fidelity Wireframes to create a prototype to test on real users using high fidelity wireframes. I designed these with Dr. Stacey goals & needs in mind as well as the scenarios at hand.

Usability Testing

Before usability testing,  it was imperative to come up with a usability test plan that outlined key objectives, along with the stated scenarios and specific tasks to be completed. Therefore, I wrote a usability testing plan to define what and why I want to test and get prepared for the test.

I expect a 100% completion rate since all tasks are normal steps for navigating medical related tools. I'm expecting an 94% error free rate with the majority of errors stemming from a limited mid-fidelity prototype and unfamiliarity using a mobile application for medical-related functions.

I conducted four remote, usability testing via Zoom with 4 participants, and created transcripts for each participant based on my observation of their interaction with the prototype. Participants were asked to share their screen while navigating the prototype tasks. I requested they think aloud and bring up any steps they considered to be intuitive or frustrating.

I jot down their mistakes, slips, and confusions they expressed in the process. This transcript is a perfect raw material for summarizing the patterns of user’s interaction with the prototype.

Affinity Map

With all the notes compiled from the usability tests, I started to synthesize all the information through an affinity map. I was able to draw connections to uncover patterns which helped me identify design recommendations to improve the usability of my design. Like the empathy map, it is effective in helping us find patterns and frustrations when users are interacting with the prototype, and identify areas of improvements based on priority levels. where I will fix problems that affect key functions for our app.

Pain Points

I identified common pain points encountered by users during testing leading to my discovery of key insights which helped me to identify  design recommendations.
4/4 Users had difficulty realizing they need to swipe to the next medication first.

4/4 users showed some confusion to misinterpret the regimen progress bar to be an adherence compliant percentage.

3/4 Users do not find the calendar that shows when patients regimens end to be helpful or necessary.
  • Insights
    Users are focused on the create regimen CTA when reviewing the first medication that they don't realize they need to swipe to the next medication first.

    Users assume they can directly edit the review medicine screen without having to click on an edit button first.

    Users misinterpret the regimen progress bar to be an adherence compliant percentage because of how certain medications are prescribed.

    Users do not find the calendar that shows when patients regimens end to be helpful or necessary.

    Users would rather see a calendar view of upcoming patient appointments instead.
    Recommendations
    Remove the create regimen CTA from the first medication screen and make the scrollable indicator easier to notice.

    Remove the edit button and add drop down indicators to the appropriate fields.

    Change regimen progress to adherence compliance % instead.

    Replace the calendar view that displays when patients regimens end with a calendar view that displays upcoming patient appointments on home screen.

Priority Revisions

Using the recommendations identified through testing, I started to make these revisions in the Mid-fidelity wireframes.

1. Remove the create regimen CTA from the first medication screen and make the scrollable indicator easier to notice.

Remove the edit button and add drop down indicators to the appropriate fields.

  • Before
    After

2. Change regimen progress to adherence compliance % instead.

  • Before
    After

3. Replace the calendar view that displays when patients regimens end with a calendar view that displays upcoming patient appointments on home screen.

  • Before
    After

Mid to Hi-Fidelity Wireframes

Using Figma, after creating high-fidelity wireframes. I attempted to integrate the newly-added features seamlessly into Regimed.

Prototype

Following my wireframes, I then used Figma to create an interactive high fidelity, limited functionality prototype that I would use for usability testing.

Final Prototype

After completing the revisions, I updated my prototype with the revised design.

High-Fidelity Design Artboard

High-Fidelity Design Interaction Wiring

High-Fidelity Interaction Scenario 1 prototype

Dr. Stacey wants to create a new medicine regimen, via import data from EMR system, for patient miller brown. The regimen will consist of miller blood pressure medications and will be emailed to him after it's created.

High-Fidelity Interaction Scenario 2 prototype

Dr. Stacey wants to track patient robert smith adherence to his blood pressure medicine regimen.

High-Fidelity Interaction Scenario 3 prototype

Dr. Stacey wants to know if any of her patients will finish their medicine regimens on Nov. 27th to decide whether a follow up appointment is necessary.

Reflection & Next Steps

This was definitely a challenging project, from that complexity of the issue, to the number of different groups it involves, to the assumptions that needed to be made. It's actually quite shocking how serious of an issue medication regimen adherence is and how little focus seems to be thrown at it. Luckily for me, quite a few of my friends are practicing physicians. so I was able to dig deeper from a physician's POV. I would present my deliverables to the rest of the team (stakeholders, product manager, developers, fellow designers, marketing, etc) and explain my design process and how I came to these decisions. I would work with the developers to ensure handoff is as smooth as possible by documenting my work well, utilizing the design system, and specifying any wireframes that may be unclear.

The next steps I would take this project through from here are:
  • Re-Test
    I would also love to continue usability testing and improve on the recommendations I took into consideration. Next steps would be to identity patient personas to interview and design what it would look like from their end.
    Implementation
    Assuming time wasn't a constraint, I think there is a lot more I could do with this project. I created Regimed from the physician's side of the application but wasn't able to do the same from the patient's side.

Let’s make 
Something great.

Vikash.danegi@gmail.com
+91 93548 43964
negi.vikash1490@gmail.com
negi.vikash1490@gmail.com
+91 93548 43964
negi.vikash1490@gmail.com
Let’s Connect

Hire Me

Let's Connect

Hire Me

Let's Connect

Hire Me

Let's Connect

Hire Me

Let's Connect