Biobank software is the specimen- and data-management platform a biorepository uses to track biological samples from collection through storage, distribution, and disposal — linking each specimen’s physical location, consent status, and chain-of-custody record to the metadata that makes it findable and usable for research years later. It is a distinct software category from a general-purpose Laboratory Information Management System (LIMS), built around the specific operational and regulatory demands of running a biobank or biorepository: donor/participant consent tracking, cold-chain inventory across multiple storage tiers, and accreditation reporting under standards like ISO 20387.
What Biobank Software Actually Does
Strip away individual vendor branding and biobank software consistently handles five things:
- Specimen accessioning and inventory. Every aliquot, tube, or block gets a unique identifier at intake, tied to a specific freezer, rack, box, and position — the same underlying problem covered in more physical-storage detail in lab freezer inventory systems and barcode/RFID sample tracking, but extended here to link each specimen record to a donor or participant record.
- Consent and use-restriction tracking. The system records what a donor actually agreed to — a specific study, a broad future-use consent, or a tiered/dynamic model — and is expected to block or flag any request that falls outside that scope. This is the operational layer sitting on top of the models compared in Biobank Specimen Consent Models.
- Chain of custody and audit trail. Who collected, processed, moved, aliquoted, or shipped a given specimen, and when — the same audit-trail principle described generally in Sample Chain of Custody in Research Labs.
- Request and distribution workflow. External investigators request specimens against defined access criteria; the software routes that request through scientific and ethics review, tracks approval, and records what was released, to whom, and under what material transfer terms.
- Regulatory and accreditation reporting. Generating the records an ISO 20387 assessor, a CAP-BAP inspector, or an institutional review board will actually ask to see — quality-management records, non-conformance logs, and specimen disposition history.
How Biobank Software Differs from a General LIMS
A conventional LIMS is built around test workflows: a sample comes in, moves through a defined sequence of analyses, and produces a result. Biobank software (sometimes called biorepository management software) is built around long-term specimen custodianship instead: samples may sit untouched for a decade before a single test is ever run against them, and the record that matters most is not a test result but the consent, provenance, and chain-of-custody history attached to the specimen. Some platforms blend both models — a biobank running its own assays may pair biobank software with LIMS-style workflow modules, or a general LIMS vendor may add biobanking modules on top of a core LIMS. See LIMS Software for Research Labs: A Comparison Guide for the broader LIMS buying landscape if a lab’s real need is test-workflow tracking rather than long-term specimen custodianship.
Compliance Drivers: ISO 20387, GDPR, and Accreditation
Three compliance pressures specifically drive biobank software adoption, more than they drive general lab-software purchases:
- ISO 20387 (biobanking). This standard sets general requirements for biobanking — quality management, biological material handling, and traceability — and increasingly appears as a funder or journal expectation for biorepositories supplying samples to research. Software that cannot produce the traceability and non-conformance records an ISO 20387 assessment requires becomes a real accreditation blocker; see ISO 20387 (Biobanking).
- CAP-BAP. The College of American Pathologists’ Biorepository Accreditation Program is a widely used US accreditation route for clinical and research biorepositories, and its checklist likewise expects specimen-level traceability that manual spreadsheets struggle to sustain past a few thousand specimens.
- GDPR and data protection. For any biobank handling EU participant data, consent status, data minimization, and the research-specific legal bases in GDPR (including the broad-consent framing in Recital 33) have to be enforceable at the software level, not just documented in a policy — the system needs to actually prevent use outside the consented scope, and support data-subject requests without breaking specimen traceability.
Open-Source vs. Commercial Biobank Software
The biobank software market includes both. OpenSpecimen is the best-known open-source option: a biospecimen and biobank management platform that institutions can self-host at no license cost, with commercial hosting, implementation, and support available from Krishagni, the company that maintains it. That combination — free core software, paid support/hosting as an option — is a common pattern in this niche and is worth checking for any platform under evaluation: is the core genuinely open-source (auditable, no vendor lock-in on the data model), and is paid support optional or effectively mandatory once local IT support runs out. Commercial-only platforms exist too, generally sold as SaaS with per-specimen or per-user pricing, and often bundled with broader clinical-trial or lab-informatics suites; evaluate them against the same criteria below rather than assuming a commercial license buys more compliance coverage by default — it doesn’t automatically.
Selection Criteria: What to Check Before Choosing a Platform
Beyond generic software-procurement questions (see Vendor Selection Criteria for a broader lab-procurement framework), a biobank-specific evaluation should specifically check:
- Consent model support. Does it natively support broad, tiered, and dynamic consent, or only a single blanket flag per donor?
- Multi-tier cold storage integration. Can it track specimens across -20°C, -80°C, and liquid-nitrogen storage, and integrate with freezer monitoring/alarm systems rather than treating storage location as a free-text field?
- Barcode/RFID compatibility. Does it integrate with the physical labeling hardware already in use, or does it require re-labeling an existing collection?
- Audit trail and 21 CFR Part 11 support. If specimens will ever feed an FDA-regulated trial, does the system produce electronic records and signatures that meet Part 11 expectations, not just a generic activity log?
- Interoperability. Can it exchange data with a hospital EHR, a clinical-trial CTMS, or a separate LIMS via standard interfaces (e.g., HL7/FHIR), or does every integration require custom development?
- Data residency and hosting model. For EU or other jurisdictionally sensitive collections, where does the data actually live, and does the vendor contract support the biobank’s own GDPR obligations rather than just its own?
- Exit and data-portability terms. Can the full specimen and consent history be exported in a usable format if the biobank switches vendors later, without losing the audit trail?
Is Free Biobank Software Enough?
For a small or early-stage biorepository, a self-hosted open-source platform such as OpenSpecimen can be a genuinely sufficient answer, provided the institution has the local IT capacity to host, back up, and patch it, and the internal expertise to configure consent rules and accreditation reports correctly. What “free” does not cover is the labor: implementation, data migration from spreadsheets or a legacy system, staff training, and ongoing administration are real costs regardless of license price, and they scale with specimen volume and the number of active studies drawing on the collection. Institutions that lack dedicated IT/bioinformatics support for a biobank often find the paid-support option on an open-source platform, or a fully managed commercial SaaS product, cheaper in practice than the staff time a self-hosted deployment would otherwise consume.
Frequently Asked Questions
What is biobank software used for?
Tracking biological specimens from collection through storage, distribution, and disposal — including the donor consent, chain-of-custody, and location data needed to keep a large specimen collection usable and auditable over years or decades.
Is biobank software the same as a LIMS?
No. A LIMS is built around test workflows and results; biobank software is built around long-term specimen custodianship, consent tracking, and distribution to external requesters. Some platforms combine both, but they are conceptually different tools — see What Is a LIMS? for the LIMS side of that distinction.
Is OpenSpecimen free?
The core OpenSpecimen platform is open-source and free to self-host. Krishagni, the company behind it, offers paid hosting, implementation, and support services as an option, not a requirement.
Does biobank software need to comply with GDPR?
Any biobank holding personal data on EU participants needs its software to enforce consent scope, support data-subject rights, and document its legal basis for processing — GDPR compliance is a software-configuration requirement here, not just a paperwork exercise.
Does biobank software help with ISO 20387 accreditation?
It can, if it produces the traceability, quality-management, and non-conformance records an ISO 20387 assessment requires. Software that only tracks freezer location without a full audit trail typically falls short of what an assessor will ask to see.
