EMR Integration Architect

EMR Integration ArchitectLocation : US - Remote (onsite travel to Chicago, IL twice a month with expenses paid)CTH for the right candidateImmediate startJob Description / Duties/ Work ExperienceHealthcare integration engine — production depthMust have built, deployed, and operated a healthcare integration engine (Mirth Connect, Rhapsody, Azure Health Data Services, or equivalent) in a live clinical environment. Not configured templates — built channels, transformers, and error handling from code.FHIR R4 — hands-on implementationMust have implemented FHIR R4 APIs in a production provider or payer environment. Must be able to name specific FHIR resources, explain ConceptMap usage, and describe how they have handled proprietary EMR code sets that do not map cleanly to SNOMED CT or LOINC.Multi-EMR integration experienceMust have built integration adapters across at least two of: Epic, Cerner/Oracle Health, Meditech. Not evaluated EMRs — built production connectors against their APIs in a live hospital environment.Write-back architecture — modern approachMust be able to describe a SMART on FHIR write-back implementation — OAuth2 scopes, CPOE approval governance, signed order flow, error handling on failed write-back. HL7-era database coordination answers are insufficient.Integration Engines & Middleware•   Mirth Connect (NextGen) — channel build, JavaScript transformer development, error handling, monitoring (certification preferred)•   Rhapsody, Azure Health Data Services, or Google Cloud Healthcare API — production deployment experience a strong plus•   Interface engine configuration, version management, and operational governance in a clinical environment•   Connector design for both inbound (EMR → hub) and outbound (hub → EMR) data flowsHealthcare Interoperability Standards•   FHIR R4 / US Core — production implementation, resource-level depth (Patient, Encounter, Observation, MedicationRequest, Condition, DiagnosticReport, AllergyIntolerance)•   SMART on FHIR — OAuth2 authorization, read and write scopes, token management, EMR-specific scope approval processes•   HL7 v2.x — ADT, ORM, ORU, MDM message types. Interface engine configuration and transformation•   CCDA — clinical document exchange, section mapping, data reconciliation•   X12 EDI — 270/271, 837, 835 (payer integration experience a plus)•   Clinical vocabulary standards — SNOMED CT, LOINC, RxNorm, ICD-10. ConceptMap design and proprietary code set mappingEMR / EHR Platform Depth•   Epic — Interconnect API, Bridges, FHIR R4 sandbox, SMART on FHIR, Ambulatory and Inpatient workflow architecture. Epic certification strongly preferred.•   Oracle Health / Cerner — FHIR R4 Millennium APIs (Ignite), HL7 ADT integration, Open Platform write-back•   Meditech — REST/HL7 connectors for both Expanse (FHIR R4) and legacy MAGIC (HL7 v2). Dual-path adapter design experience•   Aggregators — InterSystems HealthShare, Redox, LK Health. Experience selecting and deploying aggregator platforms for multi-hospital environmentsArchitecture, Engineering & Data•   Distributed systems architecture — API gateway, protocol routing, session cache (Redis), event bus (Kafka or equivalent), normalization engine design•   HIPAA-compliant system design — encryption at rest and in transit, RBAC, immutable audit trail (7-year retention), PHI data residency controls•   SQL and Python — data validation pipelines, reconciliation, transformation automation•   Cloud platforms — AWS or Azure in a healthcare data environment. Azure Health Data Services experience a strong plus•   Security — TLS 1.3, OAuth2, VPN, SFTP, NIST 800-53 security controls awareness•   Agile delivery — sprint planning, backlog governance, Jira or equivalent. Scrum Master certification a plusPreferred Qualifications:PREFERRED EXPERIENCE•   10+ years in healthcare IT with a primary focus on EMR integration and interoperability — not a generalist background•   Experience leading a blended onshore/offshore engineering pod in a client-facing delivery engagement•   History of delivering multi-hospital EMR integration projects against commercial deadlines•   Clinical decision support (CDS) system architecture or physician-facing application design experience•   Experience with AI/ML integration in a clinical context — ambient documentation, acuity classification, clinical summarization•   Current Mirth Connect certification (NextGen Mirth Certified Fundamentals or higher)•   Epic certification — Ambulatory, Inpatient, and/or Orders. Current certifications strongly preferred•   AWS Certified Solutions Architect or Azure equivalent in a healthcare data context•   PMP or equivalent project management certification•   Prior experience at a healthcare IT consultancy, EMR vendor, or large health system IT department