Home / Insights / Buying

Alternatives to a full LIS for small labs and clinics

BuyingPublished 2026-11-189 min readInternational

An enterprise laboratory information system is built for hospital labs with many departments and many users. A clinic with two analysers, or a private lab with a defined test menu, often needs less, but still needs more than a spreadsheet. This guide lays out the realistic alternatives, what each is good at, and where each falls short.

Written and reviewed by the Catenix team. How these guides are written and checked.

In brief

  • EHR lab module: fine for ordering and filing results, weak on analyser connectivity, QC and lab audit.
  • Lab middleware platform: connects analysers, files QC, holds results on failure, reviews, reports and delivers to the EHR; often all a small lab needs.
  • Small-lab LIS product: a cut-down LIS, sometimes cloud based; check analyser drivers, QC depth and pricing model.
  • Reference lab portal: no in-house testing software needed, but no in-house testing either.
  • Catenix is a lab middleware platform that many clinics and small labs use instead of a full LIS, priced per site with no per-test fees.

Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).

Option 1: the EHR's lab module

Many EHRs include lab ordering, result filing and sometimes manual result entry for in-house tests. For a handful of waived or point-of-care tests read by eye, that may be enough.

Where it falls short: most EHR lab modules do not talk to analysers directly, so results are typed; QC is rarely linked to patient results; operator competency and instrument records live elsewhere; and the audit trail is designed for clinical records rather than lab inspection. As soon as you run a moderate complexity analyser, these gaps matter.

Option 2: a lab middleware platform

Middleware connects to each analyser in its own protocol, matches results to orders, files QC with Levey-Jennings charts and Westgard rules, holds results when QC fails or an operator is not authorised, and delivers results to the EHR. Platforms that have grown beyond pure middleware also handle registration, review and release, branded reports and billing.

Where it shines: fast connection of analysers, inspection-ready QC and audit, quick implementation, and pricing that suits small sites. Where to check: microbiology, blood bank and histology are usually out of scope, so a lab offering those needs a specialist system. See what lab middleware does.

Option 3: a small-lab LIS product

Several vendors sell LIS products aimed at small and mid-size labs, many cloud based. They cover the core LIS workflow and some include billing for US labs.

Where to check: whether each of your analysers is supported natively or needs separate middleware; how deep QC goes and whether it can hold results; whether pricing is per test, per user or per interface; and how long implementation takes. Ask the questions in our LIS requirements checklist.

Option 4: send everything to a reference lab

If testing volume is low or turnaround is not critical, sending samples to a reference lab removes the need for in-house lab software. The reference lab's portal or interface delivers results to your EHR. The cost is margin per test and turnaround time, and you give up control of the patient experience.

Many clinics combine options: urgent or high volume tests in house on connected analysers, specialist tests to a reference lab, all results visible in one record.

Side by side

EHR lab moduleLab middleware platformSmall-lab LISReference lab
Analyser connectivityRareCore strengthVaries, sometimes via middlewareNot needed
QC linked to resultsRareYesVariesNot your responsibility
Competency and auditLimitedYesVariesNot your responsibility
Reports and deliveryInside the EHRBranded reports and EHR deliveryYesThrough the lab's route
ImplementationAlready thereDays to weeksWeeks to monthsDays
Typical pricingIncluded or add-onPer sitePer test, user or interfacePer test

Three clinics, three choices

An urgent care group with point-of-care analysers at every site. It runs CRP, HbA1c, INR and urinalysis, and orders in its EHR. It does not need a LIS. Lab middleware that connects the analysers, holds QC and competency, and sends results into the EHR covers the work.

A private clinic with a small in-house lab. It runs chemistry, immunoassay and haematology analysers, serves its own patients and a few partner clinics, and wants branded reports and invoices. A middleware platform with registration, review, reports and billing covers it. A small-lab LIS is the alternative if it needs features such as complex referral workflows.

A specialist lab adding microbiology. Culture work, organism identification and susceptibility reporting are outside what middleware usually covers. It needs a LIS with a microbiology module, and middleware can still connect its analysers and hold QC.

Hybrid set-ups that work

