Home / Insights / Buying guide

Software for a clinic with on-site blood testing: a buying guide

Buying guidePublished 2026-11-1711 min readInternational

For founders and practice managers opening a clinic with benchtop analysers: the pieces of software you need, the four ways to provide them, what must be ready before go-live, a realistic setup plan and the questions to ask a vendor.

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

In brief

  • A clinic that runs blood tests on site needs software for eight jobs: analyser connection, patient and sample identification, a results store, clinical review and sign-off, branded patient reports, referral laboratory results, quality control with an audit trail, and stock.
  • There are four common ways to cover those jobs: manual entry, the analyser vendor's own software, a full laboratory information management system (LIMS), or a point-of-care testing (POCT) middleware or connected-diagnostics platform that sits across all the analysers.
  • Before go-live you need the analyser interface manuals, a working network, reference ranges approved by your clinical lead, user roles and a documented verification of each analyser.
  • A cloud platform can usually be set up in 2 to 6 weeks, and most of that time goes on clinical sign-off and analyser verification rather than software installation.
  • Ask every vendor where data is hosted, how it meets UK GDPR or HIPAA, how it charges (per site or per test), and which of your exact analyser models it has already connected.

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

What a clinic with on-site blood testing needs from software

A private, longevity, wellness, men's or women's health, occupational health or urgent care clinic that buys benchtop analysers is, in a small way, running a laboratory. A chemistry analyser, a haematology counter, an HbA1c (glycated haemoglobin) analyser, an immunoassay reader and a urine analyser each produce results that have to reach the right patient, be checked by a clinician, be reported and be kept. The software question is which system does each of those jobs, and whether they join up.

These are the pieces a new clinic needs, whichever product provides them:

  1. Analyser connection. Each analyser sends its results to software over a cable or the network, so nobody reads a screen and types a number. Analysers use standards such as HL7 v2 (Health Level Seven version 2), ASTM E1394 and POCT1-A2, or a vendor format.
  2. Patient and sample identification. The result must land against the right person. That means a patient record created before the sample is taken, and a sample identifier (usually a barcode label) that the analyser reads or the operator scans.
  3. A results store. One place that holds every result from every analyser, with the time, the device, the operator and the reagent lot, and that can show a patient's results over time.
  4. Review and sign-off. A clinician looks at the results before they are released. Results outside the reference range or above a critical limit are flagged for attention, and the sign-off is recorded against the person who gave it.
  5. Branded patient reports. A clear report, in the clinic's own branding, that the patient receives by email, portal or app, and that a referring doctor can read.
  6. Referral laboratory results alongside your own. Few clinics run every test in house. Results from the reference laboratory you send specialist tests to should sit in the same record and the same report as the in-house results.
  7. QC and audit trail. Internal quality control (QC) recorded every time it is run, charted and checked against rules, with a tamper-evident record of who did what and when.
  8. Stock. Reagents, controls and consumables tracked by lot and expiry, so that a recall or an expired lot can be traced to the results it produced.

Most clinics also have a clinical system for appointments, notes and billing: systems such as Semble or EMIS Web in the UK, and athenaOne or eClinicalWorks in the US. The results usually need to reach that system too.

The four options compared

There are four common ways to cover the list above. None is wrong for every clinic; they suit different volumes, budgets and ambitions. Product details change, so confirm current capabilities with each vendor.

OptionWhat it isStrengthsWeaknesses
Manual entryStaff read each result and type it into the clinical system or a spreadsheetNo software cost; can start on day oneTranscription errors, no QC record, no traceability of lots or operators, slow reporting, hard to defend at an inspection
Analyser vendor softwareThe data manager supplied with one manufacturer's analysersBuilt for those devices; often included with the analyserCovers one manufacturer only; a clinic with three makes of analyser has three systems; patient reports and referral results usually out of scope
Full LIMSA laboratory information management system designed for a hospital or commercial laboratoryVery complete for a high-volume laboratory, with accreditation featuresUsually sized, priced and staffed for a laboratory, not a clinic; long implementations; patient-facing reports and clinic workflow may need extra work
POCT middleware or connected-diagnostics platformCloud software that connects analysers from different manufacturers and manages results, QC, reports and stockOne system across all analysers; built for small sites; QC, audit trail and reports included; weeks rather than months to set upEach analyser model must be supported or interfaced; scope varies widely between vendors, so check each of the eight jobs

