Comprehensive Healthcare and Wellness App
To build a comprehensive ayurveda centric healthcare ecosystem that streamlines prescription writing, patient management, scheduling, session management for Patients and Doctors
Concept Building
UX Research
System Mapping
UI Testing
Wireframe
Web Development
Hi-fi
April’24- Nov’24 (Design, Development in progress)
About the Company
A comprehensive healthcare and wellness platform offering Ayurveda-centric services. The company provides personalized health packages including diet plans, consultations, and fitness sessions. The business model involves also involves partnerships with Panchakarma centers to deliver a holistic wellness experience. They also provide non-session, concern based consultancy. They also operate an e-commerce platform for Ayurvedic products and medications.
Please note:
This is a Client of the company I work for, hence specific project details are confidential.
My Role
I was responsible for Managing, Concept Building and Designing the project from scratch. I and Database dev conceptualized ideas along with schema generation. I collaborated closely with full-stack developers to translate designs into functional web and mobile applications.
Challenges
1
User-Centric Design
Seamless data synchronization across multiple user roles and platforms, optimal taskflows with varying access levels and permissions for each user group
2
Platform Adaptability
Decreased engagement of the web-app among doctors. Explore the potential benefits of a simplified, mobile-optimized dashboard
Users
Patients
Health Professional (HP)
Doctors
Dieticians
Fitness and Wellness Professional
Wellness Centres and Resort
Clinic
Admin
Brief of Work
Service Design and Deliverables
The client's Service Design sheet facilitated our understanding of their fundamental needs and specific requirements. Deliverables were categorized based on various stakeholders and their respective functionalities. Streamlining each stakeholder's tasks was essential to minimize redundancy and simplify the process.
Deliverable sheet for all users, System Diagram, DB schema
Project Overview
1
Schedular
Appointment scheduling management and HP availability management.
2
Consultation
Patient data management, prescription generation, and medical history access.
3
Messaging System
Bidirectional(sometimes uni) messaging system with transparent initiation tracking.
4
Patient Programme System
Tailoring programs to meet specific patient requirements( an alacarte system) (WIP)
Primary Research
Doctor Prescription
Most Doctors dont Fill Investigation and Examination fields
Repetitive fields
7-10 min
Digital Prescription
2-3 min
By hand Prescription
Schedular Observation
Admin Observation
Information Overload
Wearing different hats
Competitive Research
Studied various apps specific to healthcare/ wellness sector, schedulers and appointment apps and also react libraries. These were analyzed based on usability patterns and identified areas of ease as well as potential pitfalls for improvement.
Insights and Learnings
Insights
Automated booking, realtime availability
Description for every feature
Customising scheduling page
Consultation Template
Insights
Time efficient prescription(part of consultation) writing
Dislikes
Confusing task flow related to prescription like Noting down vitals, patient details, adding reports
Insights
Time efficient prescription(part of consultation) writing
Easy task follow for prescription
Dislikes
Though extensive use of quick actions but confusing CTAs
Insights
Customizable column headers in tables
Insights
Easy to follow task and User flow, no user interaction friction
Smart Prescription
Simplified profile creation by breaking down the steps
Learnings
-Progressive disclosure -Any form filling should be break down of smaller steps.
-Prescription comes with all other tasks around it, though it has an extensive list, is equally necessary and should not break the workflow.
-Recognition over Recall - Designing screens with actions related together so as to have a consistent and justified task flow.
User Persona
Building a set of User Persona gave us the depths of divided work and opportunities.
Information Architecture
Wireframe and Ideations
Filling the gaps
User Journey and Use Cases helped me to cover all loop holes and exceptions specially for schedular/ appointment functionality.
Making specific functionality cases or journeys helped in managing bottleneck situations effectively.
Tables and Diagrams
Few of the Task Flows
1
Schedular
This functionality of the ecosystem was an crucial and challenging. An appointment can be scheduled by any of the users(admin only schedules on request). Connecting all users with diverse use cases became challenging.
What are the Problems faced?
1
Role-Based Workflows balancing with Permissions
Data flows from one user to another with different user access was challenging with UI perspective as well as working.
2
Cognitive Load
Streamlining the user interface slot viewing, actions to it, messaging system to provide essential features without overwhelming users
Setting availability
Health Professional sets their availability on their calendar
Edit access by
Scheduling an Appointment
Booking the slot for a patient
Booking by
Actions to Appointment- Reschedule, Cancel or Assign a new doctor
Further functionalities
Cancelling/
Rescheduling by
Assigning a new HP by
Understanding the Problem
Solutioning
1
Easy to Perceive Day view Scheduler
To make it readable at a glance with maximum information, day view cells were color coded and tagged appropriately for maximum perception.
2
Quick appointment booking
There are different types of booking a doctor, by concern, by subscription, by doctor, on app, on website, on call, in every case maximum information has to be achieved with minimum inputs.
3
Setting Availability- Accessible
A Health Professional has to set availability. To make it convenient ideations were around whether they set availability or non-availability, per day, weekly, custom and beyond.
Snippets of final Screens
2
Consulting
Consulting majorly consists of
Noting down Vitals
Written Primarily by Front Desk Person
Writing a Prescription
Written Only by Physician
What are the Problems faced?
1
User Interface and Navigation
A HP while writing a prescription goes through the vitals, sometime test reports and also past prescription records.
2
Extensive Data Entry
Complain, Medicines(additional fields for Ayurveda Doctors), Tests, etc that too by multiple users
3
Time Efficiency
Multiple users can lead to conflicts or no data retrieval.
Thought Process
To make thinks clear I made User journey from HP’s perspective and Patient Perspective to find loopholes and pitfalls around Consultation
Three steps that I can think of closely related to Prescription
Before Meeting a HP
Consultation List
During the Meet
Prescription
After the Meet
Next Visit, View, Actions wrt prev. visit
Primary User Journey
Booked an Appointment
Vitals( by Front desk, patient, Doctor)
Prescription
Add Reports
Follow up
No Follow up
Add Reports
New Consultation( Patients with no bookings
Vitals( by Front desk, Doctor)
Prescription
Follow up
No Follow up
Add Reports
Upcoming Patients’ Prescription
Booked an Appointment
Cancelled
Rescheduled
Assigned to new HP
Empty Prescription Generated
Follow up
No Follow up
Add Reports
Visited Patients’ Prescription
Vitals
Prescription
(non-editable)
Follow up
No Follow up
Add Reports
No Show
Booked an Appointment
Cancelled
Rescheduled
Assigned to new HP
Empty Prescription Generated
Solutioning
1
User Behavior Modelling
Mimicking Physician’s writing behaviour -
Quick & Continous
2
Flexibility of Use
Data entry and view for Patient in single page for uninterrupted experience
Iteration 1
Vitals and Prescription Clubbed together, General History of patient missing.
What was missing?
General History was not accessible easily.
Iteration 2
Vitals and Prescription clubbed, view of General History
What was missing?
Since vitals are fields that are preferably filled by Front Desk should be separated.
Difficulty in Input fields with sticky General History Overlay
Iteration 3
Vitals and General History clubbed, with layout changes in Prescription
What was missing?
Layout changes were made separating Initial Analysis( Complaints, Diagnosis) and Post Analysis(Rx, Tests to take, Next visit) but looked cramped up
Final Iteration
Snippets of final Screens
3
Messaging Sytem
The messaging system encompasses notifications, reminders, and informative messages exchanged among users. To ensure transparency, both sides of users are informed about who initiated the process.
Necessity of Messaging System?
We all know what notification and reminders are but additionally, we required an informative message exchange so that any of the user gets to know who is the initiator.
View of message, Flow of message with one of the examples
Messaging System for Detailed Panel
Set of Messages
Action doer
Receiver
When does the action happen
Frame name
Snippet of Messaging System Detailed functioning
Snippets of final Screens
4
Patient Pragramme System
It is a part of Patient Portal which consists of
Booking a Consultation
One-on-One consultation
Buying a Programme
Package of Doctor, Dietician, Fitness Trainer and Wellness Expert with varying month duration
This is going to be part of phase two with additional overall features.
Thank You
Thanks for Visiting!