Trust & security
How Trisvio protects your hospital's data
A hospital's data — patients, diagnoses, billing, pharmacy and lab records — is among the most sensitive information any organisation holds. This page describes, specifically and without marketing gloss, the controls Trisvio uses to protect it. If a control isn't listed here, we don't claim it.
Cloud-hosted, built for an India region — here's exactly how your data is protected
Trisvio is a cloud-hosted, multi-tenant platform built to run in an Indian cloud region — a fixed requirement of every deployment. Every hospital's data is isolated at the database layer, sensitive identifiers are encrypted, and access is controlled by configurable, per-role permissions. The platform needs an internet connection for day-to-day operations.
The controls, specifically
- Postgres row-level tenant isolation
- Every query is scoped per hospital and enforced in two layers — the application layer and PostgreSQL row-level security — so one hospital can never read another's data.
- Encryption of sensitive identifiers
- Government identifiers kept in the patient-identifier store (such as Aadhaar or ABHA) and staff two-factor secrets are encrypted with AES-256-GCM, with a separate key per hospital — there is no plaintext copy of them in the database. Names, phone numbers, clinical notes and bills are protected by access control and hospital isolation, not field encryption. Note that front-desk capture of Aadhaar or ABHA is not live — the registration screen shows those fields but does not save them yet.
- Encryption in transit
- Every deployment is required to serve the platform over HTTPS, and the application tells browsers to use HTTPS only. The database runs on the same server and accepts connections only from that machine, so application-to-database traffic never crosses a network.
- Configurable role-based access
- Roles are per-hospital, granting granular permission keys — module read/write plus action rights (billing discount, diagnostics verify, pharmacy adjust, discharge, prescribing, admin). Staff see only what their role allows.
- Audit logging
- Changes to clinical, billing and access records are audit-logged with who and when, and opening key records — the patient profile, a visit, a report, a printed document — is logged too.
- Backup and restore
- Database backup and restore are scripted, and the health check reports the latest backup's age. A test restore is required before go-live, then quarterly.
Reliability, stated honestly
Trisvio is built to run in an Indian cloud region, with scripted backup and restore and a test restore required before go-live, then quarterly. We deliberately don't sell an uptime SLA we can't evidence; vendors who promise '100% uptime' are telling you about their marketing, not your infrastructure.
What we don't claim
You'll notice this page has no certification badges. Trisvio does not currently hold ISO 27001 or SOC 2 certification, and we won't display badges we haven't earned. What we do offer is the specific, verifiable set of controls above — and straight answers to any security question during your evaluation. Ask us the hard ones at the demo.
Security questions to ask any hospital-software vendor
- "Where does our patient data live, and who can see it?"
- You should get a specific answer about tenant isolation between hospitals, encryption of sensitive identifiers, and role-based access inside yours.
- "What happens if we leave?"
- Your data is yours. Ask for the specifics of exporting your records during your evaluation.
- "Show me the audit trail."
- If a vendor can't show who changed a bill or a lab result and when, the system isn't really a system of record.
- "What's your backup and recovery story?"
- Ask how often backups run and whether the vendor has actually rehearsed a restore — not just scheduled one.
Frequently asked questions
Where is patient data hosted?
Trisvio is cloud-hosted, and every deployment is required to run in an Indian cloud region — application, database and file storage. Each hospital's data is isolated at the database layer, and government identifiers such as Aadhaar or ABHA are encrypted with AES-256-GCM — there's no plaintext copy of them in the database.
Is Trisvio aligned with India's DPDP Act 2023?
Trisvio is designed with the DPDP Act 2023's principles in mind — per-hospital data isolation, encryption of sensitive identifiers, a consent ledger, configurable role-based access and audit logging.
Does Trisvio have ISO 27001 or SOC 2 certification?
Not currently — and we won't show badges we haven't earned. This page lists the specific controls built into the product: row-level isolation, AES-256-GCM encryption of sensitive identifiers, HTTPS in transit, configurable RBAC, audit logging and scripted backup and restore.
What about AI and patient privacy?
AI is optional and off by default; the full Trisvio platform works without it. When enabled, drafts are reviewed and approved by a clinician, prompts and responses are never stored, and patient data is never sent to an external AI provider unless your hospital explicitly allows it.
Elsewhere on the site
Keep exploring
Bring your hardest security question to the walkthrough.