This article provides information on how to create a new Requirement.
TABLE OF CONTENTS
Video Guide
Watch the short video or read below for more information.
Running time - 4 minutes
Create the Requirement
N.B. If you are creating a requirement that needs a new, custom workflow, please see our guidance on Creating Custom Requirement Types. Before creating the requirement you would need to build your forms and send us the workflow. Depending on your licence there may be an additional cost to create the workflow.
To create a new compliance requirement click on Administration from the left hand menu, then select Requirement types.
Here you will see all the existing Requirement Types currently in your system.
To add a new requirement click +New requirement type
There are 3 steps to complete:
Page 1 - Details
Enter the details:
- Name – The name you wish to give the compliance requirement, e.g. GDPR Training (The name is what is pulled out on the report)
- Description – A description of what the requirement is, e.g. An Introduction to the General Data Protection Regulation (The Description is what is displayed to the user. If the Name has been shortened for reporting purposes, the Description can be used to give the title of the requirement in full.
- Initial completion period – Once you have assigned the task to the individual for the first time, how soon do you need them to complete it? Using this information, the "Due Date" for the requirement will be calculated.
- Initial pending period – Once you have assigned the task to the individual for the first time, how long before the due date should the requirement flag as Pending on the user's dashboard and they are notified that the requirement is now becoming due? The Initial pending period should always be either the same or a lesser amount of time that the Initial completion period
Page 2 - Workflow
Select the workflow you require from the drop-down list.
Workflows are created by Radar Healthcare. There are 3 broad categories of workflow that you might be selecting:
Option | Description | Useful Resources |
1. Toolkit Workflows | The toolkit workflows have created by Radar Healthcare to capture common compliance options. Your licence agreement will outline if your system includes the Toolkit Requirement workflows e.g. Appraisal, DBS etc. | |
2. Training Workflows | Use the training workflows to create requirements that track different types of staff training. (e.g. Moving & Handling Training, Safeguarding Training, Medication Competencies etc.) This option uses a standard Training form and a workflow created by Radar Healthcare to capture compliance information. | |
3. Custom Workflows | If the toolkit and training workflows don't meet your needs, you can design your own custom workflows. This option is subject to your licence agreement and may include an additional charge. If you want a new workflow that is not already in the list, please see the article on the right. |
If you are unsure which workflow to choose please contact the Radar Healthcare Support Team who will be happy to help.
Does this item recur in the future? If so select YES.
- How would you like the next due date to be calculated? This is in reference to the recurrence and how it should choose the next due date, there are 3 options
- Calculated from date completed in Radar (E.g. If this is due every year and I complete the full requirement in the system today it will be due exactly 1 year in the future.)
- Calculated from date set in a form (E.g. If this is due every year and there is a question on a form to say "when did you attend the training" it will be due 1 year from that date)
- Set by a date in a form (E.g. If there is a question on a form to say "when does your DBS expire?", then the next requirement will be due on the date entered)
For the first two options above you'll have the following options:
- Reschedule after – How long after the previous requirement is completed should the next requirement be rescheduled? This can link to either the date that the requirement was completed in the system, or it can be linked to a date the user entered on the form (e.g. if they are retrospectively logging training).
- Pending period – How long before the next due date should the Requirement appear as Pending on the User's dashboard and they are notified that the requirement is now becoming due? E.g. for an annual training or compliance requirement, you may wish for it to flag to the user 1 month prior to them becoming non-compliant to give them enough time to complete the requirement.
Permission rule set – Assign the correct permissions to the requirement, this dictates who can see and complete this requirement. – it is important to ensure that the correct permissions are applied at this point. For more information on Permission Rule Sets please refer to our guide: The Permission Rule Set
Tags – Tags allow you to link requirements together and help you later with filtering and reporting, e.g. you may wish to filter on all mandatory requirements and exclude less critical requirements from a report. You can do this easily if you have tagged the requirements accordingly at this point when creating them. In order for your requirement to pull through into Dashboard widgets, they also need to have a Tag assigned, e.g. Mandatory Training. You can enter as many different tags as required – either select from the existing list, or type the name into the field to add a new Tag.
Once you have entered all the details for your new requirement, click NEXT.
Page 3 - Review
You'll now be presented with a summary overview of your new compliance type. If you have any changes please use the Previous button to go back through the menu options.
If you're happy with everything please select Create to complete the requirement type.
Your new Requirement will now be listed in the Requirement Types list, along with a summary of the settings we have just selected, and is now ready to allocate.
Select the pencil icon next to the requirement should you wish to edit anything.