Healthcare · Practice-management platform · 2025–present
DSO operations platform
Principal engineer (contract) on the internal platform a mid-sized dental DSO runs its offices on. The biggest piece is insurance-verification automation: eligibility requests are generated from the schedule, routed by payer to an EDI 270/271 clearinghouse or a headless-browser scraper for that payer's portal, cross-checked, classified (payer answer vs. our failure), and written back into OpenDental, with plain-language failure reasons for the front desk and a Datadog dashboard for the RCM team. The scrapers run through a centralized egress gateway I designed so each office's traffic leaves from its own clinic network, with per-location credentials resolved from 1Password, MFA/OTP handling, circuit breakers, failure capture for post-mortems, and an LLM judge that grades ambiguous outcomes.
Around that: a merge train that batches the volume of AI-accelerated pull requests into hourly runs instead of running the pipeline on every merge, saving about $10,000 a month in CI/CD costs; migration of Rails encrypted credentials to environment-sourced secrets; DB-backed feature flags with percentage rollouts; and an OAuth 2.0 + PKCE layer so Claude and other LLM clients can reach the platform's MCP tools.
RailsSidekiqEDI 270/271PlaywrightTailscale / SOCKS51PasswordDatadogTerraformECS FargateMCP / OAuth