Set-upHow it works
Middleware plus EHRMiddleware connects analysers and holds QC; results file into the EHR
Middleware plus reference labIn-house results from connected analysers; send-out tests through the reference lab's own interface
Middleware feeding a LISMiddleware handles analysers and rules; the LIS remains the record for a larger lab or network
Middleware now, LIS laterStart with middleware; if you outgrow it, point its standard HL7 or FHIR output at a new LIS

Common mistakes

  • Buying for the menu you might run in five years rather than the one you will run next year.
  • Leaving QC on paper because the EHR lab module has nowhere to put it.
  • Ignoring the EHR interface cost, which applies to every option except the EHR's own module.
  • Assuming a reference lab portal makes in-house testing unnecessary, when turnaround is the reason patients choose you.
  • Choosing without checking analysers by model. Use our analyser connection guides or the open connectivity dataset, or ask in ChatGPT or Claude through our AI assistant connector.

Questions to ask whichever option you consider

  1. Which of our analysers connect today, by model and protocol?
  2. Where are QC, competency and audit records kept, and can a QC failure hold results?
  3. How do results reach our EHR, GP or partner clinics?
  4. What does it cost over three years at our expected volume?
  5. How do we get our data out if we move to a different option later?

Comparing cost across options

The options are priced in different ways, so compare them on a three-year total for your expected volume. An EHR lab module may look free, but count the time spent typing results and keeping QC on paper. Middleware is usually a per-site or per-interface subscription. A small-lab LIS may charge per test, per user or per interface. A reference lab charges per test and keeps the margin you would earn in house. Add interface fees on the EHR side, implementation, validation time and hardware to each. Our guide to what a LIS costs includes a worked example.

What an inspector will ask, whichever option you choose

For any result tested in house, expect to show: the QC run before it and whether it passed, the operator and their competency at that date, the analyser and its maintenance status, who released the result and when, and the report as sent. If your chosen option cannot answer those five questions from one record, plan where the missing evidence will live before go-live.

How to choose

  1. List the tests you run in house now and plan to run in a year.
  2. List your analysers by model and protocol.
  3. Decide which inspections and accreditations you face.
  4. Identify where results must go: EHR, GP, partner clinics, patients.
  5. Shortlist options that cover all four without spreadsheets on the side.
  6. Compare three-year cost; see how much does a LIS cost.

Where Catenix fits

Catenix is a lab middleware platform for clinics and small labs. 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, files QC with Westgard rules, holds results when QC or competency fails, covers registration, review and release, branded reports and billing, and delivers results to athenahealth, eClinicalWorks and Epic over interfaces built to each vendor's published specification, and any record system that accepts a standard HL7 v2 or FHIR result. 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 goes live in days for supported analysers. Many small labs use Catenix instead of a full LIS; labs in a network use it to feed the LIS they already run. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device.

Questions people ask

Can a small lab operate without a LIS?

Yes, if its software covers registration, analyser connectivity, QC, review, reports, delivery and an audit trail. Many small labs use a middleware platform for this.

Is the EHR's lab module enough?

For a few manually read tests, often yes. Once you run connected analysers with QC and competency requirements, usually not.

What is the cheapest alternative to a LIS?

The one with the lowest three-year total for your volume, not the lowest first invoice. Per-site pricing tends to be cheaper as volume grows than per-test pricing.

Can Catenix work alongside a reference lab?

Yes. In-house results come from connected analysers, and reference lab results can be recorded against the same patient.

When does a small lab actually need a full LIS?

When it offers disciplines such as microbiology, blood bank or histology, runs many departments with dozens of users, or has referral and billing workflows that lighter products do not cover.

Can we start with middleware and move to a full LIS later?

Yes. Middleware that sends standard HL7 v2 or FHIR can later feed a LIS instead of the EHR, so the analyser connections and QC history carry on.

Is lab middleware cheaper than a LIS?

Often for a small lab, because implementation is shorter and per-site pricing does not rise with volume, but compare three-year totals at your own volume. A lab that needs microbiology or blood bank will need a LIS whatever the cost.

Sources and further reading

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.

We use your email only to send the guide and, if you ask, to follow up once. No newsletter unless you tick the box. See our privacy notice.

Thank you. The guide is on its way. You can also open it now.
That did not send. Open the guide directly or email contact@catenix.com.

See it done in software.

A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.