Beckman Coulter Vi-CELL BLU to LIMS integration

Seal connects Vi-CELL BLU cell count and viability results to the samples, cultures and experiments your scientists are working on. Bring the measurements and their source evidence into the same record, making culture comparisons easier to prepare and easier to review.

A cell-count result joins a culture comparison

Illustrative records; reported density scale and dilution are part of the mapping.

  1. Sample

    CULT-019 / day-4 collection

    Resolve the sampled culture and collection event.

  2. Analysis

    VICELL-02 / analysis 3108

    Retain the source analysis and configured cell type.

  3. Results

    Viability, total density, viable density

    Keep each quantity in its own field with units and dilution context.

  4. Review

    Culture comparison / selected analysis

    Link the chosen result to any repeat measurements and source files.

Give every cell count its culture context.

Seal lets the lab connect viable cell density, total density and viability to a named sample and collection event. Scientists can compare a culture series while keeping the method, dilution and analysis identity close to the reported value.

neil can help assemble a comparison of selected cultures and identify records with missing units or unresolved repeat analyses. The resulting brief points back to the source measurements, giving your team a useful foundation for the next scientific discussion.

With the records connected, try asking neil:

Compare viable cell density and viability across these cultures. Show each sample's collection time, dilution and source analysis, and identify repeat measurements needing review.

Choose the result export for the question you need to answer.

Beckman Coulter documents CSV result exports and separate report and offline-analysis options for Vi-CELL BLU. Agree the single-sample or multiple-sample layout available in your installation, then collect a completed result file for the receiving workflow.

In Seal, map each source analysis into the relevant sample record and retain its file. If image-level reanalysis is part of the laboratory's process, keep the appropriate source archive available through the agreed retention workflow alongside the result summary.

Keep the scale with the reported density.

Define separate fields for total cell density, viable cell density and viability percentage. Preserve the reported unit and scale, plus the dilution context used by the analysis. The import should document any conversion it performs.

Compare the imported values with a known source result before using them in a study view. With that mapping in place, Seal helps scientists work from consistent fields instead of reinterpreting density labels every time they combine exports from different runs.

Retain the measurements behind the selected result.

A repeat count can be useful scientific evidence. Keep its own analysis identity and link it to the same collected sample, rather than overwriting the previous measurement. Record the laboratory's selected or reported result separately where its workflow requires a choice.

Connect that sample to the culture and collection time. The resulting Seal record supports study comparisons and review while retaining a clear route to both the original count and the reason a later measurement was selected.

Vendor references for this workflow

Test it with your data.

Use these cases to agree and test the connection’s behaviour. They are proposed acceptance checks, not completed tests or automatic connector features.

The exported density is scaled in millions

The CSV reports a density in millions of cells per mL while the destination field uses cells per mL.

Expected behaviour
Apply the agreed scale conversion once and retain the original reported value and unit.
Evidence to keep
The source column definition, conversion rule and comparison with the original result.

A second cell count is chosen for reporting

The same culture sample has two attributable analyses and the laboratory selects the later measurement.

Expected behaviour
Keep both analyses and record which measurement supports the reported sample result.
Evidence to keep
Both source analyses, their sample reference and the result-selection history.
More checks for this connection
  • Compare density scale and dilution treatment with the original result.
  • Import a multiple-sample CSV and reconcile each analysis separately.
  • Verify that a repeat count remains accessible after selecting a reported result.

Before you connect

Can Vi-CELL BLU results be connected to Seal LIMS workflows?

Yes. Configure the CSV mapping to retain sample and analysis identity, selected cell-count results and their units, then connect the records to the culture or experiment in Seal.

How are repeat Vi-CELL counts handled?

Keep each analysis as an attributable measurement of the collected sample. The receiving workflow can identify the selected result while retaining the earlier measurements for review.

Can Seal combine Vi-CELL viability with other culture results?

Yes. Match the measurements through their sample and culture references. Seal can bring cell counts together with related chemistry and process evidence, and neil can help prepare a comparison from those connected records.

Check your system’s connection options.

Confirm the installed version, available exports and permissions. These pages cover the source interface and link to setup instructions.

For configuration: Seal Scripts and local-file collection.

Build the workflow around your lab.

Start with a Seal blueprint, then connect the source evidence and records your team uses.

Start with one export.

Bring the source evidence and the records it needs to connect to. For this workflow, a useful starting pack is:

  • A single-sample and a multiple-sample Vi-CELL BLU CSV from your installation.
  • The cell-density units, scale and dilution convention used by the laboratory.
  • A collected sample with two analyses and the corresponding culture record.
Discuss this connection