Rhapsody Developer

Hybrid Role

Interview Process:
Virtual Interview via MS Teams. A screenshot photo of candidate will be required for any interviews as well as a vendor present at beginning of virtual interview to validate candidate.

Remote or On-site:
Accepting local candidates and non-local candidates willing to relocate at their own expenses with no delays. Position will be hybrid, in office 2 days a week upon start and there is NO REMOTE ONLY option.

Responsibilities include, but not limited to:

• Responsible for developing solutions for new use cases
• Develop Interfaces based on the business requirements and specifications
• Create technical requirements and system design based on the business requirements
• Develop custom filters as required using Rhapsody Developer Kit (RDK)
• Create mappers, mapper definitions using EDI message designer
• Write JavaScript code with on Rhapsody using JavaScript(v1) and JavaScript (v2) filters
• Develop API calls for SOAP, REST and web service calls.
• Data format translations from HL7v2, HL7 V3, FHIR, CCDA, XML, JSON and flat file as required
• Working on CDA mapping and conversions
• Prepare code review SUITE SDLC documents
• Develop database connections for MSSQL or Oracle databases
• Develop TCP, HTTP, LLP and OAUTH connections as per the standards
• Responsible for overall system design
• Responsible for overall code and configuration

Skills:

Required technical and health care IT skills:

• JavaScript programming
• SQL
• XML
• HL7 version 2.x messaging
• HL7 FHIR
• CDA standards and related document types
• Health care vocabularies; LONIC, SNOMED, Rx Norm
• Health Information Exchange (HIE) technology
• Integrating the Healthcare Enterprise (IHE)
• Implementing solutions based on Implementation Guides

Desired Rhapsody skills include:

• Using latest Health Rhapsody Integration Engine (7.x)
• Using Rhapsody Developer Kit (RDK) to create custom filters, mappers, etc.
• Custom message payload translation from one format (e.g., JSON, XML, HL7) to a different format (e.g., proprietary/legacy format)
• Experience using web services, SOAP, REST, OAUTH, TCP-connections, LLP, etc.
• Experience using transport encryption/security; TLS, mutual authorization via certificates, etc.