Pricing Medicare Claims Across Facility Types: IPPS, OPPS, ASC, IRF & SNF

Ask anyone who’s priced Medicare claims for more than one kind of facility and they’ll tell you the same thing: the hard part isn’t the math — it’s that the math changes completely depending on where the care was delivered. A knee replacement priced under the Inpatient Prospective Payment System looks nothing like the same procedure priced for an ambulatory surgical center. If your team handles claims across multiple facility types, you’re not running one pricing methodology. You’re running five or more, each with its own rates, rules, and update calendar.

Why Facility Type Drives Pricing Complexity

Medicare doesn’t pay for care — it pays for care in a setting. Each setting has its own prospective payment system, its own grouping logic, its own wage-index adjustments, and its own quarterly or annual rate updates. A pricing process that’s airtight for inpatient hospital claims can produce confidently wrong numbers the moment an IRF or SNF claim enters the queue. Below is a quick primer on what actually changes from one facility type to the next.

A Quick Primer, Facility by Facility

IPPS (Inpatient Hospital). Claims group to MS-DRGs, then get adjusted for the hospital’s wage index, disproportionate share (DSH), indirect medical education (IME), and potential outlier payments. The annual final rule reshuffles weights and rates every October.

OPPS (Hospital Outpatient). Payment runs on Ambulatory Payment Classifications (APCs), governed by status indicators and packaging logic — including comprehensive APCs that bundle entire encounters into a single payment. Rates and addenda update quarterly, not annually.

ASC (Ambulatory Surgical Center). Often mistaken for “OPPS lite,” the ASC payment system has its own covered-procedure list and its own rates. Pricing an ASC claim with OPPS logic is one of the most common multi-facility errors we see.

IRF (Inpatient Rehabilitation Facility). Payment is driven by Case-Mix Groups (CMGs) derived from IRF-PAI patient assessments — a completely different grouping input than the claim itself.

SNF (Skilled Nursing Facility). Since FY2020, the Patient Driven Payment Model (PDPM) sets per-diem rates across five case-mix-adjusted components, with variable per-diem adjustments that change over the length of stay.

And the rest of the matrix. Home Health (PDGM 30-day periods), Hospice (per-diem levels of care plus the service intensity add-on), and FQHC (per-visit PPS rates) each add another methodology to the pile.

Common Pitfalls When Teams Use Single-Facility Tools

Most pricing problems we see aren’t logic errors — they’re coverage errors. The tool was built for one facility type and got stretched to cover others. The usual failure modes:

• Stale rate quarters. OPPS and ASC addenda update quarterly. A tool refreshed annually is wrong three quarters of the year.
• Wage index drift. CBSA delineations and wage indexes change; a hard-coded locality table quietly mis-prices every claim in affected counties.
• Missed outliers and add-ons. DSH, IME, and outlier calculations are exactly the kind of “edge case” a simplified tool skips — and exactly where the dollars are.
• ASC priced as OPPS. Same procedure codes, different system, different payment.
• No edit integration. Pricing a claim that would have been rejected for coding or coverage errors produces a number nobody can use. Pricing and claims editing belong in the same workflow.

Evaluating Platforms That Cover the Full Matrix

If your claim volume spans more than two facility types, the evaluation question changes from “is this tool accurate?” to “is this tool accurate everywhere we operate?” Ask vendors which payment systems they maintain natively, how quickly quarterly updates land, and whether pricing and editing run in one pass. Specialist platforms such as Micro-Dyn Medical’s multi-facility claims pricing handle this full matrix in one engine — IPPS, OPPS, ASC, IRF, SNF, Home Health, Hospice, and FQHC — rather than bolting facility types onto a system designed for one. That architectural difference is what determines whether your fourth and fifth facility types get the same rigor as your first.

A piecemeal stack of single-purpose tools can work, but every additional tool is another update calendar to track, another rate file to load, and another place for the matrix to silently drift out of date.

The Bottom Line

Multi-facility Medicare pricing isn’t one problem — it’s a portfolio of problems that share a claim format. Whether you solve it with one platform or several, the non-negotiables are the same: native support for each payment system you touch, rate updates that land on CMS’s calendar (not the vendor’s), and edits integrated into the pricing pass.

Want to see how this works in practice? Explore our solutions for batch and API-based claims pricing, see how the Contract Manager executes payer terms downstream, or compare against the free CMS.GOV PC Pricer tools to understand what a commercial platform adds.