A clinic doing a handful of tests a week on one device can start with manual entry, but should plan to move off it. A clinic with several analysers, a clinician signing off results and patients who expect a polished report is usually best served by the fourth option. The comparison of POCT middleware and a LIS covers the difference in more depth.

What has to be in place before go-live

Software is rarely what delays a clinic's first patient. These five items are, and each belongs to the clinic rather than the vendor.

Analyser interface manuals

Every analyser has a host interface or LIS interface specification that describes how it sends results. Ask the analyser supplier for it at purchase, together with the settings for the communication port or network output. Without it, connection work stalls.

Network

Analysers connect by serial cable, USB or Ethernet. Decide where each one sits, provide wired network points or a small on-site gateway, and agree with whoever runs your IT that analyser traffic is allowed out to the cloud service. A gateway that stores results and forwards them when the connection returns protects you from internet outages.

Reference ranges approved by the clinical lead

Each test needs a reference range, by sex and age where relevant, and any critical limits. These come from the analyser manufacturer's instructions for use or your referral laboratory, and your clinical lead approves them in writing. The software holds and applies them; it does not choose them.

User roles

Decide who can register patients, run tests, run QC, sign off results, release reports and change settings. Each person needs their own login. Shared logins defeat the audit trail.

Verification of each analyser

Before the first patient result, show that each analyser performs as the manufacturer claims in your hands: precision, comparison with a laboratory method and, where relevant, the reportable range. The MHRA guidance Management and use of IVD point of care test devices expects this in the UK, and in the US the CLIA regulations at 42 CFR Part 493 set requirements depending on test complexity. The guide to verifying a new POCT analyser walks through the method.

A realistic 2 to 6 week setup plan

For a clinic with three to five analysers on a cloud platform, this is a realistic sequence. The short end assumes analysers already delivered and a clinical lead with time to review; the long end is more common.

WeekWorkOwner
1Account set up, site and users created, roles agreed, branding and report template drafted, analyser interface manuals collectedClinic manager with the vendor
1 to 2Network points and gateway installed, each analyser connected and test messages receivedVendor with the clinic's IT support
2 to 3Test menu built, reference ranges and critical limits entered, then approved by the clinical leadClinical lead
2 to 4QC material set up by lot, QC rules chosen, analyser verification runs completed and documentedSenior scientist or nurse lead
3 to 5Referral laboratory link and clinical system link configured and tested with dummy patientsVendor, referral laboratory, clinical system supplier
4 to 6Staff training and competency sign-off, dress rehearsal with dummy patients end to end, go-liveClinic manager

The step most often underestimated is the link to the referral laboratory and to the clinical system, because it depends on a third party agreeing to enable an interface. Start those conversations in week one.

Data protection and hosting

Blood results are health data, which is special category data under UK GDPR and protected health information under HIPAA (the US Health Insurance Portability and Accountability Act). The clinic is the controller, or the covered entity in the US; the software vendor is a processor, or a business associate.

  • UK clinics need a data processing agreement with the vendor, a data protection impact assessment for the new system, a clear answer on where data is stored and whether it leaves the UK, and registration with the Information Commissioner's Office (ICO). The ICO's Guide to the UK GDPR is the reference document.
  • US clinics need a business associate agreement signed before any patient data is loaded, and evidence of the vendor's safeguards under the HIPAA Security Rule: access controls, encryption, audit logs and breach notification.
  • Everywhere, ask for the hosting region, encryption in transit and at rest, backup and recovery arrangements, how access by the vendor's own staff is controlled and logged, and how you get your data back if you leave.

A recognised security certification for the vendor, such as Cyber Essentials in the UK, is a useful baseline, though not a substitute for your own assessment.

Questions to ask a vendor

  1. Which of my exact analyser models have you already connected, and over which standard? For any you have not, what does a new interface involve and how long does it take?
  2. What happens to results if the internet connection drops during a clinic?
  3. How does a result get matched to the right patient, and what happens to a result that cannot be matched?
  4. Can a clinician review, comment and sign off results, and is that recorded against them?
  5. Can patient reports carry our branding, and can they include results from our referral laboratory?
  6. Can results be sent into our clinical system, and over which standard (for example HL7 v2 or FHIR, Fast Healthcare Interoperability Resources)?
  7. How is QC captured, charted and enforced? Can the system stop a patient test when QC has failed?
  8. Is the audit trail tamper-evident, and can we export it for an inspector?
  9. Where is our data hosted, and will you sign a data processing agreement or business associate agreement?
  10. How do you charge: per site, per user, per analyser or per test? What is included and what is an add-on?
  11. Does the software interpret results or give clinical advice? (For connectivity and workflow software the expected answer is no; interpretation brings medical device regulation.)

