Home / Insights / Buying

How much does a LIS cost? The parts of the price and how to compare quotes

BuyingPublished 2026-11-1810 min readInternational

LIS quotes are hard to compare because vendors price different things. One quotes per test, another per user, a third per interface, and implementation may or may not be included. This guide breaks a LIS price into its parts, explains the common pricing models, and gives you a worksheet for comparing quotes on a three-year basis.

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

In brief

  • The licence or subscription is rarely the biggest cost. Interfaces, implementation and validation often outweigh it in year one.
  • Per-test pricing looks cheap for a new lab but grows with your volume; per-site pricing stays flat as you get busier.
  • Every analyser and every EHR link is a potential extra fee. Ask for each one by name in the quote.
  • Compare quotes on a three-year total, including staff time for set-up and validation, not on the first invoice.
  • Catenix is priced per clinic or site with flat add-on modules and no per-test fees; device drivers, updates and support are included.

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

The parts of a LIS price

Almost every LIS quote is made of the same building blocks, even when they are named differently:

Cost elementWhat it coversWatch for
Licence or subscriptionThe right to use the software, monthly or yearlyPer test, per user, per bed or per site basis
Analyser interfacesA driver for each analyser modelCharged per analyser, and again when you add one
EHR or GP interfacesOrders in and results out to clinical systemsFees on both sides: the LIS vendor and the EHR vendor
ImplementationSet-up of tests, ranges, reports, usersDay rates, travel, and who builds the test catalogue
ValidationProving the system works as intended before go-liveOften left to the lab; ask what the vendor provides
HostingServers or cloud capacityIncluded in cloud subscriptions; your cost on premise
Support and updatesHelp desk, fixes and new versionsResponse times, out-of-hours cover, version upgrade fees
TrainingInitial and new-starter trainingPer session or included
ExitGetting your data out at the endExport format and any extraction fee

Common pricing models

Per test or per result. You pay a small amount for every reportable result. It suits a lab with very low or uncertain volume. The catch is that your software bill rises with every new client, so the more successful you are, the more you pay, and budgeting a busy month is harder.

Per user or per seat. You pay for each named person. Fair for a small team, but it encourages shared logins when the team grows, and shared logins destroy the audit trail an inspector expects.

Per interface. The core system is priced low and each analyser and EHR link is charged separately. Adding an analyser becomes a purchase order rather than a configuration task.

Per site or per lab. A single subscription per location, sometimes with optional modules at fixed prices. Costs are predictable and do not move with volume. This is the model Catenix uses.

Perpetual licence plus maintenance. Common for on-premise products: a large upfront licence, then an annual maintenance fee, typically calculated as a share of the licence. You also own the servers, backups and upgrades.

Costs that are easy to miss

  • The EHR side of the interface. Some EHR vendors charge their own fee to accept lab results or send orders, separate from anything your LIS vendor charges. Ask your EHR vendor directly before you budget.
  • Serial device servers and cabling. Older analysers with RS-232 ports may need a small network adaptor. The hardware is inexpensive, but someone has to configure it.
  • Validation time. Your scientists will spend days running test messages, checking ranges and proving reports are correct. That is real cost even if no invoice arrives.
  • Report changes. Some vendors charge for every change to a report template. Ask whether you can edit templates yourself.
  • New analysers. Ask the price of adding an analyser in year two. It tells you a lot about the model.
  • Leaving. If export is a paid project, that cost belongs in your comparison.

A three-year comparison worksheet

Put every quote into the same table and add up three years. Use your own expected volume for each year, not today's.

LineYear 1Year 2Year 3
Subscription or licence
Per-test fees at expected volume
Analyser interfaces (each model)
EHR or GP interfaces (both vendors)
Implementation and training
Hardware and hosting
Support and upgrades
Staff time for set-up and validation
Total

Two quotes that look far apart on the first invoice are often close over three years, and the reverse is just as common. The worksheet makes the difference visible. Our ROI calculator helps you put a number on the time spent typing results today.

A worked example: three pricing models over three years

To see why the model matters more than the headline rate, take an illustrative lab. The figures below are invented round numbers chosen to make the arithmetic easy to follow, in any currency. They are not quotes from any vendor. The lab expects 1,500 reportable results a month in year one, 3,000 in year two and 4,500 in year three. It runs three analysers and adds a fourth in year two.

LineModel A: per resultModel B: per interfaceModel C: per site
Basis0.50 per result400 a month core, plus 150 a month per analyser900 a month, analysers included
Year 19,00010,20010,800
Year 218,00012,00010,800
Year 327,00012,00010,800
Three-year total54,00034,20032,400

