|
<< Click to Display Table of Contents >> Navigation: »No topics above this level« Introduction |

Welcome to the UltraPort SQL Schema Engine Extender (Version 4.0).
Disclaimer: It is assumed if you are reading this that you are currently a HermeTech customer and are familiar with using the UltraPort SQL Schema Engine software. If not and you are interested then we recommend that you contact customer service.
The Schema Engine Extender is a simple application that replicates the "Inbound Processor" functionality of the UltraPort SQL Schema Engine with a few very unique exceptions.
One major difference is that while in the SQL Schema Engine you may only create 1 inbound processor for each database schema, in the Schema Engine Extender you can create as many processor profiles as you like, all importing HL7 messages from different file folders into the same UltraPort SQL Schema simultaneously.
Another major difference is the development platforms, .Net 5 (outdated), .Net 6, and .Net 7.
The UltraPort SQL Schema Engine software has always been developed using the Microsoft .Net Framework. It was initially released targeting the .Net Framework version 2.0. Then over the course of its release history it was upgraded to the .Net Framework 4.0 then to the .Net Framework 4.5.2 and finally the latest versions use the .Net Framework 4.6.2. This all follows our company policy of making sure that our commercial software is always targeting a .Net platform that we consider to be comfortably "middle-aged", well vetted by software developers, enjoys wide distribution world wide, bugs and security vulnerabilities found and fixed.
Then in 2020 along came .Net 5, which Microsoft insisted was THE FUTURE of Microsoft development. The only problem is that about every 6 months since 2014 or so Microsoft has released or announced some platform or another which it has also announced loud and wide was THE FUTURE. But this time, with .Net 5, we think that maybe, just maybe, they might. just. be. serious. So, when, on a fine November Spring day in New Zealand, an intern popped up in a staff meeting and asked "Why don't we try porting our very successful Schema Engine (Enterprise) Visual Studio API to .Net 5 and actually create something with it?", she was met with haughty derision and many a guffaw. This .Net 5 of which she spake had only been released a few days before, by Microsoft, and they were claiming that it is now THE FUTURE. So, after a round of laughter from her elders (including this author), she was sent off to her room with no dinner, and told to think hard about what she had done.
Well, apparently she did just that, She came back to us 2 weeks later with a sound design plan, a budget, and a working prototype. The product for .Net 5 was released by Xmas 2020 and now for Xmas 2022 (almost) we have 3 different installers for version 4.0 which covers .Net 5, .Net 6 and .Net 7!
And that is how we got from there to here.
|
Performance Benchmarks (Amazing!)
**All benchmarks used the optimum benchmarking environment for importing HL7 messages.
|
Your Next Steps:
Review the System Requirements.
Download the latest version of the software:
• Installer for .Net 5 (outdated).
See Also: