ISBT 128 labels from the bag you already recorded
RAKT is an ICCBBA registered software vendor for the ISBT 128 Standard. ABO/Rh, product code, collection and expiry are encoded from grouping and component records — so the code on the label matches the unit on the floor.
Registered software vendor
ABO / Rh on the label
Product code from component
Centre or camp label
What ISBT 128 support covers
Vendor registration for the standard, and the data structures the bag label needs.
ICCBBA registered software vendor
Registered with ICCBBA to integrate ISBT 128 into the product. Vendor licensing for the standard — not a product endorsement by ICCBBA.
ABO / Rh (Data Structure 002)
Grouping results encode to the ISBT 128 ABO/Rh structure used on the bag label, including phenotype where recorded.
Product code (Data Structure 003)
Component type and donation type map to the ISBT 128 product-code structure so the label matches what was prepared.
Collection and expiry
Collection and expiry date/time structures come from the same bag and component records staff already enter.
Print at the centre or camp
Zebra-class label printers at the bench or on RAKT Pass at a camp — the code is generated from the unit just grouped or prepared.
Checkable for procurement
Ask us for current ICCBBA confirmation for a tender file. Licensed vendors also appear in ICCBBA’s vendor lookup once the profile is live.
From the bag record to the barcode
Group and prepare as usual
Staff record forward/reverse grouping and prepare components on the screens they already use. Nothing is typed into a parallel labeling worksheet.
Encode the ISBT 128 structures
ABO/Rh (Data Structure 002), product code (Data Structure 003), collection and expiry are generated from those records.
Print the label
Zebra-class printers at the centre, or on RAKT Pass at camp, so the bag is identified before it leaves the desk.
The register and the label agree
The code on the bag came from the same unit the Donor, Grouping and Component registers already hold — not from a second system.
What the sequence looks like
- Bag grouped & component prepared
- DS 002 ABO/Rh from grouping
- DS 003 product code from component
- Collection & expiry structures
- Label prints at centre or camp
Registered vendor status, stated precisely
ICCBBA registration authorises software vendors to integrate ISBT 128 data structures. It is not a product certification, and it does not mean ICCBBA endorses RAKT. Centres that assign Donation Identification Numbers still need their own ICCBBA facility licence where that applies.
- We say “ICCBBA registered software vendor”, never “ICCBBA certified”
- ISBT 128 structures are generated from live bag and component records
- Facility FIN licensing for the blood centre remains the centre’s obligation
- Confirmation for a procurement questionnaire is available on request
The label has to match the unit, not a second system
ISBT 128 is the international information standard, managed by ICCBBA, for identifying donations and labeling medical products of human origin — including blood components. A software vendor that encodes those data structures needs an ICCBBA software-vendor registration; a blood centre that assigns Donation Identification Numbers needs its own facility licence. The two are different obligations, and conflating them is how tenders end up with the wrong question on the questionnaire.
The product claim that matters on the floor is narrower than a logo. When grouping is recorded, the ABO/Rh structure (Data Structure 002) has to encode from that result. When a component is prepared, the product-code structure (Data Structure 003) has to reflect the component and donation type that were actually made. Collection and expiry structures have to come from the same bag record, not from a parallel labeling tool somebody re-keys into. If the label and the register disagree, the barcode is not helping you — it is inventing a second truth.
RAKT is registered with ICCBBA as a software vendor for ISBT 128. That authorises the data structures in the product. It is not a product certification and it is not an endorsement by ICCBBA. Ask for current confirmation when a purchase committee wants it in writing; do not accept “ISBT 128 certified” wording from any vendor, including us.
Questions about isbt 128 labeling
What is ISBT 128 and why do blood banks care?
ISBT 128 is the ICCBBA standard for donation identification and product labeling for medical products of human origin, including blood. Centres that need internationally readable labels, or that work with partners who expect those data structures, need software that can encode them from the operational record rather than from a separate labeling worksheet.
Is RAKT an ICCBBA registered software vendor?
Yes. RAKT is registered with ICCBBA as a software vendor for the ISBT 128 Standard. That means we are authorised to integrate ISBT 128 data structures into the software. It is not a product endorsement by ICCBBA. Ask support@rakt.in if you need confirmation for a procurement questionnaire.
Does the blood centre still need its own ICCBBA registration?
Often yes, when the centre assigns Donation Identification Numbers or otherwise uses ISBT 128 as a licensed facility. Software-vendor registration covers the vendor’s right to put the standard in the product; facility licensing covers the centre’s right to apply identifiers. They are separate. We will say so on a demo rather than imply the software licence covers the centre.
Which ISBT 128 data structures does RAKT encode?
ABO/Rh (Data Structure 002) from grouping, product code (Data Structure 003) from component type and donation type, plus collection and expiry date/time structures from the bag and component records. Labels print to Zebra-class printers at the centre or on RAKT Pass at camp.
More of what RAKT does
See this running on your own floor
Tell us how your centre works today and we will show you the parts that would change.