Medyntra

Medyntra is hospital and clinic management software that we designed, built and run ourselves. It brings registration, appointments, billing, reports, notifications and staff permissions into one secure, multi-tenant platform, with AI insights that explain a hospital’s own numbers in plain language. Building our own product keeps us honest: every architectural decision we recommend to clients, we have already lived with in production.

Clinics and hospitals in India often run on several disconnected tools. Patient details are copied between registration, scheduling and billing, collections are hard to see without a spreadsheet, and leaders wait for reports instead of seeing the day at a glance. A replacement has to be fast to learn for front-desk staff, strict about who can see what, and dependable enough to run a working hospital.

We scoped the core HMS first — patients, appointments, doctors, departments, billing, reports, roles and audit — and treated AI as a layer on top of trustworthy data rather than the headline. Pricing is an initial package plus a simple monthly maintenance fee with no per-user charges, and setup, data onboarding and training are included, because adoption is the hardest part of hospital software.

Every module shares the same patient, the same schedule and the same numbers, so nothing is entered twice. The dashboard answers the questions an administrator asks every morning — registrations, appointments, collections and dues for any period, compared with the last. Ask Medyntra answers operational questions in plain language and is deliberately limited to operations: it never gives clinical advice.

A dark, low-glare workspace designed for long shifts: one consistent design system, a clear type hierarchy, tables that stay readable at density, and charts that always have a table view. Light and dark themes are both first-class.

A pnpm and Turborepo monorepo with separate web and admin applications sharing typed packages. Each hospital is its own tenant: the organisation is derived from the signed-in session, never from the browser, and PostgreSQL row-level security returns nothing outside it — with automated cross-organisation access tests on every change. Permissions are checked on the server for every action, and sign-ins, permission changes and administrative actions are written to append-only audit logs. Local development runs an embedded PostgreSQL and tests use an in-process database, so the whole platform runs without external services.

Designed with WCAG 2.2 AA as the target: every chart has an equivalent table, interactive elements are keyboard operable with visible focus, and colour is never the only signal. One design system keeps every screen learnable.