Guide · Buying lab software
The LIS features checklist: what to look for in lab software
Most lab software feature lists look identical from the outside: patient records, billing, reports, WhatsApp, referrals, security. The differences that actually matter show up only when you check each area against what your lab really needs, area by area, and separate what you cannot go live without from what is genuinely optional. This is that checklist.
Key takeaways
- Split every feature into must-have or nice-to-have. A feature you do not use should not decide the purchase either way.
- Reference ranges should be age- and gender-aware, with automatic low/normal/high flags, not a single static range for every patient.
- WhatsApp delivery should come from your own number, not a shared sending number you have no control over.
- Referral payouts should end in a statement for every payee, not just a commission total you then explain to each doctor by hand.
- Analyzer/HL7/ASTM integration is only a must-have if you run automated analyzers today. Get any vendor's real answer in writing, not a nod during the demo.
- Security means an isolated database per lab, encryption in transit and at rest, and an audit trail, not a vague "bank-grade security" line on a slide.
A full laboratory information system touches almost everything that happens in a lab between a patient walking in and a report reaching them, so a feature checklist that only lists "reports and billing" is really only checking the surface. The list below groups the areas that matter into eight themes, and for each one states what a lab genuinely cannot run without, versus what is a real bonus but not a deal-breaker.
The LIS features checklist, area by area
Use this table as the fast pass. The detail on each row follows underneath, with what a good vendor answer sounds like.
| Feature area | Must-have | Nice-to-have |
|---|---|---|
| Patient records & billing | One record per patient across visits, with billing and invoices attached | Bulk or family-billing shortcuts |
| Test catalogue & ranges | Age- and gender-aware reference ranges, automatic flags | Formula-driven derived values across departments |
| Report generation | Your own logo and letterhead on every report, locked once finalized | A QR check the patient can use to confirm the report is authentic |
| Patient communication | Delivery from a number that is actually yours, not shared with other tenants | Per-message sent/delivered/read status |
| Referral & payouts | Commission rules applied per test at billing, not only reported at month-end (skip if you take no referrals) | A statement per payee, on WhatsApp and printable |
| Analyzer integration | Only if you run automated analyzers: a written answer on HL7/ASTM support | Not applicable if every result is entered manually today |
| Security & hosting | Your own isolated database, encryption in transit, an audit trail | A published data-export path you can run yourself |
| Support & onboarding | Catalogue, ranges and price list set up from your own files, a committed response time in writing | Full historical data migration |
Patient records and billing
Is there one patient record that carries across visits, or does every visit start a fresh file? A lab that cannot pull up a patient's last three visits in one screen is running billing software, not a patient record system. This is the floor, not a differentiator: every serious LIS should clear it.
Does billing produce a proper, sequentially numbered invoice, or a loose printout with no continuity? Sequential bill numbering matters for your own bookkeeping even before any tax question comes into it.
Test catalogue and reference ranges
Are reference ranges age- and gender-aware, with automatic low/normal/high flags, or is it one static range applied to every patient? A single range for a child and an adult, or for both sexes on a test where that matters, produces reports that are technically printed but clinically wrong.
Do derived values (ratios, calculated indices) compute themselves from the entered results, or does someone do that arithmetic by hand under pressure? Manual calculation is where transcription errors live.
A feature list is not a checklist until you know which items you cannot live without.
Report generation and delivery
Does every report, bill and message carry your lab's own logo and letterhead, or does the vendor's own branding show up anywhere a patient can see? Patients trust the lab they walked into, not a piece of software they have never heard of.
Is a finalized report locked and versioned, so a later correction is visible as a correction rather than a silent overwrite? And can the patient verify a report is the authentic one, not a copy that has been altered after it left the lab?
Does report delivery run over WhatsApp from a number the lab actually owns, or a shared sending number used by many other businesses on the vendor's platform? A shared number ties your delivery reputation to every other tenant on it. If one of them gets flagged, your patients can stop receiving reports through no fault of your own.
Doctor referral payouts
When commission rules are set per test and per doctor, does one run give every referrer their own statement, or does it only produce a total of what you owe? Nearly every lab software claims a referral feature. Far fewer actually move the money. This item belongs on the "skip it" side of the checklist entirely if your lab takes no referrals; do not let it inflate the price of something you will never use.
Analyzer and instrument integration: what to actually check
Buyer guidance, not a HealthFlow feature claim
If your lab runs automated analyzers, any LIS you buy should be able to speak to them, typically over HL7 or ASTM, so results land in the patient record without being retyped. This is a real, important checklist item for analyzer-heavy labs. It is also one of the most misrepresented lines on a feature list: "integration" can mean a fully bidirectional interface, a one-way file import, or nothing built at all behind a slide that says "supported." Ask for the vendor's honest answer in writing, not a nod during a demo. Our dedicated guide covers what HL7 and ASTM actually are and what to demand from any LIS on this exact point.
Security, hosting and data ownership
Does your lab get its own isolated database, or does it share one table with every other customer on the platform, separated only by a column in the software? Ask specifically. The answer changes what a single application-level bug can expose.
Is data encrypted in transit and at rest, and is there an append-only audit trail of who accessed what? "Bank-grade security" on a slide is not an answer; a named encryption practice and a real audit log are.
Is the product cloud-hosted, or does the vendor also offer it on your own server? Both models are legitimate and the right choice depends on your lab's IT setup. See our cloud vs on-premise lab software guide for the honest trade-offs either way. HealthFlow itself is cloud-based only, with each lab's data in its own isolated PostgreSQL database, not offered on-premise.
Support, onboarding and pricing
Who builds your test catalogue, reference ranges and price list: you, typing from scratch, or the vendor, working from files you already have? A lab with years of historical records should not start from a blank screen.
Is the price public, month-to-month, and does it state exactly what the add-ons cost, or do you have to negotiate to find out? A vendor confident in its pricing puts it on the page.
Once you have your own shortlist scored against this checklist, put the finalists side by side. See how HealthFlow compares on each of these exact areas, or start from our broader laboratory information system guide if you are still forming the shortlist itself.
How to actually verify a claim on a demo
- Bring your own test list
- Ask for the edge case
- Get the answer in writing
Do not evaluate a feature on the vendor's rehearsed scenario. Bring three tests from your own catalogue, one referral rule you actually use, and one cancellation or correction case, and watch what happens when the answer is not rehearsed. A vendor confident in its product will run this without hesitation.
Frequently asked questions
What is a LIS features checklist?
A LIS features checklist is a fixed list of capabilities to check for, area by area, before you buy diagnostic lab software: patient records and billing, test catalogue and reference ranges, report generation, patient communication, referral payouts, analyzer integration, security and support. The point of the checklist is to stop a vendor demo from being the only thing you judge a product on.
Do I need doctor referral payout features if my lab does not take referrals?
No. Referral payout handling matters only if doctors, consultants or collection centres send you patients on commission. A lab that only sees walk-ins can treat that entire feature area as not applicable and should not pay extra for it. Match the checklist to how your lab actually gets patients, not to a generic feature count.
Is analyzer or HL7/ASTM integration a must-have feature?
Only if your lab runs automated analyzers that currently produce results you retype by hand. If every test is entered manually today, bidirectional instrument interfacing is a nice-to-have you can revisit later, not a reason to delay a decision on everything else. If you do run analyzers, treat it as a must-have and get the vendor’s answer in writing before you sign, since this is one of the most misrepresented line items on any lab software feature list.
Related
Score HealthFlow against this checklist yourself.
A 20-minute WhatsApp demo, on your own tests, your own referrers and your own rules.
WhatsApp us for a demo