Skip to content

Branches, roles and audit trail

Built for a lab with more than one room and more than one person who can sign. Branches sit under one account, every screen is permission-checked on the server, and the audit trail is written by the system rather than by the user.

Branches under one account

Orders, samples and reports are recorded against a branch, and a report template can belong to one, which is how two branches print the same results on different letterheads. Pick a branch in the sidebar and the whole app follows it: dashboard figures, worklists, patient and order lists, and new registrations default to that branch. Staff can be limited to the branches they work at; a user with none assigned sees the whole lab.

A user limited to certain branches sees only those branches’ orders, samples and reports, everywhere in the app.

Settings on the Branches tab, listing the lab’s collection centres with code, city, phone and status, alongside tabs for plan and billing, organisation, users, roles, referrals and the audit log

One lab can never see another lab’s data

Which lab you belong to is fixed when you sign in, and every screen, list and search is limited to that lab. There is no setting, link or field that would show another lab’s patients, because the browser is never asked which lab it is.

Roles with a ceiling, and permissions you can edit

Owner, administrator, branch manager, receptionist, phlebotomist, technician, pathologist and referral doctor each start from a default permission set, and an administrator can edit those sets for their own lab. Some permissions and some roles are locked, and nobody can grant a role above their own.

Deactivate someone and their sessions stop working

The app keeps checking that an account is still active, not just that someone signed in earlier. Deactivating a user, changing their role or resetting their password ends their existing sessions within seconds, so an open laptop in the sample room stops being a way in.

An append-only audit trail

Entry, verification, approval, release, amendment, print, delivery, sign-in, role change and configuration edit are all written with the user, the time, the record and the old and new values. The trail is append-only and the application never offers a way to edit it.

Guided setup, then a checklist for the rest

A new lab is walked through six steps: lab details, a plan, the report formats to start with, your rates, the letterhead and a final review. The letterhead can wait for later; the other five are what it takes to print a first bill. What is left after that, such as referring doctors, messaging and your team, stays on a Getting started list that ticks itself off as the work gets done.

Setup progress is worked out from your lab’s own data, so a step finished anywhere in the app counts, and nothing can be ticked off without being done.

Getting started checklist with a completion bar, split into essentials needed before the first order and worth-doing items, each finished step struck through with what it produced and the outstanding ones linked for action

What this does not do yet

Labs ask for all of these. None of them work today, so none of them are counted as features anywhere else on this site.

  • No single sign-on. There is no SAML, no OIDC and no Google Workspace login: sign-in is email and password, rate-limited.
  • No two-factor authentication, and no hardware key support.
  • No per-branch rate list. Prices are one list for the whole lab, so branch-level pricing is not possible yet.
  • One role per user. A person who works reception on Tuesdays and runs the analyser on Fridays needs two accounts.
  • No IP allow-list, no working-hours restriction and no device registration.

Set up your lab this afternoon.

Create your organisation, add your tests, print the first barcode. If you would rather see it first, ask for a walkthrough.

Start 30-day free trialBook a demo