Humana’s Brian Bargender Gives Tips on How to Work with Medicare Part C & D Plans

May 12, 2022

Chalk board with Medicare Part C & D

Attendees of Tower’s Premier Webinar on April 20 received sound advice on how to work with Medicare Part C (Advantage) and D (Drug Benefits) plans. Our guest presenter was Brian Bargender, Consultant, Subrogation and Third-Party Liability with Humana, a nationally recognized expert on these plans.

Bargender noted that these plans have the same rights and responsibilities as original Medicare under the Medicare Secondary Payer (MSP) Act. This means that Part C and D plans must avoid payment for treatment covered by primary payers, such as workers’ compensation or liability. Part C plans take this commitment seriously as they want to prove they are more efficient than original Medicare.

The PAID Act gave primary payers visibility into Medicare beneficiary enrollment status in Parts C and D. Previously, they could only see that an individual was enrolled in Medicare. It was problematic to identify a beneficiary’s plan and resolve conditional payments. The growing popularity of Medicare Advantage plans was making the process more time consuming. Approximately 46% of Medicare beneficiaries use Part C and 75% of the ones on original Medicare have Part D.

Bargender explained the plans’ approach to MSP compliance and touched on Private Cause of Action and Double Damages in the MSP Act. Medicare Advantage plans can obtain double damages from primary payers that refuse to reimburse conditional payments. And primary payers remain liable for repayment until plans are repaid, even if they have already paid the injured worker their settlement.

To make it easier to work with Part C and D plans in light of the PAID Act, Bargender offered these insights and advice:

  • While Section 111 reporting gives primary payers “an” address, it’s not necessarily the address the plan would have chosen. As such, further investigation into the appropriate plan contact may be necessary.
  • Medicare Advantage plans get Section 111 data, but not always in time to act on it. They use it as a back sweep to see if they missed anything.
  • Contact the plans before trying their recovery vendors; they have multiple vendors.
  • Ask for the subrogation or legal departments. Customer service reps at C and D plans are not well versed in Medicare Set-Asides.
  • It’s hard for Medicare Advantage and drug plans to predict and staff for call volume; prepare for delays.
  • The plan may not have the file when payers contact them.
  • It’s good for primary payers to notify the plan(s) when they accept responsibility for the claim, and certainly when they prepare for settlement. The Centers for Medicare and Medicaid Services (CMS) notifies plans later in the process.
  • To minimize calls and delays, provide plans the same information given to CMS for Ongoing Responsibility for Medical (ORM) or Total Payment Obligation to Claimant (TPOC) reporting along with the MSA diagnosis and prescription drug details if they are available.
  • At minimum, plans need this data:
    • Medicare Beneficiary Identifier
    • Name
    • Date of birth
    • Loss/Injury Date
  • Part C and D plans cannot correct errors in the file; these must be done through Section 111 reporting or through the Benefits Coordination and Recovery Center (BCRC).
  • These plans do not track how funds are used or exhausted. They need a letter from CMS to the MSA administrator or beneficiary that says funds were properly exhausted before they can start paying for injury care.

Tower has found Bargender and Humana’s subrogation team to be very helpful. They promptly identify specific reimbursement claim information when the claimant is enrolled in a Humana Medicare Advantage plan. Further, they are open to understanding the liability issues and basis for settlement; this is something not typically found with the Medicare conditional payment recovery contractors.

As Bargender stressed, “proactive beats reactive,” when it comes to resolution of these Part C and D claims. Primary payers must be proactive in using PAID Act data to identify whether a Medicare eligible claimant is enrolled in a MA plan, and, if so, investigate whether the plan is seeking reimbursement for payments it made on the claim.

For our Section 111 reporting clients, Tower has the PAID Act data readily available. Whether you are a reporting or non-reporting client, we can help you contact the Part C and/or D plan to investigate and resolve conditional payments at the time of settlement.

If you have questions or want a link to the recorded webinar, please contact Dan Anders at Daniel.anders@towermsa.com

Related articles

The PAID Act: Implementation and Implications for Claims Handling

CMS to Hold Webinar on “Go Paperless” Feature in MSPRP

March 28, 2022

Tower MSA Partners covers CMS new guide on Medicare conditional payment appeals and the upcoming Section 111 reporting webinar.

On April 13, 2022, at 1:00 pm ET, the Centers for Medicare and Medicaid Services (CMS) will host a webinar on the “Go Paperless” option in the Medicare Secondary Payer Recovery Portal.  The selection of this option will provide for more expeditious receipt of correspondence from the CMS Medicare conditional payment recovery contractors.  Per the announcement:

The Centers for Medicare & Medicaid Services (CMS) will be hosting an overview of the new “Go Paperless” feature available in the Medicare Secondary Payer Recovery Portal (MSPRP). Insurers and authorized agents may now choose to opt-in to paperless functionality. Once registered, users will be able to quickly and easily access all recovery correspondence including demand letters, using the MSPRP. Opting to “Go Paperless” in combination with the ability to submit correspondence through the MSPRP and the multiple available options for electronic payment will allow your organization to not only reduce the amount of paper that needs to be physically handled, associated workload and environmental impacts, but also eliminate concerns about delays that can arise when information is sent through the mail.

The webinar will feature opening remarks and a presentation, followed by a question-and-answer session.

Note, there is no pre-registration, instead, just follow the provided link shortly before the webinar start time.

By way of background, in January CMS released an updated Section 111 User Guide, Version 6.7, which in Chapter V provides as follows:

