Medicare Part B procedure volume by state and service
Centers for Medicare & Medicaid Services
In a RepVector build, this dataset quantifies clinical need and utilisation across the population.
| State | Code | Service | Setting | Providers | Beneficiaries |
|---|---|---|---|---|---|
| Ohio | 11721 | Removal of fingernails or toenails, 6 or more nails | Office | 752 | 98,579 |
| Ohio | 11720 | Removal of fingernails or toenails, 1-5 nails | Office | 646 | 34,824 |
| Ohio | 11102 | Biopsy of related skin growth, first growth | Office | 1,080 | 69,010 |
| Ohio | 00731 | Anesthesia for other procedure on esophagus, stomach, or upp | Facility | 3,761 | 37,501 |
| Ohio | 00142 | Anesthesia for lens surgery | Facility | 1,601 | 32,264 |
| Ohio | 00811 | Anesthesia for other procedure on large bowel using an endos | Facility | 3,468 | 39,350 |
| Ohio | 11042 | Removal of skin and tissue, 20.0 sq cm or less | Facility | 1,072 | 10,570 |
| Ohio | 11056 | Removal of noncancer thickened skin growth, 2-4 growths | Office | 565 | 16,990 |
What this dataset is
For each billing code, how many providers performed it in a state, how many beneficiaries received it, total service volume, and average submitted, allowed and paid amounts. The closest public equivalent of a procedure-level market size for anything Medicare pays for. It is published by Centers for Medicare & Medicaid Services and can be queried at state level, refreshed annual. Each row is an aggregate statistic for a geography, so results describe a market as a whole rather than a single account.
Why it is useful
- Separates markets with real clinical demand from markets that only have supply.
- Grounds a territory case in published prevalence and utilisation instead of assumption.
- Highlights where need outruns available capacity — usually the fastest conversations.
Questions it helps answer
- Where is the underlying clinical need highest relative to available capacity?
- How does utilisation here compare with the state and national picture?
- Which measures are suppressed or unreported for this geography?
How different verticals use it
RepVector is vertical-agnostic: this dataset is selected by what your question asks for, not by industry. These are common ways teams put it to work.
Prioritises territories where clinical need outruns available capacity.
Quantifies prevalence and utilisation behind a programme or referral case.
Informs risk and benefit design with published utilisation patterns.
Shows community health pressures that shape support-service demand.
How RepVector uses it
- You describe a market in plain language. The geography resolver turns the place you named into the exact identifiers this dataset needs — city to county to state, plus DMA where relevant — so a query at state runs without you knowing any codes.
- The planner selects Medicare Part B procedure volume by state and service only when your question matches what it actually reports. It is never included to pad a result.
- Returned rows are normalised into the shared metric layer, so figures from Centers for Medicare & Medicaid Services line up with every other source in the same dashboard instead of sitting in an isolated table.
- Quality checks score coverage and recency. If Centers for Medicare & Medicaid Services suppresses or omits a value for your geography, the gap is reported as a gap — nothing is estimated or filled in.
- The result renders as charts, KPIs and, where the rows are entities, prioritised targets you can export to PDF, Excel, CSV or JSON.
What it does not tell you
- Aggregated and often suppressed at small geographies to protect privacy; gaps are reported rather than filled in.
| Field | Key | Type |
|---|---|---|
| State | state | geo |
| Code | hcpcs | string |
| Service | service | string |
| Setting | setting | string |
| Providers | providers | number |
| Beneficiaries | beneficiaries | number |
| Services delivered | services | number |
| Avg allowed amount | avgAllowed | currency |
| Avg Medicare payment | avgPaid | currency |
How it fits with the rest of the catalog
Need data explains why a territory matters; provider and facility data explains who you visit once you get there. RepVector queries every selected dataset against the same resolved geography and time window, then normalises the results into one metric layer so they can be charted side by side. These datasets are the most common companions to Medicare Part B procedure volume by state and service:
Other health datasets
Common questions
What does Medicare Part B procedure volume by state and service contain?
For each billing code, how many providers performed it in a state, how many beneficiaries received it, total service volume, and average submitted, allowed and paid amounts. The closest public equivalent of a procedure-level market size for anything Medicare pays for. It is published by Centers for Medicare & Medicaid Services at state grain.
How often is it refreshed?
Centers for Medicare & Medicaid Services publishes on a annual cycle. RepVector re-reads the source on that cadence and keeps every prior capture, so you can see what changed.
Do I need an account to use it?
No. Browsing the catalog and the free lookup tools needs no account. Running a full market build across every county in a territory is the paid product.
Build the list for one county and see whether the names are right.
Ask in plain language. RepVector finds the universe, enriches each target from its own website, scores it 0–100, and hands you a ranked call list with phones, addresses and named contacts.
3 free runs — no card required.