The questions, including the awkward ones.

The outpatient journey: patient management, appointments, OPD and check-in with a token queue, the consultation record with prescriptions and orders, pharmacy, laboratory, and billing, all on the platform core of tenancy, access control, audit and branding.

Inpatient depth: no drawn bed map, no structured medication administration record, no auto-generated discharge summary — though admission, the bed board, wards, nursing charting and discharge themselves are built and in verification. No WhatsApp. No telemedicine. No insurance, TPA or claims. No analyzer interfacing. No purchasing side to the pharmacy. No drug interaction checking. No specialty clinical surfaces such as an odontogram. That is the honest list and it is on our features pages too.

No. Milestones 1 to 4 are built and verified in the NHA sandbox, and no health record has been exchanged in production in either direction. Certification needs functional testing, a security audit certificate and committee approval, and we hold none of them.

We are pre-release and in verification ahead of our first customers. When we have them and they agree to be named, they will appear on this site with their consent, and not before.

On the modules you turn on, your branches and your beds. Never per doctor, never per seat, never per patient, and never by specialty.

Because we have not set one we are willing to publish and honor. Tell us your modules, branches and beds and you will get a real number rather than a range we would have to correct.

We run a guided pilot rather than a self-serve trial. A hospital’s branches, roles and price list have to be right before the software means anything, and that is a conversation rather than a signup form.

Nothing. We do not charge an exit fee in any form. Report export to CSV works today and broader export is scheduled; whichever exists when you leave, it is not billed.

No. Every hospital runs the same version, so there is nothing to upgrade to and nothing to maintain separately.

In India. The database runs in an India region and object storage is set to an India jurisdiction per environment at deployment. It is an architectural decision taken ahead of any legal requirement.

By PostgreSQL row-level security. The database enforces it, not application code. Tenant context comes only from the authenticated session, never from anything a client sends, and isolation is tested in both directions on every module.

A short, named list of sub-processors, covering hosting and the database, email and SMS, and object storage, published on our security page, with what each one handles. Where a hospital enables online payment, the gateway is the hospital’s own merchant account and we are not in the funds flow.

No. We do not sell, share or mine it, and we send nothing patient-, staff- or hospital-identifying to an analytics vendor. The Portal ships no third-party analytics at all.

The software is quick; the data is not. Building your fee schedule, cleaning your patient list and training your staff are the real work, and they are yours regardless of vendor. Onboarding is guided and included.

It is responsive web, which works on a tablet and a phone. There is no native app and there will not be one until the web Portal is shown to be insufficient for a specific role.

Yes. Your facility gets a branded QR link for self-registration, booking and check-in. The tenant is resolved server-side from an opaque token, so a link cannot be edited to reach another hospital, and a patient submission creates something for your desk to review rather than a record nobody checked.

Yes. Multi-branch is in the schema from the start, so a branch is a column rather than a second installation. Cross-branch group reporting is scheduled.