Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

This screen is the Notification Policies administration page, accessible at /cl/notifications/policies. It manages rows in cl_notification_policies and cl_notification_escalation_chains.

​
Overview

The Notification Policies page lists all cl_notification_policies rows for the current organization, ordered by signal_type. Each row displays the signal type, SLA (formatted as seconds, minutes, or hours), dedup window, and an active/inactive toggle. Administrators can create a new policy via a sheet editor (PolicyEditorSheet), edit an existing one by clicking Edit, or permanently delete a policy after a confirmation dialog. Below the policy table, an EscalationChainEditor section lets administrators configure ordered recipient roles that are notified when an SLA is breached. Toggling the Active switch calls useUpsertNotificationPolicy immediately; no separate save step is required. Deletion is permanent and confirmed by a destructive dialog. Both the route and the in-page PermissionGate enforce cl.notification_policy.manage. The route also wraps the page in a FeatureFlagGate for cl.notification_service_enabled — if that flag is off, a NotificationServiceDisabledBanner is shown instead.

​
Who it’s for

Requires permission: cl.notification_policy.manage

​
Before you start

  • You must hold the cl.notification_policy.manage permission.
  • The feature flag cl.notification_service_enabled must be enabled for this route to render. If it is disabled, a NotificationServiceDisabledBanner is displayed and the policy list is not accessible.

​
Steps

1

Navigate to Notification Policies

Go to /cl/notifications/policies. If you see a disabled-service banner, contact an administrator to enable the cl.notification_service_enabled feature flag.
2

Create a new policy

Click New Policy. The PolicyEditorSheet opens. Fill in the signal type, SLA, dedup window, and severity rules, then save.
3

Edit an existing policy

Click Edit on any row. The same sheet opens pre-populated with that policy’s values. Save to apply changes.
4

Toggle a policy active or inactive

Use the Active toggle in the Status column. The change is saved immediately via useUpsertNotificationPolicy.
5

Delete a policy

Click the trash icon on a row. Confirm the destructive dialog. Deletion is permanent and cannot be undone.
6

Manage escalation chains

Scroll to the Escalation Chains section. Use EscalationChainEditor to configure ordered recipient roles for SLA-breach escalation.

​
Key concepts

A free-text identifier stored in cl_notification_policies.signal_type that categorizes the clinical event triggering the notification. SME: confirm the canonical list of valid signal type values.
The number of seconds within which a notification must be acknowledged before escalation begins. Displayed as seconds (s), minutes (m), or hours (h).
A window during which duplicate events of the same signal type are suppressed. Displayed in the same s/m/h format as SLA.
Ordered sequences of recipient roles stored in cl_notification_escalation_chains. When an SLA is breached, the next step’s role is notified.
When no policies exist, an empty state with a Create policy action is displayed. When data fails to load, an error empty state shows a sanitized error message.

Clinical

Overview of the Clinical core.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/cl.tsx
  • src/cores/cl/pages/notifications/NotificationPoliciesPage.tsx
  • src/cores/cl/hooks/useNotificationPolicy.ts