Skip to content
ABHA, eRaktKosh & ISBT 128

ABHA at the desk. eRaktKosh from the working day. ISBT 128 on the label.

RAKT links donors to ABHA at registration, files eRaktKosh returns from the bags your staff already enter, and encodes ISBT 128 data structures for labeling — as an ICCBBA registered software vendor.

What procurement asks first

National systems and the international label standard. One product.

Purchase committees ask whether your software handles ABHA, eRaktKosh and ISBT 128. RAKT does — from the same floor workflow your team already uses.

ABHA at registration

Verify or create an ABHA, pull demographics into the donor form, and keep one identity across every centre on your network.

eRaktKosh without re-typing

Build the monthly Collection Summary from live records, validate it, submit to MOHFW, and keep public stock current between returns.

ISBT 128 labeling

ICCBBA registered software vendor. ABO/Rh, product code, collection and expiry encoded as ISBT 128 data structures for the bag label.

Registered on ABDM

RAKT Innovation Private Limited is on ABDM’s Health Facility Registry as a digital health facility — ID IN0710008026.

ABHA / ABDM

Faster registration. Cleaner identity across your centres.

A verified health account at the counter means less typing, fewer duplicate donors, and donation history you can trust inside your own network.

Create or verify ABHA

Enrol with Aadhaar or mobile OTP, or verify an existing ABHA address, number or mobile against the ABDM gateway.

Donor-confirmed OTP

The donor enters the OTP on their phone. Linkage only completes when they confirm — the counter cannot silently attach an ID.

Scan & Share

HIP / bridge QR profiles arrive on the callback, get claimed at the desk, and link to a donor or a blood-component request.

Demographics auto-fill

Name, age, sex and address land from the verified profile. Staff confirm — they do not re-key a card at a busy queue.

One donor across your network

The same person at two of your centres resolves to one record, so donation interval and prior deferrals in your network are checked against what actually happened.

Built for camp pace

Less time per donor at the desk. That is the difference when the queue is forty people and the hall closes at noon.

From ABHA to a filled donor form

Donor at the deskABHA address,number or AadhaarOTP to thedonor's phoneABDM returns theverified profileDemographics fillthe form
  1. Donor at the desk
  2. ABHA address, number or Aadhaar
  3. OTP to the donor's phone
  4. ABDM returns the verified profile
  5. Demographics fill the form
Verified identity at the counter: the donor confirms with an OTP, ABDM returns the profile, and RAKT fills the registration form from that profile.
eRaktKosh

National reporting from the records you already keep.

Collections, TTI results and issues map to the eRaktKosh schema. You submit a clean return. Public stock stays current between months.

Monthly Collection Summary

OAuth to the MOHFW API, then a collection-summary payload for the month you choose — built from operational data, not re-keyed into the portal.

Validated before send

Blood group, component, donation type and related fields match the national vocabulary first, so problems surface before the API call.

Reply on the same screen

Acceptance or rejection comes back immediately on the Settings integration screen. Fix mapping, resubmit, move on.

Live tested stock

eRaktKosh polls your tested, non-reactive stock so public availability stays current between monthly returns.

Donor list in portal format

MIS export ready for the eRaktKosh upload path, with a preflight check for blank or invalid mandatory cells.

Reconcile before inspection

Compare what went out against your Donor and Issue Registers for any date range — find gaps yourself, not in an assessment.

From floor records to the national return

sent in one action, when you send itYour working daybags, tests, issuesMapped to theeRaktKosh schemaValidatedbefore sendingMOHFW APIReply onthe same screenTested stockeRaktKosheRaktKosh calls our endpoint for public availability
  1. Your working day bags, tests, issues
  2. Mapped to the eRaktKosh schema
  3. Validated before sending
  4. MOHFW API
  5. Reply on the same screen

Trigger Sent in one action, when you send it

The other way: eRaktKosh pulls public availability

  1. eRaktKosh
  2. Tested stock at your centre
Two legs, and the difference between them is who starts. The return goes out when somebody submits it, with validation first so a schema problem appears before sending rather than as a rejection afterwards. The stock leg is the other way round: eRaktKosh calls an endpoint at your centre, which is what keeps public availability current between returns without anyone filing anything.
ISBT 128

International labeling from the same bag record.

ISBT 128 is the ICCBBA standard for identifying donations and labeling medical products of human origin. RAKT is a registered software vendor with ICCBBA, and encodes the data structures the bag label needs from grouping and component records already on the floor.

ICCBBA registered software vendor

RAKT is registered with ICCBBA to integrate ISBT 128 into the product. That is 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 are generated from the same bag and component records staff already enter — not typed onto a separate labeling tool.

Labels from the working day

Print on Zebra-class printers at the centre or camp. The code on the label comes from the unit that was 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.

FAQ

Quick answers for purchase committees

Does RAKT support ABHA, eRaktKosh and ISBT 128?

Yes. ABHA runs at the registration desk — create, verify, OTP confirmation, Scan & Share, and demographics into the donor form. eRaktKosh runs from the working day: Collection Summary to MOHFW, validation before send, tested-stock availability, and donor-list export in the portal format. ISBT 128 data structures for ABO/Rh, product code, collection and expiry are encoded from the same bag and component records.

Is RAKT an ICCBBA registered software vendor?

Yes. RAKT is registered with ICCBBA as a software vendor for the ISBT 128 Standard. That authorises ISBT 128 data structures in the software. It is not a product certification or an endorsement by ICCBBA. Ask support@rakt.in if you need confirmation for a procurement questionnaire.

Is RAKT registered under ABDM?

Yes. RAKT Innovation Private Limited is registered on ABDM’s Health Facility Registry as a digital health facility, ID IN0710008026. ABHA flows at the desk run against ABDM’s live APIs.

Will eRaktKosh still need parallel data entry?

No. The return is built from the bags, tests and issues your staff already record. Validation catches schema problems before send, and the MOHFW reply appears on the same screen.

Can we see this on a demo with our own return?

Yes. Bring last month’s format and the instruments you use. We walk an ABHA registration, an eRaktKosh submit and ISBT 128 labeling on a centre like yours.

Put ABHA, eRaktKosh and ISBT 128 on your floor this quarter

Book a demo. We will show donor ABHA linkage, an eRaktKosh Collection Summary and ISBT 128 labeling on a live centre workflow.