12  The Aarokya Platform: Infrastructure for a Healthcare Ecosystem

12.1 More Than an App

There is a temptation, when describing what Aarokya is, to call it an app. And it is an app — a beautifully designed, deeply intelligent app that sits in a person’s pocket and connects them to healthcare.

But calling Aarokya just an app is like calling UPI just a payments app. UPI is not an app. UPI is infrastructure — a set of rails upon which an entire ecosystem of financial services has been built. Banks, fintech companies, merchants, government programs, and hundreds of millions of individuals all connect through UPI’s open architecture. The power is not in any single application. The power is in the platform.

Aarokya is designed with the same ambition. It is platform infrastructure for healthcare — a set of open, intelligent, secure rails upon which an entire ecosystem of healthcare services can be built, connected, and scaled.

An employer can plug into Aarokya to offer health benefits. A gig platform can integrate Aarokya’s SDK to enable micro-contributions. An insurer can connect through Aarokya’s API to offer coverage products. A pharmacy node can use Aarokya’s protocols to deliver local care. A government program can route benefits through Aarokya’s accounts. A hospital can receive patients with complete, Aarokya-maintained health records.

The app is the surface. The platform is the substance.

12.2 Core Platform Components

Aarokya’s platform is composed of interconnected systems, each essential to the whole.

flowchart TB
    subgraph UL["👤 User Layer"]
        U1["Individuals &<br/>Families"]
        U2["Gig Workers"]
        U3["Employers &<br/>Gig Platforms"]
        U4["Pharmacies &<br/>Care Nodes"]
        U5["Hospitals &<br/>Providers"]
    end

    subgraph AL["📱 App Layer"]
        A1["Mobile App<br/>Voice · Chat · Local Languages"]
        A2["Provider Portal<br/>Dashboard · Case Management"]
        A3["Partner Portal<br/>SDK · Integration · Analytics"]
    end

    subgraph IL["🧠 Intelligence Layer"]
        I1["AI Health Assistant<br/>Multilingual · Multimodal"]
        I2["Triage & Routing<br/>Engine"]
        I3["Risk Intelligence<br/>& Analytics"]
        I4["Preventive Care<br/>Workflows"]
    end

    subgraph DL["🗄️ Data Layer"]
        D1["Health Records<br/>ABHA-Linked"]
        D2["HSA Ledger<br/>Contributions & Balances"]
        D3["Claims &<br/>Disbursements"]
        D4["Provider &<br/>Network Registry"]
    end

    subgraph EL["🔗 Integration Layer"]
        E1["India Stack<br/>Aadhaar · UPI · ABHA<br/>DigiLocker"]
        E2["Insurance<br/>Partners"]
        E3["Laboratory<br/>Networks"]
        E4["Hospital<br/>Systems"]
    end

    UL --> AL
    AL --> IL
    IL --> DL
    DL --> EL

    style UL fill:#2780e3,color:#fff,stroke:#1a5fb4
    style AL fill:#3d8cf8,color:#fff,stroke:#2780e3
    style IL fill:#6a1b9a,color:#fff,stroke:#4a148c
    style DL fill:#1565c0,color:#fff,stroke:#0d47a1
    style EL fill:#339af0,color:#fff,stroke:#1a5fb4

Figure 12.1: Aarokya platform architecture — from users to external systems

Each layer builds on the one below it, designed to be modular, extensible, and open to integration.

12.3 The Health Savings Account Engine

At the financial heart of Aarokya is the HSA engine — the healthcare-dedicated account described in earlier chapters, now seen from the platform layer. Here it is not just a savings product but a high-throughput ledger system processing potentially millions of micro-transactions daily.

The engine accepts contributions from any source — individuals, employers, gig platforms, family members, CSR programs, tips, government benefits — each tracked and attributed. It handles transactions as small as one rupee, because meaningful healthcare funding can be built from daily, per-task increments. And because the account belongs to the individual rather than any employer or platform, the engine must support full portability across jobs, cities, and life stages.

Speed, reliability, auditability, and deep integration with India’s payment infrastructure — these are the engineering demands. The HSA engine is the financial rail upon which everything else runs.

12.4 Contribution and Payment Rails

Money flows into and out of the HSA through rails designed for flexibility, automation, and trust.

Inbound, the system handles recurring salary deductions, per-task gig platform contributions triggered via API, UPI-based self-contributions, family transfers across geographies, CSR disbursements, government benefits, and even customer tips directed to a worker’s health account.

