Other settings

Set business rules for reporting incidents, feedback, improvements and repairs

Program the field logic to automatically assign who the issue is reported to, who is notified and how it's coded for business area, meeting, and viewing permissions.

Business Rules Builder is an optional add-on for your platform. Click here to find out more.


Overview

Business Rules Builder gives you more control, adds built-in intelligence to how events are coded, ensures events are managed as per the organisation's policy, and reduces the risk of critical issues being overlooked. There is no limit to the number of business rules that can be programmed. Note: this feature is non-reversible.


Program business rules

Note: You need administrative permissions to program Business rules. Learn more

  1. Switch to Admin mode via your user account menu and select Business rules 
  2. Click on the edit icon beside the register you want to program a business rule for.
  3. Click on + Add business rule to add a new rule for the register or click on the edit icon to edit an existing business rule.
  4. Add your rule conditions (see below for more details on rule conditions)
  5. Click OK to add the rule
  6. Click Save to activate the rule

Setting the conditions of a Business rule

There are two sections to the Business Rules Builder form which is based on the framework for the conditional logic of: IF this Then:

IF fields:

Select one or more of the IF fields to set the conditions for your business rule. Depending on the register, different fields are available to specify the conditional logic. For example, on the Incident register you can use 'severity rating' to determine who the event is reported to, whereas on the Feedback register, you have the option to use 'feedback source', eg. client.

Note: Some fields allow you to select multiple options. For example, multiple incident types can be selected. This can support efficiency when programming the business rules

 
Use the Then fields to program the values for one or more of the following fields:

  1. who the event is reported to + fallback position (The item will go to the 'fallback' user if the original user's position is un-assigned)
  2. which meeting is to be notified
  3. which business area the event is to be assigned to - note this can be either an input to or output of the conditional logiqc 
  4. who can view the reported event by role eg CEO + EMT as well as additional personnel
  5. who is to be notified of the reported event 

  add business rule

Example:

In the example above, based on the program business rule that when an incident is entered where the Incident type is 'Incident' and the Incident area is 'Clinical', the incident will automatically be assigned to:

  • Florence Nightingale (or if her account has been made 'inactive' the incident will be assigned to Jacqueline McDonald)
  • the assigned business area will be 'General Practice'
  • the assigned meeting will be the 'Clinical Team Meeting'

Example

In the example below, all fields in the Assign component of the form have been programmed to auto populate based on what the User selects in the Incident details component of the form.  

incident_business_rule_example