HomeServicesPortfolioTeamContact
Back to Selected Works
Representative Project
HealthTech · Donor Management

Blood Bank & Donor Management Platform

A digital ecosystem that connects donors, blood banks, and hospitals — replacing fragmented paper-based processes with intelligent matching, real-time inventory, and structured emergency workflows.

Services
Product Strategy · UX/UI Design · Full-Stack Development · Database Architecture
Technology
React · Node.js · PostgreSQL · REST APIs · Real-Time Notifications
Platform
Web Application
Classification
Representative — demonstrates capability
02

The Challenge

Blood bank operations in many regions still depend on manual record-keeping, phone calls, and paper registers. When a hospital needs a specific blood type urgently, the process often involves calling multiple blood banks, checking availability through verbal confirmation, and coordinating transportation — all under time pressure where delays have direct medical consequences.

Donor management is equally fragmented. Donor records are maintained in ledgers or basic spreadsheets. There is no systematic way to track donation eligibility windows, notify donors when their blood type is needed, or maintain communication that keeps donors engaged between donations. The result is a system where supply and demand are connected by human memory and phone calls rather than data infrastructure.

This representative project explores how a unified digital platform could address these operational gaps — connecting the donor lifecycle, blood bank inventory management, and hospital request workflows into a coherent system where information flows automatically rather than through manual coordination.

Operational Pain Points

  • No centralized donor registry with eligibility tracking
  • Blood inventory managed through paper ledgers or disconnected spreadsheets
  • Emergency requests handled through phone calls to individual banks
  • No automated matching between blood requests and available inventory
  • Donor communication limited to in-person interaction during donations
  • No visibility into system-wide inventory levels across multiple banks
  • Expiration tracking and wastage monitoring done manually
  • No structured reporting for regulatory compliance
03

The Product

The platform is structured around the complete blood supply chain — from donor registration through hospital fulfillment. Rather than building a feature list, we designed the system around the natural workflow: a donor registers and becomes available, a blood bank collects and manages inventory, a hospital submits a request, the system matches inventory to need, notifications coordinate the fulfillment, and the cycle continues.

Donor
Blood Bank
Request
Matching
Notification
Fulfillment

Donor Management — Registration with blood group, medical history screening questions, contact preferences, and donation history. The system tracks the mandatory waiting period between donations and marks donors as eligible or ineligible automatically. Donors receive notifications when their blood type is needed in their area.

Blood Bank Operations — Inventory management with unit tracking, blood group counts, collection dates, expiration monitoring, and cross-match records. The dashboard surfaces units approaching expiration to minimize wastage and provides real-time inventory status across all managed blood groups and components.

Request & Matching — Hospitals submit blood requests specifying type, quantity, urgency level, and required delivery window. The system searches available inventory across participating blood banks, prioritizing by proximity, unit freshness, and urgency tier. Emergency requests trigger immediate notifications to relevant banks and eligible donors.

Admin & Reporting — Role-based dashboards for blood bank administrators, hospital coordinators, and system supervisors. Reporting covers donation volume, request fulfillment rates, inventory turnover, wastage tracking, and donor engagement metrics — structured for both operational use and regulatory compliance.

04

Our Role

Product Strategy

Workflow mapping across donor, blood bank, and hospital user types. Feature prioritization for phased rollout.

UX/UI Design

Role-specific interfaces for donors, bank staff, hospital coordinators, and system administrators.

Frontend Development

Responsive web application with real-time inventory dashboards and request management interfaces.

Backend Engineering

API layer managing donor records, inventory state, request matching logic, and notification dispatch.

Database Architecture

Relational schema modeling donor profiles, blood units, requests, and the relationships between entities.

Notification System

Multi-channel notification delivery for emergency requests, donor eligibility, and inventory alerts.

This is a representative project that demonstrates Prisma Akatsuki's capabilities in healthcare workflow systems. It is not presented as a completed client engagement.
05

Key Product
Decisions

01

Role-Based Access Architecture

The system serves four distinct user types — donors, blood bank staff, hospital coordinators, and administrators — each with fundamentally different workflows and data access needs. Rather than building four separate applications, we designed a unified platform with role-based views that show only the information and actions relevant to each user type. A blood bank technician sees inventory management and collection forms. A hospital coordinator sees request submission and fulfillment tracking. The admin sees cross-system analytics and user management. The underlying data model is shared, but the interface layer adapts completely to the role.

02

Automated Eligibility Tracking

Donor eligibility is not a simple yes/no flag — it depends on the time since last donation, the type of donation (whole blood vs. platelets have different waiting periods), recent medical events, and travel history. We built an eligibility engine that evaluates these factors automatically and transitions donor status on schedule. This eliminates a significant source of manual error and ensures that no ineligible donor is contacted for a donation, which has both safety and trust implications.

