Notification Settings - enable alerts and set scan intervals

Use Notification Settings to choose which events the LIS should watch for and how often to check. Set a global polling interval in minutes, then enable specific notification types and configure their options. Notifications help staff act quickly on transmission errors, billing follow‑ups, QC issues, and TAT violations.

Global frequency

• Notify every [n] minutes: how often the LIS scans for new items that match your selections.

Notification types (as shown in the form)

• Pending Calls
  • Alerts for outstanding call tasks that require follow‑up.
• Expired QC Lots
  • Flags control lots that have reached expiration.
• Failed Result Transmissions
  • Reports, faxes, emails result deliveries that failed.
• Failed Requisition Transmissions
  • Requisition messages that failed to send.
• Pending Collection Letters
  • Accounts queued for collection letters that need action.
• Delinquent Patients
  • Patient balances in delinquent status.
• Delinquent Clients
  • Client balances in delinquent status.
• Orders with Pending Billing
  • Orders not yet invoiced. Enter a number to limit the alert (e.g., only show orders older than N days or over a threshold count, per your build).
• Pending Online Payments
  • Online/portal payments awaiting posting, only used on semi automatic online payment portals.
• Missing Info Updated
  • Orders whose previously missing demographics/insurance were updated and may now be ready for billing.
• TAT Violation
  • Notifies when tests exceed configured TAT. Options on this row:
    • Threshold h:m (e.g., 00:05) — tolerance or grace beyond the target before alerting.
    • Basis (e.g., Ordered) — which timestamp anchor is used for TAT (your system offers Ordered/Collected/Received).
    • Apply to the last [n] days — lookback window for finding violations.

📘 Instructions

1. Open Settings → Notification Settings.
2. Set Notify every [n] minutes.
3. Check the notification types you want to monitor.
4. Configure per‑type options (e.g., Orders with Pending Billing threshold; TAT Violation h:m, basis, and lookback).
5. Click Save.
   
6. Open your notifications window when the Notifications label turns blue.

Best practices

• Start with a 5–15 minute scan interval; adjust based on volume and performance.
• Enable Failed Result/Failed Requisition Transmissions and TAT Violation for operational awareness.
• Use a 7‑day lookback for TAT violations to keep lists actionable.
• Route follow‑ups: assign staff responsibility for each category (e.g., billing team for Delinquent/Orders with Pending Billing).

Troubleshooting

• No alerts are appearing: confirm the interval isn’t set too high, types are checked, and there are qualifying records within the lookback.
• Too many alerts: increase thresholds (e.g., age/quantity), shorten lookback, or narrow operational filters where available.
• TAT looks wrong: verify test‑level TAT settings and the selected basis (Ordered/Received/Collected).
• Transmission failures persist: review Transmission Logs for errors and requeue after fixing destinations.