A comprehensive guide to the features of the DICOM Toolbox HL7 Sender & Receiver module.
Fully compliant Minimal Lower Layer Protocol (MLLP) wrapper over TCP/IP, ensuring HL7 payloads are safely framed using standard VT and FS/CR characters. Includes optional TLS/SSL layer for encrypted communication.
A powerful rules engine that allows you to define custom tokens (e.g., {{PATIENT_ID}})
and replace them with specific values in your templates right before the message is transmitted.
{{WARD}}, Value: ICU-1. Update your HL7 template's PV1
segment to include {{WARD}}. Upon clicking Send, the toolbox automatically swaps the
token for the value, making testing highly dynamic.
Import a directory of raw HL7 files or templates and rapidly fire them at a target endpoint. Allows configurable batch counts, transmission intervals, and real-time metrics (Messages Per Second).
Configure the receiver to intelligently respond to incoming messages based on specific segment values (e.g., MSH-9 Message Type). Simulate network lag or force Application Rejects (AR/AE) to test error handling.
MSH-9 = ADT^A01 triggers an AR (Reject)
response with a 2000ms delay. Send an ADT message to it and watch the sender gracefully handle the
simulated failure and timeout.
Act as a man-in-the-middle. The receiver can catch an incoming HL7 message, log it, and seamlessly forward it to another downstream host/port without breaking the connection chain.
Automatically save every received HL7 message to the local filesystem as a neatly organised text file, stamped with the exact date and time of receipt.
C:\HL7_Logs\. Leave the receiver running
overnight. In the morning, you will have a physical record of every single message that hit the port
for audit purposes.
Comes pre-loaded with standard HL7 v2.x templates (ADT^A01, ORM^O01, ORU^R01, SIU^S12). Users can freely edit these, create their own custom message structures, and save/delete them to a local JSON config.
A real-time, colour-coded traffic console that logs every SEND, ACK, TLS Handshake, and ERROR. It tracks exact round-trip times in milliseconds and displays the raw payloads.
AA (Application Accept) code
they returned.
Breaks down cryptic, pipe-delimited raw HL7 text into an easily readable, hierarchical Tree-View structure, allowing users to drill down into specific segments (MSH, PID, PV1, OBR).