Tag: Common Working File (CWF)

New SNF PPS Edits Highlight the Importance of Facility Agreements

Written by Brian Werfel on May 16, 2019. Posted in Medicare, Member-Only, Reimbursement, Talking Medicare.

On April 1, 2019, CMS implemented a new series of Common Working File (CWF) edits that are intended to better identify ground ambulance transports that are furnished in connection with an outpatient hospital service that is properly bundled to the skilled nursing facility (SNF) under the SNF Consolidated Billing regime.

These edits work by comparing the ambulance claim to the associated outpatient hospital claim. Hospital claims were already subject to CWF edits designed to identify outpatient hospital services that should be bundled to the SNF. These hospital edits operate by referencing a list of Healthcare Common Procedure Coding System (HCPCS) or Current Procedural Terminology (CPT) codes that correspond to outpatient hospital services that are expressly excluded from SNF Consolidated Billing. Hospital claims for outpatient services that are submitted with one of these excluded codes bypass the existing CWF edits, and are then sent to the appropriate Medicare Administrative Contractor for further editing and payment. Hospital claims submitted without one of these codes are denied for SNF Consolidated Billing.

The new ambulance edits will extend these process one step further. The ambulance claim will be associated with the outpatient hospital claim on the same date. To the extent that hospital claim is bundled under SNF Consolidated Billing, the associated ambulance claim will also be bundled. To the extent the hospital claim is unbundled, the associated ambulance claim will be unbundled.

In order for these new edits to work properly, there must be an outpatient hospital in Medicare’s claim history. If the ambulance claim beats the hospital claim into the system, the ambulance claim will be rejected. If and when an outpatient hospital claim with the same date of service enters Medicare’s system, the initial rejection of the ambulance claim will be overturned, and the ambulance claim will be reprocessed using the same edits.

It is important to note that the new edits were designed to reject the ambulance claim as a bundled service unless the hospital claim indicates that it should not be bundled. In other words, these edits are designed to be “over inclusive.” This over-inclusiveness creates the potential for ambulance denials in situations that, on their face, would not appear to be bundled.

A few examples will help illustrate this point. Imagine a situation where the patient elects, for whatever reason, to pay out-of-pocket for their hospital care (in a situation where that care would not be bundled to the SNF), and, as a result, the hospital does not submit a bill to Medicare for its services. Based on how the new edits are designed, your ambulance claim for the transport to that excluded service will be rejected based on the lack of a hospital claim. Or maybe the patient has both Medicare and the V.A., and has elected to have the V.A. be the primary payer for their required hospital care. Again, there would likely be no outpatient hospital claim submitted to Medicare on that date of service, resulting in the rejection of your ambulance claim.

I can see your point, but those examples are pretty far-fetched. How big an issue is this really?

I agree those examples are pretty far-fetched. However, there are other situations that create the same problem. For example, what about an emergent response to transport an SNF patient to the hospital for necessary emergency services? Imagine if you are called to respond late at night (e.g., 11:30 p.m.) tonight. Now imagine that, by the time you get to the patient, load them into the vehicle, and transport them to the ED, it has crossed over midnight into the next day.

What date of service is going to be on the hospital’s claim? Almost certainly, the hospital will use tomorrow’s date. As a result, when your claim hits Medicare’s system, there will not be an associated hospital claim, which will result in your claim being rejected as the responsibility of the SNF. In this situation, Medicare’s edit has worked as intended, but the result is the denial of a claim that should be separately payable by Medicare Part B.

Okay, I can see how this might be annoying,
but I can appeal the claim and likely win on appeal, right?

Yes and no. The problem is that you are not likely to win on either of the first two levels of appeal, as they are likely going to rely upon the information in the CWF. I can see you possibly winning your appeal at the ALJ level…5 to 7 years from now.

In other words, the appeals process is unlikely to provide an acceptable resolution. Instead, I think the majority of ambulance providers are going to look to the SNFs to make good in these situations. Of course, the SNFs are likely going to disclaim liability, arguing (correctly) that ambulance transportation to an ED is an excluded service.

