Home / Insights / Connectivity
Bidirectional analyser interfaces: host query vs worklist download
A unidirectional interface sends results from the analyser to your system. A bidirectional interface also tells the analyser what to run. That second direction removes manual test selection at the analyser, one of the commonest sources of error in a small lab. This guide explains the two ways it works and how to choose.
Written and reviewed by the Catenix team. How these guides are written and checked.
In brief
- Unidirectional: the analyser sends results only; someone selects tests at the analyser, by hand or from the request form.
- Bidirectional: the analyser also receives orders, so it runs exactly the tests requested for each specimen.
- Host query (query mode): the analyser reads a barcode and asks the host which tests to run. Best for random access analysers and walk-in work.
- Worklist download (batch mode): the host sends the analyser a list of specimens and tests in advance. Suits batch runs and analysers without query support.
- Catenix supports host query and order download in ASTM E1394 and HL7 v2 for analysers that offer them. POCT1-A2 point-of-care devices work differently: Catenix sends them operator lists and directives rather than test orders.
Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).
Why the direction matters
In a unidirectional set-up, the person at the analyser chooses the tests for each sample, usually by reading the request and pressing buttons. It is quick when the menu is short, but it is where wrong-test and missed-test errors creep in: a panel loaded without one test, a test run that was not ordered and is then billed, a sample loaded in the wrong position. A bidirectional interface removes that step. The order in the system decides what runs, and the barcode ties it to the tube.
There is a second benefit. When the analyser knows the order, the result comes back already linked to it, so matching is exact and reconciliation at the end of the day disappears.
Host query
In host query mode the analyser scans the tube barcode and sends a query to the host: "what tests do you have for specimen 2611180042?" The host looks up the order and replies with the tests. The analyser runs them and later sends the results.
In ASTM E1394, the analyser sends a Q (request information) record and the host replies with O (order) records. In HL7 v2, analysers that support it typically use a query message and receive an order message in reply; exact message types vary by manufacturer. POCT1-A2 is built differently. The device sends observations, and the host manages it through directives and operator lists rather than answering test queries; the patient is usually identified at the device.
Host query suits random access analysers where samples arrive in any order, walk-in clinics, and add-on tests. It needs the host to answer within the analyser's timeout, usually a few seconds, which is one reason a local gateway rather than a distant server should answer.
What a host query looks like on the wire
A simplified ASTM E1394 exchange, without the link-layer framing. The analyser scans specimen 2611180042 and asks for its tests:
H|\^&|||ANALYSER^1.0|||||||P|1|20261118093000 Q|1|^2611180042||ALL||||||||O L|1|N
The Q record carries the specimen ID and asks for all tests (ALL), with O in the last field meaning a request for orders. The host finds the order and replies:
H|\^&|||HOST|||||||P|1|20261118093001 P|1 O|1|2611180042||^^^TSH\^^^FT4|R L|1|N
The O record lists two tests, TSH and FT4, separated by the repeat delimiter, with R for routine priority. The analyser runs both and later sends the results as R records. If the host has no order, it replies with a "no information" answer and the analyser follows its own setting: skip the sample, or wait for the operator. Every vendor varies the details, so build from the analyser's own interface manual, and keep a capture of a real exchange as validation evidence.
Worklist download
In download or batch mode, the host sends the analyser the list of specimens and tests before the run, often when the operator presses a button to request the worklist. The analyser stores it and runs samples as they are loaded. This suits analysers without query support, batch runs such as overnight immunoassay, and labs that load racks in a fixed order.
The risk is drift: an order added after the worklist was sent will be missed unless the worklist is refreshed. Good middleware shows which orders were sent to which analyser and when.
Side by side
| Unidirectional | Host query | Worklist download | |
|---|---|---|---|
| Who selects the tests | Operator | Host, on barcode scan | Host, in advance |
| Wrong-test risk | Highest | Lowest | Low, if refreshed |
| Add-on tests | Manual | Easy | Need a new download |
| Needs barcoded tubes | Helpful | Yes | Usually |
| Analyser support | Universal | Many modern analysers | Many analysers |
| Host response time | Not critical | Seconds | Not critical |
When there is no order for a barcode
Decide this before go-live, because it happens every week:
| Situation | Sensible default |
|---|---|
| Order not yet received from the EHR | Hold the sample; retry the query after a short wait |
| Barcode misread or damaged | Operator re-scans or enters the ID; never guess |
| Sample for a test the analyser cannot run | Reply with no tests; route the sample to the right analyser |
| Order cancelled after collection | Reply with no tests; record the cancellation |
| Add-on test requested after the first run | New query or worklist entry for the same specimen |
Common mistakes
- A host that answers too slowly. A query routed over the internet to a distant server can miss the analyser's timeout on a bad day. Answer locally.
- Barcode formats nobody agreed. Symbology, length and check digits must suit both the label printer and the analyser's reader.
- Stale worklists. In download mode, orders added after the worklist was sent are missed unless it is refreshed.
- Panels mapped as one test. The analyser needs the individual test codes, not the EHR's panel code.
- Untested failure paths. Test a timeout, a cancelled order and an add-on before go-live, not after.
Setting it up
- Confirm from the analyser's interface manual which modes it supports and in which protocol.
- Agree the specimen ID format and barcode symbology with whoever prints labels.
- Map each orderable test to the analyser's test codes, including panels.
- Decide what happens when the host has no order for a barcode: hold the sample, or run a default test.
- Test add-ons, cancellations, reruns and a host timeout.
- Train operators on what the analyser screen shows when a query fails.
Our ASTM E1381/E1394 guide shows query and order records, and the POCT1-A2 guide covers point-of-care devices.
Examples
Many benchtop immunoassay analysers, such as the Tosoh AIA-900, support ASTM host query: the operator loads barcoded tubes and each one picks its tests from the order. Many haematology counters support download. Many point-of-care devices identify the patient and operator at the device and send results with those identifiers, with the operator list and device settings managed by the host over POCT1-A2. The Snibe MAGLUMI X3 is an example of an HL7 analyser that supports both host query and orders pushed from the host. See our analyser connection guides for each analyser's interface notes, or download the open connectivity dataset, which records order support for each analyser. You can also ask inside ChatGPT or Claude through our AI assistant connector. Analyser not on the list? We build the driver, usually within a couple of days.
What to keep as validation evidence
Bidirectional interfaces deserve their own validation record, because a failure sends the wrong tests to the analyser rather than a wrong number to a report. Keep, for each analyser:
- a capture of a real query and reply, or a real worklist download, with the specimen IDs visible
- the result of a query for a barcode with no order, and what the analyser did next
- a cancelled order and an add-on test, showing what was sent and what ran
- a deliberate slow or failed reply, showing the analyser's timeout behaviour
- the sign-off of the person responsible, with the date and the analyser software version
Repeat the key checks after an analyser software update or a change to the order catalogue.
Where Catenix fits
Catenix's on-site edge gateway answers host queries locally from orders it already holds, so analysers get a reply within their timeout even if the internet is slow, and sends worklists to analysers that use download mode. Orders come from the EHR or are created at registration in Catenix. Results return linked to the order, QC is filed separately with Westgard rules, and failed QC or an unauthorised operator holds results. Every query, order and result is logged in the audit trail. Catenix is connectivity, workflow and record-keeping software; it does not interpret results and is not marketed as a medical device.
Questions people ask
What is a bidirectional analyser interface?
An interface where the analyser both receives orders from the host and sends results back, so tests are selected by the order rather than by hand.
Is host query better than download?
For random access analysers and walk-in work, usually yes, because each tube gets its current order at the moment it is scanned. Download suits batch runs and analysers without query support.
Do all analysers support bidirectional interfaces?
No. Check the analyser's interface specification. Some send results only.
What happens if the internet is down during a host query?
With a local gateway that holds orders, the query is answered on site. With a cloud-only host, the query may time out and the operator must select tests manually.
Does Catenix support host query?
Yes, in ASTM E1394 and HL7 v2 for analysers that offer it, for example the Tosoh AIA-900 over ASTM and the Snibe MAGLUMI X3 over HL7. For POCT1-A2 point-of-care devices, Catenix manages operator lists and device directives rather than test orders.
What is the difference between host query and order push?
In host query the analyser asks for orders when it scans a barcode. In push, or download, the host sends orders to the analyser before the samples are loaded. Some analysers support both.
Do point-of-care analysers use host query?
Rarely. Most identify the patient and operator at the device. POCT1-A2 devices are managed by the host through operator lists and directives rather than test orders.
Sources and further reading
Read next
More for coordinators.
How lab orders and results interfaces work
How lab orders reach a lab system and results return to the EHR: HL7 ORM and ORU, FHIR, specimen IDs, acknowledgements, corrections and who builds...
Read →ASTM E1381/E1394 guide
ASTM E1381 and E1394 are an older, serial-oriented way analysers send results. See how it works and how Catenix brings serial devices into one...
Read →Supported devices
Step-by-step guides to connecting point-of-care and lab analysers to your LIS or EHR over HL7, POCT1-A2 and ASTM, with bidirectional, wire-level...
Read →Take it with you
The buyer's guide, in your inbox.
Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.
Get the POCT connectivity buyer's guide
Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.
See it done in software.
A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.