Notifications
Patients, coordinators, and doctors receive push notifications at key points in the case journey. Some notifications are sent automatically on a schedule; others are triggered by user actions.
Automated notifications (scheduled)
Section titled “Automated notifications (scheduled)”flowchart TD Schedule[Scheduled job runs] --> Check[Find eligible cases] Check --> Send[Send push notification] Send --> Mark[Mark case so it is not sent again]
Two automated flows run on a schedule:
Draft reminder
Section titled “Draft reminder”When: A case has been left in draft for at least 24 hours without being submitted.
Purpose: Remind the patient to finish and submit their case.
Sent once per case — the same patient will not receive duplicate draft reminders for the same case.
Overdue report reminder
Section titled “Overdue report reminder”When: A case has passed the expected report delivery window (based on review-type rules).
Purpose: Alert relevant parties that the report is overdue.
Sent once per case for the overdue condition.
Action-triggered notifications
Section titled “Action-triggered notifications”Notifications are also sent when specific business events occur, for example:
| Event | Typical recipients |
|---|---|
| Coordinator assigned | Coordinator, patient |
| Payment successful | Coordinator, patient |
| Doctors assigned | Assigned doctors, patient |
| Documents requested | Patient |
| Medical opinion submitted | Coordinator |
| Final report ready | Patient, coordinator |
| Case cancelled or rejected | Affected parties |
Manual overdue notification
Section titled “Manual overdue notification”A coordinator can manually send an overdue-report notification for a specific case from the doctor app when follow-up is needed.
Technical reference: scheduler endpoints, queue processing, and notification codes (e.g. UCP98, UCP105) are documented in API Flows → Scheduler and the worker source under src/services/scheduler/.