LookbackForward Trace from a Reactive Donor to All Consignees and Recipients

Lookback is the identification and follow-up of earlier blood donations after a later finding indicates evidence of HIV or HCV infection in the donor. Also called donor lookback or transfusion lookback, it connects the donor's history to previously collected components, their consignees, and, where applicable, transfusion recipients. The governing blood provisions are 21 CFR 610.46 for HIV and 21 CFR 610.47 for HCV.

A familiar trigger is a donor who previously tested nonreactive and now tests reactive. The provisions also address an establishment being made aware of other reliable test results or information indicating evidence of the relevant infection. Lookback therefore is not limited to a new reactive result generated by the collecting establishment's own testing.

Paragraph (a) of each section applies to establishments collecting Whole Blood or blood components, including Source Plasma and Source Leukocytes. Paragraph (b) assigns duties to consignees. A transfusion service receiving affected blood components should distinguish its consignee responsibilities from the collecting establishment's responsibilities; the two roles are not interchangeable. The HCT/P retention boundary is addressed separately below.

• Outside this definition: donor deferral under 21 CFR 610.41.
• Outside this definition: the broader donor-screening and further-testing framework under 21 CFR 610.40.

Under paragraph (a)(1) of each blood Lookback section, the establishment reviews the retained records to identify previously donated blood and blood components. The ordinary identification anchor is the donor's most recent nonreactive screening tests: the provisions specify donations collected twelve months and less before those tests.

Both sections also contain a lesser-period alternative involving a reactive direct viral detection test and a nonreactive antibody screening test. The HIV provision names nucleic acid testing and HIV p24 antigen testing as examples of direct viral detection. The HCV provision names nucleic acid testing. The applicable period is twelve months and less before the specified testing event, using whichever of the two periods is lesser.

Keep three concepts separate: the records reviewed to identify prior donations, the test-anchored period used to identify affected collections, and the in-date status and intended use that determine the required quarantine controls. A long record-retention period does not itself define the identification window.

The two sections are closely parallel, but they should not be treated as interchangeable text. In particular, their direct-detection examples and their representative-notification wording differ.

Within 3 calendar days: review and initial controls

Sections 610.46(a)(1) and 610.47(a)(1) place the initial actions within 3 calendar days after the donor's reactive result or awareness of the other reliable results or information described in those provisions. The collecting establishment must review the records, quarantine the covered previously collected in-date blood and components, and notify consignees to quarantine them. The intended-use conditions and pooled-component exception are explained below. These are calendar days, not business days.

Within 45 calendar days: notify consignees of test results

Paragraph (a)(2) requires further testing for the relevant infection on the reactive donation under 610.40(e). Paragraph (a)(3) separately requires notification to consignees within 45 calendar days after the donor tests reactive under 610.40(a) and (b). The clock does not restart when further-testing results become available.

For HIV, the notice communicates the further HIV testing results. For HCV, it communicates the further HCV testing results. Each section provides for communicating the reactive screening result instead if further testing is unavailable or FDA has exempted it for the specified use under an investigational new drug application or investigational device exemption. The notice must include results for the identified earlier collections from the donor.

Within 12 weeks: reasonable recipient-notification attempts

For HIV, paragraph 610.46(b)(3) requires the consignee to notify affected transfusion recipients, or their physician of record, of the need for HIV testing and counseling when further testing is positive or the specified reactive-screening fallback applies. Reasonable attempts must occur within 12 weeks after receiving the further HIV results from the collecting establishment, or the reactive screening result when that fallback applies.

For HCV, paragraph 610.47(b)(3) requires the corresponding notice concerning HCV testing and counseling when further HCV testing is positive or its specified reactive-screening fallback applies. Its 12-week reasonable-attempts clock likewise runs from receipt of the specified HCV results, not automatically from the donor's reactive-test date.

Both sections require notification through the physician of record or a legal representative or relative in the stated circumstances involving a minor, a recipient adjudged incompetent by a State court, or a competent recipient for whom State law permits representative or relative receipt. The HIV sentence also expressly includes a deceased recipient. These are notification requirements, not a clinical testing or counseling protocol.

Every date and event below is fictional. Assume one unnamed donor has a reactive HCV screening result, positive further testing is available, and the reactive-direct-detection/nonreactive-antibody alternative does not apply. A consignee holds affected in-date components and also has records of earlier components already transfused. The collecting establishment sends the positive further-testing results on January 20, 2026, and the consignee receives them that day.

This example illustrates timing, not a recommended schedule for delaying work. In particular, the initial quarantine actions precede receipt of the further-testing results. The recipient deadline concerns reasonable attempts to notify; it should not be described as a guarantee that every recipient will have been reached.

