Great questions, and they hit the real complexity. Honest rundown of where it stands:
Handled today:
- Multi-dose daily schedules (two in the morning, one at lunch, one before bed) are the core case. You add a dose per time slot, each with its meds.
- A blister-pack-style slot works via the medications field: one dose entry per time, listing everything in that slot (e.g. "Keppra, Phenobarbital, Trazodone").
Not yet, and worth being upfront about:
- Finite courses (a 10-day antibiotic, a fixed dose count). Right now it assumes an ongoing daily schedule with no end date, so a course end-date / count is a clear addition.
- Titration (half-strength intro, full, then taper). The schedule is static, so today you'd edit it manually at each phase. Automated phased schedules are a bigger piece.
- Repeats / refill tracking. Not modelled yet.
The important one: PRN / "as required." You've put your finger on the case the current design doesn't fit at all. It's schedule-based, and as-needed meds aren't. And you're right that this is exactly where over-medication risk lives (paracetamol ceilings, dependency with the stronger painkillers). That needs its own dose type: an "as needed" med with a minimum interval and a max per 24 hours, where logging a dose checks against both and warns or blocks rather than silently allowing it. That's the safety feature, not a nice-to-have, so I'll prioritise it.
"Same as before": not currently, each dose is entered individually. A duplicate-dose / clone-a-schedule option would make complex regimens much faster to enter, and I'll add it to the list.
So the everyday "fixed times, multiple meds" case is solid; courses, titration, and especially PRN-with-limits are real gaps, and the PRN one is what I'd build first because it's about safety.