Skip to content

Miner

Miner is the clinical core of iFlow. It owns the entities that make up a clinical case — subjects, samples, orders, analyses, labflows, and the variant catalogue — and it is the service a clinical user spends most of their time in.

What Miner owns

Entity What it is Deep dive
Subject The individual being tested Subjects
Sample The physical specimen from a subject Samples
Order The case-level record Orders
Analysis A single pipeline run Analyses
Labflow The stage state machine orders travel through Labflows
Variant Per-order variant records surfaced for curation Variants
VCF browser Per-order variant curation UI VCF Browser

The report is owned by a separate service — see Report service.

Clinical workflow

The clinical journey from sample to signed report is laid out in the Workflows section. If you have not already, read the Default scenario end-to-end walkthrough.

How the pieces fit together

Subject ─┬─ Sample ──┬─ Analysis (runs pipeline, produces VCF)
         │           │
         └─→ Order ──┴─→ Labflow (state machine)
                          │
                          └─→ Report (via Report service)
  • A subject owns one or more samples.
  • Samples carry their sequencing files and can be run through analyses.
  • An order groups samples for a single clinical case and walks through a labflow.
  • The labflow drives which actions are allowed at which stage; see RBAC Matrix.
  • On sign-off, the order produces an immutable signed PDF (owned by the Report service).