• Notification - This is the message that will be received by the recipient. It can be in a form of email, push notification or newsfeed.

• Notification Trigger - This is an event that happened within CareVision that can trigger a notification. There’s a lot of notification triggers that are available in the system and each trigger can have their own unique behavior (eg, Forgot Password, Leave Approval, Publish bookings, etc)

• Notification Channel - This is the method on how the notification was sent to the user. Currently we have 3 notification channels:
  

• Email - this sends an email message to the recipient’s email address
  

• App Notification - this sends a push notification to the recipient’s mobile device
  

• Newsfeed - this creates an entry on the user’s CareVision account in both mobile and web portal
  

• Notification Recipients - This is the person or group of users that will receive the notification. We have 3 types of recipients:

  • Recipient Groups - these are recipients that can be assigned by the organizations in the settings page. Some of the available recipient groups are Named User, Target List, Client Case Manager, Security Roles, etc. More details will be explained in the sub-section below.

  • Default recipients - these are custom recipients that will be hardcoded within the code that can be enabled/disabled in the settings page by the organizations. This can follow multiple criteria and complicated logics. However, organizations won't have the ability to change the criteria. They can only enable or disable it.

  • Required Recipients - these are the list of recipients that are hardcoded within the code and can also follow complicated logics. However, this can't be disabled by the organization and the notification will always be sent to the recipient no matter what the settings is.

• Merge Variables - This is a list of variables or placeholders that can be placed into the subject, title or body of the message to personalize the notification or to include some related information into the message. Each notification trigger has its own custom set of merge variables (eg. firstname, lastname, etc). Merge variables should be enclosed in double curly braces (eg. {{firstname}}) and it will be automatically replaced by the actual value once the notification is sent. More details will be explained in the sub-section below.

Recipient Group Types

• Named User
  • With this option you can select any specific person from your registered users for the notification to be sent to. Useful when there is just a few specific people responsible for responding to the notification. 
• Target List
  • Use the Target Lists module to build a dynamic segmented list of system users that meet certain criteria at the time the notification is triggered. 
• Client Case Manager 
  • If a trigger is related to a client in some way, you can choose to send the notification to that clients active case manager as per their care / support plan. 
• Security Roles 
  • Use security roles if you want to send out a bulk update to a large group of staff based on their core security role. 
• Departments 
  • Use this security role to send out a bulk update to all staff in a certain department at the time of the trigger.
• Job Titles 
  • Use this security role to send out a bulk update to all staff in a certain job titles at the time of the trigger.
• Affected Users 
  • This is a default for all triggers, the users affected by or related to the record that initiated the trigger for the notification, i.e. created by, modified by, about user, attendees, allocated etc. 
    
• Staff Related
  
• Staff
  
• Staff Manager
  
• Department Head
• Client Related
  
• Client
• Client Contact by Contact Type
  
  Contact Types
  
  
• Billing Contact
  
• Rostering Consultant
  
• Busines Development Consultant
• Care Plan Manager

Enabling / Disabling Notifications

In the “Settings > Notification Settings” section of the New Management Portal , you can see the list of all available triggers in the system.

Each trigger can be set individually to be able to send different types of notifications to different users of the organizations. A trigger can have multiple settings and each setting is associated to one notification channel.

Here’s an example use-case of notification settings:

       Whenever a leave of the client ends,  organization wants to send notifications an email to a specific user (John Doe), another email to the Client Case Manager, and a newsfeed to all CareorgAdmins.

To do this, we need to create 3 settings under the “Client Leave Ends” trigger:

• Use “Email” channel and select “Named Users” for the recipient group, then select “John Doe” in the list of users

• Use “Email” channel and select “Client Case Manager” for the recipient group

• Use “Newsfeed” channel, select “Security Roles” for the recipient group, then select “CareorgAdmins” in the list of recipients
  
  

Although not recommended, it’s possible to send emails to individuals that are not part of CareVision. Under Email channel, just populate the “Other Recipient” field with the recipient’s email address.

Customizing Notification Messages

Notification subject and messages can be customized for each channel. Merge Variables can also be used to make the message more personal. For example, if the organization wants to include the name of the invited user and the name of the organization on the email subject whenever they send an staff invitation, they can use this on the subject field: "Hi {{FirstName}}, you're invited to join {{CareOrgName}}". The available merge variables that can be used for the current trigger are listed at the lower right side of the screen (under “Merge Field Look up”).

 

Custom Email Templates

By default, emails will use the regular templates of CareVision. However, there are cases where an organization wants to use a customized template (with their logo, branding and custom message) for certain triggers. We can do this but this will require additional implementation time in our side. Please contact support if you want to avail this feature.