Senior FHIR Developer

Revelation Pharma LLC•Remote, US,

2d•$130,000 - $165,000•Remote

About The Position

Evergreen Telehealth is a vertically integrated direct-to-consumer telehealth platform under Revelation Pharma Corporation. We are building Grove, a transactional healthcare system, and FHIR is its core. We are hiring a Senior FHIR Developer to own Grove’s FHIR data layer from resource design through system integration. This is a focused, deep specialty role. You will define how clinical data is modeled in FHIR R4 across every domain Grove touches — patient demographics, medications, observations, care plans, diagnostic reports, and clinical encounters — and you will build and maintain the integrations that make that data useful to the systems that depend on it. The two systems you will live inside are AWS HealthLake and Canvas Medical. HealthLake is Grove’s FHIR-native data store — you will own its resource schema, ingestion pipelines, and query surface. Canvas Medical is Grove’s ONC-certified EHR — you will program directly to the Canvas SDK, build and maintain clinical workflow integrations, and evolve how Canvas-sourced FHIR data is used across the rest of the platform. You will also define the FHIR contracts consumed by Grove’s AI agents, the Prescription Dispatch Service, and any downstream clinical analytics layer. If you have spent years doing real FHIR work — not reading the spec, not advising on it, not configuring a FHIR server someone else stood up — this is the role where that depth becomes the job.

Requirements

4+ years of production FHIR R4 implementation experience — resource modeling, profiling, validation, and API development in live clinical systems; not configuration, not consulting, not spec familiarity
AWS HealthLake hands-on experience — ingestion pipeline development, FHIR search parameter design, and data lifecycle management at the infrastructure level
Canvas Medical SDK programming experience — direct integration development using the Canvas SDK; candidates without Canvas experience must have equivalent depth on a modern FHIR-native EHR (Epic FHIR R4 APIs, Athenahealth) and be able to demonstrate a clear ramp path
Deep clinical resource fluency — you can model a GLP-1 titration protocol, a compounding pharmacy prescription lifecycle, or a longitudinal weight management care plan in FHIR R4 without referencing the spec
FHIR Subscription and event-driven data flow experience — real-time clinical event delivery, webhook integration, and async data synchronization patterns
HIPAA-compliant data handling — PHI field-level controls, FHIR-layer access scoping, audit log design, and data minimization in a production clinical environment
Strong TypeScript or Python — you write the integration code, not just the specs

Nice To Haves

Experience defining FHIR resource contracts consumed by LLM or agentic AI systems — structuring clinical context for model input, and modeling structured clinical outputs back into FHIR resources
US Core, Da Vinci, or other FHIR implementation guide profiling experience
SMART on FHIR authorization and CDS Hooks integration experience
Bulk FHIR export ($export operation) for ML feature pipeline or analytics use cases
Compounding pharmacy or e-prescribing domain knowledge — Medication Request lifecycle, pharmacy workflow modeling, or DoseSpot/SureScripts integration experience
Experience maintaining FHIR data quality in a system with multiple upstream write sources (EHR, patient-facing app, pharmacy system)
Familiarity with ONC certification requirements and their implications for FHIR API design

Responsibilities

FHIR R4 resource schema governance — canonical definitions for every resource type Grove uses: Patient, Practitioner, Medication, Medication Request, Medication Dispense, Observation, Diagnostic Report, Care Plan, Goal, Condition, Encounter, Coverage, and Subscription resources
AWS HealthLake data layer — ingestion pipeline design and maintenance, resource validation, search parameter configuration, bulk export for analytics and ML feature pipelines, and FHIR API contract ownership
Canvas Medical SDK integration — direct programming to the Canvas SDK for clinical workflow automation, note creation, protocol execution, patient chart updates, and event-driven synchronization between Canvas and HealthLake
FHIR data evolution — owning the roadmap for how Grove’s FHIR data model grows as new therapeutic verticals, clinical protocols, and platform capabilities are added; defining extension patterns, profiling strategy, and versioning standards
AI agent FHIR contracts — defining the FHIR resource payloads consumed and produced by Grove’s six clinical AI agents, including the context structures passed to Bedrock and the structured outputs written back to HealthLake
Prescription Dispatch Service FHIR interface — Medication Request and Medication Dispense resource design and lifecycle management across the LifeFile (Innovation Compounding), DoseSpot/SureScripts (Phase 2), and HiveRx (Phase 2) dispatch paths
Subscription and webhook architecture — FHIR Subscription resource configuration for real-time clinical event delivery, and webhook payload schema design for inbound events from Canvas and LifeFile
Data quality and conformance — resource validation rules, profile conformance testing, and ongoing data quality monitoring across the HealthLake data store
FHIR API documentation and standards — internal developer-facing documentation for all FHIR contracts, resource profiles, and integration patterns; the reference layer that backend, mobile, and AI teams build against
Technical collaboration with the KMS Technology engineering team — FHIR design reviews, resource modeling guidance, and integration standards enforcement on backend deliverables
Other duties as assigned