Custom hospital LIS covering test ordering from OPD/IPD/ED, barcode sample collection and tracking, result entry with auto-validation, NABL-format reports, critical value alerts, LOINC-coded observations for ABDM FHIR export, and HL7 2.x analyser integration. Part of the OneCity 120-module Hospital ERP.
Get a Free Demo WhatsApp UsA hospital laboratory receives test orders from OPD, IPD, ED, and ICU simultaneously, processes samples across multiple departments (haematology, biochemistry, microbiology, pathology), generates results with validated reference ranges, alerts on critical values that require immediate clinical action, and reports in NABL-accredited format. Managing this manually or on a standalone LIS disconnected from the clinical system creates the most common lab problem in Indian hospitals: doctors waiting for results that are already available but not communicated, or clinical decisions made on results that have not been validated.
Module 11 of the OneCity Hospital ERP integrates the LIS directly with the clinical and patient management layer. Lab orders placed in the OPD consultation (Module 4) or IPD nursing orders flow to the LIS automatically — no paper requisition for the patient to carry to the lab. Sample collection generates a barcode label at the collection point. The specimen is tracked from collection through receipt, processing, result entry, validation, and report delivery. Critical values trigger an immediate alert to the ordering doctor. Results appear in the patient’s electronic record the moment they are validated, visible to every clinician treating that patient. LOINC-coded observations make every result ABDM FHIR R4-exportable as part of the patient’s portable health record.
OneCity Technologies Pvt. Ltd (CIN: U72100KA2009PTC048911), Bengaluru, Mangaluru, Mysuru. We have implemented hospital LIS as part of the ERP for Karnataka hospitals since 2017. Every LIS implementation begins with a lab workflow mapping session — understanding which departments are in-house, which tests are outsourced, which analysers are deployed, whether NABL accreditation is current or planned, and what the current critical value communication workflow looks like. The LIS is then configured to match existing workflows while fixing the specific gaps — usually sample tracking, critical value communication, and billing integration — that the hospital identifies as the primary pain points. This workflow-first approach means the LIS goes live with high adoption rates because it solves real problems rather than imposing new ones.
A haemoglobin result stored as "Hb: 11.2" in free text is readable by a human but not by any other system. The same result stored with LOINC code 718-7 (Hemoglobin), value 11.2, unit g/dL, and reference range 12.0-17.5 is machine-readable, ABDM-interoperable, and supports clinical decision support queries across the patient population. LOINC coding in Module 11 is what transforms a lab report into a structured health record.
All features from the live OneCity Advanced Hospital ERP, deployed 2026.
Doctors order lab tests directly from the OPD consultation screen (Module 4) or IPD nursing orders — selecting from the test master with LOINC codes, panel profiles, and department routing. Orders arrive in the LIS queue automatically. For ED and ICU, stat orders are flagged for priority processing with a different collection and reporting queue. The patient does not carry a paper requisition; the sample collection point receives the order on screen.
Sample collection generates a barcode label at the phlebotomy station with patient UHID, test name, collection date-time, and collector ID. The specimen is tracked through every transition: collected → received in lab → assigned to section → processing → result entered → validated → reported. Any specimen with no movement for longer than the expected processing time triggers a pending sample alert. Sample rejection workflow (haemolysed, insufficient volume, wrong container) routes the rejection back to the ordering doctor with a recollection request.
Results are entered against the LOINC-coded test with the reference range visible on screen. Auto-validation flags results outside the reference range for review before reporting. Critical value thresholds (set per test by the lab) trigger an immediate push notification and in-app alert to the ordering doctor when a result crosses the panic threshold — haemoglobin below 6 g/dL, potassium above 6 mmol/L, glucose above 500 mg/dL. The critical value alert is acknowledged by the doctor and logged with timestamp for medicolegal documentation.
Lab reports are generated in NABL (National Accreditation Board for Testing and Calibration Laboratories) format with the accreditation number, NABL logo placement, test name, result, unit, reference range, and validating pathologist’s signature. Reports are delivered to the patient record automatically on validation, available for printing at the lab counter, and downloadable from the patient portal. LOINC-coded results are packaged as HL7 FHIR R4 DiagnosticReport resources for ABDM export with patient consent.
Internal QC (quality control) runs are logged with Levey-Jennings chart data for each analyser and test. External QC participation records from EQAS schemes are stored. Turnaround time (TAT) is tracked from order to result for every test, with TAT breach alerts when a test exceeds the SLA. The TAT dashboard shows average TAT by test, section, and shift, identifying bottlenecks. This data is required for NABH accreditation and NABL quality management.
Most modern lab analysers (Beckman Coulter, Roche, Abbott, Siemens, Sysmex) support HL7 2.x bidirectional interface. Module 11 is integration-ready for these interfaces: orders are transmitted to the analyser electronically, and results return to the LIS automatically without manual entry. This eliminates the transcription errors and time delays of manual result entry for high-volume routine tests. Every test order also pushes a billing line to Module 14, so lab charges are captured without a separate billing entry.
In hospitals where the LIS is disconnected from the clinical system, results are available in the lab but the doctor does not know. The patient or a ward attendant carries the printed report. An IPD patient’s evening blood test result is not seen by the treating doctor until rounds the next morning. With Module 11 integrated into the ERP, the validated result appears in the doctor’s patient list the moment it is reported, with a push notification on the doctor’s mobile app. Critical values do not wait for the doctor’s next visit to the ward.
A sample without a barcode or with a handwritten label that becomes illegible is a patient safety risk. Barcode-based collection in Module 11 eliminates handwritten labels. The barcode is generated at the collection point from the electronic order, contains the patient UHID and test, and is scanned at every tracking point. Specimen identity is verified at the analyser interface. Mix-up at the collection or processing stage is caught by the tracking system rather than discovered when a result does not make clinical sense.
NABL accreditation requires documented QC records, validated instruments, controlled reference ranges, personnel qualification records, TAT monitoring, and complaint records. Maintaining these manually alongside a LIS that does not integrate them is a significant administrative burden before every NABL surveillance visit. Module 11 maintains QC logs, TAT records, and validation documentation in the system so the NABL audit trail is always current. Reference: nabl-india.org.
The test master in Module 11 supports multiple lab departments under one LIS, each with their own reference ranges, QC protocols, and report formats.
Haematology: CBC, ESR, peripheral smear, coagulation profile, reticulocyte count. Analyser integration for automated CBC with differential. Critical value alerts for haemoglobin, platelet count, and WBC.
Biochemistry: Liver function, kidney function, lipid profile, blood sugar, thyroid function, electrolytes, cardiac markers. Auto-validation against age and sex-specific reference ranges.
Microbiology: Culture and sensitivity reports with organism identification and antibiogram. Antibiotic stewardship integration (Module 81) flags restricted antibiotics in the sensitivity report.
Pathology / Histopathology: Biopsy and FNAC reports with structured template entry, image attachment capability, and resident-to-consultant approval workflow before report release.
Blood Bank Integration: Compatibility testing results from Module 31 (Blood Bank) link to the LIS for patient blood group records and transfusion reaction documentation.
Module 11 connects to the 120-module Hospital ERP — orders from the EMR, charges to billing, results to ABDM, and QC data to the NABH quality module. A standalone LIS cannot deliver this integration.
Lab results are the most structured clinical data a hospital generates — every result has a test name, a numeric value, a unit, and a reference range. This makes them the easiest type of health record to code correctly (LOINC) and the most valuable for ABDM interoperability. A patient’s HbA1c trend over three years, visible to any ABDM-connected provider with consent, is a complete diabetes management record. Lab results coded in LOINC and exported as FHIR DiagnosticReport resources are the foundational layer of the national health record.
For NABL-accredited labs, Module 11 maintains all documentation required under ISO 15189 (the standard for medical laboratory quality) — test method validation records, reference range establishment documentation, QC logs with Levey-Jennings charts, reagent and calibrator records, and equipment maintenance logs. The NABL audit does not require pulling records from paper folders; the LIS generates the documentation audit trail.
Patient lab data is protected under the DPDP Act 2023 as sensitive personal data. Module 11 implements role-based access (phlebotomists access collection, technicians access result entry, pathologists access validation, doctors access results for their patients), full audit trail of every result view and edit, and FHIR export only with documented patient consent via the ABDM consent module. Reference: DPDP Act 2023.
Many hospitals in Karnataka use standalone LIS products (Medicat, DISA, MyLAB) that manage lab operations well but connect to the clinical and billing system only through exports or manual entry. The gap shows in three places: billing leakage (test ordered but not billed), result communication delay (result available but not pushed to the clinical system), and ABDM non-participation (standalone LIS cannot export FHIR R4 to the hospital’s ABDM implementation).
An integrated LIS built as Module 11 of the hospital ERP eliminates all three gaps: every ordered test is billed automatically, every validated result appears in the clinical record immediately, and every LOINC-coded result is eligible for ABDM FHIR export. The trade-off is the integration effort at development time — which is why building lab software as part of the ERP from the start, rather than integrating two separate products later, is the better-value approach. See our custom vs off-the-shelf guide for the decision framework.
A standalone LIS product like DISA, Medicat, or MyLAB manages the lab workflow competently — order entry, result entry, report printing. For a standalone diagnostic centre, it is often the right choice. For a hospital lab that serves OPD, IPD, ICU, and ED simultaneously, the disconnection from the clinical system creates problems that grow worse as the hospital scales.
The billing leakage is the most quantifiable. Every test ordered but not billed because the standalone LIS does not push charges to the hospital billing system is lost revenue. At 200 tests per day, even a 3% leakage rate (6 tests/day unbilled) at an average test cost of Rs 300 is Rs 1,800 per day — Rs 54,000 per month, Rs 6.5 lakh per year. Over five years that is Rs 32 lakh in unbilled lab revenue. A hospital-integrated LIS eliminates this leakage on day one.
The clinical communication gap is harder to quantify but more important. When a doctor has to physically ask for a result, or wait until a report is physically delivered to the ward, the gap between result availability and clinical action can be hours. For time-sensitive results — blood culture in a septic patient, coagulation in a bleeding patient, cardiac markers in a chest pain presentation — those hours matter. An integrated LIS that pushes results to the clinical record the moment they are validated closes that gap completely.
Many hospitals in Karnataka start with a basic biochemistry and haematology lab and expand over time into microbiology, histopathology, and cytology as the hospital grows. A standalone LIS that handles biochemistry may not handle microbiology’s culture and sensitivity reporting or histopathology’s image-attached reports. The hospital ends up with multiple disconnected lab reporting systems for different departments — exactly the fragmentation an integrated LIS prevents.
Module 11’s test master supports all lab departments from the same platform. Adding microbiology or histopathology means configuring the department in the test master and setting up the report templates — not deploying a new product and its integration. As the hospital’s lab service line grows, the LIS grows with it without the department-by-department integration effort that comes with a standalone product per speciality.
For hospitals considering NABL accreditation for specific departments, the ISO 15189 documentation infrastructure is already present in Module 11. The quality management work and the documentation tools are in the same system. For ABDM participation, the LOINC coding and FHIR export capability mean every new lab department added to the ERP automatically participates in the national health record infrastructure. These are long-term advantages that a standalone LIS swap cannot easily provide because integration into the hospital’s ABDM and billing layers requires rework at every expansion step.
For the full picture of hospital software investment, see our hospital software cost guide and the hospital management software overview.
22 years in business. CIN: U72100KA2009PTC048911. Bengaluru, Mangaluru, Mysuru. Compliant with March 2026 Spam Update. Contact: +91 99023 30233 · contact form · Author profile.
Yes. Most major lab analysers (Beckman Coulter, Roche, Abbott, Siemens, Sysmex, BioSystems) support HL7 2.x bidirectional interface. Module 11 is integration-ready for these — orders transmitted to the analyser electronically, results returned automatically. For analysers using serial RS-232 or proprietary protocols, a middleware interface can be built. The specific analyser models you use are confirmed during the discovery phase and integration tested before go-live.
Yes. Module 11 maintains QC logs with Levey-Jennings chart data, turnaround time monitoring and TAT breach records, reference range validation documentation, reagent and calibrator records, and the test method documentation required under ISO 15189. For labs pursuing NABL accreditation, the LIS provides the documentation infrastructure that NABL assessors verify. The system does not replace the quality management work, but it organises and preserves the records that work generates.
When a result crosses the critical value threshold (set per test by the lab pathologist), the LIS fires an immediate push notification to the ordering doctor’s mobile app (Module 71) and an in-app alert in the clinical system. The notification identifies the patient, the test, and the critical value. The doctor acknowledges the alert within the system, creating a timestamped acknowledgment record. If the alert is not acknowledged within a defined time window, it escalates to the consultant and the nursing station. This documentation protects both the lab and the clinical team.
Results are eligible for ABDM FHIR R4 export once validated and LOINC-coded. The export is governed by patient consent through the ABDM consent module — results are pushed to the ABDM Health Information Exchange only when the patient has granted consent for their lab data to be shared. The patient can view their results in the patient portal (Module 69) and grant or revoke sharing consent at any time. Automatic push without consent is not permitted under ABDM rules.
All standard hospital lab departments: haematology, biochemistry, microbiology (including culture and sensitivity with antibiogram), serology, immunology, pathology, histopathology, cytology, and blood bank interface. Each department has its own test master configuration, reference ranges, QC protocols, report templates, and result approval workflow. A pathologist reviewing and approving a histopathology report has a different workflow from a technician validating a routine CBC — Module 11 supports both in the same system with role-based access and department-specific approval chains.
Yes. Tests ordered in Module 11 can be routed to the in-house lab or to an external reference lab depending on the test master configuration. For outsourced tests, the order generates a requisition for the external lab and the LIS tracks the expected result return date. When the external lab report arrives (uploaded or received via interface), it is linked to the original order and the patient record. Billing for outsourced tests works identically to in-house tests from the patient’s perspective.
Access the laboratory information system (LIS) module — with screenshots, feature documentation, and implementation details for Karnataka hospitals.
Tell us your lab departments, analyser models, current LIS, and NABL status. Free assessment and fixed-price proposal within 5 business days.
Request Free Assessment Call +91 99023 30233 Bengaluru: No. 1869, 2nd Floor, 1st Main Rd, Rajajinagar 560010 | Mangaluru: 1st Floor, Mohtisham, Emporium Complex, Kankanady 575002 | Mysuru: Kantharaj Urs Road, Kuvempu Nagara 570023