Integration Specialist

Software/EHR Integration Engineer — MuleSoft Integration LayerRequirements5. Deliverables:Solution Design DocumentArchitecture for outbound and inbound flowsTenant configuration modelTransformation mappingsOutbound Integration FlowsBuilt and tested MuleSoft flows for:JSON → FHIR R4JSON → HL7v2 (HTTPS)JSON → HL7v2 (MLLP)Kafka Ingestion ConnectorConsumer accepting standardized clinical events from the event streamInbound Query ConnectorsBuilt and tested MuleSoft EHR connectors for:EpicCernerAthenaAllscriptsSupport for FHIR and/or HL7v2 query patterns, as applicable to each EHRTenant Configuration SchemaConfiguration structure enabling onboarding of new partners/destinations without code changesRetry & Delivery Tracking MechanismRetry and backoff logicDelivery outcome loggingDelivery tracking dashboardTest EvidenceUnit and integration test resultsSample message traces for each format and destination typeDocumentationOperations runbookConfiguration guide for onboarding new tenantsMapping and transformation reference 6. Roles & ResponsibilitiesConsultant / Integration Engineer will:Design and implement outbound and inbound flows per the scope above. - Define and document the tenant routing/configuration schema. - Implement error handling, retries, and delivery tracking. - Provide testing evidence and documentation for handover. - Participate in design reviews and status check-ins with the internal team.Client / Internal Team will:Provide access to sandbox/test instances of relevant EHR systems (or test harnesses simulating them). - Provide sample data, existing standardized JSON schema, and any existing tenant configuration conventions. - Provide credentials, network access, and security approvals required for connecting to EHR/partner systems. - Review and approve design documents and deliverables at agreed checkpoints. 7. Required Skills & QualificationsProven experience with MuleSoft (Anypoint Platform) — API design, DataWeave transformations, and connector development/configuration.Hands-on experience working with MuleSoft’s EHR connectors, integrating with systems such as Epic, Cerner/Oracle Health, Athena, or Allscripts — direct experience with multiple is preferred.Working knowledge of HL7 v2.5 message structure and MLLP transport.Working knowledge of FHIR R4 resources and RESTful FHIR APIs.Experience with Kafka (producer/consumer patterns).Understanding of healthcare data privacy/security requirements (e.g., HIPAA) as they apply to data-intransit and access control.Experience designing multi-tenant, configuration-driven integration systems is a strong plus.