Why I Started NuroVed: Fixing the Small Fractures in Everyday Healthcare
How seeing doctors battle disjointed software and patients lose vital records convinced me to build a simpler, patient-centric healthcare platform.
✦ Early architecture sketches of NuroVed patient record sync, drafted on grid paper in Ahmedabad.
Most software problems look trivial from thirty thousand feet. When you examine healthcare software through investor pitch decks, you see polished dashboards, automated billing, and promises of end-to-end hospital management. But when you sit in an actual clinic in Ahmedabad, the reality looks completely different.
Doctors spend more time clicking through poorly organized desktop menus than looking their patients in the eye. Meanwhile, patients carry manila folders stuffed with loose lab reports, paper prescriptions with fading ink, and imaging CDs that nobody has a disc drive to read anymore. When someone switches doctors or visits an emergency room, their medical history effectively resets to zero.
That disconnect is why I founded Promacle, and it is why NuroVed became our primary focus. We did not set out to build an all-encompassing enterprise hospital system that takes six months of training to understand. We set out to fix the immediate, painful breakdown: making a patient's health records portable, clean, and immediately comprehensible to any doctor they consult.
Building healthcare software teaches you humility very quickly. In consumer tech, a small bug causes a minor user annoyance. In medical software, an incorrect allergy note or a delayed record sync can directly compromise someone's care. That responsibility forces you to build with extreme care, verify your schemas rigorously, and throw away any feature that adds confusion.
NuroVed is still in active development, but the core thesis remains unchanged: healthcare software should feel invisible to the patient and effortless for the practitioner. Every line of code we write is tested against that standard.
In medical software, an incorrect record sync can compromise care. That responsibility forces you to build with extreme care.— Fazil Malek
What I Learned
Direct takeaways and practical principles recorded from this experience:
- 1
Real pain points live in clinics, not pitch decks
Spending time observing actual consultations reveals that software usability in healthcare is a clinical safety issue, not just a design preference.
- 2
Simplicity is a moral requirement in health tech
Complex interfaces create data entry fatigue. If a system requires a multi-day onboarding course, doctors will revert to paper.
- 3
Patient ownership over data is the foundation
When patients hold their encrypted records, interoperability happens naturally across different clinics and specialists.

Fazil Malek
Founder @ Promacle • B.E. Computer Engineering @ GTU
Indian entrepreneur and Computer Engineering student at Sal College Of Engineering backed by Gujarat Technological University (GTU). Founder of Promacle, builder of NuroVed, and footballer based in Ahmedabad.
Related Notebook Stories
Building While Being a Student: Managing Code, Classes, and Founder Mode
Reflections on pursuing a Bachelor of Engineering at Gujarat Technological University while running Promacle. Lessons on practical execution vs theoretical syllabi.
How I Approach Building Products: Starting on Paper Before Writing Code
My tactile design philosophy: why I start every system architecture and interface in physical notebooks before jumping into Figma or writing code.