Thermo Scientific Chromeleon to LIMS integration

Seal brings Chromeleon results into the laboratory workflow that needs them. Connect sequence reports and individual injections to sample tests, specifications and batch records, giving analysts and reviewers a clear path from the reported value to its source evidence.

One sequence supports two sample tests

Illustrative sample and sequence records for the proposed mapping.

  1. Sequence

    SEQ-204 / assay report

    Keep the selected report template and channel.

  2. Standard

    Injection 1 / reference solution

    Retain its analytical role within the sequence.

  3. Sample test

    S-204-A / injections 3 and 4

    Link the supporting injections to one requested assay.

  4. Review

    B-204 / accepted test revision

    Show the result and source report used in the batch review.

Move from sequence reports to connected decisions.

A sequence can contain standards, blanks and several customer or batch samples. Seal lets you organize that evidence around the work: one requested test, its supporting injections and the result ready for review. Teams gain an accessible record of how a laboratory result contributes to the broader batch decision.

neil can help assemble the relevant reports and compare selected sample results across sequences. The reviewer can follow the source links and see the analytical context, making the discussion more useful than a list of isolated numbers.

With the records connected, try asking neil:

Prepare a review of these Chromeleon sample results. Group the injections by requested test and show the report, channel and processing revision for each reported value.

Make the report template part of the connection.

Chromeleon 7.3.2 documents report export for an injection, a sequence or multiple sequences. The selected template, channel and output format determine what the receiving workflow sees. For multiple sequences, the preferred report template and format must be configured for each sequence.

Agree a stable handoff format for the values that Seal should map, and retain a readable report for review. Record the chosen template and revision with the connection configuration so a future report-layout change can be assessed against a known example.

Keep standards and samples in their proper roles.

Resolve the sequence and injection before matching the sample test. Preserve the injection role, component and channel where supplied. The connection should identify which injections support a reportable sample result and where the analytical procedure records suitability or exclusions.

This structure makes the review easier: Seal can present the requested sample test with its relevant evidence while retaining the surrounding sequence record. The receiving calculation follows the agreed method rather than treating every numeric row as another sample result.

Reconcile the transfer at the result level.

Configure the collector and mapping Script around completed exports. Track received files, resolved tests and any rows needing attention. If one sample cannot be matched, the receiving team should be able to identify it without losing the results that were successfully linked.

Use a source result and evaluation identifier to distinguish a retry from a changed analysis. Where an external LIMS accepts the final values, retain its acknowledgement with the exchange. Seal then connects analytical delivery to the work that follows, including a batch review or investigation.

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.

A standard has the same label as a sample

The sequence report includes a calibration standard and a sample with overlapping display labels.

Expected behaviour
Use the source injection identity and role to keep the standard separate from the sample test.
Evidence to keep
The sequence report, role mapping and linked sample population.

A sequence uses an unexpected report layout

The preferred report template changes and the export no longer contains the agreed result column.

Expected behaviour
Identify the missing field and hold the affected result for mapping review.
Evidence to keep
The template identity, received report and mapping exception.
More checks for this connection
  • Export a sequence with blanks, standards and two samples and verify their roles.
  • Change the report template and confirm that an unexpected layout is visible to the mapping owner.
  • Compare destination test counts with the source sample population.

Before you connect

How does Seal integrate Chromeleon with LIMS?

Seal can collect completed Chromeleon reports and use a configured mapping to connect sequences, injections and selected results to laboratory records. An external LIMS exchange can be included using that system's supported interface.

Can a whole Chromeleon sequence be imported?

Yes, a sequence export can be the source for the connection. The mapping should retain the sequence and distinguish the sample, standard and blank roles needed by the receiving workflow.

What happens when the Chromeleon report template changes?

Treat the changed template as a change to the data contract. Compare representative exports, update the field mapping where needed and verify the reported results before using the new layout routinely.

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 Chromeleon sequence report containing standards, blanks and sample injections.
  • The report template, chosen channel and receiving sample-test codes.
  • A second export with a changed analysis or report layout.
Discuss this connection