Job Seekers, Please send resumes to resumes@hireitpeople.com
Consultants will have to work on west coast time.
Highlights
- No production support
- They develop new interfaces (approx. 120 hours), and at times enhance existing interfaces (approx. 40 hours).
- Client customizes their own middleware product, the interface engine.
Need 2 years’ experience on the “Engine” side, not just 2 years of HL7 experience.
Similar middleware Engines are:
- Client leverages a non-common middleware platform for the healthcare sector but experience with any of the following major interface engines utilize many of the expected concepts and technologies (Rhapsody, Corepoint, Cloverleaf, eLink, eGate, Ensemble, Mirth, Impact (Sybase), OpenLink, OpenEngine, Iguana).
- Experience working in a very matrixed organization is important.
· A minimum of two years’ experience working in the Healthcare IT sector dealing with major integration engines is required. Client leverages a non-common middleware platform for the healthcare sector but experience with any of the following major interface engines utilize many of the expected concepts and technologies (Rhapsody, Corepoint, Cloverleaf, eLink, eGate, Ensemble, Mirth, Impact (Sybase), OpenLink, OpenEngine, Iguana).
Questions for consultants follows.
· Question 1: What does the application they support do? Internal Application or Web Application?
Answer: This role deals with authoring and modifying real time healthcare data interchanges using common industry formats such as HL7, EDI / ASII X12, and Batch file secure deliveries. The application is a middleware engine that is responsible for receipt, data transformation, and transmission of Health Care based transactions. The engine is a sever side install and is not web based development.
· Question 2: Is this new development, enhancements of an existing application or production support?
The vast majority of current openings deal primarily with net new development and enhancement of interfaces. The openings we are currently looking to fill are NOT production support or operations based.
· Question 3: If new development: what % design vs development?
The current mix of design vs. development is close to 50/50 split.
· Question 4: Will this be Server or Client side development?
While some projects can span each – the lion’s share of projects are server side development. The purpose of the middleware engine is to receive data from a sending system, transform or massage data as applicable to the project requirements, and deliver the transactions to one or many destination systems.
· Question 5: What Operating System is used for development? And deployment?
The Servers deployed for production, test, and development environments windows server and IBM AIX based. Windows Server can span from Windows Server 2003 – Windows Server 2012.
· Question 6: What languages will be used? Versions? Other than these languages, what development background might be important?
The Client's middleware technology platform is a proprietary based scripting language. Experience with and concepts related to the following scripting and programming languages is preferred (VBScript, JavaScript, C#, C++, SQL)
· Question 7: What database will interface with this application? How important is database experience in this role?
Basic understanding of database concepts is preferred. The middleware engine uses queuing technology that does not directly store transmissions in a SQL relational database.
· Question 8: What other APIs/tools will be needed? EJB, JSP, Servlets, JMS, XML
Experience with HL7, XML, and EDI message formats is strongly preferred.
· Question 9: What Application Servers/Middleware interface with this application?
Client has more than 100 vendor applications that are used in our technology footprint. Some of the major players which the middleware engine will be leveraged are Cerner, MS4, Invision, GE Centricity Business, and Allscripts.
