mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 23:33:29 +00:00
feat(medications): make low-stock alert reorder-lead-time aware
The low-stock alert fired when the projected runway dropped below the user threshold (default 7 days). For a sparse cadence — a weekly injection's 7-day floor is barely one dose-interval — the warning landed with about one dose left, too late to reorder before the supply ran out. Add an optional per-medication reorder lead time plus a user-level default (0–60 days, default 10) and widen the alert trigger to max(lowStockRunwayDays, leadDays + cadenceIntervalDays), so the warning lands before the last dose for any cadence. Because the trigger is a max() over the user floor it never shrinks anyone's current threshold; a daily med with no lead keeps its prior boundary. The push body and the card notice surface concrete dates — supply runs out around <date>, reorder by <date> — with a last-dose informational state and the days/units fallback when supply data is thin. Retire the stale fixed 4-dose count threshold on the GLP-1 details endpoint and route its card lowStock flag through the same runway evaluation so the card and the daily cron agree. Surface the lead default in the low-stock settings card with progressive disclosure; a single medication can override it. Additive schema: nullable Medication.reorderLeadDays (migration 0161, no backfill) and notificationPrefs.medication.reorderLeadDays. OpenAPI regenerated.
This commit is contained in:
1 parent
52bf985734
commit
08aa655be4
29 files changed
+1060
-97
No files matched your search
@@ -0,0 +1,19 @@
|
||||
-- v1.17.0 — reorder lead time for the medication low-stock alert.
|
||||
--
|
||||
-- The low-stock alert previously fired only when the projected runway fell
|
||||
-- below the user's threshold (default 7 days). For a sparse cadence (e.g. a
|
||||
-- weekly injection) 7 days is barely one dose-interval, so the warning landed
|
||||
-- with about one dose left — too late to reorder before the supply ran out.
|
||||
--
|
||||
-- `medications.reorder_lead_days` carries an OPTIONAL per-medication reorder
|
||||
-- lead time (days between placing an order and the new supply arriving). The
|
||||
-- alert engine adds it, plus one dose-interval, on top of the user threshold
|
||||
-- so the warning lands before the LAST dose for any cadence. NULL = inherit
|
||||
-- the per-user `notificationPrefs.medication.reorderLeadDays` default.
|
||||
--
|
||||
-- Additive + back-compatible: the column is nullable with no backfill; every
|
||||
-- existing row keeps NULL and inherits the global default. iOS picks the field
|
||||
-- up without a migration of its own.
|
||||
|
||||
ALTER TABLE "medications"
|
||||
ADD COLUMN "reorder_lead_days" INTEGER;
|
||||
@@ -1408,6 +1408,14 @@ model Medication {
|
||||
/// against. A changed threshold re-arms the medication even while
|
||||
/// the runway stays low, so the user hears about the new crossing.
|
||||
lowStockNotifiedThresholdDays Int? @map("low_stock_notified_threshold_days")
|
||||
/// v1.17.0 — optional per-medication reorder lead time in days (how
|
||||
/// long between placing a refill order and the new supply arriving).
|
||||
/// The low-stock alert adds this lead plus one dose-interval on top of
|
||||
/// the user threshold so the warning lands BEFORE the last dose for any
|
||||
/// cadence. NULL = inherit the per-user
|
||||
/// `notificationPrefs.medication.reorderLeadDays` default. Additive; no
|
||||
/// backfill.
|
||||
reorderLeadDays Int? @map("reorder_lead_days")
|
||||
createdAt DateTime @default(now()) @map("created_at")
|
||||
updatedAt DateTime @updatedAt @map("updated_at")
|
||||
|
||||
|
||||
Reference in new issue
Block a user