Best Practice Guidelines: Healthcare Practice Management & POPIA Compliance Framework: Web App Roles & User Access

Best Practice Guidelines: Healthcare Practice Management & POPIA Compliance Framework

Best Practice Guidelines: Healthcare Practice Management
&
POPIA Compliance Framework

GoodX online Learning Centre

learning.goodx.co.za

◄ Previous: 1.3. Configuration, Onboarding & Authentication Next: 1.5. Your right to retain personal information ►

1. Introduction to GoodX Software

1.4. Web App Roles & User Access

It is essential that users have defined roles and limited access to functions and information in the software system. Typically your owner will have full access, but other users will have limited access to tasks and information pertinent to one or more roles they fulfil in the practice.

GoodX Web App has predefined roles with predefined user access to make it easy for the practice to get going on the system without much consultation. If users fulfil more than one role in the practice, more than one role can be linked to the user, and all the user access capabilities will compound to give the user all the access rights that all the linked roles allow.

Take note that all users' access limitations can be designed according to the practice's needs.

Users can log in to GoodX using:

A fob commonly called a key fob. It is a small security hardware device with built-in authentication to control and secure access to mobile devices, computer systems, network services and data. The key fob displays a randomly generated access code, which changes periodically, usually every 30 to 60 seconds. Users will first authenticate themselves on the key fob with a personal identification number (PIN), followed by the current code displayed on the device.
A unique username and password (that only the user know)
Facial recognition - our facial recognition system is a technology capable of matching a human face from a digital image or a video frame against a database of faces, typically employed to authenticate users through ID verification services, works by pinpointing and measuring facial features from a given image.

In the Web App:

Users can be linked to one or more Entities;
Users can be linked to one or more system Roles per Entity (the default roles are described below), and they can be directly linked to Groups. This means that one user can have different system roles/access for each entity.
Roles can be linked to one or more Groups, which are the basic system access items that provide access to functions/actions and information in the software.

Here follows an example of how Entities, Users, Roles and Groups (actions) can be linked in the Web App:

In this example, Doctor A and Doctor B have their own practices but share one reception area.

User 1:

Doctor A is working in Practice A as a Practitioner in Entity 1. His access is set to the Practitioner role.

User 3:

Doctor B is working in Practice B as a Practitioner in Entity 2. His access is set to the Practitioner role.

User 2:

User 2 works in the reception area. She fulfils the role of Practice Manager for Practice A with all the access available to perform her duties as a practice manager. However, she works only as Receptionist and Cashier for Practice B, with the added ability to reverse the receipts that she captures for her role as Cashier.