The contract rate has not changed. The payer has not reduced the fee schedule. But next month, the same service may require prior authorization before it can be reimbursed.
That is where a rate-only model runs out of answers. It can calculate what a service should be worth under an agreement without explaining whether a new policy changes the conditions for payment.
For managed care teams, the useful question is bigger: what changed, which agreements and services does it affect, how much reimbursement is in scope, and what should we do before claims start coming back?
Consider the following fictional imaging example. All payer policies, contract terms, service volumes, authorization indicators, and dollar amounts are synthetic. This is a worked example, not a customer financial result.
The policy changes. The rates do not.
A sample commercial payer introduces prior authorization for two hospital outpatient facility services: lumbar spine MRI, code 72148, and CT abdomen and pelvis with contrast, code 74177. The requirement applies to one fictional New Jersey fully insured commercial PPO product, with emergency services and professional claims excluded.
The previous policy did not require authorization for these services. The new edition is published and delivered on September 1, 2026, with an effective date of November 1, 2026.
Nothing in the sample policy changes reimbursement rates. The financial question comes from the new condition attached to payment, not a lower price.
Before estimating any dollars, the team needs to establish which agreements the change reaches. A payer name and a matching procedure code are not enough for this example.
Hospital B’s notice shortfall is a review issue, not an automatic conclusion that the policy can be ignored. Its dollars belong in a separate unresolved bucket until the necessary evidence and decision are available.
Put dollars against the right services and period
For Hospital A, the sample uses a 90-day baseline from July 1 through September 28, 2026. It contains 120 MRI episodes and 80 CT episodes, with one reimbursable facility service unit per episode and no overlap between the two cohorts.
The model identifies $144,000 of gross reimbursement exposure on the 90-day baseline. That is not $144,000 of denied claims, a monthly revenue figure, or a recovery opportunity.
The rate type matters too. These fictional amounts represent baseline payer net liability, not billed charges, total allowed amounts including patient responsibility, or observed payments.
The baseline helps size the service cohort that would encounter the new requirement if a comparable mix continued. It does not establish how many future services will occur, obtain authorization, be denied, or ultimately be paid.
Hospital B adds a separate $36,000 baseline: 60 MRI episodes at $600 each. Because applicability remains unresolved, that amount is not added to Hospital A’s confirmed total.
The model also leaves out professional claims, the Medicare Advantage cohort, and emergency services. Those exclusions are part of the answer: including every imaging claim would produce a larger number for the wrong population.
Separate exposure from authorization readiness
The sample then adds a fictional operational authorization extract. It identifies readiness gaps associated with 30 MRI episodes and 20 CT episodes in Hospital A’s baseline cohort.
That is 50 episodes representing $36,000: 30 × $600 plus 20 × $900. It is a subset of the $144,000, not another amount to add to it.
These are prospective workflow-readiness indicators, not proof that historical claims lacked required authorization. The old policy did not require authorization for these services.
The other 150 episodes account for $108,000, but their authorization status under the new requirement is unknown. An absent readiness flag does not establish that authorization exists, that it is missing, or that it will be approved.
The next operational question is therefore not “how do we recover $144,000?” It is “how do we prepare the affected workflow, resolve the flagged gaps, and establish what we still do not know about the remaining services?”
Even an approval is not a universal payment guarantee. UnitedHealthcare’s outpatient radiology FAQ, for example, states that an authorization number does not guarantee payment and identifies other payment conditions, including the member’s benefit plan and participation agreement (UnitedHealthcare outpatient radiology FAQ).
That guidance illustrates the distinction; it is not the rule used for our fictional payer. Authorization readiness, approval, coverage, and payment remain separate questions.
Make every scenario name its denominator
Sensitivity analysis can help prioritize the work, but only if the reader knows what amount the percentage applies to. A 25% assumption produces very different answers on the full cohort and the readiness-gap subset.
These are two different scenario scopes, not additive estimates. Neither column represents an observed denial rate or an expected-loss forecast.
For example, $9,000 answers “what if 25% of the flagged subset becomes incremental loss?” The $36,000 in the same row answers “what if 25% of the entire confirmed cohort becomes incremental loss?”
The zero-loss case is important. A new requirement does not establish that revenue will be lost; if the services satisfy the applicable requirements and are reimbursed at the baseline amounts, incremental loss is zero.
Use these scenarios to test assumptions and decide where to focus. Do not convert an illustrative percentage into a forecast without evidence supporting the affected population, future volume, denial behavior, and remediation assumptions.
After adjudication, investigate the reason for a variance
The sample brief was prepared as of October 7, ahead of the November 1 effective date. It contains no post-change adjudicated claims, so it cannot establish actual denials or realized loss.
Now move the example forward hypothetically. A service with a modeled $600 payer net amount receives a zero payment after the policy takes effect.
A variance review can flag the $600 difference. It cannot establish from that difference alone that the payer used the wrong rate.
The reviewer needs to connect the evidence:
- Claim facts: Confirm the payer product, provider entity, service, setting, units, coding, modifiers, and date of service.
- Governing documents: Verify the applicable agreement, amendments, policy edition, notice requirements, and any documented exemption or transition arrangement.
- Authorization record: Establish whether authorization was required, requested, approved, denied, or otherwise unresolved for that specific service.
- Adjudication explanation: Read the payer’s adjustment reasons and reconcile the remittance with the modeled payer responsibility.
CMS describes Medicare remittance advice as reporting adjudication and payment information, adjustment amounts, and reasons through group, reason, and remark codes (CMS payment and remittance guidance). For a commercial claim, review that payer’s explanation and the applicable documents rather than treating a Medicare-specific rule as universal.
If the evidence supports an authorization-related denial, the work is different from correcting an incorrectly applied fee schedule. If the cause remains unclear, the output should say so and identify what evidence is missing.
A relevant policy is an investigation lead, not proof of causation. This is the next step beyond finding the payer policy: determining what it establishes about the particular claim.
End with owners and decisions, not just a dollar amount
The prospective analysis points to distinct actions. Contract management and legal resolve Hospital B’s document and notice questions; operations and revenue cycle prepare Hospital A’s authorization workflow; finance and managed care analytics define how post-change payment results will be measured.
Those actions connect prevention with retrospective review. The same evidence used to understand a forthcoming policy change should help explain a later variance, without treating modeled exposure as an amount already lost.
At Trek, that connection is the point: bring policy, contract, and payment evidence into the same workflow so the team can move from a number to an informed next action. Trek’s agent catalog describes contract modeling, policy checks, underpayment analysis, and denial-review workflows; those descriptions are not proof that this fictional example has been validated against a customer’s data (Trek Health’s agent catalog).
For a financial workflow, human review belongs in the design. Validate the contract interpretation, effective dates, cohort, calculations, and proposed action before relying on the output; repeatable arithmetic alone does not establish that the right rules were applied.
The rate is still important. But the decision-ready answer explains which rate applies, what conditions surround payment, what remains unresolved, and who should act.
Bring one payer-policy change, its governing agreements, and a deidentified service cohort to a working session with Trek Health. Start by defining what the evidence can establish before turning exposure into a forecast or a payment variance into a recovery claim.
