For hospitals and clinics in India

The modular hospital management system for Indian healthcare.

Patients, appointments, EMR, pharmacy, lab, and billing in one system. Turn on only the modules each hospital needs.

Onboarding is guided by our team. No credit card, no self-serve setup.

Isolated per tenant

PostgreSQL row-level security keeps one hospital's data unreachable from another. Tested on every module, not assumed.

India-resident by design

Built to run on India-resident cloud infrastructure, with health data kept in-region.

Auditable by design

An append-only audit trail records every change and security event, and is kept for 180 days and queryable.

Encryption and least privilege

TLS 1.2 or later on every connection, stored credentials encrypted with AES-256, and a least-privilege architecture.

The model

Buy only what you need. Turn on the rest later.

Each module is installable and billable on its own. A single-doctor clinic can run just patients, appointments, and billing, while a hospital chain runs the full set, all from the same platform.

  • Modules are entitlements per hospital, not code forks.
  • Entitlement and user access are separate levers.
  • Add a module the day the hospital is ready for it.

Modules

Everything a clinic needs on day one.

The seven core modules cover the full outpatient journey, from the front desk to the pharmacy counter. Inpatient, critical care, theater, diagnostics and operations modules are built too, and the catalog marks every module with its status.

Every module marked Built is implemented and in verification ahead of our first release; none is yet running in a paying customer’s hospital. Everything marked Awaiting certification is built and tested but waits on an outside certification, and everything marked Planned is scheduled scope from our product plan. Neither is something you can use today.

One tenant can never see another's data.

Isolation is enforced at the database layer with PostgreSQL row-level security, and it is tested on every module, not assumed. Every meaningful action lands in an append-only audit trail.

  • Row-level isolation per tenant
  • Append-only audit of every change
  • TLS 1.2+ encryption in transit
  • Hosted in India, kept in-region
Reception, nursing and pharmacy staff at work in different parts of a hospital.

Every role sees exactly its own work.

Permissions are checked on the server for every action. Staff see the modules, screens, and data their role allows, and nothing else.

  • Receptionist

    Register patients, book and check in appointments, manage the front-desk queue.

  • Doctor

    Open an encounter, record vitals and SOAP notes with ICD-10-CM coding, and issue prescriptions and lab orders.

  • Nurse

    Chart vitals and nursing notes on the ward, give medicines from the MAR, triage in emergency, and run the sterilizer.

  • Pharmacist

    Dispense against prescriptions and manage stock by batch and expiry, first-expiry-first-out.

  • Lab Technician

    Work the order-to-result worklist, record collection, and enter results against reference ranges.

  • Accountant

    Raise the visit invoice, record part payments, and see the day's collections in the reports.

  • Organization Admin

    Manage users, roles, branches, and branding across the organization, with full visibility inside the tenant.

  • Branch Admin

    Run a single branch, its users and day-to-day operations, within the organization's rules.

Included with every plan

The platform core, in every hospital.

These are never a line item. Whatever modules a hospital turns on, they sit on the same secure, multi-tenant foundation.

Tenant & branch isolation

Every hospital's data is isolated at the database layer with PostgreSQL row-level security. Unlimited branches per tenant.

Role-based access control

Fine-grained permissions per role, per-user overrides, and time-bound grants. Explicit deny always wins.

Module entitlements

Turn modules on per hospital as entitlements, not forks. Entitlement and user access are separate levers.

Immutable audit trail

Every change and security event is written to an append-only log that the application never deletes.

Notifications

One communication service for email, SMS and WhatsApp, with idempotency on every send. Patient SMS and WhatsApp go through your hospital’s own accounts and approved templates.

Financial infrastructure

Invoice, payment, tax, and receipt primitives live in one place; every billing module builds on them.

Standards

Built on the standards Indian healthcare uses.

The codes, data models and rules the product works with today, and what is still ahead, each marked as such.

  • ICD-10-CMDiagnosis coding
  • LOINC®Lab test codes
  • HL7®FHIR®ABDM record formatAwaiting NHA certification
  • TRAIDLTRegistered SMS
  • ABDMABHADigital health IDAwaiting NHA certification
  • NABHQuality indicatorsPlanned
  • ISO/IEC27001Security certificationFuture scope
  • HIPAAUS privacy lawFuture scope
Awaiting NHA certification:
HL7 FHIR®, ABDM and ABHA. Built. ABHA, record sharing and record requests have run end to end in the NHA sandbox, and the records are not yet checked with the official FHIR validator. Not certified by the National Health Authority yet.
Planned:
NABH. On the roadmap. Not built yet.
Future scope:
ISO/IEC 27001, HIPAA. A goal for later. Not started, and not held today.

Names are used only to describe compatibility and imply no endorsement, accreditation or certification. ICD-10-CM is maintained by the US National Center for Health Statistics. LOINC is a registered trademark of Regenstrief Institute, Inc. HL7 and FHIR are registered trademarks of Health Level Seven International. ISO/IEC 27001 is a standard of ISO and IEC. NABH is the National Accreditation Board for Hospitals and Healthcare Providers.

See it running with your own workflows.

Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.