Pricing that grows with your network

Yes. A tenant (the hospital admin org) owns one or more hospitals, and every record — users, patients, doctors, appointments, bills — is scoped to that tenant and usually to a specific hospital.

Permissions are capability-based — expressed as feature.action (e.g. patients.create) rather than blunt role checks. The six roles each map to a set of capabilities, so every screen and action respects fine-grained rights.

Yes. Hospitals support a branch hierarchy and per-hospital departments, plus settings for letterhead, GSTIN and logo — used on printed prescriptions.

A doctor starts a consult from an appointment, records clinical notes and a follow-up date, and on completion MedOps atomically generates the prescription and the consultation-fee bill. Prescriptions print on hospital letterhead with the doctor's digital signature.

Fully. Admit a patient to a vacant bed with transactional vacancy and duplicate-admission guards, run doctor rounds (vitals + notes), write IP prescriptions, then discharge or transfer beds. Payment supports self-pay, cashless and corporate with insurance fields and advance deposit.

Sessions use AES-256-encrypted httpOnly cookies (no localStorage), with 15-minute inactivity logout, per-IP rate limiting, Helmet headers and tenant-scoped audit logging in MongoDB. End-to-end-encrypted PHI with zero-knowledge keys is on the roadmap (design stage).

Yes. A demo seeder wipes and re-seeds a full dataset — hospitals, doctors, patients, appointments, admissions and IP rounds/prescriptions — so you can explore a realistic system instantly.