Outbound, the rails process insurance premium payments on schedule, provider payments to pharmacies, hospitals, labs, and teleconsultation services, claims disbursements from insurers, and reimbursements.

All of this is built on UPI and India’s existing payment infrastructure, extended with healthcare-specific logic: eligibility verification, fraud detection, constrained-purpose spending rules, and real-time balance management.

12.5 Insurance Integration Layer

Aarokya does not aim to replace insurance companies. It aims to make insurance accessible, affordable, and aligned — and to provide the infrastructure that insurers need to serve populations they have historically found too risky or too expensive to cover.

The integration layer handles premium management with automated collection from HSAs and installment support. It provides anonymized, consented health data that enables better risk assessment and more inclusive underwriting. It supports digital-first claims processing with AI-assisted verification. And it accommodates product flexibility — traditional indemnity, micro-insurance, community-rated pools, hospital-aligned plans, and hybrid models — all within IRDAI regulatory compliance.

For insurers, Aarokya is a distribution channel, a data partner, and an operational platform. For users, it is the interface that makes insurance simple — something that works quietly in the background, funded incrementally from the HSA, activated seamlessly when needed.

12.6 Intelligence Layer

The AI capabilities described in the previous chapter — multilingual health intake, pattern detection, triage and routing, preventive care workflows — are powered by this platform architecture. The intelligence layer sits between the app and data layers, providing the computational and clinical reasoning that makes Aarokya more than a record-keeping system.

What matters at the platform level is how this intelligence connects to everything else: how the AI draws on the health record store, how its triage decisions route to the provider network, how its risk detection feeds the analytics engine, and how all of this happens within the safety rails — never diagnosing, never prescribing, always routing to human judgment when it matters.

Building AI for 1.4 Billion People

Aarokya’s AI must work for a farmer in Madhya Pradesh speaking Hindi with a Bundelkhandi inflection. It must work for a grandmother in Kerala who speaks only Malayalam. It must work for a teenager in Delhi who code-switches between Hindi and English mid-sentence. It must work for someone who has never used a smartphone before, and for someone who uses five apps before breakfast.

This is not a narrow technical challenge. It is a design philosophy: the AI adapts to the person, not the other way around.

12.7 Provider Network Management

Healthcare is ultimately delivered by people and institutions. Aarokya’s provider network management system ensures that doctors, nurses, hospitals, pharmacies, and labs are discoverable, connected, quality-assured, and properly compensated.

The system maintains a comprehensive provider registry with credentials, capabilities, and performance metrics. When a patient needs care, intelligent matching considers condition, location, language, availability, insurance coverage, and patient preference. Ongoing quality assurance tracks outcomes and patient feedback. And real-time scheduling manages capacity across teleconsultations, in-person appointments, and pharmacy node services.

12.8 Claims and Disbursement Engine

When healthcare costs are incurred, the claims engine handles financial resolution — quickly, transparently, and with minimal friction.

Claims are submitted digitally at the point of care, with no paper forms or postal delays. Routine claims are assessed automatically against policy terms, provider agreements, and treatment protocols — anomalies flagged for human review. Wherever possible, payments flow directly between the HSA or insurer and the provider, so the patient never handles large sums out of pocket. And pattern analysis across the network identifies billing anomalies and potential fraud, protecting both patients and the system.

The patient sees exactly where their claim stands at every step — what has been approved, what is pending, and what their remaining balance covers.

12.9 Analytics and Risk Intelligence

Aarokya’s data — aggregated, anonymized, and consent-governed — creates a powerful lens on population health.

For individuals, analytics means personalized health insights: risk trajectories, preventive care adherence, health trends over time. For providers, it means practice intelligence: common conditions in their area, treatment outcomes, follow-up rate gaps. For insurers, it means actuarial intelligence: better risk models, earlier intervention opportunities, outcomes-based pricing. For policymakers, it means evidence: real-time data on healthcare access, utilization, outcomes, and costs — disaggregated by geography, demographics, and socioeconomic factors.

All of this is built on a foundation of privacy, consent, and anonymization. Individual data is never shared without explicit consent. Population-level insights are always anonymized and aggregated. The platform generates intelligence, not surveillance.

12.10 SDK and API Layer

This is where Aarokya’s platform ambition becomes most tangible. The SDK and API layer transforms Aarokya from a product into infrastructure.