This is where the agreement with the SNF comes into play. One key purpose of contracts is to allocate known risks between the parties. In this instance, the “risk” that needs to be addressed is the possibility that Medicare might incorrectly reject your claim thinking it is bundled to the SNF. I would argue that this risk should be absorbed by the SNF. The transport to the ED should have suspended the patient’s SNF stay, which would have allowed you to receive a separate payment from Medicare. However, the fact that your claim was rejected is proof positive that the CWF does not reflect the suspension of the patient’s SNF stay. Indirectly, it also serves as proof that the SNF received a per diem payment for the patient on that date. To me, the fact that they accepted the per diem payment means they accepted the risk of a bundled ambulance service on that date. I would also argue that it was their failure to properly suspend the patient’s SNF stay that set in motion your denial. Either way, I would be looking to the SNF for payment.

Based on my experience, the typical agreement with an SNF does not address this situation. Frequently, these agreements do not even address the specifics of SNF Consolidated Billing. Instead, I tend to see general language indicating that the ambulance provider will bill the SNF when payment responsibility lies with the SNF under an applicable federal or state health care program. I doubt that language is going to convince an SNF to take financial responsibility for the situation discussed above.

The good news is that your existing agreements can easily be revised to address this situation. The language I would recommend is something along the lines of:

“The parties acknowledge and agree that a denial from Medicare for SNF consolidated billing shall constitute conclusive evidence that a transportation service is the financial responsibility of the facility.”

In sum, the new SNF Consolidated Billing edits are going to increase the frequency with which we are forced to look to the SNFs for payment. In most instances, it will be a situation where the SNF is legally responsible under SNF Consolidated Billing. However, there will also be situations where the over-inclusive nature of the edits results in the claim being incorrectly denied as the SNF’s responsibility. The question becomes how you want to handle these incorrect denials. Do you want to appeal and hope CMS reverses its decision? Or do you want to hold the SNF responsible? If you want to hold the SNF responsible, you will likely need to revise your agreements with the SNFs.

Have an issue you would like to see discussed in a future Talking Medicare blog?
Please write to me at bwerfel@aol.com.

Update on New SNF Edits

Written by Brian Werfel on March 19, 2019. Posted in Medicare, Member Advisories, Member-Only, News, Reimbursement.

CMS Set to Implement New Common Working File Edits to Identify Ambulance Services Provided in Connection with Outpatient Hospital Services that should be bundled to the SNF under Consolidated Billing.

In a Member Advisory issued last week, the AAA provided an update on a series of new Common Working File (CWF) edits intended to identify ambulance transports furnished in connection with outpatient hospital services that are properly bundled to the skilled nursing facility under the SNF Consolidated Billing regime. These new edits are set to go into effect on April 1, 2019.

In our discussion of the implementation specifics, we attempted to answer the question of what would happen when an ambulance claim is submitted prior to the receipt of the associated hospital outpatient claim, and where the associated hospital claim eventually hit Medicare’s system. Specifically, we indicated as follows:

“The Transmittal contains further instructions that the CWF be updated to identify previously rejected ambulance claims upon receipt of an associated hospital claim for the same date of service that contains an Exempted Code. Once identified, the Shared System Maintainer (SSM) is supposed to adjust the previously rejected or denied ambulance claim. At this point, the nature of that “adjustment” is unclear, i.e., it is unknown whether the SSM will automatically reprocess the ambulance claim for payment. The AAA is seeking additional clarification from CMS on this important point.”

On March 15, 2019, CMS responded to our request for clarification. Specifically, CMS indicated that it has instructed the SSM and/or its Medicare Administrative Contractor (MAC) to automatically reprocess claims that were rejected for lack of an associated hospital outpatient claim.

Upon reprocessing, the claims will pass the edits to the extent the associated hospital claim contains a HCPCS or CPT code that indicates that the hospital outpatient service was excluded from SNF Consolidated Billing. Such claims would then be forwarded to the MAC for further editing, and either paid or denied. By contrast, when the associated hospital outpatient claim contains HCPCS or CPT codes that suggest the hospital services should be bundled to the SNF, the claim will be reprocessed and denied by the MAC with a remittance advice code indicating that the SNF is financially responsible.

