01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Reproducible flow-cytometry acquisition, publication, repository deposition, reanalysis, and exchange of gating strategies across compatible tools.
- Limits
- Implementations can omit or interpret metadata differently, Gating-ML support is not universal, and the stack does not supply one governed cell-type ontology, panel model, calibration policy, or assay-quality threshold.
- Best for
- Cytometry and Immunology 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
Cytometry and Immunology and Laboratory source data, metadata, and local mappings
- FCS · MIFlowCyt · Gating-MLWhat changes
Use FCS · MIFlowCyt · Gating-ML as a pinned standard 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 laboratory exports FCS 3.1 files, completes the MIFlowCyt 1.0 record, serializes compatible gates as Gating-ML 2.0, and preserves compensation, transformations, controls, software versions, and source workspaces.
Why it matters: Makes event measurements, experiment context, and some analysis decisions reusable, but gating subjectivity, calibration, batch effects, panel drift, cell labels, and cohort design remain material risks.
04
What it fits with
FCS carries event measurements and acquisition metadata, MIFlowCyt supplies experiment, specimen, instrument, and analysis context, and Gating-ML encodes gates that FCS alone cannot preserve.
- Data model / schemaAIRR · MiAIRR
Both support Immunology and Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - 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
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision FCS · MIFlowCyt · Gating-ML must support.
Pin the exact version and companion artifacts: FCS 3.1 · MIFlowCyt 1.0 · Gating-ML 2.0.
Map one representative input to the required standard 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
Implementations can omit or interpret metadata differently, Gating-ML support is not universal, and the stack does not supply one governed cell-type ontology, panel model, calibration policy, or assay-quality threshold.
Run one representative end-to-end pilot and record exactly where FCS · MIFlowCyt · Gating-ML 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 event measurements, experiment context, and some analysis decisions reusable, but gating subjectivity, calibration, batch effects, panel drift, cell labels, and cohort design remain material risks.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
ISAC Data Standards
The steward overview for FCS 3.1, MIFlowCyt, Gating-ML 2.0, and related cytometry interoperability work.
- Publisher
- International Society for Advancement of Cytometry
Flow Cytometry Standard 3.1
The open publication describing the FCS 3.1 event-data file format and its changes from FCS 3.0.
- Publisher
- ISAC Data Standards Task Force
MIFlowCyt 1.0 Recommendation
The minimum-information recommendation for reporting a flow-cytometry experiment and its analysis context.
- Publisher
- ISAC Data Standards Task Force
Gating-ML 2.0
The open publication describing the XML-based representation for exchanging cytometry gates across software.
- Publisher
- ISAC Data Standards Task Force