The API enables any authorized system to interact with Aarokya programmatically. A gig platform can create an HSA for a new worker and begin automated per-task contributions. An employer can integrate health benefits into their HR system. A hospital can pull a patient’s health record with consent during admission. An insurance company can push policy details and process claims. A government program can route health subsidies directly into citizen HSAs.

The SDK makes integration simpler for common use cases. A ride-hailing app embeds the Aarokya widget, allowing riders to direct tips to their driver’s health savings. A gig platform adds a health benefits dashboard using Aarokya’s UI components. A corporate wellness program integrates screening tools into their employee portal.

The Platform Test

A platform is real when others build on it — when the ecosystem it enables is larger than the product itself. Aarokya’s SDK and API layer is designed to pass this test. The goal is not to build every health service ourselves, but to build the rails that make a thousand health services possible.

12.11 Data Architecture: Privacy-First, Consent-Driven

In a system that handles the most sensitive information a person has — their health — data architecture is not a technical afterthought. It is a moral obligation.

ABHA-linked identity — Every health record is linked to the user’s Ayushman Bharat Health Account, providing a nationally standardized, verifiable health identity. This ensures portability, interoperability, and alignment with India’s national health data architecture.

Consent-driven access — No provider, insurer, employer, or third party can access a user’s health data without explicit, informed, revocable consent. Consent is granular: a user can share their blood pressure history with their doctor without sharing their mental health notes. Consent is logged, auditable, and always under the user’s control.

Minimal data collection — Aarokya collects only the data necessary for the services the user has opted into. No background data harvesting. No behavioral tracking for advertising. No selling of health data to third parties. Ever.

Privacy by design — Encryption at rest and in transit. Anonymization for all analytical use. Strict role-based access controls. Regular security audits. Compliance with India’s data protection regulations and international health data standards (HL7 FHIR).

A Non-Negotiable Commitment

Health data is sacred. A person’s medical history, their conditions, their medications, their fears — this is among the most intimate information that exists. Aarokya treats it accordingly.

There will be enormous commercial pressure to monetize health data. That pressure will be resisted. Absolutely and permanently. The moment health data becomes a product, the trust that makes the entire system possible will be destroyed.

Aarokya’s data commitment: your health data belongs to you. Period.

12.12 Integration with India Stack

Aarokya is not being built in isolation. It is being built on top of India’s extraordinary digital public infrastructure — and designed to extend it into healthcare.

Aadhaar provides the identity layer. Verified, biometric, universal. Aarokya uses Aadhaar-based authentication to ensure that health accounts, records, and benefits reach the right person — securely and without duplication.

UPI provides the payment layer. Instant, low-cost, interoperable. Every contribution to an HSA, every provider payment, every insurance premium, every claims disbursement flows through UPI rails — making healthcare finance as frictionless as splitting a dinner bill.

ABHA provides the health identity layer. A standardized health ID that links records across providers, institutions, and systems. Aarokya’s health records are ABHA-native, ensuring that a patient’s history is portable and accessible wherever they seek care.

DigiLocker provides the document layer. Health reports, prescriptions, insurance documents, and medical certificates — all stored securely, all accessible when needed, all verifiable.

Together, these form the foundation upon which Aarokya builds. India has already invested billions in this digital public infrastructure. Aarokya’s role is to use it — faithfully, responsibly, and with purpose — to deliver healthcare outcomes that justify that investment many times over.

12.13 Security and Compliance

Building healthcare infrastructure demands security practices that go beyond industry norms. Aarokya’s approach spans three dimensions.

Technical and operational security — End-to-end encryption for all data in transit, AES-256 encryption at rest, multi-factor authentication for all access, regular penetration testing, and bug bounty programs. Role-based access controls ensure that each participant can only access the data they need. Comprehensive audit trails log every data access event. Incident response protocols are tested and updated quarterly.

Regulatory compliance — Full alignment with India’s Digital Personal Data Protection Act, IRDAI regulations for insurance operations, National Health Authority standards for ABHA integration, and international health data standards (HL7 FHIR) for interoperability.

Ethical governance — An independent data ethics board reviews Aarokya’s data practices, AI models, and privacy policies. Regular transparency reports are published publicly. User-accessible dashboards show what data is held, who has accessed it, and for what purpose.

12.14 Open Source, Open Architecture

Aarokya is open source. The code, the platform, the protocols — all built in the open, inspectable by anyone, improvable by the community, and adaptable for any context or country.

