← All case studies
HealthTech
·
iOS & Android
·
2021
MedBaseNet
A daily check-in short enough that people actually do it.
Onboarding - 390
iOS & Android
The 30-second version
0:30 read
Role
Lead Product Designer
Team
1 Product Designer, 1 Database Architect, 3 Cross-Platform Engineers
Timeline
4 months
Platform
iOS & Android
Problem
Over 5.2 million deaths in India annually are linked to misdiagnosis driven by care fragmentation and siloed patient records. With patients seeing multiple uncoordinated specialists, critical medical histories and test results frequently fail to reach doctors at the point of care, leading to severe diagnostic errors.
30+
Production Screens
42
Validated Patient & Provider Surveys
3-tap
Emergency Record Retrival
01 Context
The Healthcare Landscape & The Cost of Misdiagnosis
Out of the 9 million annual deaths recorded in India, an estimated 5.2 million are exacerbated by medical misdiagnosis. When investigating the root causes behind these failures, the breakdown is systemic rather than purely clinical:
Severe Fragmentation of Care: Patients frequently consult multiple independent specialists who order redundant tests in silos. No single clinician possesses a unified, longitudinal view of a patient’s medical trajectory.
Cognitive Overload Under Pressure: Clinicians operate under crushing patient volume. Without structured, instant record retrieval, critical contraindications and chronic histories are regularly missed.
Absence of Patient Data Sovereignty: Patients have minimal ownership over their health records, relying on physical folders, loose lab slips, or proprietary hospital portals that do not interoperate.
Project Mandate & 0→1 MVP Vision
MedBaseNet was initiated to bridge this gap by designing a decentralized electronic health record ecosystem. While the wider architecture included an organization portal and ledger infrastructure, my role as the sole mobile product designer was to conceptualize and deliver the patient-facing mobile application from scratch—creating an intuitive, secure hub for managing medical histories, booking consultations, and providing emergency first-responder access.
02 Research
Desktop vs. Mobile: Designing for High-Stress Utility
Our research revealed that mobile healthcare users exhibit fundamentally different mental models than desktop portal users:
Web Portal Behavior: Exploratory, administrative, seated in controlled work environments with tolerance for high information density.
Mobile Patient Behavior: Hyper task-oriented, hurried, and often triggered by anxiety or immediate physical need. Mobile health interactions happen in pharmacy lines, transit, or acute clinical settings.
Core Design Principle: Zero decorative friction. Minimize steps, taps, and visual clutter to support task completion in under 60 seconds.
Quantitative Discovery & Survey Patterns (N=42)
We deployed targeted discovery surveys across 42 prospective users, segmenting responses across healthcare providers, chronic illness patients, and emergency responders:
78% of respondents reported having to repeat their medical history manually to every new doctor they visited.
Over 65% had lost physical diagnostic reports or lacked access to past lab tests when traveling or switching clinics.
Privacy Paradox: While patients demanded frictionless sharing with new doctors, they strongly resisted centralizing sensitive records without granular, revocable consent.
Jobs-to-be-Done (JTBD) Framework
Because the target audience spanned both tech-savvy young adults and elderly patients managing chronic illness, I moved away from static demographic personas in favor of situational JTBD statements:
JTBD 1 (Emergency Access): When a patient experiences a medical emergency, first responders want to access critical allergies and blood types instantly without bypassing device lockouts, so that they can administer safe, life-saving interventions immediately.
JTBD 2 (Specialist Consultations): When visiting a new specialist for a chronic issue, patients want to provide temporary, view-only access to their verified chronological history, so that the doctor makes a diagnosis based on comprehensive context rather than memory.
JTBD 3 (Data Sovereignty): When managing ongoing prescriptions, users want to track and revoke external clinic access to their private records, so that they retain sovereign control over sensitive personal data.
03 Decisions
1. Low-Fidelity Wireframing & Structural Ergonomics
I began with rapid sketching and low-fidelity wireframes to validate interaction paths before investing in visual styling. The core navigation was anchored to a bottom bar optimized for single-handed thumb-zone reachability, prioritizing four core pillars: Home/Overview, Checkup Timeline, Doctor Discovery, and Security Settings.
2. Frictionless Onboarding & Authentication
Recognizing that cognitive resistance is highest during initial setup, onboarding was engineered for progressive disclosure:
Integrated instant social and biometric sign-ins (Apple ID, Google, and FaceID/Fingerprint).
Required only three essential baseline fields at initial registration, deferring deep medical history inputs until the user actively linked an existing clinic or booked an appointment.
3. Contextual Doctor Discovery & Smart Appointment Booking
Unified Provider Search: Built a search-and-filter index allowing patients to locate vetted clinicians by specialty, hospital affiliation, and consultation availability.
Structured Pre-Consultation Context: When scheduling, patients can select specific past checkups or upload relevant lab reports to attach directly to the booking slot, ensuring the clinician enters the consult pre-briefed.
4. The Longitudinal Checkup History Timeline
To solve the "fragmentation of care" problem, I designed an interactive, chronological card stream organizing multi-specialty checkups:
Each timeline entry condenses diagnosis, prescribing doctor, clinic stamp, and prescription attachments into a scannable summary card.
Color-coded category tags differentiate routine dental visits, diagnostic imaging, pathology results, and emergency events.
5. Cross-Platform UI Style Guide & State Completeness
Rather than designing only "happy paths," I built a modular system of reusable UI components tailored to native iOS and Android conventions:
Developed an end-to-end design token library covering accessible type scales, clinical contrast-safe color ramps, and reusable form molecules.
Designed explicit visual layouts for edge conditions: empty data states, network timeout screens, biometric validation errors, and cryptographic hash confirmation screens (30+ total screens).
04 Result
Delivery & Cross-Functional Impact
Over the 4-month development cycle, MedBaseNet progressed from an abstract concept addressing national health misdiagnosis into a production-ready mobile architecture:
30+ Production Screens Handed Off: Delivered a complete, annotated Figma design spec to mobile engineering teams, complete with responsive layouts and micro-interaction states.
Data Privacy by Design: Solved complex compliance hurdles by architecting off-chain health record storage, persisting only cryptographic verification hashes to protect patient confidentiality.
Streamlined Handshake: Reusable symbols and component libraries reduced front-end UI delivery cycles across cross-platform engineering sprints.
Reflections & Enterprise Scope
Designing Under Strict Constraints: Working in healthcare UX taught me that usability directly impacts human outcomes. Simplicity in high-stress user states is not just an aesthetic choice; it prevents catastrophic user error.
Interoperability as the Future: While MBN successfully established a standalone mobile patient hub, full healthcare transformation requires bridging legacy EHR formats (such as HL7 and FHIR) to allow hospital networks to read and write records without changing their core internal systems.
Screens
Screen 01
1600 × 1000
Screen 02
1600 × 1000
Screen 03
1600 × 1000
Screen 04
1600 × 1000
Next
More case studies.
All case studies →