AAA Webinar on New SNF Consolidated Billing Edits

March 27, 2019 | 2:00 PM Eastern
Speakers: Brian Werfel, Esq.
$99 for Members | $198 for Non-Members

Join AAA Medicare Consultant Brian Werfel, Esq., to go over the new SNF Consolidated Billing edits that go into effect April 1, 2019. These edits are being implemented by CMS in response to 2017 investigation by the HHS Office of the Inspector General that determined that CMS lacked the appropriate claims processing edits to properly identify ambulance transports provided in connection with hospital outpatient services that are not expressly excluded from SNF PPS. The implementation of these new edits will force ambulance providers and suppliers to rethink their current claims submission processes for SNF residents. Ambulance providers and suppliers will need to make a decision on what to do with these claims moving forward. Sign up today to make sure your service is ready!

CMS SNF Edits Go Into Effect – April 1, 2019

Written by Brian Werfel on March 11, 2019. Posted in Medicare, Member Advisories, Member-Only, News, Reimbursement.

CMS Set to Implement New Common Working File Edits to Identify Ambulance Services Provided in Connection with Outpatient Hospital Services that should be bundled to the SNF under Consolidated Billing

On November 2, 2018, the Centers for Medicare and Medicaid Services (CMS) issued Transmittal 2176 (Change Request 10955), which would establish a new series of Common Working File (CWF) edits intended to identify ambulance transports furnished in connection with outpatient hospital services that are properly bundled to the skilled nursing facility under the SNF Consolidated Billing regime. These new edits are set to go into effect on April 1, 2019.

Why these edits are necessary?

In 2017, the HHS Office of the Inspector General conducted an investigation of ground ambulance claims that were furnished to Medicare beneficiaries during the first 100 days of a skilled nursing home (SNF) stay. Under the SNF Consolidated Billing regime, SNFs are paid a per diem, case-mix-adjusted amount that is intended to cover all costs incurred on behalf of their residents. Federal regulations further provide that, with limited exceptions, the SNF’s per diem payment includes medically necessary ambulance transportation provided during the beneficiary’s Part A stay. The OIG’s report was issued in February 2019.

The OIG conducted a review of all SNF beneficiary days from July 1, 2014 through June 30, 2016 to determine whether the beneficiary day contained a ground ambulance claim line. The OIG excluded beneficiary days where the only ambulance claim line related to: (1) certain emergency or intensive outpatient hospital services or (2) dialysis services, as such ambulance transportation would be excluded from SNF Consolidated Billing. The OIG determined that there were 58,006 qualifying beneficiary days during this period, corresponding to $25.3 million in Medicare payments to ambulance suppliers.

The OIG then selected a random sample of 100 beneficiary days for review. The OIG determined that 78 of these 100 beneficiary days contained an overpayment for the associated ambulance claims, as the services the beneficiary received did not suspend or end their SNF resident status, nor was the transport for dialysis. The OIG determined that ambulance providers were overpaid a total of $41,456 for these ambulance transports. The OIG further determined that beneficiaries (or their secondary insurances) incurred an additional $10,723 in incorrect coinsurance and deductibles.

Based on the results of its review, the OIG estimates that Medicare made a total of $19.9 million in Part B overpayments to ambulance suppliers for transports that should have been bundled to the SNFs under SNF Consolidated Billing regime. The OIG estimated that beneficiaries (and their secondary insurances) incurred an additional $5.2 million in coinsurance and deductibles related to these incorrect payments.

The OIG concluded that the existing edits were inadequate to identify ambulance claims for services associated with hospital outpatient services that did not suspend or end the beneficiary’s SNF resident status, and which were not related to dialysis. The OIG recommended that CMS implement additional edits to identify such ambulance claims.

Overview of new claims processing edits

In response to the OIG’s report, CMS issued Transmittal 2176, which implements a new series of claims processing edits to identify ambulance claims associated with outpatient hospital services that should be bundled to the SNF. As noted above, these edits will go into effect on April 1, 2019.

