Sr Health Interoperability Engineer
Listed on 2026-06-18
-
IT/Tech
Data Engineering, Data Warehousing
At Commence, we’re the start of a new age of data‑centric transformation, elevating health outcomes and powering better, more efficient process to program and patient health. We combine quality data‑driven solutions that fuel answers, technology that advances performance, and clinical expertise that builds trust to create a more efficient path to quality care.
Job TypeFull‑time
RequirementsThe Senior Health Interoperability Engineer is a critical role that will help establish dedicated interoperability ownership within the Data & Analytics organization. This position will serve as the technical authority on healthcare data exchange standards - designing integrations across EHR systems, federal health agencies (CMS, VA, DHA), commercial payers, and health information exchanges - and will own the data modeling work required to map source health data structures into FHIR US Core and, where applicable, into OMOP CDM for research and analytics use cases.
Standards& Integration
- Design and implement FHIR R4‑compliant APIs and integration pipelines across EHR systems (Epic and others), federal payers, and commercial health clients, with conformance to US Core Implementation Guide requirements.
- Own HL7 v2.x message processing and EDI X12 transaction pipelines (837, 835, 270/271, 278) from architecture through production support.
- Build and maintain federal and commercial health data pipelines - with an initial focus on CMS - aligned to the CMS Interoperability Final Rule, Da Vinci Implementation Guides (PDex, PAS, CDex), and TEFCA exchange requirements; scope expands to VA, DHA, and commercial payer integrations over time.
- Establish and document HIE integration patterns, federated exchange workflows, and API contract standards for internal and client‑facing use.
- Model source health datasets – claims, clinical, and administrative – into FHIR US Core resource profiles, ensuring conformance to required and must‑support elements across patient, encounter, condition, observation, and related resource types.
- Design and maintain mapping logic from proprietary and standard source formats (HL7 v2, EDI, flat file, EHR extracts) to FHIR US Core‑compliant representations.
- Lead OMOP CDM transformation work: translate FHIR‑mapped clinical data into OMOP standard vocabularies and domain tables (Person, Visit, Condition, Drug, Measurement, Observation) to support research and population health analytics use cases.
- Build and maintain vocabulary mapping assets (ICD‑to‑SNOMED, CPT‑to‑SNOMED, LOINC, RxNorm) required for OMOP conformance and cross‑study comparability.
- Collaborate with the analytics and data science team to ensure OMOP‑structured data is properly exposed for cohort definition, quality measurement, and ML feature engineering.
- Partner with the Sr. Data Engineer and Sr. Solutions Architect to embed interoperability and data modeling standards into the core stack: AWS, Databricks, Postgres, and SQL Server.
- Author and maintain integration specifications, data dictionaries, mapping documentation, and exchange pattern standards.
- 7+ years of hands‑on experience in healthcare data exchange and interoperability engineering.
- Deep expertise in HL7 FHIR R4 and US Core IG; proficiency with SMART on FHIR authorization patterns.
- Demonstrated experience mapping source health data (claims, clinical, ADT) to FHIR US Core resource profiles.
- Hands‑on experience with HL7 v2.x and EDI X12 transaction processing (837, 835, 270/271).
- Support customer data integrations with HL7v3 C-CDA/CDA/CCD and Document Query/Retrieval of IHE profiles.
- Experience with EHR system integrations (Epic, Cerner, or equivalent).
- Working knowledge of OMOP CDM structure, standard vocabulary mapping, and ETL design for clinical data.
- Strong SQL and data modeling skills; experience on cloud‑based data platforms (AWS/ Databricks preferred).
- Familiarity with the CMS Interoperability Final Rule, 21st Century Cures Act, and TEFCA exchange framework; familiarity with VA, DHA, or commercial payer data exchange environments a plus.
- Experience implementing Da Vinci Implementation Guides (PDex, PAS, CDex,…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).