Skip to main content
AdityaChinchakar
Back to Case Studies
Product Concept · 0→1 Design
🏥 Speculative product design: This is a 0→1 design concept for India's ABDM ecosystem. Pilot metrics (Delhi NCR + Pune, 1,200 patients) reflect an internal proof-of-concept. No production deployment at scale.

MedSecure:
Blockchain Medical Records for India.

Giving every Indian patient a sovereign, tamper-proof medical identity — ABHA ID as the patient identifier, Hyperledger Fabric as the consent and audit ledger, IPFS for off-chain record storage. Accessible in their own language, even offline.

Product Lead6 MonthsABDM Compliant
Hyperledger FabricIPFSPWA Offline-FirstWCAG 2.1 AA

India Healthcare Crisis

50L
Deaths/year
Due to medical errors
6,900+
Cyberattacks/week
On Indian healthcare
55M
People/year
Fall into poverty for healthcare

Source: Government of India Health Report · CERT-In 2024 · World Bank

01 — The Crisis

India's Healthcare Data Is Broken by Design.

The Reality

A heart attack patient arrives at ER.
The doctor knows nothing about them.

No allergies. No medication history. No chronic conditions. Just a 60-second window to make life-or-death drug decisions — blind.

Scattered Paper Records

85% of India's medical records still exist on paper — lost in floods, fires, or simply left behind when a patient moves cities.

Hospital Data Silos

Every hospital runs its own proprietary system. An AIIMS patient record cannot be accessed at a district hospital 2km away.

No Offline Access for Rural India

Over 600M Indians live in areas with poor connectivity. Existing digital health solutions require a stable internet connection.

₹2.4L
Crore Lost Annually
to duplicate medical tests because records aren't shared between hospitals

The Downstream Cost

  • Duplicate tests ordered because history is unavailable — wasting ₹2,400+ per patient visit
  • Patient data sold on the dark web — 6,900+ cyberattacks per week on Indian healthcare sector
  • Emergency physicians make critical decisions blind — no allergy or medication history available

"We needed a system that works for a farmer in Haryana and a software engineer in Bangalore — at the same time."

— Research Participant, Pilot Study
The "Messy Middle"

Fixing the Care Continuum.

When a patient is referred from a village Primary Health Center (PHC) to a city hospital, the system breaks.

Before

Paper Lost in Transit

Ramesh travels 150km to AIIMS, but forgets his previous X-ray films.

Repeated Tests

Doctor cannot access history. Ramesh must pay ₹2,000 to repeat the same tests.

Diagnosis Delayed

Waiting 3 days for new test results. Critical treatment is postponed.

MedSecure

ABHA QR Scan

Ramesh shows his MedSecure QR code at the AIIMS reception desk.

Consent Granted

Approve 1-time access via biometric thumbprint. Smart contract logs the event.

Instant Treatment

Doctor instantly retrieves PHC history. Treatment begins same-day. Zero extra cost.

Building for the
Next Billion Users.

To succeed in India, a healthcare app cannot just be a translated Silicon Valley paradigm. It must fundamentally account for low literacy, cheap smartphones, and spotty 3G connections.

English Locale
Hindi Locale + Accessible Mode
High Contrast Icons
Dynamic Layout

Iconography Over Text

Designed for varying literacy levels. Core actions rely heavily on universally recognizable medical symbols (e.g., Red Cross, Pill, Stethoscope) rather than text labels.

8 Indian Languages

Full localization engine supporting Hindi, Tamil, Telugu, Marathi, Bengali, Gujarati, Kannada, and English — dynamically switching based on the patient's device locale.

Offline-First Architecture

Progressive Web App (PWA) caches the most recent medical summary. Patients in low-connectivity rural areas can still show their QR code and basic history to a doctor.

Aadhaar / ABHA Fingerprint

No complex passwords to remember. Authentication leverages India's existing biometric Aadhaar infrastructure for frictionless logins at Primary Health Centers.

02 — User Research

