BioEcko Docs
Laboratory

Analyzer Management

Analyzer Management connects your automated laboratory instruments to Bio-Ecko for bi-directional data exchange. This eliminates manual transcription of...

February 2026 · 6 min

Manual area

Laboratory

Coverage

6 sections

Operator notes

3 implementation notes

Overview

Analyzer Management connects your automated laboratory instruments to Bio-Ecko for bi-directional data exchange. This eliminates manual transcription of results, reduces errors, and significantly improves turnaround time. The system supports haematology, biochemistry, immunoassay, coagulation, blood gas, urine chemistry, and microbiology analyzers from all major manufacturers (Beckman Coulter, Roche, Siemens, Mindray, Sysmex, Abbott, Bio-Rad).

Integration works in two directions: the LIS sends patient/test information to the analyzer (host query), and the analyzer sends results back to the LIS (result upload). This means the technician only needs to load samples and verify results -- no manual data entry.

Supported Integration Protocols

Bio-Ecko supports multiple integration methods to cover both modern and legacy instruments:

  • ASTM / LIS2-A2 -- The standard laboratory instrument communication protocol. Works with most analyzers manufactured after 2005. Supports bi-directional communication (host query + result upload).
  • HL7 v2.x -- Health Level 7 messaging for enterprise-grade integrations. Used by larger analyzers and middleware solutions.
  • Serial / RS-232 -- For older analyzers with serial output only. Bio-Ecko's interface agent reads the serial stream and parses results.
  • TCP/IP Socket -- Direct network connection for analyzers that support Ethernet communication.
  • File-Based Import -- For analyzers that export CSV, TXT, or XML files to a shared folder. Bio-Ecko monitors the folder and imports results automatically.

Each protocol can be configured with custom parsing rules to handle manufacturer-specific data formats.

Setting Up an Analyzer

Navigate to Laboratory > Settings > Analyzers > Add Analyzer:

  1. Register the Instrument -- Enter make, model, serial number, department section, and location.
  2. Select Protocol -- Choose the communication protocol (ASTM, HL7, Serial, TCP/IP, File).
  3. Configure Connection -- Set the connection parameters:
    • Serial: COM port, baud rate, parity, stop bits.
    • TCP/IP: IP address, port number.
    • File: Folder path, file pattern, polling interval.
  4. Map Test Codes -- Map the analyzer's internal test codes to Bio-Ecko's test master. For example, analyzer code 'GLU' maps to Bio-Ecko test 'Blood Glucose Fasting'.
  5. Map Result Fields -- Map analyzer output fields to the appropriate result parameters (value, unit, flags).
  6. Configure QC Integration -- Enable QC result routing to the Quality Control module.
  7. Test Connection -- Run a connectivity test to verify communication.
  8. Go Live -- Activate the interface. Results begin flowing immediately.

Bi-Directional Workflow

Host Query (LIS to Analyzer):

  1. Technician loads the sample tube onto the analyzer rack.
  2. The analyzer reads the barcode and sends a query to Bio-Ecko: 'What tests are ordered for this sample?'
  3. Bio-Ecko responds with the test list.
  4. The analyzer runs only the ordered tests -- no unnecessary reagent consumption.

Result Upload (Analyzer to LIS):

  1. The analyzer completes the tests and sends results to Bio-Ecko.
  2. Bio-Ecko receives the results, maps them to the correct patient and test, and pre-fills the worklist.
  3. The technician sees the results in the worklist with an 'Auto' source indicator.
  4. The technician reviews, validates, and submits for pathologist approval.

Auto-Validation (optional): For routine tests where the result falls within normal ranges, delta check passes, and QC is in control -- results can be auto-validated and released without manual review. This is configurable per test and requires pathologist approval to enable.

Middleware & Multi-Analyzer Routing

For labs with multiple analyzers of the same type (e.g., two chemistry analyzers for load balancing):

  • Middleware Mode -- Bio-Ecko acts as middleware, routing samples to analyzers based on workload, test menu, and availability.
  • Priority Routing -- STAT samples can be routed to a dedicated 'fast-track' analyzer.
  • Failover -- If an analyzer goes offline, samples are automatically re-routed to the backup instrument.
  • Result Consolidation -- When a patient's samples are split across analyzers (chemistry on one, immunoassay on another), results are consolidated under a single order in the worklist.

For labs already using third-party middleware (e.g., Roche cobas IT, Siemens CentraLink), Bio-Ecko integrates with the middleware via HL7, and the middleware handles individual analyzer communication.

Monitoring & Troubleshooting

The Analyzer Dashboard provides real-time status for all connected instruments:

  • Connection Status -- Green (connected), Yellow (intermittent), Red (disconnected). Auto-reconnect attempts every 30 seconds.
  • Message Log -- All communication messages (sent and received) are logged with timestamps. Useful for debugging parse errors or missing results.
  • Error Queue -- Messages that failed to parse (unknown test code, invalid format) appear here for manual resolution.
  • Uptime Tracking -- Percentage uptime per analyzer over the day/week/month.
  • Result Volume -- Number of results received per analyzer per shift, for workload analysis.

Alerting: If an analyzer disconnects for more than the configured threshold (default 5 minutes), the lab supervisor receives a notification.

Notes

Tip

Map all analyzer test codes during initial setup, including rare tests. Un-mapped results go to the error queue and require manual entry, defeating the purpose of integration.

Clinic tip

For small labs with a single analyzer, the file-based import method is often the simplest to set up. Export results as CSV from the analyzer and Bio-Ecko picks them up automatically.

Warning

Always verify auto-uploaded results before validation, especially during the first week after a new analyzer integration. Mapping errors can cause results to appear under the wrong test parameter.

On this page