Unmasking the hidden cost of care
Like any project, we wanted to build something that solved a massive challenge we faced in our own lives. Medical billing in the United States is purposefully confusing, and we realized this firsthand when one of our teammates got slapped with a $202.17 bill for a routine EKG at a local hospital. A cost estimator and a support agent had predicted a $30.77 liability, but the hospital sneaked in a split charge for "facility" and "professional" fees without any warning.
With nearly half of insured adults receiving bills for care they thought was covered, and up to 80% of medical bills containing errors, we realized people aren't just overpaying, but lack the tools even to know when they are being overcharged. We built OpenHealth to bridge this gap between opaque pricing and the patients who pay the price.
OpenHealth is a medical bill transparency platform that empowers users to fight back against confusing hospital charges by leveraging autonomous, reasoning AI.
We built a robust, real-time stack designed to showcase true agentic behavior and high-fidelity data handling:
agent.ts): We utilized the ReAct (Reason → Act → Observe) pattern to build a Sandboxed Analyst Agent. The agent uses a Schema Discovery Protocol to understand our Convex tables in real-time, intelligently deciding when to retrieve information. It executes Bounded Queries via strict function-calling to fetch data, ensuring 100% factual accuracy and preventing hallucinations.Mapping disparate medical concepts (like CPT codes, units, and allowed vs. billed amounts) into a unified, queryable schema was a massive structural headache. None of us is a medical billing expert, so understanding the US healthcare hierarchy was incredibly difficult.
Additionally, ensuring agentic reliability with sensitive financial data is tough; general LLMs are prone to hallucinating specific pricing. We overcame this by leaning into Nemotron's advanced reasoning capabilities and building a rigid validation layer. We forced the agent into multi-step workflows where it must mathematically prove its answers via structured database tool-calling. Finally, ensuring that these complex analytical queries remained fast and responsive on the backend was a significant optimization hurdle.
We are incredibly proud of our agent.ts implementation. We're proud of it demonstrating true agentic behavior by carrying out actions such as planning, tool-use, and autonomous problem-solving to act as a sophisticated bridge between raw data and natural language. We successfully generated and managed a professional-grade medical dataset that accurately reflects real-world US healthcare pricing standards. Going from being frustrated about insurance overcharges to having a fully functional, multi-modal price-comparison agent within 24 hours is something our whole team is stoked about.
| Category | Technology |
|---|---|
| Frontend | Next.js 15+, TypeScript, Tailwind CSS, Recharts |
| Backend | Convex (Real-time Database & Serverless Functions) |
| AI/ML | NVIDIA NIM (Nemotron-3-nano-omni-30b-a3b-reasoning), Google Gemini 1.5 Flash |
| Infrastructure | UploadThing, custom Agentic Orchestration layer (agent.ts) |
| Tooling | Github, Copilot, Cursor, Gemini, Antigravity, Codex |
Colin
Sarvesh Thiruppathi Ahila
Ajinkya Gokule
David Gesl