A LIMS quote often has a line that reads “instrument integration,” followed by a number or by nothing at all. That line hides most of the technical risk in the project. It can describe a parser that reads a text file from a shared folder, a custom serial interface written for one balance, or a full capture layer that archives every file your chromatography systems produce. These are different products with different maintenance burdens, and a buyer who does not ask which one is being sold finds out during implementation.
This guide sets out the connection methods vendors describe in their own material, what the two regulatory texts most labs are held to say about data exchange, and a list of questions that turn a vague line item into a commitment. It does not rank vendors. It is a checklist for the stage after you have a shortlist, and it pairs with our guide to running a LIMS proof of concept, which is where most of these checks should be tested.
Four ways data gets from an instrument to the LIMS
Vendors rarely name a single method. LabWare’s product page says it has “highly flexible capabilities for instrument interfacing including direct network connections,” and lists instrument file parsing, web services and direct database connections as further options (accessed 22 October 2026). The page gives balances, pH meters and titrators as examples and names integration modules for Waters Empower and Agilent OpenLab. It gives no detail on how any of these are built or validated, which is normal for a marketing page and is the reason to ask for the technical documentation.
An implementation partner’s description of STARLIMS shows the same split from the practical side. In a post dated 19 October 2018, Astrix describes two main routes. The first is the SDMS “Grabber,” which “watches a targeted networked folder for any new exported instrument files,” uploads them to the repository and then parses them. The second is a custom interface for simpler devices such as pH meters and balances, reading COM or TCP/IP streams directly. The post is more than eight years old and STARLIMS has changed since, so read it as an illustration of the two patterns and not as a statement of the current product.
| Method | How it works | Typical fit | Main trade-off |
|---|---|---|---|
| File parsing | A watcher picks up an exported file; rules extract the fields | Instruments and software that can export text, CSV or reports | Depends on the export format staying stable; each change to the export can break the parser |
| Direct serial or network connection | The LIMS reads the device stream or sends commands | Simple devices such as balances, pH meters | Per-device scripts to write and maintain; mostly supports result entry (Astrix, 2018) |
| SDMS capture, then parse | Native files are archived first, then data is extracted | Complex instruments and chromatography systems | Another system to validate and operate; the archive and the LIMS must stay linked |
| Web service or system-to-system link | LIMS exchanges data with the instrument software or a data system | Enterprise chromatography and data systems | Needs a supported interface on both sides; version upgrades on either side can affect it |
The CASRAI dictionary definition of an SDMS is useful here because it comes from a neutral glossary and not from a vendor. It describes an SDMS as software that “automatically captures, indexes, and archives electronic data files,” that connects through file-watcher agents, direct instrument drivers or network folder monitoring, and that keeps files “in their original native format.” The practical point is that a converted PDF or a summary table cannot be reprocessed later, while the native file can.
What the regulations ask of an interface
Neither Annex 11 nor 21 CFR Part 11 prescribes a connection method. Both ask for outcomes, and a vendor answer should be judged against those outcomes.
Annex 11 (January 2011) says in clause 5 that systems exchanging data electronically with other systems “should include appropriate built-in checks for the correct and secure entry and processing of data.” Clause 6 asks for an extra accuracy check on critical data entered manually, done “by a second operator or by validated electronic means.” Clause 7.1 asks that stored data be checked for “accessibility, readability and accuracy.” Clause 9 asks that, based on a risk assessment, the system record GMP-relevant changes and deletions in an audit trail that is available, intelligible and regularly reviewed.
Section 11.10 of 21 CFR Part 11 is framed similarly. It asks for validation of systems “to ensure accuracy, reliability, consistent intended performance” (11.10(a)), the ability to generate accurate and complete copies of records (11.10(b)), secure, time-stamped audit trails where “record changes shall not obscure previously recorded information” (11.10(e)), and device checks to determine “the validity of the source of data input or operational instruction” (11.10(h)).
Read together, these texts give four questions to put to any integration method:
- Is the exchange checked? A parser that silently drops a malformed line is a data integrity problem.
- Is the original record kept and linked to the parsed result?
- Is every change to a transferred value traceable, including edits made after import?
- Is the parser itself under change control and validated for its intended use?
Annex 11 is also under revision. The draft published for consultation in July 2025 is longer and more specific on suppliers and audit trails, and the 2011 text remains the one in force at the time of writing. Our Annex 11 revision guide tracks the draft.
Ten questions that turn a line item into a commitment
Put these in writing to every vendor on the shortlist, per instrument model, and keep the answers for the validation file.
| # | Question | A usable answer | A warning sign |
|---|---|---|---|
| 1 | Which method will each of our instruments use? | A named method per model, with a reference site | “We integrate with everything” |
| 2 | Is the interface configuration or custom code? | Configuration screens, with scripts documented where used | Code that only one consultant understands |
| 3 | Who writes the parser and who maintains it? | A named party and a stated response time | Unclear ownership after go-live |
| 4 | What happens when the instrument software is upgraded? | A tested upgrade path or a change procedure | “Contact support” |
| 5 | Is the native file kept and linked to the result? | Yes, with retention controls | Only parsed values stored |
| 6 | How are malformed or partial files handled? | Rejected with an alert and a log entry | Silent skip or partial import |
| 7 | Can imported values be edited, and is it audited? | Edits require a reason and appear in the audit trail | Edits overwrite the imported value |
| 8 | What validation evidence do you supply for the interface? | Test scripts and a traceability matrix we can reuse | “Validation is the customer’s responsibility” with no support |
| 9 | What is the price, and is it per instrument or per parser? | A written figure with the assumptions | “Depends on scope” with no range |
| 10 | Can we test our own instrument and file in a trial? | Yes, with our real output | Only the vendor’s sample files |
Question 9 deserves a word. We found no public price list for instrument integration from any of the vendors reviewed for this guide, and Astrix says only that integration “can be a complex and time-consuming process” that can lead to project time and cost overruns without careful planning. Treat any quoted figure as the start of a scoping discussion.
What to test, and what it costs you
The most reliable check is the one in your own trial: bring a real file from your most awkward instrument, including a bad one, and watch the system process it. Our proof of concept guide lists instrument integration among the items worth a written pass/fail criterion. A good one is specific, for example “this chromatography export loads with all named fields mapped, and a truncated copy is rejected with a visible error.”
Astrix suggests assessing an instrument before integrating it: how often it is used, how critical its results are, how much time the integration would save scientists, its contribution to data integrity, and whether the instrument’s PC can reach the network. That is a sound filter. It also means the honest answer for some instruments is not to integrate them at first. An instrument used twice a week for a non-critical measurement may cost more to connect and revalidate than it saves, and a second-person check on manual entry, as Annex 11 clause 6 allows, can be the proportionate control.
The trade-off runs the other way too. Manual transcription is the risk that integration exists to remove, and for high-volume or critical results a validated interface is usually cheaper than the errors it prevents. We cannot put a number on that without data from your lab, and we did not find a neutral study that does.
For labs working to ISO 17025, the interface also feeds the evidence an assessor will ask to see, which we cover in ISO 17025 and LIMS. The validation work for the interface belongs in the plan described in LIMS Validation Explained.
What we could not verify
Several limits apply to this guide. LabVantage’s online documentation pages for instrument connections returned errors when we tried to read them, so we do not describe LabVantage’s approach. The Anton Paar application report on middleware refused our request, so we draw no conclusion from it. We did not read G2 or Capterra reviews of integration experience, so we make no claim about user satisfaction with any vendor’s interfaces. The only vendor-specific implementation detail here comes from a partner post from 2018. If your shortlist includes products we have not covered, the ten questions still apply.
For a French-language explanation of the archive layer, the sister site covers the SDMS.
The bottom line
Before you sign, convert “instrument integration” into a table with one row per instrument model: the method, the party who maintains it, the validation evidence supplied, the treatment of the raw file and a price. Test the hardest row in your own trial. Regulations ask for checked exchange, accurate records and traceable changes, and a vendor who can show each of the three for your instruments has answered the question that matters.
This site is editorially independent. Labsoftwareguide.com is not paid by LabWare, STARLIMS, Astrix or any other party named here for placement, favorable coverage or link inclusion, and no vendor reviewed this piece before publication.
FAQ
What does LIMS instrument integration actually mean?
It means a defined route for results to move from an instrument or its control software into the LIMS without retyping. The route can be a direct connection, a parser that reads an exported file, a capture tool that archives files first, or a web service. Vendors use the same phrase for all of them, so ask which one applies to each instrument.
Is file parsing less compliant than a direct connection?
Not by itself. Neither Annex 11 nor 21 CFR 11.10 names a connection method. They ask that exchanged data is checked, that records are accurate and complete, and that changes are traceable. A parsed file can meet that if the parser is validated and the original file is kept. A direct connection that overwrites results without a trail would not.
Who should maintain instrument parsers after go-live?
Decide it before signing. Some labs rely on the vendor’s services team, some on a partner, some on a trained in-house administrator. Each choice has a cost, and each parser change in a regulated lab triggers a change-control and often a re-test. Put the responsibility and the response time in the contract.
Should the LIMS store the raw instrument file?
In most regulated settings you want the original file retained and linked to the result, because a result table cannot be reprocessed. Capture tools that archive files in their native format are designed for this. If the LIMS only stores the parsed values, ask where the raw files live and who controls retention.
Can a small lab skip most of this?
Partly. If your instruments are a few balances and pH meters that output simple text, the integration work is small, and a short demonstration with your own devices is a reasonable check. The questions in this guide matter most once you add chromatography systems, plate readers or anything that exports complex reports.
Sources
- LabWare LIMS: Laboratory Information Management Systems for Enterprises Large & Small (accessed 2026-10-22)
- Integrating Instruments with Your STARLIMS System (Astrix, 19 October 2018) (accessed 2026-10-22)
- Scientific Data Management System (SDMS), CASRAI dictionary (accessed 2026-10-22)
- EudraLex Volume 4, Annex 11: Computerised Systems (January 2011) (accessed 2026-10-22)
- 21 CFR 11.10, Controls for closed systems (eCFR) (accessed 2026-10-22)
