Dynamic and results-driven Integration Interface Specialist with over two decades of success leading a wide range of corporate IT initiatives. Proven track record in designing and implementing integrated solutions that align with and support strategic business objectives. Adept at bridging the gap between technical systems and operational needs to create robust, scalable environments.
Core Specialties:
- Design and development of Microsoft and Oracle SQL databases
- HL7 ancillary systems integration
- Intersystems Ensemble and IRIS solutions
- Legacy systems expertise including eGate, DART, JDBC, and custom interface components
Professional Highlights:
- Deep expertise in Intersystems technologies, particularly Ensemble and Cache ObjectScript, developed through hands-on problem-solving and active engagement with the Intersystems Developer Community.
- Known for a self-driven learning style—asking the right questions, exploring solutions independently, and collaborating effectively when needed.
- Strong background in legacy integration platforms, with years of experience developing and maintaining systems and handling non-standard integration challenges.
The Enterprise Application Developers (Web Team) that develop our External Patient facing Applications are not used to trying to connect to something other than Microsoft SQL from .Net. So, trying to find a way to expose this via a REST application would be helpful and less time consuming then trying to figure out the InterSystems Drivers to connect via ODBC/JDBC from .Net.
That is why this was concerning; I didn't want to grant %Development to this new user I was going to create for this purpose. Any suggestions on what else I could do?
Creating a REST Service within InterSystems is rather a new concept for me since I am used to the Interoperability (HL7, JDBC, etc..) world. I found some examples out on Open Exchange and other posts that I am trying to figure out how I can mold it into something appropriate for this Use Case.