Inventory Management · August 24, 2026
Blood Unit Recall Records: Trace Every Component
If your centre withdraws a unit or component, the record must prove that you found the complete component family, established the status of each item, traced anything issued or supplied, documented every contact and reconciled the case before closure. A component with no verified outcome should remain an open exception under your approved SOP.
NABH’s current Accreditation Standards for Blood Centres require controlled recall procedures and traceability through the blood and component trail.1 Recall criteria, clinical decisions and instructions to a receiving facility remain with your centre’s approved SOPs and competent authority.
Build one record chain for the whole recall
A recall form records the decision to act. It does not, by itself, prove completeness. That proof comes from linking the recall file to the donor record, blood and component master records, inventory movements, issue or supply records, crossmatch documentation, communications and final reconciliation.
Schedule F Part XIIB, section L of the Drugs and Cosmetics Rules names the statutory source records, including the blood donor record, master records for blood and components, the issue register, records of components supplied, the cross-matching report and transfusion adverse reaction records.2 Your donor-to-recipient traceability provides the ordinary trail. A recall tests whether that trail still works when you must account for every related component at once.
Record the donation or unit ID and every component ID or product code exactly as they appear in your master and component separation records. These IDs are the keys your team uses to retrieve the complete family and prevent a second component from being missed while attention is on the first.1
| Record or control | What it proves | Fields to retrieve |
|---|---|---|
| Recall initiation record | Scope and authority | Trigger reference, date and time, initiator, unit and component IDs |
| Donor and master records | Source donation and component family | Donation ID, component IDs, preparation and status references |
| Inventory movements | Physical custody | Storage location, controlled status, movement and disposition |
| Issue, crossmatch and supply records | Destination and recipient trail | Issue status, request or recipient reference, receiving facility and date |
| Communication log | Action outside the centre | Contact person, time, channel, instruction and acknowledgement |
| Reconciliation and closure | No component was omitted | Outcome for every ID, exceptions, reviewer and closure authority |
Schedule F Part XIIB names the underlying records but does not prescribe a separate statutory recall form.2 Your recall record should join those sources into one controlled case file, rather than copy selected entries into a register that cannot be checked against the originals.
Retrieve location, issue status and recipient in order
Start with the authorised scope recorded under your SOP. Preserve the reason or source reference, the opening date and time, the person who initiated the action and the identifiers included. If a storage event led to the review, retain the relevant cold-chain excursion record as source evidence without using it to replace the recall record.
Next, build the component family from the master and separation records. Search both active and historical inventory, then match the recorded location against physical custody. A status such as “available” or “held” is incomplete if the team cannot identify where the component is and which control has been applied.
For an issued component, retrieve the issue entry, request and crossmatch trail used by your centre. For a component supplied to another establishment, retrieve the components-supplied record, transfer details and the receiving establishment’s acknowledgement. These are part of the record categories specified in Schedule F Part XIIB.2 An inter-state stock transfer needs the same unit-level destination trail; a summary dispatch total cannot establish which component reached which centre.
Record each communication with the date and time, person contacted, method, instruction given and response received. Close the case only after every component ID has a documented outcome, unresolved discrepancies have been escalated under the SOP, and the authorised reviewer has signed or approved the reconciliation. Those controls turn the centre’s NABH recall procedure into retrievable evidence.1
Give every component a clear outcome
Use a controlled outcome list in your SOP so two technicians do not describe the same status differently. Suitable operational outcomes may include:
- Located in stock and placed under the required control.
- Returned and assigned a controlled inventory status.
- Discarded with the corresponding disposition entry.
- Supplied to another establishment, with contact and acknowledgement recorded.
- Issued against a patient request, with the recipient trail identified and the receiving area contacted.
- Unresolved, escalated and left open for further action.
Treat an issue-register entry as evidence that the component left available inventory. Use the patient request, crossmatch trail and receiving-area response to document what was subsequently confirmed. Never change “issued” to a final recipient outcome merely to make the reconciliation balance.
If the review starts after a question from a ward or another facility, preserve the original question, who received it and how it was resolved. Your transfusion inquiry records can supply that opening evidence, while the recall file accounts for every linked component.
Test the file the way an assessor will retrieve it
A defensible retrieval test starts with one identifier and answers the following without relying on staff memory:
- Which donor and source collection produced this unit?
- Which components were prepared from that collection?
- Where is each component now, or what final disposition was recorded?
- Which patient request or receiving establishment is linked to anything issued or supplied?
- Who was contacted, when were they contacted and what did they acknowledge?
- Which discrepancies remained open, and who authorised eventual closure?
NABH treats recall and traceability as controlled processes supported by records, review and corrective action.1 If your team can retrieve one issued component but cannot account for its linked products, the ordinary unit trail has worked while the recall trail has failed.
Keep SOP ownership clear as well. The current approved procedure should define who may open a recall, apply inventory controls, communicate outside the centre, review discrepancies and authorise closure. Your quality manual and SOP control should also prevent staff from using an obsolete recall form during an actual event.
Retain the source trail with the recall file
Schedule F Part XIIB, section L says that the records listed there shall be kept for five years. It names no start date for that five-year period.2 Rule 122G separately requires testing records to be maintained for five years from the date of manufacture.3
Section L does not separately name a recall register.2 Your blood bank record-retention schedule should therefore list the recall case file and its supporting source records clearly, so communication and closure evidence are not removed while the underlying unit trail remains available.
Retrievability matters as much as preservation. If older separation records are filed by date, issue entries by patient and communication records in email, write down the index that joins them. Otherwise, the records may all exist while nobody can assemble the case under assessment pressure.
Run a retrieval drill before you need a recall
Select a completed donation under your quality plan and ask a staff member who did not process it to reconstruct the component family. Have them locate each component’s recorded disposition, retrieve any issue or supply trail, identify the communication route and prepare a reconciliation.
Document where the drill stopped: a component ID that was not searchable, a transfer acknowledgement filed elsewhere, a stock status with no location, or a closure record with no reviewer. Assign corrective action to those specific gaps and repeat the retrieval after correction.
Software helps when donor, component, inventory, crossmatch and issue records remain searchable through consistent identifiers. Your centre still decides the recall scope, follows its approved SOP, communicates with the relevant parties and signs the closure. The useful test is simple: start with one unit ID and prove, from records, where every linked component went.