Voluntary Blood Donor Records After a Local Change

When a hospital stops asking for replacement donors, keep four linked records: the written instruction and its effective date, a controlled donor-source field for each donation, the consent and screening trail, and reports that reconcile each source total to individual donor and unit records. Preserve earlier classifications exactly as recorded.

A monthly voluntary-donation total cannot stand alone. You should be able to open any line behind that total and show who classified the donation, which local instruction applied and where the supporting donor records sit.

Separate national policy from the local instruction

The National Blood Policy, 2002 sets the national direction towards voluntary non-remunerated donation and the time-bound phasing out of replacement donors.¹ Your operative date and scope must come from the written instruction that applies to your centre or the hospital you serve.

Rule 122G makes maintenance of the records and registers specified in Schedule F Part XIIB a condition of the blood centre licence.² Keep the local instruction as the document that explains why your source classification or reporting practice changed.

Ask the issuing authority to make these points clear:

• instruction or reference number;
• date issued and effective date;
• hospital, facility or service covered;
• whether the change covers every donation pathway or a limited request pathway;
• treatment of requests already in progress on the effective date;
• the earlier instruction being replaced; and
• the person authorised to approve clarifications.

A news report or verbal message should prompt verification, not silent reconfiguration. Log an unclear direction and obtain documented clarification through your approved change-control route.

Classify donor source at registration

Use a controlled field instead of free text. Your approved source dictionary should keep voluntary non-remunerated and replacement donations separately countable wherever both categories occur, while accommodating any additional category required by the applicable instruction.

Keep donor origin separate from the request pathway

Record donor origin against the donor and donation. Record the hospital’s replacement-donor practice against the relevant referral or request pathway. A later component preparation, reservation or issue should not rewrite how the original donation was classified.

This separation also matches the record structure in Schedule F Part XIIB, Section L, which lists the blood donor record, master records for blood and components, the issue register and records of components supplied as distinct records.³ Your source report should therefore state which record and transaction status it counts.

Introduce the change without rewriting history

Set the cutover from the effective date in the written instruction. Keep donations before that point under the source code valid when they were recorded. If a technician corrects a genuine entry error, retain the original value and the reason for correction.

Put the change into use through five controlled steps: receive the instruction, approve the source codes, set the cutover, classify each donation and reconcile the resulting report.

Keep consent and screening connected

Schedule F Part XIIB provides for donor selection and written donor consent, while Section L requires the blood donor record and the linked master records.³ A voluntary source label does not prove that consent was obtained or screening completed.

For each completed collection, keep a retrievable chain containing:

• donor identifier and recorded source category;
• written consent record;
• completed donor screening and medical examination record;
• acceptance or deferral outcome;
• donation and bag or unit identifier;
• linked master blood and component records; and
• any authorised correction to the source classification.

When screening ends in deferral, keep the decision connected to the donor record so it remains available on return. The same retrieval problem is addressed in donor deferral records that work on return.

For a camp collection, keep the collection mode separate from donor source and connect each donation to the relevant camp record. Your blood donation camp documentation trail should lead to the same donor and unit identifiers used in the source report.

Build reports that reconcile to donations

Because Section L separates donor records from component and issue records, avoid mixing donation counts with component preparation, supply or issue counts in one source total.³ Name the report denominator clearly, such as completed collections during the reporting period.

A useful source report should show:

• reporting period and the instruction version applied;
• total completed collections;
• collections by approved donor-source category;
• collection location or hospital scope where relevant;
• unclassified records and documented exceptions;
• corrections made after initial entry; and
• confirmation that the source subtotals equal the stated total.

If the replacement count is zero after the cutover, print zero rather than leaving the field blank. A blank cannot tell the reviewer whether there was no activity or whether classification was missed.

Retrieval by donor and unit identifier is the test that matters. Your donor-to-recipient traceability and component separation record should use the same identifiers without changing the original donor-source value.

Retain the instruction with the records it explains

The above said records shall be kept by the licensee for a period of five years.³

That is the closing note in Schedule F Part XIIB, Section L. It does not specify a start date, so do not add a last-entry trigger as though the Schedule contains one. Rule 122G separately requires testing records to be maintained for five years from the date of manufacture.² The distinction is covered in the blood bank record retention guide.

Keep a small change pack ready

1. The current local instruction and the instruction it replaced.
2. The approved SOP and donor-source code dictionary.
3. The configuration or register change showing the effective date.
4. A donation trail from before the change and another from after it.
5. The reconciled source report and correction log.
6. Documented staff communication or acknowledgement.

RAKT is cloud blood bank software used by 200+ blood centres across India. It runs donor registration, camp management, compliance records and returns, but your centre remains responsible for approving the source categories, entering them correctly and producing the local instruction when asked.

If an assessor selects a donation recorded immediately after the change, you should be able to produce the instruction, source classification, consent and screening trail, linked unit records and the report total without relying on staff memory.

Sources

1. National Blood Policy, 2002 no public URL
2. Drugs and Cosmetics Rules, 1945, Rule 122G cdsco.gov.in
3. Drugs and Cosmetics Rules, 1945, Schedule F Part XIIB cdsco.gov.in