Donor Deferral Records That Work on Return

Your blood donor deferral records should do one job at the next visit: identify the returning donor, retrieve the authorised decision and pause the workflow long enough for staff to apply your centre’s current donor-selection SOP. Attach every deferral to a durable donor identifier and record the decision date, authorised person, controlled reason category, current status, review information and the alert staff must see on re-presentation.

A paper form can remain supporting evidence, but it cannot be the only place where the decision lives. When the donor returns at your centre or another camp, staff should find the status before proceeding, even if a different technician entered the original deferral.

Build one complete deferral record

Schedule F Part XIIB of the Drugs and Cosmetics Rules, 1945 sets requirements for donor selection and the associated blood-centre records.¹ The National Standards for Blood Centres provide the corresponding framework for donor selection, deferral and blood-collection documentation; use the current applicable edition held in your controlled document register.²

Use your approved donor-selection and deferral SOP to define the precise categories, statuses, review authority and permitted actions. If software needs a value that the SOP has not defined, resolve the gap through document control instead of letting technicians invent labels as they work.³

A practical deferral record should carry the following fields:

Keep this field set inside the same donor master used by your wider donor-management workflow. A separate deferral spreadsheet or paper-only list can fall out of step with registration.

Separate the reason, status and review

Reason, status and review answer different questions. The reason category records the authorised basis used at that visit, the status tells staff what applies now, and the review field tells them whether another authorised decision is required.

A note that says only not eligible leaves the next technician guessing. Choose a controlled reason category and status from your SOP, then preserve any restricted supporting note according to your centre’s access rules.

Clinical thresholds and eligibility criteria belong in the approved procedure and the authorised assessment. This record should preserve the decision that was made, not create a second set of clinical rules inside the software.

Make the decision survive identity matching

A phone number or name can help with a search, but neither should replace your centre’s durable donor identifier. Match the returning person to the donor master first, then retrieve the deferral history attached to that identity.

If a camp team creates a second registration for an existing donor, the original alert may remain attached to the first profile. Build duplicate checking and reconciliation into your camp documentation trail, including the handover from camp records to the centre.

Once a donation is accepted, the same identity discipline supports traceability from donor to recipient. Fix duplicate donor masters before they create two incomplete histories.

Store the status and display an alert

Keeping a status in the database is only half the control. Display it at the point where staff identify the donor and review eligibility, before the workflow can move past the SOP-defined action.

A useful alert shows the decision date, current status, controlled reason category and required next step. Detailed notes can remain restricted while the person handling registration sees enough information to route the donor correctly.

When your SOP permits an acknowledgement, review or override, record the staff identity, date, action and resulting decision. Preserve the earlier entry and append the new one so an assessor can follow the chronology.

Handle the donor’s return in a fixed order

At re-presentation, match the donor identity, retrieve the complete deferral history, check the current status and review information, obtain any authorised review required by the SOP, and append today’s outcome. If matching produces duplicate or uncertain records, pause and reconcile the identity before relying on either history.²³

Once staff complete the review, keep the prior decision visible as history. Changing an old deferred status into an accepted status without a new dated entry removes the evidence of what happened between the two visits.

Test retrieval, not just data entry

Ask a colleague who did not enter the deferral to process a test return visit. A working control should let that person:

• find the donor through the permanent identifier and approved matching fields;
• see the original decision date, category and authorised person;
• understand the current status and required review action;
• open the supporting visit or camp record;
• see who created, reviewed or changed the status; and
• append a new decision without overwriting the old one.

If the colleague has to ask who keeps the paper register, search a separate spreadsheet or remember which camp used another numbering series, the record has failed the return-visit test.

Keep the history after the status changes

Rule 122G of the Drugs and Cosmetics Rules requires the relevant records to be preserved for five years.⁴ A deferral reaching its review date does not erase its history, and a later review becomes another dated entry in the chronology.

Apply the same retrieval and retention controls described in your blood bank record retention process. An assessor should be able to move from the donor master to the original decision and every subsequent review without reconstructing the sequence from loose forms.

Use automation for the preventable failure

Software helps when it matches a durable identity, presents the status before staff proceed, restricts decisions to authorised roles and preserves every change. Include those controls when assessing a blood bank management system, rather than checking only whether it has a field called deferral.

In RAKT, map your centre’s approved categories, permissions and return-visit actions before go-live. Connect each change to staff activity tracking so the centre can identify who recorded or reviewed the decision; software presents the record, while your authorised staff remain responsible for applying the SOP.

The final test is simple: when the donor returns, can the technician find the earlier decision before proceeding, understand what action the SOP requires and record today’s authorised outcome without destroying yesterday’s evidence?

Sources

1. Drugs and Cosmetics Rules, 1945, Schedule F, Part XIIB, donor selection and record requirements cdsco.gov.in
2. National Standards for Blood Centres, Ministry of Health and Family Welfare/NACO, current applicable edition, donor selection and blood collection requirements no public URL
3. The blood centre's approved donor-selection and deferral SOP, current controlled version no public URL
4. Drugs and Cosmetics Rules, 1945, Rule 122G, records and retention cdsco.gov.in