> Markdown version of [/jobs/ext/2713055-integration-engineer](https://www.wearedevelopers.com/jobs/ext/2713055-integration-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Integration Engineer - **Company:** Innovaccer, Inc. - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Python (Programming Language), Network Model, OAuth, Rhapsody, Fast Healthcare Interoperability Resources, Information Technology, Health Level Seven International, Restful APIs - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/senior-integration-engineer-us-innovaccer-analytics-9000759 ## About the Role * B.E., B.Tech., M.Sc. degree in Computer Science or a related technical field. * 5+ years of healthcare integration or interoperability engineering experience. * Strong working knowledge of FHIR R4: resources, profiles, search, and implementation guides (US Core or equivalent). * Hands-on HL7 v2 experience: message structures, segments, acknowledgments, and MLLP transport. * Working knowledge of REST API design, OAuth2, and mutual TLS; SMART on FHIR experience is a plus. * Familiarity with agent interoperability protocols: Model Context Protocol (MCP) and/or Agent-to-Agent (A2A), or demonstrated ability to come up to speed quickly on emerging standards. * Experience with clinical terminologies: SNOMED CT, LOINC, ICD-10, CPT. * Professional development experience with Python or Java; integration engine experience (Mirth/Rhapsody or equivalent) is a plus. ## Description As a Senior Integration Engineer, you will own how clinical data and AI agents cross the boundary of Innovaccer's on-premise platform. On the clinical side, that means inbound HL7 v2 feeds over MLLP, outbound HL7 delivery through controlled egress, and FHIR R4 APIs that expose platform data through standard profiles. On the agent side, it means implementing the emerging interoperability protocols, Model Context Protocol (including healthcare-specific HMCP patterns) and Agent-to-Agent (A2A), that let AI agents interact with the platform safely inside a locked-down network. This role sits at the intersection of healthcare interoperability standards and agent-era infrastructure. A Day in the Life * Build and operate inbound clinical feeds: HL7 v2 message ingestion (ADT, ORU, and related event types) over MLLP, with acknowledgment handling, error queues, and replay. * Design outbound clinical delivery paths through gateway-controlled egress in a default-deny network model. * Implement FHIR R4 APIs and resource mappings against standard implementation guides, including terminology handling across code systems. * Build agent interoperability surfaces: MCP servers exposing platform capabilities, HMCP patterns for healthcare-safe agent access, and A2A flows with proper authentication and authorization. * Define integration patterns that hold under strict network isolation: certificate management, mutual TLS, and boundary-controlled connectivity. * Work directly with customer integration teams on connectivity setup, interface testing, and cutover of clinical feeds. ## Related Videos - [Why make use of an integration platform in today's software developments and infrastructure?](https://www.wearedevelopers.com/videos/758-why-make-use-of-an-integration-platform-in-today-s-software-developments-and-infrastructure) - [Rest API Antipatterns](https://www.wearedevelopers.com/videos/100208-rest-api-antipatterns) - [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect) - [REST In Peace: Why LLMs Can't CRUD](https://www.wearedevelopers.com/videos/100272-rest-in-peace-why-llms-can-t-crud) - [Enterprise Integration Is Dead! Long Live AI-Driven Integration with Apache Camel](https://www.wearedevelopers.com/videos/1606-enterprise-integration-is-dead-long-live-ai-driven-integration-with-apache-camel) - [Delay the AI Overlords: How OAuth and OpenFGA Can Keep Your AI Agents from Going Rogue](https://www.wearedevelopers.com/videos/1637-delay-the-ai-overlords-how-oauth-and-openfga-can-keep-your-ai-agents-from-going-rogue) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [Everything a Developer Needs to Know About MCP with Neo4j](https://www.wearedevelopers.com/magazine/604-everything-a-developer-needs-to-know-about-mcp-with-neo4j) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers)