Can one sample report ions from different injections?
Yes, if the laboratory's method allows it. The mapping names which injection reports each ion and keeps the others as history or for review.
Integrations / Ion chromatography
Ion chromatography to LIMS integration.
Ion chromatography results come out of a chromatography data system as peak tables and calculated amounts per injection. CTM scopes and builds the interface that turns those injections into LIMS results for the right sample, ion, reporting form, and QC context.
What IC exports usually look like
IC data systems generally export per-injection or per-sequence reports as CSV, text, or XML using a configurable report template. A useful export carries the injection name, the sample ID field, the component name for each identified peak, retention time, area or height, calculated amount, units, dilution factor, and any integration or calibration flags. Some templates put one ion per row; others put each ion in its own column. The parser is built for the agreed template and rejects layouts it does not recognize.
Matching injections to LIMS samples
An IC sequence mixes calibration standards, check standards, blanks, samples, duplicates, spikes, and reinjections. The interface needs a reliable way to tell them apart, usually from sample type fields or naming conventions, and a rule for extracting the LIMS sample ID from the injection name. Rows that do not resolve to a sample awaiting that analysis are held for review with the reason stated.
Ions, reporting forms, and units
Component names in the data system rarely match LIMS analysis names exactly, so the mapping lists each one. Reporting form matters for some ions: nitrate and nitrite may be reported as the ion or as nitrogen, and phosphate as the ion or as phosphorus. If the laboratory reports a different form from the one the data system calculates, the conversion is written into the mapping once, with the factor documented, rather than applied by hand. Units are usually mg/L; any change of units is explicit.
Dilutions and reporting limits
Samples are often diluted to bring major ions into range while minor ions are reported from a less diluted injection. That means one sample can have reportable results from more than one injection. The contract states which injection reports each ion, how dilution factors are carried, and how results below the reporting limit are represented, for example as a qualifier with the limit rather than a zero.
QC samples, blanks, and spikes
Typical IC QC includes calibration verification standards, continuing checks at a set frequency, method or reagent blanks, laboratory control samples, matrix spikes, and duplicates. The interface identifies each QC injection, links it to its batch where the LIMS supports it, and carries recoveries and flags. Unidentified peaks and retention-time shifts that the data system flags are passed through for review rather than discarded.
Reinjections and manual integration
Reinjections happen after failed checks, carryover, or out-of-range results. Manual integration may be used on difficult peaks. The mapping states which result becomes reportable, keeps earlier injections as history where the LIMS supports that, and preserves any manual-integration flag the data system exports so reviewers can see it.
Validating the mapping
Validation runs representative sequences with non-sensitive values: a clean batch, a batch with a split dilution, a failed continuing check followed by reinjection, a nitrate-as-nitrogen conversion, and an injection name that does not match any sample. Each imported value is compared with the data system output, including form, units, dilution, 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 is nitrate as nitrogen handled?
The laboratory chooses the reporting form. If it differs from what the data system calculates, the conversion factor is documented in the mapping and applied consistently by the import.
What happens to unidentified peaks?
They are passed through as flags or held for review according to the laboratory's rules. The import does not assign them to an analysis on its own.
Do we need to change our data system report template?
Sometimes. A small template change, such as adding a sample type or dilution column, can make matching far more reliable. Any change is agreed with the laboratory and recorded in the interface contract.
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.