Senior healthcare interoperability leader focused on EHR interoperability, EMR connectivity, and enterprise delivery across hundreds of ambulatory and acute care systems.
Built credibility across implementation, support, enterprise delivery, and product ownership, with senior-level judgment in EMR connectivity strategy, launch governance, and cross-functional execution for healthcare SaaS platforms.
Open to remote senior healthcare interoperability, EMR connectivity, and healthcare SaaS product or delivery leadership roles.
Credibility Highlights
Proof points
Healthcare interoperability, EMR connectivity, and enterprise delivery scope
18+ Years
Healthcare interoperability delivery
Hundreds
Ambulatory + acute care EHR/EMR systems
22-Person Team
Built and led a standalone support org
8-Month Integration
Post-acquisition workflow and roadmap alignment
A quick view of 18+ years of delivery scale, leadership scope, and interoperability outcomes across healthcare SaaS programs.
Built career-long interoperability depth across database and ODBC connectivity, interface engines, APIs, FHIR, SMART on FHIR, webhooks, CDS Hooks, and RPA-style automation workflows.
Created the first standalone support function, formalized escalation paths and SLAs, and gave implementation and engineering teams a cleaner signal on recurring integration issues.
Unified teams, delivery workflows, and roadmap priorities after acquisition so platform transitions could continue without losing launch momentum.
Led cross-functional release readiness for remote testing workflows, HL7 orders/results processing, and high-visibility operational coordination.
This is the high-level view of how I operate. The full role progression, case study detail, and capability inventory live on the Experience, Case Studies, and Skills pages.
The work is not just connecting systems. It is managing EMR connectivity across hundreds of partner-system variations, mixed technical standards, launch risk, and post-live accountability.
Ambulatory and acute care environments bring different workflows, mapping conventions, data-quality issues, vendor dependencies, and readiness constraints into the same delivery portfolio.
Programs often span HL7 v2, FHIR DSTU2, R4, and R5, SMART on FHIR, CDS Hooks, interface engines, REST APIs, webhooks, databases, and ODBC in the same operating model.
Interoperability leadership still owns testing readiness, cutover decisions, hypercare stability, support handoffs, SLA performance, and remediation prioritization after release.
The delivery path crosses engineering, QA, support, implementation, security, client teams, vendors, and executives who each own a different part of readiness.
This work has included direct people leadership, CTO-level partnership, and operational accountability across interoperability programs where launch quality and post-live stability both matter.
The product work is not abstract roadmap language. It is deciding how interoperability capabilities should be standardized, sequenced, launched, and supported across real EMR connectivity constraints.
A short preview of the role progression. The Experience page has the full timeline, scale signals, and role-by-role detail.
ELLKAY, LLC
January 2024 - Present
Owns EHR interoperability discovery, scope definition, testing readiness, and go-live coordination for healthcare connectivity programs spanning mixed legacy and modern integration patterns, grounded in 18+ years of implementation and delivery context.
ELLKAY, LLC
January 2020 - December 2023
Led enterprise delivery workstreams for high-volume interoperability programs with compressed onboarding timelines, strict operational coordination needs, and partner-system variation built from hundreds of ambulatory and acute care environments.
Two quick previews here. The Case Studies page expands each example into a full context, constraint, decision, execution, and outcome narrative.
Case Study
Health system with inpatient and ambulatory workflows, multiple technical owners, and mixed legacy-to-modern interoperability priorities.Large health system aligning legacy lab and order interfaces with a more modern interoperability roadmap across inpatient and ambulatory workflows.
Decision: Standardized mapping expectations, readiness checkpoints, and launch evidence so teams could make cleaner go or no-go decisions across multiple workstreams.
Why it matters: Shows the ability to turn complex EMR connectivity work into a repeatable operating model that can scale beyond a single project.
Case Study
National program with compressed rollout windows, HL7 orders/results coordination, and high operational visibility.National lab program supporting institution onboarding under compressed timelines and strict data integrity requirements.
Decision: Introduced phased onboarding governance with explicit dependency owners, test gates, and hypercare expectations before production promotion.
Why it matters: Demonstrates leadership in healthcare programs where scale, timing pressure, and operational control matter as much as the interface build itself.
Standards, care settings, and implementation constraints used across career-long EHR interoperability work.
Product strategy and program practices used to keep delivery credible from discovery through launch.
My operating model is built for healthcare programs where EHR interoperability spans mixed connectivity models and where dependency management, launch quality, and post-live stability matter as much as feature delivery.
Aligned to senior interoperability, EMR connectivity, and healthcare SaaS product or delivery leadership roles where deep implementation context still matters.