Blood Donor Matching and Request Coordination
A platform matching urgent blood requests to eligible nearby donors, respecting blood group compatibility and donation eligibility intervals, and notifying by SMS because that is what reaches people. The engineering is in eligibility rules and privacy, not in the map.
Intermediate
A small team, or one strong student willing to learn something new.1 semester, 2 students
5 to ship
3 optional extrasSuggested stack
What you should ship
- Donor registry with blood group, location, last donation date and contact preferences
- Compatibility and eligibility engine encoding blood group matching and minimum interval between donations
- Geospatial search returning eligible donors within a configurable radius, ordered sensibly
- SMS notification flow with accept and decline, and escalation to the next group when nobody responds
- Privacy model where a donor's contact details are never exposed until they accept a request
If you have time left
- Hospital verification so requests cannot be raised anonymously
- Donation history with reminders when a donor becomes eligible again
- Rare blood group registry with a wider search radius
The problem
Urgent blood requests currently circulate through personal messaging and social media, which is slow, unverified, and reaches mostly people who cannot donate. Meanwhile willing donors are not contacted because nobody has a list.
What you build
A registry, an eligibility engine, geospatial matching and an SMS notification flow with escalation.
Why SMS rather than an app
The people you need to reach will not have installed your application. A donor registers once through a link and is contacted by text message thereafter. Designing for that constraint is a realistic engineering decision and worth defending in your report.
The part that requires care
Eligibility rules. Blood group compatibility is a fixed table and easy. The minimum interval between donations, deferral after illness or travel, and age and weight criteria vary by jurisdiction and must be sourced from your national transfusion service and cited. Getting this wrong is not a bug, it is a safety problem.
Privacy design
A donor's phone number must never be visible to a requester before the donor accepts. Build the notification flow so the platform mediates contact, and describe the threat model explicitly: this is a database of health information about identifiable people.
Scope warning
Do not attempt inventory management for blood banks. Matching a request to willing donors is the project.
Ideas and guidance, not finished projects
These are project ideas and scoping guidance, published free for students to use as a starting point. I do not build, write, or sell final-year projects, and I do not complete coursework for anyone. Take an idea, make it yours, and build it.
Not sure this one fits you?
I help students pick an idea that matches their skills and their deadline, then scope it down until it is finishable. Guidance only, never done for you.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Every session is free; a few slots open each week.
Follow along
New writing, resources and project ideas land here first.