Bring the instrument results into the sample review.
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.
Thermo Fisher Scientific
Sample review
- Measurements, units and source-file references
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
Collect results and metadata exported from Thermo Fisher Scientific instrument software with the Seal IoT app, 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’s IoT app or a scoped integration. The equipment model, software version and available interfaces determine the connection method.
- Find models in the instrument catalogue →
- Chromeleon guide →
- Xcalibur guide →
- QuantStudio guide →
- NanoDrop One guide →
- Qubit 4 guide →
- Attune NxT guide →
- OMNIC guide →
- KingFisher guide →
- Countess 3 guide →
- On-site equipment docs
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.
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.