|
Welcome to the UltraPort HL7 TCP/IP . The NEXT generation of our award winning Router products. The UltraPort is smaller, faster and more flexible than any of our previous HL7 sending products and works with any HL7 standard TCP/IP , such as the UltraPort HL7 Listener.
 The UltraPort Router Main Window Great Features
| • | The Developer's License. A (slightly) restricted functional license for less than 20% of the retail price of it's production equivalent. See Developers License for more information! |
| • | 64 Bit Compatible! No problems working with MS Windows newest operating systems! |
| • | A FREE API toolkit for software developers using Microsoft Visual Studio .Net! With the UltraPort Proxy Toolkit, you can basically make any or all of your listeners an integrated part of YOUR own custom integration software. Have HL7 messages forwarded directly into your application where you process them however you like! And all with about 10-15 lines of code! |
| • | Run as a MS Windows Service OR as a regular Desktop Application directly from the configuration program! |
What's New in version 2.0?
| • | An issue was reported whereby IF you had checked option #7 in the Global Settings (HL7 Message Optimization) then any HL7 message field which was a REPEATING field was being truncated if it contained more than 25 repeating elements. This has been fixed. |
| • | In the router profile optional settings the wait for acknowledgement timeout allowable values has been increased from 5 seconds to 30 seconds. |
| • | In the router profile optional settings the acknowledgement retry count allowable values has been increased from 5 to 15. |
What's New in version 1.6.1?
| • | A clarification and fix was put in place to address issues of excessive CPU Usage being reported. The issue could occur when the target HL7 listener would close the TCP/IP connection during idle time (if the Keep Connection Open flag in the Router Profile is checked) or if the connection to the target listener was force closed during message transmission (either by the listener, a network outage, or blockage). This could result in the system CPU monitor displaying excessive usage (50-100%) which is caused by the .Net framework's internal code. While the CPU monitor would show excessive CPU usage, it does NOT significantly impact system performance (much like the System Idle process). See HERE for more information. |
| • | The CONNECTION DROPPED event is now being logged to each profiles LOG file if your system log level is not set to NONE. |
What's New in version 1.5.4?
| • | A minor bug was fixed in that file maintenance was not purging aged log / archived files correctly. The bug was data-harmless in that the files were being left on the file system longer than configured rather than being purged too soon. |
| • | The CONNECTION FAILED event is now being logged to each profiles LOG file if your system log level is not set to NONE. |
See GETTING STARTED for your next step!
|
