Prepare a laboratory investigation. Use the permitted Thermo Scientific SampleManager records and show me the supporting evidence.
Once the records are shared with me, I’ll collect the selected sample’s results and the available instrument references.
Selected JSON resources from the REST services configured in your SampleManager release.
Prepare a laboratory investigation
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
1What’s connected.
Trace laboratory findings back to samples, tests and instrument results. Select the records to share in Seal, then reference them with @ in documents, comments and Neil.
Connection setup and permissions
Seal’s SampleManager binding reads approved REST resources and passes the JSON to your Scripts; it does not write to the LIMS. File Sweeper and instrument collection are separate interfaces.
SampleManager uses Seal’s configurable LIMS REST binding. It reads selected resources with GET requests and gives your Seal Scripts the complete JSON response. Mapping, entity creation, review and scheduling stay in those Scripts; the binding does not install a sample schema or write to the LIMS.
Supported authentication headers are Authorization, X-API-Key and apikey. Multiple headers, cookies, SOAP and request signing need additional native support or an approved gateway. Private or VPN-only addresses need a site-approved HTTPS gateway.
Set up Thermo Scientific SampleManager
- Ask the SampleManager administrator for the supported REST resource, its authentication and a read-only account scoped to the intended laboratory.
- Open Settings → Integrations → Thermo Scientific SampleManager. Enter the narrowest approved HTTPS API prefix, a relative test resource path and the authentication header, then choose Test and connect.
- Select the REST resources to share, choose Seal groups and grant access to the Seal API key used by the Scripts that map the responses.
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3What Neil can do with Thermo Scientific SampleManager once connected
Once the connection is set up and the records are shared:
- 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.
4Connection questions
Will this work with our SampleManager installation?
It works where your installation exposes a documented JSON GET service that Seal’s cloud can reach over HTTPS. A successful connection test shows connectivity and readable JSON, not analytical correctness, so compare representative responses with SampleManager before mapping them.
5Before it goes live.
Access
The organisation library reads only; it makes no changes in Thermo Scientific SampleManager. Define which records are shared and which Seal groups can read them.
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.