Integrations / ICP-MS and ICP-OES
ICP runs produce many results per sample: several elements, isotopes or emission lines, internal standards, and a dense pattern of calibration and QC checks. CTM scopes and builds the interface that moves those results into the LIMS with the right sample, analyte, units, and flags.
ICP-MS and ICP-OES software typically exports a report or data file per run or per batch, as CSV, tab-delimited text, or XML depending on the vendor template. Rows are commonly one per sample and element, or one per sample with a column per element. Alongside the concentration, the export may carry the isotope or wavelength, the measurement mode, internal standard recovery, relative standard deviation across replicates, the analyst's sample label, a dilution factor, and flags for over-range or failed checks.
The first job is to fix one export template and treat it as part of the interface. If analysts can change the template freely, the parser needs to detect and reject layouts it was not built for.
The sequence or sample list on the ICP is where matching succeeds or fails. The interface needs to know which field holds the LIMS sample ID, how prep or digest suffixes are written, and how QC positions are named. Typical rules include stripping a known digest suffix, recognizing a rerun marker, and refusing any row whose ID does not resolve to a sample that is ready for this analysis. Where analysts type sample labels by hand, importing the sequence from the LIMS worklist into the instrument software removes a common source of mismatches.
ICP-OES often measures an element at more than one emission line; ICP-MS may measure more than one isotope or use different collision or reaction modes. The mapping must say which line or isotope reports to which LIMS analysis, whether alternates are kept for review, and what happens when the preferred line is flagged. That decision belongs to the laboratory's method; the interface enforces it consistently.
Instrument concentrations are usually in solution units such as µg/L or mg/L. The reported result may need a dilution factor, a digestion final volume, and a sample mass or volume to reach mg/kg or mg/L in the original sample. The interface contract states where each factor comes from: the instrument file, the LIMS prep record, or both, and what happens when they disagree. Rounding and reporting limits are applied in one agreed place, not twice.
A typical ICP batch includes calibration blanks and standards, initial and continuing calibration verification, calibration blank checks, method blanks, laboratory control samples, matrix spikes and duplicates, and sometimes serial dilutions or interference check solutions. The interface recognizes each QC type from its label or position, links it to the batch in the LIMS where the LIMS supports that, and carries pass or fail flags and internal standard recovery so reviewers do not need to reopen the instrument software to see why a result is qualified.
Over-range results are commonly rerun at a higher dilution, and failed QC can trigger a rerun of a bracket of samples. The mapping needs explicit rules: which result becomes reportable, whether earlier values are kept as history, and who confirms the selection. By default, the import should stage reruns for review rather than silently overwrite an existing result.
Validation uses real run structures with non-sensitive or synthetic values: a normal batch, a batch with an over-range rerun, a failed continuing check, an unmatched sample label, and a changed export layout. Each imported value is compared with the source file, including units, dilution, flags, and the chosen line or isotope. The record of that comparison becomes part of the handoff.
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:
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.
Often, when the instrument software can produce a stable export and the LIMS accepts a file or API import. Feasibility is confirmed from the actual export and LIMS options before a build is proposed.
The laboratory decides which line or isotope is reportable for each analysis. The interface maps that choice explicitly and can keep alternates for review.
From the instrument file, the LIMS prep record, or both, as agreed in the interface contract. Disagreements are routed to review instead of guessed.
No. It carries the instrument's flags and values and can apply checks the laboratory has documented, but acceptance decisions remain with the laboratory's reviewers.
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.