Integration Engineer | Epic & Oracle Health Interoperability | FHIR, HL7 & EHR Integrations

Dawson Riggs

Healthcare Integration Engineer

I help healthcare technology teams deliver reliable EHR integrations that work in real-world clinical and operational environments.

My work sits at the intersection of engineering, implementation, production support, and customer workflows—designing, troubleshooting, and improving integrations across Epic, Oracle Health/Cerner, Meditech, NextGen, eClinicalWorks, FHIR, HL7, REST APIs, SOAP APIs, and SQL-backed production systems.

Epic integrationsOracle Health/CernerFHIR + HL7REST + SOAP APIsSQL + production systems

View LinkedIn View Case Studies

Positioning

Healthcare integration work, grounded in implementation reality.

I started my career at Epic Systems as a MyChart Technical Solutions Engineer supporting patient experience workflows, telehealth integrations, and large health system go-lives. That foundation shaped how I think about interoperability: the technical path has to work, but it also has to survive operational reality.

At Luma Health, I moved from Enterprise Technical Support Engineer to Implementation Specialist to Integration Engineer, working across EHR connectivity, healthcare workflows, customer implementation, escalation support, and production reliability.

My strongest work happens in the gray area where technical systems, customer needs, implementation constraints, and operational reality intersect. I focus on making system behavior visible, translating ambiguity into concrete next steps, and staying with the problem until the integration is dependable.

Technical systems

Clinical workflows

Customer operations

Implementation delivery

Intersection

Reliable healthcare integrations

Focus areas

EHR interoperability, production reliability, and workflow-aware delivery.

The work spans technical implementation, solutions engineering, customer communication, support escalation, and the operational details that determine whether an integration actually works in production.

Healthcare Interoperability

Connecting healthcare SaaS products to clinical and operational systems with careful attention to data exchange, workflow impact, and long-term maintainability.

EHR Integrations

Implementing and supporting EHR integrations across Epic, Oracle Health/Cerner, Meditech, NextGen, and eClinicalWorks environments.

Implementation & Go-Live Support

Guiding integrations from configuration and validation through launch readiness, customer communication, go-live support, and post-launch stabilization.

Production Troubleshooting

Debugging FHIR, HL7, REST API, SOAP API, SQL, and workflow issues with a calm, structured approach to restore reliability and reduce downtime.

Workflow Systems

Translating healthcare workflows into practical integration behavior, data mappings, automation logic, and supportable implementation patterns.

Technical Customer Ownership

Bridging engineering, implementation, support, customer success, and health system stakeholders with clear communication and accountable follow-through.

Implementation

Delivery readiness

Validation

Delivery readiness

Go-live

Delivery readiness

Monitoring

Operational reliability

Troubleshooting

Operational reliability

Optimization

Operational reliability

Experience highlights

From Epic MyChart to healthcare SaaS integration engineering.

Epic Systems

MyChart TS · enterprise healthcare workflows

Luma Support

EHR issues · APIs · customer escalations

Implementation

workflow builds · validation · go-lives

Integration Engineering

FHIR · HL7 · SOAP · reliability

~90%

Epic API cost reduction

20+

customer go-lives led

400+

complex support tickets resolved

93% → 100%

Meditech PDF writeback reliability

Luma Health

Integration Engineer · Implementation Specialist · Enterprise Technical Support Engineer

Oct. 2022 – Present

Progressed across support, implementation, and integration engineering roles focused on EHR connectivity, healthcare workflow delivery, production support, and customer-facing technical ownership.

Reduced Epic API costs from $1.3M/month to $134K/month—about 90% savings—through integration and workflow optimization.
Implemented and maintained HL7 and API integrations with enterprise EHRs including Epic, Cerner, Meditech, NextGen, and eClinicalWorks.
Developed an Epic SOAP API integration workflow powering AI-enabled IVR prescription refill automation and patient self-service.
Owned the Meditech Cold Feed pipeline across implementation, debugging, code enhancements, and documentation, improving PDF writeback reliability from 93% to 100% for key customers.
Led 20+ customer go-lives by configuring integration workflows and data synchronization processes across implementation, engineering, and customer success teams.
Resolved 400+ Zendesk tickets involving complex EHR integrations, APIs, and workflow issues while maintaining a greater than 95% CSAT.

