All BlueprintsHealth
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.
What you’ll build.
Repeat prescription requests. Patients see the medicines they are already on and ask for a repeat. A clinician works a queue and approves or declines each one with a reason the patient can read. Every decision stays on a record nobody can quietly change.
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.
Renewing a prescription
You can take a renewal request, put it in front of the right clinician, and show what the patient sees while it waits and after it is refused.
Roles and permissions
You can give users different roles and have the server refuse what a role may not do — not merely hide the button — and show the refusal working against a request the interface never offered.
Who read this record
You can show, for one patient, everyone who accessed their record and when — and explain why that log cannot be edited by the application.
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, 34 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Telling people apart
Somebody can make an account and come back to it, and nobody can hand themselves the right to prescribe.
4 tasks
- A patient can make an account the practice will recognise
- Coming back next week does not mean registering again
- Signing out on a shared machine means something
- A clinician account is issued, never claimed
What you already take
A patient can see the medicines the practice has them down for, and a correction never erases what was there before.
4 tasks
- A clinician records what a patient is on
- A patient sees their own list of medicines
- A medicine that is stopped leaves the list without leaving the record
- Correcting a dose does not erase the dose it used to be
Asking for a repeat
A patient asks for a repeat of something on their own list, and asking twice does not mean two requests.
4 tasks
- A patient asks for a repeat
- A patient can see where their request has got to
- Asking twice does not put two requests in the queue
- A patient can take back a request nobody has answered
Two sides of the request
A clinician sees every request waiting. A patient sees only their own, wherever they ask from.
4 tasks
- A clinician opens the queue of requests waiting
- Asking directly for somebody else's request is refused
- The rule holds in every place a request is reachable
- A request never waits for one particular clinician
Yes, no, and why
A clinician decides, once, and the patient gets a sentence they can act on.
5 tasks
- A clinician approves a request
- A decline says why, in words the patient can read
- Two clinicians cannot decide the same request
- A decision cannot be quietly changed afterwards
- A patient hears that their request was answered
A trail somebody answers for
Every decision and every look is on a record the product itself cannot rewrite, and somebody at the practice can produce it.
4 tasks
- Every decision is on the record, and the record says who
- Every look at somebody else's record is recorded, including the refused ones
- The product cannot rewrite its own trail
- One patient's trail can be produced without a developer
Proving the address is theirs
A repeat is only ever asked for, and answered to, an address somebody proved they own.
4 tasks
- Registering sends a link that proves the address
- An unverified account cannot ask for a repeat
- A link that never arrived can be asked for again
- Changing the address means proving the new one
Where patients can reach it
The practice is on the internet at an address worth printing, and a wrong release is undone before the morning surgery ends.
5 tasks
- A stranger can reach it without you
- Nothing it needs lives only on your laptop
- The email genuinely leaves
- An address a receptionist can read down the phone
- A wrong 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 a repeat prescription actually works
Domain you will not have: what a repeat is, why a clinician has to sign for it, and why "no" is the hardest screen in the product.
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.
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.
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 prescription renewal requests.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.