Role
Product Designer
Overal work
User Research,
Workshop organization
Facilitation
Design
User testing
QA
Team
1 Product Manager
1 Engineering Manager
1 Data Scientist
1 Data Analyst
5 Developers
1 UX Researcher
1 UX Writer
Doctolib Practice is a practice management software for healthcare professionals. It offers features such as appointment scheduling, patient management, online booking, teleconsultation, and billing.
Context
Why is biology crucial for practitioner?
By studying biology, doctors can develop a deeper understanding of how treatments and medications work and how to diagnose and treat a wide range of medical conditions.
This knowledge helps doctors provide better patient care and improve overall health outcomes.
Business goals
1
Fill the gap versus the competition
2
Improve the NPS
Understanding the user flow
Receiving a biology doc
User’s verbatims from interviews
We don’t remember the patient, we only remember the context if a consultation happened 48 hours ago. More than that and we won’t remember the patient
We don’t have time to write down all the information of each document in each patient’s file, we write down a comment linked to the biology and look at it when the patient’s in front of us.
The design challenge
First focus
Focus on the inbox
An unoptimized main page medical history experience
Adapting to the classification flow
Receiving a biology doc and analyzing it
Features we focused on
UI Rework
Increase the number of items displayed for a quicker analysis of the document
Favorites
Practitioners are following only a few important observations. Favorite will make them stand out allowing a quicker analysis for future results and in the patient file
Patient file’s overview
Reduce the number of actions to get a good overview of the patient’s health straight from the email.
Automatically integrate the data in the patient file
Practitioners can directly add the content of the biology result in the patient file.
A redesigned biology solution
Focus on the crucial value for the patient
Extract the data
Extract and add the biology data in the patient’s file
File the document in the patient’s file
Second focus
Focus on the biology & biometry page
A biometry-centered screen
Change the global analysis of a patient’s biology
Checking the full biology history during the consultation
Features we focused on
Chronologically organized
Get a first grasp of the last results and increase the usability.
Results organized as they are used to
They are used to the paper and what they have been taught.
Optimized navigation
Optimized navigation
Favorites
Practitioners are following only specific observations. Favorite will make them stand out allowing a quicker analysis.
A global table
Automatic codification
As we were only starting automatic codification
thanks to machine learning, we needed a way to
validate pre-entered codification.
Modify
Explanation
Third focus
Focus on impact in consultation
A biometry-centered feature during consultation
Adapting to the consultations' needs
Check and add multiple biology results
A new table during the consultation + batch adding
Last 2 results
+ history
User’s verbatims from interviews
The biology is nice, I don’t think a lot of softwares are doing this.
Personally, I like the new layout: less scrolling, the option of choosing the unit, and still the option of adding favourites.
Thanks
Thanks to the developers for making it possible to change the unit for a particular variable (mmol/l blood glucose in gr/l for example) and, what's more, the change is memorised! Super
Before, blood test results were unclear and hard to understand. Now, with the new analysis system, it's easier to get a comprehensive understanding of the results. It’s more intuitive.
Reflections
I would like to share with you that this project was my first introduction to Machine Learning and the concept of providing suggestions to users.
This experience led to some interesting conversations within our team about the magic of "AI" as well as how the user can correct it if there are any errors in the results.
Over the course of 6 months, I was able to learn the importance of launching early, continuously improving, and always keeping the user's satisfaction in mind by some delighting improvements on top of the main project.
Start designing without AI as a parameter
When starting designing, my main goal was to simply start designing as if AI was not part of the final solution.
This led to a feature the user had control over before having to take
Big sprints, small delights
We had to divide the full project into different sprints, that we could then beta test. When a big chunk of feature was launched, we would monitor while increasing the delight by adding some small, awaited feature here and there.