Sentinel Annual Recheck
Schedule annual sentinel-site rechecks, clamping leap-day anniversaries to the target month end.
Description
Annual rechecks require calendar arithmetic: the same month and day can fail to exist in a later year when the starting date is February 29.
Annual rechecks require calendar arithmetic: the same month and day can fail to exist in a later year when the starting date is February 29.
The tool returns recheckDates (recheck dates). Input measurements and model parameters are supplied by the caller; the tool computes the stated summary rather than acquiring those measurements.
When to use Sentinel Annual Recheck
Use Sentinel Annual Recheck when you already have startYear, month, day, recheckCount and want recheckDates. This is useful for checking a supplied calculation, documenting a measurement convention, or comparing observations prepared on the same basis.
How to use Sentinel Annual Recheck and understand its results
- Enter startYear, month, day, recheckCount using the field table below. Match the units, ordering and data boundaries described in the calculation.
- Run the tool after checking the stated bounds and matching paired observations or categories. A malformed request gives a tool error rather than a usable measurement.
- Read recheckDates. Use the calculation and interpretation below to distinguish amounts, ratios, signs and decision flags where applicable.
- Review the supplied parameters and assumptions before using the result in a report or comparing it with another observation.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| startYear | Start year | integer | Required |
| month | Month | integer | Required |
| day | Day | integer | Required |
| recheckCount | Recheck count | integer | Required |
Validate the calendar date and requested year count. Produce one ISO date for each following year; a leap-day anniversary becomes February 28 in a non-leap year.
recheck[i] = start date advanced by i calendar years, with day clamped to month end The symbols refer to the supplied quantities or generated values described above; unit conversions and comparison boundaries follow the stated implementation.
{
"input": {
"startYear": 2024,
"month": 2,
"day": 29,
"recheckCount": 2
},
"output": {
"recheckDates": [
"2025-02-28",
"2026-02-28"
]
}
}Limitations and assumptions
The caller decides whether annual review is appropriate. This creates dates rather than appointments, notifications or a disease-specific follow-up policy.
Numerical inputs must be finite. The tool checks its declared input shape and calculation constraints; those checks do not verify the quality, calibration or representativeness of the supplied observations.
Alternative or Complementary methods
Surveillance Followup Years: Schedule surveillance calendar years using caller-defined offsets after treatment completion. Gametocyte Clearance Followup: Track first observed zero gametocyte count and subsequent rebound in an ordered follow-up series.
Methodological background: Monitoring drug coverage for preventive chemotherapy.1
References
-
Monitoring drug coverage for preventive chemotherapy — World Health Organization
Similar or alternative tools
- Surveillance Followup Years
Schedule surveillance calendar years using caller-defined offsets after treatment completion.
- Gametocyte Clearance Followup
Track first observed zero gametocyte count and subsequent rebound in an ordered follow-up series.