Case Studies/HemaFlow, NMB-HLabSys
Software Engineering·Delivered

How a Gqeberha haematology lab traded paper charts for a system built around its own workflow

A regulated clinical lab needed its exact workflow reflected in software, not bent to fit an off-the-shelf tool.

nmb-hlabsys.internal/requests
REQUEST QUEUE
REQ-2231Verified
Full blood count
REQ-2232In progress
Coagulation panel
REQ-2233Received
Blood smear
AUDIT TRAIL · REQ-2231
08:12Request received
Reception
08:26Assigned to bench
Lab lead
09:41Result entered
Technician
09:58Verified and released
Lab lead
01

Understand

A haematology laboratory at Nelson Mandela Bay Hospital was running test requests, tracking, and result entry entirely on paper. Every handoff between technicians was a physical form. Nothing was searchable, nothing was auditable, and a lost or misfiled request meant a lost or delayed result for a patient.

02

Define

The problem was not "we need software." It was: which parts of the lab's exact workflow (request creation, tracking, result entry, reporting) needed to become digital and traceable, without forcing a haematology technician to work around a generic system that didn't match how the lab actually operated.

03

Solve

Off-the-shelf lab management software assumes a generic workflow. This lab's process, and the compliance and audit requirements around it, were specific enough that bespoke software was the right call: something built to the lab's conventions, not the other way around.

04

Build

What was actually built, in service of the problem above, not a feature list for its own sake.

  • Lab test request management system on ASP.NET Core MVC
  • Lab technician subsystem with role-based access
  • Test request creation, tracking, and result entry
  • Reporting and audit trail for clinical compliance
  • Administrator and technician dashboards
05

IMPROVE

The lab now runs on a system tailored to its own clinical workflow: requests are tracked, results are auditable, and nothing depends on a paper trail. Operational software built to fit the domain, not the domain forced to fit the software.