RBAC (Role-Based Access Control)

Role-based access control assigns permissions to named roles — receptionist, nurse, pharmacist, administrator — and then assigns people to roles. Changing what a role can do changes it for everyone holding that role; moving someone between jobs changes their access in one step. Well-built systems go beyond module-level read and write to action rights: who may approve a discount, who may verify a laboratory result, who may record a drug administration.

Why it matters in a hospital

In a hospital, access control is a safety and accountability mechanism as much as a security one. The question is rarely whether someone is trustworthy — it is whether the record shows who did a thing, and whether a person can do something their job does not include. Action-level rights are where this gets real: separating who may request a discount from who may approve it puts a second pair of eyes on money leaving the hospital, and separating who enters a result from who verifies it is a basic laboratory control. Coarse roles cannot express either.

How Trisvio handles it

Roles in Trisvio are per-hospital data rather than fixed in code, so a hospital defines its own and grants module rights plus action rights — discount approval, laboratory verification, stock adjustment, discharge, administering medication. Changing a role or an assignment revokes that user's live sessions rather than waiting for them to sign out.