Sometimes it is useful to have several compliance items which are required for some clients, but not others. For example in a medical environment there may be certain checks & compliance items required by all Private Hospitals, and other checks which are only applicable to NHS based organisation. Compliance Type codes provide a way to group multiple compliance items together to achieve this.

Contents  (Click an Item to Jump to that section)

TABLE OF CONTENTS

• Creating Compliance Types
  • When Compliance Types will be Applied
• Using Compliance Types
• How it Works
  • Example 1:
  • Example 2:

Creating Compliance Types

Compliance types are stored in a code table.
They can be added from:

Maintenance > Setup > Code Tables
choose C - Contact Management and then select code table Compliance Types [233]

When Compliance Types will be Applied

If you decide to use compliance types, you will need to think carefully about how/when  compliance items will be applied. Linking an item to one or more compliance Types will affect how and when the item gets enforced.

WARNING: Please take care when using Compliance TYPES, as this will affect when the compliance item gets applied. As soon as a compliance item is associated with a TYPE it will only be applied for bookings/placements at clients where that TYPE is applied. Example: In the example below, the compliance item CHK1 will only ever be enforced at a site that is using either CONS or MED as the 'Types' - it will never be applied at any other sites,The screenshot below shows where you set the TYPE that is in-use at a client,using the

Back to top

Using Compliance Types

When defining a new Compliance Item it is possible to allocate a Compliance Type to the item using the drop-down at the right hand side. It is possible to allocate more than one Compliance Type to a single Compliance Item.  (see below)

These same Compliance Types can be recorded against client records (or Sites) on the [Compliance] tab of the record to indicate that they require all Compliance Items of this type to be checked.

Back to top

How it Works

The [Compliance] tab of a candidate record is used to record which items they have and areas in which they are compliant.

When making a booking at a client, if the client record has a Compliance Type specified then the system will look at any compliance items of this Type in addition to any 'normal' compliance items which have no Type specified.

When holding a Compliance Type it can be recorded against a SITE, or (if the site is blank) then the system can revert to look at the main CLIENT record. This behaviour is controlled with a parameter (RecD, Flag(21) )

Example 1:

Assume you create a compliance type of 'Danger'
The compliance item HV Training is flagged as being of the Danger type, and marked as a warnable item for TEMP workers.

BBR Demolition Ltd has been set to indicate that Compliance Type 'Danger' is required.
JP Builders Ltd has no Compliance Type specified.

Candidate John Trowell has the HV Training items marked as complete.
Candidate Micky Bricks  does not have the HV Training item marked as complete.

i) Booking for John Trowell @ BBR Demolition is ALLOWED as he has HV Training.
ii) Booking for Micky Bricks @ BBR Demolition is NOT ALLOWED as he needs HV Training.

iii) Booking for John Trowell @ JP Builder is ALLOWED - HV Training is not considered.
iv) Booking for Micky Bricks @ JP Builders is ALLOWED - HV Training is not considered.

Back to top

Example 2:

Let's Suppose you have  Compliance TYPES of:

Now suppose you have some compliance items setup as below, all of which have been set as Mandatory  (i.e. The candidate cannot be booked without them) 

When making bookings, the system will check for the presence of these items, depending upon the COMPLIANCE TYPE that has been set for the client, i.e.

Back to top

Attachments (3)

bpK5hxGyHig1....jpeg
63.2 KB

ieEpUxK7Kvst....jpeg
114 KB

5SJF59hR1mLA....jpeg
98.4 KB