Hospital lab software: an LIS that works next to your HMS

Standalone LIS or the HMS lab module?

If the hospital wants wards, pharmacy, OT and lab from one vendor, an HMS with a lab module may suit it better, and we say so. A separate LIS makes sense when the lab also serves outside doctors and collection centres, needs analyzer interfacing, QC and NABL records that the HMS module lacks, or is run as its own business unit.

How do orders come from the HMS?

The HMS (or its integration engine) calls the PathLab Software REST API with an API key: create the patient, create an order with test codes such as CBC or LFT, and read the sample barcode back for the label. Results and signed report links are read back by order or barcode. Ward, OPD and emergency priority (routine, urgent, STAT) is carried on the order.

What about critical values on the ward?

When a result crosses a critical limit, the referring doctor gets an automatic voice call and WhatsApp alert with retries about every 10 minutes and escalation to the lab in-charge; every attempt and acknowledgement is logged with the result. It supports, and never replaces, the lab's duty to inform the clinician.

Can a hospital outsource tests to us?

Yes. A hospital that sends samples to your lab is a B2B account with its own rate list, credit ledger, monthly statement, transfer manifests and a centre login to see its own samples and reports.

ABDM for hospital labs

With the patient's ABHA number or address captured, each signed report can be linked as a care context and shared as a FHIR DiagnosticReport bundle when a consent request arrives. The module runs in sandbox until the facility completes its own HFR registration and HIP onboarding.