← Aleksandr Baranov

EMR integration hub & partner help center

Software Engineer · contract · 2024 — now · K Health

EMR Connect is the service our internal teams go through to reach partner clinics' medical systems (Epic / FHIR). Beside it, the partner help center on Next.js and Contentful.

EMR Connect: the service in the middle, carrying requests from five internal teams out to partner clinics' Epic systems and the patient records backEMR CONNECT — ONE SERVICE, BOTH DIRECTIONSInternalservicesSalesforce · mobile appeligibility · Airflow ETLfive internal teamsEMR Connectconfig-driven traversalRedis cache-aside · TTLPub/Sub sync workersPartner clinicEMRFHIR API · Epicrate-limitedRedox: real-timesync requestpatient historypaced FHIR callsrecords · updatesNo internal team talks to Epic directly — everything crosses this one service.

My role

Team product. The integration service and the partner help center are mine.

What I did

  • — I own the integration layer between our services and partner clinics' medical systems (EMR, Epic / FHIR). It is built for their rate limits and their outages: a partner goes down and the product does not notice.
  • — Onboarding a new clinic went from weeks to days. Everything that depends on the clinic moved out of code into standard configuration and editable document templates, and there is far less back-and-forth with each new one.
  • — Moved the partner help center off Salesforce to Next.js and Contentful. One template for everyone instead of a site per partner, so launching or updating one takes hours instead of days.
  • — Added AI search to the help center (RAG on Gemini, personal data scrubbed for HIPAA). It answers from the knowledge base before the question becomes a support ticket.

Stack

Node.js · TypeScript · NestJS · PostgreSQL · Redis · GCP Pub/Sub · Next.js · Contentful · Gemini

More work →