Hospital prices are public by law. But they are buried in thousands of massive, inconsistently formatted files that no patient can read. ProcedureRadar is the translation layer. We parse the nightmare so you do not have to.
See the DataSee the Data
I played running back at Villanova University, where I learned that preparation, film study, and relentless execution separate the good from the great. Football teaches you to read complex systems fast and find the gap nobody else sees.
That instinct, reading chaos and finding a path through it, is exactly what ProcedureRadar does with healthcare pricing data.
I signed with the Philadelphia Eagles as a running back in 2015, then competed for a roster spot with the Minnesota Vikings. Two NFL organizations, two training camps, two systems to learn under pressure. The speed of professional football teaches you to process complexity fast and execute without hesitation.
After my playing career, I transitioned to coaching. As an Offensive Assistant Coach for the New York Giants, I broke down film, built opponent scouting reports, and translated analytics into weekly game plans. I coordinated with video and analytics teams on situational cut-ups: red zone, third down, two-minute drill.
The NFL taught me two things that built ProcedureRadar: how to read complex systems under pressure, and how broken healthcare billing is. Athletes deal with injuries, surgeries, and medical bills constantly. Even with top-tier insurance, nobody could tell you what anything actually cost.
After football, I moved into corporate finance. I spent years analyzing spreadsheets, building financial models, and learning how data drives decisions. Then I transitioned to tech, building products that solve real problems.
I founded RawRecruit, a sports recruiting platform, and LocalLayer AI, an AI consultancy. Both gave me the technical foundation and product intuition that ProcedureRadar is built on.
When someone in my family needed a medical procedure, I did what anyone would do: I tried to find out how much it would cost. I could not get a straight answer.
The hospital could not tell me. My insurance gave me a range so wide it was meaningless. I spent hours on the phone. I am someone who reads financial statements for a living, and I could not figure out what a common procedure would cost at a hospital 20 minutes from my house.
Then I discovered that hospitals are legally required to publish their prices. The data existed. It was just buried in files designed to be unreadable. ProcedureRadar was born that day.
Hospital prices are public by law. ProcedureRadar makes them readable.
Kevin Monangai, Founder
Every month, our automated pipeline processes data from thousands of hospitals. Here is how we turn regulatory compliance files into pricing information you can actually use.
Download Machine-Readable Files from 3,500+ hospitals mandated by federal law under 45 CFR Part 180.
Map billing codes to plain-English procedure names. Convert three different file formats into one clean standard.
Flag outliers, validate ranges, and assign confidence ratings so you know which prices to trust and which to question.
Deliver updated pricing monthly across 100 US metros. Accessible on the web and via our developer API.
Read Full MethodologyOur data processing methodology is the subject of a pending US provisional patent application covering normalization, quality scoring, and pipeline architecture.
Every price on ProcedureRadar traces to a hospital Machine-Readable File mandated by CMS under the Hospital Price Transparency Rule. Verifiable, attributable, real.
Our automated pipeline downloads and processes the latest hospital files on the 1st of each month. Stale data is flagged, not hidden.
Search real hospital pricing across 100 US metros. Or read about exactly how we collect and process every record.
About the Data. All pricing data on ProcedureRadar is sourced from hospital Machine-Readable Files required by federal law under 45 CFR Part 180. ProcedureRadar processes these files monthly, normalizing billing codes to consumer-friendly procedure names and validating data quality. For questions about our data or methodology, contact info@procedureradar.com.