Unit-level traceability from donor to transfusion, TTI screening tied to each unit, and e-RaktKosh data straight from the register you already run on.
Most hospital modules improve efficiency. A blood bank register is different: human blood is defined as a drug under the Drugs and Cosmetics Act, 1940, and the records around it are what a Drugs Inspector examines during inspection. A missing screening result, an untraceable component, or a break in the cold chain isn't an operational inconvenience, it's a licence problem.
Blood banks are regulated under the Drugs and Cosmetics Act, 1940 and the Drugs and Cosmetics Rules, 1945. The operative provisions sit at Rules 122-G to 122-O, with the technical standards for accommodation, personnel and equipment set out in Schedule F, Part XII-B (and Part XII-C for blood components). Application is made in Form 27-C to the State Licensing Authority; the licence is granted in Form 28-C. The Drugs Controller General (India) acts as Central Licence Approving Authority for notified products including blood and blood components.
Schedule F, Part XII-B specifies a minimum area of 100 square metres for blood bank operations, plus an additional 50 square metres where component preparation is carried out. Technical staff qualifications, equipment and standard operating procedures are prescribed in the same Part.
| Record | Why it matters |
|---|---|
| Donor registration and deferral history | A permanently deferred donor must be blocked at registration, not caught after collection |
| Unit number, issued at collection | The anchor for every downstream record; components, tests and transfusion all reference it |
| TTI screening results per unit | HIV, HBV, HCV, syphilis, malaria, traceable to the specific unit, not a batch note |
| Component separation lineage | Packed cells, plasma, platelets each traceable back to the parent donation |
| Cold chain / storage temperature | Component-specific storage requirements; excursions must be logged, not silently corrected |
| Cross-match and issue record | Links a specific unit to a specific patient, which is what a look-back investigation follows |
| Expiry and discard log | Discarded units need a documented reason, whether expiry, TTI-reactive, or breakage |
| e-RaktKosh reporting data | Stock, donation and issue figures reported to the national portal |
This is the requirement that separates a real blood bank system from an inventory spreadsheet. Given a donor, the system must identify every component made from their donations and every patient who received one. Given a patient, it must identify every unit transfused and trace each back to its donor and screening record. That bidirectional look-back is the entire point of unit-level record keeping, and it's what fails when component separation is recorded as a stock adjustment rather than as a parent-child relationship.
Reporting to the national e-RaktKosh portal has been made compulsory for blood centres. The failure mode in most hospitals isn't refusing to report, it's reporting via a separate manual data-entry process, which drifts out of sync with the actual register and creates two versions of the truth. Stock, donation and issue data should come from the same records the blood bank runs on daily. The regulatory background is covered in more depth in our note on e-RaktKosh becoming compulsory for blood banks.
Donor screening happens before a needle goes anywhere near a donor, and the system's job is to make an unsafe collection difficult rather than to record it afterwards. Deferral comes in two forms and they behave very differently.
Temporary deferral has an end date, recent tattoo or piercing, recent illness or antibiotic course, low haemoglobin, recent travel to a malaria-endemic area, pregnancy or recent childbirth, or simply not enough time since the last donation. The system needs to store the reason and the date the donor becomes eligible again, and it should be able to tell a donor at the door "you are eligible from the 14th" rather than sending them away with a vague answer.
Permanent deferral has no end date, and this is where a register that lives only on paper genuinely endangers patients. A donor deferred permanently at one visit must be blocked at every subsequent visit, including when they present at a camp rather than the main centre, and including when they give a slightly different spelling of their name. Matching on name alone is not sufficient; a stable donor identifier plus date of birth and contact number gives a workable match, and near-matches should prompt a human check rather than silently creating a second donor record.
Inter-donation interval enforcement is the everyday version of the same control. Whole blood donation intervals are defined in the rules, and a donor presenting too early should be stopped by the system at registration, not discovered afterwards when someone reconciles the register.
National blood policy is built around promoting voluntary non-remunerated repeat donation, and a blood bank's records are where that intent either shows up or does not. Practically, a hospital blood bank runs three streams: voluntary donors at the centre, camp collections, and replacement donors brought by a patient's family. Each has different record-keeping friction.
Camps are the hardest. Collection happens away from the centre, often with intermittent connectivity, and the units arrive with paperwork that then has to be reconciled. A system that only works online forces camps back onto paper forms and creates a transcription step, which is exactly where unit numbers get mistyped and donor records get duplicated. Offline capture that syncs on return is not a luxury here; it is the difference between a camp's records being reliable and being reconstructed. The same tier-2/3 connectivity argument covered in our offline-first design note applies with unusual force to camp collections.
Repeat-donor tracking is the other thing a good donor register buys you. Knowing which donors are eligible again this month, by blood group, turns an emergency O-negative shortage from a public appeal into a targeted call list.
Different components have different storage requirements and different shelf lives, and a single "blood fridge temperature" reading does not cover them. Whole blood and packed red cells are refrigerated; plasma products are frozen; platelets are held near room temperature with continuous agitation, and have a notably short shelf life. A platelet agitator failing overnight is a discard event for everything on it.
What the record has to show is continuity, not spot checks. Two-hourly manual logs are the traditional approach and they have an obvious weakness: nobody is writing at 3 a.m., so the log gets filled in later from memory, and an excursion that happened between readings leaves no trace. Continuous logging with alarm thresholds, and a documented action trail whenever an alarm fires, is what an inspector can actually rely on.
| Cold chain record | Why it exists |
|---|---|
| Continuous storage temperature per unit of equipment | Demonstrates the storage condition held, not just that it was checked twice |
| Excursion alarms with time, duration and peak | An excursion is not automatically a discard, but an undocumented one is |
| Action taken on each excursion, and by whom | Shows the alarm reached a person who decided something |
| Transport container validation for issued units | The chain does not end at the fridge door |
| Equipment calibration and maintenance history | An uncalibrated probe makes every reading above it meaningless |
Blood storage equipment sits in the same calibration and maintenance regime as everything else clinical, which is why it belongs in the hospital's biomedical equipment register rather than being tracked separately by the blood bank alone.
The issue record is the last link in the traceability chain and the one that matters most in an investigation. It has to bind a specific unit to a specific patient, with the compatibility testing performed, the person who authorised release, the person who collected it, and the time. Where a unit is returned unused, the return time and the storage condition during its absence determine whether it can go back into inventory or must be discarded, a decision that needs recording either way.
Transfusion reactions close the loop back to the donor. A suspected reaction triggers investigation of the implicated unit, which means retrieving its donation record, its screening results, its component siblings from the same parent donation, and every other patient who received one of those siblings. If component separation was recorded as a stock movement rather than as a parent-child link, that investigation cannot be run from the system at all, it becomes a manual reconstruction from paper under time pressure, which is precisely the situation unit-level records exist to prevent.
Haemovigilance reporting sits on top of this. A reaction investigated and closed internally, with no report generated, leaves the hospital's own record complete but contributes nothing upward.
Blood inventory behaves unlike any other hospital stock. It cannot be ordered from a supplier on demand, it expires on a fixed clock from the moment of collection, and shortages are group-specific rather than general. A blood bank can be simultaneously oversupplied in one group and critically short in another, and a headline "units in stock" figure hides exactly that.
Inspection under the Drugs and Cosmetics Rules focuses on records, premises, equipment and personnel against the Schedule F Part XII-B conditions. The record side, which is where software either helps or hurts:
That last one catches hospitals out regularly. A change in the blood bank medical officer or technical supervisor has to be reported to the Licensing Authority, and a licence operating with unreported staff changes is out of compliance regardless of how good the clinical practice is.
Human blood is treated as a drug under the Drugs and Cosmetics Act, 1940, so a blood bank operates under a licence issued by the State Licensing Authority, with the Drugs Controller General (India) acting as Central Licence Approving Authority for notified products. Application is made in Form 27-C and the licence is granted in Form 28-C, subject to the conditions in Schedule F, Part XII-B of the Drugs and Cosmetics Rules, 1945.
Commonly cited as five years from issuance, though hospitals should verify the term printed on their own licence and their State's current renewal practice rather than assuming, since renewal requires fresh inspection.
e-RaktKosh reporting has been made compulsory for blood centres, covering stock, donation and issue data reported to the national portal. A blood bank system should generate the required data directly rather than requiring separate manual entry into the portal.
Transfusion-transmissible infection screening under the Drugs and Cosmetics Rules includes HIV, hepatitis B, hepatitis C, syphilis and malaria. HIV 1 and 2 antibody testing was made a mandatory pre-transfusion requirement by notification in 1989. Every unit must have its screening results traceable to that specific unit.
Schedule F, Part XII-B specifies an area of 100 square metres for blood bank operations, with an additional 50 square metres where blood component preparation is carried out.
Yes. A whole blood unit separated into packed cells, plasma and platelets should retain a traceable link from each component back to the original donation and donor, so a look-back investigation can run in either direction.
Tell us your licence status and whether you separate components in-house.
Talk to OneCity