Skip to content
  • There are no suggestions because the search field is empty.

How to manage user access in SystemView

Handle access requests, choose the right role and access, limit domains and remove access.

Your health service has its own access process. It says who can approve access and what each type of user should have. If anything here differs from that process, follow your process.

This article is for Local Administrators, who may also be called Local System Administrators (LSAs). For the screen-by-screen steps to add a user, see How to add and manage users in SystemView.

In this article:


Handle an access request

Most users ask for access with the form on the SystemView sign-in page. They select Request Access and give:

  • their username, which is their health network login
  • their email address and name
  • the domains they need, such as Surgery or Beds
  • their user group, such as Clinical, Administration or Executive
  • the facilities they need. Most people need only the hospital they work at, or the hospital network it belongs to.
  • their reason for asking, such as their job title and how SystemView will help their work

The Access Request form, with fields for username, email, name, domains, user group, facility access and reason.

Each form creates an email to the inbox your project team set up for access requests. Some requests come by direct email instead, often from a manager asking for access for their staff. If you're unsure who sent one, check with them before you act on it.

An access request email listing the user name, first name, last name, email and reason. The details are blurred.

Before you set anything up:

  1. Check the request has everything you need.
  2. Check it fits your access process.
  3. If something is missing, contact the person who asked and get the details first.
  4. Wait for a yes from the approver your process names.

Then choose the settings below and add the user. You can set up most access yourself. If your own tools can't fix the problem, raise a support request and choose Access to SystemView. We follow your health service's access process. If your health service uses its own service desk to contact us, use that instead.


See which settings control access

No single setting controls a user's access. Each one below does a different job, so check them together.

SettingWhat it decidesWhere you set it
RoleWhat the user can do, including any admin toolsCreate New User form
User GroupThe kind of work the user does, so they are grouped correctly in reportsCreate New User form
Jurisdiction View User GroupWhether the user can open JurisdictionView, and which parts of itCreate New User form
Facility AccessWhich facilities the user can see, and whether patient details are identifiable or PseudoFacility Access screen, after you create the user
Domain BlockWhich domains are hidden from the userDomain Block, under Applications

On the Create New User form, Role is in box 2, User Group is in box 3 and Jurisdiction View User Group is in box 5.

The Create New User form with numbered boxes around its fields. Box 2 includes Role, box 3 is User Group and box 5 is Jurisdiction View User Group.


Choose a role

The role sets what a person can do in SystemView. It doesn't decide which facilities or domains they can see. Most people need General User.

RoleWho it's forWhat it lets them do
General UserMost staff, such as clinical, operational and reporting usersUse Explore and Interact for the facilities they have access to. No admin tools.
General User with Mandatory WorkflowOnly the users your access process namesThe same access as a General User.
Executive UserExecutives and senior leaders who add organisational targetsEverything a General User can do, plus add organisational targets and standards.
Local AdministratorStaff who manage SystemView access, often your service deskEverything an Executive User can do, plus the admin tools under Applications.
System AdministratorHealthCare Logic staff onlyManages the settings for your whole SystemView. You can't give this role to anyone.

Only choose Local Administrator if your access process approves it. You can't edit your own account. If your own access needs to change, ask another Local Administrator or raise a support request.

Local Administrators use the tools under Applications. The tools you see depend on your health service's setup.

The Applications page in SystemView, showing the admin tools a Local Administrator can open.


Choose a user group

User Group describes the kind of work a person does. SystemView uses it to group people in reports. It doesn't change what a person can see. Choose the group that best fits their job.

User GroupChoose it for
ClinicalNurses, doctors and allied health staff
Clinical LeaderClinical leaders, such as nurse managers, bed managers and clinical directors
AdministrationAdministrative staff, such as booking staff, admissions staff and clinic reception
Operational LeaderManagers, such as operations, finance and general managers
ExecutiveExecutives, such as chief executives and chief operating officers
Local AdministratorStaff who manage SystemView access
Always OnAccounts for shared displays, such as a screen on a ward. These accounts are never signed out automatically.

Choosing Executive here doesn't give someone the Executive User role. They are separate settings. Only use Always On if your access process allows it.

You may also see a group for department of health staff, and groups for HealthCare Logic staff. Don't use the HealthCare Logic groups.


Choose a Jurisdiction View User Group

JurisdictionView compares key measures across hospitals and health services. This group decides whether a user can open it and which of its four parts they get: KPIs and Trends, Scorecard, Demand and Capacity, and Forecasting Tools.

This area may have a different name at your health service. So may this field and the groups in it, which can use your own words, such as network or district.

GroupWho it's forUsual facility accessJurisdictionView
Hospital UserStaff who need some facilities in one health service, such as admin officers and clinical staffSome facilities in one health service, identifiableNone
Hospital Group UserStaff who need every facility in one health service, such as directorsAll facilities in one health service, identifiableNone
Hospital User with JurisdictionView AccessExecutives of one health serviceAll facilities in one health service, identifiableAll four parts, for their own health service
Strategic UserStaff who compare health services, such as system performance staffAll relevant facilities, usually PseudoAll four parts, across health services
Department of Health UserCentral or statewide staffAll relevant facilities, usually PseudoKPIs and Trends and Scorecard only. Explore isn't available.

Here are the same fields on the Edit User Profile screen, with the list of groups open. Your list may show different names.

