Modifying Alert Properties

The General tab is shown when the Alert Properties dialog first appears. It contains editable details that help you define basic alert attributes, as well as read-only information regarding the alert’s creation date, the last time it was triggered, when it was modified and the name of the person who created it. The Alert History section presents dates and times generated by the system. All system-generated dates and times are displayed to users in their own time zone, as defined in their preferences.

Prerequisite: You must have the 'Admin - AlertsA warning that is sent out in the form of an email and/or an in-system alert notification under defined circumstances (e.g. an abnormally high number of complaints or incidents are reported, a high severity incident occurs, or when a file is ignored for a given period of time). Alerts are created by your administrator and are triggered at defined intervals (e.g. daily, weekly, monthly).' and 'Create Alerts' or 'Edit Alerts' functions enabled for your role.

To modify alert properties:

1. Open the Alert Properties dialog by editing the alert or creating a new one. See Managing Alerts and Creating Alerts for more information.
2. Enter up to 50 characters for the Alert Name and up to 255 characters for the Alert Description.
3. Choose an Alert Category (see Organizing Alerts with Categories).
4. (Optional) If the alert is private, check the Private Alert box. By default, the current owner is displayed as the Alert Owner but you can specify another user by selecting the Search icon and choosing a different user. Only this person and the administrators who can view/edit private alerts will see this alert.
5. Note: This does not affect alert notification settings. To manage privacy of in-system notifications for this alert, see Common Module Role Functions.
5. For the Repeat Alert check box, do one of the following:
   1. Leave the box unchecked. When an alert is triggered, the system will check the BlacklistAn RL6 feature that tracks sent alert notifications and controls the re-distribution of notifications when an alert is triggered multiple times at scheduled intervals. When there is a new alert, the Alert processor checks the Blacklist to determine whether or not a notification should be sent to a recipient. If no entry of a prior notification is found, a new notification will be sent to the recipient. But if a notification was sent earlier, no duplicate notification will be sent unless the Repeat Alert option in the Alert properties is checked or when there is an update to a related patient file. The black-list can be thought of as a do not call list. For all modules except Infection, the Blacklist is a combination of alert, user and file ID. For Infection, the Blacklist is a combination of alert, user and matching criteria of the alert definition.. If the system finds notifications sent previously to a recipient, no new duplicate notification will be sent for the file. (The system will only send an alert notification when it finds no prior notification was sent.)
   2. Check the box to allow recipients to receive repeat notifications in notification messages each time a schedule triggers an alert.
   3. Note: This field is read-only for Watchdog and HL7Health Level-7 is an international set of open standards used to format data and content, allowing different health information systems to easily and effectively communicate with one another. alerts.
6. Indicate the Alert Priority with a one or two-digit number. This field is used at the discretion of your organization and has no bearing on how the alert is processed. Rather, it allows users to quickly sort their alert notifications so the most important alerts are shown first.
7. Click OK to save and close the alert.