Standard · 2018 Edition 1 · published · replacement revision at FDIS

ISO 20387 Biobanking Requirements

Maintained by ISO/TC 276 Biotechnology

What it helps you do

ISO 20387 supports requirements for biobank competence, impartiality, consistent operation, and quality control of biological material and associated data collections.

  • Biobanking
  • Laboratory
  • Discovery
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits and where it does not

Use these four checks before committing implementation time.

Use it when
Biobank quality systems, capability assessment, accreditation preparation, partner qualification, and governance of materials intended for research and development.
Limits
The current edition is under revision, so contracts and assessments must pin the exact edition. Its scope excludes biological material intended for food, feed, or therapeutic use.
Best for
Biobanking and Laboratory and Discovery teams working across Plan → Acquire → Harmonize → Exchange.
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.

  1. InputWhat starts

    Biobanking and Laboratory and Discovery source data, metadata, and local mappings

  2. ISO 20387What changes

    Use ISO 20387 as a pinned standard across Plan → Acquire → Harmonize → Exchange

  3. OutputWhat becomes possible

    A handoff the next system or team can validate against the same release

Readiness gateThe current edition is under revision, so contracts and assessments must pin the exact edition. Its scope excludes biological material intended for food, feed, or therapeutic use.

03

A concrete example

A biobank defines its scope, competence, impartiality, operating controls, and quality evidence against the 2018 edition, records nonconformities, and maintains a transition plan for the replacement edition.

Why it matters: Strengthens provenance and operational consistency around source material, but conformance does not certify that a derived dataset is representative, statistically valid, or ready for a model.

04

What it fits with

Provides the organizational and quality-system layer around MIABIS metadata and SPREC preanalytical coding; those artifacts support evidence and exchange but do not replace ISO 20387 requirements.

05

Implementation starter

Start with one bounded handoff. Pin, test, and review it before scaling.

  1. Define one handoff, its accountable owner, and the decision ISO 20387 must support.

  2. Pin the exact version and companion artifacts: 2018 Edition 1 · published · replacement revision at FDIS.

  3. Map one representative input to the required standard artifacts.

  4. Test the result against the canonical source and record every exception.

  5. Preserve the source data, mappings, and review evidence before scaling.

06

Test the main limitation

Risk

The current edition is under revision, so contracts and assessments must pin the exact edition. Its scope excludes biological material intended for food, feed, or therapeutic use.

Test

Run one representative end-to-end pilot and record exactly where ISO 20387 loses context, needs an extension, or depends on another standard.

Risk

Machine-readable output may still be unfit for analysis or ML.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Strengthens provenance and operational consistency around source material, but conformance does not certify that a derived dataset is representative, statistically valid, or ready for a model.

07

Official resources

Specifications, diagrams, examples, and guides from the organizations that maintain them.

  • Primary source2018 Edition 1 · published · replacement revision at FDIS

    ISO 20387:2018 catalogue record

    Official publisher or steward guidance for this standard profile.

    Publisher
    ISO/TC 276 Biotechnology
    Open official source

Next action

Put this profile in context

Compare its role with adjacent standards or place it inside an end-to-end data pathway before choosing an implementation.