This is not incidental. It is foundational. Healthcare infrastructure that affects hundreds of millions of lives should be transparent, auditable, and collectively owned. Open source makes trust verifiable rather than promised.

Aarokya inherits this ethos from two proven open source projects built by the same engineering organization:

• HyperSwitch — an open source payments orchestration system handling transactions at scale across multiple gateways and geographies. It proved that financial infrastructure demanding the highest standards of security, reliability, and compliance can be built in the open. Aarokya’s backend — the HSA engine, contribution rails, and payment integration — inherits HyperSwitch’s architecture and engineering rigor.

• Namma Yatri — an open source ride-hailing platform serving millions of rides daily in Indian cities. It proved that consumer-facing apps with beautiful UI/UX and massive transaction volumes can be built and operated as open source. Aarokya’s user experience — multilingual, low-bandwidth-friendly, accessible to first-time smartphone users — inherits Namma Yatri’s design DNA.

The architecture is deliberately designed to be built upon, extended, and integrated with. Not open in the sense of exposing user data — that is protected with the highest standards. Open in the sense that the platform is designed for ecosystem participation.

This is a strategic choice rooted in a simple insight: no single organization can build all the healthcare services India needs. The need is too vast, the contexts too varied, the innovation required too diverse.

What a single organization can do is build the rails — the identity, the accounts, the records, the intelligence, the connectivity, the trust — and then invite the ecosystem to build on top of them.

A health-tech startup building a diabetes management program shouldn’t need to build an HSA from scratch — they should plug into Aarokya’s. A rural health NGO shouldn’t need to build their own health records system — they should use Aarokya’s. A state government launching a maternal health initiative shouldn’t need to create a new digital identity — they should leverage ABHA through Aarokya.

The philosophy is simple: build the rails, and let the ecosystem grow. The more participants on the platform, the more valuable it becomes for everyone. The more services available, the more reasons for users to engage. The more data flows through the system (with consent, always), the smarter the AI becomes. The smarter the AI, the better the health outcomes.

This is the flywheel. And it begins with open, robust, trustworthy infrastructure.

12.15 The Healthcare Operating System for India

Let us step back and see the whole.

Aarokya is a Health Savings Account that makes healthcare funding work for everyone. It is a contribution engine that allows individuals, employers, platforms, families, and communities to participate in building someone’s healthcare security. It is an insurance integration layer that makes coverage accessible and aligned. It is an AI health assistant that amplifies doctors and nurses tenfold. It is a provider network connecting pharmacies, hospitals, labs, and care nodes into a coherent system. It is a claims engine that resolves costs transparently. It is an analytics platform generating health intelligence at population scale. It is an SDK and API that lets any organization build on these rails.

It is, in essence, a healthcare operating system.

Not in the grandiose sense of controlling everything. In the humble, powerful sense of providing the foundational services — identity, accounts, records, intelligence, connectivity, payments — that everything else needs in order to function.

Just as Android provides the operating system upon which millions of apps run, Aarokya provides the operating system upon which a healthcare ecosystem can grow. The platform handles the infrastructure. The ecosystem handles the innovation. And the patient — always the patient — benefits from both.

What an Operating System Does

An operating system doesn’t do everything. It does the fundamental things that everything else depends on — and does them reliably, securely, and at scale.

Aarokya’s role as a healthcare operating system is to provide:

• Identity — know who the patient is (ABHA-linked, Aadhaar-verified)
• Accounts — manage their healthcare funds (HSA engine)
• Records — maintain their health history (consent-driven, portable)
• Intelligence — understand their health context (AI-powered)
• Connectivity — link them to care (provider network)
• Payments — handle the money (UPI-based, insurance-integrated)
• Extensibility — let others build on top (SDK/API)

Everything else — the specific health programs, the innovative care models, the specialized services — can be built by the ecosystem on these foundations.

India built UPI and gave the world a model for digital payments infrastructure. India built Aadhaar and created the world’s largest digital identity system. India built CoWIN and administered the world’s largest vaccination drive.

Aarokya aspires to the same lineage: India’s healthcare operating system — built for Indian realities, powered by Indian digital infrastructure, and designed to ensure that affordable healthcare reaches everyone who needs it.

The rails are ready. The architecture is open. The ecosystem is waiting.

Aarokya is not just an app. It is the infrastructure upon which Indian healthcare can be rebuilt — open, intelligent, and built to serve every citizen.