Generic HL7 Device Setup

This guide covers the general principles for connecting any HL7-capable analyzer to Cortex. It applies to devices such as Horiba, Samsung, and other vendors that use HL7 v2.x over TCP/IP.

For Mindray-specific step-by-step instructions, see the dedicated guides: Mindray BC-30Vet · Mindray BC-5000Vet · Mindray BS-240Vet

1. Prerequisites

• Confirm the device supports HL7 v2.x output over TCP/IP (LIS/host connection)
• Confirm the device is on the same local network as the Cortex daemon
• Note your Cortex daemon IP address and port — Cortex listens on TCP port 2575 by default
• Windows users: TCP port 2575 must be open in Windows Defender Firewall

2. Device Settings

Every HL7-capable analyzer has a menu for network/LIS configuration, though the exact path varies by vendor. Look for one of the following in your device's menu:

• LIS Settings / LIS Configuration
• Network Settings → Host Communication
• Communication → External Connection
• Setup → Output → HL7

Regardless of menu path, configure the following values:

After saving, restart the device if prompted.

3. Test Transmission

1. Run a test sample or QC sample on the device
2. After results appear, use the device's Send to LIS / Transmit / Export function
3. Open Cortex Studio → Devices tab — the device should appear as Online
4. Check the Cortex daemon log to confirm the HL7 message was received and parsed

4. Troubleshooting

Device does not appear Online in Cortex Studio

• Verify the IP address entered on the device matches the Cortex daemon host
• Confirm port 2575 is not blocked by a firewall or router

Open TCP port 2575 in Windows Defender Firewall:

netsh advfirewall firewall add rule name="Cortex 2575" dir=in action=allow protocol=TCP localport=2575

Check that the device and Cortex daemon are on the same subnet (e.g., both on 192.168.1.x).

Results received but not parsed correctly

• Confirm the device is transmitting standard HL7 v2.x segments (MSH, PID, OBR, OBX)
• Check the Cortex daemon log for parse errors: cortex tail
• If the device uses a non-standard HL7 dialect, contact Vetigen support with a sample HL7 message

"Connection refused" error on device

• Verify the Cortex daemon service is running
• Confirm the daemon is bound to the correct network interface (not only 127.0.0.1)

Results arrive but are not matched to a patient

• Ensure the sample ID on the device matches an open order in Cortex Studio
• Check that the PID or OBR segment contains a recognizable patient or accession ID

5. Frequently Asked Questions

Q: Which HL7 versions does Cortex support? A: Cortex supports HL7 v2.3, v2.4, and v2.5. If your device uses a different version, contact support.

Q: Does bidirectional mode work? A: Cortex supports Host Query (bidirectional) for devices that implement the QRY/ORF or ORM/ORR workflow. Check your device documentation for Host Query support.

Q: My device uses a serial/RS-232 connection, not TCP/IP. Is it supported? A: Serial connections require a serial-to-TCP bridge (e.g., a terminal server). Once bridged to TCP, the setup is the same as above.

Q: Can I change the Cortex HL7 listener port from 2575? A: Yes. The port is configurable in the Cortex daemon settings. If you change it, update the device settings to match.

Q: Multiple devices — same port? A: Yes. Port 2575 uses a shared listener. Cortex identifies each device by source IP and the SendingApp field (MSH-3) in the HL7 header.