Blood bank software in India gets judged on one thing: whether it produces the registers a drug inspector asks for and the data e-RaktKosh expects, every day, without anyone remembering to do it. Donor record, master record per bag, issue register, cross-match, cold chain. The dashboards are optional. The registers are the licence.
Key takeaways
- Registers have to survive five years. Rule 122-P makes them a licence condition, and the Form 28-C licence itself runs five years.
- Five tests are mandatory on every unit before use: HIV I and II antibodies, HBsAg, HCV antibody, VDRL and malarial parasite. Results go on the label.
- The CDSCO advisory of 3 June 2022 says every licensed blood centre is required to register on e-RaktKosh, update stock daily, and send donor data and monthly reports. It is an advisory routed to State licensing authorities for follow-up, not a rule carrying its own penalty.
- A hospital storage centre is not a licensed blood centre. Schedule K entry 5B exempts it under 2,000 units a year, from a licensed source.
- Patient Square does not build blood bank software. Nothing here is a pitch for one.
Key facts
- Retention required for blood centre records and registers
- 5years
- Mandatory on every unit before use (Schedule F Part XII-B)
- 5tests
- Stock update expected on e-RaktKosh (CDSCO advisory, 03.06.2022)
- daily
Sources: CDSCO regulatory requirements for blood and its components; CDSCO e-RaktKosh advisory, 3 June 2022.
The rulebook writes your feature list, not the vendor
Most demos open with a donor app and a stock dashboard. Neither is what an inspector wants.
The operating rules sit in the Drugs and Cosmetics Rules, 1945, Rules 122-F through 122-P, with the detail in Schedule F Part XII-B. You apply in Form 27-C under Rule 122-F. If the State Drug Controller is satisfied after inspection, you get a licence in Form 28-C under Rule 122-G to collect, store, process and distribute whole human blood and its components, valid five years under Rule 122-H.
Rule 122-P is the part that should shape a shortlist. It makes the Schedule F registers a condition of holding the licence, requires them kept five years from the date of manufacture, and lets an inspector walk in with or without prior notice to read any of them. One condition belongs in the software as a hard block: no blood from a professional or paid donor. Donor category is a compliance field.
On vocabulary: government documents now say blood centre, the older Rules text still says blood bank, and vendors mostly say blood bank. Same licensed facility.
What has to exist in the record, and who comes looking
Every row below is a record Schedule F Part XII-B names, with what it must carry, who asks for it, and whether it also surfaces nationally.
| Record | What the rules require it to carry | Who asks to see it | Surfaces on e-RaktKosh? |
|---|---|---|---|
| Blood donor record | Serial number, date of bleeding, donor identity and signature, age, weight, haemoglobin, group, blood pressure, medical examination, bag number, voluntary or replacement, deferral records, Medical Officer’s signature | Drug inspector, with or without notice | Yes, donor data is named in the advisory |
| Master record for blood and components | Bag serial number, collection and expiry dates, volume, ABO and Rh group, all five test results, irregular antibodies, donor particulars, issue number, components prepared or discarded | Drug inspector | Yes, as the stock position updated daily |
| Issue register | Serial number, date and time of issue, bag serial, group, volume, recipient identity and group, unit, cross-matching report, indication for transfusion | Drug inspector; transfusion committee if accredited | Feeds the monthly report |
| Cross-match report to the patient | Must be issued to the patient together with the blood unit | The receiving ward, and the inspector if a unit is queried | No, it travels with the unit |
| Kit and reagent register | Name of kit or reagent, batch number, date of expiry, date of use | Drug inspector; NABH assessor | No, kept locally |
| Transfusion adverse-reaction records | Reactions recorded as they occur | Drug inspector; NABH assessor | No, kept locally |
| Cold-chain evidence | Whole blood at 2 to 6 °C, on a fridge with digital dial thermometer, recording thermograph, alarm and continuous power; component freezers at minus 30 to minus 40 °C and minus 75 to minus 80 °C | Drug inspector, by walking to the machine | No, kept locally |
All of it retained five years. The 2022 advisory names daily stock, donor data and monthly reports without mapping register by register, so the last column is the practical split, not a quotable clause.
Look at the donor row again. Deferral records are named in the rule, and they are where paper fails. Schedule F sets deferment periods across a long list: twelve months after surgery, six months after a tattoo or a prior transfusion, three months after treated malaria in an endemic area and three years in a non-endemic one. A donor deferred in March who walks back in June is a check the system should raise before the phlebotomist reaches for a bag, with the medical officer still making the call. Free-text remarks are not deferral logic.
e-RaktKosh changed the question in 2022
e-RaktKosh is the Ministry of Health and Family Welfare’s centralised blood centre system. The public side is familiar: search availability, find a centre, register as a donor, raise a thalassemia request.
The part that matters to a buyer sits behind the login. On 3 June 2022 the office of the Drugs Controller General of India issued an advisory, File No. Blood Bank/Misc/e-RaktKosh Advisory/2022-D, stating that all licensed blood centres are required to register on the portal to enter their blood stock availability and “update the same on a daily basis”, along with donor data and monthly reports. Copies went to every State and UT licensing authority and every CDSCO zonal office for follow-up.
Daily is the operative word. A district hospital centre that closes at 8pm and keys yesterday’s issues into the portal next morning is doing double entry forever, and it drifts from the register on exactly the days that matter. So the question to put to a vendor is narrow: does the system make my e-RaktKosh position a by-product of accessioning, testing and issuing, or does it print a report someone retypes?
We think that one question separates good blood centre software from adequate more reliably than any feature grid. Everything else can be worked around. Double entry can’t.
What an inspector actually asks for
An inspection is a trace, and you can rehearse it. Nobody asks to see your dashboard. Pick a bag serial number. Show the donor record behind it, with the medical examination and the deferral check. Show the master record with all five test results. Show the label carrying them, then the issue register entry with the cross-match and stated indication, then the reagent register for that day’s kit lots, then the temperature record for the fridge that held it.
If any link lives in a spreadsheet or a drawer, the trace stalls and someone loses an afternoon reconstructing it. Run it during the trial, not after go-live. The NABH documentation requirements guide makes the same point about hospital records generally: the system that survives an assessment is the one where evidence is a by-product of work.
Standalone system, HMS module, or e-RaktKosh alone
Running on e-RaktKosh alone is what plenty of small licensed centres actually do, day to day. Cheapest path, and reporting stays current by definition. Limits appear when you want your own component workflow, quality records, or a link to hospital billing.
The blood bank module in your HMS is the right call when blood is one service among many and volume is modest. One login, and the issue lands on the bill without re-keying. The usual failure is depth: modules handle ordering and issuing, then treat deferral, component preparation, reagent lots and adverse reactions as text fields. Same gap we described between a real LIMS and a thin lab tab in the lab management software guide, and the one in bundled stock modules in hospital inventory management.
A specialist blood centre system is built around the bag: accessioning, test results tied to the unit, component splitting with parent and child lineage, quarantine of untested units, cross-match and issue, cold-chain logging, e-RaktKosh submission. If you bleed donors and prepare components, this is normally the better buy, and lineage is the reason more than features. Once one bag becomes packed cells, plasma and platelets, each child unit inherits the donor and the test results and expires on its own schedule. Systems built to issue stock rarely model that. The HMS modules explainer maps the rest of the stack around it.
The storage centre case that changes the answer
Plenty of hospitals shopping for blood bank software actually run a blood storage centre. The rules treat those differently. Notification GSR 909(E) of 20 December 2001 inserted entry 5B into Schedule K, exempting storage centres run by a First Referral Unit, CHC, PHC or any hospital from holding an operating licence. The conditions: approval by the State or UT licensing authority after inspection, captive consumption under 2,000 units a year, blood procured only from a licensed government, Indian Red Cross Society or regional transfusion centre, and a two-year approval renewed three months before expiry.
If that’s you, half this article doesn’t apply. No bleeding, so no donor register and no deferral logic. You need receipt from your source centre, temperature evidence, cross-match, issue and expiry control. An HMS module usually covers it, and a specialist system is overbought. Working out which side of entry 5B you sit on is the cheapest decision on this page.
NABH, if accreditation is on the table
NABH runs a separate accreditation programme for blood banks and blood centres, distinct from its hospital programme, covering donor screening, collection, component preparation, testing, storage and distribution. It accredits the facility, not your vendor. No software is “NABH certified” for your centre. A vendor implying otherwise is selling you a category error. What good software does is make evidence producible: quality indicators, reagent lot traceability, adverse-reaction records, turnaround data.
Alongside NABH sits the National Blood Transfusion Council under DGHS, whose stated role is to formulate policy, strategy, standards and technical guidelines. It has published National Standards for Blood Centres and Blood Transfusion Services (2nd edition, July 2022) and a Transfusion Medicine Technical Manual (3rd edition, August 2023). Read those before the brochures.
What it costs, honestly
Blood centre software pricing in India is not publicly listed. Vendors gate it behind a call, and the number moves with annual collection, component preparation, apheresis and site count. We are not going to invent a range. What to insist on in the quote: the figure in rupees, ex-GST, with 18% GST stated separately; implementation and migration as line items; annual support and upgrade costs named in figures; and e-RaktKosh submission confirmed as included, not a chargeable add-on. Get that last one in writing.
The honest verdict, including where we don’t belong
Buy the specialist system if you hold a Form 28-C licence, bleed donors, prepare components and report daily. Component lineage, deferral logic and daily reporting are the three things a bundled module gets shallow on, and each sits on the licence side of the line. Keep the HMS module if you run a Schedule K storage centre, or if volume is small and issue against cross-match is most of the work. Run on e-RaktKosh alone if you’re a small licensed centre with no appetite for a second vendor.
Now our own position. Patient Square does not build blood bank software. No donor register, no component preparation, no cross-match, no e-RaktKosh submission. If an AI vendor tells you their documentation product covers transfusion services, ask to see a master record and an issue register inside it. Ours has neither, and a documentation tool rarely does.
What we build sits one step away, in the consult room. AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft — ready to review and sign about two minutes after the visit. Where that touches this workflow is narrow: the transfusion consult itself. A haematologist explaining why a thalassaemia child needs a shorter interval, a physician writing up the consent discussion and the stated reason for transfusion. That’s documentation, and documentation is our lane. Our security page covers how the data is handled to DPDP Act 2023 standards, and pricing starts at ₹1,599 per clinician per month on annual billing, ex-GST, about ₹1,887 once 18% GST is added.
If the notes around transfusion are what your clinicians finish at 9pm, explore the workflow and bring a real consult. For the centre itself, take the record table above to two specialist vendors and one HMS vendor, and make each of them trace a bag in front of you.
Sources: CDSCO regulatory requirements for blood and its components (Drugs and Cosmetics Rules 122-F to 122-P, Schedule F Part XII-B, Schedule K entry 5B); CDSCO e-RaktKosh advisory, 3 June 2022; DGHS Blood Transfusion Services; e-RaktKosh; NABH Blood Centres Accreditation Programme.