AuditRes
Revenue Recovery Intelligence
One AuditRes platform

AuditRes Medical · Practical review guide

Medical underpayment case review

Medical underpayment case review evaluates whether an identified candidate has enough support for a clear follow-up request. It connects the expected amount, payment history, evidence gaps, and reviewer conclusion.

The problem to investigate

A candidate list is not a ready case. The reviewer must eliminate identity errors, incomplete histories, and unsupported assumptions before stating the disputed difference.

Common causes to check

  • Candidate flags missing calculations
  • Later payments not incorporated
  • The same issue opened in multiple cases

What your organization should review

  • Confirm identity and current payment history
  • Review the expectation and evidence gaps
  • Check for an existing case on the same issue

Verification and supporting evidence

Keep a concise case rationale with source references and the current verified amount, if established. Record rejected candidates and unresolved questions without implying an outcome.

Synthetic review example

A synthetic candidate duplicates an already open adjustment case. The reviewer links the evidence to that case instead of creating two recovery opportunities.

How this fits the AuditRes workflow

Use Medical's underpayment and resolution workflow to preserve the review decision and prevent unsupported or duplicate follow-up.

AuditRes Medical brings reimbursement analysis, underpayment review, evidence, and resolution workflows together. Examples in this guide are synthetic. A payment variance needs a supported expectation and human review; it is not, by itself, a verified underpayment or realized recovery.

Frequently asked questions

What should happen when review disproves the candidate?

Record the explanation and close or reclassify it according to the review process. A dismissed candidate is a useful control outcome, not a failed recovery.

Are these examples based on real patients or recovery results?

No. All examples are synthetic educational scenarios. Medical remains in its QA phase; no real PHI should be submitted and no production compliance certification is claimed.

Explore the current AuditRes Medical workspace

In QA — synthetic evaluation. Do not submit real PHI. These modules are built for evaluation; their presence does not establish production compliance activation, payer certification or a live payer submission connection. OCR and extracted fields require verification, and risk signals do not guarantee payment or recovery.

  • Underpayment review — Compare expected and paid amounts in the evaluation dataset, keeping potential reimbursement differences separate from confirmed recovery.
  • Pre-submission risk review — Inspect draft-claim risk signals and the available governing contract proof before a submission decision. Missing proof remains explicit.

All AuditRes Medical features and readiness