LIS requirements checklist for small labs and clinics
A requirements checklist keeps vendor demos honest. Without one, every system looks good because every vendor shows what it does best. This checklist is written for small labs and clinics with a handful of analysers. Copy it, mark each line must, should or could, and ask every vendor to answer in writing.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- Group requirements into workflow, connectivity, quality, compliance, delivery, security, support and commercial terms.
- Mark each line must, should or could, and score vendors only on what you marked.
- Ask for written answers and a demonstration with your own analysers, test menu and report layout.
- Include the exit: data export, format and cost.
- Catenix will answer this checklist line by line for your lab; ask us through the contact page.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
Workflow
| Requirement | Must, should or could |
|---|---|
| Patient or client registration, with duplicate detection | |
| Requests from clinicians, partner clinics or an EHR | |
| Accession numbers and barcode labels | |
| Worklists or host query for each analyser | |
| Manual result entry with the same controls as connected results | |
| Review and release by authorised staff | |
| Critical result communication recorded and acknowledged | |
| Corrected and amended results with history | |
| Branded reports per client or partner clinic | |
| Cumulative results view per patient | |
| Billing, price lists and invoices |
Analyser connectivity
| Requirement | Must, should or could |
|---|---|
| Named support for each analyser model we run, with protocol | |
| Bidirectional interfaces where the analyser supports them | |
| QC runs identified and filed separately from patient results | |
| Store and forward if the network or internet drops | |
| Raw analyser messages kept for traceability | |
| New analysers added as configuration, with a stated lead time for new drivers |
Ask each vendor: "Analyser not on your list: how long to build the driver, and at what cost?" Catenix builds drivers for unsupported analysers, usually within a couple of days. To fill in the analyser lines before you contact anyone, use our analyser connection guides or the open connectivity dataset, or ask in ChatGPT or Claude through our AI assistant connector.
Quality
| Requirement | Must, should or could |
|---|---|
| Levey-Jennings charts per analyser, test, lot and level | |
| Westgard multi-rule evaluation with configurable rules | |
| Lockout of a test when QC fails, until reviewed and repeated | |
| EQA or proficiency testing records | |
| Operator training and competency, able to block release | |
| Equipment maintenance, calibration and temperature records | |
| Nonconformities and corrective actions | |
| Method verification records |
Compliance and audit
| Requirement | Must, should or could |
|---|---|
| Tamper-evident audit trail of every create, change and release | |
| Evidence aligned to ISO 15189:2022 for accreditation | |
| CLIA, CAP or Joint Commission readiness records, if in the US | |
| CQC or other regulator evidence, if in the UK | |
| Document control for procedures | |
| Role-based access, with no shared logins needed |
Delivery and integration
| Requirement | Must, should or could |
|---|---|
| Orders from and results to our EHR, named, by HL7 v2 or API | |
| Results to GP systems such as SystmOne or EMIS, if in the UK | |
| Patient portal or app with release control | |
| FHIR support where the receiving system offers it | |
| Acknowledgements, retries and alerts on failed delivery |
See how lab orders and results interfaces work for the detail behind these lines.
Security and data
| Requirement | Must, should or could |
|---|---|
| Hosting region we can choose, such as UK or US | |
| Encryption in transit and at rest | |
| Multi-factor sign-in | |
| Backups with tested restore | |
| HIPAA business associate agreement (US) or UK GDPR processor terms (UK) | |
| Full data export in a standard format |
Implementation and support
| Requirement | Must, should or could |
|---|---|
| Implementation plan with dates and named responsibilities | |
| Validation support and test scripts | |
| Training for current and new staff | |
| Support hours and response times | |
| Update and release process, with notice of changes |
Commercial terms
| Requirement | Must, should or could |
|---|---|
| Pricing model stated: per site, per test, per user or per interface | |
| Every analyser and interface priced in the quote | |
| Annual price increase cap | |
| Contract length and break options | |
| Cost of exit and data export |
Compare quotes over three years; see how much does a LIS cost.
Writing requirements vendors cannot dodge
A requirement a vendor can answer "yes" to without thinking is not doing its job. Rewrite vague lines as statements you can test in a demonstration:
| Vague | Testable |
|---|---|
| Good analyser connectivity | Results from each of our named analysers arrive matched to the request with no typing, and QC runs file as QC |
| Strong QC | A failed Westgard rule on any control holds patient results on that analyser until someone reviews it |
| Integrates with our EHR | Results file into our EHR against the original order, and a corrected result replaces the earlier value |
| Secure | Multi-factor sign-in for all users, encryption in transit and at rest, and the hosting location stated in the contract |
| Easy to leave | A full export of patients, results, QC and audit records in a standard format, at a price stated now |
A worked scoring example
An illustrative lab marks its lines, sends the checklist to three vendors and scores the written answers. Must lines are pass or fail; should lines score 0, 1 or 2.
| Line | Priority | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| Every analyser supported by model | Must | Pass | Pass, one needs a new driver | Fail |
| QC failure holds patient results | Must | Pass | Pass | Pass |
| Results into our EHR against the order | Must | Pass | Pass | Pass |
| Branded reports per partner clinic | Should | 2 | 1 | 2 |
| Patient portal with release control | Should | 1 | 2 | 2 |
| Stock and lot tracking | Could | Not scored | Not scored | Not scored |
Vendor C fails a must line and drops out, however good its other scores. Vendors A and B are level on should lines, so the decision moves to the demonstration, a reference call and the three-year cost. Could lines only break ties.
Common mistakes with requirements lists
- Marking everything must. If every line is a must, nothing is, and every vendor fails.
- Yes or no questions. Ask how each line is met, and see the important ones demonstrated.
- Leaving out the bench. The people who run the analysers know which steps waste time today.
- Analysers described by type, not model. "A haematology analyser" cannot be checked; a model and software version can.
- Scoring the demonstration from memory. Score the written answers, then use the demonstration to confirm them.
A demonstration script to send in advance
Send the shortlisted vendors the same script a week before the demonstration, so you see your workflow rather than their favourite screens:
- Register a patient and a request from one of your partner clinics or your EHR.
- Show a result arriving from one of your analysers, matched to that request, with no typing.
- Fail a QC run and show what happens to the next patient result on that analyser.
- Try to release a result as a user whose competency has lapsed.
- Correct a released result and show what the EHR or the report receives.
- Produce the audit trail for that result, from the analyser message to the report.
- Export the data for one patient in a standard format.
Reference calls: what to ask
A reference customer chosen by the vendor will be a happy one, so ask questions that reveal detail. How long did it take from contract to first real result? Which analysers did you connect, and did any need a new driver? What went wrong at go-live and how quickly was it fixed? How does support respond to an urgent problem? What would you check more carefully if you chose again?
Using the checklist
- Mark each line must, should or could with your team.
- Send it to three or four vendors and ask for written answers.
- Shortlist two and ask each for a demonstration using your analysers, tests and a sample report.
- Ask for a reference customer of similar size.
- Score only against your must and should lines.
Where Catenix fits
Catenix is built for the workflow, connectivity, quality, compliance, delivery and security lines above for clinics and small labs, with analyser connectivity over HL7 v2, POCT1-A2 and ASTM E1394, and sends HL7 v2 or FHIR R4 on to clinical systems, with QC with Westgard rules and lockout, competency, a tamper-evident audit trail aligned to ISO 15189:2022, delivery to EHRs and GP systems, and hosting arranged to meet your local data requirements, including in-country hosting where required. It is priced per site with no per-test fees. Send us your checklist through the contact page and we will complete it for your lab. 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 should be in a LIS requirements specification?
Workflow, analyser connectivity, quality control, compliance and audit, delivery and integration, security, implementation and support, and commercial terms, each marked by priority.
How many vendors should we compare?
Three or four on paper, two in demonstration. More than that slows the decision without improving it.
Should we write a full tender?
Private labs and clinics rarely need one. A checklist with written answers and a demonstration is usually enough. NHS buyers may need a formal process; see our POCT software RFP template.
Will Catenix complete our checklist?
Yes. Send it through the contact page.
Who should write a lab's requirements list?
The lab manager or quality lead, with input from the people who run the analysers, the clinicians who receive results, and whoever owns IT and data protection.
How do we stop vendors answering yes to everything?
Write requirements as testable statements, ask how each one is met, and check the important ones in a demonstration with your own analysers, test menu and report layout.
Should the requirements list name our analysers by model?
Yes. List each analyser by manufacturer, model and software version, with the protocol if you know it. Vendors can then confirm support line by line instead of answering in general terms.
How much weight should price get?
Treat price as a separate step. Score the must and should lines first, drop any vendor that fails a must, then compare three-year cost among those left, so a cheap quote cannot hide a missing requirement.
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 →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 →POCT software RFP template
A POCT software RFP template: numbered requirement tables for connectivity, QC, security, integration and support, plus scoring and common mistakes.
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.