All BlueprintsHealth
Clinic referral handoff
One clinic refers a patient to another. The receiving end accepts or declines with a reason, both clinics can see every referral still waiting on an answer, and one that has waited too long is chased without anybody remembering to chase it.
What you’ll build.
A referral system between clinics. One clinic sends a referral carrying only what the other clinic needs to see. The receiving clinic accepts or declines it with a reason, and the sender is told without watching the screen. Both see everything still waiting on the other side, and referrals nobody has answered are chased on their own.
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.
Referring a patient onward
You can create a referral, share exactly the records it covers, and show that access ends when the referral does.
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.
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. 8 sprints, 40 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Two clinics, two front doors
Somebody can set up a clinic, bring a colleague into it, and sign back in to the same one tomorrow.
4 tasks
- A clinic registers itself and lands inside it
- Coming back tomorrow, and leaving a shared machine
- A colleague joins the clinic rather than starting a new one
- The clinic outlives whoever registered it
Sending it
One clinic writes a referral, chooses who it goes to, and the other clinic can read that referral and nothing else.
5 tasks
- A clinic says what it treats, and can be found by it
- Writing a referral about a patient
- Sending it puts it in front of the other clinic
- A clinic reads the referral it was sent, and nothing else about that patient
- A referral sent to the wrong clinic can be taken back
The other end answers
The receiving clinic accepts or declines with a reason, once, and a referral that is finished stops giving anybody access.
5 tasks
- The receiving clinic accepts a referral
- Declining takes a reason the sender can act on
- A referral is answered once, and only once
- A finished referral stops giving access
- The history of a referral settles who did what
Neither side loses track
Each clinic opens one screen that is its own outstanding work, and nothing hides in it while they work through it.
5 tasks
- Not yet opened and not yet answered are different things
- The receiving clinic works one queue
- The sending clinic sees everything it is waiting on
- A long list narrows to the ones that matter
- Working a queue that is changing does not hide a referral
Told without watching the screen
Each clinic hears what happened to its referrals without keeping the product open, and a busy day is one message.
5 tasks
- The receiving clinic is told a referral has arrived
- The sending clinic is told what the answer was
- A message says what it is about without saying who it is about
- A dozen answers in an afternoon is one message
- Urgent does not wait for the summary
Nothing waits forever
The product notices an unanswered referral on its own, chases it once rather than four times, and says when it could not.
5 tasks
- The summaries go out on their own
- What counts as too long is a number the clinic chose
- A referral nobody has answered is chased
- Nothing is chased twice for the same reason
- Work that failed is somebody's problem
Proving the address
A clinic can only be referred to at an address somebody there has proved they can read.
5 tasks
- A new clinic proves it can read the address it gave
- A clinic nobody can reach cannot be referred to
- The link cannot be guessed, reused, or used a year later
- Mail that is slow does not strand a clinic
- Changing where a clinic is contacted proves it again
Where both clinics are
Two clinics on two different networks use the same product at the same address, and nobody has to keep a laptop open.
6 tasks
- Two clinics on two networks reach the same product
- Nothing it needs lives only on your laptop
- The overnight work runs there too
- The mail genuinely arrives at a clinic
- An address a clinic could put on a letter
- 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, the two organisations that use it, and what finished means.
Both ends of a handoff
Domain you will not have: what a referral is, why the gap between sending and answering is the dangerous part, and what a decline is really for.
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 clinic referral handoff.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.