ABHA at the desk. eRaktKosh from the working day.
RAKT links donors to ABHA at registration and files eRaktKosh returns from the bags, tests and issues your staff already enter — so national reporting stops being a second job.
Two national systems. One product that runs both.
State councils, hospital trusts and purchase committees ask whether your software handles ABHA and eRaktKosh. 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.
Registered on ABDM
RAKT Innovation Private Limited is on ABDM’s Health Facility Registry as a digital health facility — ID IN0710008026.
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 desk
- ABHA address, number or Aadhaar
- OTP to the donor's phone
- ABDM returns the verified profile
- Demographics fill the form
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
- Your working day bags, tests, issues
- Mapped to the eRaktKosh schema
- Validated before sending
- MOHFW API
- Reply on the same screen
Trigger Sent in one action, when you send it
The other way: eRaktKosh pulls public availability
- eRaktKosh
- Tested stock at your centre
Quick answers for purchase committees
Does RAKT support ABHA and eRaktKosh?
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.
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 and an eRaktKosh submit end to end on a centre like yours.
Put ABHA and eRaktKosh on your floor this quarter
Book a demo. We will show donor ABHA linkage and an eRaktKosh Collection Summary on a live centre workflow.