CTMS is a web project where patients, doctors, nurses, patient advocates, and pharma companies can examine patient data and manage information. Only the data of patients who have given consent are examined. CTMS manages over 33.000 patients’ data worldwide.
There were many manager profiles on this platform therefore we have evaluated every scenario and made a great effort to determine the needs. We weren’t able to access our competitors’ web projects therefore our research mainly focused on users’ needs and the daily problems they faced.Users didn’t need this type of data management application in their daily lives and this made the process even harder.
Not having a digital equivalent of the health system was one of the biggest problems that we faced. Users preferred to carry out their process in a more traditional way instead of a digital platform. The reason for this was their concern about data and information safety. We carried out our researches while making information security our top priority and made sure that the security systems were at the top of the ladder. We worked in the most minimal way to make sure that users could use the application most efficiently.
Information confidentiality and protection
Users’ devotion to traditional methods
Effective data presentation and comparison
Fast services and information architecture
The number of applications we could find in the market was limited and this was one of the other challenges we faced. We then decided to evaluate the process in parts instead of looking at it as a whole. We compared our priority features to the best practices of some of the other applications and tried to understand how helpful they would be in meeting users’ needs and in creating values for us.
We decided that testing the page orders with quick sketches was the fastest route for us to use. Then, we moved on with clearly-organized modular and instructive design patterns that had a lot of negative spaces.
New Issues with High Fidelity Prototype
These hi-fi wireframes helped us overcome the problems related to the information architecture. We were able to decide which elements would come secondary and discovered some of the issues that users faced in terms of language as well as new functions.
Understanding what works and what doesn't
I faced some challenges when confirming the basic user duties that I had determined during testing. Even though these duties were straightforward, I realized that some features needed reviews. We realized we were still inadequate in language. Many users expressed that there were points on the screen that they missed even though they had completed the processes successfully.
I learned the problems that users faced and found out how we could integrate our services into their daily lives with an in-depth user analysis. I was able to come up with plans to present information fast.With extensive research and tests, we understood the problem points and the relative importance of the information users wanted to see. This showed me what to examine to create a simple yet neat and understandable flow.
What have I learned
Time and reliability are key factors
Users tend to give up quickly due to the problems they have with applications. I saw that we could integrate these users into our systems with a fast, simple, reliable, and understandable flow. This has become a priority for us in our other applications as well.
Variables are important
No matter how much data were on the result pages, users wanted to see and control all data. Easy-to-use filters and in-page navigation were essential parts of the process.
Clarity of the process and the language mattered
Users expressed their concerns about the unclear data that they were not experts in along with knowing where they were in the treatment process and which data were being compared. Use of a simple language and intuitive expressions were essential in guiding the users fast.