Everything a blood centre runs on
From Bag Entry through TTI Screening, component preparation and Shift To Tested Stock, to Blood Request, Crossmatch Compatibility and Issue — with the registers and eRaktKosh reporting written as you go.
Blood centres run on RAKT
States covered
Donors on record
Components prepared
The eleven parts, grouped by what they are for
A centre rarely needs all of it on day one. These are the three questions the parts answer.
Running the floor
The screens your staff are in all day.
Cloud-Based Software
Hosted, continuously updated and reachable from every centre you run.
Lab Automation
Analyser results captured against the unit, with release rules enforced by the system.
Camps & RAKT Pass
Plan camps, register donors on a tablet and reconcile collections the same day.
RAKT AI
Assistance that removes data entry while decisions and accountability stay with staff.
Ready when the inspector arrives
Registers, indicators and returns, written from the day’s work rather than reconstructed later.
eRaktKosh Integration
Scheduled submission with validation up front and acknowledgements retained.
Compliance & Quality
NABH indicators and statutory registers derived from live operational data.
Reports & MIS
Stock, collection, issue, discard and utilisation reporting, ready to export.
Staff Activity Tracking
Every action attributable to a person, with a tamper-evident change history.
Identity, access and integration
Who the donor is, who touched the record, and what else the centre has to talk to.
ABDM & ABHA
One health identity per donor, with consent recorded and deferrals that follow them.
ISBT 128 Labeling
ICCBBA registered software vendor. ABO/Rh, product code and expiry from the bag record.
Security & Passkeys
Phishing-resistant passkey sign-in, role-based access and encryption throughout.
API & Integrations
Connect the blood bank to your HIS, instruments, billing and messaging providers.
How the parts fit together
The eleven parts above are not eleven products. They are one path, and it is the path of a single bag of blood: a donor is registered and screened against their own deferral history, a bag is entered against them, the unit is grouped and tested, what comes back from the analyser decides whether it can move to tested stock, tested stock is separated into components, and a component is crossmatched and issued to a named patient. Every register a licensed centre has to produce is a view of that same path, which is why they can be generated rather than written.
The reason it matters that this is one path and not eleven modules is what happens at the gates. A unit that has not been tested cannot be issued, because the issue screen has no way to reach it — not because a policy says so. A reactive TTI result quarantines the unit and its components together. A donor deferred at one centre is deferred at every centre under the same licence. Software that stores these facts without enforcing them will demonstrate well and fail an assessment, and the difference is invisible in a feature list.
Almost no centre needs all of it in the first month, and it is worth being plain about the order. Bag Entry through Issue, with the statutory registers, is what replaces the paper and is where the whole benefit starts — a centre can run on that alone. Analyser integration is the next thing worth adding, because transcription is the one manual step whose errors are dangerous rather than inconvenient. eRaktKosh reporting follows from records that by then already exist. ABHA, the API, camps and RAKT AI are worth adding when there is a specific reason to, and not before: a module nobody has a use for is a screen staff learn to click past.
What none of the eleven do is make a clinical or a regulatory decision. A deferral, a discard, the release of a unit — those belong to a person who is accountable for them. The system’s job is to make sure the decision is recorded, attributed to whoever made it, and difficult to bypass quietly.
Not sure which parts you need?
Walk us through your day — who does Bag Entry, where TTI results come from, which registers your inspector asks for — and we will tell you honestly which parts of RAKT would change it and which would not.