Sr. Software Engineer (EHR Integration Team)
Sr. Software Engineer (EHR Integration Team)
Posted yesterday
SENIORITY
Lead
About the role
- Build and ship SMART on FHIR apps: EHR launch and standalone launch, OAuth 2.0 withPKCE, backend services authorization, scopes and token handling.
- Design and build the server side: FHIR R4 APIs, mapping to our internal data model, profiles and extensions.
- Build CDS Hooks services with prefetch that respond within EHR time limits.
- Take apps through EHR vendor onboarding and go-live, starting with Epic (VendorServices and Showroom), then Oracle Health and others. Work with health system IT onbuild and testing.
- Handle PHI correctly in storage, caching, logging and tracing: minimum necessary data, encryption, audit trails, no PHI in logs.
- Work with HL7 v2 and interface engine flows where the EHR needs them.
- Write design docs, review code and mentor engineers.
- Be on call for what you ship.
- This role works with PHI on a regular basis both in paper and electronic form and haveaccess to various technologies to access PHI (paper and electronic) in order to performthe job.
- Must complete training relating to HIPAA/PHI privacy, General Policies and Procedure Compliance training and security training as soon as possible but not later than the first 30days of hire.
- Must maintain a current status on Natera training requirements.
- BS in computer science, a related field, or equivalent experience.
- 6+ years of software development, with at least 3 building EHR integrations in production.
- Hands-on SMART on FHIR: you have built and shipped an app that launches inside anEHR, not only consumed FHIR data.
- Strong FHIR R4: resource modeling, search, and terminology (LOINC, SNOMED, ICD-10).
- Production go-live with Epic. Oracle Health (Cerner), athenahealth, MEDITECH or othersa plus.
- Backend services in Java and Spring Boot or similar, on AWS.
- Experience handling PHI under HIPAA in a production system.
- Clear communication with clinicians, health system IT and product.
- CDS Hooks in production.
- An Epic Showroom listing, or an app built in the Oracle Health code console.
- Lab orders and results: Service Request, Diagnostic Report, Observation, and HL7 v2ORM/ORU.
- FHIR Subscriptions and Bulk FHIR.
- Interface engines such as Mirth, Rhapsody or Cloverleaf.
- React and TypeScript for in-EHR user interfaces.
- USCDI, Da Vinci implementation guides, or ONC certification work. KNOWLEDGE, SKILLS, AND ABILITIES
- FHIR R4, SMART App Launch, OAuth 2.0 and OIDC, CDS Hooks
- Java and Spring Boot; REST and event-driven microservices
- AWS services such as SQS, S3, SNS and Lambda
- Relational databases and SQL, preferably PostgreSQL or MySQL
- Docker, CI/CD, Linux fundamentals
- React and TypeScript
- Quality assurance mindset
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
