01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Biobank directories, cohort discovery, federated catalogues, access negotiation, and metadata exchange across biospecimen networks.
- Limits
- Core 3.0 is aggregate-level metadata, not a complete specimen record. Individual-level components and serializations version separately, and MIABIS does not by itself establish consent, sample quality, or one universal conformance test.
- Best for
- Biobanking and Clinical and Laboratory teams working across Plan → Acquire → Harmonize → Exchange.
- Maturity
- ScalingUsable now, but adoption or tooling is still developing. Pilot the exact stack first.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Biobanking and Clinical and Laboratory source data, metadata, and local mappings
- MIABISWhat changes
Use MIABIS as a pinned metadata profile across Plan → Acquire → Harmonize → Exchange
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
A network catalogue validates Core 3.0 records for each biobank, collection, research resource, and network, links individual-level records with stable identifiers, and pins every component, terminology, and serialization release.
Why it matters: Improves cohort discovery and exposes sample and donor context, but analytical quality, outcome validity, representativeness, access rights, and leakage controls remain separate gates.
04
What it fits with
A draft MIABIS-on-FHIR implementation guide maps selected content to FHIR R4; SPREC adds preanalytical history, while ISO 20387 addresses biobank competence and operations.
- StandardISO 20387
Both support Biobanking and Laboratory work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - StandardCDISC
Both support Clinical work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileSDRF-Proteomics
Both support Laboratory work and meet around Plan, Acquire, Harmonize, Exchange. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata vocabularyDPV
Both support Clinical work and meet around Plan, Acquire, Harmonize, Exchange. 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 MIABIS must support.
Pin the exact version and companion artifacts: Core 3.0 · individual-level components version independently.
Map one representative input to the required metadata profile 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
Core 3.0 is aggregate-level metadata, not a complete specimen record. Individual-level components and serializations version separately, and MIABIS does not by itself establish consent, sample quality, or one universal conformance test.
Run one representative end-to-end pilot and record exactly where MIABIS 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. Improves cohort discovery and exposes sample and donor context, but analytical quality, outcome validity, representativeness, access rights, and leakage controls remain separate gates.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
BBMRI-ERIC MIABIS documentation
Official publisher or steward guidance for this metadata profile profile.
- Publisher
- BBMRI-ERIC