LIS vs LIMS vs lab middleware: what each one does and which you need
Three acronyms that get used as if they mean the same thing. They don't. This guide explains what a laboratory information system, a laboratory information management system and lab middleware each do, where they overlap, and how to work out which one your clinic or lab needs.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- A LIS (laboratory information system) runs patient testing: orders, samples, results, review and reports for clinicians and patients.
- A LIMS (laboratory information management system) runs sample-centric work such as research, pharmaceutical, food or environmental testing, where the "customer" is a batch or a study rather than a patient.
- Lab middleware sits between analysers and the LIS or EHR. It speaks each analyser's protocol, applies rules, files QC and passes clean results on.
- Clinical labs and clinics almost always need LIS functions plus middleware, not a LIMS. Many small labs get both from one platform.
- Catenix is lab and point-of-care middleware that can also act as the working record for a clinic or small lab without a full LIS, or feed the LIS you already run.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
The short answer
If you test patients, you need LIS functions. If you test products, batches or research samples, you need a LIMS. If you have analysers that should send results to a computer without anyone retyping them, you need middleware, either as a separate product or built into whatever system you choose.
The confusion comes from vendors. Some LIMS products are sold into clinical labs, some LIS products call themselves LIMS for search reasons, and some middleware products have grown patient registration, reporting and billing until they cover most of what a small lab needs. So the useful question is not "which acronym" but "which jobs does this system do, and which jobs do I need done".
What a laboratory information system (LIS) does
A LIS is built around the patient and the request. Its core jobs are:
- Orders and requests: receiving a request from a clinician, an EHR or a walk-in, and turning it into tests to run.
- Accessioning and specimens: giving each sample an accession number and a barcode, and tracking it from collection to result.
- Worklists and instrument interfaces: telling analysers what to run and receiving results back, often through middleware.
- Review and release: letting a scientist check results against reference ranges, flags and QC before release.
- Reports: producing a patient report and sending it to the requesting clinician, the EHR or the patient.
- Billing and audit: recording what was done, by whom and when, and producing billing data.
Large hospital LIS products also handle microbiology, blood bank, histology and referral to other labs. A small private lab or a clinic with an on-site testing room usually needs only the core patient-testing jobs.
What a LIMS does
A laboratory information management system is built around the sample or batch rather than the patient. Typical users are pharmaceutical QC labs, contract research organisations, food and water testing labs, environmental labs and academic research groups. The core jobs are sample login, chain of custody, stability studies, specifications and pass or fail against them, instrument data capture, and certificates of analysis.
A LIMS can be configured for clinical work, and some vendors do this well, but it usually means building the patient, request and report model on top of a product designed for batches. If your customers are patients, start your search with LIS functions, not LIMS.
What lab middleware does
Middleware sits between the analysers and the system of record. It exists because analysers speak their own dialects: ASTM E1381/E1394, HL7 v2, POCT1-A2, or a manufacturer's own format, over serial cables or the network. Middleware handles that layer:
- connects to each analyser in its own protocol and keeps the connection alive
- matches results to the right order and patient using the specimen ID
- identifies QC runs and files them as QC, with Levey-Jennings charts and Westgard rules
- applies rules, such as holding a result when QC has failed or an operator's competency has lapsed
- translates results into what the LIS or EHR expects, usually HL7 v2 or FHIR
- keeps an audit trail of every message so you can show what the analyser sent and what was stored
In a hospital, middleware is usually a separate product from the LIS. In a clinic or small lab it is often the only system you need between the analyser and the EHR. Our guide to POCT middleware versus a LIS goes deeper on that point-of-care case.
Side by side
| LIS | LIMS | Lab middleware | |
|---|---|---|---|
| Built around | Patients and requests | Samples, batches, studies | Analysers and messages |
| Typical users | Clinical and private labs, clinics | Pharma QC, research, food, environmental | Any lab or clinic with connected analysers |
| Talks to analysers | Usually through middleware | Through instrument integration | Directly, in each analyser's protocol |
| Main output | Patient report to clinician or EHR | Certificate of analysis, study data | Clean, matched results and QC records |
| QC handling | Varies | Specifications and limits | Levey-Jennings, Westgard rules, lockout |
Which one do you need?
Work through these questions:
- Who is the result for? A patient means LIS functions. A product or study means LIMS.
- How many analysers, and do they connect? If results are typed in today, middleware is where the time and error savings are.
- Do you already have a system of record? A hospital or a lab network usually has a LIS or EPR already. Middleware should feed it, not replace it.
- Does a clinician order in an EHR? Then you need an orders and results interface, usually HL7 v2 ORM and ORU or a FHIR API. See how lab orders and results interfaces work.
- What will an inspector ask for? CLIA, CAP, UKAS or CQC inspections all want QC records, competency evidence and an audit trail. Whatever you choose must produce them without a spreadsheet on the side.
For a clinic with one to five analysers, or a small private lab, the most common answer is one platform that covers registration, orders, analyser connectivity, QC, review, reports and the audit trail. That is the space Catenix works in.
Mistakes we see when labs choose
Buying a LIMS for patient testing. A LIMS can store a result against a sample, but the patient record, the request from a clinician, the report layout and the delivery back to the EHR often have to be built as custom configuration. That work is slow and it is yours to maintain.
Buying a hospital LIS for a small lab. Enterprise LIS products are designed for hundreds of users and dozens of departments. A clinic with two analysers ends up paying for modules it never opens and waiting months for an implementation slot.
Forgetting the analyser interfaces. A LIS quote that does not list each analyser by model, with the protocol and who builds the driver, is incomplete. Ask for the list in writing, including what happens when you add a new analyser next year.
Keeping QC on paper. If QC lives in a binder while results live in software, nobody can prove that a patient result was released only after QC passed. Inspectors ask exactly that question. QC should sit in the same system as the results, linked by analyser, lot and time.
Ignoring the exit. Ask how you get your data out, in what format, and at what cost, before you sign. A system you cannot leave is a system you cannot negotiate with. Our guide to switching LIS vendor covers this in detail.
Three labs, three answers
A private GP clinic with two point-of-care analysers. It runs HbA1c and CRP on small analysers next to the consulting rooms, and patients are registered in the clinic's EHR. It does not need a LIMS, and a hospital LIS would be oversized. It needs middleware that connects the analysers, files QC and sends results into the EHR, or a platform that also produces the report if the EHR cannot.
A private lab with six analysers serving partner clinics. It receives requests from many organisations, accessions samples, runs chemistry, immunoassay and haematology, and sends branded reports to each client. It needs full LIS functions plus middleware. One platform that covers both is simpler to validate and support than two products joined by an interface.
A contract lab testing supplements for a manufacturer. Its customer is a batch with a specification and a certificate of analysis. That is a LIMS job, even if some of its instruments are the same models a clinical lab uses.
Questions to ask any vendor, whatever they call their product
- Which of our analysers do you connect today, by model, and in which protocol?
- Who builds a driver for an analyser you do not support yet, how long does it take and what does it cost?
- Can a failed QC run or a lapsed competency hold patient results automatically?
- Can you show us the raw analyser message behind any result?
- How do results reach our EHR, GP or partner clinics, and who builds each side?
- Is the patient and request model native, or configured on top of a batch model?
- How do we export all our data, in what format and at what cost?
If you want to check connectivity before you speak to anyone, our analyser connection guides list the protocol and interface notes for 130 analysers, the same facts are published as an open analyser connectivity dataset, and you can ask the question inside ChatGPT or Claude through our AI assistant connector.
Where Catenix fits
Catenix is lab and point-of-care middleware that grew into a full platform. It connects analysers over HL7 v2, POCT1-A2 and ASTM E1394, and sends HL7 v2 or FHIR R4 on to clinical systems, through an on-site gateway with store-and-forward, files QC with Levey-Jennings charts and Westgard rules, holds results when QC or competency fails, and keeps a tamper-evident audit trail aligned to ISO 15189:2022.
For a clinic or small lab with no LIS, Catenix can be the working record: patient registration, accession numbers, results, review and release, branded reports, billing and dashboards. For a lab network that already runs a LIS, Catenix feeds it. Analyser not on the list? We build the driver, usually within a couple of days. It is priced per site, with no per-test fees, and it is used in the UK and the US. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device.
Questions people ask
Is a LIS the same as a LIMS?
No. A LIS is built around patients and test requests and is used by clinical labs. A LIMS is built around samples and batches and is used by research, pharmaceutical, food and environmental labs. Some products cover both, but the starting design differs.
Do I need middleware if I already have a LIS?
Often yes. Many LIS products rely on middleware to talk to analysers, apply autoverification rules and file QC. Check whether your LIS has native drivers for every analyser you run.
Can a small lab run without a full LIS?
Yes, if the system it uses covers registration, orders, analyser connectivity, QC, review, reports and an audit trail. Many small labs use Catenix in place of a full LIS.
Which is cheaper, a LIS or middleware?
It depends on the pricing model more than the category. Ask whether you pay per test, per user or per site, and what interfaces cost. See how much a LIS costs.
Does Catenix interpret results?
No. Catenix handles connectivity, workflow and records. Reference ranges and comments on reports are content your lab writes, and clinical decisions stay with your clinicians.
Is lab middleware the same as an interface engine?
No. An interface engine is a general tool for routing messages between systems. Lab middleware is built for analysers, with drivers, QC handling and lab rules included. See interface engine vs lab middleware.
Can one system be both a LIS and middleware?
Yes. Several platforms, Catenix among them, combine analyser connectivity with registration, review, reports and billing. That suits clinics and small labs that do not want two products joined by an interface.
Sources and further reading
Read next
More for coordinators.
Catenix device connectivity
Bidirectional point-of-care device connectivity over HL7, POCT1-A2 and ASTM, with LIS/EHR integration and a self-healing edge gateway.
Read →Cloud LIS for small and private labs
What a cloud laboratory information system should do for a small or private lab: analyser connectivity, QC, review, reports, EHR links, security and...
Read →POCT middleware vs LIS
POCT middleware vs LIS explained: what each system does, where they overlap, three common architectures and a decision table by care setting.
Read →Take it with you
The buyer's guide, in your inbox.
Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.
Get the POCT connectivity buyer's guide
Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.
See it done in software.
A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.