Should compounds be mapped by name or CAS number?
A stable identifier such as CAS number or an agreed compound code is usually more reliable, with names kept for display. The laboratory's analysis list decides what the LIMS expects.
Integrations / GC-MS and LC-MS
GC-MS and LC-MS to LIMS integration.
Mass spectrometry panels can report dozens or hundreds of compounds per sample, each with qualifiers, surrogates, and internal standards. CTM scopes and builds interfaces that carry quantitation results into the LIMS with compound identity, units, and review flags intact.
What GC-MS and LC-MS exports usually look like
Quantitation software generally exports batch results as CSV, text, XML, or a vendor report format intended for LIMS transfer. A useful export includes the sample or data file name, the LIMS sample ID field, compound name and often a CAS number or compound ID, calculated amount and units, retention time, qualifier ion ratio results, internal standard response, surrogate recovery, dilution factor, and flags for manual integration or values outside calibration. The chosen export is fixed as part of the interface contract.
Compound identity and naming
Compound names drift between methods, software versions, and LIMS analysis lists: synonyms, isomers reported as a sum, abbreviations, and different capitalization. A mapping keyed on a stable identifier such as CAS number or an agreed compound code is more reliable than names alone. Compounds present in the export but not in the LIMS analysis for that sample are held for review, not added automatically.
Matching batch rows to LIMS samples
A mass spectrometry batch includes calibration levels, continuing calibration checks, method blanks, laboratory control samples, matrix spikes and spike duplicates, samples, and reinjections, often with prep or extraction suffixes. The interface needs a rule for each sample type and for extracting the LIMS sample ID. Anything ambiguous goes to a review queue with the reason.
Dilutions, extraction, and units
Reported concentrations may need to account for the instrument dilution, the extract final volume, and the sample weight or volume extracted. The contract states which values come from the instrument file and which from the LIMS prep record. Units such as ng/mL, µg/L, or µg/kg are converted only where the mapping says so, and non-detects are carried as qualifiers with the applicable limit rather than as zero.
QC, surrogates, and internal standards
Surrogate recoveries and internal standard responses are the first things a reviewer checks. The interface carries them with each sample, links batch QC such as method blanks, LCS, and MS/MSD where the LIMS supports that, and passes through the software's flags for failed qualifier ratios, calibration range exceedances, and manual integrations. Acceptance limits can be checked by the import if the laboratory documents them, but the decision stays with the reviewer.
Reinjections, re-extractions, and multiple results
A sample may be reinjected at dilution for a few compounds and reported from the original run for the rest, or re-extracted after a failed check. The mapping defines how the reportable result is selected per compound, how earlier results are kept, and who confirms the selection. Overwriting a reported value without review is not a default behavior.
Validating the mapping
Validation covers a full-panel batch, a partial dilution rerun, a surrogate failure, a manual integration flag, a compound missing from the LIMS analysis, and a renamed compound after a method update. Each imported value is compared with the quantitation output, including identity, units, qualifiers, and flags.
What CTM delivers
- A written mapping from the instrument export to LIMS analyses, units, qualifiers, and QC types.
- The parser or import component, tested against representative files outside production.
- Rules for sample matching, reruns, and exceptions, agreed with the people who review results.
- A validation record comparing imported values with the source export for normal and edge-case runs.
- A runbook and change triggers for software updates, template edits, and new analytes.
Related guides and services
Integration work usually sits inside a broader workflow question. The lab informatics service maps the sample-to-report path the interface must serve, and legacy LIMS stabilization covers older or inherited LIMS installations where an import must be added without disrupting what already runs. Labs using Clearline LIMS can review the Clearline LIMS guide to importing instrument results.
See the LIMS instrument integration overview for interface patterns and how an engagement runs, or another technique guide:
What shapes cost and timing
The number of instruments and export templates, how consistent sample naming is, QC and rerun rules, LIMS import options, and how much of the mapping is already documented.
Fees and schedule are proposed after fit and scope are confirmed; they are not fixed by this page.
Questions labs ask
How are manual integrations shown in the LIMS?
If the quantitation software exports a manual-integration flag, the interface carries it through so reviewers can see it alongside the result.
Can results from a dilution rerun be combined with the original run?
Yes, when the laboratory's method allows it. The mapping selects the reportable result per compound and keeps the other results as history or for review.
What about compounds found but not requested?
They are held for review rather than added automatically, unless the laboratory defines a rule for them.
Next step
Name the instrument, its software and version, what it exports today, the LIMS it needs to reach, and who owns failed imports. A redacted or synthetic example export helps more than a description.
Use the systems-need link on this page. Do not include credentials, regulated records, production exports, or client-sensitive material in initial intake.