What does pathology lab software do? Follow one sample
Pathology lab software, or a laboratory information system (LIS), is the record of every sample a lab handles and every result it releases. The simplest way to see what it must do is to follow one blood sample through a morning.
At 8:10 a.m. a patient arrives at a collection centre with a doctor’s slip for a CBC, lipid profile and HbA1c. The centre registers them, the software works out that three tubes are needed and prints three barcode labels. The phlebotomist sticks them on and the centre marks the samples as collected. At 10:30 the pickup boy scans the bag at the main lab; the software records receipt and warns if a sample is missing or arrived too late.
In the lab, the technician loads the tubes. The haematology counter reads the barcode, asks the LIS which tests to run, and sends back results. The biochemistry analyzer does the same. The software applies reference ranges, compares with the patient’s previous HbA1c and flags anything unusual. The pathologist reviews, adds a comment, signs. At 4:40 p.m. the patient receives a PDF on WhatsApp, and the referring doctor gets a copy.
Every one of those steps is a place where manual work causes errors. Good pathology lab software removes as many of them as the lab’s budget allows.
Ready-made pathology lab software or your own build?
Buy first if you are a single lab with standard reports and analyzers the product already supports; build when your network, analyzers or report rules keep fighting the product. Many labs should never build.
A ready-made LIS makes sense when you are starting, your test menu is typical, and you can live with the vendor’s report designer. The subscription covers upgrades and you are running within days. Check three things before signing: whether your exact analyzer models are supported (ask for a lab already using them), whether you can export all patient and result data, and how price changes with branches, users and collection centres.
Custom pathology lab software pays off in specific situations: a chain with many franchise collection centres on different rate lists; an unusual analyzer, or a mix of old serial and new network instruments; report formats that referring hospitals insist on; or a subscription that now costs more each year than owning would. It also suits labs that want their data in their own cloud for reporting and future AI work.
Signals to stay with a product
One location, fewer than a handful of analyzers, reports that match the product’s style, and staff who are comfortable with it.
Signals to build
Collection network billing done in Excel on the side, technicians retyping results from an unsupported analyzer, or repeated requests the vendor has not delivered.
How does barcode sample tracking work in pathology lab software?
Barcode tracking gives every container its own ID the moment it is collected, so the sample never depends on a handwritten name again. Pathology lab software prints the label, and every later step scans it.
The rule we build around is one label per container, not one per patient. A CBC in an EDTA tube and a lipid profile in a serum tube get different barcodes, because they go to different analyzers. The software knows from the test master which container each test needs, groups tests that can share a tube, and prints the right number of labels with the patient name, age, sex, container type and collection time.
Scanning then creates a trail. Collected at the centre, packed in a bag, received at the lab, loaded on an analyzer, result posted, report released. If a sample goes missing, you can see the last scan and who did it. If a sample arrives outside its stability window, the software warns at receipt so it can be recollected before the patient waits a day for nothing.
- Code 128 labels from a thermal label printer at each counter
- Container type and colour printed on the label
- Scan at collection, dispatch, receipt and loading
- Rejection reasons recorded: haemolysed, clotted, insufficient, unlabelled
What is analyzer interfacing, and do you need ASTM or HL7?
Analyzer interfacing means the instrument sends results straight into pathology lab software, so nobody retypes numbers. Which protocol you use is decided by the analyzer, not by you.
Most bench analyzers, such as haematology counters, biochemistry and coagulation analyzers, speak the ASTM format (ASTM E1394 with the E1381 transport, now maintained by CLSI as LIS2 and LIS1). Newer instruments and hospital systems often use HL7 version 2 messages. Older machines connect through an RS232 serial cable; newer ones use a network (TCP/IP) connection.
The practical step is the maker’s host interface manual, a document describing exactly what that model sends and expects. Ask your analyzer supplier or service engineer for it; without it, interfacing is guesswork. We then write a small interface agent that runs on a PC in the lab, next to the instruments. It reads the serial port or network socket, parses the messages, matches them to the barcode and posts results to the cloud LIS. If the internet drops, it keeps results locally and sends them when the line returns.
Each model is a separate line on the quote, because each maker implements the standard with its own test codes and quirks. We do not supply cables, converters or the analyzer’s own licence if the maker charges for its host interface.
Unidirectional or bidirectional interfacing: which one pays off?
Start with unidirectional on most analyzers and move the busiest ones to bidirectional. Bidirectional saves more time, but it needs more from the instrument and more testing.
With a unidirectional link, the technician still selects tests on the analyzer, and results flow back into the pathology lab software automatically. That alone removes most transcription errors. With a bidirectional (host query) link, the analyzer reads the barcode, asks the LIS which tests are ordered and runs only those. Nobody touches the analyzer keyboard, which matters when a biochemistry analyzer runs hundreds of tests a day.
Not every analyzer supports host query, and some support it only with a paid option from the maker. The host interface manual tells you. For a lab with one busy biochemistry analyzer and a few smaller instruments, a common pattern is bidirectional on the big machine and results-only on the rest.
Whatever the mode, test code mapping (the analyzer’s code for glucose matched to your LIS test) is where most go-live problems hide. We build a mapping screen so your lab can maintain it without calling us.
NABL and ISO 15189: what the pathology lab software must support
Software does not make a lab accredited; it makes the records an assessor asks for easy to produce. NABL accredits medical laboratories against ISO 15189:2022 together with its own specific criteria document, NABL 112A, published on the NABL website.
For pathology lab software that translates into a few concrete features. Reports should carry unique patient identification, the lab’s identity, sample type and collection, receipt and report times, results with units and biological reference intervals, the method where relevant, interpretive comments, page numbering, and the identity of the person who authorised release. Amended reports should be marked as amended, with the original kept and the change logged.
Behind the report, the software should keep an audit trail of every edit, record who validated each result, store equipment and reagent details used for a run if your quality manager wants them, and give turnaround-time reports by test and department. Critical values need a recorded notification: who was informed, when and by whom.
We build these features to support your quality system; your quality manager and your consultant decide what the lab’s procedures require. Treat any vendor who promises that software alone will get you accredited with caution.
Quality control, delta checks and critical values
Quality control data belongs inside pathology lab software, next to the patient results it protects. Keeping QC in a separate notebook means nobody sees the problem until reports are already out.
We record control runs per analyzer and level, plot Levey-Jennings charts and apply the Westgard rules your quality manager selects. If a control fails, the software can hold release of patient results on that analyzer until the run is accepted. Delta checks compare a new result with the same patient’s previous one and flag a change too large to be believable, such as a sudden haemoglobin drop, which is often a sample mix-up rather than a clinical event.
Critical values, like a dangerously low potassium, trigger an alert on the pathologist’s screen and a task to call the doctor or patient. The call is logged with time and name. None of this replaces the pathologist’s judgement; it just makes sure the right result reaches the right person in time.
How do labs send pathology reports on WhatsApp safely?
Send a report-ready message with the PDF through the official WhatsApp Business Platform, only after pathologist sign-off, and keep a verification link so anyone can confirm the report is genuine. Pathology lab software should never send from a staff member’s personal phone.
The message itself is a pre-approved utility template, such as “Your report for sample 24081 is ready” with the PDF attached. Meta’s pricing documentation states that since 1 July 2025 template messages are charged per message, and utility templates sent inside the 24-hour window after the patient messages you are free. Asking patients to send “Hi” at registration opens that window for same-day reports.
Safety comes from the details. The PDF carries a QR code that opens the report on your domain, so a doctor can spot an edited copy. Reports for sensitive tests can be held for collection or sent with an extra check. Partial reports are labelled as such. Referring doctors can receive copies automatically if the patient agreed at registration.
Setting up the platform itself, with display name, templates and number verification, is covered on WhatsApp Business API integration.
Billing franchise collection centres and B2B clients
Collection-centre billing is where generic pathology lab software most often breaks, because every centre has its own deal. The software has to know, for each centre, what the patient pays, what the centre owes the main lab and how credit works.
We model it as rate lists. The main lab keeps an MRP list. Each franchise or partner centre gets its own B2B list or a discount rule against MRP, and special rates for packages. When a centre registers a patient, the patient bill uses the centre’s price and the lab records what the centre owes. At the month end, each centre gets a statement: samples sent, amount due, payments received through UPI or bank transfer, and balance.
Credit limits stop a centre from sending more samples once it owes too much, with an override for the owner. Hospitals and corporates sending samples in bulk get their own lists and consolidated invoices with GST where it applies. Pickup routes, the list of centres the rider visits and the bags scanned at each, sit alongside billing so revenue and logistics match.
Running many branded outlets rather than partner centres? Royalty and stock rules for that model are on franchise management software.
Home collection and the phlebotomist’s phone
If your lab offers home collection, it runs smoothest when the phlebotomist carries the pathology lab software in a simple app.
The app shows the day’s bookings in route order, the tests and container list per patient, and the fasting instructions sent the day before. At the door, the phlebotomist prints or attaches pre-printed labels, confirms collection with a photo or signature, takes payment by UPI and marks each sample. The lab sees samples in transit before they arrive, and patients get a WhatsApp message that collection is done.
Bookings come from your website, a call centre or WhatsApp. The public side, test menu with prices, pincode check and slot booking, belongs on your website and is covered on diagnostic centre website design. The app is built with Flutter or React Native and published in your own Play Console and App Store Connect accounts, starting at ₹40,000.
Pathology lab software cost: what moves the quote
Custom pathology lab software starts at ₹60,000 for a single lab with manual result entry, barcodes, reports and billing. Four things move the quote more than anything else.
Analyzer models
Each model needs its own parser and mapping, tested against real messages from your instrument. Two identical machines count once; two makers count twice.
Report layouts
Haematology, biochemistry, serology, histopathology and culture reports all look different. Histopathology with free-text gross and microscopy findings takes more work than a table.
Collection network
Centre logins, rate lists, credit rules, statements and pickup tracking add screens and testing.
Migration
Moving years of patients and results from another system depends on how clean its export is.
Hosting in your own cloud account and WhatsApp message charges are paid by you directly. Two months of maintenance are included; after that it is optional from ₹8,000/mo. The cost table below shows how the pieces add up.
How long does it take to set up pathology lab software?
A first release of custom pathology lab software usually takes 6 to 12 weeks. A single lab with two analyzers and no collection network sits near the short end; a chain with centres and five analyzer models near the long end.
The order matters more than the total. We build registration, labels and manual result entry first, so the lab can run parallel tests with dummy patients while analyzer interfaces are written. Interfacing depends on access: someone at the lab must connect the cable or network port and let the agent listen while real controls run. Report layouts are reviewed by the pathologist on printed samples before go-live.
Go-live normally starts with one department. Many labs switch haematology first, run it for a week, then add biochemistry and the collection centres. The two free months of maintenance cover the adjustments every lab needs in the first weeks.
Report security, patient privacy and the DPDP Act
Lab reports are health data, so pathology lab software should treat access to them as carefully as the samples themselves.
The Digital Personal Data Protection Act, 2023 governs digital personal data, and the DPDP Rules, notified in November 2025, phase its obligations in over the following eighteen months. In practice labs need a clear notice at registration, consent for things like sharing reports with a referring doctor, and a way to correct records.
We build role-based access (a collection centre sees its own patients, not the whole lab), audit logs on every edit and release, encrypted connections, report links that expire, and daily backups in your own cloud account with a tested restore. We build the controls; your lawyer approves the wording of notices and consents.
Linking lab reports to ABHA
ABDM lets a lab share reports into a patient’s ABHA-linked health locker, and it is optional for most private labs. It is worth considering if your referring hospitals or patients ask for it.
The lab registers on the Health Facility Registry, and the pathology lab software is integrated with ABDM through the sandbox and approval steps. Then, with the patient’s consent, released reports can be linked to their ABHA. The National Health Authority’s Digital Health Incentive Scheme has covered diagnostic labs as well as hospitals and clinics; check abdm.gov.in for whether it is open and on what terms before counting on it.
We handle the technical integration and testing; the registrations are yours. If your clinics also want ABHA features, the clinic side is covered on clinic management software.
How to choose pathology lab software: a test script for demos
Choose with your own samples and reports, not with the vendor’s demo data. Give every candidate, including us, the same script and time it.
- Register a patient with five tests across three containers; count labels and clicks
- Show a result arriving from your exact analyzer model, not a similar one
- Print a report on your letterhead and hand it to your pathologist
- Amend a released report and show how the change is recorded
- Create a collection centre with its own rate list and run a month-end statement
- Send a report on WhatsApp and open the QR verification link
- Export all patients and results to a spreadsheet
- Pull the internet cable and see what still works
A product that does all eight with your data is worth buying. If three or four fail, a conversation about building your own pathology lab software is worth having.
A worked example: a Varanasi lab with six collection centres
The following is a hypothetical scenario to show how a build would be planned, not a client story.
Imagine a pathology lab in Varanasi with a five-part haematology counter, a biochemistry analyzer, an older serial-port electrolyte analyzer and six franchise collection centres in nearby towns. Reports are typed from analyzer printouts; centre dues are tracked in a notebook.
The quote starts from ₹60,000 for the core system and adds three analyzer lines, one per model, with the biochemistry analyzer bidirectional. It adds centre logins, rate lists and statements, and department layouts for haematology, biochemistry and serology. A phlebotomist app is left for a second phase.
Week two delivers registration and labels on a test link; the centres try them with dummy patients. By week five the haematology counter posts results into the test system; the old electrolyte analyzer, on a serial-to-USB adapter the lab buys, follows in week six. The pathologist signs off printed layouts in week seven, and haematology goes live on a Monday. Biochemistry and the centres switch the following week. Whether the result is worth it depends on the lab’s own numbers; we would say so if a ready-made product fitted better.
Pathology lab software across India
Everything we do is remote: requirement calls on video, test systems on your own screens, analyzer work through a remote session on the lab PC, and support on WhatsApp. We do not visit labs, wire analyzers or supply hardware; your staff or analyzer engineer handles the physical connections with our guidance.
Labs in Varanasi, Patna, Surat, Visakhapatnam, Mysore, Kanpur, Ranchi, Agra, Thrissur and Bhubaneswar work with the same process and starting prices. City pages describe the wider business context there.
Payment is by UPI or bank transfer, on the schedule set out in your quote. If your lab also wants to rank for test searches in its city, see SEO services, starting at ₹10,000/mo, with the honest caveat that no one can guarantee positions.