CXL PRO LIS Integration: HL7 and ASTM Bidirectional Ordering

Most analyzers speak one language to the LIS. The CXL PRO speaks two. Its vendor documentation describes an HL7 v2.3.1 interface over MLLP and, separately, a classic ASTM interface, and both support asking the host what to run on a sample. That flexibility is useful, but it also means the first decision in a CXL PRO LIS integration is a choice most people did not know they had.

LISBridge supports both dialects, in both directions. This post explains what each looks like on the wire, how host-query ordering works in each, and how to choose.

The CXL PRO (CS6400) in Brief

The CXL PRO is an auto-chemistry analyzer. Its vendor internal model code is CS6400, and a sibling model, the CS1600, shares the same interface. In LISBridge both are handled identically, and results appear under the CXL PRO name in your reports and monitoring dashboard.

It is one of the 17 bidirectional instruments LISBridge supports out of the box. You can see the details on the CXL PRO instrument page.

Dialect One: HL7 v2.3.1 over MLLP

In its HL7 dialect the analyzer sends ORU^R01 result messages over TCP, wrapped in MLLP framing. You can recognise it on the wire by the sending application field in the MSH segment, which reads CS6400 (or CS1600 for the sibling model).

There is one quirk worth knowing about, and it is the same family of quirk we described in our post on the HTSH-2000: the analyzer omits the OBX Set ID. In a standard OBX segment the first field after the segment name is a sequence number. Here that field is absent, so the value type comes first and every later field sits one position to the left of where a strict reader of the HL7 specification expects it.

A parser that assumes the standard layout does not fail loudly. It reads the identifier as the value type and the value as the identifier, and the data looks plausible while being wrong. LISBridge locates the value-type token and reads the layout relative to it, so the layout works whether or not a site has added the Set ID back. QC messages, which the analyzer marks in MSH-16, carry no result segments and are kept out of the patient pipeline.

Dialect Two: Classic ASTM

The same analyzer can also use classic ASTM E1394 over the E1381 low-level protocol. That is the frame-numbered, record-per-line style most laboratory staff recognise: header, patient, order and result records, each introduced by a letter and a frame number.

Here the analyzer identifies itself through the sender and receiver fields in the header record. The vendor defaults are Analyzer for the sender and Host for the receiver. If your site changed those values, the interface has to know. This is one of the first things to check when an ASTM link is up but nothing is recognised.

For background on how the two standards compare, see HL7 vs ASTM E1394 and our HL7 and ASTM support overview.

Host Query in Both Dialects

Bidirectional means the analyzer does not wait to be told what to run. When it reads a sample barcode, it asks the LIS what is ordered. The mechanism differs by dialect:

• HL7: the analyzer sends a QRY^Q02 query. LISBridge looks up the sample and replies with a DSR^Q03 message carrying the ordered tests.
• ASTM: the analyzer sends a Q record. LISBridge replies with a worklist built from header, patient, order and terminator records.

Either way the effect for the lab is the same. Nobody keys the worklist into the analyzer by hand. The order is created once, in the HIS or LIS, and reaches the instrument through LISBridge. Results go back along the same path. The general pattern is explained in how analyzer host-query worklists work and bidirectional lab orders.

Choosing a Dialect for Your Site

Both work, so choose on practical grounds rather than preference.

1. Follow what is already running. If the analyzer is already configured for one dialect and is working, changing it adds risk with no benefit.
2. Check what your service engineer can support. The dialect setting is made on the analyzer, and the person who installed it knows which they configured and tested.
3. Prefer the one your team can read. When a result looks wrong, someone has to read the raw message. HL7 segments and ASTM records both read well once you know them, so choose the one your staff are already comfortable with.
4. Do not run both at once. Pick one per analyzer and document it.

A caution on certainty: the CXL PRO support in LISBridge is built from vendor documentation. As with any new analyzer connection, validate against your own unit with a few known samples before you rely on it for patient results. That advice applies to every integration, and it is the reason raw instrument data is stored alongside every parsed result for full traceability.

Setup Walkthrough

1. Decide the dialect and confirm the analyzer's network settings (IP address and port) or serial settings with your service engineer.
2. Add the instrument in LISBridge and select the matching connection.
3. Map the analyzer's test names to your LIS fields yourself in the mapping screen. No custom programming and no vendor ticket.
4. Run known samples and compare the stored record with the analyzer's own printout.
5. Test ordering: create an order in your HIS or LIS for a sample you can load, and confirm the analyzer receives the right tests.
6. Test an unmatched sample to confirm the analyzer receives a clean "no data" answer rather than waiting.

If the link drops, LISBridge reconnects with exponential backoff and jitter, and crash-safe local storage keeps results through a power cut. Pulling orders from your HIS or HMS uses outbound polling, so you do not need to open inbound firewall ports. The device connectivity overview shows how this analyzer fits into a mixed fleet.

Frequently Asked Questions

Does LISBridge support the CXL PRO?

Yes, over both HL7 v2.3.1 on MLLP and classic ASTM, with bidirectional ordering in each.

Is the CS1600 supported as well?

The CS1600 shares the same interface and is handled identically.

Why do HL7 fields look shifted by one position?

The analyzer omits the OBX Set ID. LISBridge reads the layout relative to the value type, so the shift is handled.

How does the CXL PRO ask for orders?

By QRY^Q02 in HL7, answered with DSR^Q03, or by a Q record in ASTM, answered with a worklist.

Which dialect should I use?

Whichever is already configured and tested at your site. Use one per analyzer and do not switch mid-deployment.

Start your free trial — no credit card required. lisbridge.com/pricing