Skip to main content

Integration guideInstrument export

Thermo Fisher Scientific

Collect exported instrument results and metadata into Seal records.

Illustration of a seal beside a Thermo Scientific Orbitrap Exploris 480 mass spectrometer with a Vanquish UHPLC.

Thermo Fisher Scientific to SealInstrument export

Seal reads
Results and metadata exported from Thermo Fisher Scientific software
Writes back
No
Source of truth
Instrument software
Set up
Seal Edge and an upload Script
Neil › Sample review
draft

Bring the instrument results into the sample review.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Results and metadata exported from Thermo Fisher Scientific software
Returns
  • Measurements, units and source-file references
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with Thermo Fisher Scientific: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Collect results and metadata exported from Thermo Fisher Scientific instrument software with Seal Edge, and map them to Seal records with a Script. Separate guides cover Chromeleon, Xcalibur, QuantStudio, NanoDrop and others.

Connection setup and permissions

Connect through Seal Edge or a scoped integration. The equipment model, software version and available interfaces determine the connection method.

Related blueprints

2Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

3Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

Data and failure handling

Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →