Clinside
Clinside is a web-based Electronic Health Record software aiming to address the challenges faced by small and medium-sized clinics, enhancing organization and management and bringing more efficiency to regions with limited technological adoption in the interior of Brazil.
Through a user-friendly and simplified system, Clinside seeks to innovate and streamline manual and bureaucratic processes for healthcare professionals, allowing them to focus on what truly matters: their medical practice and their patients.
Clinside is a web-based Electronic Health Record software aiming to address the challenges faced by small and medium-sized clinics, enhancing organization and management and bringing more efficiency to regions with limited technological adoption in the interior of Brazil.
Through a user-friendly and simplified system, Clinside seeks to innovate and streamline manual and bureaucratic processes for healthcare professionals, allowing them to focus on what truly matters: their medical practice and their patients.
Role
UX Designer
Areas
User Research, Interaction, Prototyping, User Testing
Date
2021 – 2024
An Electronic Health Record app for enhanced clinical management
An Electronic Health Record app for enhanced clinical management
The Problem
Very archaic, manual, and decentralized methods for organizing crucial information about patients' health. This makes the management of patient health data something that can be easily lost, often leading to delays in the diagnosis and treatment of diseases.
Appointment scheduling management by attendants/receptionists is still being carried out using physical agendas, without real-time integrations and updates, especially in clinics with multiple professionals. This makes the task laborious and allows for a high number of scheduling errors.
Lack of synchronization of schedules and patient databases for professionals working in different locations, promoting an inefficiency in the quality of service.
Very archaic, manual, and decentralized methods for organizing crucial information about patients' health. This makes the management of patient health data something that can be easily lost, often leading to delays in the diagnosis and treatment of diseases.
Appointment scheduling management by attendants/receptionists is still being carried out using physical agendas, without real-time integrations and updates, especially in clinics with multiple professionals. This makes the task laborious and allows for a high number of scheduling errors.
Lack of synchronization of schedules and patient databases for professionals working in different locations, promoting an inefficiency in the quality of service.
User Research
Several interviews were conducted with healthcare professionals, including doctors from various specialties, nurses, nutritionists, pharmacists, as well as clinic receptionists. The focus of this research was:
Understand the needs of each professional profile
Comprehend the tasks and responsibilities of these professionals' work
Explore possible points of improvement in the workflow of these individuals
Understand what existing solutions are considered to have changed the way they interact in their work
Several interviews were conducted with healthcare professionals, including doctors from various specialties, nurses, nutritionists, pharmacists, as well as clinic receptionists. The focus of this research was:
Understand the needs of each professional profile
Comprehend the tasks and responsibilities of these professionals' work
Explore possible points of improvement in the workflow of these individuals
Understand what existing solutions are considered to have changed the way they interact in their work
User Persona
Based on the valuable insights from interviews and adding demographic data of our participants, we were able to create two robust personas. These targeted user profiles serve as pillars as we navigate towards a solution for our challenge.
The first and main persona is Victor Santos, a 37-year-old experienced physician living in Aracaju and a frequent commuter to work in other small cities. His profile is rich in information that we obtained from our research, especially his goals and pain points. Other information gathered in our research added key elements to his personality. Victor's persona is a true guide in our process of understanding the user experience.
Our second persona, Rachel Fontes, is a 28-year-old receptionist currently pursuing her nursery diploma. She has been in this occupation for the past 2 years. Her profile was developed from data we collected through interviews and surveys with medical receptionists, exposing the pain points and areas for improvement in their daily routine.
Based on the valuable insights from interviews and adding demographic data of our participants, we were able to create two robust personas. These targeted user profiles serve as pillars as we navigate towards a solution for our challenge.
The first and main persona is Victor Santos, a 37-year-old experienced physician living in Aracaju and a frequent commuter to work in other small cities. His profile is rich in information that we obtained from our research, especially his goals and pain points. Other information gathered in our research added key elements to his personality. Victor's persona is a true guide in our process of understanding the user experience.
Our second persona, Rachel Fontes, is a 28-year-old receptionist currently pursuing her nursery diploma. She has been in this occupation for the past 2 years. Her profile was developed from data we collected through interviews and surveys with medical receptionists, exposing the pain points and areas for improvement in their daily routine.
Ideation and Design
After we developed our personas, the ideation process began with the structuring of information architecture, followed by the initial design of the user flow along with low-fidelity screens of the main features. After initial evaluations by the team, I refined a low-fidelity prototype to iterate the user flow for the start of usability testing. Following feedback and analysis, the process of creating higher-fidelity mockups was initiated.
After we developed our personas, the ideation process began with the structuring of information architecture, followed by the initial design of the user flow along with low-fidelity screens of the main features. After initial evaluations by the team, I refined a low-fidelity prototype to iterate the user flow for the start of usability testing. Following feedback and analysis, the process of creating higher-fidelity mockups was initiated.
The Solution
Clinside simplifies and connects clinic management with a system for scheduling appointments, organizing medical data, and maintaining a consultation history. By centralizing the workflow with a straightforward agenda and efficient appointments, it becomes the ideal tool for professionals working in multiple clinics.
Clinside simplifies and connects clinic management with a system for scheduling appointments, organizing medical data, and maintaining a consultation history. By centralizing the workflow with a straightforward agenda and efficient appointments, it becomes the ideal tool for professionals working in multiple clinics.
Usability Testing
Throughout the development of Clinside, user tests were conducted. Based on these tests, we observed and reassessed some of the features and microinteractions, culminating in the final version of the product.
Some of the usability tests that were conducted include:
Low fidelity prototypes: Bi-weekly tests with low-fidelity prototypes were conducted, involving both the development team and technical staff, to gather feedback on the ongoing progress.
Task Success Rate Analysis: Specific tasks were assigned for professionals to perform. Various factors were measured, including the time required to complete these activities and the major challenges encountered while using the app.
Unmoderated testing: we have simulated user groups to assess the platform's functionality and user experience. Participants in these groups engaged with the platform to perform hypothetical tasks, providing valuable insights into the system's usability and effectiveness.
Beta Testing: Before the system's launch, free access was provided to some key users so that all features could be tested in routine situations.
Throughout the development of Clinside, user tests were conducted. Based on these tests, we observed and reassessed some of the features and microinteractions, culminating in the final version of the product.
Some of the usability tests that were conducted include:
Low fidelity prototypes: Bi-weekly tests with low-fidelity prototypes were conducted, involving both the development team and technical staff, to gather feedback on the ongoing progress.
Task Success Rate Analysis: Specific tasks were assigned for professionals to perform. Various factors were measured, including the time required to complete these activities and the major challenges encountered while using the app.
Unmoderated testing: we have simulated user groups to assess the platform's functionality and user experience. Participants in these groups engaged with the platform to perform hypothetical tasks, providing valuable insights into the system's usability and effectiveness.
Beta Testing: Before the system's launch, free access was provided to some key users so that all features could be tested in routine situations.
Learnings
During this project, I learned two main key points about building a brand-new product:
Respecting research: It is crucial to consider each aspect discovered in the research with interviewees. Often, designers prioritize aesthetics, and specific details of people's usage end up unnoticed. One of the initial premises was to make the application intuitive, clean, and easy to use, eliminating the constraints of analyzed competitors.
Failing fast: Through constant usability testing with various user profiles, many initial concepts the team had about the project took a direction not previously considered. I believe the success of the MVP launch was primarily due to the environment of constant evaluation and analysis among the designers, along with the exchange of information with the development team.
Additionally, I discovered the importance of focusing on budget-friendly and schedule-aligned features, while understanding the significant impact of personas in design decisions and stakeholder communication.
During this project, I learned two main key points about building a brand-new product:
Respecting research: It is crucial to consider each aspect discovered in the research with interviewees. Often, designers prioritize aesthetics, and specific details of people's usage end up unnoticed. One of the initial premises was to make the application intuitive, clean, and easy to use, eliminating the constraints of analyzed competitors.
Failing fast: Through constant usability testing with various user profiles, many initial concepts the team had about the project took a direction not previously considered. I believe the success of the MVP launch was primarily due to the environment of constant evaluation and analysis among the designers, along with the exchange of information with the development team.
Additionally, I discovered the importance of focusing on budget-friendly and schedule-aligned features, while understanding the significant impact of personas in design decisions and stakeholder communication.