EMR Integration Engineer

Role Description

This is a remote position.

CTI Staffing is partnering with a growing healthcare technology company to find an EMR Integration Engineer who can own and scale the integrations connecting their referral management platform to the major EMR systems their customers run on. This is a high-impact, foundational role — integration capacity is the direct bottleneck to the company's growth, and this person will be responsible for removing it. They are looking for someone who has done this work before, knows the real-world complexity of healthcare APIs, and can be productive from day one.

What You'll Own

• Design, build, and maintain production integrations between a referral management platform and major EMR systems, owning the full lifecycle from API authentication through ongoing support.
• Map and reconcile patient, appointment, scheduling slot, insurance, and referring-provider data across systems with inconsistent and often incomplete vendor APIs.
• Navigate real-world EMR API limitations — missing fields, undocumented behavior, partial endpoint support — and engineer around them without breaking downstream workflows.
• Onboard new EMR integrations as customer contracts are signed, scoping the work and setting realistic timelines for each platform.
• Help finish and harden an in-flight integration with the company's pilot customer scaling toward significant daily referral volume.
• Support the AI-assisted referral ingestion pipeline as volume grows, addressing exceptions requiring engineering judgment.
• Document integration patterns and decisions so the broader team can support and extend the work over time.

Qualifications

• Demonstrated, hands-on experience building EMR/EHR integrations in a production environment — not adjacent API work; you've done healthcare integration before.
• Direct integration experience with one or more of the following EMRs (in priority order): NextGen, Athena (athenahealth), ModMed, Greenway, Cerner (Oracle Health).
• Working knowledge of healthcare data and workflows: patient records, scheduling and appointment-slot logic, insurance/payer data, and the referring-provider/billing relationship.
• Strong software engineering fundamentals — this is a code-first, ownership-first role.
• Proficiency in TypeScript, or strong Node.js/JavaScript background with ability to work primarily in a TypeScript codebase.
• Self-directed and able to ramp quickly in a remote, small-team environment with minimal hand-holding.
• Clear written communication — ability to document integration behavior and decisions for both engineers and non-technical stakeholders.

Requirements

• Production EMR/EHR integration experience (hands-on, in a live environment).
• Direct integration experience with at least one: NextGen, athenahealth, ModMed, Greenway, or Cerner/Oracle Health.
• Healthcare data knowledge: patients, scheduling, insurance, referring-provider/billing.
• TypeScript proficiency or strong Node.js/JavaScript background.
• Strong software engineering fundamentals; self-directed; remote-capable.
• US-based.

Nice-to-Have

• Experience integrating with multiple EMRs across a customer base, not just a single deep integration.
• Background serving ambulatory or outpatient practices.
• Familiarity with HL7, FHIR, and common healthcare interoperability standards.
• Experience with AI-assisted document ingestion (faxes, referrals) and the data-quality work that comes with it at scale.
• Prior experience at an EMR vendor or a healthcare integration-focused firm.

Technical Environment

• EMR REST APIs (NextGen, athenahealth, ModMed, Greenway, Cerner/Oracle Health).
• TypeScript/Node.js.
• HL7, FHIR R4, SMART on FHIR.
• REST/OAuth 2.0.
• Scheduling and appointment data structures, patient and insurance data.

What Success Looks Like

• In the first 60–90 days: the in-flight pilot integration is hardened and running reliably at scale, and integration patterns are documented clearly enough for the broader team to support.
• At 6 months: at least one new EMR onboarded and in production; a repeatable onboarding process in place for future integrations.
• Long-term: serving as the integration roadmap owner and a core technical pillar of the engineering team as the company scales.