03

Urgency-Tiered Request Processing

Blood requests vary enormously in urgency — a scheduled surgery next week is fundamentally different from a trauma case that needs blood within the hour. We implemented a three-tier urgency system that changes how requests are processed. Routine requests follow standard matching and confirmation workflows. Urgent requests trigger simultaneous notifications to multiple banks. Emergency requests bypass the standard queue entirely, broadcasting to all available banks and eligible donors within a configurable radius.

04

Expiration-Aware Inventory

Blood products have strict shelf lives — red blood cells expire in roughly 42 days, platelets in 5 days. The inventory system tracks collection date for every unit and surfaces approaching expirations prominently in the dashboard. When a blood bank has units nearing expiration, the system can proactively search for pending requests that could use those units, reducing wastage while ensuring patient safety standards are never compromised.

05

Data Model for Traceability

Healthcare systems require complete traceability — the ability to track any blood unit from donor through processing, storage, and eventual transfusion or disposal. The database schema was designed around this requirement from the start, with every state change recorded as an immutable event. This creates a complete audit trail that supports regulatory compliance, quality assurance investigations, and operational reporting without requiring data reconstruction from fragmented records.

06

The Experience

Donor Dashboard
Profile, eligibility status, donation history
Inventory Management
Blood group counts, expiration alerts, unit tracking
Request & Matching Interface
Request submission, inventory search, fulfillment coordination
Admin Analytics
Donation volume, fulfillment rates, wastage metrics
Emergency Request Flow
Broadcast, matching, confirmation, dispatch

Conceptual interface representations for a representative project.

07

Technology
in Context

React

Component-based frontend providing role-specific dashboard views, real-time inventory displays, and responsive form workflows for donor registration and request submission.

Node.js

API server handling request processing, matching logic, notification dispatch, eligibility calculations, and the business rules that govern blood bank operations.

PostgreSQL

Relational database with schema designed for healthcare traceability — immutable event logging, temporal eligibility tracking, and inventory state management with full audit capability.

Real-Time Notifications

WebSocket and push notification infrastructure for emergency request broadcasting, donor alerts, expiration warnings, and fulfillment status updates.

Role-Based Security

Authentication and authorization layer with granular permissions ensuring each user type accesses only appropriate data and operations, with session management and audit logging.

Reporting Engine

Automated report generation for operational metrics and regulatory compliance, with exportable formats and configurable date ranges across all system entities.

08

Outcome

Unified Operational System

Replaced fragmented paper-and-phone workflows with a single platform connecting donors, blood banks, and hospitals through structured data flows.

Automated Donor Lifecycle

Built eligibility tracking that manages donation windows, medical screening, and donor communication without manual record-keeping.

Intelligent Request Matching

Created a matching engine that connects blood requests to available inventory based on type, location, urgency, and unit freshness.

Wastage Visibility

Implemented expiration-aware inventory that surfaces at-risk units and proactively suggests fulfillment opportunities to reduce product waste.

Emergency Response Workflow

Designed tiered urgency processing that accelerates coordination for time-critical blood needs without disrupting routine operations.

Compliance-Ready Traceability

Established a complete audit trail for every blood unit from collection through disposition, supporting regulatory requirements.

This is a representative project. No quantitative metrics are claimed as verified client results.

09

What Made This
Project Interesting

The most compelling aspect of this project was designing around urgency as a first-class system concept. In most applications, all operations have roughly equal priority — a user action triggers a process, and it completes when it completes. In a blood bank system, the difference between a routine request and an emergency request is not just speed — it changes the entire interaction model, notification strategy, and matching logic.

In healthcare systems, the data model is not an implementation detail — it is the operational policy expressed in structure.

The data modeling challenge was equally instructive. Blood bank operations have a deceptive surface simplicity — donors donate blood, banks store it, hospitals use it. But beneath that simplicity is a web of temporal constraints (eligibility windows, expiration dates, hold periods), classification complexity (blood types, Rh factors, components like plasma and platelets), and traceability requirements that demand every state transition be recorded immutably.

The hardest design problem was not the emergency workflow or the matching algorithm — it was the daily dashboard view for blood bank staff. These users interact with the system all day, every day. If the dashboard surfaces too much information, critical items get lost in noise. If it surfaces too little, staff miss expiration warnings or pending requests. Finding the right information density required genuine observation of how blood bank operations work in practice, not assumptions about what information "should" be important.

Have a workflow that
needs a system?

Tell us about the operational challenge. We will assess the complexity and propose an approach within 48 hours.