ERP-style platform for blood bank operations

Context

• Operational teams needed speed at collection and processing sites while regulators expected demonstrable traceability and separation of duties.
• Off-the-shelf products covered either clinical notes or generic inventory poorly suited to donation and lab handling rules.

Problem

• Data sat across tools that did not share a single operational timeline, making reconciliation slow and audit preparation manual.
• Exception paths (holds, quarantine, redirects) were common but unsupported in standard product configuration.

Approach

• Mapped the full lifecycle as explicit states and transitions with named actors—not only the default happy path.
• Co-designed permissions with how shifts and sites were actually staffed, avoiding generic role templates.
• Released in vertical slices into live operations with monitored data quality and rollback paths.

System / architecture

• Governed domain model shared by operational UI and integrations; APIs for lab and partner systems where required.
• Immutable audit events for critical transitions; structured reporting for compliance review.

Outcome

• One internal system became the operational source of truth; less spreadsheet bridging between departments.
• Interfaces prioritised clarity under time pressure, reducing misreads at the point of action.

Representative engagement pattern; organisation and metrics are not named publicly. Specifics generalised where confidentiality applies.