Data Readiness
Knowledge BaseLife-sciences R&D
54 profiles ·
source-checked 13 Jul 2026

Metadata profile · MIAME 2001 guidance · MINSEQE 1.0 (June 2012)

MIAME + MINSEQE Guidelines

Maintained by FGED Society legacy standards · operational repository implementers

What it helps you do

Use MIAME · MINSEQE when you need minimum information for interpretable and reproducible microarray and high-throughput sequencing studies, including design, samples, raw and processed data, and protocols.

  • Omics
PlanAcquireHarmonizeExchangeLearn + reuse

01

Where it fits—and where it doesn’t

Use these four checks before committing implementation time.

Use it when
A submission and publication completeness gate for functional-genomics studies, especially when preparing repository records and supporting data.
Do not use it as
Do not treat MIAME · MINSEQE as a complete solution on its own. These are minimum-information checklists rather than one executable schema. Stewardship is legacy, and newer assay classes such as single-cell data require current repository guidance and additional profiles.
Best for
Teams working with Omics data across Plan → Acquire → Harmonize → Exchange.
Maturity
EstablishedEstablished enough for serious use; still pin the exact release and any implementation profile.

02

See it in the workflow

A standard creates value by changing a handoff, not by existing in a catalog.

  1. InputWhat starts

    Omics data, metadata, and the local decisions around them

  2. MIAME · MINSEQEWhat changes

    MIAME · MINSEQE applies a shared metadata profile across Plan → Acquire → Harmonize → Exchange

  3. OutputWhat becomes possible

    A more consistent, reviewable handoff for the next system or team

Readiness gateBefore scaling: These are minimum-information checklists rather than one executable schema. Stewardship is legacy, and newer assay classes such as single-cell data require current repository guidance and additional profiles.

03

A concrete example

Before release, a transcriptomics study checks that design, biological variables, sample-data relationships, raw reads, processed matrices, and laboratory and computational protocols are present.

Why it matters: Raises the metadata floor for reuse, but does not standardize expression matrices, ontology depth, QC, batch correction, labels, or cohort representativeness.

04

What it fits with

MAGE-TAB is a MIAME-supportive serialization; ISA can represent richer study structure. Current repository guidance applies MIAME to microarrays and MINSEQE to high-throughput sequencing.

05

Implementation starter

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

  1. Name an accountable owner and the decision MIAME · MINSEQE must support.

  2. Pin the exact version and companion artifacts: MIAME 2001 guidance · MINSEQE 1.0 (June 2012).

  3. Map one representative input to the required metadata profile 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

Limitation to test first—and the tests that catch it

Risk

These are minimum-information checklists rather than one executable schema. Stewardship is legacy, and newer assay classes such as single-cell data require current repository guidance and additional profiles.

Test

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

Risk

A structured or machine-readable result can still be unfit for analysis or AI.

Test

Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Raises the metadata floor for reuse, but does not standardize expression matrices, ontology depth, QC, batch correction, labels, or cohort representativeness.

07

Why we believe this

Checked against the canonical source plus independent operational evidence from an adopter, regulator, or implementation report.

Evidence notation: E1 + E2. The code is shorthand; the plain-language statement above is the claim.

Formal status
Published legacy guidelines; FGED closed, repository implementation continues
Confidence
High
Review state
Source-checked · watch
Reviewed by
Functional-genomics metadata reviewer
Last verified
13 July 2026
Review again when
Repository guidance or successor minimum-information standard update
How the evidence method works

08

Source shelf

Official diagrams, examples, specifications, and explainers. Nothing external loads until you choose to open it.

  • Primary sourceMIAME 2001 guidance · MINSEQE 1.0 (June 2012)

    FGED legacy standards registry

    The canonical publisher or steward source used to verify this metadata profile profile.

    Publisher
    FGED Society legacy standards · operational repository implementers
    Rights
    Rights remain with the publisher; this knowledge base links to the source rather than copying it.
    Access
    Opens the publisher's source in a new tab; no external media loads on this page.
    Verified
    2026-07-13
    Open at 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.