# Cell-product chain of identity and custody

Source: https://onco.cc/terms/chain-of-identity-and-custody/  
OnCo record `chain-of-identity-and-custody` (Term). Data CC BY-NC 4.0, attribute "Data from OnCo (onco.cc)"; commercial use needs a licence.

## TL;DR

Identity records connect cells and products to their source and intended recipient. Custody records show who held them and what happened during handoffs.

## Summary

Traceability preserves relationships across source material, engineering construct, processing lots, containers, samples and intended recipients. Chain of identity and chain of custody answer different questions: what material and recipient are associated, and who had responsibility at each stage under which recorded conditions. A coded identifier makes a relationship recordable; it does not independently prove that the label, material and recipient agree.

## Fields

- Kind: Term
- Last checked: 2026-11-09
- Also known as: cell-therapy traceability; COI and COC; chain of identity; chain of custody

## Notes

- A collection can branch into processing lots, doses or test samples. Retain parent links and construct versions so a sample result can be attributed to the material it represents. One bag need not mean one manufacturing run or one dose; an allogeneic workflow can relate donor material to later recipients according to its actual design.
- ICCBBA ST-028 version 1.1.0, June 2025, describes chain-of-identity relationships and responsibilities. IG-050 version 1.0.0, December 2023, gives bounded examples in which material is returned to the same patient; it explicitly does not cover one collection manufactured into therapies for multiple patients. That example scope must not be generalised into a complete donor-bank scheme.
- In a fictional single-recipient example, collection A produces lot A, which branches into doses A1 and A2 and test sample S. Each child retains the parent link. A separate custody trail records handlers, handoff times and conditions. Keeping those links does not establish acceptable quality or clinical suitability.
- Barcodes, biological identity assays, HLA typing, potency results and temperature traces are different evidence. None alone replaces the complete material/intended-recipient verification. A discrepancy or excursion requires investigation and the authorised quality disposition; an audit trail is evidence to assess, not a guarantee of safety.
- FDA's CAR T-cell guidance addresses documented tracking from collection to administration and independent recipient/label checks. The required process is not equivalent to purchasing a particular orchestration system. Research samples, fresh products, cryopreserved products and in vivo carriers retain their own applicable identities and handling context.

## Sources

- FDA: CAR T-cell development guidance, January 2024: https://www.fda.gov/media/156896/download
- ICCBBA: Chain of Identity standard ST-028, version 1.1.0 (June 2025): https://iccbba.org/wp-content/uploads/2025/08/1a7593_0aa7a5f7202c4b43be4cc11bcd2048ef.pdf
- ICCBBA: single-patient collection examples IG-050, version 1.0.0 (December 2023): https://iccbba.org/wp-content/uploads/2025/08/1a7593_badfaf3c48d443f78006340096a671e0.pdf

## Connected records

- terms: [Apheresis (leukapheresis)](https://onco.cc/terms/apheresis/), [Cell-manufacturing outcomes and nonconforming products](https://onco.cc/terms/cell-manufacturing-outcomes/)
- technologies: [Allogeneic (off-the-shelf) cell therapy](https://onco.cc/technologies/allogeneic-cell-therapy/), [Autologous CAR-T manufacturing, batch by batch](https://onco.cc/technologies/car-t-manufacturing-process/), [Cell-therapy orchestration and chain-of-identity software](https://onco.cc/technologies/cell-therapy-orchestration-software/), [Cryopreservation and cell-therapy cold chain](https://onco.cc/technologies/cell-therapy-cold-chain/), [In vivo CAR-T](https://onco.cc/technologies/in-vivo-car-t/)
- fronts: [Cell Therapy](https://onco.cc/fronts/cell-therapy/)

---
JSON: https://onco.cc/api/v1/entities/chain-of-identity-and-custody.json