Cloud LIS for small and private labs: what to look for before you buy
Small and private labs used to choose between an expensive on-premise LIS and a spreadsheet. Cloud systems changed that, but they are not all built the same. This guide covers what a cloud LIS must do for a lab with a handful of analysers, how the analyser connection works when the software lives in a data centre, and the questions to ask before you sign.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- A cloud LIS keeps the database and screens in a data centre, but the analysers are still in your lab, so every cloud system needs a local gateway that speaks to the analysers and forwards results securely.
- The gateway should store and forward: if the internet drops, results queue locally and arrive later, in order, with nothing lost or duplicated.
- For a small lab the must-haves are registration, accession and barcodes, analyser connectivity, QC with Westgard rules, review and release, reports, EHR or GP delivery, and an audit trail.
- Ask how the vendor charges: per test, per user, per interface or per site. The model matters more than the headline price as your volume grows.
- Catenix runs as a cloud platform with an on-site edge gateway, priced per site with no per-test fees, used by clinics and labs in the UK and the US.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
Who this guide is for
This guide is for labs that run patient testing at modest scale: a private blood testing service opening its own lab, a fertility or endocrine clinic running hormone assays in house, an occupational health provider with a testing room, an urgent care group with chemistry and haematology on site, a specialty lab serving a network of clinics, or a physician office lab in the US. Typically there are one to ten analysers, a few scientists or technicians, and clinicians or patients waiting for reports.
Labs at this size have three things in common. They cannot afford months of implementation. They have no IT department to run servers. And they still face the same inspection questions as a hospital lab: show me the QC behind this result, show me who released it, show me that operator was competent.
How a cloud LIS reaches analysers in your lab
Analysers talk to a host computer over a serial cable or the local network, using ASTM E1381/E1394, HL7 v2 or POCT1-A2. A server in a data centre cannot open a serial port in your lab, and you should not open inbound firewall ports to let it try. So every credible cloud LIS installs something small on site: a gateway service on a lab PC or a small appliance.
The gateway does four jobs:
- holds the connection to each analyser in its own protocol
- sends outbound, encrypted connections to the cloud, so no inbound ports are opened
- stores results locally if the internet drops and forwards them in order when it returns
- logs every message so you can trace a result from the analyser to the report
Ask any vendor to show you what happens when the internet goes down mid-run. A good answer is a demonstration, not a slide. Catenix's edge gateway updates itself, integrity-checks each update before it installs, and keeps a durable local queue for exactly this reason. Analyser not on the list? We build the driver, usually within a couple of days. Our guide to connecting an analyser to a LIS explains the cabling and protocol side.
Must-have functions for a small lab
| Function | What good looks like |
|---|---|
| Registration and accession | Patient or client record, request, accession number and barcode label at reception |
| Analyser connectivity | Named drivers for each of your analysers, bidirectional where the analyser supports it |
| QC | QC runs identified automatically, Levey-Jennings charts, Westgard rules, lockout when QC fails |
| Review and release | Results held for review, flags and ranges visible, release recorded with user and time |
| Reports | Branded patient and clinician reports, corrected-report handling, delivery by portal, email or interface |
| EHR and GP delivery | HL7 v2 or FHIR to the requesting system; in the UK, routes into SystmOne, EMIS or private EHRs |
| Competency | Operator training and competency records that can block an untrained user |
| Audit trail | Every create, change and release recorded and tamper evident |
| Billing | Price lists, packages and invoices if you bill patients or corporate clients |
Nice-to-haves at this size include stock and lot tracking, temperature and maintenance logs, EQA records, dashboards and a patient app. Check which of these are included and which are extra.
Security and data residency
Health data in the cloud is normal now, but you must be able to answer your own data protection questions. Ask where data is hosted and whether you can choose the region; whether data is encrypted in transit and at rest; how access is controlled and whether multi-factor sign-in is available; how often backups run and how a restore is tested; and what certifications or assessments the vendor holds. In the UK, NHS-facing work also brings the Data Security and Protection Toolkit and DTAC. In the US, you need a HIPAA business associate agreement.
Hosting is arranged to meet your local data requirements, including in-country hosting where required. Data is encrypted in transit and at rest, and Catenix uses role-based access control and signs a business associate agreement for US customers. See our security page for detail.
Pricing models and what they mean for you
Cloud LIS pricing comes in a few shapes:
- Per test or per result: cheap at first, expensive as you grow, and it makes a busy month cost more.
- Per user: fair for small teams, but it can push labs to share logins, which breaks the audit trail.
- Per interface: each analyser or EHR link carries its own fee; adding an analyser becomes a budget decision.
- Per site: one subscription per location, with add-ons at fixed prices; predictable and easy to forecast.
Catenix uses the last model: a subscription per clinic or site, flat-priced add-on modules, and no per-test fees. Device drivers, updates and support are included. See how Catenix pricing works and our guide to what a LIS costs.
Ten questions to ask every vendor
- Which of our analysers do you already support, by model, and in which protocol?
- What happens to results when the internet drops?
- How are QC runs identified and filed, and can QC failure hold patient results?
- Who can release a result, and is release recorded per user?
- How do results reach our clinicians' EHR or the GP, and who pays for that interface?
- How are corrected results handled and sent on?
- Where is our data hosted, and can we export all of it in a standard format?
- What does implementation involve, and how long until the first real result?
- What is included in the price, and what is extra?
- What happens to our data if we leave?
What a good outage demonstration looks like
Ask the vendor to run this live, on a test analyser or a simulator:
- Start a run and disconnect the lab's internet connection at the router.
- Let several results complete while the lab is offline.
- Check the gateway screen or log shows the results queued locally, with a count.
- Reconnect and watch the queued results arrive in order, each one once, matched to the right patient and request.
- Open the audit trail for one of them and confirm it shows when the analyser sent it and when it reached the cloud.
If any result is lost, duplicated or filed against the wrong request, the gateway is not ready for clinical use. Also ask what happens if the lab PC restarts in the middle of a queue; a durable queue survives a restart. Before the demonstration, check whether your analysers appear in our analyser connection guides or the open connectivity dataset, so the vendor can run the test with a real driver rather than a simulated one.
Mistakes small labs make with cloud systems
Putting the gateway on a PC that is switched off at night. The gateway should run as a service on a machine that stays on, or on a small dedicated device. Analysers that finish overnight runs need somewhere to send results.
Leaving analysers on the guest Wi-Fi. Analysers belong on a wired or separated network, with the gateway the only device that talks to them.
Assuming cloud means no validation. You still validate every test, every analyser and every report layout before go-live, and again after significant changes.
Signing before seeing an export. Ask for a sample export file on day one, not on the day you want to leave.
Forgetting the bench. A screen that works on a large office monitor may be awkward on the small screen next to an analyser. Test with the people who will use it every day.
Where Catenix fits
Catenix is a cloud platform for clinics and small labs with an on-site edge gateway. It connects analysers over HL7 v2, POCT1-A2 and ASTM E1394, and sends HL7 v2 or FHIR R4 on to clinical systems, files QC with Levey-Jennings charts and Westgard rules, holds results when QC or operator competency fails, and keeps a tamper-evident audit trail aligned to ISO 15189:2022. It covers registration, accession numbers, review and release, branded reports, billing and dashboards, and sends 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, including SystmOne and EMIS Web through the NHS-approved routes, set up with your practice.
Many small labs use Catenix instead of a full LIS; larger networks use it to feed the LIS they already run. For analysers Catenix already supports, implementation is measured in days: install the gateway, point the analysers at it, confirm the first traced result, go live. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device.
Questions people ask
What is the best cloud LIS for a small lab?
The best fit is the one that already supports your analysers, files QC automatically, delivers results to the systems your clinicians use, and prices in a way that suits your growth. Use the ten questions above to compare vendors side by side.
Can a cloud LIS work if our internet is unreliable?
Yes, if the on-site gateway stores results locally and forwards them when the connection returns. Ask for a live demonstration of an outage.
Do we need an IT team to run a cloud LIS?
No server to run, but someone needs to own user accounts, the lab PC that hosts the gateway, and the network settings on each analyser. Most small labs manage this with the vendor's support.
Is a cloud LIS acceptable for ISO 15189 or CLIA?
The standard cares about what the system does, not where it runs. You need validated workflows, QC records, competency evidence, an audit trail and control over changes, all of which a cloud system can provide.
How long does it take to go live?
For a small lab with supported analysers, days to a few weeks, mostly spent on test set-up, report templates and validation. See implementation.
Does a cloud LIS need inbound firewall ports?
It should not. A well designed gateway makes outbound, encrypted connections only, so nothing on the internet can open a connection into your lab network.
Where does the on-site gateway run?
Usually as a service on a lab PC that stays switched on, or on a small dedicated device near the analysers. It needs a network path to each analyser, or a serial-to-network adaptor for older serial analysers.
Sources and further reading
Read next
More for coordinators.
Analyser connection guides
Step-by-step guides to connecting point-of-care and lab analysers to your LIS or EHR over HL7, POCT1-A2 and ASTM, with bidirectional, wire-level...
Read →LIS vs LIMS vs lab middleware
The difference between a LIS, a LIMS and lab middleware, in plain terms: who uses each, what they store, and which a clinic or small lab actually...
Read →How much does a LIS cost?
What drives the cost of a laboratory information system: licences, per-test fees, interfaces, implementation and support, and how to compare quotes.
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.