Every unit, accounted for.
Blood centre software that follows every unit from the donor's vein to the patient's bedside, and refuses the wrong move along the way.
One bag. Seven hands. Keep scrolling.
This is the life of a single donation. Watch what the software checks at each step, and how the record grows behind it.
-
Donor
Thumbprint, questionnaire, consent, haemoglobin and vitals. A medical officer's PIN signs the decision.
Refuses: collection from anyone not declared fit.
-
Collection
A donation number is allocated once and never reused. It follows this blood everywhere from here on.
Refuses: a bag from an expired lot.
-
Laboratory
Forward and reverse grouping, five mandatory infection markers, and a second person who verifies with their own PIN.
Refuses: progress past a grouping discrepancy, or a reactive marker not repeated in duplicate.
-
Components
One bag becomes red cells, plasma and platelets. Each keeps the donation number and gets its own expiry.
Refuses: release of a component that fails the rejection check.
-
Inventory
A medical officer releases it to stock. Its fridge, slot and temperature are on record from then on.
Refuses: release before results are verified. An excursion puts units on hold.
-
Cross-match and issue
A patient sample, a cross-match and a timed reservation. Then the bag is scanned against the requisition.
Refuses: the wrong patient, an incompatible group, unmet special needs, expired or held bags.
-
Bedside
Wristband and bag are scanned together. Vitals go on record at start, 15 minutes and end, along with any reaction.
Refuses: starting a transfusion until wristband and bag both match.
Now try to issue the wrong bag.
Patient DEMO-1042 is group A+, confirmed, and needs irradiated red cells. Only one of these bags is safe. Pick one to scan it.
Waiting for a bag
Pick a bag to scan it.
A synthetic example. The refusal wording comes from the issue desk in the software.
Three more things to try breaking.
When a fridge goes out of range, its units go on hold.
Fridge BBR-03 is holding at safe temperature. Its range is 2–6 °C.
Change one word and the record gives you away.
Each entry's hash includes the one before it, so a change breaks everything that follows. Edit the highlighted entry and watch.
Checking the chain.
- TechnicianBag received in the laboratory
- Second technicianResults verified with own PIN
- Medical officerReleased to stock
- Issue deskIssued to patient DEMO-1042
A donation camp with no signal keeps working.
You're at a camp with no network. Register a few donors, then reconnect.
Camp laptop
10 reserved numbers left
Blood centre
0 records received
Built to be inspected.
Registers and returns come out of daily work, not a retyping exercise. Requirements are traced to the Drugs & Cosmetics Rules (Schedule F, Part XII-B), NABH standards, NACO/NBTC guidance and the Haemovigilance Programme of India.
- 0.00%
- failed requests at 240 virtual users
- 46 ms
- 95th-percentile page response, same run
- 7.3 s
- back online after a database crash, no data lost
- 4 s
- to restore to the moment before a bulk delete
Pre-validation rehearsal, 21 October 2026, on one developer laptop with one app instance and synthetic data. These aren't production results. Each site repeats the performance qualification on its own hardware.
Registers and returns
- Eight statutory registers, printable and exportable
- Signed by a medical officer or QA officer; later changes are detected
- 15 quality indicators, calculated automatically
- EQAS, reagent lots and equipment QC on record
- NACO/SBTC return, e-RaktKosh files, HvPI export
Security and audit
- Named accounts, password policy, lockout
- A PIN signature on each step, and an idle lock
- Permissions set by role; superadmins can't do clinical work
- Append-only audit trail with hash-chain tamper detection
- Rule changes versioned, with reason and approver
On your own servers
- Docker deployment inside your hospital network
- PostgreSQL primary and standby, encrypted backups
- TLS on every connection
- Donor portal kept apart; the internal system only calls out
- No data sent to external AI or analytics services
Donation types and blood products
- Whole blood, platelet apheresis, granulocytapheresis, PBSC collection and therapeutic phlebotomy, each with its own workflow
- WB, PRBC, FFP, RDP, SDP, cryoprecipitate, cryo-poor plasma, granulocytes and PBSC, each with its own storage and expiry rules
- Irradiation, leukoreduction, washing, paediatric aliquots and RDP pooling
- English and Malayalam throughout
What it connects to
- Built in
- Zebra label printers, RD-certified fingerprint readers, barcode scanners, NIC SMS gateway with DLT templates, e-RaktKosh import and upload files.
- Your HIS
- Patients are registered in Xcyto by MRD or CSV import. A connection point for HIS lookup is ready, and each HIS link is scoped per project.
- Analysers
- Results are entered by staff and checked by a second person. There's no direct analyser interface in the current release.
The road to go-live.
You keep your current records running until your own team signs off on the new system.
Install
Application, database and donor portal on your servers.
Configure
Your rules, master data, fees, counters, devices and roles.
Migrate
e-RaktKosh import with a dry run and signed reconciliation.
Validate
IQ, OQ, PQ and UAT from the supplied pack, plus a CERT-In empanelled security audit.
Train
By role, on a sandbox, in English and Malayalam.
Run in parallel
Alongside your current records, with a daily discrepancy review.
Go live
On your blood centre head's go/no-go sign-off.
See it working on synthetic data.
Ask for a walkthrough of the full chain, donor to bedside, on a demonstration system that holds no real patient or donor records.
- support@xcyto.app
- Research office
- Cytoscan Intelligence
Office No. 04, Golden Jubilee Building
CSIR-National Institute of Interdisciplinary Science and Technology
Thiruvananthapuram, Kerala - Business office
- Cytoscan Intelligence
DOTSPACE Private Offices
Level-B, No. 03 & 04, Kowdiar
Thiruvananthapuram