Blood bank requests, crossmatch and issue — with the MSBOS audit, component exchanges and supply agreements.
Requests, grouping, crossmatch and issue with cold-chain custody — every unit traceable from donor code to transfusion record. A whole-blood bag collected by DonorDesk lands here with its components under it, and a bag whose infection screen is pending or reactive cannot be crossmatched or issued, whatever the shelf says. Audit and supply: the hospital’s own Maximum Surgical Blood Order Schedule from its transfusion committee (none ships), units crossmatched against units transfused per procedure with the C:T ratio and orders above the schedule, read against a target only when the committee sets one; every bag sent to or received from a partner blood bank on one ledger, settled up to a date with a reference and the balance by component frozen; and supply agreements with each partner — component, monthly quota against bags received this month, dates, the agreement’s reference, and a processing charge only as the agreement states it with the order it rests on named. Nothing blocks a crossmatch, and blood is never priced here.
/bloodbankblood.readWhat it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.