These new claims processing edits are somewhat complicated. In order to properly understand how these claims edits will work, it is helpful to understand that CMS already has claims processing edits in place to identify hospital outpatient claims that should be bundled to the SNF. These CWF edits operate by referencing a list of Healthcare Common Procedure Coding System (HCPCS) or Current Procedural Terminology (CPT) codes that correspond to outpatient hospital services that are expressly excluded from SNF Consolidated Billing. Hospital claims for outpatient services that are submitted with one of these excluded codes bypass the existing CWF edits, and are then sent to the appropriate Medicare Administrative Contractor for further editing and payment. Hospital claims submitted without one of these codes are denied for SNF Consolidated Billing. For convenience, the list of HCPCS and CPT codes excluded from SNF Consolidated Billing is hereinafter referred to as the “Exempted Codes.”

The new edits for ambulance claims will compare Part B ambulance claims to the associated outpatient hospital claim to see whether or not that hospital claim is excluded from SNF Consolidated Billing.

Specifics related to new claims processing edits

Under these new edits, the CWF will reject an incoming ambulance claim whenever the beneficiary is determined to be in an SNF Part A stay if either:

There is no associated outpatient hospital claims for the same date of service on file; or
There is an associated outpatient hospital claim for the same date of service on file (paid or denied), but where that outpatient hospital claim does not contain at least one Exempted Code.

When an incoming ambulance claim is rejected by the CWF, it will be sent to the applicable Medicare Administrative Contractor and rejected (Part A Ambulance Providers) or denied (Part B Ambulance Suppliers) using the applicable Claim Adjustment Reason Code/Remittance Advice Remark Code for SNF Consolidated Billing. In other words, the ambulance claim will be denied with an indication that youshould bill the SNF.

The Transmittal contains further instructions that the CWF be updated to identify previously rejected ambulance claims upon receipt of an associated hospital claim for the same date of service that contains an Exempted Code. Once identified, the Shared System Maintainer (SSM) is supposed to adjust the previously rejected or denied ambulance claim. At this point, the nature of that “adjustment” is unclear, i.e., it is unknown whether the SSM will automatically reprocess the ambulance claim for payment. The AAA is seeking additional clarification from CMS on this important point.

Potential concerns for ambulance providers and suppliers

Based on the current experience of hospital providers, the AAA is cautiously optimistic that the new edits can be implemented in a way that proper identifies ambulance transports associated with hospital outpatient claims that should be bundled to the SNF vs. those that correctly remain separately payable by Medicare Part B.

However, the AAA has some concerns with the manner in which CMS intends to apply these edits. Ambulance providers and suppliers are typically in a position to submit their claims earlier than the corresponding hospital, many of which submit claims on a biweekly or monthly cycle. This creates a potential timing issue. This timing issue arises because the edits will reject any ambulance claim that is submitted without an associated hospital claim on file. In other words, even if the hospital outpatient service is properly excluded from SNF Consolidated Billing, the ambulance claim will still be rejected if it beats the hospital claim into the system. The hope is that CMS will subsequently reprocess the ambulance claim once the hospital claim hits the system. However, at this point in time, it is unclear whether these claims will be automatically reprocessed, or whether ambulance providers and suppliers will be forced to appeal these claims for payment.

One option available to ambulance providers and suppliers would be to hold these claims for a period of time, in order to allow the hospitals to submit their claims. By waiting for the hospital to submit its claim, you can ensure that your claims will not be denied solely due to the timing issue. This should eliminate the disruption associated with separately payable claims being rejected and then subsequently reprocessed and/or appealed. It would also give you a degree of certainty when billing the SNF for claims that are denied for SNF Consolidated Billing. However, holding claims carries an obvious downside, i.e., it will disrupt your normal cash flow.

To summarize, the implementation of these new edits will force ambulance providers and suppliers to rethink their current claims submission processes for SNF residents. Ambulance providers and suppliers will need to make a decision on whether to hold claims to minimize the potential for problems, or to continue their existing submission practices and deal with any issues as they arise.

AAA webinar on new SNF Consolidated Billing edits