Skip to content
  • There are no suggestions because the search field is empty.

Alert Overrides (New)

Organizations may override personal alert settings

 

This article applies to BloodCOMM version 3.2.0, which may not be released at this time.  Please refer to the "Legacy" articles for instructions on configuring the legacy system.  https://info.deltadevteam.com/bloodcomm#alerts

IMPORTANT: Action Required for Alerts

In order to receive organizational alerts, every user in your Organization must properly set up their "Alerting Channels". For example, this means verifying email and phone number, or enabling Push Notifications.   Individual users' verification status is visible on the Users tab.  Read more. 

 

Default Excursion Alerts

All organizations will have Excursion Alerts enabled for all users and all devices by default. This means that every user will receive an alert whenever a device they have access to crosses the 2°C or 6°C threshold.

It is highly recommended to keep this setting enabled to ensure compliance with AABB requirements.

To limit which users receive alerts for specific devices, you should set up your organization's Teams.

 
Configuring Organization Alerts (Admin Guide)

As an administrator, you have the ability to set mandatory Organization Alerts. This allows you to push global alert settings down to your users, ensuring that critical notifications—such as a temperature excursion on a blood transport cooler—are received by your team at the exact thresholds you define.

Organization alerts cannot be modified or deleted by end users.  Users will receive the specified alerts under the following conditions:

  • The relevant "Alert Channel" (i.e., SMS or email) has been set up
  • The user has not disabled "Cloud Alerts" entirely
Using the Alert Configuration Wizard

Setting up an Organization Alert is very similar to setting up a personal alert. You will use the standard Alert Configuration Wizard, which guides you through selecting the Alert Type (e.g., Device Temperature, Time Until Excursion), Device Subscription, Thresholds, and Notification Channels.

The Key Difference: User Assignment

Because you are configuring an alert on behalf of others, the Organization Alert wizard includes one unique step not found in personal settings: User Assignment.

During this step, you will choose exactly who receives this mandatory alert:

  • All Users: The alert will be assigned to every user in your organization.
  • Specific Teams: The alert will only be assigned to users within the specific Team(s) you select.

Important Note on Team and Device Routing: When you configure an Organization Alert for a specific Team, BloodCOMM uses intelligent routing to prevent alert fatigue. The alert will only trigger for the intersection of users and devices on that shared team.

If you set the User Assignment to "Station 4 Team" and the Device Subscription to "All Devices", BloodCOMM will only alert the users on the Station 4 Team when a device also assigned to the Station 4 Team triggers the threshold. They will not receive alerts for Station 5's devices.


Summary and Review

At the end of the wizard, a summary will display all selected settings for your review. If you are updating an existing Organization Alert, the summary will highlight the exact differences between the old and new settings before you save.