All BlueprintsHealth
Medication reminders
Somebody writes down what they have been told to take and for how long, and is reminded at the hour on their own clock: on the day they fly somewhere else, and on the two days a year that are not twenty-four hours long.
What you’ll build.
A medication reminder that gets the times right. You set a course with a start and an end and see every dose dated at the hour you will take it, including the Sunday the clocks change. Reminders go out at that hour on their own, and you say whether you took it.
What you’ll learn.
Each sprint is built around one skill. You show you have it in a pull request your team reviews, then explain it in a walkthrough.
Authentication
You can register and sign in a user, keep a request authenticated without asking for the password again, and explain where the credential lives in the browser and why there rather than somewhere else.
Patient records
You can record and retrieve a patient record, and demonstrate that a clinician outside the care relationship is refused — by the server, not the interface.
Booking an appointment
You can show availability, book a slot, and prove that two simultaneous bookings produce one appointment and one clear refusal.
Notifications people do not mute
You can notify a user when an event concerns them, show an unread count that survives a refresh, and honour a preference that says stop.
Background jobs
You can hand work to a worker, tell the user it is in progress, and show the result when it lands — and say what happens to that work if the process dies halfway.
Email verification
You can issue a verification link, activate the account when it is followed, and explain what the link contains and why it cannot simply be a user id.
Going live
Somebody who has never met you can open a URL and use the product — and you can say what is different about the copy running there, where its secrets come from, and what you do when a release turns out to be wrong.
The roadmap. 7 sprints, 35 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Somebody to remind
Somebody can make an account, come back to it, and the product knows where in the world they are.
4 tasks
- Somebody can register and land signed in
- Coming back tomorrow finds the same account
- Signing out on a phone that is not theirs
- Where they are is part of who they are
A course with an end
Somebody writes down what they take, how often, from when, and until when.
5 tasks
- Somebody writes down what they are taking
- A course that ends, and one that does not
- A course belongs to the person who wrote it down
- Three medicines at once read as one day
- Changing the dose does not change last week
The hour on their own clock
Every dose of every course is dated at the hour the person will read on their own clock, on all three hundred and sixty-five days.
5 tasks
- A plan they can read, day by day
- Every time is the hour in their own room
- The Sunday with twenty-five hours in it
- The Sunday with twenty-three hours in it
- Somebody who moves takes their doses with them
A reminder you can answer
The product speaks first at the hour of the dose, and the answer becomes the record.
5 tasks
- A reminder at the hour the plan already says
- Answering takes one action
- A dose nobody answers becomes a missed dose
- Nothing is said about a course that is over
- Silencing one medicine without silencing the rest
Work nobody starts
Reminders go out at each person's own local hour with nobody in the building, and never twice.
5 tasks
- Reminders go out with nobody pressing anything
- Eight in the morning happens all day
- One dose, one reminder, even on the long Sunday
- The message is worked out when it is sent
- A record of what went out, and what did not
An address that is theirs
Nothing is sent to an address nobody has proved they own.
5 tasks
- Registering sends a link that proves the address
- The link expires after a length of time, not at an hour
- The link cannot be guessed or used twice
- They did not get it, so they ask again
- An unverified account is useful and silent
Somewhere with its own clock
It is on the internet at its own address, and the machine it runs on has no opinions about time that anybody can see.
6 tasks
- A stranger can reach it without you
- Nothing it needs lives only on your laptop
- An address worth giving out
- The reminders actually arrive
- On time from a machine that is nowhere near anybody
- A bad release can be undone in minutes
Read before you build. The best engineers do.
Senior engineers read the docs before they touch the code. Every Blueprint comes with short documents on the product and its world, the kind a team hands a new hire. Read them well and you ask sharper questions and walk into every review prepared.
What you are building
The product, who it is for, and what finished means.
Taking medicine on time
Domain you will not have: what a course is, when the hour genuinely matters, and why a missed dose is a fact rather than a failure.
More health Blueprints.
Clinic appointment booking
Booking for one small clinic: patients find a slot that is genuinely free and take it themselves, the front desk sees the day at a glance, and nobody arrives to be told their time was given to somebody else.
Prescription renewal requests
Repeat prescriptions for one practice: patients ask for more of what they already take, a clinician approves or declines with a reason the patient can read, and every decision stays on a record the product cannot quietly rewrite.
Immunisation record
An immunisation record for families: a parent sees what each child has had and what is due next, a practice sees which of its children are behind, and the card comes out as a file a school will accept.
Build medication reminders.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.