Cytogenetic LUTs belong inside the scoring workflow

In most cytogenetics labs we've talked to, the probe Lookup Table (the mapping a SME uses to interpret what a stain or signal pattern actually means) lives in a spreadsheet. Sometimes a wiki page. Occasionally a printed binder near the microscope.

This isn't a knock on the teams running it that way. The LUT is one of the most carefully-curated assets in the lab. Each row in it represents years of decisions. Of course it lives somewhere safe and edit-controlled.

But it doesn't live where the work happens. And that has a cost.

The cost of context-switching

Watch a cytogeneticist score for an hour. The pattern is roughly:

1. Pull up the image
2. Recognize the relevant signal
3. Tab over to the LUT spreadsheet
4. Find the matching row
5. Apply the interpretation
6. Record the call in whatever system is logging it
7. Repeat

Steps 3 and 4 are the cost. Per case, it's small. Across a shift, it isn't. And the interpretation step (5) gets noisier the more the SME has to jump out of context to look something up.

Worse: the LUT in the spreadsheet and the LUT the SME is using in their head can drift. A row added last week may or may not be in active use by every reviewer. If two reviewers are scoring the same assay using slightly different LUTs, your QC team finds out about it the hard way.

What we do differently

DataTorch supports embedding the cytogenetic LUT directly into the scoring workflow. It works roughly like this:

• The LUT lives as a managed asset inside your DataTorch environment. Version-controlled, edit-permissioned, auditable.
• During scoring, the relevant LUT entries appear next to the image the SME is reviewing, not in a separate tab.
• The interpretation choices the SME makes are recorded against the LUT version that was active at the time. Six months later, your QC team can reproduce exactly what they saw.
• When the LUT is updated, the change is logged, and reviewers see the new mappings on the next case (or after the rollout window your lab defines).

It isn't a glamorous feature. It's also one of the highest-leverage things we've shipped for cytogenetics customers, because every minute saved on lookup is a minute spent on judgement.

What we don't do

A few clarifications, because we get asked.

We don't ship a starter LUT. Yours is yours; we have no opinion about what should be in it.

We don't auto-update from external sources. If your lab pulls reference data from a public registry, that's a workflow you run; we ingest the result.

We don't lock you in. If you decide to take your LUT to another platform, export it as CSV. Done.

If your scoring workflow has a Lookup Table

The pitch is simple: bring it inside the workflow. The lift is small, the downstream effect on throughput and reproducibility is not.

Book a call if you want to talk through what this looks like for your assays.