Clodoc brings patients, doctors, pharmacists, and community health workers together in one connected ecosystem — making healthcare feel less complicated, with experiences simple and familiar enough for everyone to navigate.
I'm sharing what I can. For more details, feel free to contact me at digisha.vp@gmail.com or @LinkedIn
Clodoc is a healthcare platform connecting doctors, patients, and pharmacies — and the people around them who keep care running.
It didn't start with a feature list. It started with conversations: with doctors between patients, by observing pharmacy operations, with real people in our neighbourhood, watched and understood up close.
AI is used only where it genuinely reduces complexity for doctors and patients — never layered on as a feature for its own sake.
Built to fit how care actually happens, not to force doctors and patients into a workflow that's easier to code than to live with.
Working under the mentorship of our lead designer, my part in Clodoc has grown from understanding the problem to owning a module end-to-end.
I started as a junior UX/UI designer, working under the mentorship of our lead designer.
My first job wasn't to design — it was to understand. I did deep research into the healthcare industry, interviewed our stakeholder doctors directly, and ran role-plays and brainstorming sessions with a colleague to step into the shoes of the people we were designing for — doctors, patients, and everyone in between.
From there, I moved into ideation, wireframing, and visual design for the doctor-patient app, alongside broader research into healthcare workers around the world — to make sure what we were building held up beyond just our own context.
Today, I'm working independently on the pharmacy module — owning it end-to-end, from ideation to final visual design — still under my lead designer's mentorship, but with my own hands fully on the wheel.
What I can share about the work itself, without breaching what's under NDA.
Contributed deep secondary research on pharmacy operations and community health worker systems across India and globally — shaping the design direction and information architecture for Clodoc's pharmacy and community health platform.
Doctors and patients had no shared view of where a complex second-opinion case stood once it left the queue — creating uncertainty on both sides.
Before — no visibility
After — staged tracker
Direction: gave doctors and patients a shared, plain-language status — without exposing clinical detail — and reduced how often patients had to ask for updates.
Led ideation and design for prescription template generation inside a doctor-facing AI-assisted chat interface, focused on feedforward and feedback cues that a busy, time-constrained doctor could read at a glance.
Prescription generating flow
Independently leading the pharmacy module — ideation to final visual design — with mentorship from the lead designer and research-backed decisions at every step.
The goal is to get something out and test it, not get it flawless on the first try.
Collect them, don't fear them.
A clear problem statement holds no suggestions — just what's wrong.
It helps the work, and it helps everyone's headspace.
And don't fall in love with your first idea — stay open to it changing.
The obvious ones are usually worth asking anyway.