Electronic Health Record System (EHR)
We re-vamped the outdated interface of this platform and added a smart search function. As a result, medical professionals using it can complete tasks faster and spend more time with patients
We re-vamped the outdated interface of this platform and added a smart search function. As a result, medical professionals using it can complete tasks faster and spend more time with patients
The product is 16 years old. During this time, it was created and improved by various experts. Thus, the product was extremely inconsistent and not user friendly. Our task was to make a truly complex product easy to understand, and the development process understandable and simple for the team.
We started by exploring health care. It is a complex topic. We studied the healthcare system in the market and gradually got acquainted with the structure of the existing product. We had also created Personas to understand user needs.
After that, we made the first attempt to create a product map. This attempt crashed. The product was too complex and we decided to work on the product map step by step.
We immediately took up the most difficult part of the product — the patient card. This is a complex module. There was the first and main challenge — navigation.
Navigation was supposed to be flexible, capable of theoretically accommodating an unlimited number of items.
We created the ability to search for an item in the navigation list, and also added the ability to customize this navigation. The reason for that is due to the fact that different hospitals may use different modules in the patient card.
When creating the UI, we relied on Fuse - Angular 8+ Material Design since this style was most suitable for the task that we faced with, namely, an understandable, unloaded style.
Full Design System CaseWhen developing a design system, we looked at the best examples for creating an optimal design system for this product. The best example for this project was the Atlassian design system.
Bases are the simplest entities. The whole system consists of them. These are the bricks in the construction of the system. Font styles, colors, icons are all examples of bases.
Elements are simple entities, they consist of bases. Not independent and often found in different cases and modules. They do not carry the semantic load by themselves. Are more technical entities.
Components are intermediate entities between patterns and elements. If you divide the pattern into entities, you get a component.
If you combine elements into some entity, but it is not completely independent, as a pattern, it is a component.
Yevheniia Klysha
Lead UX Designer
Olesya Vdovenko
Senior UX Designer
Nina Prisniak
Art Director
Igor Alexandroff
UI designer
Eugeniya Zhuravlyova
UI Designer
Alex Smurov
Lead UI designer
Kristina Manzhaliy
Project Manager
Fill out the form to start the conversation — we’ll get right back to you
Thank you! See you soon