All BlueprintsHealth
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.
What you’ll build.
A vaccination record for families. A parent adds a child, writes down the jabs they have already had, sees what is due next and what is already overdue, and downloads a card a school will accept. The practice sees which of its children are behind.
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.
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.
Search and filtering
You can search a list by keyword, combine that with filters, and say what the database does to answer the query — including which part uses an index and which part cannot.
File uploads
You can upload a file from the browser, store it somewhere the application does not own, and show it again on a later request — and say where the bytes travelled and what the database actually holds.
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. 8 sprints, 41 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Somebody the record belongs to
A parent can make an account and come back to it, and a practice account cannot be issued from the sign-up form.
4 tasks
- A parent can register and land signed in
- Coming back in three months does not mean signing up again
- Leaving properly on a shared family device
- Practice accounts exist, and cannot be self-issued
One child, one history
A parent can put a child on the system with the vaccinations they have already had, and nobody outside the family can read it.
5 tasks
- A parent adds a child
- A parent writes down what the child has already had
- A parent sees only their own children
- A child can have a second parent
- A family with more than one child
What is due next
From a date of birth and what has been given, the product says what is coming and when.
6 tasks
- The schedule is written down once
- A child's timeline: what has been given and what is coming
- A dose given too early or too close does not count
- The timeline reads at a glance on a phone
- A wrong date is corrected without losing what was there
- A birthday is the same day everywhere
Late is not the same as missing
A dose that should already have been given is called late, by something that works it out without being asked, and a child who started late gets a schedule they can follow.
5 tasks
- A dose past its date is called late, and says how late
- A child who started late gets a schedule they can follow
- A dose that can no longer be given stops being called late
- Something works out who is behind every night
- A parent is never shown last night's answer
The practice's list
A practice sees which of its children are behind, in an order that does not shuffle underneath them, and records the dose it has just given.
5 tasks
- A child is on a practice's list
- The list: which of our children are behind, worst first
- Page two never skips a child
- Narrowing the list, without it quietly lying
- A nurse records the dose they have just given
The card the school asks for
A parent takes away a file a school will accept, and the paper card behind it is attached to the record.
5 tasks
- A parent attaches the paper card
- The card comes out as a file
- The card says what was confirmed and what was reported
- The card is never out of date
- Having the link is not the same as being allowed
Proving the address
An account belongs to the person holding the inbox, and somebody locked out can get back to their children.
5 tasks
- A new account proves the address before it holds a child
- The link cannot be guessed, reused or kept forever
- Mail is slow, and sometimes never arrives
- Changing an address proves the new one first
- A forgotten password does not cost a family its record
Put it where parents are
The record is on the internet at its own address, the files and the mail are real, and a bad release can be undone.
6 tasks
- A parent can reach it without you
- Nothing it needs lives only on your laptop
- The email actually arrives
- The cards and the photographs survive a deploy
- An address worth putting on a card
- 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.
How an immunisation schedule actually works
Domain you will not have: ages rather than dates, minimum gaps, catch-up, and why a school asks at all.
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.
Therapy intake and consent
Intake for a small therapy practice: new clients fill in one form over as many evenings as they need, consent is recorded against the wording they actually read and the date they read it, and a practitioner sees the clients who are theirs and nobody else's.
Build immunisation record.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.