Samples tracked on paper registers
With eMedHub: Each sample gets a system-generated sample ID (SID) and a Code128 barcode label. The record shows who collected it and when.
Manage laboratory workflows from test order to final report.
Connect laboratory orders, sample collection, results, approval and reporting in one system, with billing and the patient record alongside. It works for hospital labs and standalone diagnostic centres.
Most lab delays and errors happen between steps: when a sample changes hands, a value is copied, or a bill is reconciled. Here is how eMedHub handles each one.
With eMedHub: Each sample gets a system-generated sample ID (SID) and a Code128 barcode label. The record shows who collected it and when.
With eMedHub: Every test moves through visible statuses from collection to delivery, and a TAT report shows where the time went.
With eMedHub: Doctors' orders from OPD and IPD reach the lab electronically. Results from connected interface middleware can be posted straight into the test.
With eMedHub: The barcode carries the SID (with the UHID), so results are entered against the right sample. Rejected samples are marked with a reason rather than quietly re-drawn.
With eMedHub: In a hospital, the lab works from the same patient record and UHID as OPD and IPD. Results go back to the ordering doctor, and IP tests land on the inpatient bill.
With eMedHub: Lab bills cover cash, credit, insurance and corporate payers, with discounts, concessions and advance adjustment, plus day-end collection reports.
With eMedHub: Tests sit in clear statuses (collected, in progress, saved, completed, delivered), so the team can see which results are not yet out.
With eMedHub: Result changes are kept in a history with the old value, new value, user and time. Where approval is switched on, a different user must approve the result before release.
Seven steps, one record. Each step is logged against the sample, so you can see where any test is and who handled it.
From a doctor in OPD or IPD, or billed at the lab counter for walk-in and referred patients.
Collection is recorded against the test, with the collector and the time.
A sample ID (SID) is generated and printed as a Code128 barcode label.
The test moves to in progress. Send-out tests follow a tracked outsourcing chain.
Values entered by hand or posted by interface middleware, with reference-range and panic flags.
Optional approval step: a department approver approves, rejects or sends a result back for recheck.
Signed PDF report, printed or sent by SMS, WhatsApp, the patient app and to the patient's ABHA.
Everything listed here is in eMedHub's laboratory module today. See the laboratory module overview for a summary.
The same laboratory module is set up differently depending on whether the lab serves a hospital's own doctors or walk-in patients and referring doctors.
Copying values from an analyser printout into software is slow and introduces transcription errors. Connecting the analyser removes that step, but how it works depends on the instrument, its interface and the middleware in between.
eMedHub receives results through a result API. Your interface middleware sends the sample ID, the analyser's test code and the value. eMedHub maps that code to the ordered test, records the result and flags it as machine-entered.
How analyser integration works, and what to check →NABL accredits laboratories, not software. Accreditation to ISO 15189 depends on your quality management system, staff and processes. Software helps by keeping the records consistently.
See the full breakdown in how lab software supports NABL readiness.
Reports available in the laboratory module today:
Read more about where lab turnaround time is lost.
Most of the work is in the test master and reference ranges, which your pathologist should check before go-live.
Departments, test menu, report formats, payers, referring doctors and any analysers you plan to connect.
Tests, groups, packages, specimens, containers and methods, with prices. Existing test masters can be imported from a template.
Ranges by gender and age, units, abnormal and panic values, checked by your pathologist before go-live.
Letterhead, signatures, barcode sticker size and printed fields.
Roles for front desk, technicians and approvers, with department-wise approval rights.
Role-wise training, parallel runs on real samples, then switch-over with our team on hand.
It runs a laboratory from test order to released report: registration and billing, sample IDs and barcodes, result entry with reference ranges, approval, report printing and delivery, and the reports a lab manager needs. It is often called a laboratory information system (LIS).
Each sample gets a system-generated sample ID and a Code128 barcode label. Collection is recorded with the collector and time, and the test then moves through statuses up to delivery. A rejected sample is marked with a reason, and the test returns to pending so a new sample can be collected.
Yes. Lab bills support discounts and concessions, credit, insurance and corporate payers, advance adjustment, partial and modified bills, cancellations and receipts. Day-end, insurance and doctor-share reports help with reconciliation.
eMedHub accepts results from interface middleware through its result API: the middleware sends the sample ID, analyser test code and value, and eMedHub maps the code to the ordered test. The instrument connection itself runs in the middleware, so supported analysers depend on your middleware. We confirm this for your instruments during the assessment.
No software is NABL accredited. NABL accredits laboratories, against ISO 15189 for medical labs. eMedHub keeps records that help with accreditation, such as sample IDs, collection details, result change history and approvals. Areas like quality control, equipment calibration and document control need to be managed outside the software today.
Reports print as PDFs on your letterhead and can be sent by SMS, WhatsApp and the eMedHub patient app. Completed reports are also linked to the patient's ABHA record.
Yes. Culture reports record the organism, colony count and antibiotic sensitivity with MIC, zone size and S/I/R interpretation, using organism and antibiotic masters.
Yes. Send-out tests are mapped to partner labs with their cost, and each sample is tracked through collected, transferred, received and result uploaded, with the user and time at each step and reminders when results are due.
It depends mainly on the size of your test menu, how many report formats and reference ranges need to be set up and checked, and whether analysers are being connected. We give you a plan after the assessment.
Cost depends on the number of users and branches, modules (lab alone or with hospital modules), test-master setup, integrations and training. Our standard plans are on the pricing page; book a demo for a quote matched to your lab.
Comparing options? Read our LIS buyer's guide for Indian labs or see pricing.
Tell us about your lab. We'll show you the order-to-report workflow on your own test menu, including sample barcodes, result entry, approval, billing and report delivery.