Senior Integration Engineer (US)

Ovii's Interpretation of the Role

The Senior Integration Engineer will own the flow of clinical data and AI agents across Innovaccer's on‑premise platform, building secure HL7, FHIR and emerging agent interoperability interfaces. The role requires deep healthcare integration expertise, strong API design skills, and the ability to work directly with customer integration teams in a remote‑first environment.

Role Snapshot

• Own clinical data integration pipelines
• Design and implement HL7 v2 and FHIR R4 interfaces
• Build agent interoperability surfaces (MCP, A2A)
• Ensure secure, network‑isolated connectivity (TLS, certificates)
• Collaborate with customer integration teams
• Maintain integration engine tooling (Mirth/Rhapsody)
• Develop Python or Java integration services

Must-Have Requirements

• HL7 v2 (MLLP transport)
• FHIR R4
• REST API design
• OAuth2
• Mutual TLS
• Python or Java
• Clinical terminologies (SNOMED CT, LOINC, ICD‑10, CPT)
• healthcare integration
• interoperability engineering
• B.E., B.Tech., or M.Sc. degree in Computer Science or related technical field

Nice-to-Have Signals

• SMART on FHIR
• Model Context Protocol (MCP) / Agent‑to‑Agent (A2A)
• Integration engine experience (Mirth/Rhapsody or equivalent)
• agent interoperability protocols

Work Setup

• Location: United States
• Work mode: REMOTE
• Remote scope: COUNTRY_RESTRICTED
• Remote countries: United States
• Employment type: Full-Time

Eligibility Gates

• Work authorization: must be authorized to work in the United States (E‑Verify)
• Visa sponsorship: no

Not Specified in JD

• Salary range
• Visa sponsorship
• Coding test
• Portfolio
• GitHub
• Cover letter

What You'll Likely Work On

• Build and operate inbound HL7 v2 feeds (ADT, ORU) over MLLP with acknowledgment handling and replay
• Design outbound clinical delivery paths through gateway‑controlled egress in a default‑deny network model
• Implement FHIR R4 APIs and map resources to standard implementation guides, handling terminology translation
• Create MCP servers and A2A flows with proper authentication, authorization, and mutual TLS
• Define integration patterns that meet strict network isolation requirements, including certificate management
• Partner with customer integration teams for connectivity setup, interface testing, and cut‑over of clinical feeds

Good Fit If You Have

• Experience with SMART on FHIR is a plus
• Familiarity with integration engines such as Mirth or Rhapsody
• Ability to quickly learn emerging agent interoperability standards