Solution
Trisvio for Hospital Groups & Multi-Branch
A hospital group needs one platform across its branches without one branch seeing another’s patients or bills. Each branch runs its own Trisvio — its own users, patients and billing — under one group account, with data isolation enforced in two layers.
A Tenant groups multiple hospital branches under one commercial account, but it’s an ownership grouping only — every branch’s clinical and billing data is isolated by application-level scoping and Postgres row-level security, keyed to that specific hospital.
- Who it's for
- A group running two or more hospital branches that wants one platform and one commercial relationship, with each branch operating independently.
- Daily workflow
- Each branch runs day-to-day exactly like a single hospital — its own registration, OPD, IPD, billing, pharmacy and lab, with no visibility into any other branch.
- What's not included
- No consolidated cross-branch dashboard, roll-up reporting, or single login that spans branches — see below.
- Modules used
- Patient Registration, Billing & Payments, Staff & Access Control
Why Trisvio fits hospital groups & multi-branch
- Grow from one hospital to several without data bleedAdding a new branch means adding another hospital under the same group account, with its own patients and billing kept strictly separate from every other branch — nothing leaks across branches as the group grows.
- Isolation enforced twice, not onceEvery branch’s data is scoped at the application layer and again at the database layer through Postgres row-level security, so branch isolation doesn’t rest on a single point of failure.
- Per-branch access controlEach branch configures its own roles and permissions, so a user at one branch doesn’t automatically get access at another — access rights stay local to the branch they belong to.
- One platform, one licence, across the groupThe group runs on a single Trisvio platform and licence rather than juggling different software at different branches, while each branch’s day-to-day operation stays independent.
Modules used
- FeaturePatient RegistrationRegister a patient once with a permanent MR number, then reuse that same record for every OPD visit, IPD admission, pharmacy sale and lab order.See how it works →
- FeatureBilling & PaymentsGST-aware billing across OPD, IPD, pharmacy and lab — a bill editor, A5 receipts, cash/UPI/card payments, advances, and a daily collection report.See how it works →
- FeatureStaff & Access ControlConfigurable roles with granular permission keys, password policy, account lockout, revocable sessions and optional TOTP two-factor for every staff account.See how it works →
In detail
What "group" means today: ownership, not shared operations
A Tenant in Trisvio is an ownership grouping over one or more Hospital records — the entity a commercial relationship (plan, trial, suspension) attaches to. It is deliberately not a scoping key for clinical or billing data: every table that carries patient, billing or clinical information is isolated by hospitalId, never by tenantId, at both the application query layer and again as a Postgres row-level security policy on the database itself. That double enforcement means one branch’s records can’t be read by another branch even if a bug slipped past the first layer.
Suspending a group account does reach every branch at once — it revokes every live session across all of the tenant’s hospitals rather than leaving old sessions to expire on their own. That’s the one place the group boundary is genuinely operational today; everything else about running a branch is independent of the others.
Separate logins, separate roles, per branch
A staff member’s account belongs to one hospital. Someone who works at two branches under the same group holds two separate accounts — possibly with the same email address, since email is unique per hospital rather than globally — and signs into each one separately; there’s no in-session "switch branch" control. Roles and permissions are configured per hospital too, so a role set up at one branch has no effect at another, even under the same group.
What isn't included today
- No consolidated, group-wide dashboard or cross-branch roll-up report — each branch reports on its own data, the same way a single hospital would.
- No single login that spans branches — a person with accounts at two branches signs into each one separately.
- No insurance/TPA claims workflow and no ABDM/ABHA registry integration, the same as every other Trisvio deployment.
Related reading
Frequently asked questions
Can group leadership see all branches in one consolidated dashboard?
Not today. Each branch runs its own Trisvio under one group account, with strict data isolation between branches — reporting and analytics work within each branch, the same way they would for a single hospital. A consolidated, group-wide roll-up dashboard across branches is not part of the platform right now.
How is one branch’s data kept separate from another branch’s?
Isolation is enforced in two layers: application-level scoping on every query, and Postgres row-level security underneath it. Between them, one branch cannot read another branch’s patients, billing, or records — the Tenant is only an ownership grouping, not a shared data pool.
Does suspending the group account affect every branch?
Yes — that’s the one place the group boundary is operational today. Suspending a tenant’s account revokes every live session across all of its hospitals at once, rather than leaving existing sessions to run until they expire naturally.
What does Trisvio cost for a hospital group?
Pricing is matched to the number of branches and their needs rather than a fixed number — talk to us and we’ll work out what fits.