HomeCareBilling
- State
- Live
- Kind
- Own product
- Role
- Solo founder and engineer — architecture, implementation, and production operations.
Medicaid billing automation for home-care agencies.
HomeCareBilling runs the whole Medicaid billing cycle for a home-care agency: visit and payroll data goes in, claims go out to the state, and payments post themselves back against the claims they belong to.
Problem
Agencies bill Medicaid through spreadsheets and the state's own web portal. One formatting mistake, or a visit the state's verification system never recorded, becomes a denied claim nobody sees for weeks — and matching payments back to claims by hand is slow and easy to get wrong.
Approach
Built a Phoenix LiveView platform that owns the whole cycle: spreadsheet ingest, claim generation, submission to the state Medicaid payer, and automatic posting of payments, with visit verification synced to the state's aggregator. Claim reference numbers come from counters that cannot collide when two submissions run at once, background work runs on Oban, and every outside connection sits behind a behaviour so it is exercised in tests rather than in production.
Role
Solo founder and engineer — architecture, implementation, and production operations.
Stack
- Elixir
- Phoenix
- LiveView
- PostgreSQL
- Oban
- State Medicaid integration
- Redis
- Cloak
- Fly.io
Outcome
- The whole cycle — ingest, claim generation, submission, payment posting — happens in one place instead of four
- Each agency's billing data is separated at the database layer, not by a filter somebody could forget
- Claim reference numbers come from counters that cannot collide when two submissions run at once
- Sensitive credentials are encrypted at rest, and outside connections are exercised behind test doubles
Arrival
Want work like this shipped for you?
Every project starts with a short discovery conversation — no obligation, no boilerplate pitch. Tell me what you're building.