Machine integration
Orders go out, results come back, and technicians validate instead of retyping, instrument by instrument.
In short
Analyzer integration connects laboratory instruments to the DevOrbital HMS laboratory module so results are captured automatically rather than keyed in. Commonly used protocols include ASTM and HL7 over serial or network links. Each analyzer is assessed per device and enabled independently, and manual result entry always remains available.
Device types
Data flow
Where the instrument supports it, test requests are sent from the LIS so the operator does not program each sample by hand.
Values are received into the LIS against the right sample, removing the step of reading and typing numbers.
Incoming results sit in a validation queue where abnormal or flagged values can be reviewed before release.
Sample identifiers link instrument runs to patients, which is why barcode scanning is usually set up alongside.
Validated results populate the report template, with reference ranges and remarks added as configured for your lab.
Interfaces
Which interface applies depends on the device. We assess each one during onboarding — nothing here is a promise that a specific model works.
ASTM
Commonly used by laboratory instruments for exchanging orders and results with a LIS, often over a serial or network connection.
HL7
Commonly used messaging standard for results and orders between clinical systems; some instruments or middleware use it.
Serial (RS-232) and TCP/IP
Common physical or network connections; the right one is agreed per device during onboarding.
File or middleware export
Some instruments only export files or work through supplier middleware; whether this is workable is assessed per device.
How we scope it
We list each analyzer, its model type and software version, and how it is connected to a PC or network today.
We review the instrument's documented output, such as protocol, test codes and fields, and agree what flows in each direction.
Test codes are mapped to your test catalogue and tried in a non-live environment with sample runs before real patients.
Each analyzer is enabled on its own, with manual entry as the fallback while confidence builds.
New instruments, firmware changes or replacements are scoped as separate pieces of work.
Benefits
Removing the retyping step removes a common source of wrong values in reports.
Results reach the validation queue as soon as a run finishes, which helps turnaround, particularly at peak hours.
Staff spend effort on checking abnormal results and quality, not on data entry.
Instruments you do not connect continue on manual entry and typed reports in the same workflow.
Feeds into
In practice
Illustrative scenario · not a customer story
A morning biochemistry run
Senior lab technician
The technician loads barcoded sample tubes onto the biochemistry analyzer. The instrument reads each barcode, asks the LIS which tests were ordered and runs them. When the run completes, results appear in the validation queue against the correct patients. The technician reviews flagged values, repeats one sample, then approves the rest. Reports are generated from templates and released. Nothing was typed in by hand. This is an illustrative composite, not a real lab.
An analyzer produces numbers; a LIS turns them into reports. Interfacing is the connection between the two. In a one-way interface, the instrument sends results to the LIS. In a two-way, or bidirectional, interface, the LIS also sends test orders so the instrument knows what to run on each sample.
Most laboratory instruments that can be interfaced use a commonly used protocol such as ASTM, sometimes HL7, over a serial cable or network connection. The laboratory information system in DevOrbital HMS receives those messages and files each result against the correct order. Our detailed article on LIS analyzer interfacing with ASTM and HL7 explains the protocols in plain English.
Many will, but it depends on the instrument's output interface. Some analyzers have a documented interface; others are closed, or only print results. We cannot promise any specific model in advance, which is why each device goes through discovery and testing before it is enabled.
If an instrument cannot be connected, nothing breaks. The laboratory module supports manual entry, typed reports and templates, so that analyzer remains in the same order-to-report workflow. For a goal-focused view, see faster lab turnaround and diagnostic centres and pathology labs. To read more about the wider benefits of sample identification, see barcode sample tracking in the lab.
FAQ
It depends on the analyzer's output interface. Many instruments can send results through commonly used protocols such as ASTM or HL7, but each device is assessed individually before we commit to an integration. Manual entry remains available either way.
No. Each analyzer is scoped and enabled independently. You can start with the highest-volume instrument and add others later.
One-way sends results from the instrument to the LIS. Two-way also sends test orders from the LIS to the instrument. What is possible depends on the analyzer.
Captured results go to a validation queue where a technician reviews them before release. Your lab's validation rules determine how that works.
We do not publish a list of brands or models, because compatibility depends on the specific instrument and its interface. We assess your equipment during onboarding.
Yes. Manual result entry, typed reports and templates mean no machine dependency is forced.
Keep exploring
Lab & Diagnostics
LIS Analyzer Interfacing: ASTM and HL7 Explained
● DevOrbital HMS
Lab & Diagnostics · 7 min read
How LIS analyzer interfacing works: ASTM and HL7 messages, serial and TCP/IP links, test mapping, staged testing and what to ask a vendor first.
Read this guideLab & Diagnostics
Laboratory Information System (LIS): A Complete Guide
● DevOrbital HMS
Lab & Diagnostics · 9 min read
What a laboratory information system does, from order to report: sample tracking, analyzer interfacing, quality and TAT, and how to choose one in India.
Read this guideLab & Diagnostics
How to Reduce Lab Turnaround Time in a Hospital Lab
● DevOrbital HMS
Lab & Diagnostics · 6 min read
Practical ways to reduce lab turnaround time: define TAT, find delays in the pre-analytical, analytical and post-analytical stages, and fix them.
Read this guideShare the devices you want connected and we will tell you what it takes — each one is scoped and enabled independently.
