Blood Connect: Hospital Blood Request System
Doctors raise blood requests, the blood centre answers from stock, and a bot recruits donors for the shortfall. One loop, replacing paper forms and phone calls.
The problem
When a hospital needs blood, three disconnected things happen: a paper request form, a phone call to the blood centre, and, when the shelf is empty, a message forwarded around asking strangers to show up. No shared state, no record of what happened, and no one tells the doctor how it ended. In a medical-college hospital, that runs many times a day.
Who it’s for
Four roles on four surfaces: doctors raising requests, blood-centre staff deciding them, volunteers watching live demand per blood group, and administrators managing accounts.
How it works
A doctor submits a request and the patient details freeze at that moment, so a later edit never rewrites what the centre was told. The centre issues bags oldest-expiry-first, and any shortfall becomes donor demand. A bot then recruits eligible donors in waves, nearest locality first, and closes the demand once the outcome is recorded. Everyone learns how it ended, including when it ends badly.
Decisions worth naming
- Clinical conservatism on purpose. Issuing from stock is exact-group-match only. Substituting a compatible group stays a decision a person makes.
- Administration is a separate deployment, so a compromised admin account reaches no clinical action.