How Zivyaa is built
Healthcare software fails in ways ordinary business software does not. A billing bug is an argument. A records bug is a safety problem. These are the decisions we made because of that.
Your data stays in India
All data — live and backup — is stored in India. Encrypted in transit and at rest.
Every organisation sees only its own data
An organisation sees itself and its own stores. A store sees only itself, not the other stores of the same organisation. A doctor working across several facilities sees only their own patients at each one, and loses access to new data the moment that link ends. This is enforced on the server, not by hiding buttons on a screen — a modified app or a direct API call gets the same answer: nothing.
Roles decide what each person can reach
Reception, doctor, pharmacist, lab staff, admin — each role reaches only what the job needs. Finance roles do not open clinical records. Clinical roles do not open the full accounts.
Records move only with the patient’s consent
A record created at one facility does not travel to another because a provider asked for it. The patient decides, and every access that follows is logged against the consent it was given under.
Everything is written down
Logins, record views, edits and money actions are logged. Audit records are append-only: they cannot be edited or deleted afterwards, by anyone, including us.
Built to keep working when the connection does not
Facilities in tier-2 and tier-3 towns lose internet and power as a matter of routine. The platform is designed so the work continues instead of stopping at the front desk, and syncs up once the connection is back.
One platform, not modules bolted together
OPD, pharmacy, laboratory, billing and inventory are built as one system rather than separate products stitched at the edges — which is where re-typing and mismatched records come from. You still only pay for the parts you run.
Web and mobile
Desktop for admin and back-office. Mobile where the work is physical: registration, the pharmacy counter, sample collection.
That is how it works. Whether to believe it is a fair next question.
Encryption, backups and restores, where we stand on NABH, NABL and ABDM, and how to report a security problem.