Gate Modules by Tenant Entitlement

Veona is sold as modules, not as one all-or-nothing system. A laboratory might buy the lab spine and patient registration and nothing else; a hospital might licence wards, theatre, pharmacy, billing and more. The mechanism that makes this honest is entitlement gating: every sellable module is locked off until your facility is entitled to it, and a module you have not purchased is genuinely unavailable — it does not half-work, leak data, or sit there as a dead button. This page explains the model and what a Tenant Admin sees because of it.

Who / when: the Tenant Admin (the facility Administrator) meets entitlements whenever a colleague reports “I can’t reach this screen” or when the facility’s purchased set changes. The gating itself is enforced by the system on every request, deny-by-default.

The words that matter:

• Module — a self-contained area of Veona that can be bought on its own: Labs, Imaging, Ward, Theatre, Pharmacy (Rx), Billing, Blood Bank, and so on.
• Entitlement — the record that says “this facility may use this module.” No entitlement, no access.
• Deny-by-default — the safe stance: if there is no entitlement saying yes, the answer is no. Nothing is open unless it has been explicitly opened.
• 403 — the polite refusal the system returns when a request hits a module the facility is not entitled to. It is a clean, blocking “not available here”, not an error.
• Base / always-on module — the handful of modules every facility always has, because the product cannot function without them. These are never separately sold.
• Edition — a pre-packaged bundle of modules sold together (for example Health Centre, Hospital, Network, Public Health, and the standalone Veona Labs).

1. System — on every request to a sellable module, Veona checks the facility’s entitlement. If the entitlement is present and active, the request proceeds; if it is absent or switched off, the request is refused with a 403 and the screen reports the area is not available for your facility. This check is deny-by-default, so a missing entitlement always means no.
2. Tenant Admin — the always-on base set needs no purchase and is never locked: patient registration and UHID, the universal e-signature, the shared diagnostics ordering screen, plus the foundations on this very journey — storage, the audit trail, notifications, reference data and settings. A colleague will never be told these are “not entitled”.
3. Tenant Admin — for a sellable module, your facility’s access reflects exactly what was purchased. When a colleague cannot reach Ward or Theatre or Blood Bank, the first thing to check is whether your facility’s plan includes that module — the gate is doing its job, not failing.
4. Tenant Admin — to change what your facility is entitled to, the entitlement is granted from the Veona platform side when your plan changes, not toggled inside the facility app. New modules light up after the change is provisioned (cloud) or delivered to the appliance (on-premise).

Note

Entitlement gating and role permissions are two different locks, and a request must pass both. Entitlement asks “is this facility licensed for this module?”; role permission (RBAC) asks “is this person allowed to do this action?” A clinician with every clinical permission still cannot reach Blood Bank if the facility never bought it — and a fully-entitled facility still won’t let a cashier write a prescription.

Caution

Modules degrade gracefully, never dangerously. If one module is not licensed, a neighbouring module that would normally hand off to it simply skips that step rather than failing — for example, a lab can run perfectly well with results entered by hand when the device-integration module (Veona Connect) is not part of the plan. The gate protects a module’s own screens; it never breaks an unrelated workflow that happens to sit beside it.

What happens next: with entitlements enforced everywhere, what your facility sees is exactly what it bought — no more, no less — and your plan can grow over time without any reinstall. Add a module to the plan and it appears; the foundations every facility relies on (storage, audit, notifications, reference data) are always there underneath, whichever modules sit on top.

Follow the trail