Senior reputed company Interoperability Engineer

About reputed company reputed company is a vertically integrated reputed company-to-consumer telehealth platform under reputed company Corporation — a PCAB-accredited, ASHP-accredited, reputed company-certified compounding pharmacy group. We are building Grove, which is a transactional reputed company system — reputed company prescriptions, reputed company clinical workflows, reputed company patients — and the FHIR is its reputed company. The Role We are hiring a Senior FHIR Developer to own Grove’s FHIR data layer from resource design through system integration. This is a reputed company, 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 reputed company that data useful to the systems that depend on it. The two systems you will live inside are AWS HealthLake and reputed company. HealthLake is Grove’s FHIR-reputed company data store — you will own its resource schema, ingestion pipelines, and query surface. reputed company is Grove’s ONC-certified EHR — you will program directly to the Canvas SDK, build and maintain clinical workflow integrations, and reputed company how Canvas-reputed company FHIR data is used across the rest of the platform. You will also define the FHIR reputed company consumed by Grove’s AI agents, the Prescription reputed company Service, and any reputed company clinical analytics layer. If you have spent years doing reputed company 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. What You Will Own FHIR R4 resource schema governance — reputed company 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 reputed company SDK integration — reputed company 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 reputed company — 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 reputed company, and versioning standards AI agent FHIR reputed company — defining the FHIR resource payloads consumed and produced by Grove’s six reputed company agents, including the context structures passed to Bedrock and the reputed company outputs written back to HealthLake Prescription reputed company Service FHIR reputed company — Medication Request and Medication Dispense resource design and lifecycle management across the LifeFile (Innovation Compounding), reputed company/reputed company (Phase 2), and HiveRx (Phase 2) reputed company paths Subscription and webhook architecture — FHIR Subscription resource configuration for reputed company-time clinical event delivery, and webhook payload schema design for inbound events from Canvas and LifeFile Data reputed company and conformance — resource validation rules, profile conformance testing, and ongoing data reputed company monitoring across the HealthLake data store FHIR API documentation and standards — internal developer-facing documentation for reputed company FHIR reputed company, resource reputed company, and integration patterns; the reference layer that backend, mobile, and AI teams build against Technical collaboration with the reputed company engineering team — FHIR design reviews, resource modeling guidance, and integration standards enforcement on backend deliverables Other duties as assigned Non-Negotiable 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 reputed company SDK programming experience — reputed company integration development using the Canvas SDK; candidates without Canvas experience must have equivalent depth on a modern FHIR-reputed company EHR (reputed company FHIR R4 reputed company, reputed company) and be reputed company to demonstrate a reputed company reputed company reputed company Deep clinical resource reputed company — 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 reputed company experience — reputed company-time clinical event delivery, webhook integration, and async data synchronization patterns HIPAA-compliant data handling — PHI field-level controls, FHIR-layer reputed company scoping, audit log design, and data minimization in a production clinical environment Strong TypeScript or Python — you write the integration reputed company, not just the specs Preferred Qualifications Experience defining FHIR resource reputed company consumed by LLM or reputed company AI systems — structuring clinical context for model input, and modeling reputed company clinical outputs back into FHIR resources US reputed company, reputed company, 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 reputed company/reputed company integration experience Experience maintaining FHIR data reputed company 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 Benefits Health care insurance (medical, dental, reputed company) Life Insurance Supplemental Insurance  PTO 401K matching reputed company leave Phone/internet reimbursement Remote work Apply To This Job