PMSI - Settlement Solutions PMSI - Settlement Solutions

CMS Provides New Self-Calculated Final Conditional Payment Amount Option

By , December 20, 2011 12:05 pm

CMS issued an Alert which provides an option for certain liability settlements below $25,000 to obtain a final Medicare conditional payment demand prior to settlement starting in February 2012. Under this option, the beneficiary or their representative will calculate the amount of Medicare’s conditional payment amount using information received from the MSPRC, the MyMedicare website, or other claims information available to the beneficiary. The MSPRC will review this amount and, if finding the amount accurate, will respond with Medicare’s final conditional payment amount within 60 days.

To secure the final conditional payment amount, the beneficiary must settle within 60 days after the date of Medicare’s response. Additionally, the alert confirms that ALL the below criteria must be met:

1. The liability (including self-insurance) settlement is for a physical trauma based injury (the settlement does not relate to ingestion, exposure, or medical implant);

2. The total liability settlement, judgment, award, or other payment will be $25,000 or less;

3. The Date of Incident occurred at least six months before the beneficiary or their representative submits the proposed conditional payment amount to Medicare;

4. The beneficiary demonstrates that treatment has been completed and no further treatment is expected either through a written physician attestation or by certifying in writing that no medical treatment related to the case has occurred for at least 90 days prior to submitting the proposed conditional payment amount to Medicare

A full explanation, including instructions on how and when to elect this option, will be available on the MSPRC website by January 15, 2012. This option is an “initial step” to provide beneficiaries and their representatives with Medicare’s conditional payment amount prior to settlement and CMS plans to expand this option as it gains experience with this process.

At this time, the self-calculation option will only be helpful for a small portion of liability settlements. However, if CMS truly expands the option to a larger group of settlements, it would greatly assist the liability community and avert the common issue of holding the release of settlement funds pending Medicare conditional payment demand.

PMSI believes that this alert, as well as other recent MPSRC changes (as noted in our October 26, 2011 blog) is a reaction to the proposed SMART Act. The SMART Act calls for the ability of parties to obtain final conditional payment amounts prior to settlement. As the SMART Act continues to garner increased bi-partisan support, CMS may be looking to stay in control and avert the need for legislation to reform the conditional payment recovery process.

To view the alert in its entirety please visit the MSPRC website.

Share

The Medicare Secondary Payer Act in 2011: A Busy, Busy Year

By , December 19, 2011 11:29 am

This year, 2011, was an extremely busy year for Medicare Secondary Payer Act (MSP) related information and case law– quite possibly the busiest year in the past ten years. As 2012 is looking to be another active year, it is important to have a firm grasp and understanding of some of the information promulgated by the Centers for Medicare & Medicaid Services (CMS) in 2011, state level enforcement of the MSP, as well as MSP case law before moving onto 2012. Please find below a brief synopsis of some of the more seminal changes affecting MSP compliance which occurred in 2011.

CMS Memoranda as well as full legal bulletins on most cases described below can be viewed in PMSI’s Knowledge Center under CMS Memos and Other Communications and Legal Bulletins, respectively.

CMS Memoranda

May 11, 2011- CMS reiterates their guidelines for submission of  Workers’ Compensation Medicare Set-Asides (WCMSAs) for review and approval. Submission of WCMSAs to CMS that meet CMS review threshold is a recommended (voluntary) procedure and is not mandated. Settlements with MSAs that fall outside CMS review threshold will not be reviewed .1

September 29, 2011- CMS issues their first memorandum addressing liability MSAs (LMSAs). The memorandum states that if the treating physician certifies in writing that no future treatment is needed, that Medicare will consider its interests protected. 

MSP Case Law

Hadden v. U.S.2 – On November 21, 2011, the Sixth Circuit affirmed the district court’s opinion holding that the MSP required Vernon Hadden to reimburse Medicare to the full extent that the government advocated. It was hoped by those in support of the appeal that the Sixth Circuit would overturn the district court’s decision, which held that the MSP requires full reimbursement of Medicare conditional payment demands regardless of apportionment or comparative fault principles. This case may ultimately be appealed to the Supreme Court. Until such time, tortfeasors and Medicare beneficiaries can continue to expect that Medicare may obtain full recovery of their conditional payment demands, up to the amount of the settlement.

Haro v. Sebelius3- On May 5, 2011, putative class Plaintiffs, Medicare beneficiaries, and an attorney representing the beneficiaries sought a summary judgment that the Secretary’s conditional payment collection practices were not authorized by Congress, not a permissive interpretation of the MSP, and a violation of the Due Process clause of the Constitution. The Plaintiffs further sought class certification and an injunction against CMS from making premature threats from commencing a collection action before waiver or appeal was pursued. The Court found for the Plaintiffs and granted class certification as well as an injunction against CMS as requested.

USA v. Stricker4- On August 12, 2011, the District Court rejected the government’s motion for reconsideration based upon a theory of continuing accrual, that the statute of limitations re-starts each time a class member receives a settlement payment. In September of 2010, the government’s complaint was dismissed due to the fact that the claim was barred by the statute of limitations (a six year statute of limitations was to be applied to those claims in which the underlying claim was contract; three years was to be applied to those claims in which the underlying claim was a tort). In November of 2011, the government filed a notice with the court that they further planned to appeal the court’s decision. Whether the government will revive their theory of continuing accrual is not yet known.

State Level MSP Enforcement

Maryland- On November 28, 2011, Maryland enacted regulations centered on requiring the consideration of Medicare’s interests before a settlement can be formally approved. The regulations do not mandate submission of MSAs that meet the CMS workload review thresholds and that are purely voluntary, but require that specific items which address Medicare’s interests be contained in the settlement documents.

Kentucky- On February 3, 2011, Kentucky introduced proposed legislation which would require “settlements for future medicals to be approved by the federal Medicare Secondary Payer Act.” The proposed legislation did not pass and it is unclear whether it will be revived in 2012. 

Western District of New York- On May 6, 2011, the U.S. Attorney’s Office for the Western District of New York issued an MSP Protocol for liability settlements. If parties to a liability settlement of over $350,000 are not able to obtain review of the LMSA by CMS and meet other certain requirements, the U.S. Attorney’s office will opine on the sufficiency of the LMSA.

MSP Trends in Liability

Conditional Payments- In September, the MSPRC issued an alert that it would not seek recovery of conditional payment demands where the settlement is $300 or less and other criteria are met.

Additionally, in October, the MSPRC issued an alert that beneficiaries who receive a liability settlement of $5000 or less and meet other criteria can pay a fixed percentage of their settlement instead of opting for the traditional recovery process. For more information, please visit www.msprc.info.

Liability MSAs (LMSAs)- In both of the following cases which occurred in 2011, the court included or required an LMSA to consider Medicare’s interests as part of the liability settlement: Hinsinger v. Showboat Atlantic City5 and Big R Towing v. Benoit6.

Legislative Proposals

Strengthening Medicare and Repaying Taxpayers Act of 2011 (SMART Act) – This bill was introduced to the House of Representatives on March 14, 2011. The SMART Act seeks reform of the enforcement of the MSP, namely as it affects conditional payment collection and MMSEA Mandatory Insurer Reporting. Some examples of initiatives proposed would be to set the statute of limitations for conditional payment reimbursement at three (3) years, and make the MMSEA penalty of $1000 per claim/per day discretionary rather than mandatory. The SMART Act gained large bi-partisan support in the House and moved to the Senate in October of 2011. Whether the bill will pass in the Senate remains to be seen as we move into 2012.

In conclusion, 2011 was a very busy year for those affected by the MSP. We saw a dramatic rise in MSP case law, more states creating requirements for Medicare’s interests to be considered as part of settlements, increased awareness surrounding liability MSAs, and reform efforts surrounding MSP enforcement.