Epic Systems

Technical Solutions Engineer, MyChart

Jun. 2019 – Sep. 2022

Supported patient experience workflows, enterprise healthcare integrations, and post-go-live operational issues for large healthcare organizations using Epic MyChart.

Supported Epic telehealth workflows, including Epic Video Client (EVC) and Teladoc integrations.
Led integration and post-go-live support for 8 major healthcare organizations, aligning platform functionality with operational and clinical workflow requirements.
Diagnosed and documented 97+ recurring MyChart error patterns as MyChart Error Log Tech Lead, accelerating root cause analysis and issue resolution.
Wrote and optimized SQL queries supporting Epic’s largest patient record reconciliation initiative, with roughly 10M records matched.
Collaborated directly with healthcare organizations to troubleshoot interoperability, workflow, and production support issues across large-scale patient engagement systems.

Featured work / case studies

Field-tested stories from real healthcare integration work.

Case studies and technical lab notes grounded in production interoperability, implementation constraints, reliability work, workflow validation, and hands-on experimentation.

Operations console

Integration health

Stable

API health

Healthy

Queue depth

Low

Sync success

Healthy

Integration

Rules

APICost

Case study

Reducing Epic API Costs by 90%

How a usage-based Epic API pricing model exposed hidden integration inefficiencies—and how coordinated technical and operational changes reduced monthly costs from $1.3M to $134K without breaking healthcare workflows.

Epic integrationsCost optimizationProduction systemsWorkflow design

Read case study

Integration

PDF

FeedWriteback

Case study

Reliability Engineering for Real-World Healthcare Integrations

How an intermittent Meditech document filing issue revealed timing assumptions across APIs, SQL data, SFTP delivery, and ECM routing—and how workflow-aware retry logic improved reliability from ~93% toward near-complete delivery.

MeditechReliabilityAsync workflowsECM filing

Read case study

Integration

Layer

EHRGo-live

Field guide

Building Reliable EHR Integration Workflows

A practical guide to validating EHR workflows across configuration, data quality, permissions, timing, monitoring, and operational ownership—because green logs do not always prove workflow success.

EHR integrationsWorkflow validationGo-live readinessProduction support

Read case study

Integration

HL7

FHIRSOAP

Integration lab

HL7 / FHIR / SOAP Integration Lab

A lightweight technical sandbox for exploring interoperability workflows, payload validation, integration patterns, and implementation-oriented experimentation across HL7, FHIR, and SOAP-based systems.

FHIRHL7SOAP APIsPayload validation

GitHub Demo Explore lab

Writing / thinking

Thoughtful notes on healthcare integrations, debugging, and go-live reliability.

Published reflection

What Healthcare Integrations Taught Me About Debugging

A reflection on reading logs, reconstructing workflows, and separating signal from noise in high-stakes implementation work.

Read reflection →

Published reflection

The Gray Area Between Engineering and Implementation

Why some of the most important technical work happens between product behavior, customer expectations, and operational reality.

Read reflection →

Published reflection

Why Reliable Go-Lives Depend on More Than Code

A practical look at readiness, communication, validation, and ownership before production traffic starts flowing.

Read reflection →

How I work

Calm ownership for complex, cross-functional technical work.

Own the problem end-to-end.

Make invisible system behavior visible.

Communicate clearly across technical and operational teams.

Debug from first principles.

Design for real-world reliability.

Contact

Open to connecting on challenging healthcare integration problems.

If you're working on challenging interoperability or integration problems in healthcare, I'm open to connecting—especially around Epic integrations, Oracle Health/Cerner workflows, FHIR, HL7, implementation engineering, production troubleshooting, and reliable go-live support.

Connect on LinkedIn