Functional standard / Foundation
Time
How the standard represents what is due, what was missed, and which way a patient is heading.
Schedules
A Schedule has every_days, anchor, until, and grace_days. The anchor is a date and time, and defaults to when the care action was created. Each occurrence is done, due, overdue, or missed, and adherence is derived from those. The server computes this. A conforming client does not.
Routines and the tick
POST /v1/routines/run raises a task for each routine occurrence that does not already have one, so running it twice does not duplicate work. POST /v1/tick processes schedules and expiries. An implementation decides how often to call them.
Trajectories and outcomes
A trajectory reads a series of observations for a code and reports its baseline, slope, and status. Outcomes state what is being aimed for, and when due, can raise proposals for a clinician.
Time in rules
Rule expressions read the current picture. For each observation code they see only the latest numeric value. A rule cannot yet ask about a window, a sequence, or the time since an event.