Enterprise Integration Architect

HealthPartners is currently hiring an Enterprise Integration Architect . This role is responsible for defining the overall architecture of HealthPartners’ applications across web platforms, administrative systems, infrastructure, and data environments. The Enterprise Architect ensures that application development and enhancements align with HealthPartners’ strategic goals and integrate smoothly within the broader technical landscape.

The Architect connects systems and platforms across a complex healthcare technology environment, including EHRs, health plan administrative systems, cloud services, internal applications, external vendors, and health information exchanges. The role focuses on designing and governing enterprise integration and interoperability while ensuring alignment with regulatory and industry standards. Serving as a technical bridge, the Architect partners with business teams, internal technology groups, and external vendors to shape integration approaches that are scalable, compliant, and fit for enterprise use.

This role is grounded in hands‑on software engineering and integration development experience. The ideal candidate has built and operated integration solutions at scale, implementing APIs, messaging pipelines, and event‑driven systems. They engage with development teams as a technical peer, design integration patterns with practical implementation detail, and own the standards and governance that ensure integrations are reliable, secure, and maintainable over time.

This is a replacement position following the departure of a long‑tenured employee. The role reports to the Director of IT Enterprise Architecture and is part of a collaborative team of professionals.

Required Qualifications

• Bachelor’s Degree or equivalent experience.
• Twelve (12+) years of progressive experience in software engineering, including:
  • Three (3) years of hands‑on integration development
  • Four (4) years of architectural accountability
  • Four (4) years of project management experience
• Experience in healthcare IT environments (payer, provider, or health system).
• Demonstrated experience integrating AI tools (e.g., GitHub Copilot, Claude, ChatGPT) to accelerate software development, documentation, or workflows.
• Software engineering foundation: Direct experience building integration solutions – implementing REST APIs, message‑based integrations, ETL/ELT pipelines, or event‑driven systems in production environments using languages such as Java, JavaScript, or Python.
• Healthcare interoperability: Working knowledge of HL7 FHIR, HL7 v2, and X12 EDI healthcare transaction standards.
• Familiarity with integration security patterns – OAuth 2.0, SMART on FHIR, mTLS, API key management, and PHI‑aware data handling.
• Business engagement skills: Demonstrated ability to work directly with business stakeholders – leading requirements discovery, translating operational data exchange needs into integration architecture, and validating that integration solutions reflect business intent throughout delivery.
• Strong analytical and communication skills – able to decompose complex integration requirements and convey designs to both technical and non‑technical audiences.
• Proficiency with back‑end and front‑end technologies and frameworks.
• Proficiency in database technology and modeling.
• Effective communication skills across technical and non‑technical audiences using verbal and written forms.
• Excellent troubleshooting and diagnostic skills.

Preferred Qualifications

• Experienced with Linux, Windows, PostgreSQL, Oracle, and SQL servers.
• Familiarity with Java frameworks such as Spring Boot and Python API frameworks such as fastAPI.
• Familiarity with Event‑Driven Architectural models and approaches.
• Hands‑on experience with one or more integration platforms: Kafka, Azure Integration Services, InterSystems HealthShare, Rhapsody, or equivalent.

Hours / Location

• M‑F; core business hours
• This is a hybrid role with an expectation of being onsite 3-4 days per week.

Responsibilities

• Establish integration design standards: API design guidelines, message schema governance, error handling patterns, retry and idempotency strategies, and versioning policies.
• Architect event‑driven and streaming integration patterns for real‑time data exchange across clinical, operational, and analytical systems.
• Lead HealthPartners' healthcare interoperability architecture – defining implementation strategy for HL7 FHIR, HL7 v2, X12 EDI, and CCDA across care and plan domains.
• Apply direct integration development experience to guide implementation teams – reviewing integration code, message transformation logic, API implementations, and pipeline designs with technical depth.
• Champion integration observability – distributed tracing, message tracking, alerting, and structured logging as non‑negotiable requirements in integration design.