LookbackForward trace from a reactive donor to all consignees and recipients

Lookback is the regulatory obligation to identify, quarantine, and notify when a previously-distributed donation came from a donor who later tests reactive for a relevant transfusion-transmitted infection. The two FDA-codified lookback rules are 21 CFR 610.46 (HIV) and 21 CFR 610.47 (HCV); FDA guidance also covers lookback for other agents under the general 21 CFR 606.100 obligation to investigate biological product deviations. The corresponding tissue obligation is in 21 CFR 1271.150–1271.270.

Lookback is forward, not backward. It starts from a current reactive donor and looks forward through every donation that donor previously made, identifies every component derived from each donation, identifies every consignee that received each component, and ultimately reaches the recipient of each component. Backward tracing — from a sick recipient to the source donor — is a separate exercise, usually called trace-back.

• Repeat donor with a reactive screening test on a current donation that is confirmed by a supplemental (more specific) test as positive.
• Repeat donor with a reactive screening test on a current donation that is not confirmed but where the screen meets the regulatory criteria for triggering lookback (the 'repeatedly reactive' standard).
• Donor self-disclosure of a previously-undisclosed risk factor that, had it been known, would have made prior donations ineligible.
• Post-donation information indicating a possible infection (e.g. donor calls back to report a positive test or recent diagnosis).
• Recipient adverse event suggesting a transfusion-transmitted infection — triggers both lookback on this donor and trace-back on the implicated component.

Look-back applies to in-date and recently-expired components and to plasma in the manufacturing pool for plasma derivatives. The exact look-back horizon varies by agent and rule — HIV lookback under 610.46 reaches back to all donations from the donor made within the previous 5 years, and longer if there is reason to believe earlier donations are implicated.

1. Quarantine — within three calendar days of identifying the donor as reactive, quarantine all in-date components from that donor still in inventory (606.160(b)(1) and 610.46/47).
2. Identify consignees — produce a list of all consignees that received any in-date component derived from any prior donation by that donor within the lookback horizon.
3. Notify consignees — within 45 calendar days (HIV/HCV) of the donor identification. Notification must include the specific component identifiers, the test result, and a request that the consignee notify the transfusion recipient.
4. Consignee action — quarantine any in-date component still on hand, identify the recipient(s) of any already-transfused unit, and notify the recipient(s). Recipient notification is typically the responsibility of the consignee facility's medical staff.
5. Reporting — document every step and report the donor identification as a biological product deviation on Form FDA 3486 if the criteria are met.

21 CFR 1271 does not use the word 'lookback' but creates equivalent obligations through the donor-eligibility framework. If post-distribution information would have rendered a donor ineligible — including a positive infectious-disease test on a subsequent donation, post-mortem information, or a recipient adverse event suggesting transmission — the establishment must investigate, identify all HCT/Ps from the affected donor, and take appropriate action including notification of consignees, recall, and reporting via Form FDA 3486.

Tissue lookback is operationally harder than blood lookback because tissue allografts can sit on a hospital shelf for years before implantation, and a single donor can generate hundreds of allografts processed weeks or months apart. The chain of identity from donor to consignee is mandatory; the chain to the patient is the receiving hospital's.

Lookback that works is built on three foundations: a clean per-donor record that ties every donation back to the donor, a clean per-component record that ties every component to its source donation and onward to its consignee, and an event-driven workflow that triggers quarantine, notification, and reporting automatically the moment the triggering event is recorded. The chain of identity must survive donor renames, address changes, ID number reissues, and consignee mergers.