ShakyJake. Is there any reason you can't convince your company to just use nHapi to "write your own" since you're already using VB instead of trying to create a scripting language (seriously? you want to create your own scripting language)?
Again, they will reject pretty much any library or framework that Microsoft doesn't directly bless. Instead of nHapi, they created their own HL7 parsing library. We just had an overview of it a couple weeks back so I haven't had the (dis)pleasure of using it yet.
The problem with our current HL7 interfaces is that they are executables that are compiled from modifiable source code
that resides on the client's server. And this source code is Visual Basic
6, not .NET. Very old and the clock is ticking to when MS will no longer support it. The company wants to eliminate this for good reason. Problem is, they want to replace VB code with a GUI-based mapping tool. Due to the near infinite variations with the HL7 implementations out there, trying to reduce it to a GUI tool
while trying to maintain the same level of customization as codeis a fool's mission.
We definitely need to chuck the VB stuff. No doubts there. However, I feel it should be replaced with an embedded scripting language that is platform agnostic -- such as Javascript, Python, or even Lua. Fast forward 20 years now, if we need to re-write the engine to some other platform we can
probablystill use the existing scripts. That's the major problem we're facing now. All those VB6 scripts will need to be rewritten to something else.
BUT, I can hear complaints now of using one of these general-purpose scripting languages (again, not MS "approved"). It may be more palatable to them if we were to create our own, small, domain-specific scripting language. Essentially that's what they're wanting now, but just confining the user to a GUI tool rather than allowing them to type it out.
TypeScript was the big one though, with a little work all of our JS now compiles, issues warnings, errors for bad parameters etc.
Yeah, we're familiar with TypeScript. We'll definitely be using it.