Notifications And Activity
Inbox, activity logs, ops alerts, and AI review notifications inside the tenant workspace.
InboxActivity logOps alertsAI completion notices
Details
Notification Model
Notifications remain a shared operational substrate across modules and now surface AI draft completion, stale-state warnings, and scheduled ops reminders.
- AI draft completion and stale notifications route back to the AI Run Log.
- Inventory reminders and Smart Insights digests still produce operational inbox entries.
- Activity logs remain clinic-local, matching the tenant database boundary.
Workflow
Respond To A Notification
- Open the related clinic record from the notification instead of acting from the message alone.
- For AI completion or stale-state warnings, review the AI Run Log, source record version, and reviewer status.
- For inventory or appointment reminders, confirm the underlying pharmacy item or schedule state before dismissal.
- Record the corrective action in the clinic-local activity trail.
- Verify the intended role receives the event and unrelated clinic members do not.
Verification
Channel And Queue Checks
- Confirm unread count, detail link, read state, severity, and source module.
- Check queue workers and scheduler when reminders or AI completion notices are delayed.
- Use the activity log to distinguish notification creation from email or SMS delivery.
- Avoid including diagnoses, prescriptions, or other sensitive clinical details in external notification previews.
Coverage appendix
This page is tied back to routes, views, requests, tests, and implementation files in the generated docs coverage appendix.