Thermo Fisher Scientific instrument integration

1Choose the source software and evidence.

Each route starts from a documented output of the vendor software. Check the installed version, licensed options and export settings against the linked docs. A listed route is not an acquisition driver or a universal parser.

2Distinguish acquisition, analysis and preparation evidence.

Chromeleon and Xcalibur workflows can involve acquisition files, sequences and evaluated result reports. An input sequence describes planned work; it is not the evaluated analytical result. OMNIC adds spectra and evaluation context, while QuantStudio adds plate assignments and analysis settings. Choose the documented output for the installed software generation before configuring its mapping.

KingFisher preparation reports answer a different question from Qubit or NanoDrop measurements. A completed preparation does not establish the concentration or purity of the recovered material. Link the preparation outcome to the downstream measurement through sample identity, keeping each source report and its method context separately identifiable.

3Keep the measurement’s dimensions and qualifiers.

For PCR, preserve the sample, target, well and replicate relationships needed to interpret the analysed result. For Attune cytometry, distinguish the event-level FCS evidence from the selected population statistics. Countess results need counting and dilution context, and an exported image can support interpretation without becoming another numeric measurement.

Choose typed fields for values people need to search, compare or calculate, and preserve the complete export as a File. Keep reported units and any relevant qualifiers. A failed fit, excluded well or missing count must remain distinguishable from a valid zero in both the mapping and the review.

4Check the handoff for the actual instrument workstation.

Some workflows export through removable storage, others through a configured workstation folder. Verify the supported handoff and software options for the installed model. A cloud Script cannot collect a file directly from the instrument’s local drive; arrange the completed-file handoff through the site computer where necessary.

Use a representative result with its source report to test collection, mapping and access. Repeat the check for each application in scope. Success with a Qubit CSV does not validate a QuantStudio analysis export, and neither verifies the analytical meaning of an Xcalibur result report.

5Example: follow an extraction into quantification

Preserve the preparation record and the later measurement as separate evidence about the same material.

Preparation

Retain the KingFisher run identity, sample assignments and reported outcome.

Recovered sample

Resolve the destination sample and its relationship to the input material.

Quantification

Link the Qubit or NanoDrop measurement with its method, unit and measurement time.

Use these relationships as a mapping example for your own templates. The receiving fields and record grain are configured through Seal Scripts and APIs.

6Configure the collection and mapping for your site.

For local exports, use a completed-file handoff on the instrument workstation or another approved site computer. Seal IoT collects the file and uploads it to the chosen Seal destination over outbound HTTPS. Keep source files until delivery and mapping have been verified.

A Seal Script can validate the expected layout, resolve source identities and write selected typed fields. Keep the original export as File content. Acquisition and vendor analysis remain in the source application; Seal collects the completed results and does not send instructions to the instrument.

Follow the on-site equipment setup instructions ↗, then use the source-specific guide above to test the actual export and mapping. For a result exchange with an existing LIMS, also define that system’s supported receiving operation and sample identifiers.

7Test the configured workflow with known evidence.

1. Trace one sample from a preparation report to a known downstream assay without inferring an unmeasured yield.
2. Test the extra dimensions used by the application: wells, targets, populations, wavelengths or time points.
3. Check a qualified result and a revised analysis, preserving their source evidence and interpretation.

Keep the test outcome with the configuration and repeat the relevant checks when software, reports, analysis settings or destination fields change.

Discuss your Thermo Fisher Scientific workflow with a representative export, the installed software version and the records you want to connect.