Roche RIS Feedback Portal

Please submit any feature requests and vote on ideas that have already been submitted to indicate your interest in seeing them developed

Alert Summary Widget (ASW)

Business problem

Busy laboratory users must scan several dashboard widgets to understand active alerts. Alert information is fragmented by widget and competes with operational information, creating information overload, slower triage, and a risk that the most relevant alerts are missed or deprioritized.

Customer problem to solve

Information overload on busy dashboards hinders timely prioritization of critical laboratory events.

Users need a single, fast way to see and prioritize active dashboard alerts without losing the context or data held by the originating widgets.

Today, laboratory professionals using navify Monitoring must visually scan across multiple widgets on a dashboard to identify which ones are currently in an alert state. In labs with dense dashboards (e.g., 6–10+ widget instances), this creates several pain points:

  1. Alert Fragmentation: Alerts are scattered across individual widgets (LST, CQC, CNS, ORR, IMS, IST, etc.), forcing users to mentally aggregate and prioritize across the entire screen — especially problematic on large multi-monitor setups or small screens.

  2. Missed or Delayed Response: Critical alerts can be overlooked when buried among widgets that are in a "healthy" state, leading to delayed corrective action on time-sensitive items (e.g., late samples, QC failures, instrument disconnections).

  3. No Mechanism to Suppress Non-Actionable Alerts: Some alerts, while valid, may not require action from the user viewing a particular dashboard (e.g., a known calibration delay on a secondary instrument). Currently, there is no way to acknowledge or dismiss these, adding noise.

  4. Lack of a Prioritization Layer: Users cannot quickly rank or triage alerts by severity or widget type without physically inspecting each widget.

Proposed outcome

Provide an Alert Summary Widget: a consolidated, one-stop view of all active alerts currently shown across dashboard widgets. The view should help users quickly assess and prioritize what needs attention.

Initial scope

  • List active alerts surfaced by dashboard widgets in one summary view.

  • Show enough context to support triage, such as originating widget, alert type or severity, and current status or time where available.

  • Allow alerts to be removed from the summary either manually or through a user- or lab-defined rule.

  • Keep summary removal separate from the originating widget: it must not delete, change, or suppress the source-widget alert information or its underlying data.

Visual Concept:

  • Available in all standard widget sizes (small, medium, large).

  • In small size: shows a count badge per severity (e.g., 🔴 3 | 🟡 5 | 🟢 12) - Calculation TBD (configurable vs fixed?)

  • In medium/large size: shows the full alert list with details and dismiss actions.

Product boundaries

  • This is a dashboard triage and prioritization capability, not a replacement for the future navify Portal notification system, which addresses mobility and cross-channel notifications.

  • It does not alter alert generation, source-widget behavior, or the alert lifecycle.

  • Any summary-level removal should be reversible and auditable; the applicable permissions and rule model require discovery.

Expected value

Benefit

Impact

Faster Alert Triage

Lab technicians can immediately see what requires attention without scanning the full dashboard — Reduces dashboard scanning effort and cognitive load for busy labs.

Reduced Alert Fatigue

The dismiss/suppress capability prevents known, non-actionable alerts from cluttering the view — a key concern in high-volume labs.

Improved Operational Efficiency

Aligns with navify Monitoring's intended purpose of enabling lab professionals to "proactively monitor their systems through near real-time alerts of workflow issues" (per the Intended Use Document).

Foundation for Future Enhancements

Serves as a precursor to more advanced alert management (rule-based suppression, alert history/audit trail, integration with Portal notifications).

Competitive Differentiation

No equivalent "alert aggregation" layer exists in comparable lab monitoring solutions — positions nMon as a more mature operational intelligence tool. Creates a foundation for future preference or relevance-management capabilities without affecting source data


Discovery questions

  • Which alert metadata and sources are technically available for aggregation?

  • Which rule criteria are meaningful and safe for labs?

  • Should prioritization rules be built in to the widget, and if so customizable by the user? Should users be able to reorder them?


Relationship to Existing Ideas & Roadmap

Related Item

Relationship

NMON-I-70 — Additional notification possibility

Complementary. NMONI-70 / Portal Notifications address off-screen/mobile alerting. ASW addresses on-screen dashboard alert consolidation.

NMON-I-64 — Mobile App

Independent. ASW is dashboard-only; mobile is a separate channel.

NMON-I-123 — Ability to remove samples from widget via nMon UI

Related pattern. ASW dismissal is similar in concept (user-driven suppression) but operates at the summary layer, not the source widget.

NMON-I-136 — CNS UI consistency

Neutral. ASW would consume alerts from CNS but is not dependent on UI changes.

NMON-I-170 — Prioritize actionable insights over raw data

Adjacent. It focuses on AI-driven recommendations, whereas the summary widget improves visibility and prioritization of existing alerts.

  • Guest
  • Oct 22 2026