Feature
Hospital Staff Roles & Access Control (RBAC)
Not every staff member should be able to do everything, and Trisvio lets a hospital configure exactly who can. Roles are per-hospital data granting specific permission keys, managed from Settings rather than fixed in code.
Staff access control lets each hospital define its own roles and permission keys, resolves them at login, and revokes sessions immediately whenever a role or assignment changes.
- Who uses it
- Admins define roles and assign staff to them; every staff member operates within the permissions their role grants.
- What it records
- Role definitions, user-role assignments, and login/session activity protected by lockout and optional TOTP two-factor.
- What it prints / exports
- No document export — this feature governs access, and its activity shows up in the audit log under Reports & Analytics.
- Works with
- Reports & Analytics, Patient Registration
What you get
- Roles configured per hospitalRoles are data, not hardcoded — each hospital sets up its own roles and decides which permission keys each one carries, from Settings → Roles.
- Granular action rights, not just module accessBeyond read/write on a module, specific actions can be gated individually — for example requesting a discount versus approving one, verifying a diagnostics result, or reviewing a revenue exception are separate permission keys, not one blanket billing or lab right.
- Changes take effect immediatelyPermissions resolve at login, and changing a role or a user’s assignment revokes that user’s sessions, so access changes apply right away rather than lingering in an old session.
- Account security built inA password policy, account lockout after repeated failed attempts, revocable sessions, and optional TOTP two-factor sign-in, which any staff member can switch on, protect staff accounts beyond just role permissions.
How it works
Define roles and permissions
An admin sets up roles at Settings → Roles, choosing which module access and action rights each role grants.
Assign roles to users
Staff are added and assigned a role at Settings → Users, giving each person exactly the access their job needs.
Permissions resolve at login
When a user signs in, their effective permissions are resolved from their role and carried through their session.
Update and revoke as needed
Changing a role or a user’s assignment revokes that user’s existing sessions immediately, and account lockout, revocable sessions, and optional TOTP two-factor guard the sign-in itself.
Who uses it
- AdminConfigure roles and permission keys per hospital and manage staff assignments from Settings.
- OwnerControl exactly which staff can discount bills, approve discounts, verify diagnostics results, resolve revenue exceptions, or manage other users.
- Department staffEach staff member — nurse, pharmacist, lab tech, or billing clerk — sees only the modules and actions their role permits, so they can focus on their job without access to unrelated functions.
In detail
Permission keys that separate request from approval
A number of permission keys exist specifically to keep one person from both taking an action and approving it — requesting a discount and approving one are different keys, and reviewing a revenue exception is separate again from the permission that let someone dispense medicine or discharge a patient. Compliance work sits behind its own read/write keys too, and a broader admin-level key governs hospital-wide settings like doctor payout runs. A hospital decides which of these each of its own roles carries; none of it is fixed in code.
Sessions revoke immediately, at every level
Changing what a role or a specific user can do takes effect straight away by revoking that user’s active sessions — there’s no window where someone keeps acting on an old permission set after it’s been narrowed. The same principle applies a level up: on a multi-hospital group account, suspending the group revokes every live session across every hospital under it at once, rather than leaving existing sessions to expire on their own.
Frequently asked questions
Are staff roles fixed, or can a hospital configure them?
Roles are configurable per hospital. An admin defines roles at Settings → Roles and chooses which module access and action rights — like requesting or approving a discount, verifying diagnostics results, or resolving a revenue exception — each role grants.
What happens when a role or user’s access is changed?
Effective permissions resolve at login, and changing a role or a user’s assignment revokes that user’s existing sessions right away, so the updated access takes effect immediately rather than after the old session expires.
What account security features protect staff logins?
Beyond role-based permissions, accounts are protected by a password policy, lockout after repeated failed attempts, revocable sessions, and optional TOTP two-factor sign-in that any staff member can switch on. Two-factor is optional for sign-in, but managing users and roles requires the administrator to have it on and to have signed in with a code, and a lost authenticator is reset only after an in-person check approved by a second person.
Can the same person request and approve their own discount if they hold both permission keys?
No. Even holding both permission keys on one account, the approval step is refused if the approver is the same person who made the original request — that rule doesn’t depend on which permissions a role happens to combine.
Does a role apply to one hospital, or across a whole group?
Roles and permissions are configured per hospital. If a group runs more than one hospital under Trisvio, each hospital sets up and manages its own roles independently — see our solution for hospital groups for how that isolation works.