title: ProcedureMap status: active oneLiner: A consumer search tool for the prices US hospitals are legally required to publish. needs: [backend, policy]
What we're building
Under the CMS Hospital Price Transparency Rule, US hospitals have to publish machine-readable files listing what they actually charge for procedures. ProcedureMap is what happens when a person can search those files like a normal website — by procedure, by location, by hospital — instead of downloading 400-megabyte CSVs from each hospital's footer.
Where we are
The codebase is production-ready — 94 passing tests, full restore-drill runbooks, observability wired through Sentry and structured logs. What's left is operational: secrets, the first scheduled ingestion, and the restore drill that the launch checklist explicitly blocks on. We're weeks from being live, not months.
What you'd do
If you join as a backend contributor, the work is on pre-flight validation automation and on submissions triage — keeping a 3,791-source pipeline healthy without it becoming a babysitting job. If you have policy or healthcare-data background, what we want is help expanding beyond the 70 CMS-mandated shoppable services into a richer procedure taxonomy, and on outreach to non-compliant hospitals.