The overdue list — shipped inside Care Plans, not as an app.
Clinical · PHI-lite · Every specialtyThe useful half of this idea — the small overdue things across a panel of patients, ranked by how far behind the oldest one is, with the reason each is overdue — ships inside Care Plans as a read over the condition programmes and the recalls the clinic already keeps. It sets no dates of its own and stores nothing, so a second table would have been a second copy of the same facts. What is NOT built is the private scratchpad: a doctor’s own “check on this one in five days” would be a third register of dates beside the two this product already has, and nobody else could see it when the doctor is away.
It does not invent a schedule: every row names the programme milestone or the recall it came from, and nothing on the list is scored or graded.
Every app page carries this section. A listing with only benefits is an advertisement.NudgeList reads care-plan milestones, open recalls and writes nothing — it is a read. Its data class is PHI-lite. Every app works on the same patient record — nothing is copied into a silo.
It does not invent a schedule: every row names the programme milestone or the recall it came from, and nothing on the list is scored or graded.
Every record stays; only the workflow leaves.
NudgeList is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.