Thermo Scientific SampleManager
Trace laboratory findings back to samples, tests and instrument results.
Put this connection to work Set up Thermo Scientific SampleManager in the docs
Prepare a laboratory investigation. Use the permitted Thermo Scientific SampleManager records and show me the supporting evidence.
Collect the selected sample’s results and the available instrument references.
Sample and result records exposed by the installed SampleManager REST API and configured interfaces.
Prepare a laboratory investigation
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
What’s connected.
Trace laboratory findings back to samples, tests and instrument results. Scope an API integration so neil can use the permitted records to prepare analysis, reports and follow-up work.
Connection setup and permissions
Use the version-specific SampleManager REST API. Confirm API authentication, result mappings and the instrument/CDS interfaces installed at your site.
This is an API integration option to scope and implement, not a ready-made Seal connector. Start with read access; any source-system changes need separately configured actions and controls.
What could neil do with Thermo Scientific SampleManager?
Once the relevant API access and data mappings are configured:
- Prepare a laboratory investigation
- Collect the selected sample’s results and the available instrument references.
- Check a result transfer
- Compare supplied instrument outputs with recorded results, units and identifiers.
- Assemble batch evidence
- Collect the laboratory records needed for a source-backed batch-review brief.
Connection questions.
Will this work with our Thermo Scientific SampleManager environment?
We check your product edition, API availability, authentication and permitted records against the job you want neil to do. The linked provider documentation describes the interface; it does not mean a connection is already installed in Seal.
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require 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.