FAQ
The questions, including the awkward ones.
Everything a buyer asks us, in one place, starting with what is not built rather than ending with it.
What is actually built
What can we use today?
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.
What is not built?
No PACS or image viewer: imaging is ordered and reported, but the images themselves are not stored. No statutory blood bank registers. The general stores buy and issue, but keep no rate contracts or vendor bills of their own. No GPS tracking of ambulances. No insurance claims (pre-authorizations are tracked, but sent through the payer portals). Video consultations run on a Jitsi Meet server, open in a separate tab and are not recorded, with no waiting room. SMS and WhatsApp are one-way messages through your own MSG91 and WhatsApp Business accounts, with no chat or campaigns. No automatic drug interaction alerts. No analyzer, monitor or ventilator is connected, so results and readings are entered by hand. On the ward, the bed board is a list rather than a drawn map, the discharge summary is written by the clinician rather than drafted automatically from the stay, and the medication administration record has no barcode scanning or second-nurse check for high-alert medicines. The specialty modules have no body map, no clinical photographs by body site, no partograph, no fetal growth centiles and no chemotherapy day care, and nothing in them computes a dose. No HR or payroll. That is the honest list and it is on our features pages too.
Are you ABDM certified?
No. Milestones 1 to 4 are built. ABHA creation and verification, Scan and Register, record sharing (HIP) and record requests (HIU) have run end to end in the NHA sandbox, and the Health Facility and Professional Registry work is built, with registering our own facility waiting on NHA. No health record has been exchanged in production in either direction. Certification needs NHA functional testing, a CERT-In Safe to Host (WASA) certificate and Health Tech Committee approval, and we hold none of them yet, so ABDM is not yet available to customers.
Do you have customers?
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.
Pricing and commercials
How is it priced?
On the plan that fits your facility and the add-on modules you turn on, billed monthly or yearly. Never per doctor, never per seat and never per patient, and a specialty never changes the plan price.
Is the price on the pricing page what we pay?
It is the plan’s price before GST, which is added on top. The written quotation we send confirms the figure for your setup, including any add-ons, before you pay anything. Multi Speciality Hospital is always priced by quotation.
Is there a free trial?
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.
What does it cost to leave?
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.
Is there an AMC or an upgrade fee?
No. Every hospital runs the same version, so there is nothing to upgrade to and nothing to maintain separately.
Data, security and compliance
Where is our data stored?
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.
How is our data separated from another hospital’s?
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.
Who else touches our data?
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.
Do you use our data for anything else?
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.
Using it
How long does implementation take?
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.
Do you have a mobile app?
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.
Can patients book and check in themselves?
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.
Can we run more than one location?
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.
Not answered here? The compliance page covers what we claim and refuse to claim, the feature pages each end with what that feature does not do, and asking us reaches a person who built it.
See it running with your own workflows.
Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.