Skip to content

Administration, roles and branches

Set up by the clinic, not by us.

Roles and their permissions, each one a list the administrator can change

Used by Administrators, owners and IT staff.

The administration module is where a clinic sets who may do what, runs several branches and puts its own name and domain on the system. Permissions are data, so an administrator changes them without a software release.

What it does

  • Roles as data: an administrator can change what a nurse may do without a deploy.
  • Branches, with staff who work at several and stock that sits at one.
  • The clinic’s own domain, name, mark and colours, on the site and on the installed app.
  • An audit trail with no delete, recording refusals as well as successes.
  • Modules a clinic has not bought refuse at the endpoint, not merely in the menu.
  • Backups taken hourly, then restored into a scratch database to prove they work.
Roles and their permissions, each one a list the administrator can change
Sites: the buildings one organisation runs, with a form to add another

Questions buyers ask

Does the platform support role-based access? Yes. Roles and their permissions are stored as data, so an administrator can change what a role may do without waiting for a software update. Each action is checked on the server, not only hidden in the menu.

Further reading

See it workingbefore you buy

Open the demo hospital and sign in as a doctor, a nurse or the front desk. Nothing to install and no account needed. When you want your own patients in it, the trial runs for thirty days with everyone who works there included.

Administration, roles and branches | QClinicOne