Laboratory Software by Industry
Sandorian builds and integrates software around your existing LIMS - covering customer request intake, sample registration, certificate delivery, and every workflow your LIMS does not handle. We work with testing, calibration, diagnostic, and clinical laboratories operating under ISO 17025:2017, ISO 15189:2022, and EU IVDR 2017/746. Select your lab type below to see the specific gaps we address.
The four lab types Sandorian builds software for:
- Testing laboratories - request intake to signed report delivery under ISO 17025
- Calibration laboratories - certificate generation, traceability chains, and eIDAS-sealed portals under ISO 17025
- Diagnostic laboratories - IVD workflow tracking and IVDR-aligned documentation
- Clinical laboratories - patient-facing result delivery and document control under ISO 15189
Why your LIMS is not the whole answer
A Laboratory Information Management System (LIMS) does one job well: it manages sample data and test results inside the lab. What it does not own is everything on either side of that - the moment a customer submits a request, the registration handoff between intake and analysis, and the delivery of a signed report or sealed certificate back to the customer. Those gaps are real, they carry compliance risk, and no LIMS vendor closes them for you.
We do not replace your LIMS. We build what it leaves out.
Our custom software for laboratories sits around your existing system, not inside it. That distinction matters for regulated labs, because replacing a validated LIMS triggers a full revalidation cycle. We spare you that.
Four lab types, four distinct software gaps
Lab software by lab type is not a one-size-fits-all problem. Testing labs lose time on manual report assembly. Calibration labs struggle to deliver traceable certificates with proper uncertainty documentation. Diagnostic labs face IVDR documentation requirements their LIMS was never designed to produce. Clinical labs need patient-facing workflows and ISO 15189-compliant document control that sits entirely outside sample management. Each section below names the gap and the concrete work we do to close it.
Testing laboratories: from request intake to signed report
The workflow gap testing labs face
In a testing laboratory operating under ISO 17025:2017, the work starts before the LIMS ever opens. A customer submits a request, the lab reviews the contract scope, confirms methods and turnaround times, and registers the sample - all steps the LIMS expects to have already happened. When those steps run on email threads and paper forms, errors accumulate: missed scope items, wrong methods assigned, and delayed starts. At the output end, reports are often assembled manually from LIMS exports and sent by email with no audit trail.
Our article on ISO 17025 software requirements covers exactly what the standard demands from the surrounding software layer - worth reading before you scope any build.
What Sandorian builds for testing labs
We build intake portals that capture the customer request, enforce contract review steps, and hand a confirmed, registered sample record to the LIMS in a structured format. At the output end, we generate signed reports and deliver them through controlled channels. Every step produces an audit trail that supports accreditation review under ISO 17025. The full scope of what this looks like in practice lives on our testing laboratory software page.
Calibration laboratories: certificates, traceability, and ISO 17025
The workflow gap calibration labs face
A calibration certificate is not just a document - it is a traceability claim. It must record the reference standards used, their own traceability to national or international measurement standards, the measurement uncertainty, and the environmental conditions at the time of measurement. Most LIMS platforms generate a partial certificate at best. The traceability chain, the uncertainty budget, and the customer-accessible delivery portal are typically left to spreadsheets or PDF workarounds.
What Sandorian builds for calibration labs
We build certificate generation modules that pull traceability data from the LIMS, attach uncertainty documentation, and deliver the finished certificate through an eIDAS Regulation (EU) No 910/2014-compliant sealed portal. The customer receives a tamper-evident, legally binding document. The lab retains a complete audit trail. Accreditation bodies such as the Dutch RvA, Belgian BELAC, and German DAkkS can access the controlled records they need without the lab manually assembling evidence packs. See the full build scope on our software for calibration labs page.
Diagnostic laboratories: workflow automation for IVDR-ready labs
The workflow gap diagnostic labs face
The EU In Vitro Diagnostic Regulation 2017/746 raised the documentation bar for diagnostic laboratories considerably. IVDR-readiness is not a LIMS feature - it is a documentation and traceability discipline covering IVD workflow tracking, performance evaluation records, post-market surveillance data feeds, and audit-ready records for each test system. Standard LIMS platforms were not designed with IVDR in mind, and most diagnostic labs carry that gap as an open compliance risk.
Our knowledge base article on building regulated software for IVD laboratories explains the architecture decisions that make an IVD workflow auditable. Our IVDR compliance roadmap for laboratory software maps the specific documentation layers your software stack needs to cover.
What Sandorian builds for diagnostic labs
We delivered IVDR-aligned workflow software for ViroVet, a veterinary diagnostic laboratory. The project replaced a manual, paper-heavy process with a structured digital workflow - resulting in an 80% reduction in manual errors. The full story, including architecture decisions and outcomes, is on the how ViroVet digitized its lab operation page. Our diagnostic lab workflow and IVDR software page covers what a standard diagnostic lab engagement includes.
Clinical laboratories: patient-facing processes and ISO 15189
The workflow gap clinical labs face
ISO 15189:2022 governs medical laboratory quality and competence. Its requirements go well beyond sample management: referring physician workflows, patient result delivery, document control, and the traceability of amendments to reported results all fall within its scope. A LIMS handles the analytical side; it rarely handles the controlled delivery of results to clinical users or the document versioning that ISO 15189 requires for pre-analytical and post-analytical processes.
What Sandorian builds for clinical labs
We build the patient-facing and clinician-facing layer that your LIMS was not designed to own - result delivery portals, amendment logs, and document control workflows that satisfy ISO 15189 and software validation requirements. Every record is versioned, every delivery is logged, and the audit trail covers the full cycle from request receipt to reported result. The full scope lives on our medical laboratory software built for ISO 15189 page.
The layer every lab type shares: what a LIMS leaves out
Software for regulated laboratories needs to cover three areas that no LIMS vendor owns by default.
Request intake and sample registration
Before the LIMS can do its job, a customer must submit a request, the lab must review and accept the scope, and the sample must be registered with the right method, turnaround expectation, and customer reference. That entire pre-analytical sequence happens outside the LIMS. When it runs on email and paper, errors accumulate - wrong methods assigned, samples registered without confirmed scope, contract terms never formally accepted. A structured intake system closes that gap at the source.
Signed and sealed output delivery
At the other end of the workflow, the LIMS produces a result. Turning that result into a customer-deliverable - a signed report, a sealed certificate, or a structured data feed - is not a LIMS function. It requires document generation, signature or seal application, controlled delivery, and proof of receipt. For calibration labs, eIDAS-compliant sealed certificates are a legal expectation in many European procurement contracts. For testing and clinical labs, signed outputs with a complete audit trail are a core accreditation requirement.
Audit trails and controlled records
ISO 17025:2017, ISO 15189:2022, and EU IVDR 2017/746 each require that the software surrounding the analytical process maintains controlled records, supports deviation management, and produces an audit trail that an accreditation body can review. Our article on audit-ready lab software maps exactly what "audit-ready" means in practice for each of these standards.
Here is how that breaks down across the LIMS boundary:
| Layer | Covered by LIMS? | Covered by Sandorian? |
|---|---|---|
| Sample data and test results | ✓ | - |
| Customer request intake | ✗ | ✓ |
| Sample registration handoff | Partial | ✓ |
| Certificate / report generation | Partial | ✓ |
| eIDAS-sealed delivery | ✗ | ✓ |
| Audit trail for accreditation | Partial | ✓ |
How Sandorian has delivered across regulated lab segments
ViroVet: 80% reduction in manual errors through lab digitization
ViroVet is a veterinary diagnostic laboratory that came to us with a fully manual, paper-driven workflow running alongside a LIMS that could not connect to its customer-facing processes. We designed and built a structured digital workflow that bridged intake, sample registration, and result delivery into a single traceable system. The outcome: an 80% reduction in manual errors. Read how ViroVet digitized its lab operation for the full technical and operational breakdown.
Laboratory workflow software delivered under ISO 17025, ISO 15189, IVDR, and eIDAS
Sandorian has delivered ISO 17025 and ISO 15189 lab software across all four lab types covered on this page, under their respective standards. Our engineering team brings direct experience with the accreditation-aware build methodology that regulated labs require - meaning every design decision is made with the audit trail, the validation record, and the accreditation body's perspective in mind. We are based in Rijen, Netherlands, so European regulatory context is not an afterthought for us; it is the default.
Accreditation note: Software can support the conditions required by ISO 17025, ISO 15189, and EU IVDR 2017/746 - but conformity with those standards is assessed and awarded by the relevant accreditation body, not by your software vendor. We build software that makes a strong accreditation case. Whether your lab achieves accreditation is the accreditation body's determination.
Choose your laboratory type
Not sure which category fits your lab? Reach out through sandorian.com with a brief description of your workflow and the standards that apply. We will tell you in plain terms whether it fits what we build - and if it does, what a scoping call looks like.
If you want to understand what a project costs before booking that call, our page on what lab software projects cost gives honest range guidance.
Book a scoping call about your lab's workflow gap
Frequently asked questions
Do you replace our LIMS?
No. Sandorian builds software around your existing LIMS, not in place of it. Replacing a validated LIMS triggers a full revalidation cycle - an expensive and time-consuming process your lab does not need. We build the intake, registration, certificate, and delivery layers your LIMS leaves uncovered, and we integrate with your existing system through its API or database layer.
Which lab types do you work with?
We work with testing laboratories, calibration laboratories, diagnostic laboratories, and clinical laboratories - specifically those operating under ISO 17025:2017, ISO 15189:2022, EU IVDR 2017/746, or combinations of these. Each lab type has a dedicated page on this site with the specific workflow scope we cover.
Can you build software for a lab type not listed here?
Yes, in many cases. The four lab types above cover our primary delivery track record, but the underlying architecture - intake, registration, controlled output delivery, audit trail - applies to other regulated laboratory contexts. Contact us with your workflow description and the applicable standards and we will give you a direct answer.
Does your software make us compliant with ISO 17025 or ISO 15189?
Software can create the conditions that support compliance - structured records, audit trails, controlled document delivery, and deviation tracking. Whether your lab is compliant with ISO 17025:2017 or ISO 15189:2022 is a determination made by your accreditation body, not by your software vendor. We build software that gives your lab the strongest possible evidence base when that assessment happens.
Sources
Let's talk
We build the systems that power your business. Let us know how we can help.
Book a 30-min Call