Including the ones with uncomfortable answers.
No. Every record is scoped to the hospital that owns it at the database layer, enforced by five independent mechanisms and proven by a test suite that attacks every record type on every build. A hospital identifier sent by a browser is ignored — which hospital a request belongs to is decided from the web address and the signed-in session.
Your hospital becomes read-only rather than locked. You keep access to records and to a full export. We do not hold a patient’s allergy list hostage to an invoice.
Yes, at any time, in a machine-readable format, including after cancellation. It is a feature rather than a favour.
No. Patient records are never metered, and a plan limit can never block a registration — including an emergency one. Plans meter users, branches, storage and outbound messaging.
Modules not in the smaller plan are hidden and stop accepting new entries. Nothing is deleted. If you upgrade again, everything is exactly where you left it. If your current usage exceeds the smaller plan, we tell you before the change and give you a window to adjust.
Yes, on plans that include it. Every hospital gets an address on our domain immediately, and a custom domain can be added later — the platform was designed for that from the first release rather than retrofitted.
No. This is a web platform and it needs a connection. We would rather say that plainly than describe a partial offline mode that would put your records at risk of diverging. If your connectivity is genuinely unreliable, tell us before you commit.
Usually. Patient master data, doctors, services, pharmacy items and outstanding balances import cleanly. Full clinical history is harder and depends entirely on what your current system will give you. Tell us what you run and we will be specific rather than encouraging.
A doctor sees patients they have a clinical relationship with — an appointment, visit, admission or referral. Broader access is a separate permission that an administrator must grant, and every use of it is audited with the user, the patient and the reason.
For platform staff, hospital administrators, and anyone who can approve a report, cancel an invoice, issue a refund or delete a user — yes. For everyone else it is available and encouraged. A hospital can raise the requirement but not lower it below the platform minimum.
Not without an explicit, time-boxed support grant that you can see in your own security log. Our staff have no standing access, and every action taken during a support session records both the staff member and the account they acted as.
Yes. Tax is computed per line with HSN/SAC codes, split into CGST and SGST for intra-state or a single IGST line for inter-state, with rounding that keeps the halves adding back to the whole. Invoices carry your GSTIN and registration details.
Software that runs daily hospital work on one platform: registration, OPD and IPD, electronic medical records, pharmacy, laboratory, billing, insurance claims, inventory and staff. Nanostack HMS connects those so each department works from the same patient record.
Yes. A clinic can run appointments, EMR and billing. A hospital can add admissions, pharmacy, laboratory, theatre and insurance on the same platform. Modules follow the plan, so you do not change products when the facility grows.
We do not claim NHA approval. A hospital can store an ABHA number encrypted on the chart, and, when it configures the ABDM gateway (sandbox or production), create or verify an ABHA, link a visit as a HIP, push a record when consent is granted, and receive Scan and Share tokens. Insurance work, including NHCX, is configured separately.
A clinic that starts with registration, appointments and billing can be using the product in days once master data is in. A hospital that also brings pharmacy, laboratory and wards needs longer, mostly for import and staff training rather than for installing software. Tell us what you run today and we will be specific.
Your hospital does. Records stay in your tenant, administrators can export them in a machine-readable format at any time, and cancellation does not delete that export path. We do not lock the chart behind a renewal.