The POCT software RFP template turns these into a scored document if you are comparing several vendors.

How the costs are structured

Software for on-site testing is usually charged in one of two ways, often with a one-off setup fee for configuration and analyser connection.

  • Per site subscription. A fixed monthly or annual fee for each clinic location, sometimes with optional modules. The cost is predictable and does not rise as you test more patients, which suits a clinic planning to grow volume.
  • Per test fees. A charge for each result processed. The cost starts low and rises with volume, and it makes the software bill harder to forecast.

Other costs to budget for are analyser interface cables or gateway hardware, QC material for verification, staff time for training, and any fee your clinical system supplier or referral laboratory charges to enable an interface. Ask each vendor for a written quote that separates these items.

Where a connected-diagnostics platform fits

Catenix is a POCT middleware and connected-diagnostics platform built for this kind of clinic. It connects analysers over HL7 v2, POCT1-A2, ASTM E1394, FHIR and REST, with an on-site gateway that stores and forwards results if the network drops. It holds results with the device, operator and lot, supports clinician review and sign-off, produces branded patient reports, captures QC with Westgard rules and lockouts, keeps a tamper-evident audit trail and tracks stock by lot and expiry. It is designed and ready to connect over open standards to clinical systems such as Semble or EMIS Web in the UK and athenaOne or eClinicalWorks in the US, with the route confirmed during implementation. Catenix is charged as a subscription per site with optional modules and no per-test fees, explained on the pricing page, with UK hosting available. It does not interpret results or provide clinical decision support; the clinical decision stays with your clinician.

Questions people ask

Is there a cloud platform that connects our analysers, holds the results and produces patient reports?

Yes. POCT middleware and connected-diagnostics platforms do this. They connect benchtop analysers from different manufacturers, store every result against the patient with the device and operator, let a clinician sign off results and produce branded patient reports. Check that the platform supports your exact analyser models, can include referral laboratory results in the same report and can send results to your clinical system. Catenix is one example built for clinics.

Do we need a LIMS to run blood tests in our clinic?

Usually not. A full laboratory information management system is designed for a hospital or commercial laboratory with high volumes and dedicated laboratory staff. A clinic with a few benchtop analysers needs analyser connection, a results store, sign-off, patient reports, QC and stock, which a POCT middleware or connected-diagnostics platform provides with a shorter setup. A LIMS makes more sense if you plan to run a high-volume accredited laboratory.

Can we just type the analyser results into our clinic system?

You can, and many clinics start that way, but it carries risk. Typing introduces transcription errors that cannot be detected afterwards, leaves no link between the result and the operator, device or reagent lot, and gives you no QC record. As volumes grow, manual entry also slows reporting. Connecting the analysers removes the typing step and creates the records an inspector or auditor will ask for.

How long does it take to set up software for on-site blood testing?

For a clinic with three to five analysers on a cloud platform, 2 to 6 weeks is realistic. Connecting the analysers and building the test menu are the quick parts. The time goes on your clinical lead approving reference ranges, verifying each analyser, training staff and getting the referral laboratory and clinical system links enabled by third parties. Starting those conversations in the first week shortens the timeline.

Can the patient report include results from our referral laboratory as well as our own analysers?

It can, if the software receives results from the referral laboratory electronically, usually over HL7 v2 or FHIR. The in-house and referral results then sit in the same patient record and the same branded report. Ask the vendor whether they have connected to your chosen laboratory before, and ask the laboratory early, because enabling an interface on their side can take several weeks.

What data protection do we need for clinic blood test software?

In the UK, health data is special category data under UK GDPR: you need a data processing agreement with the vendor, a data protection impact assessment and a clear answer on where data is hosted. In the US, you need a business associate agreement under HIPAA before loading patient data. In both, ask about encryption, backups, vendor staff access and how you get your data back if you leave.

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.