01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Biospecimen traceability, sample selection, cross-biobank exchange, retrospective comparability, and analysis of preanalytical effects.
- Limits
- SPREC compresses selected variables and is not a complete process history, empirical quality score, or substitute for SOPs. Unknown, unavailable, and local conditions still require explicit handling.
- Best for
- Biobanking and Laboratory teams working across Acquire → Harmonize → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Biobanking and Laboratory source data, metadata, and local mappings
- SPRECWhat changes
Use SPREC as a pinned metadata vocabulary across Acquire → Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A biobank generates a version-pinned SPREC v4.0 code at processing and release, retains the underlying timestamps and SOP evidence, and exposes both the code and its version to downstream researchers.
Why it matters: Makes important preanalytical covariates available for confounding and batch-effect analysis, but the code alone cannot establish specimen integrity or assay fitness.
04
What it fits with
Complements MIABIS specimen metadata and ISO 20387 quality-system controls; a LIMS can store the SPREC code alongside detailed timestamps, procedures, equipment, and custody records.
- Metadata profileSDRF-Proteomics
Both support Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaNWB
Both support Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - TerminologyLOINC
Both support Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - StandardInChI
Both support Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision SPREC must support.
Pin the exact version and companion artifacts: v4.0 · online 2024 · issue publication 2025.
Map one representative input to the required metadata vocabulary artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
SPREC compresses selected variables and is not a complete process history, empirical quality score, or substitute for SOPs. Unknown, unavailable, and local conditions still require explicit handling.
Run one representative end-to-end pilot and record exactly where SPREC loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Makes important preanalytical covariates available for confounding and batch-effect analysis, but the code alone cannot establish specimen integrity or assay fitness.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
Standard PREanalytical Code Version 4.0 publication record
Official publisher or steward guidance for this metadata vocabulary profile.
- Publisher
- ISBER Biospecimen Science Working Group