When there is an active Medicare Secondary Payer Recovery Portal (MSPRP) account for the insurer/recovery agent TIN, Section 111 submitters may set Go Paperless options (i.e., choose to receive letters electronically or by mail) for the insurer and recovery agent address using the following new TIN Reference File fields (Appendix B):

  • TIN/Office Code Paperless Indicator (Field 23)
  • Recovery Agent Paperless Indicator (Field 24)
  • Recovery Agent TIN (Field 25

Note: There are also five new fields (Fields 48-52) returned for these entries on the TIN
Reference Response File (Appendix D).

Along with the updates to the Section 111 User Guide, CMS also updated the Medicare Secondary Payer Recovery Portal (MSPRP) User Manual, Version 5.3, to incorporate functionality around the Go Paperless option.

Key Takeaways

We are pleased to see CMS provide this Go Paperless option for Responsible Reporting Entities (RREs) and their authorized agents. It is environmentally friendly and will allow time-sensitive correspondence i.e., Conditional Payment Notice with a 30-day due date, to be received and acted upon sooner.

If you are interested in taking advantage of the Go Paperless option or have other questions we encourage you to attend the CMS webinar.  Also, you can always contact Dan Anders, Chief Compliance Officer, at 888.331.4941 or daniel.anders@towermsa.com with any questions.

CMS Clarifies Policy on Non-Submit MSAs in Updated Reference Guide

March 22, 2022

book marked by sticky notes illustrating changes Section 111 reporting on ORM

The January 2022 addition of Section 4.3 to the CMS WCMSA Reference Guide that discussed the agency’s treatment of non-submit Medicare Set-Asides caused quite a stir throughout the MSA industry and raised many questions for those who use non-submit MSAs in workers’ comp settlements.  A February CMS webinar addressed some of those questions and we now have an update (Version 3.6) to the CMS WCMSA Reference Guide that modifies and clarifies this section.

Revisions to Section 4.3

Below is a breakdown of the revisions to Section 4.3 along with comments.

More general language around non-submit MSAs

The original language called out certain MSA products as indemnifying:

“A number of industry products exist with the intent of indemnifying insurance carriers and CMS beneficiaries against future recovery for conditional payments made by CMS for settled injuries.”

The new language is more general:

“A number of industry products exist for the purpose of complying with the Medicare Secondary Payer regulations without participation in the voluntary WCMSA review process set forth in this reference guide.”

Comment:  The original language took aim at MSA indemnification agreements where the new language is broader and includes any product that addresses future medicals. It also reiterates that the CMS MSA review process is voluntary. This was likely in response to people who said that CMS’s original policy changed the MSA review process from voluntary to mandatory.

 ‘May’ instead of ‘Will’ Deny

 CMS’s original policy said that it “will” deny payment of medical services up to the total settlement amount whereas the revised policy indicates CMS “may at its sole discretion” deny payment.

Comment:  It appears that CMS is giving itself wiggle room depending on the circumstances of an individual case.  Also, as is further explained below, CMS has given itself the option to accept less than the entire settlement amount as sufficient to protect its interests.

Total Settlement Definition

The original Section 4.3 defined total settlement as “total settlement less procurement costs.”  This was now revised to define total settlement “as defined in Section 10.5.3 of this reference guide, less procurement costs and paid conditional payments.”

Comment:  Section 10.5.3 is CMS’s longtime definition of “total settlement.” It makes sense that the definition of total settlement in the non-submit context should align. CMS also acknowledges that besides procurement costs, payment of conditional payments from the settlement amount should also be deducted from the amount of the settlement available to pay for future medical.

Post-MSA exhaustion review

When released in January, Section 4.3 provided no option for CMS to acknowledge the non-submit MSA as sufficient. The updated policy now says, “CMS will ignore the non-submit MSA and use the total settlement amount (minus procurement costs and paid conditional payments) as the amount available to pay future medicals “unless it is shown, at the time of exhaustion of the MSA funds, that both the initial funding of the MSA was sufficient, and utilization of MSA funds was appropriate.”

Comment:  It will be the Medicare beneficiary’s responsibility, or someone working on their behalf, to demonstrate that the MSA was sufficient at the time of settlement and that the MSA funds were spent appropriately.  We can assume that CMS will use the standards found in the WCMSA Reference Guide and its MSA Self-Administration Guide to make its determination. If CMS finds either that the MSA was insufficiently funded or inappropriately utilized, does the Medicare beneficiary have a right to an appeal? Medicare beneficiaries have a right to appeal a denial of payment for medical care. Presumably, that right extends to the context of a non-submit MSA, but it remains unclear how this would play out in practice, and CMS did not address it here.

Policy start date:  Per CMS, Section 4.3, “shall apply to all notifications of settlement that include the use of a non-CMS-approved product received on, or after, January 11, 2022; however, flags in the Common Working File for notifications received prior to that date will be set to ensure Medicare
does not make payment during the spend-down period.”

Comment:  Before the January date, there was no obligation to notify CMS of a settlement that includes the use of a non-CMS-approved MSA product (Yes, there is a Section 111 reporting responsibility, but that does not include notification of a non-submit MSA). Is there an obligation now? Nothing in Section 4.3 affirmatively states such an obligation exists and there is no statutory basis that provides for such notification.

Under threshold MSAs:  CMS says “CMS does not intend for this policy to affect any settlement that would not otherwise meet review thresholds. This comment does not relieve the settling parties of an obligation to consider Medicare’s interests as part of the settlement; however, CMS does not expect notification or submission where thresholds are not met.”

Comment:  Again, by saying it does not expect notification where thresholds are not met, CMS implies that they do expect notification when a non-submit MSA is used and thresholds are met. Why would CMS expect no notification on an under-threshold MSA? I suspect there are two reasons:

  • If a claimant is a Medicare beneficiary with a settlement of $25,000 or less, CMS expects that the MSA is a low-dollar amount and not worth the time it takes to coordinate its benefits.
  • If a claimant is not a Medicare beneficiary but has a reasonable expectation of Medicare eligibility within 30 months and the settlement is $250,000 or less, CMS cannot track the claimant as they are not yet a Medicare beneficiary.

Summary comments on Section 4.3 revisions

CMS should be credited for quickly addressing several of the questions and concerns that arose from the original Section 4.3 language. The revised section backs off the seeming implication that the mere use of a non-submit MSA represents a potential cost shift to Medicare. With that said, CMS reiterated that if the non-submit MSA exhausts, then it must be demonstrated that the MSA was sufficiently allocated at the time of settlement and the funds properly expended. As we do not know how this policy will play out in practice, the non-submit MSA route continues to present a notable risk to the claimant Medicare beneficiary.

Other CMS Updates to WCMSA Reference Guide

Beyond Section 4.3, CMS also made updates to other sections of the guide:

Section 9.4.1.1 Most Frequent Reasons for Development Requests

CMS added language to this section around documentation required for disputed cases, in other words, $0 MSAs for denied claims. CMS stated that medical records are required even when the parties are in dispute. Further, draft or final settlement agreements and court rulings are required documentation if they exist.

Comment:  CMS has required the above for quite some time.  This is just putting the requirements into the reference guide.

Section 16.1 Re-Review

CMS added the following to its re-review criteria:

 “Should no change be made upon response to a re-review request (i.e., no error was identified), additional requests to re-review the same error will not be entertained. “

Comment:  Tower has on occasion gone back and forth with CMS on arguments to remove a certain treatment or medication from the MSA. This new statement implies that once CMS makes its decision regarding a particular item it will not entertain other arguments.

If you have any questions, please contact Dan Anders, Chief Compliance Officer, at 888.331.4941 or daniel.anders@towermsa.com.

 

CMS Webinar Delves Further into Non-Submit MSA Matters

February 26, 2022

Man confused on a Non Submit MSA

The Centers for Medicare and Medicaid Services recently hosted a webinar on Workers’ Compensation Medicare Set-Asides (WCMSAs). While the webinar covered several topics around MSA submissions, CMS policy toward non-submit and evidence-based MSAs was an attendance-driver, according to its presenter, John Jenkins, Health Insurance Specialist for the CMS Division of Medicare Secondary Payer Operations.

As Tower’s recent articles CMS: Non-Submit MSAs Potentially Shift Costs to Medicare and CMS Letter Confirms Non-Submit MSA Denial is Real noted, the addition of Section 4.3 to the WCMSA Reference Guide has raised many questions and led some payers to reconsider whether non-submit MSAs are the best option for them.

Here is a webinar summary with Tower’s comments on Mr. Jenkins’ statements pertaining to non-submit MSAs along with a breakdown of some of the other matters discussed.

Non-Submit MSAs

Mr. Jenkins explained that the addition of Section 4.3 on non-submit and evidence-based MSAs was in response to industry requests for CMS’s position on such products.

He said that Section 4.3 is consistent with prior policy announcements which advise that Medicare has a right of recovery up to the settlement amount when the MSA is not CMS-approved and is prematurely exhausted.

  • Tower comment:  As we indicated in our prior article on Section 4.3, we believed this would be CMS’s position.

Mr. Jenkins could not clear up the question about MSAs that do not meet the CMS WCMSA review thresholds, i.e., Medicare beneficiary and total settlement higher than $25,000.  First, he said CMS treats these as if they never existed, thus the total settlement would be considered available to pay for future medical. However, later he said that if CMS obtains the non-submit MSA amount, that amount may be used to determine the “marker” in their system (This marker determines whether Medicare will pay for a certain treatment). Ultimately, he indicated further policy guidance will be issued around under-threshold MSAs.

  • Tower comment:  The common working file is CMS’s system to coordinate benefits to Medicare beneficiaries so that Medicare does not pay when a primary payer is available to pay. CMS places the marker for certain diagnoses to enable it to deny payment for treatment related to those diagnoses codes.  CMS needs to clarify how under-threshold MSAs will be treated. If parties have included a clinically and/or legally reasonable and defensible MSA in the settlement or have acceptable reasons for not including one, CMS should limit the liability for future medicals to the MSA amount. Perhaps CMS will have a post-settlement review process but its details are not clear at this time.

Mr. Jenkins went on to indicate that if CMS receives the non-submit documentation, settlement, and MSA amount, then it will use this information to place a marker in the common working file to deny medical care until such time as the settlement is exhausted.

According to Mr. Jenkins, CMS expects that Medicare should never see an injury-related bill if the non-submit MSA is priced correctly. If the MSA prematurely exhausts, the Medicare beneficiary will have to provide reasons for its exhaustion. Then it would be up to CMS to determine if the allocation and spending of the MSA were appropriate, using the same process used to approve MSAs.

  • Tower Comment:  Mr. Jenkins said that they see many instances of CMS-approved MSA funds exhausting and expects the same from non-submit MSAs. Even the best cost projections for future medical care are, in the end, still predictions. Future medical inflation alone will increase costs in addition to changes in treatment and medications. Thus, while a majority of non-submit MSAs will appropriately cover future medical care, some non-submit MSAs–just like some CMS-approved MSAs–will exhaust.

Mr. Jenkins referenced conducting some type of review if non-submit MSA exhausts, similar to the current pre-settlement WCMSA review process. Naturally, this raises more questions.  First, who is completing the review? The current CMS WCMSA review contractor, CMS itself, or some other contractor? What criteria will be used as part of the review? What documentation must be submitted to support the MSA allocation as sufficient and the fund spending as appropriate? To verify adequate funding, the same documentation used at settlement (medical treatment records, prescription histories, and rated ages) would likely be required. We assume appropriate spending of the funds would be determined using healthcare bills and payment receipts.

Mr. Jenkins advised that if a structured MSA’s funds exhaust in any given year, CMS will not temporarily step in to pay for injury-related care as it does with a CMS-approved MSA.

  • Tower Comment:  This leaves anyone with a non-submit MSA annuity in a difficult position. They would need to use their personal funds to pay for medical until next annuity payment is received when they could theoretically reimburse themselves. Even if they can reimburse their medical bills from the annuity payment, CMS is not likely to agree that reimbursing interest payments that occurred from putting medical bills on a credit card is an appropriate use of these funds.

Mr. Jenkins was clear in stating that the MSA, whether CMS-approved or not, is an agreement solely between CMS and the Medicare beneficiary.

  • Tower Comment:  This indicates that CMS will not take any action against the employer or insurance carrier as they are not seen as a party to the agreement. That said, there remain repercussions to the payer. A Medicare beneficiary claimant may be reluctant to agree to a settlement with a non-submit MSA. Additionally, the workers’ compensation board, commission or other governing authority may be less likely to approve such a settlement.

Mr. Jenkins stated that a large number of CMS-approved MSAs exhaust early and that non-submit MSAs are even more likely to exhaust early.

  • Tower Comment:  The allegation that a large number of CMS-approved MSAs exhaust early is, thus far, unsupported by data from CMS.

As to whether Section 4.3 of the reference guide applies retrospectively or just prospectively, Mr. Jenkins said that while what was stated in this section has always been CMS policy, anything after 1/11/22 must meet this requirement.

  • Tower Comment:  We believe this statement is still unclear. Does this mean that CMS will only apply this policy to settlements that occur after 1/11/22 or does it apply to settlements that took place before 1/11/22 when MSA funds continued to be used after that date?

Finally, Mr. Jenkins advised that Section 111 reporting and WCMSAs are not connected. Therefore, the agency does not use the Section 111 Total Payment Obligation to the Claimant (TPOC) data to place a marker in the common working file.

  • Tower Comment:  While this has been our understanding, CMS’s statement that it does not use Section 111 reporting data to stop Medicare payment for post-settlement medical is significant. It means that unless the settling parties proactively advise CMS of a non-approved MSA, CMS will continue to pay for injury-related care because it is unaware that an MSA was funded.

While the webinar answered some questions around CMS’s approach to non-submit MSAs, many remain. We believe CMS needs to significantly increase its guidance to Medicare beneficiaries surrounding their rights, responsibilities, and the risks they face when settling a claim with a non-submit MSA. At a minimum, CMS may not automatically acknowledge the non-submit MSA amount as the extent of liability for future medical. Consequently, the Medicare beneficiary may be placed in a position to defend the MSA amount and their spend from that amount at some point years in the future.

Other MSA Matters

  • Submission of settlement documents:  CMS continues to identify cases where settlement occurred, and the settlement documents were not forwarded to CMS. These documents must be submitted to make the MSA effective in CMS’s system.
  • Electronic attestation:   Mr. Jenkins indicated that MSA administrators are not submitting yearly and final attestations electronically even though this option is available. He encouraged its use.
  • State statutes:  Advised that parties who wish to limit the MSA per the Georgia 400-week cap need to provide an order from the Georgia Workers’ Compensation Board confirming the claim as non-catastrophic. Also, if a California Independent Medical Review (IMR) confirms the denial of certain care, CMS will not exclude the denied care from the MSA without an “Alternative Treatment Plan” from the treating physician.
  • Pricing of Prescription Drugs:  Addressed a question about whether CMS would consider another pricing mechanism for prescription drugs other than Red Book by saying that CMS is always open to a discussion on alternatives.
  • Lack of updated medical treatment:  In situations where the claimant has not been treated in several years CMS will not assume that this is sufficient evidence to demonstrate that no further care is necessary. Instead, CMS will consider the worst-case scenario and assume that the claimant will return for care.
  • Comorbidities that prevent surgery:  If a comorbidity, such as cardiac or respiratory problems, prevents a surgery from proceeding, CMS will assume that the person will improve and thus allocate the surgery in the MSA.
  • Release from care statements:  If a treating physician releases a claimant from care this does not automatically create a presumption of no future care. CMS assumes that if a specialist releases the claimant from care that there may be follow-up with a primary care physician for ongoing maintenance unless otherwise indicated.
  • MSA Amended Reviews:  Advised that parties who have a previously approved MSA that falls outside of the 72-month window for submitting an Amended Review can still fund that older approved MSA as it will be the only one on record with CMS.

If you have any questions, please contact Dan Anders, Chief Compliance Officer, at 888.331.4941 or daniel.anders@towermsa.com.

 

CMS Letter Confirms that Denial for Non-Submit MSAs is Real

February 11, 2022

Man confused about Medicare Set Aside (MSA) and cms denial

CMS to Hold WCMSA Webinar on February 17

The Centers for Medicare and Medicaid Services updated its Workers’ Compensation Medicare Set Aside (WCMSA) Reference Guide on 1/10/22 adding a section that addresses non-submit MSAs or evidence-based MSAs. The new section makes it clear that CMS will treat the use of such MSAs as a potential attempt to shift the financial burden of future medical care to Medicare.

Since the update, questions have swirled around whether CMS will follow through and deny payment for Medicare beneficiaries with non-submit MSAs.

Now we know CMS does and will.

Tower obtained a recent letter sent to a Medicare beneficiary claimant in which CMS advised that while a certain amount for future medical was agreed to in settlement between the claimant and the employer/insurer, as the claimant chose to forgo the CMS WCMSA review process, Medicare will not pay until the entire settlement minus procurement costs is exhausted.  In other words, the non-submit MSA is not recognized as the limit of settlement funds available to pay for future medical.

The letter states:

Section 1862(b)(2)(A) of the Social Security Act prohibits the Medicare program from making payment where payment was made or may reasonably be expected to be made by another party. 42 C.F.R. 411.46 specifically allows Medicare to deny payment for treatment of work-related conditions if a settlement does not “adequately protect Medicare’s interest”-that is, does not include enough money to pay for treatment of those conditions. Because you did not seek prior review and approval by CMS of the amount set aside in your settlement for your future medical care, Medicare will not pay for the treatment of your work-related condition until you have demonstrated the appropriate exhaustion of your “net” settlement proceeds. Please review the enclosed package for information about the submission of annual attestations. Once you have shown that the settlement proceeds (total settlement amount minus procurement costs such as attorney fees, and minus funds repaid to Medicare for care prior to the date of settlement) have been exhausted, Medicare will make payment again. If you have questions about this letter, please call RO-09 CUSTOMER SERVICE at (415) 744-3658.

Also notable is that CMS issued the letter on 1/13/2022, a few days after the WCMSA Reference Guide update on 1/10/2022.  In addition, the letter references a settlement date of 11/17/2021, one that occurred before the update. This confirms CMS is reviewing non-submit MSAs retrospectively.

The letter shows that CMS does not recognize the amount set aside for future medicals when it has not reviewed and approved the MSA. Instead, the Medicare beneficiary claimant must exhaust the amount in their entire settlement minus procurement costs before Medicare will cover future medicals. The following scenario illustrates this:

Parties settle a workers’ compensation case for $50,000 inclusive of $10,000 for a non-submit or evidence-based MSA.  Procurement costs (attorney’s fees and expenses) are $12,000 of the settlement.  Post-settlement the claimant Medicare beneficiary (whether self or professionally administering the MSA) uses the $10,000 to pay for injury-related treatment and medications. However, treatment is still needed.

At this point, Medicare’s position is that the entire settlement amount minus procurement costs, $50,000 – $12,000 = $38,000 is available to pay for such care.  It would need to be documented to CMS that not just $10,000, but $38,000 was paid for injury-related care before Medicare steps in to pay.

There is no problem with Medicare unless the $10,000 runs out and injury-related care is still needed.

As Tower discussed in our prior article, CMS; Non-Submit MSAs Potentially Shift Costs to Medicare, and in our recent webinar, many questions remain.  Some may be answered in CMS’s upcoming webinar on Thursday, February 17, at 1 p.m. ET.

Here is the announcement:

CMS will be hosting a webinar to discuss a variety of WCMSA topics, including a summary of what’s new in Medicare set-asides, and addressing questions related to the inclusion of treatments, application of state rules, re-reviews/amended reviews and more. The webinar format will be opening remarks and a presentation by CMS followed by a live question and answer session with representatives from CMS.

Note, there is no pre-registration, instead just follow the provided link shortly before the webinar start time.

Additionally, Tower is working with our industry colleagues at the National MSP Network (MSPN) to directly address questions around the policy and seek needed clarifications, especially around retrospective applicability, Medicare beneficiary claimant appeal rights, and settlements that do not meet CMS WCMSA review thresholds.

The bottom line is CMS has begun 2022 with a significant effort to assert what it believes is its right to claim the entire settlement amount, minus procurement costs, as available to pay for future injury-related medical when the settlement does not include a CMS-approved MSA. Parties to settlements where the CMS WCMSA review thresholds are met and the MSA is not submitted should be wary of the risks and the potential extent of liability for payment of future medical before Medicare will pay for injury-related care.

Since its founding a decade ago, Tower has recommended MSA submission when CMS review thresholds are met. Consequently, we have extensive experience in the CMS submission process and can identify and address MSA cost drivers and facilitate quick CMS MSA approval.  We would be pleased to discuss a seamless transition from a non-submit to submit MSA program which properly addresses future medical costs while also confirming CMS compliance.

If you have any questions, please contact Dan Anders, Chief Compliance Officer, at 888.331.4941 or daniel.anders@towermsa.com.

CMS: Non-Submit MSAs Potentially Shift Costs to Medicare

January 13, 2022

Scale heavy with money showing the costs of Non -Submit Medicare Set-asides

The Centers for Medicare and Medicaid Services’ updated Workers’ Compensation Medicare Set-Aside Reference Guide (Version 3.5) has a new section on the use of “Non-CMS Approved Products to Address Future Medical” that says CMS views non-submit/evidence-based MSAs “as a potential attempt to shift financial burden” to Medicare.  Below is the new section followed by key takeaways and Tower answers to questions stemming from the new policy.

4.3 The Use of Non-CMS-Approved Products to Address Future Medical Care

 A number of industry products exist with the intent of indemnifying insurance carriers and CMS beneficiaries against future recovery for conditional payments made by CMS for settled injuries. Although not inclusive of all products covered under this section, these products are most commonly termed “evidence-based” or “non-submit.” 42 C.F.R. 411.46 specifically allows CMS to deny payment for treatment of work-related conditions if a settlement does not adequately protect the Medicare program’s interest. Unless a proposed amount is submitted, reviewed, and approved using the process described in this reference guide prior to settlement, CMS cannot be certain that the Medicare program’s interests are adequately protected. As such, CMS treats the use of non-CMS-approved products as a potential attempt to shift financial burden by improperly giving reasonable recognition to both medical expenses and income replacement.  

As a matter of policy and practice, CMS will deny payment for medical services related to the WC injuries or illness requiring attestation of appropriate exhaustion equal to the total settlement less procurement costs before CMS will resume primary payment obligation for settled injuries or illnesses. This will result in the claimant needing to demonstrate complete exhaustion of the net settlement amount, rather than a CMS-approved WCMSA amount.

Key Takeaways

  1. CMS specifically speaks to evidence-based / non-submit MSAs for the first time in the reference guide.
  2. CMS will treat the use of non-CMS approved products as a potential attempt to shift the financial burden to Medicare, calling this process “improper”
  3. As a matter of “policy and practice,” CMS will deny payment for medical services related to WC injuries until total settlement has been exhausted. 
  4. CMS does not limit this to future MSAs only…this could impact existing non-submit MSAs.

Questions and Answers

Does this represent a change in CMS policy toward non-approved MSAs?

No. As mentioned in other sections of the reference guide, CMS has consistently stated that when an MSA is not approved, Medicare may deny related medical claims or pursue recovery for related medical claims that Medicare paid up to the full amount of the settlement.

What CMS does do in this version of the reference guide is to directly address evidence-based and non-submit MSAs along with MSA vendor indemnifications that sometimes accompany such MSAs.  It presumes non-CMS-approved products may represent a cost-shift to Medicare.

This presumption then leads to their next statement in which they indicate the claimant will need to demonstrate complete exhaustion of the net settlement amount before CMS will pay primary for injury-related medical care.  Consequently, this could mean that even with an MSA, the claimant would need to access their settlement funds to pay for future injury-related medical care.

Is Section 4.3 applicable to all MSAs ever done or prospective MSAs?

There is no indication that this policy only applies to future MSAs and settlements.  Consequently, unless CMS says otherwise payers should assume that CMS takes this position for any settlement whether past or future.

If a non-submit MSA was used to settle a case does the beneficiary have cause for concern?

Keep in mind that CMS involvement is only triggered when Medicare is requested to pay for injury-related medical care.  If the MSA amount sufficiently pays for such care, then the beneficiary does not have to worry. However, if the MSA amount is exhausted, then CMS has made it clear that it will deny payment.

What happens if the claimant wants to dispute the denial?

The claimant Medicare beneficiary has a statutory right to appeal Medicare’s denial.  Presumably, the beneficiary or someone on their behalf will need to submit an appeal.  The appeal would assert that the non-submit or evidence-based MSA was reasonable at the time of settlement.  The outcome of this is uncertain as to date CMS has not routinely denied medical care in settlements involving non-submit and evidence-based MSAs.

If a non-submit MSA was utilized to settle a case does the payer have cause for concern?

If the payer provided some type of indemnification or guarantee or is otherwise open to liability for a failure to properly fund future medical, those provisions may be tested.

What about non-submit MSAs that could not be submitted because the CMS MSA review threshold was not met?

If CMS was to deny payment in these cases the Medicare beneficiary could rebut the denial based on the reasonableness of the MSA at the time of settlement and on the basis that there was no CMS WCMSA review process available to ascertain whether the amount appropriately addressed Medicare’s interests.

How does this affect my MSA program?

If you have a program that largely obtains CMS MSA approval when review thresholds are met, then Section 4.3 is not relevant except for MSAs that were under threshold. (However, I believe Section 4.3 targets settlements that meet CMS MSA review thresholds.)

On the other hand, if you have maintained a program that largely does not submit MSAs to CMS for approval, then the risk of MSA exhaustion and denial of injury-related medical is real.

Tower recommends taking a critical look at whether non-submit/evidence-based MSAs remain the best policy for you and the injured worker.  Once plaintiff attorneys review this policy, they may not consider a non-CMS-approved MSA sufficient to protect their client’s access to Medicare for injury-related care in the future.

Cost-Effective CMS-Approved MSAs are Possible

The non-submit MSA route has usually been taken based on an assumption that all CMS-approved MSAs contain unrealistic allocations.  While there are some of those, Tower has found that MSA costs can be contained so that a CMS-approved MSA can pave the way to settlement.  We do this through a clear understanding of CMS’s MSA pricing methodology and knowing exactly what will lead to MSA increases or development letters that delay CMS MSA approval.  Tower proactively obtains records and physician statements or works with our clients to do this so cases can be settled without concern that CMS may deny payment for future injury-related medical care.

Please contact Chief Compliance Officer, Dan Anders, with any questions about this or any other MSP compliance issue at Daniel.anders@towermsa.com or 888.331.4941.

Related Articles

Tower’s Dan Anders Says “It’s Still OK to Submit and MSA”

 

 

CMS Releases Updated Section 111 NGHP User Guide

December 28, 2021

book marked by sticky notes illustrating changes Section 111 reporting on ORM

The Centers for Medicare and Medicaid Services (CMS) has released Version 6.6 of its Section 111 NGHP User Guide.  Below is a summary of the notable updates and practical implications.

Funding Delayed Beyond TPOC Start Date Field

Last month we discussed an 11/03/2021 Alert from CMS on the use of Field 82 Funding Delayed Beyond TPOC Start Date.  Field 82, per the Section 111 User Guide, is to be used in specific circumstances where the amount the claimant Medicare beneficiary is to be paid is not known at the time the settlement occurs.  Per CMS, this happens most often in mass tort settlements.

As we previously related, the CMS Alert is confusing when it refers to the date settlement funds are “dispersed.”  CMS seems to assume that the date inserted into Field 82 is not only the date that the settlement amount is determined but is the same date the funds are dispersed. However, these dates may be weeks or months apart.  Our recommendation was to place the date settlement funds are dispersed in Field 82.

In its update to the User Guide, CMS now acknowledges this as the correct use of Field 82.  Specifically, CMS states (Chapter III: Policy Guidance):

6.5.1.2 Timeliness of Reporting

NGHP TPOC settlements, judgments, awards, or other payments are reportable once the following criteria are met:

  • The alleged injured/harmed individual to or on whose behalf payment will be made has been
    identified.
  • The TPOC amount (the amount of the settlement, judgement, award, or other payment) for
    that individual has been determined.
  • The RRE knows when the TPOC will be funded or disbursed to the individual or their
    representative(s)

RREs should retain documentation establishing when these criteria were or will be met. RREs

should not report the TPOC until the RRE establishes when the TPOC will be funded or

disbursed. In some situations, funding or disbursement of the TPOC may not occur until well

after the TPOC Date. RREs may submit the date the TPOC will be funded or disbursed in the

corresponding Funding Delayed Beyond TPOC Start Date field when they report the TPOC Date

and TPOC Amount, but must do so if the TPOC Date and date of the funding of the TPOC are

30 days or more apart.

Timeliness of MMSEA Section 111 reporting for a particular Medicare beneficiary will be based

upon the latter of the TPOC Date and the Funding Delayed Beyond TPOC Start Date.

Example:

There is a settlement involving an allegedly defective drug where a large settlement is to be

disbursed among many claimants.

The settlement provides a process for subsequently determining who will be paid and how much.

Consequently, there will be payment to or on behalf of a particular individual, but the specific amount of the settlement, judgment, award, or other payment to or on behalf of that individual is not known as of the TPOC Date. RREs are to submit the date of the settlement in the TPOC Date field and the amount of the settlement in the TPOC Amount field.

In this example, the determination of the TPOC Amount, as well as the funding or disbursement of the TPOC, will be delayed after the TPOC Date. Once the TPOC Amount and the date when the TPOC will be funded or disbursed are determined, the RRE should submit the record with the appropriate date in the corresponding Funding Delayed Beyond TPOC Start Date field.

Practical Implications

What CMS is getting at here is they want to know when the claimant receives the settlement funds so they can correctly time their recovery efforts.  For Responsible Reporting Entities (RREs) this means if payment will be delayed more than 30 days post the TPOC date, then they must hold off on Section 111 reporting until the date the settlement funds will be disbursed has been identified.

We note that while CMS expects the above rule to apply to mass tort settlements, there are certainly cases, both liability and workers’ compensation, where funding may be delayed more than 30 days beyond the TPOC date.   Thus, we believe the effect of this update on the “Timeliness of Reporting” rule will likely be much wider.

In terms of making this simpler for those entering the TPOC information, if the disbursement of settlement funds commonly occurs more than 30 days post-TPOC date, it may be easiest to always enter a date in the corresponding Funding Delayed Beyond TPOC Start Date field along with the TPOC Date and TPOC Amount, whether less than or more than 30 days from the TPOC date.

Updates to No-Fault Policy Limit

Also last month we discussed another CMS Alert reminding RREs where, depending upon state law or the terms of a given policy, the no-fault policy limit may vary.  The Alert reminded RREs to update to the new policy limit as quickly as possible, including the use of an “off-cycle” report (A report made in addition to the required quarterly reporting).  In our analysis of this Alert, we expressed concern as to whether such “off-cycle” reporting is mandatory or recommended.  In other words, if mandatory and not done, that it would be considered non-compliance and potentially subject the RRE to penalties.

The updated User Guide CMS states as follows (Chapter III: Policy Guidance, Section 6.5.1.3):

Note: In some states, depending on various factors associated with the incident being reported, no-fault policy limits may vary. The reported Policy Limit should reflect the amount the RRE has accepted responsibility for at the time the record is submitted or updated. Just as importantly, if the Section 111 record needs to be corrected to reflect a new Policy Limit, the RRE should update the record as soon as possible.

Practical Implications

While CMS states the RRE should update the record as soon as possible, there is no reference to “off-cycle” reporting.  We assume that while “off-cycle” reporting is preferred, that proper compliance will be determined based upon the quarterly report which includes the updated no-fault policy limit.

$750 Threshold Maintained for Section 111 Reporting and Medicare Conditional Payment Recovery

In a December 15, 2021, Alert CMS announced the 2022 recovery threshold for liability, no-fault and workers’ compensation settlements will remain at $750. Accordingly, Total Payment Obligations to the Claimant, TPOCs, in the amount of $750 or less are not required to be reported to CMS through the Section 111 Mandatory Reporting process, nor will CMS attempt to recover conditional payments for TPOCs of this amount (The threshold does not apply to liability settlements for alleged ingestion, implantation or exposure cases).

Practical Implications

As CMS is keeping the $750 threshold for mandatory reporting and conditional payment recovery there are no changes to the reporting processes or determinations as to when conditional payments should be investigated or resolved.

If you have any questions regarding these updates, please contact Dan Anders at daniel.anders@towermsa.com or 888.331.4941.

 

 

 

 

 

CMS Alerts Remind RREs to Accurately Report Section 111 Data

November 22, 2021

Clipboard noting New Section 111 Reporting with Red exclamation sign

Over the past month the Centers for Medicare and Medicaid Services issued two alerts reminding Responsible Reporting Entities (RREs) to make sure data reported through the Section 111 Mandatory Insurer Reporting process is accurate and updated. This appears to be part of an ongoing effort by CMS to avoid unnecessary Medicare conditional payment recovery efforts.

In the first alert, entitled “Reporting of Incorrect No-Fault Policy Limits” CMS states:

Responsible Reporting Entities (RREs) are accountable for ensuring the information included in their Section 111 MMSEA Mandatory Insurer Reporting submissions is accurate. There may be situations where, depending upon state law or the terms of a given policy, the policy limit may vary. In these situations, the reported Policy Limit should reflect the actual amount the RRE has accepted responsibility for at the time the record is submitted or updated. Just as important, if the Section 111 record needs to be corrected to reflect a different Policy Limit, the RRE should update the record as quickly as possible to reflect the new policy limit. For example, if a policy allows for a minimum amount of MedPay coverage and will only allow a higher amount under certain circumstances, and those circumstances are not yet met at the time of reporting, the RRE should report the lower amount. Should the criteria that triggers the higher policy limit be met after that report, the RRE should update the record as soon as possible. Reporting of an incorrect Policy Limit or failing to timely update the record can put the RRE at risk of non-compliance with the Section 111 reporting requirements.

 Inaccurate and/or uncorrected information can impact current Medicare claims payment actions. Inaccurate and/or uncorrected information also places the RRE at risk of recovery actions and increases the burden of proof upon the RRE should it attempt to dispute recovery efforts. Therefore, we advise the RRE to consider contacting their EDI Representative to submit an off-cycle Section 111 report with new policy limit information, rather than wait for their next Section 111 reporting cycle.

Practical Implications

By recommending an “off-cycle” reporting of the new policy limit, CMS is trying to avoid paying medical expenses when a primary payer, in this case, the no-fault carrier, is available to pay. (CMS has a similar recommendation in the Section 111 User Guide for an immediate report of ORM termination to the EDI representative.) If the no-fault plan can pay medical costs directly to the provider, it streamlines the system and eliminates the conditional payment recovery process.

This portion of the alert’s language raises some concern, though: “failing to timely update the record can put the RRE at risk of non-compliance with the Section 111 reporting requirements.”  While CMS has yet to issue final regulations regarding civil monetary penalties for non-compliance with Section 111 reporting requirements, in its proposal, timeliness and accuracy of reporting are factors in determining whether penalties will be imposed.

CMS could clarify this alert by stating that “failing to update the record by the quarterly reporting period following the policy change puts the RRE at risk of non-compliance.” Making failure to report “off-cycle” a basis for penalties adds confusion to a system based on quarterly reporting.  Tower will seek clarification from CMS on this point.

The second alert from CMS, “Use the Funding Delayed Beyond TPOC Start Date Field,” states:

This is a reminder that if funding is delayed after the settlement date reported in Field 80: TPOC Date, in the Claim Input File Detail Record, RREs should provide the actual or estimated date of the funding determination in Field 82: Funding Delayed Beyond TPOC Start Date.

Some RREs are failing to indicate a Funding Delayed Beyond TPOC Start Date when funds have not yet been released. This has resulted in CMS recovery demands being sent based upon the receipt of a TPOC date and TPOC amount before the funds for the settlement have been received by the beneficiary.

 As soon as CMS receives a report of a TPOC Date and corresponding TPOC Amount, CMS begins its recovery process to collect Medicare claims conditionally paid that are covered by the TPOC. The Funding Delayed Beyond TPOC Start Date is used to delay the recovery process so as not to negatively impact the beneficiary prior to receipt of the settlement proceeds.

In addition, the Funding Delayed Beyond TPOC Start Date is used to ensure an RRE is not found noncompliant with the Section 111 timeliness reporting requirements when a settlement has been made, but the final payment amount has not yet been determined or dispersed.

Practical Implications

What is not explained here is that Field 82, per the Section 111 User Guide, is to be used in specific circumstances where the amount the claimant Medicare beneficiary is to be paid is not known at the time the settlement occurs.  This happens most often in mass tort settlements.  Here is an example from the user guide:

  • There is a settlement involving an allegedly defective drug.
  • The settlement contains or provides a process for subsequently determining who will be paid and how much. Consequently, there will be payment to or on behalf of a particular individual and/or the amount of the settlement, judgment, award, or other payment to or on behalf of that individual is not known as of the TPOC Date.
  • Timeliness of MMSEA Section 111 reporting for a particular Medicare beneficiary will be based upon the date there is a determination both that payment will be made to or on behalf of that beneficiary and a determination of the amount of the settlement, judgment, award, or other payment to or on behalf of that beneficiary.
  • RREs shall submit the date of the settlement in the TPOC Date field and the date when there is a determination both that payment will be made to or on behalf of that beneficiary and a determination of the amount of the settlement, judgment, award, or other payment to or on behalf of that beneficiary in the corresponding Funding Delayed Beyond TPOC Start Date Field.

While it’s important to remind people to use Field 82 when applicable, the alert causes confusion when it refers to the date settlement funds are “dispersed.”  CMS seems to assume that the date inserted into Field 82 is not only the date that the settlement amount is determined but is the same date the funds are dispersed. However, these dates may be weeks or months apart.

We will seek clarification from CMS but based on CMS’s representation that this is the date it uses to initiate conditional payment recovery against the Medicare beneficiary claimant, we recommend placing the date settlement funds are dispersed in Field 82.

Recognizing that both alerts are somewhat technical, and questions are understandable, feel free to contact me at Daniel.anders@towermsa.com or 888.331.4941.

The PAID Act: Implementation and Implications for Claims Handling

October 15, 2021

Chalk board depicting what the PAID Act covers

Thanks to the Provide Accurate Information Directly (PAID) Act effective December 11, 2021, payers will have access to Medicare beneficiary enrollment status in Medicare Part C (Medicare Advantage [MA]) plans or Part D (prescription drug) plans. Enrollment information will be provided through the Section 111 query response file for the past three years.

Historically, workers’ compensation, liability, and no-fault insurance plans have had a difficult time trying to determine a Medicare beneficiary’s enrollment status in such plans as the current query response file only provides a yes or now as to whether the individual is enrolled in Medicare.  However, as close to 40% of Medicare beneficiaries are enrolled in a Part C plan and over 70% are enrolled in a Part D plan, the potential for these plans to seek reimbursement from both payer and/or claimant is significant.

Currently, payers must ask the claimant to voluntarily provide Part C and D plan information which sometimes is never provided or is provided, but incomplete or inaccurate.  Notably, Medicare beneficiaries can change plans every year, meaning in some cases many plans may have reimbursement rights over the course of a claim.

Of course, Medicare already shares Section 111 reporting data with the Part C and D plans, thus giving them the ability to seek reimbursement against a payer who may have no idea the claimant is enrolled in such a plan until they receive a demand for payment.

Great, But Now What? 

Tower’s September 15 “How-to Guide for PAID Act Implementation” webinar explained how the PAID Act affects payers, the differences in recovery processes, and the new reports Tower is creating to make life easier for its clients. If you missed the webinar, contact me at Daniel.Anders@towermsa.com to request the link because there’s a lot of information.

The Section 111 query response data received from the Benefits Coordination & Recovery Center (BCRC) is changing in a big way.  There are 244 new data fields. Parts A, B, C, and D will have the most recent effective dates and termination dates. Part C and D will have most recent and previous plan(s) data, up to three years of data. This will include not only the plan name, but also contract number, enrollment date, termination date, benefit package number and plan address.

Payers can receive and store this data themselves or, for Tower reporting clients, we will store it for our clients who can then obtain the data via Tower’s Section 111 portal.  In other words, it is the payer’s choice whether to receive this information.

Tower will also create PAID Act-specific reports around the new data, accessible through our S111 Management dashboard. These will be:

  • Most Recent Medicare Effective and Termination Parts A, B, C, and D
  • All Part C data
  • All Part D data

Now, the Centers for Medicare and Medicaid Services will only provide the past three years of data, but Tower will store data beyond three years for use by our clients on claims which remain outstanding past that timeframe.

Handling Recovery

Based on the MSP statute and regulations and court decisions the Part C and D plans have a right of recovery against the primary plan and all those who receive payment from that primary plan, such as the claimant and the claimant’s attorney.  In some cases, a claim for reimbursement will be issued by the Part C or D plan without initiating an inquiry. Payers should use the contact information from the Section 111 data to initiate a query with the plan(s) to determine whether they have a reimbursement claim.

There are several differences among CMS recovery through Part A and B (Original Medicare) and Parts C and D recovery.

  • Part C and D plans cannot access the Medicare Secondary Payer Recovery Portal (MSPRP)
  • Debt collection is not split into two recovery contractors (Commercial Repayment Center (CRC) and BCRC), however, these plans might contract out their recovery efforts.
  • The C and D plans also cannot refer debts to the U.S. Treasury Department; they must file suit instead.
  • In our experience, Part D and C plans have significantly less unrelated charges on their claims for reimbursement compared to CRC and BCRC.
  • Appeal rights are only held by the claimant unlike with Original Medicare conditional payment demands where an appeal right is also held by the payer.

Considering the above, on balance, while identifying the plan and obtaining the reimbursement claim may be a bit more difficult, Part C and D claims for reimbursement tend to be easier to resolve compared to demands from CMS’s recovery contractors.

Guidance for Addressing Part C and D Reimbursement

The following is recommended to properly resolve Part C and D reimbursement claims at time of settlement:

  • Identify if the claimant is a Medicare beneficiary and enrolled in a Part C or D Plan
  • Identify If the claimant was ever enrolled in traditional Medicare; if so investigate conditional payments with CRC and BCRC
  • Investigate with Part C or D plan whether it is seeking reimbursement and obtain a letter itemizing reimbursement claims.
  • Negotiate with Part C or D plan to remove charges unrelated to work injury or where there is a reasonable basis to dispute. These plans largely use the same dispute and appeal criteria as CRC/BCRC
  • Contact plan at time of settlement to confirm final amount owed
  • Resolve case with clear understanding of how plan will be reimbursed

Keep in mind that the PAID Act in no way changes Part C and D reimbursement rights nor puts any additional obligations on these plans that did not already exist prior to its passage.  Nonetheless, access to plan information by payers will undoubtedly lead to a greater emphasis on contact with the plan prior to settlement.  Payers should make use of this data to query the plan and identify and resolve reimbursement claims at the time of settlement.

Whether you’re ready to implement the PAID Act or not, Tower is.  In fact, we’re in front of it, building out our systems, creating reports to add to our year-old S111 Management Dashboard. We’ve been watching pending legislation and posting on it all along, thinking about how it could affect you and planning for the future.

As always, if you have questions about the PAID Act or anything else MSP or MSA related, please contact me at Daniel.Anders@towermsa.com or 847-946-2880.

There’s no better time to let Tower manage your Section 111 reporting. Contact Hany Abdelsayed for the details.   Hany Abdelsayed, hany.abdelsayed@towermsa.com, (916) 878-8062.

Attend the Virtual MSPN Annual Conference!

August 23, 2021

MSPN Annual Conference details and registration information

The National Medicare Secondary Payer Network (MSPN) will hold its virtual MSPN Annual Conference on September 29 and 30.  With the theme of the Roaring ‘20s, the conference celebrates surviving, revamping, and emerging stronger.

MSPN is the only national MSP organization with an influential membership base of claims adjusters, insurance carriers, life care planners, Medicare Set-Aside allocators, nurses, and other medical professionals. Attorneys, professional administrators, self-insured employers, settlement planners, social workers, structured settlement brokers, and third-party administrators are other prominent members. If you’re one of those, work for a self-insured employer, or are reading this post, you should attend.

Open to non-members, the MSPN Annual Conference is designed for insurance, healthcare, financial services, and litigation professionals whose business touch MSP compliance directly or tangentially.  The conference applies for continuing education for multiple licenses and certifications in insurance, case management, legal, disability, nursing and other medical, and disability management fields.

Presented by national leaders in MSP compliance, representatives of CMS and its contractors, the annual meeting examines various aspects of Medicare Secondary Payment.  Sessions dive into Medicare Set-Asides, the recent PAID Act, MSP compliance in Liability, legislative updates, the coming Civil Monetary Penalties for incomplete or inaccurate Section 111 reporting, post-settlement overview, and other timely topics.

CMS Directors and executives from its contractors explain its conditional payment recovery reimbursement and appeals processes in separate presentations. These give you a chance to hear from the folks who make the MSP decisions that determine our compliance.

Plus, Tower’s Chief Compliance Officer and MSPN President Dan Anders (that’s me) will host a lively Fire Side chat with Jackie Cipa, Deputy Director, CMS Division of MSP Program Operations and Steve Forry, CMS Division Director for MSP Program Operations. They will share meaningful takeaways from this year’s annual meeting and highlight emergent issues in the MSP universe.

You can find plenty of information on MSPN’s website about the conference along with early registration fee discounts (Available before Sept. 1).  Remember, the conference is virtual, September 29 and 30 (As the conference is virtual, all sessions will be recorded and may be viewed post the set conference days).  Don’t delay! Register today!

If you have questions about the MSPN or its annual meeting, do not hesitate to contact me at Daniel.anders@towermsa.com or (888) 331-4941.