Agilent OpenLab CDS to LIMS integration

Make chromatography part of the complete sample story.

Seal gives the analytical result a home alongside sample preparation, specifications, the batch and any investigation. Configure the import once around the identifiers your lab uses, then let the workflow bring the evidence to the people who need it. A reviewer can follow a value back to the associated injection and report instead of searching several folders.

With those records connected, neil can help compare results and assemble a review brief with links to the underlying evidence. Your team keeps the analytical method and review decisions in view while spending less time collecting the material for the discussion.

With the records connected, try asking neil:

Compare the OpenLab assay results for this batch with the previous three batches. Show the injections, processing revisions and source reports behind any difference.

Choose the signal and the quantitative report deliberately.

Agilent documents a CSV export plugin for OpenLab CDS 2.x raw chromatograms. It runs after processing and lets the method owner choose the delimiter and destination. Reference chromatograms are excluded from that export. Quantitative reporting is a separate part of the handoff, so collect a representative report as well as the signal file.

For the Seal workflow, agree which reported fields should become searchable results: component, concentration, unit, qualifier and method revision, for example. Retain the corresponding source files with the injection. This gives the lab both a useful result table and a route back to the evidence used to create it.

Connect the injection to the right test.

Use the source system, result set and injection identity to find the receiving sample test. Keep the component and channel when they affect interpretation. A sample display name can appear in more than one project, and several injections can support one reported result.

Configure a Seal Script to resolve those references, check the agreed fields and create or update the appropriate result record. An unresolved sample goes to a visible work queue. Once resolved, the same mapping can be reused for later deliveries from the agreed export format.

Carry the analytical revision into batch review.

Retain the processing revision used for the reported value. Reprocessing can produce a new result from the same acquisition; the receiving workflow should retain that relationship and show which version supported the review. A repeat delivery of identical evidence should resolve to its existing result.

When another LIMS receives the values, agree the destination test codes, permitted result state and acknowledgement separately. Seal can connect the records around that exchange, giving laboratory and manufacturing teams a shared route from the batch to the exact analytical evidence.

Vendor references for this workflow

• Agilent OpenLab CDS 2.7: CSV export. Vendor reference for the chromatogram export plugin and its scope.

Test it with your data.

Use these cases to agree and test the connection’s behaviour. They are proposed acceptance checks, not completed tests or automatic connector features.

Check your system’s connection options.

Confirm the installed version, available exports and permissions. These pages cover the source interface and link to setup instructions.

• Agilent OpenLab CDSVendor documentation ↗
• LabWare LIMSVendor documentation ↗
• LabVantage LIMSVendor documentation ↗
• Seal Scripts

For configuration: Seal Scripts and local-file collection.

Build the workflow around your lab.

Start with a Seal blueprint, then connect the source evidence and records your team uses.

• Laboratory information management
• Scientific data management
• Analytical development