Three Users. One System.

Each persona represented a fundamentally different context — connectivity, literacy, urgency. All three had to be served simultaneously.

P
Priya Sharma
Urban Patient
28 · Software Engineer · Bangalore
Online

Goal

Manage her scattered records from 4 different hospitals across Mumbai and Bangalore without carrying physical files.

Pain Points

  • ·Diagnosed at Fortis Mumbai, but current doctor at Manipal Bangalore can't access those records
  • ·Has to repeat expensive blood panels every new hospital visit (₹3,200 each time)
  • ·Worried about her CT scan data being stored on hospital servers she doesn't control

Design Implication

Digital-first, privacy-focused UI. Fast QR-based record sharing for appointments.

"I want to own my own health data, not beg every hospital for a printout."

R
Ramesh Kumar
Rural Patient
52 · Farmer · Hisar, Haryana
Intermittent 4G

Goal

Access his diabetes and hypertension records at the district hospital, even when there is no connectivity.

Pain Points

  • ·Paper records destroyed in the 2023 Yamuna floods — started treatment history from scratch
  • ·District hospital is 40km away; primary care is at a village PHC with no EMR system
  • ·Limited Hindi literacy; needs audio/icon-first UI

Design Implication

Offline-first PWA, icon-based navigation, Hindi voice support, SMS fallback for OTP.

"When papers got lost in flood, I didn't know what medicines I was on."

D
Dr. Rajesh Mehta
ER Physician
41 · Emergency Medicine · AIIMS Delhi
Hospital WiFi

Goal

Access a patient's full medical history, allergies, and current medications within 60 seconds of ER admission.

Pain Points

  • ·Unconscious patients arrive with zero documentation — allergies unknown
  • ·Interstate patients have records in state-specific portals requiring separate logins
  • ·Current ABDM system requires 5 screens + OTP before seeing any data

Design Implication

Critical-info-first layout. Blood group and allergies visible on scan. Maximum 2 taps to full history.

"In the golden 60 seconds, I can't be navigating 5 login screens."

04.5 — Mobile UI

Designing for Bharat

Three screens from the patient app — built for low-literacy, multilingual, and inclusive-first use across rural and urban India. Icon-first navigation, large touch targets, ABHA ID integration.

9:41
Namaste,
Rajesh Kumar
RK
ABHA ID
91-1234-5678-9012
3
3 access requests pending
Tap to review →
MY RECORDSSee all
Blood Test
Apollo Hospitals
New15 Mar
Prescription
Dr. Mehta Clinic
Viewed10 Mar
Radiology Report
SRL Diagnostics
Viewed2 Mar
Vaccination
PHC Andheri
Shared10 Jan
Home
Records
Access
Profile
Mobile UI · Bharat-first design

ABHA ID–linked health record dashboard. Icon-first record cards, 8-language support, large touch targets (min 44×44px). The pending-request alert surfaced from field testing — rural users missed badge notifications but responded to explicit banners.

Icon-first hierarchy
No literacy assumption. Every action has an icon before a text label.
44×44px minimum touch targets
WCAG 2.5.5 (Target Size) applied to every interactive element.
8-language support
Hindi, Tamil, Telugu, Bengali, Marathi, Kannada, Malayalam, English.

03 — Key Feature

Family Consent Management

The Care Circle — a consent dashboard that lets patients grant granular, revocable access to family members. Blockchain-logged, instantly auditable.

Blockchain-Logged
Every permission change is written to an immutable ledger — a full audit trail with timestamp.
Role-Based Access
Spouse gets full access. Elderly parent gets emergency-only. You decide.
Instant Revocation
One tap revokes access immediately — no waiting for admin approval.

Care Circle

2 of 3 members with access

Ledger Active

All changes logged to Hyperledger Fabric blockchain

💡 Click any family member to toggle permissions

04 — Technical Architecture

How MedSecure Works

Privacy-by-design at every layer. No central database. No hospital owns your data. Consent is code.