Model A is the cheapest in year one and the most expensive by year three, because the bill follows volume. Model B steps up when the fourth analyser arrives, and would step again for each EHR link if those are priced the same way. Model C costs the most in year one and the least over three years. Now change one assumption: if volume stayed flat at 1,500 results a month, Model A would total 27,000 over three years and be the cheapest. That is the point of the exercise. The right model depends on your growth, so run the same arithmetic with your own forecast.

Then add the one-off lines: implementation, the EHR vendor's interface fee, hardware such as serial adaptors, and validation time. These are often similar across vendors, but not always. Where drivers for your analysers are included and implementation is remote, two of those lines shrink.

Why quotes for the same lab vary so much

Two quotes for the same lab can differ several times over, and the reason is usually scope rather than greed. One vendor includes analyser interfaces, hosting and implementation; another lists them as extras or leaves them out entirely. One quotes a one-year term, another a five-year term with the first year discounted. One includes out-of-hours support; another charges for it. Before comparing, rewrite every quote into the worksheet above, line by line, and send each vendor the same written questions:

  1. What exactly is included in the recurring price?
  2. What does adding an analyser cost, and adding an EHR or GP link?
  3. What happens to the price if our volume doubles?
  4. Are implementation and training fixed price or charged by the day?
  5. What is the cap on annual increases?
  6. What does a full export of our data cost at the end?

Common mistakes when budgeting

  • Forecasting at today's volume. If you expect growth, price it in; per-result models punish success.
  • Leaving out staff time. If two scientists spend five days each on validation, that is ten working days, whatever the invoice says.
  • Comparing different scopes. A cheap core with expensive interfaces can cost more than an all-inclusive subscription.
  • Ignoring the EHR side. The record system vendor may have its own fee and timeline.
  • Forgetting the drivers you do not have yet. Check which of your analysers already have connection guides, or look them up in our open analyser connectivity dataset, before you assume an interface is a quick configuration.

How Catenix is priced

Catenix is a subscription per clinic or site. The core platform covers analyser connectivity, device drivers, QC with Levey-Jennings charts and Westgard rules, results and review, reports, the audit trail, updates and support. Specialist modules that only some services need, such as billing or environmental monitoring, are flat monthly add-ons, listed openly, and available on any plan. There are no per-test fees, so a busy month costs the same as a quiet one, and adding an analyser that Catenix already supports is a configuration task, not a new contract.

Implementation is quick because there are no servers to install: an edge gateway goes on a lab PC, the analysers are pointed at it, the first result is traced end to end, and the lab goes live, usually in days. Full detail is on how pricing works.

Negotiating a LIS contract

Prices are rarely final on the first quote. Things that are reasonable to ask for: a fixed price for analysers already on the vendor's supported list; a cap on annual price increases; a free or fixed-price data export at the end of the contract; a defined go-live date with the vendor's obligations written down; and a short initial term or a break clause, so you are not locked in before you know the system works for you.

Questions people ask

How much does a LIS cost for a small lab?

It depends far more on the pricing model than on the size of the lab. Per-site subscriptions give a fixed monthly cost; per-test models start lower and rise with volume. Compare quotes over three years using the worksheet above.

Why are LIS interfaces so expensive?

Each analyser and each EHR speaks its own dialect, and someone has to build, test and support the translation. Vendors that already support your analysers should charge little or nothing extra for them.

Is a cloud LIS cheaper than on-premise?

Usually over three years, because there are no servers, backups or upgrade projects to fund. The monthly cost may look higher than an on-premise maintenance fee, but the total is often lower.

Does Catenix charge per test?

No. Catenix is priced per clinic or site, with flat-priced add-on modules and no per-test fees.

What should be included in a LIS quote?

Every analyser by model, every EHR or GP interface, implementation, training, validation support, hosting, support levels, upgrade terms and the cost of exporting your data at the end.

Are there free LIS options for small labs?

Some open-source and freemium systems exist, but the software licence is only part of the cost. Analyser interfaces, validation, hosting, support and your own staff time still apply, and an unsupported system can be hard to defend at an inspection.

What should I budget for an EHR lab interface?

Ask both sides. Your lab software vendor may include the interface, while the EHR vendor may run its own approval process and charge its own fee. Get both answers in writing before you compare quotes.

Why do two LIS quotes for the same lab differ so much?

Usually because they price different things. One includes interfaces, implementation and hosting; another lists them separately or leaves them out. Put both into the same three-year worksheet before you compare.

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.