Several hospitals, cleanly separated, one owner view
Each unit runs its own staff, roles, numbering and branding. You see across all of them without any of them seeing each other.
Running a second branch on a system designed for one is where most clinic software falls apart. Patient numbers collide, staff at one branch can see the other’s records, and the owner ends up asking two managers for two reports. OlivHealth was built multi-tenant from the first table: every unit is properly separated at the data layer, not filtered in the interface, and separation is enforced centrally rather than left to each screen to remember.
True multi-tenancy
Organisations hold hospitals, and every tenant-scoped record carries its unit. Cross-unit access is refused, not hidden.
Per-hospital numbering
Patients, bills and receipts get their own per-unit sequences, so no branch inherits another’s series.
Hospital switcher
Owners move between units from one login, while a member stays pinned to the unit they belong to.
Per-hospital features
Modules are switched on per unit, so a branch with a pharmacy and a branch without do not have to look the same.
Branding and custom domain
Each unit can carry its own logo and accent over the group identity, and the group can run on its own domain.
Owner-level view
Read across every unit from one account, while each unit’s staff only ever sees their own.
Go live ABDM-enabled from day one
Every practice we onboard goes live ABDM-enabled — create and verify a patient’s ABHA at registration, and let their records follow them across the health system on their consent. It’s part of onboarding, not a separate project or an extra module to buy.
Frequently asked questions
Can one person work at two branches?
Each account belongs to one hospital, so a person working at two units holds two accounts. That is deliberate: it keeps permissions unambiguous and makes the audit trail honest about which unit an action happened at.
Do we need a separate subscription per hospital?
No. The subscription sits on the organisation and covers the units under it, with the number of hospitals as part of what you are on.
Can each branch have its own prices and services?
Yes. Services, prices and tax treatment are configured per hospital, so branches in different cities can price differently.
How is cross-branch data leakage prevented?
Tenant scoping is applied centrally rather than being re-implemented in each query, and a lookup that crosses units returns not-found rather than a permission error, so record IDs cannot be probed.