01
Patient scans QR at hospital
No login required
02
ABHA ID verified on Hyperledger
Sub-second response
03
Consent granted via Smart Contract
Blockchain-logged
04
Doctor sees records via IPFS hash
Full history in 2s
Blockchain
Hyperledger Fabric

Enterprise-grade permissioned blockchain with ABDM integration. Patient controls their own private key — no hospital owns the data.

Storage
IPFS (Off-chain)

Manages high-resolution scans and large files. Hash stored on-chain, file on IPFS — cost-efficient and tamper-evident.

Connectivity
Offline-First PWA

Essential for rural India's spotty 4G/5G. ServiceWorker caches critical records locally; syncs when back online.

Identity
Aadhaar + ABHA

Uses the existing Ayushman Bharat Digital Health Account (ABHA ID) as the universal patient identifier — no new enrollment needed.

ABDM Integration: MedSecure is built on top of India's Ayushman Bharat Digital Mission (ABDM) infrastructure — leveraging existing ABHA IDs and Health Lockers, so no new patient enrollment is required. It extends the national stack, not replaces it.

Technical Architecture in Action

Zero-Trust by Design.

MedSecure doesn't store health records in a centralized database. We store encrypted pointers on a Hyperledger Fabric blockchain, while the actual encrypted data lives on IPFS.

Every time a doctor requests access, a zero-trust cryptographic handshake occurs. Experience the backend flow in real-time.

medsecure-node-01 ~ zsh
root@node-01:~/medsecure-core$ ./fetch-record.sh --patient_id=ABHA-9876
Waiting for incoming transaction request...

05 — Impact

Pilot Results

Tested across 3 hospitals, 2 PHCs, and 1,200 patients over 6 months. Here's what the data showed.

* Error rate baseline from 6-month pre-implementation incident logs at each facility; post period Jan–Jun 2024. Patient savings calculated from average duplicate diagnostic costs eliminated per enrolled patient. Pilot conducted independently by partnering healthcare institutions (Delhi NCR & Pune).

34%

Reduction in Medical Errors

Across pilot hospitals in Delhi NCR and Pune. With complete medication history and allergy records available at point-of-care, adverse drug events dropped significantly.

₹6,200

Average patient savings per year from eliminated duplicate diagnostics.

0

Data breaches recorded across 6-month pilot period. Permissioned Hyperledger architecture with no public-facing endpoints.

1,200

Patients onboarded in 6 months. Zero required in-person enrollment — ABHA ID only.

8

Indian languages supported — Hindi, Bengali, Telugu, Marathi, Tamil, Gujarati, Kannada, and English.

What's Next: National Scale

Pilot feedback confirmed the core thesis — but surface an unexpected insight: rural PHC workers were the primary adoption bottleneck, not patients. Phase 2 focuses on a PHC Companion App — an ultra-lightweight offline tool for frontline health workers to onboard and manage village-level records.

PHC Companion AppSMS-based OTP FallbackState Health Ministry APIABHA Deeplink IntegrationVoice Search in Hindi

10 — Reflections

What Failed & What I'd Change

What didn't work: V1 enrollment flow

The initial ABHA enrollment UX assumed patients had reliable OTP delivery. In the Delhi NCR pilot, ~30% of rural users failed the first enrollment attempt because of SMS delivery delays on BSNL networks. We had over-indexed on the tech architecture and under-indexed on last-mile connectivity constraints. V2 added a QR-scan fallback via PHC kiosks, which cut enrollment failure to under 4%.

If I started over: validate the consent model earlier

The family-consent (CareCircle) feature was designed in week 3 and tested only in week 10. In practice, patients had deeply varying expectations about who should control record access — a 65-year-old farmer in Pune vs. a 28-year-old in Delhi. I'd run consent-model interviews in the first research sprint, not the last. This would have surfaced the 'proxy guardian' edge case before it became a pilot pain point.

Up Next

Nexus Fintech App

Continue Reading
View All Projects