GoMed App: UX Case Study
GoMed App finds the nearest medicines donors and connects them to the poor patients in a hospital by providing one-to-one information. This project mainly focuses on solving the problem of poor, backward patients by providing the medicines who can’t afford them at the earliest.
The Problem
I met one of my friends who was working on this idea and wanted to make an android app. I talked with him about the whole problem and analyzed the main design approach in the application.
The major problems solved by the app-
- Search the nearest donor who could help in case of an emergency.
- Providing medicines sooner ie from the person nearest to the patient.
Why is there a need for this app? Who will be the users?
The basic purpose was to help the poor and backward patients with medicines in a short period of time. There was no such app that provides this service for poor patients and could help them.
So donors of medicine, doctors, compounders, and hospitals will have the mobile application and as the patients are assumed to be poor will be communicated by SMS service in mobile phones.
GoMed App
Approach
The basic approach I kept in mind was to make the process of using the app hassle-free and interactive experience. The process of looking for apps should be as easy as someone searching for a topic on Google.
The idea
After putting a considerable amount of research and discussion with my friend several times into the app, there was an idea for how the app should look like and what features should it contain assuming all the factors and the basic requirements.
Features
- Locate the nearest donors.
- Ask the donor to donate medicine at a particular time through notification.
- Verify the doctor based on reg no.
- Provide a login pin to compounder to authorize him/her to a specific hospital.
- Ask for substitute medicine to doctor if a particular medicine is not found.
- Notification if after a certain duration of time no reply from donors.
- SMS service for patients as assuming no mobile phones are used by them.
- Hospitals could only add new Doctors and Compounders and can update the information.
Prototypes
We chose colors that felt fresh and appealing, and that was easy to read. We also broke our onboarding process into 3 different users.
The application is divided into three main users —
Donors
The main task of the donor would be to donate medicines. As soon as the Compounder searches for medicine, the notification is sent to the donor whether he/she is available for providing that medicine at that certain duration of time. As soon as he/she will accept it, SMS will be sent to the patient and compounder providing the whole information like phone no. , address, etc. of the donor so that they can contact each other. In this way, the patient could approach the donor and access the medicine.
In case if no donor is available to provide that specific medicine or has ignored the notification due to some reason, then after 15min the SMS will be sent to both compounder and patient that medicine is not available.
Compounder
Compounder will be the part of the Hospital and would only be able to access the app with a login Pin given by the Hospital administrator. He/she would be finding the medicine based on the prescription provided by the patient. Search will be based on Doctor’s name as it will serve as a key to record the medicine found.
And then if the medicine is found in the database with the donors, in a certain range of the hospital like 3 Km, and automatic notification would be sent to all of them. As soon as the donor accepts the request of donating the medicine, a notification will be received to him/her along with the patient.
Hospitals
Hospitals would be the main authority to manage doctors, compounders, and patients. It will add new doctors and compounder and delete or modify the existing profiles for each. All the background work is done here like prescription, authorize patients, compounders, and doctors.
There are two dependent users as well —
Doctors
Doctors are a dependent entity on hospitals and are not the direct users of the application. But will prescribe the medicines that will act as authentication to provide a specific medicine. In case the specified medicine is not found then he/she could ass a substitute for it.
For future extension and safety issues, we could add a B Pharma person in hospital administration who could verify the compounder identity and prescription so that there is no misuse of the profiles shared by donors.
Patients
In the process, the patients don’t need the application and would not be required to access the app directly as they are assumed to be backward and poor, so will get the SMS with the information of the donor like name, phone no, email, address, quantity, and weight of the medicine if the donor accepts the donation.
Development
Once I finished with the design, now it’s time to discuss with my friend about the constraints while developing. Usually, I prefer to use Figma to upload all the screens and tried to keep in touch with him on chat at the development stage to make sure that they have not missed anything.
Summary
Well, there you have it. UX project completed and many lessons learned. I took around a week's time to understand, plan, and design. Through the design, I did my best to understand the users and constraints the user may have. I would like to further test my decisions, learn what I did right or wrong, and keep repeating.
Show this project some ❤️ by 👏👏👏
My portfolio: http://www.paarmita.in
