Research billed and allowed amounts against relevant payer-negotiated rates, Medicare benchmarks, and commercial comparables.
In short
Medical bill review often requires more than a single fee schedule. Gigasheet provides access to published commercial negotiated rates and geographically adjusted Medicare benchmarks, then uses AI-assisted reasoning to select useful comparables when an exact provider, payer, service, or market match is unavailable or too narrow to support a meaningful comparison. The result is independent market context for research, repricing, and negotiation, not a determination of the correct payment.
No single benchmark answers every question about a medical bill. Each source has a different origin, a different bias, and a different appropriate use.
| Benchmark | What it represents | Strengths | Limitations |
|---|---|---|---|
| Billed charges | The provider's chargemaster price | Always available on the claim | Rarely paid by anyone; weak reference for reasonableness |
| Contracted rate | The amount a specific payer and provider agreed to | Definitive when the contract applies | Only covers in-network claims under that agreement |
| Medicare fee schedule | CMS-set reimbursement, geographically adjusted | Standardized, public, covers most services and settings | Does not reflect commercial pricing; multiples vary widely by service and market |
| Historical paid claims | What the plan or a data vendor has previously allowed | Reflects actual payments | Backward-looking; reflects the plan's own history rather than the market; often sparse for high-cost or unusual services |
| Customary-rate datasets | Percentile tables compiled from billed charges or paid claims | Familiar in dispute and out-of-network workflows | Methodology and provenance vary; charge-based tables inherit chargemaster inflation |
| Commercial negotiated rates | Rates published under Transparency in Coverage and hospital price transparency rules | Observable, current, market-wide, and specific to payer, provider, and service | Published rates are not paid claims; require careful matching to be meaningful |
A well-built bill review uses more than one row. Commercial negotiated rates are the newest addition to the list and the only one that shows, at scale, what competing payers have agreed to pay a given provider for a given service.
Before 2022, the commercial price of a service was private to the payer and provider that negotiated it. Reviewers worked from Medicare, their own claims history, and charge-based tables. Transparency in Coverage and hospital price transparency files made negotiated rates observable across payers, providers, and markets.
That changes three things in a bill review workflow:
Price transparency data complements the traditional sources. It does not replace the contract when one applies, and it is not a record of what was paid.
Having 150 billion rates is not the same as having the right twelve. A comparable is useful when it matches the claim on the dimensions that drive price and is drawn from a sample large enough to trust.
| Dimension | What to match | Why it matters |
|---|---|---|
| Service basis | Same CPT, HCPCS, MS-DRG, or APC; a customer-approved service family only when explicitly allowed | Rates vary more by code than by any other single factor |
| Provider or facility characteristics | Facility type, bed count, teaching status, health system, specialty, provider type | A tertiary academic center and a community hospital price the same DRG differently for structural reasons |
| Payer or payer set | Same payer, then comparable commercial payers, then the broader market | Payer leverage and network design shape negotiated rates |
| Geography or market | Exact local market first; broader customer-approved geographies only when needed | Labor cost, competition, and consolidation vary by market |
| Sample sufficiency | A minimum number of observations, distribution quality, outlier handling | A median of three rates is an anecdote, not a benchmark |
| Provenance and date | Source file, payer, posting date, plan type | A benchmark that cannot be traced cannot be defended |
| Customer rules | Approved exclusions, fallback order, and weighting | The right comparable depends on what the review is for |
Gigasheet applies these dimensions through configurable rules. A reviewer who is building a case for negotiation may want the tightest possible match. A reviewer screening thousands of claims may accept a broader set in exchange for coverage. Both are valid, and the rules make the choice explicit.
An exact match on all dimensions is often not available, or exists but is too thin to trust. When that happens, the question becomes which dimension to relax first, and the answer depends on the customer's policy, not on a fixed formula.
The AI-assisted endpoint evaluates multiple candidate paths:
Each path is scored against the customer's minimum sample threshold and preference ordering. The endpoint returns the selected comparison set, the benchmark statistics, and the underlying rate records on request, so a reviewer can see what was compared and why.
Illustrative. Values are synthetic and do not represent any real provider, payer, or customer.
Submitted claim
| Attribute | Value |
|---|---|
| Service | MS-DRG 291, heart failure and shock with MCC |
| Facility | 320-bed teaching hospital, part of a regional health system |
| Payer | National commercial PPO, out-of-network for this member |
| Market | Large metro, Midwest |
| Billed charges | $96,300 |
| Requested reimbursement | $71,800 |
Candidate comparison sets
| Set | Dimensions held | Observations | Median | Assessment |
|---|---|---|---|---|
| A | Same facility, same payer, same DRG | 1 | $44,900 | The facility's in-network rate with this payer. One observation; useful context, not a distribution |
| B | Same facility, all commercial payers, same DRG | 6 | $46,200 | Below the customer's threshold of 10 |
| C | Teaching hospitals in the same metro, all commercial PPOs, same DRG | 23 | $42,700 | Meets threshold; holds market and facility class |
| D | All hospitals in the state, same payer, same DRG | 61 | $35,100 | Large sample but mixes community hospitals into a teaching-hospital comparison |
Selected set: C. The customer's policy prioritizes facility class over payer match for inpatient medical DRGs and requires at least 10 observations. Set C meets both. Set A is retained as a reference point because it shows what this payer already pays this facility in network.
Benchmark output
| Statistic | Value |
|---|---|
| 25th percentile | $37,800 |
| Median | $42,700 |
| 75th percentile | $48,900 |
| Facility's own in-network rate (Set A) | $44,900, 60th percentile |
| Requested reimbursement ($71,800) | Above the 95th percentile |
| Geographically adjusted Medicare | $16,400 |
| Requested reimbursement as multiple of Medicare | 4.4x |
| Median comparable as multiple of Medicare | 2.6x |
Reviewer takeaway
The requested amount exceeds what any comparable teaching hospital in the metro has negotiated with a commercial PPO for this DRG, and it is 60% above the facility's own in-network rate with the same payer. That is strong market context for a negotiation. It does not, on its own, determine what the plan owes: that depends on the plan document, applicable out-of-network rules, and any state or federal balance-billing provisions.
| Direct API lookup | AI-assisted comparable selection | |
|---|---|---|
| Best for | High-volume screening, known in-network combinations, repricing against a defined benchmark | Out-of-network claims, high-dollar disputes, unusual providers or services, thin markets |
| Input | Code, provider NPI, payer, geography | The same, plus what the reviewer is trying to determine and the customer's comparison policy |
| Output | Matching rates, percentiles, aggregates | Selected comparison set, statistics, and the underlying rate records on request |
| Reviewer effort | None; fully automated | Minimal; the reasoning is done, the reviewer evaluates the result |
| Typical volume | Every claim | The claims worth a closer look |
Most bill review shops use both. The direct API handles the volume. The AI-assisted endpoint handles the claims that end up in a negotiation, an appeal, or a dispute.
Yes, as independent market context and documented evidence. Published negotiated rates show what other commercial payers have agreed to pay the same or comparable providers for the same service, which is directly relevant when a reviewer is evaluating whether a requested amount is consistent with the market.
What they do not do is establish the legally or contractually correct reimbursement. That is set by the plan document, the provider agreement if one exists, and applicable state and federal rules. Gigasheet supplies the market evidence and the provenance behind it. The reviewer, the plan, and where necessary their counsel determine what it means for the claim.
Medical bill review is the examination of a healthcare claim to confirm that the coding is accurate, the services were covered and appropriate, the pricing is consistent with the applicable contract or benchmark, and the payment is correct. It can occur before payment, after payment, or during an appeal or dispute.
Repricing is the step of determining what a claim should be paid when a benchmark, rather than a contracted rate, sets the amount. It is common for out-of-network claims and reference-based pricing plans. Repricing is distinct from auditing, which checks whether a claim was processed correctly; repricing establishes the amount, auditing verifies the process.
Common benchmarks include Medicare fee schedules, contracted rates, historical paid claims, customary-rate percentile tables, and, increasingly, commercial negotiated rates published under Transparency in Coverage and hospital price transparency rules. Each reflects a different source and carries different limitations, and many reviews use more than one.
No. Transparency in Coverage files are published by payers and hospital price transparency files are published by hospitals, but both contain negotiated rates, not paid claims. Claims record what was actually billed and paid for a specific encounter; the paid amount can differ from the negotiated rate because of benefit design, cost sharing, bundling, modifiers, and adjudication. Because the two sources describe the same contracts from opposite sides, a reviewer can cross-check one against the other when they disagree.
Yes, when the rate and the claim are matched on service, provider or facility characteristics, payer context, and market, and the comparison set is large enough to support a distribution. Gigasheet performs this matching directly when the combination is known and through AI-assisted comparable selection when it is not.
Same service code, similar facility characteristics such as type, size, teaching status, and system affiliation, a comparable payer or payer set, the same or a defensibly similar market, and enough observations to form a distribution. Two rates that match on code alone are not comparable if one is from an academic medical center and the other from a critical access hospital.
The AI-assisted endpoint evaluates alternative comparison paths, relaxing geography, payer set, facility characteristics, or service basis in whatever order the customer's policy permits, and reports a benchmark only once the comparison set meets the minimum sample threshold. The path taken and the rates used are available for review.
Yes. Every benchmark can be expressed alongside the geographically adjusted Medicare rate for the same service and setting, so a reviewer sees both where the claim sits within the commercial distribution and what multiple of Medicare it represents. Medicare is one reference point, not the standard for what commercial payers owe.
It can support research and negotiation by documenting what comparable payers and providers have agreed to for the same service. It does not by itself establish the correct reimbursement, which depends on the plan document, provider agreement, and applicable law. Gigasheet supplies the market evidence and its provenance; it does not provide legal opinions.