Skilled nursing product in development

Ease currently serves behavioral health organizations and is planning a skilled nursing product. Discuss planned scope and availability.

Admissions and RCM directors

SNF Medicare Secondary Payer Review: Resolve Conflicting Coverage Before Recovery

Resolve conflicting SNF payer records with a dated employment, coverage and accident chronology, then reconcile any conditional-payment recovery separately.

Quick answer

Treat conflicting Medicare and other-insurance records as an evidence problem tied to service dates. Verify the facts that determine payer order, preserve the source chronology, and route corrections through the appropriate payer and coordination channels. Conditional payment is a separate, recoverable payment category under applicable rules. Do not turn an old insurance card, a payment receipt or a generic payer priority into a resident-specific coverage conclusion.

Resolve the facts that make the records disagree

A fictional SNF admission file contains an old employer insurance card, a Medicare eligibility response and an intake note saying “retired.” The billing record lists Medicare first. A later response identifies current employment-based coverage through the resident's spouse. The presence of three documents does not establish which is correct for the service dates.

CMS requires providers to maintain a process for identifying other payers and collecting relevant employment and insurance information. Its billing-responsibility guidance supports a deliberate inquiry, while the MSP overview explains why different facts lead to different payer-order branches.

This guide develops the administrative evidence file. Complex coverage, accident-relatedness and recovery determinations require the responsible specialists and actual payer instructions; the examples do not decide a real resident's liability.

Ask the question that distinguishes the relevant branch

For working-aged beneficiaries, CMS distinguishes coverage through current employment and employer-size conditions, including the 20-employee threshold and multi-employer considerations. For disability, its common-situation overview uses a 100-employee threshold with current employment through the beneficiary or a family member. ESRD has a distinct 30-month coordination framework. Retiree coverage is not equivalent to current employment coverage.

These are reasons to collect specific facts, not shortcuts around exceptions. An intake field labeled “commercial insurance” cannot distinguish them. Record whose employment provides coverage, whether it is current employment, relevant coverage dates and the information needed to evaluate employer-size and other applicable rules. Use the official MSP framework and contractor assistance for unresolved cases.

For accident-related services, separately establish the potentially responsible no-fault, liability or workers' compensation coverage and the relevant service relationship. A resident can have other coverage without every SNF service belonging to the same accident-related population.

Build a chronology that preserves the conflict

The original example assumes service dates of October 3–20. The following is an internal evidence register, not a coverage determination.

Evidence What it establishes What remains unresolved
Employer card copied at admission A policy identifier existed Current coverage and employment basis
Intake interview on October 3 Resident reports personal retirement Spouse's employment and dependent coverage
Medicare response on October 4 Medicare entitlement information Complete current payer-order facts
Later coverage response Reports spouse's employment-based plan Effective dates, current-employment basis and applicable employer facts
Employer/plan confirmation obtained October 12 Verifies the missing facts for the reviewed interval Specialist application of the governing MSP branch

The packet owner does not delete the early interview. It may have been accurate about the resident's own retirement while incomplete about the spouse. The later confirmation resolves the missing fact without pretending the earlier record said something else.

After qualified review, document the supported payer order and the affected dates. Route any incorrect coordination record and claim through the applicable correction channels. Keep evidence of those submissions and subsequent responses. Changing a local payer field does not prove that an external coordination record changed.

Reconcile a conditional-payment case separately

Consider a second fictional case involving a potential liability payment. CMS explains that Medicare may make a conditional payment when the relevant primary coverage will not pay promptly, subject to the applicable requirements and recovery when a settlement, judgment, award or other payment occurs. An ordinary primary payment and a conditional payment must not share an undifferentiated “Medicare paid” status.

Assume a recovery review lists $12,000 of Medicare payments. The facility's ledger contains $10,500 of those payments for its own services; $1,500 relates to another provider. The facility then finds a $2,000 reversal already applied within its $10,500 population. Its reconciliation shows $8,500 of unreversed facility payments, a $2,000 prior reversal and $1,500 outside its books.

That arithmetic is an evidence bridge, not the final recovery amount. Submit relevant discrepancies through the actual review route and retain the response. Do not subtract another provider's services from a demand merely because they are absent from the SNF ledger, and do not assume a ledger reversal has already updated the recovery record.

Close the loop across systems and responsibilities

The completed file links service dates, insurance facts, the payer-order decision, corrected claims and any recovery correspondence. Assign owners separately for factual verification, billing correction and recovery review so a resolved intake discrepancy does not leave an old demand unattended.

A platform demonstration should preserve both conflicting source records, the later evidence and the dated decision. It should also keep the conditional-payment reconciliation separate from ordinary claim status. The buyer is evaluating traceable coordination work, not a promise that software alone decides Medicare payer responsibility.

Questions & answers

Does Medicare eligibility prove Medicare is primary?

No. Medicare entitlement and payer order are separate questions. Employment-based coverage, ESRD coordination and accident-related coverage can change which payer has primary responsibility.

Does a conditional Medicare payment settle payer responsibility?

No. Conditional payments can be recovered when the relevant settlement, judgment, award or other payment occurs. Review the actual recovery correspondence and service population.

Can an SNF use one payer order for the entire stay?

Only if the verified facts support it. Coverage or employment facts may change during a stay, and accident-related responsibility may concern only relevant services.

Primary sources

Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.