Built on Nigeria's Postcode

Showcase

BloodLink

Emergency response and public services · Enugu North, Enugu · prototype

The problem it solves

When a patient in Nigeria needs blood urgently, the search usually falls on the family. A doctor writes down the blood group and the number of units, and relatives start phoning friends, posting in WhatsApp groups and going from one blood bank to the next. Hospital staff do the same from their side. These appeals reach people who are the wrong blood group, who donated too recently to give again, or who live on the other side of the city. Promises made in a chat are never tracked, so nobody knows who is actually coming until it is too late. Even location is vague: “behind the market in Abakpa Nike” tells a donor nothing about how far away the hospital is, and tells the hospital nothing about which donors are close. BloodLink is for the people caught in this: hospitals and blood banks that need donors fast, families who are sent out to find them, and voluntary donors who want to help but only hear about a need by chance. A verified hospital raises a request with the blood group, component, units and deadline. BloodLink finds donors who are compatible, eligible to give today and nearby, texts them starting with those in the hospital’s own postcode area, and tracks each pledge until the hospital records a donation, a no-show or a deferral at screening. When a pledged donor drops out, a standby donor is called in automatically, and the request closes itself once enough units are pledged. Nigeria’s digital postcode fixes the weakest link, which is location. Pinning every donor, hospital and request to a postcode turns “nearby” into a real distance. It lets a family find the nearest verified hospital or blood bank from a code instead of a description, and it shows donor coverage by postcode area and LGA, so it is clear where donors are missing. A donor’s full postcode is never stored; BloodLink keeps only the area.

How it uses the postcode

Location is the core of emergency blood matching, and BloodLink uses the postcode at every step where location matters. Registration. Donors and hospitals add their postcode by typing it, or by pressing “Find from my location”, which uses NIPOST reverse search to return the postcode of the building they are in. Lookup Level 1 checks the code is assigned before we save it, and Level 2 adds the state, LGA and locality names; the LGA name also comes from NIPOST’s free reference data. Verifying hospitals. Before a hospital can raise requests, our administrator sees NIPOST’s record of its building (Lookup Level 3: address and building use) next to what the hospital registered, so a fake “hospital” in a residential building stands out. Family requests. A family member searching for blood finds verified hospitals on BloodLink’s public page by typing the hospital’s postcode, or their own to see hospitals close to home first, ranked by how closely the postcodes match, or by their location. The appeal goes to that hospital, whose staff confirm the patient before any donor is alerted, so families get a real tool and nobody can send fake appeals. Matching in widening circles. BloodLink alerts compatible, eligible donors in rings that follow the postcode’s own structure: the hospital’s own area first, then its district, LGA and state, nearest first within each ring. Alerts that work on any phone. The SMS a donor receives contains the hospital’s postcode, so they can find the exact building, or give the code to a rider, without a smartphone. Seeing where donors are missing. Each hospital sees how many reachable donors of each blood group it has in its postcode area, district, LGA and state, which shows where to hold the next blood drive. Privacy and cost: a donor’s building postcode is checked with NIPOST and then cut back to its area before it is stored, so their home is never kept. Search, reference data and Level 1 are free, and every paid Level 2–3 answer is cached so each building is paid for once. Levels 2–3 are built in and our access request is with NIPOST. BloodLink is built against NIPOST’s published API specification; while our developer access is being approved, the demo runs on NIPOST’s published sample buildings, and switching to the live API is a single configuration change.

Search APILookup Level 1Lookup Level 2-3

See the demoThe product

Interested in this one?

If you would pilot it, buy it, partner on it or invest in it, tell us and we will introduce you to the team within five working days. We do not publish their contact details, and we tell them each time somebody asks.

Register interest

Listed here means the solution was built on the Nigerian postcode and cleared our first check. It is not an endorsement by the Ministry or NIPOST, and nothing here has been tested by them.