1. [The CMS review thresholds remain unchanged and are the following: Class 1: Medicare Beneficiary and Total Settlement Amount exceeding $25,000; Class 2: Reasonable Expectation of Medicare Entitlement within 30 months of the Settlement date and the anticipated Total Settlement Amount exceeds $250,000.]

2. [2011 U.S. App. LEXIS 23289, United States Court of Appeals for the Sixth Circuit.]

3. [CV 09-134 TUC DCB, (D.AZ.) (May 5, 2011). ]

4. [No. CV-09-BE-2423-E (N.D. Ala. Aug. 12, 2011).]

5. [No. CV-09-BE-2423-E (2011 N.J. Super LEXIS 96 (January 21, 2011).]

6. [2011 U.S. Dist. LEXIS 1392 (W.D. La. Jan. 5, 2011). This case involved a Jones Act claim which is considered a liability claim for CMS submission purposes.]

Share

CMS Issues RFP for MSP Business Program Operations Contract

By , December 15, 2011 2:35 pm

In a previous blog dated September 23, 2011, we announced the confirmation that the MSPRC contract which was previously held by Chickasaw Nation Industries (CNI) would not be renewed when it expired on September 30, 2011 (the contract had been in effect since 2006).  CMS confirmed that they would be seeking to establish a centralized Coordination of Benefits (COB) and Medicare Secondary Payer Recovery (MSPR) operation by consolidating the two units.   In the interim, Group Health Incorporated (GHI) will be overseeing the recovery process. 

On December 8, 2011, CMS posted an RFP (Solicitation Number: RFP-CMS-2011-0048) for an MSP Business Program Operations Contract to establish a centralized operation by consolidating under a single program, the performance of all activities that support the collection, management, and reporting of other insurance coverage of Medicare beneficiaries, and the collection of mistaken primary payments. The intent of the consolidation is to provide quality customer service and a single source to Medicare providers, suppliers, beneficiaries, insurers, and other stakeholders by streamlining the MSP data and debt collection processes while ensuring the integrity of the Medicare Trust Funds.

PMSI believes that the industry would welcome this integration with the hope that it will lead to an improvement in the overall recovery process, particularly the length of time currently involved in verifying and resolving conditional payments.  We will continue to monitor the transition as well as the RFP process and will post additional information as it is received. 

 

Share

Transitional Relationships and Roles under Section 111

By , December 13, 2011 4:28 pm

Regulatory guidelines for MSP and MMSEA compliance are frequently changing, and it is no surprise that the reach of the types of entities impacted by these laws are constantly changing as well.  Multiple entities can be involved in the process of managing and handling claims, such as insurance carriers, employers, and third party administrators. In reference to MMSEA Section 111, reporting agents also come into play.  With such hefty fines threatened with non-compliance ($1000 per claim/per day), it is important for everyone involved in this process to understand their roles and obligations. 

Section 111 reporting has become an important factor to consider when a transition in these relationships occurs. Examples of these types of transitions include switching TPAs or an acquisition of one RRE by another RRE. Insurance carriers and employers who are RREs now need to consider a new reporting structure and/or process in order to remain compliant with Section 111 guidelines during the transition. Points to consider include:

  • Which claims are involved in the take over process?
  • Are any additional RRE IDs required and/or do any need to be placed in an inactive status?  
  • Is there a change in reporting agent?
  • Has there been a change in RRE responsibility?
  • When will the change take place?
  • What is the RRE’s quarterly reporting schedule?

Transitional Relationship Scenario #1- New TPA
When transitioning claims from one TPA to another, an RRE will need to identify which claims will be involved in the takeover process.   For example, will a new TPA be handling only new claims for an RRE on a go-forward basis or will they also be taking over existing claims? If only new claims will be moving to the new TPA, it is possible that a new RRE ID will be needed, depending on how each TPA is handling Section 111 reporting.  Section 8.2 of the NGHP User Guide states the following in regard to multiple RRE IDs: “Only one Claim Input File may be submitted on a quarterly basis for each RRE ID. Due to corporate organization, claim system structures, data processing systems, data centers and agents that may be used for data submission, you may want to submit more than one Claim Input File to the COBC on a quarterly basis and therefore will need more than one RRE ID in order to do so.”

On the other hand, an RRE may have the option to discontinue using a previously established RRE ID if claims will now be administered by TPAs utilizing the same reporting agent.  If multiple RRE IDs were obtained, the RRE may be able to condense reporting under fewer RRE IDs based on the new reporting structure.

Transitional Relationship Scenario #2- New Reporting Agent
If an RRE is changing reporting agents, the new agent should continue to submit files under the RRE’s existing RRE ID(s). The COBC cannot supply a file of previously submitted and accepted records for the RRE IDs.  The RRE will need to ensure the new reporting agent is granted access to the RRE ID via the COBSW by inviting the appropriate members of the new agent as account designees. If applicable, the new reporting agent may take on the account manager role, for which a written request will need to be made to the EDI Representative. 

Section 8.3.3 of the NGHP User Guide states, “Updates to other information such as changing reporting agent, changing from one file transmission method to another, changing from DDE to a file transmission method, overriding the 500 claim limit for DDE, or changing the TIN associated with the RRE ID must be requested through your EDI Representative. You must also contact your EDI Representative to change your Authorized Representative or Account Manager to a different individual.”

The new agent will only be able to submit and access files for the RRE once these changes are made.  In addition, the account manager should ensure account designees associated with the previous reporting agent or associated organizations are removed.

Transitional Relationship Scenario #3- Change in RRE
It is also possible for a change in RRE to occur.   According to CMS, the transition of reporting responsibility in whole or in part, from one RRE to another is the responsibility of the entities involved.  If this occurs, it is important to ensure that the COBC no longer expects claims to be submitted under existing RRE ID(s) by submitting a written request via email to the assigned EDI Representative requesting that the RRE ID be placed in an inactive status.  If production files were never submitted under the RRE ID, then the ID can be deleted.

Section 8.3.2 of the NGHP User Guide states, “the new RRE may register for a new RRE ID or report the transitioned claim records under one of its existing RRE IDs. The new RRE may update and delete records previously submitted by the former RRE under a different RRE ID as long as the key fields for the records match. Key fields are injured party HICN or SSN, CMS date of incident, plan insurance type (liability, no-fault, or workers’ compensation) and ORM indicator. The RRE IDs do not need to match. The former RRE must NOT delete previously submitted and accepted records. If the ORM previously reported has ended, then update transactions should be sent with applicable ORM Termination Dates. The new RRE may send add transactions for new ORM and new claims with TPOCs or update transactions to change existing records with new information such as the new RRE TIN.”

It is important that the RRE will need to identify whether the date of any transition will interfere with their quarterly reporting schedule.  If there is any risk that claims may not be submitted through the query process or for the quarterly submission timely, they should notify the EDI Representative regarding the details of the transition or takeover process and coordinate the proper steps that should be taken to avoid any potential risk.

Whether the RRE role is transitioning to you or away from you, you will have a role to play within this process. CMS makes this clear by stating that the “transition of reporting responsibility from one RRE to another is the responsibility of the RREs involved.” It is important to understand the tasks involved, your responsibility in the process, and any issues with regard to the timing of the change. Communication between the RREs, reporting agents, and the COBC is essential and should be coordinated to ensure a smooth transition. The transition of claim responsibility from one RRE to another can be a complex task with several moving parts but with careful synchronization and communication, the daunting task can be accomplished. 

Regardless of the type of transition taking place, changes with respect to Section 111 can be complicated but must be effectuated correctly or noncompliance can occur. PMSI recommends that you consult with your reporting agent, CMS, COBC, as well as the User Guide and/or any other available written guidance from CMS prior to undertaking any of these transitions.

Share

Panorama Theme by Themocracy