Biobank Specimen Request Workflow: Steps and Data Fields
A biobank specimen request workflow is the defined sequence a researcher follows to obtain samples or linked data from a biobank: application, feasibility check, scientific and ethics review, access committee decision, agreement, preparation and release. Each step creates a record with a status, an owner and a timestamp, so the biobank can show exactly why every specimen left the freezer and who approved it.
This guide walks through each stage, lists the data fields that a request record should hold, and explains how the same workflow can govern the data that specimens generate, not only the tubes themselves.
Why the Request Workflow Deserves Careful Design
Biobank collections are finite. Every aliquot released for one project is an aliquot that cannot go to the next, and some sample types, such as rare disease tissue or early-life cohorts, cannot be replaced at all. A clear request workflow is how a biobank protects that scarce resource while still getting it into the hands of good science.
The workflow also carries legal and ethical weight. Participants gave consent for particular kinds of research. Funders often require fair and transparent access. Regulators and auditors expect the biobank to show that each release matched its consent and governance rules. International guidance such as the ISBER Best Practices and the ISO 20387 standard for biobanking both expect documented access procedures.
Finally, most requests today are not only for samples. Researchers want the clinical, genomic and imaging data linked to those samples, and often they want the data alone. A workflow designed only for physical material leaves the larger, faster-moving asset, the data, without the same controls.
The Stages of a Specimen Request
1. Pre-Application Inquiry and Feasibility
Most workflows start with a feasibility question: does the biobank hold enough samples that match the study criteria? Researchers query a catalog or ask the biobank team to count eligible specimens by type, volume, disease group and available linked data. Good practice is to return counts only, never participant-level detail, at this stage.
2. Formal Application
The researcher submits a structured application covering the scientific question, study design, requested specimen types and volumes, linked data needed, funding, the team and their institution, and the analyses planned. A structured form beats a free-text letter because it lets reviewers compare requests consistently.
3. Scientific and Ethics Review
Reviewers assess scientific merit, whether the requested amount is justified, and whether the use matches participant consent. Many biobanks also require proof of ethics approval from the applicant’s own institution.
4. Access Committee Decision
A data and materials access committee makes the decision: approve, approve with conditions, request changes or decline. Conditions might limit volumes, restrict certain analyses or require results to be returned to the biobank.
5. Agreement
Approved requests move to a material transfer agreement for samples and a data access agreement for linked data. These set out permitted use, publication terms, return of results, and what must happen to leftover material.
6. Preparation and Release
Lab staff retrieve, aliquot and quality-check specimens, then ship them under chain of custody controls. For data, this is where the biggest design choice sits: is a dataset extracted and sent out, or is access granted inside a controlled environment?
7. Closure and Return of Results
The request stays open until the project reports back, returns derived data or results where required, and confirms what happened to unused material.
The Data Fields a Request Record Should Hold
Whatever software runs the workflow, the request record needs a consistent core. These fields make the process auditable and reportable.
- Request ID and version, so amendments are tracked.
- Applicant, institution and role, with verified identity.
- Project title, aims and lay summary.
- Specimen types, volumes and counts requested, each linked to the feasibility result.
- Linked data requested, by data category.
- Consent categories required, checked against what participants agreed to.
- Ethics approval reference and expiry date.
- Status (submitted, under review, approved, conditionally approved, declined, released, closed) with a timestamp for every change.
- Reviewer and committee decisions, with the reasons recorded.
- Agreement references for materials and data.
- Specimen IDs actually released, linking each one to its chain of custody record.
- Return-of-results due date and status.
A status history with timestamps is what turns a request system into evidence. When an auditor asks why a particular sample went to a particular lab, the answer should take one query.
Releasing Samples Versus Releasing Data
Physical release and data release look similar on paper, but they behave very differently once the approval is given.
| Dimension | Data extract sent to researcher | Access inside a federated TRE |
|---|---|---|
| What leaves the biobank | A copy of record-level data | Only approved aggregate results |
| Control after release | Relies on the signed agreement | Technical controls stay in place for the whole project |
| Audit trail | Ends at transfer | Every query and output request is logged |
| Consent withdrawal | Hard to apply to copies already sent | Applied once, at the source |
| Project closure | Depends on the researcher deleting data | Access is switched off |
| Time to access | Delayed by extraction and transfer | Access granted as soon as approved |
For samples, physical release is unavoidable. For data, it is a choice, and it is the choice that decides whether the biobank keeps control after the committee says yes.
Connecting the Workflow to a Trusted Research Environment
A Trusted Research Environment (TRE) lets the access decision drive technical permissions directly. When the committee approves a request for linked data, the TRE grants the named researchers access to exactly the approved cohort and variables, in a workspace where data never leaves the source. When the project closes, access ends.
Outputs follow the same governance. Researchers submit results for release, and an airlock checks them against disclosure rules before anything leaves. The request record and the TRE audit log then tell one consistent story, from application to final output.
This also helps with cross-site studies. Where a project needs samples and data from several biobanks, a Federated Trusted Research Environment lets each biobank apply its own access decision while the researcher runs a single analysis across all approved sites. Each biobank keeps its own committee, its own consent rules and its own data.
Who Does What in the Workflow
Clear roles stop requests from stalling between teams. A typical split looks like this.
- Biobank access manager: owns the request record, checks completeness and moves it between stages.
- Scientific reviewers: judge merit and whether the requested volumes are justified.
- Access committee: makes and records the decision, including any conditions.
- Legal or contracts team: issues and tracks material and data access agreements.
- Laboratory team: retrieves, aliquots, checks quality and ships specimens.
- Data team: sets up access to linked data and reviews outputs before release.
Writing these roles into the workflow, with a named owner for each status, makes it clear who must act next on every open request and lets the biobank measure where time is lost.
Common Bottlenecks and How to Remove Them
- Slow feasibility answers. Publish a searchable catalog with aggregate counts so researchers can self-serve before applying.
- Incomplete applications. Use structured forms with required fields, and validate requested specimen types against the catalog automatically.
- Consent checks done by hand. Store consent scope as coded fields so eligibility can be filtered, not read from scanned forms.
- Agreement delays. Keep standard material and data access agreement templates, and negotiate only true exceptions.
- Data extraction backlogs. Replace bespoke extracts with access inside a TRE, so approval and access happen together.
Practical Next Steps
- Map your current workflow from first inquiry to closure and time each stage over the last ten requests.
- Compare your request record with the field list above and close the gaps.
- Link every released specimen ID to its request ID and chain of custody record.
- Decide, as a policy, whether linked data is released as extracts or accessed in place, and write that into your access procedure.
- Report request volumes, approval rates and time to access to your governance board each quarter.
A well-designed request workflow is how a biobank says yes to more research, faster, without losing sight of the samples and data it is trusted to protect.
Frequently asked questions
What is a biobank specimen request workflow?
It is the documented process a researcher follows to obtain biobank samples or linked data, from feasibility and application through review, approval, agreement, release and closure.
Who approves biobank specimen requests?
Usually an access committee, sometimes called a data and materials access committee, after scientific and ethics review. Its decision and reasons should be recorded on the request.
How long does a specimen request take?
It varies widely by biobank and request type. The main delays tend to be incomplete applications, agreement negotiation and data extraction, all of which can be reduced with structured forms, standard templates and in-place data access.
What data fields should a request record include?
Request ID, applicant and institution, project aims, specimens and data requested, consent categories, ethics approval, status history, committee decisions, agreements, released specimen IDs and return-of-results status.
Can researchers get linked data without receiving a copy?
Yes. In a Trusted Research Environment, approved researchers analyze linked data inside a controlled workspace and only approved aggregate results are released.
How does consent affect the request workflow?
Each request must match the consent participants gave. Storing consent scope as coded fields lets the biobank filter eligible specimens and apply withdrawals consistently.