The Role, User Group, Team - Position and JurisdictionView User Group fields, with the list of jurisdiction groups open.

A Jurisdiction View User Group doesn't add facilities, and it doesn't set identifiable or Pseudo access. You set both in Facility Access. For example, choosing Strategic User doesn't make a user's access Pseudo.

Some health services have extra groups, such as a scorecard-only group or groups for the Coordination Hub. Your access process says who should have them. Availability depends on your deployment.


Set facility access

Facility access decides which facilities a user can see. A user can't see a facility's data until you add that facility. For each facility, choose one of these:

  • Identifiable: the user sees patient details, such as names and record numbers.
  • Pseudo: identifying patient details are hidden or replaced.

Only give identifiable access if your access process approves it for this user.

The Facility Access panel, with two example facilities listed and an Identifiable or Pseudo choice beside each one.

Keep these points in mind:

  • After you change someone's facility access, they need to log out and log in again to see the change.
  • A Strategic User needs every relevant district and facility, or JurisdictionView won't show the full picture.
  • Feature Access on the left of this screen may show No Access Permission. That's expected, because only HealthCare Logic can change feature access.

Limit domains with Domain Block

By default, users can see every domain your health service has. Domain Block limits a group of users to the domains they need for their role. It's optional, so check your access process to see when to use it.

Domain Block only appears under Applications once HealthCare Logic has switched it on for your health service. To ask for this, raise a support request and choose A settings or feature access change.

Users in a Domain Block group can't see:

  • the pages of the blocked domains
  • any tiles or charts from those domains
  • tiles from those domains that were added to personal or shared areas, such as MyView or MyHub
  • tiles from those domains in the Notification List sidebar

Where a blocked tile would show, users see a No Permission message. To create a group and add users:

  1. Click the drop-down arrow in the top right corner and select Applications.
  2. Select Domain Block.
  3. Click Create New Group.
  4. Enter a group name and select the domains to block.
  5. Click Create.
  6. Click the user icon to open the Blocked Users panel.
  7. Search for the users to add and select them.
  8. Click Update.

The numbers in these screenshots match the steps above.

The Applications page with the Domain Block tile highlighted and marked step 2.

The New Group window with a group name entered, Emergency Department ticked under Blocking Domains, and the Create button marked step 5.

The Blocked Users list with a filter box and tick boxes marked step 7, and the Update button marked step 8. User names are blurred.

To get a list of the users in a group, click Export on the Blocked Users screen. The export covers that group only.


Check common set-ups

These examples show how the settings fit together. They are a guide only, so check them against your access process.

PersonRoleUser GroupJurisdiction View User GroupFacility Access
A nurse at one hospitalGeneral UserClinicalHospital UserTheir hospital
A booking officer who works across two hospitalsGeneral UserAdministrationHospital UserThose two hospitals
A director across your health serviceGeneral UserClinical Leader or Operational LeaderHospital Group UserAll facilities in your health service
An executive who adds organisational targetsExecutive UserExecutiveHospital User with JurisdictionView AccessAll facilities in your health service
A new Local AdministratorLocal AdministratorLocal AdministratorAs your access process saysAs your access process says
A shared screen on a wardGeneral UserAlways OnHospital UserOnly the facilities the screen shows

Remove a user's access

Remove access when someone leaves, changes role or no longer needs SystemView. Unless your access process says otherwise, make the account inactive rather than deleting it.

What happensMake inactiveDelete
Can the user sign in?NoNo
Is the account kept?YesNo, it moves to the Deleted Users list
What happens to anything they shared with colleagues?It stays availableIt is deleted
Can you undo it?Yes, make the account active againYes, restore it from the Deleted Users list

Make an account inactive

  1. In User Management, find the user and click the pencil icon to open their profile.
  2. Change Status from Active to Inactive.
  3. Click Save Changes.

The Edit User Profile screen with the Status list open and Inactive highlighted. Personal details are blurred.

Delete an account

  1. In User Management, find the user and click the red bin icon.
  2. Choose a reason from the list.
  3. Select Delete to confirm.

The delete warning with four reasons: No longer works in service, Not relevant for position, Duplication and Administrator Error.

Restore a deleted account

  1. In User Management, select Deleted Users.
  2. Find the user and click the clock icon in the Reinstate User column.
  3. Select Restore.

Now and then, check your user list for accounts that no longer need access.


See what only HealthCare Logic can change

Local Administrators manage people and their access. HealthCare Logic manages the settings that affect your whole SystemView. If a change affects one user or a group of users, you can usually make it yourself. If it changes what everyone can do, ask us.

TaskLocal AdministratorHealthCare Logic
Create, change and remove usersYesYes
Set a user's role and groupsYesYes
Set facility access, including identifiable or PseudoYesYes
Create Domain Block groups and add users to themYes, once Domain Block is onYes
Post announcements and manage training resourcesYesYes
Switch Domain Block or another feature on or offNoYes
Change feature access for one userNoYes
Switch a component or facility on or off for your whole SystemViewNoYes
Set up TeamView accessNoYes
Change the pseudonymisation rules, which decide what gets hiddenNoYes
Open the audit logNoYes

To ask for something in this list, raise a support request. For a change, choose A settings or feature access change. Some features are part of a separate agreement. If so, we'll tell you. If your health service uses its own service desk to contact us, use that instead.


Related articles