Data iSight Negotiations: Provider Review and Counteroffer Guide
A careful provider workflow for understanding a Data iSight payment recommendation, requesting claim-level information, testing the methodology, and building an evidence-based counteroffer.

Before you act on this guidance
- Check the controlling jurisdiction, coverage terms and current agency guidance; a published overview is not a determination for your claim.
- Prepare the relevant records: Payer and plan type, EOB rationale, payment methodology and appeal status.
Data iSight is a Claritev solution used to generate out-of-network reimbursement recommendations. Claritev's current product page describes it as an alternative to usual-and-customary or Medicare-based recommendations and says it uses different approaches for facility and practitioner claims. That is the vendor's description of its product. It does not establish what a particular health plan promises to pay, whether a claim was processed correctly, or whether a provider must accept the recommendation.
This article separates verified public methodology statements from provider-side operational analysis. It does not attempt to reverse-engineer a proprietary formula, repeat unverified allegations, or characterize a pending dispute as proven fact. The correct response always begins with the actual remittance, plan, claim, contract status, and available explanation.
1. Identify what Data iSight did on this claim
A Data iSight reference may appear on an EOB, pricing notice, portal, or correspondence. Determine whether the solution supplied a recommendation, handled an appeal, supported a member-balance process, or performed another delegated function. Then identify the health plan, insurer, TPA, or employer plan that adopted the result and issued the benefit determination.
| Question | Why it matters |
|---|---|
| Who issued the EOB or ERA? | Identifies the entity communicating the benefit decision |
| Who funded the claim? | Distinguishes a self-funded plan from fully insured coverage |
| Where is Data iSight named? | Shows whether it appears as repricer, explanation resource, contact, or appeal channel |
| Who can change the payment? | Prevents sending a counteroffer only to a vendor without settlement authority |
| What does the plan say about OON payment? | Tests whether the recommendation was used consistently with governing terms |
2. Separate facility and practitioner methodology statements
Claritev publicly states that Data iSight generally uses a cost-based approach for facilities and an accepted-amount or median-reimbursement approach for practitioners. Its detailed article describes facility review as a cost-up approach using comparisons involving facilities of similar size, location, and type; for practitioners, it describes median reimbursement analysis. Claritev also says the process can incorporate claim editing, severity, national benchmarking, regional wage indexing, geographic adjustment, and commercial paid-claims information.
| Claim type | Publicly described concept | Provider review focus |
|---|---|---|
| Facility | Cost-up / comparable-facility approach | Facility classification, location, service line, acuity, cost inputs, implants or supplies, severity, and claim edits |
| Practitioner | Median reimbursement / accepted-amount approach | Provider type, specialty, code family, modifier, place of service, geography, conversion factor, and claim edits |
| Either | Geographic and other adjustments | Correct locality, date, service category, units, and whether unusual complexity was captured |
3. Obtain the claim-specific explanation
Claritev and the Data iSight provider site describe a process intended to explain how payment amounts are determined. Use the identifier and contact information on the actual notice rather than relying on a generic phone number copied from another claim. Request the claim-level explanation, methodology category, service and provider classification, geographic area, code edits, severity adjustments, and the party authorized to consider an appeal or counteroffer.
- Preserve the original claim, itemized bill, EOB or ERA, Data iSight notice, patient cost-sharing amount, and all identifiers.
- Request the governing plan provision and any client configuration or benefit-limit language cited for the out-of-network payment.
- Ask whether the claim was treated as facility or practitioner, which codes and modifiers were priced, and whether any services were excluded or edited.
- Ask what geographic unit and comparison group were used and how the service date was matched to the data period.
- Ask whether a formal appeal, commercial negotiation, or both are available, and obtain the address, portal, deadline, and authorized decision-maker.
4. Audit the inputs before challenging the output
A productive challenge identifies a factual mismatch or presents material information the model or reviewer may not have captured. Check provider taxonomy, facility type, location, specialty, place of service, emergency status, codes, modifiers, units, severity, multiple-procedure logic, and authorization. For a facility claim, separate routine cost from implant, device, pharmaceutical, trauma, ICU, or other resource-intensive components when the documentation supports that distinction.
- Verify that the claim was not subject to a direct, leased-network, single-case, or letter-of-agreement rate.
- Compare the pricing explanation with the plan's stated out-of-network benefit language.
- Reconcile every line; do not challenge only the aggregate payment.
- Identify missing clinical facts and provide concise records rather than an undifferentiated chart dump.
- Document any mismatch in provider type, facility class, geography, code grouping, units, or modifier handling.
- Distinguish a benefit denial, coding edit, and pricing recommendation because each requires a different response.
5. Build an evidence-based counteroffer
A counteroffer should explain why the requested resolution better fits this claim. Choose benchmarks that match the service and disclose their limits. Potential evidence includes an applicable contract or single-case agreement, comparable commercial allowed amounts, Transparency in Coverage data, credible cost information, Medicare as a transparent reference point where relevant, historical claim-specific payments, and clinical or operational complexity. No single benchmark is automatically controlling unless the governing plan or contract makes it so.
| Evidence | Useful when | Guardrail |
|---|---|---|
| Contract / SCA / LOA | A negotiated term may control | Prove entity, dates, services, and network chain |
| Commercial comparable rates | Showing market context | Match code, modifier, provider type, geography, and period |
| Transparency in Coverage data | Testing public plan-rate context | Validate plan, billing class, file quality, and exact service match |
| Facility cost evidence | Responding to a facility cost-up analysis | Use reliable claim-specific or audited data; explain allocations |
| Medicare reference | Creating a transparent common reference | Do not imply Medicare sets commercial payment unless incorporated |
| Clinical complexity | Showing why standard comparisons may be incomplete | Tie every assertion to the record and resource use |
State the exact requested amount or methodology, how it was calculated, and what the amount resolves. If proposing a settlement, define whether it closes only the claim, addresses patient balance billing, or affects future claims. Do not allow a one-claim resolution to become network participation or a broader rate agreement through ambiguous language.
6. Direct the negotiation to the right authority
A pricing vendor may explain or defend its recommendation while the plan, insurer, or TPA retains authority over benefits or settlement. Send the technical challenge to the methodology contact and the requested benefit or payment remedy to the entity identified by the plan's claims procedure. Request a coordinated written response when roles overlap.
For an ERISA group health plan, 29 C.F.R. § 2560.503-1 may give the claimant rights to a full and fair review and to relevant claim documents. Provider access depends on valid representative authority and plan procedures. Preserve the formal appeal separately from the commercial negotiation. For claims covered by the No Surprises Act, follow the applicable federal or state open-negotiation and dispute process instead of substituting a general repricer appeal.
7. Use a controlled negotiation record
- Create one claim chronology with submission, payment, notice, request, appeal, offer, counteroffer, and response dates.
- Record names, roles, call references, portals, email addresses, delivery proof, and stated authority.
- Maintain a versioned offer table showing amount, methodology, conditions, expiration, and disposition.
- Confirm verbal terms in writing before treating the matter as resolved.
- Track whether the agreed payment posted correctly and whether patient responsibility was adjusted as promised.
- Analyze results by plan, TPA, methodology, claim type, and evidence used—not only by gross percentage increase.
Related Millennova Legal resources
Review TPA and out-of-network commercial negotiation support and the broader TPA negotiation methodology guide. For benefit-claim record rights, see the ERISA provider appeal workflow. For qualifying surprise-billing claims, use the Federal IDR process guide.
Sources and methodology references
Frequently Addressed Procedural Questions
Review a commercial underpayment dispute
Discuss payer or TPA identity, claim-level methodology and counteroffer documentation after confirming plan rules and appeal options. Millennova Legal provides non-attorney operational and documentation support, not legal advice or representation.