Flow Cytometry Reporting Templates

Flow cytometry reports carry more interpretive weight per page than almost any other lab report — a single immunophenotype finding can be the deciding factor in a leukemia or lymphoma diagnosis. A report template that structures this consistently, every time, reduces the chance that a busy sign-out session skips a step that matters.

The core sections a flow cytometry report needs

1. Specimen and clinical context Specimen type (peripheral blood, bone marrow, tissue, fluid), collection date, and — critically for interpretation — the clinical question being asked. A flow study ordered to rule out a lymphoproliferative disorder is read differently than one monitoring known disease, even with similar raw data.

2. Panel used The specific antibody panel applied, including which tubes/combinations were run. Panels are often disease-suspicion-specific (a broad screening panel versus a targeted panel for known or suspected lymphoma versus a myeloid-focused panel), and the report should make clear which panel logic was applied and why, since that shapes what conclusions can and can't be drawn from the result.

3. Specimen adequacy and cell viability Total events collected, viability percentage, and whether the specimen was adequate for the requested analysis. A low-viability or low-cellularity specimen with a stated limitation is a defensible report; the same specimen reported without that caveat is a liability if the result is later questioned.

4. Gating strategy A described (and ideally illustrated) gating hierarchy — how populations of interest were isolated from the total events, particularly for any population flagged as abnormal. This is the section most likely to get abbreviated under time pressure, and the section a reviewing pathologist most needs intact to independently assess the interpretation.

5. Immunophenotype findings Marker expression for each population of interest, typically presented as a structured table (marker, population, result — positive/negative/dim/bright, and percentage where relevant) rather than narrative prose. Structured tables are dramatically easier to compare against prior results for monitoring cases.

6. Interpretation The synthesized conclusion — does the immunophenotype support a specific diagnosis, rule one out, or remain equivocal pending correlation with morphology and other studies. This section should explicitly state what it does not rule out when the panel or specimen adequacy limits the interpretation's scope.

7. Correlation note A statement tying the flow result to (or flagging the need for correlation with) morphology, cytogenetics/FISH, and molecular studies where applicable — flow cytometry rarely stands alone in a heme-onc diagnostic workup, and the report should make that explicit rather than implying a standalone conclusion.

A structured table beats narrative prose

Marker	Population	Result	% Positive
CD19	B-cell gate	Positive	94%
CD5	B-cell gate	Positive (aberrant)	88%
CD23	B-cell gate	Positive	91%
Kappa/Lambda	B-cell gate	Kappa-restricted	—

A table like this, kept in the same structure across every report, does two things a paragraph doesn't: it makes serial monitoring reports directly comparable at a glance, and it makes the report faster and less error-prone to review during sign-out.

Where reporting consistency breaks down

• Panel documentation gets abbreviated when the same panel is run routinely, on the assumption "everyone knows what's in it" — until a report gets reviewed months later, or by someone outside the original team.
• Gating strategy is described inconsistently between technologists, making population definitions hard to compare across serial specimens from the same patient.
• Specimen limitations get mentioned informally (verbally, in a sign-out conversation) but not captured in the final report text.

Why templated structure matters more here than in most report types

Flow cytometry interpretation is inherently pattern-based and comparative — a current result is almost always read in the context of a panel, a gating logic, and often a prior result from the same patient. A consistent, structured template isn't a formatting nicety in this context; it's what makes serial comparison actually reliable, and what protects the interpretation when it's reviewed later by someone who wasn't in the room when the specimen was run.