Nicheloom visits: 59,713 all-time · 7,913 in the last 7 days

The opportunity tracker for new startups.

Today: 895 launches · Niche of the day: browser-based video games · See what launched today →

What 482 hospitals charge vs. what insurers pay, from their own files

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

US hospitals must publish a machine-readable file of their prices, including the rate they've negotiated with each insurer. The files are huge (one is 36GB), in four formats and often messy, so almost nobody reads them.I built a crawler that finds each hospital's official file and pulls out 29 common services. Across 482 hospitals: a moderate ER visit is listed at a median $1,285 while insurers pay $288; a metabolic panel is listed at $207 while insurers pay $11.46.To keep it honest: only per-service fee-schedule dollar rates count (no case rates or percentages, which cover a whole visit), each figure needs at least 3 insurers, and every value is checked against Medicare reference rates. Surgery is excluded because insurer surgery rates cover the whole operation while the list price is one line item. Each hospital page links its source file. Feedback on the methodology is very welcome.

HN · launched Oct 1, 2026 · 31 upvotes (top 26%) · 0 views

Niche: comparison engines and tools · 292 launches, 35 in the last 7 days ▲ +9% · Explore this niche →

Category and tags

  • Healthcare
  • Analytics & BI
  • B2B
  • Not AI
  • Commercial product

Visit website ↗ Source listing ↗

Could you build this?

Partial The web UI and data tables are easy to vibe code, but acquiring, standardizing, and parsing tens of gigabytes of inconsistent multi-format machine-readable hospital price files across hundreds of institutions requires substantial data engineering.

What it would actually take: The system requires a distributed scraping and ETL pipeline (using tools like DuckDB, Polars, or Apache Spark) capable of streaming and normalizing multi-gigabyte CSV, JSON, and XML files published under 45 CFR 180. The core challenge is handling corrupted formats, memory crashes on 30GB+ files, and messy entity resolution across CPT/HCPCS codes and insurer plans.

Discussion

2 comments analyzed.

Feature requests: Natural language search for medical procedures

Competitors

Other products that read as similar to this one : 317 launches clear the similarity bar, closest 8 shown.

Attention rank: #85 of 318 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 302 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.