The collecting-establishment quarantine and quarantine-notice requirements cover identified, previously collected in-date blood and components intended for use in another person or for further manufacture into injectable products. The exception is specifically for pooled blood components intended solely for further manufacturing into products manufactured using validated viral clearance procedures. The consignee quarantine provisions contain the same pooled-component exception.

This is not an exemption for all plasma, all Source Plasma, or every product destined for manufacturing. Source Plasma is expressly included in the sections' establishment scope. The exception belongs to the specified quarantine and quarantine-notice provisions; it is not a blanket removal of record review, further testing, results notification, or recordkeeping duties.

Both the collecting establishment and consignee must release from quarantine, destroy, or relabel quarantined in-date blood and components consistently with the further-testing results, or with the reactive screening result when the stated unavailable-testing or FDA-exempted IND/IDE circumstances apply. Quarantine is therefore a control step, not the final disposition record.

Under 606.160(a)(1), records must be maintained concurrently with each significant step in collection, processing, compatibility testing, storage, and distribution so that the steps can be traced. Records must be legible and indelible, identify the person performing the work, include entry dates, show test results and their interpretation, identify assigned product expiration dates, and provide a complete history of the work.

Section 606.160(c) requires a donor number for each accepted donor. It connects the collected unit to the donor, the donor's medical record, components or products from that unit, and records describing their history and ultimate disposition. The record provisions also require links between the donor and each previous donation's unit number, together with distribution and disposition records.

Lookback documentation is explicit, not merely implied by general traceability: 606.160(b)(1)(viii) requires records of activities under 610.46 and 610.47 covering quarantine, consignee notification, testing, notification of the recipient, physician of record or legal representative, and disposition. See also 21 CFR Part 606.

Under 606.160(d), retain individual product records for at least the later of 10 years after records of processing are completed or 6 months after the individual product's latest expiration date. The provision also requires retention beyond expiration as necessary to facilitate reporting unfavorable clinical reactions. When a product has no expiration date, its records are retained indefinitely. This is not an indefinite-retention rule triggered simply by a donor's deferred status.

HCT/P boundary: a different product-record clock

For records pertaining to a particular HCT/P, 1271.270(d) requires retention for at least 10 years after administration; if administration is unknown, use at least 10 years after distribution, disposition, or expiration, whichever is latest. This is a different clock from the blood-product rule. HCT/P establishments should not substitute one for the other; the other duties of 21 CFR Part 1271 are outside this definition.

A useful operational case file connects the following stages without making reviewers reconstruct the investigation from disconnected messages. These are record-organization suggestions, not additional regulatory fields or deadlines.

1. Trigger → Record the finding, when it became known, the donor identifier, the infection involved, and the evidence used to open the case.
2. Identification → Preserve the search logic, test anchors, treatment of the lesser-period alternative, and the resulting donation and component list. Explain exclusions rather than silently dropping units.
3. Quarantine → Connect each affected component to its location, status, control action, and supporting evidence; distinguish available stock from components already transfused or otherwise disposed of.
4. Consignee notice → Link each consignee to the affected components, the notice sent, its time, the destination used, and any acknowledgment or follow-up.
5. Further testing → Connect the reactive donation to the subsequent test reports and their receipt dates; document any unavailable-testing or exemption issue for review.
6. Results notice → Preserve what results were communicated, to whom, when, and which earlier collections the communication covered.
7. Recipient attempts → Link the relevant recipient records to the appropriate notification route and a dated attempt log, without confusing an attempt with successful contact.
8. Disposition record → Reconcile each affected component to its final status and supporting decision, retaining links back to the trigger and test evidence.

As a practice check, another authorized reviewer should be able to follow the chain in both directions: from donor to component and consignee, and from a component back to the donor finding and disposition evidence. Open communications and unresolved component statuses can remain visible as separate follow-up items rather than being hidden by a single case-closed label.

• How would the system keep the 3-calendar-day, 45-calendar-day, and 12-week clocks separate, including their different start events?
• How would users record the identification-period calculation and distinguish the nonreactive-screening anchor from the lesser-period alternative?
• Can reviewers trace a donor to previous donations, derived components, consignees, recipient-notification records, and final dispositions?
• How would a workflow distinguish a quarantine notice from a later results notice and preserve the evidence for each communication?
• How would the system represent the narrowly scoped pooled-component exception without treating all plasma as exempt?
• How would users distinguish a notification attempt, an acknowledgment, and confirmed recipient contact?
• How would retention settings distinguish expiring blood products, products without an expiration date, and HCT/P administration-based records?
• What evidence could a buyer inspect to evaluate change history, access controls, record export, and retrieval of a complete Lookback case?