Required Skills & Experience
Top Requirements:
- 8-10+ years of enterprise technology experience, including 7+ years designing enterprise integration architecture
- Healthcare integration with EMRs, clinical platforms or other regulated systems
- FHIR and HL7 with hands-on implementation
- API management, REST, async messaging, event-driven architecture, distributed systems
- Azure: API Management, Service Bus, Event Hubs/Event Grid, Logic Apps, Functions
- API and data contracts, schemas, mapping, validation, versioning and integration testing
- OAuth 2.0, OpenID Connect, managed identity, secrets and API security
- CI/CD, infrastructure as code, observability and production support for integrations
- Has worked with vendor/SI teams from architecture through production
Nice to Have Skills & Experience
Additional Skills:
- Provider, Pharmacy, HIE, payer or lab interoperability
- Homecare Homebase, WellSky, Netsmart, PointClickCare, MatrixCare, Epic or Oracle Health
- FHIR R4, SMART on FHIR, HL7 v2, C-CDA, X12, US Core
- Mirth/NextGen Connect, Rhapsody, InterSystems or MuleSoft
- Has enabled AI agents through APIs, events or MCP
- Azure Health Data Services, Databricks; HIPAA/HITRUST
Job Description
Daily Responsibilities: A large healthcare organization is looking for an Enterprise Integration & Interoperability Architect to define and govern integration architecture across its healthcare applications, EMR platforms, AI products, data platforms and external partners. This person sets reusable patterns for APIs, events, messaging and healthcare data exchange, including FHIR, HL7 and X12, across Provider and Pharmacy environments, with the goal of replacing brittle point-to-point integrations with standards-based ones. The role is hands-on: they work alongside internal and vendor teams to turn architecture into detailed designs, API and event contracts, and mappings, then review the implementation through production. They also define how AI agents can securely reach enterprise systems through governed APIs and MCP, and own the shared Azure integration services once they're set up.
- Set the strategy: Define integration target state, reference patterns, standards and modernization roadmap.
- Own healthcare interoperability: Set FHIR, HL7, C-CDA, X12 and SMART on FHIR patterns across EMRs, HIEs, labs, payers and referral partners.
- Standardize APIs and events: Define API standards (contracts, versioning, security, idempotency) and event-driven patterns on Azure.
- Integrate EMRs: Architect integrations with vended and home-grown EMRs, and build abstraction layers to reduce vendor coupling.
- Enable AI agents: Define governed API, event and MCP patterns and authorization boundaries for agent access.
- Make it reliable: Set retry, dead-letter, reconciliation, tracing and monitoring standards.
- Govern delivery: Review vendor APIs, schemas, interfaces and mappings for conformance, and drive remediation of technical debt.