LIMS integration and instrument middleware

Your LIMS doesn't need replacing. It needs connecting.

We build the software between your instruments, LIMS and business systems, eliminating manual handovers without disrupting validated workflows.

Discuss your integration gap

The problem is often around your LIMS

Replacing the core system is expensive, disruptive and often unnecessary. The missing piece is usually an integration, workflow or specialized module around it.

Instrument results still require manual entry

Critical workflows live in Excel, email or paper

LIMS data does not reach ERP, reporting or customer systems

What LIMS integration can connect

Most of the friction in a laboratory sits between systems rather than inside them. Integration closes those gaps:

Laboratory instruments to the LIMS

LIMS platforms to ERP, CRM and accounting systems

Sample workflows to customer and reporting portals

Legacy databases to modern applications

Manual spreadsheet and email workflows to validated software

Multiple laboratory systems through middleware and APIs

We work with the interfaces a system exposes: REST and SOAP APIs, database and file exchange, messaging standards such as HL7, and proprietary instrument protocols where the manufacturer documents them. Where an interface is supportable, we can usually build against it.

What Sandorian builds

The integration, middleware and custom software that sits around your LIMS and holds the workflow together.

Instrument-to-LIMS integrations

Capture results from instruments and push them into the LIMS with the right sample and test context, so nobody retypes a number.

Middleware between systems

A reliable layer between laboratory and business systems that keeps data moving and in sync instead of being exported and re-imported by hand.

Workflow automation around your LIMS

Automate the steps your LIMS leaves to people: intake, routing, review and release, built around the platform you already run.

Custom modules

Purpose-built functionality for the workflows an off-the-shelf LIMS does not cover, without forking away from the core system.

Data migration and legacy integration

Move data out of ageing databases and spreadsheets, or connect them to modern applications when a full migration is not worth the risk.

Monitoring and audit tooling

Operational tooling, audit trails and alerting so every automated handover is observable, traceable and safe to rely on.

Keep the systems that work

We connect and extend the systems you already rely on instead of defaulting to a full platform replacement. A new core system is the biggest, riskiest change a lab can make, and it rarely fixes the manual handovers that actually slow you down.

Read our guide: new LIMS or better workflow?
  • Preserving validated workflows
  • Avoiding unnecessary migration risk
  • Introducing changes incrementally
  • Keeping operational continuity
  • Replacing only components that are genuinely the constraint

Built for regulated laboratories

Integrations for accredited and diagnostic laboratories are developed with compliance in mind from day one. We build validation documentation, audit trails, change control and data-integrity checks into the work, not onto the end of it.

ISO 17025ISO 15189IVDRIEC 62304Audit trailsValidation documentationChange controlData integrity and traceability

Software supports your accreditation; it does not replace the audits, procedures and people that earn it. We are honest about that line.

My first engineering role was at TNO, the Netherlands' largest applied research organization. That is where I learned what labs need from the software between their systems: reliability, traceability, and no tolerance for data that changes on the way from an instrument to a report.

Sander van Hooft

Sander van Hooft

Founder, Sandorian

Experience with testing, calibration and diagnostic laboratories

Based in the Netherlands, focused on European laboratories

Works in English, German and Dutch

Long-term software maintenance and evolution

From integration gap to reliable workflow

Every engagement starts with a short assessment phase of two to four weeks to map the current systems and define the roadmap before a line of production code is written.

01

Map the current systems

We map the systems, data flows and manual handovers as they actually run today, not as the documentation says they do.

02

Identify the smallest reliable intervention

We find the one integration, workflow or module that removes the most manual work for the least disruption.

03

Build, validate and integrate

We build it with validation and traceability from the start, and connect it to the systems around it.

04

Monitor, maintain and evolve

We keep it observable and maintained, and extend it as instruments, systems and regulations change.

Frequently asked questions

Common questions from lab directors and IT managers with an active integration problem.

What is LIMS integration?

LIMS integration is the software work that makes your laboratory information management system exchange data with the systems around it: instruments, ERP and invoicing, customer portals, and reporting. Instead of results being typed over by hand or exported to spreadsheets, information flows automatically between the LIMS and the rest of your operation. It usually means building connectors, middleware or small custom modules rather than replacing the LIMS itself.

Can you connect laboratory instruments directly to our LIMS?

Often, yes. What is possible depends on what the instrument exposes: a documented API, a serial or file-based export, or a proprietary protocol. Where a manufacturer provides an interface we build middleware that captures results and pushes them into the LIMS with the right sample and test context. Where an instrument only produces files or printouts, we build the layer that parses and validates that output. We scope instrument connectivity honestly up front instead of promising it blindly.

Can we keep our current LIMS?

That is the starting assumption. Most laboratories do not need a new LIMS; they need the workflows and systems around it to connect. Replacing a validated core system is expensive and disruptive, and it rarely fixes the manual handovers that actually slow the lab down. We connect and extend the LIMS you already run, and only recommend replacing a component when it is genuinely the constraint.

Which LIMS platforms and instrument protocols can you work with?

We are platform-agnostic. We integrate with commercial and in-house LIMS platforms through whatever they expose: REST and SOAP APIs, database-level access, file exchange, and messaging standards such as HL7 where relevant. On the instrument side we work with vendor APIs, serial and file-based exports, and proprietary protocols where the manufacturer documents them. If a system has a supportable interface, we can usually build against it.

Can you integrate a LIMS with ERP or other business systems?

Yes. Connecting the LIMS to ERP, CRM, accounting and invoicing systems is some of the most common work we do. It removes the double entry between the lab and the back office: orders, samples, results and certificates on one side, quotes, invoices and customer records on the other. We build the middleware and APIs that keep both sides in sync.

How long does a typical LIMS integration take?

A focused integration between two systems that already exist typically takes 3 to 6 months. Connecting a full workflow, from customer request through sample handling to certificate and invoice, can take 6 to 12 months. We always start with a short assessment phase of 2 to 4 weeks to map the current systems, data flows and manual handovers before committing to a build.

How do you handle validation and auditability?

Integrations for regulated laboratories are built with validation documentation, audit trails, change control and data-integrity checks from the start, not added at the end. We work with the requirements of ISO 17025, ISO 15189, IVDR and IEC 62304, and we build traceability into the data flows so every automated handover can be reconstructed. Software supports your accreditation and compliance; it does not replace the audits and processes that grant it.

Do you work with laboratories outside the Netherlands?

Yes. We are based in the Netherlands and focused on European laboratories, and we work in English, German and Dutch. Our experience covers testing, calibration and diagnostic laboratories across Europe, and we build software for the long term, maintaining and evolving it as regulations and instruments change.

Looking beyond integration?

This page focuses on integration and middleware. For the full picture of the software we build for laboratories, including customer portals, sample workflows and reporting, start at our labs hub.

Custom software for laboratories

Find the missing piece in your laboratory workflow

Show us where data, instruments or systems stop connecting. We will help determine whether you need an integration, a workflow change or something more fundamental.

Discuss your integration gap