OpenCyto Gating Templates: Version the Strategy and Its Assumptions

OpenCyto's 2014 framework makes hierarchical gating strategies explicit. Reusing a template still requires checking the staining panel, preprocessing and failure route.

The template is part of the measurement record

When an automated gating result changes, the reason may lie in a template edit rather than in a specimen. A saved image cannot reliably show which hierarchy, algorithm or parameter produced the change. Versioning the strategy makes that question answerable.

What the original OpenCyto framework describes

Finak and colleagues' 2014 PLOS Computational Biology paper describes hierarchical gating templates in CSV text. These specify populations, parent relationships, markers and algorithms; gate coordinates are then generated from the data. The framework connects preprocessing, population identification and downstream comparison, and supports comparisons with imported manual analyses.

The authors discuss reuse with the same staining panel under well-standardised assay conditions. Their examples include intracellular cytokine staining and mass cytometry. These demonstrations do not establish that an arbitrary clinical MRD strategy is validated, or that a template can be transferred unchanged across instruments and panels.

Original CFCM conceptual checklist: Version the strategy; Check the inputs; Review exceptions. No patient data or reproduced study figure. — Original CFCM conceptual diagram. Educational synthesis; not clinical validation.

Make a change reviewable

For a local teaching exercise, preserve an existing strategy and create a separate candidate version containing one intentional change. Identify the changed step and the downstream populations that depend on it. Save the software environment and input file identities with both runs.

Ask a reviewer to explain the difference without relying on a verbal account from the developer. Comparing only the final population count can conceal an upstream change that happens to cancel another difference. Review the parent population and the gate affected by the edit before interpreting the final result.

Reuse requires an exception route

A template embodies assumptions about the input and the meaning of its markers. Decide how a workflow will respond when a channel is missing, a distribution differs substantially or a target population cannot be located. An explicit held result is more informative than silently accepting a gate because the program completed.

These are proposed implementation checks, not performance results from a new CFCM experiment. The appropriate validation evidence depends on the intended application. Keep automation reproducibility separate from agreement with a reference process and from the clinical consequences of an error. Manual review also needs a recorded basis; it is not automatically a correct answer.

Daily Learning Pill

A versioned template makes a strategy inspectable. It does not, by itself, establish that the strategy is suitable for a clinical decision.

Explore CFCM Academy and the evidence hub. Original ChatGPT/Codex educational analysis, without independent scientific review or clinical certification.