CMS Section 111 Reference Guide Update Clarifies Date of Incident Reporting

July 15, 2024

CMS Section 111 Reference Guide Update Clarifies Date of Incident Reporting

New DOI Reporting Rules for Cumulative Injuries in Section 111 NGHP Guide

The new update of the Section 111 NGHP User Guide, Version 7.6, clarifies how to report the Date of Incident (DOI) in a Cumulative Injury.  The Centers for Medicare and Medicaid Services added the following to Chapter III Policy Guidance, Chapter 2: Introduction and Important Terms:

Note: Cumulative injury refers to those categories of injuries that may persist or grow in severity, intensity, or pain but for which a formal diagnosis may not occur until a later date. Examples of cumulative injuries include, but are not limited to, carpal tunnel syndrome, or back pain that is not the result of an acute trauma. Exposure, ingestion, and inhalation injuries are not considered cumulative injuries for purposes of calculating DOI or any other reporting requirements.

Differentiating DOI Reporting for Cumulative Trauma vs. Exposure, Ingestion, or Inhalation Claims

We assume CMS added this note to ensure that RREs do not use the definition for DOI in cumulative trauma claims when they report an exposure, ingestion or inhalation claim, as there is indeed a difference.

Cumulative Trauma Claim DOI is defined as: The earlier of the date that treatment for any manifestation of the cumulative injury began, when such treatment preceded formal diagnosis, or the first date that formal diagnosis was made by a medical practitioner (for claims involving cumulative injury).

The guide defines the exposure, ingestion or implant DOI as:

  • The date of first exposure (for claims involving exposure, including; occupational disease)
  • The date of first ingestion (for claims involving ingestion)
  • The date of the implant or date of first implant, if there are multiple implants (for claims involving implant(s)

The NHGP update to Chapter IV Technical Information, Section 6.3.3 also included this addition regarding TIN/TN errors:

If your address fails validation with USPS, you must visit your local USPS office to correct this issue. Please make the correction immediately, as TN errors delay MSP records posting.

Per Section 6.6.5 of the guide:

RRE Address Validation

• RREs are encouraged to pre-validate insurer and recovery agent addresses using postal verification software or online tools available on the USPS website pages such as https://tools.usps.com/go/ZipLookupAction_input. RREs should try to use standard abbreviations and attempt to limit data submitted in these fields and adhere to USPS standards. The address validation enhancements in place will “scrub” addresses submitted on the TIN Reference File using USPS standards, and we recommend that RREs also attempt to meet these standards, to improve results. Although NGHP DDE reporters do not submit TIN Reference Files, they do submit the same TIN information online. It is recommended that DDE reporters also pre-validate RRE addresses.

CMS stressed:

Please address errors immediately, as TIN errors delay MSP record posting.

In short, make sure your TIN Reference File has a USPS-accepted address. If you are a Tower Section 111 reporting client, we will advise you if the file contains an error and recommend a correction and resubmission.

If you have any questions, please contact Dan Anders at daniel.anders@towermsa.com.

Section 111 Reporting for WCMSAs & Avoiding Civil Penalties

June 28, 2024

Section 111 Reporting for WCMSAs: Avoiding Civil Penalties

It’s time to get everything set up to accommodate new Section 111 reporting fields for WCMSAs. While compliance has long been required, Civil Money Penalties (CMPs) are real now.

Tower’s Chief Technology Officer Jesse Shade joined our Chief Compliance Officer Dan Anders for the “Premier Webinar: Get Ready for Section 111 Reporting Penalties and WCMSA Reporting” to help attendees do just that. Here are the highlights:

Important Section 111 penalty and WCMSA reporting dates

October 11, 2024
The date that CMS starts to make Responsible Reporting Entities (RREs) accountable for the timely reporting of ongoing responsibility for medicals (ORM) and of the Total Payment Obligation to the Claimant (TPOC). Any claims with ORM or TPOC on or after October 11, 2024, can be audited and subject to penalties.

April 1, 2025
CMS requires the reporting of WCMSA information when a TPOC is reported

October 11, 2025
Date that CMS starts its compliance review process.

April 1, 2026
CMS begins Section 111 reporting audits.

About those penalties

No penalties will be issued for claims that are reported within one year of the date of acceptance of ORM or the TPOC date. And no claims with ORM or TPOC dates prior to October 11, 2024, will be reviewed.

If a claim is not reported within one year, the RRE can incur penalties of $357 per calendar day. This per-day penalty increases to $1,428 if it’s not reported for three years. (These are 2024 inflation-adjusted rates.)

The good news is that CMS caps the amount of a penalty for a single instance of noncompliance by a non-group health RRE. The bad news is that cap is $365,000!

In the somewhat good news department, CMS will randomly select only 1,000 claims to audit each year and audit 250 claims every quarter. Additionally, the agency will randomly select claims from group health as well as non-group health plan (NGHP) claims from workers’ compensation, liability and no-fault programs. This greatly mitigates your risk of an audit even if you have instances of late ORM or TPOC reporting.

How does CMS notify RREs of penalties?

CMS first emails an informal notice, so it is important to keep contact information updated in the Section 111 Profile. This initial notice allows the RRE to present mitigating evidence and this must be presented within 30 days.

Examples of the type of evidence to submit include: ORM was not reported because the claim was under investigation OR a good-faith effort was made to obtain claimant information, such as a social security number, but the claimant refused to provide it or did not respond. (See CMS Section 111 Penalties Rule Focuses on Untimely Reporting – Tower MSA for details on “good-faith efforts” to establish Medicare eligibility.)

If the RRE does not respond to the informal notice or CMS rejects the explanation, the agency mails a formal written notice. At this point, an RRE either needs to pay a fine or appeal to an administrative law judge within 60 days.

WCMSA Reporting Fields

Jesse Shade reviewed the upcoming changes CMS will implement to collect additional information on WCMSAs through Section 111 reporting. New fields and the information for them were covered in this post.

Tower smooths the transition for its Section 111 clients.

Jesse also described Tower’s IT efforts to make things as easy as possible for our Section 111 reporting clients. Our goal is to improve your ability to monitor the pivotal events in a claim.

The first step for Tower reporting clients is adding the new WCMSA fields to the end of your current claim input file.  Once the fields are added to the feed file, testing will be scheduled to confirm that the data is properly transmitted to Tower. Tower will, in turn, participate in a testing period with CMS that begins in October.

The additional fields will require those who enter the Section 111 reporting information to be trained on when to enter the WCMSA date, what date to enter, and how to enter the data.

Additionally, Tower will highlight in our MSA delivery correspondence the importance of completing this information at the time of settlement.

Tower will continue to provide comprehensive reports to our Section 111 reporting clients, ensuring the accuracy of the data reported.

Our commitment is to make this transition easy and seamless for everyone involved and we will customize systems where needed so the process works for all our clients.

Practices that protect RREs from penalties

Dan advised clients to do the following to maintain compliance with the reporting rules:

  • Query claims to identify Medicare beneficiaries monthly and document when a social security number cannot be obtained.
  • Report ORM acceptance and TPOCs on the next quarterly submission.
  • Correct errors in reporting data to avoid report rejection (if they reject a submission, it will be considered untimely if not corrected within the reporting deadline).
  • When WCMSA reporting begins, make sure these fields are completed anytime a TPOC is reported.

The webinar also provided several examples of how ORM and TPOC penalties could work and how they could be mitigated. Slides and access to the recorded webinar can be requested from Dan Anders, daniel.anders@towermsa.com.

Tower’s proactive audit

To ensure your organization’s readiness for the coming audits and penalties, have Tower audit your processes, policies and systems to see if there are any holes in your compliance. Not only will we identify errors and other issues that could lead to penalties, but we also help you fix issues that lead to them. For more information on our Section 111 audit offer, please contact hany.abdelsayed@towermsa.com.

Avoid Penalties: Tower’s Section 111 Reporting Audit Service

May 16, 2024

Person preforming Section 111 reporting audit service

Tower’s Section 111 Reporting Audit Service Can Help You Fix Systemic Issues and Avoid Penalties. Workers’ compensation payers and other Responsible Reporting Entities (RREs) have a little over five months to get their Section 111 reporting houses in order. And Tower’s Section 111 reporting audit service is here to help you clean things up.

Section 111 reporting – a bit of background

Starting October 11, 2024, RREs, which are workers’ compensation plans, liability insurance (including self-insurance) and no-fault insurance) will be held accountable for the timely reporting of Medicare beneficiary claimants where ongoing responsibility for medicals (ORM) has been accepted or where a Total Payment Obligation to the Claimant (TPOC) has occurred. Civil Money Penalties (CMPs) for untimely reporting of ORM acceptance or TPOC can be thousands of dollars on a single claim.

Three reasons to have Tower audit your Section 111 reporting

  1. Catch the type of errors, omissions and inconsistencies that could trigger thousands of dollars in penalties.
  2. Eliminate systemic flaws that lead to time-consuming and unnecessary conditional payment demands
  3. Help you correct human and technology processes and procedures so you can avoid future reporting errors

What’s involved in the audit?

You provide a set of claim input, claim response and query response files for an agreed-upon period.
Our compliance experts examine this data for issues that can prevent proper and timely reporting of:

  • Acceptance of ongoing responsibility for medicals (ORM)
  • Termination of ORM
  • TPOC

We also look for:

  • Errors in claim input file data
  • CMS-identified errors and flags in claim response files
  •  Consistency of your policies and procedures with CMS Section 111 reporting standards

You’ll receive an audit report and consultation. The report will identify actual or potential errors, omissions and inconsistencies and recommend corrective actions. You’re not left on your own! Tower collaborates with you during the audit and guides the implementation of process and policy changes. As with all our services, we answer your questions and consult with you every step of the way.

How does this help conditional payment resolutions?

If payers or their RREs fail to report ORM termination through Section 111 reporting, Medicare assumes the payer is still responsible for injury-related medical bills. The agency will either deny payment on these or pay them and seek reimbursement through the conditional payment process. The audit identifies TPOC/ORM/Section 111 reporting issues and shows you how to fix them to prevent unnecessary conditional payment demands.

Tower’s Section 111 Audit provides quick fixes and policy and process changes for long-term Section 111 reporting compliance assurance.

Next steps? Contact Hany Abdelsayed, our EVP of Strategic Services at
hany.abdelsayed@towermsa.com or 888.331.4941.

Premier Webinar: Get Ready for Section 111 Reporting Penalties and WCMSA Reporting

May 3, 2024

Section 111 reporting

CMS Announces Section 111 Mandatory Insurer Reporting Changes: Penalties and New WCMSA Requirements

The Centers for Medicare and Medicaid Services (CMS) has released several announcements regarding Section 111 Mandatory Insurer Reporting over recent months.  Some relate to Section 111 penalties and some to the new requirement to add Workers’ Compensation MSAs to Section 111 reporting.

Timely and accurate Section 111 reporting is essential if you want to avoid penalties. And WCMSA reporting will introduce new tasks for claims professionals and potentially affect how WC cases with Medicare beneficiary claimants are settled.

To help you and your organization prepare for these changes

Tower will hold a “Get Ready for Section 111 Reporting Penalties and WCMSA Reporting” webinar on May 22.

Please join Tower’s Chief Compliance Officer Dan Anders and Chief Technology Officer Jesse Shade for this valuable, instructional session. Scheduled for Wednesday, May 22, 2024, at 2 pm ET, the hour-long webinar will address:

  • Criteria and timeline for the implementation of Section 111 Reporting penalties.
  • Practices to mitigate and eliminate the potential for penalties.
  • How a Section 111 reporting audit can identify errors, blind spots and recommend corrective actions to your systems and processes.
  • Criteria and timeline for Workers Compensation MSA reporting.
  • Implication of WCMSA reporting for claims professionals, attorneys, and settling parties.

A Q&A session will follow the presentation, and you can provide questions ahead of time at registration. Please click the link below and register today!

CMS Moves Start Date for WCMSA Reporting to April 2025

April 23, 2024

CMS delays start date for section 111 reporting of WCMSAs

CMS delays start date for Section 111 reporting of WCMSAs to April 2025 and announces new webinar for Q&A

During last week’s webinar, the Centers for Medicare and Medicaid Services (CMS) announced an extension of the start date for Section 111 reporting of WCMSAs from January 2025 to April 4, 2025.

(Due to technical difficulties with the April 16 webcast, CMS has scheduled another webinar for Q&A this Thursday, April 25, 2024, at 2:30 ET. Details on the webinar are here.

Remember, CMS requires Section 111 reporting of WCMSAs of any MSA amount, even if $0. These amounts must be reported whether they are CMS-approved MSAs or not.

CMS details new reporting guidelines and start date for Section 111 WCMSA Implementation

CMS reiterated several points that had been detailed in a prior webinar and through the recent Section 111 User Guide update.  Please review CMS Updates Section 111 NGHP User Guide and WCMSA Reference Guide for this information. New points are below:

  • The start date for WCMSA reporting was changed from January 2025 to April 4, 2025, to give Responsible Reporting Entities (RREs) more time to make the needed changes to their reporting processes.
  • Testing of the new fields will be available beginning on October 7, 2024.
  • All WCMSA fields except Field 43 (Professional Administration EIN) will result in “hard” errors if reported incorrectly. Hard errors cause the TPOC report to be rejected, which can in turn cause the report to be untimely if it is not corrected promptly.
  • As such, hard errors may result in the imposition of civil money penalties (CMPs) although CMS will not impose a CMP for two reporting periods after implementation of WCMSA reporting. In other words, only records on or after October 15, 2025, and with a reportable MSA are subject to a CMP.
  • If an RRE fails to report an MSA, CMS may utilize all available statutory and regulatory options to recover mistakenly made payments, including under the False Claims Act.
  • No changes are made as to what constitutes a reportable TPOC. If a TPOC is reportable, then the WCMSA fields must be completed. If it is not reportable, such as when the WC settlement is $750 or less, then the WCMSA fields are not completed.
  • If multiple defendants are parties to a single settlement, they must report the total TPOC amount (and not their “share”) and the total MSA amount.
  • The Section 111 reporting process is not intended to replace the submission of settlement documents to CMS following the settlement of a claim with a CMS-approved MSA. (Final settlement documents should always be sent to Tower for upload to CMS.)
  • Receipt of the MSA report through the Section 111 reporting process will allow CMS to send information to the beneficiary on the attestation and exhaustion process. (Currently this is not done for most self-administered non-submit MSAs).

CMS outlines impact of “W” records in common working file (CWF) for MSA reporting

CMS also explained that once the MSA is reported, a “W” record will be posted in the Common Working File (CWF), which prevents payments of medical services related to the reported diagnosis codes. The CWF is part of CMS’s system to accurately coordinate benefits, so Medicare does not make payment when another “primary payer” is available.

A copy of the webinar slides can be found here.

Please contact Dan Anders at daniel.anders@towermsa.com with any questions.

CMS Updates Section 111 NGHP User Guide and WCMSA Reference Guide

April 5, 2024

woman holding CMS-Updates binder

CMS Releases Updates to MMSEA Section 111 NGHP User Guide and WCMSA Reference Guide

The Centers for Medicare and Medicaid Services (CMS) began April with updates to two of its popular user guides, the MMSEA Section 111 NGHP User Guide and the WCMSA Reference Guide.  Notably, the NGHP User Guide, version 7.5, now includes details on the requirements to report WCMSA amounts with other relevant data. These will need to be reported as of April 4, 2025.

The NGHP User Guide, Section 6.5.1.1 of Chapter III: Policy Guidance, was updated to state:

For workers’ compensation records submitted on a production file with a TPOC date on or after April 4, 2025, Workers’ Compensation Medicare Set-Aside Arrangements (WCMSAs) must be reported.

CMS also updated Chapter IV: Technical Information with similar language.

CMS Revisions to WCMSA Reporting Fields in Chapter V: Appendices

Additionally, CMS updated Chapter V: Appendices to identify the fields that will be added to the Claim Input File Detail for WCMSA reporting:

  • Field 37 – MSA Amount: This will be either $0 or an amount greater than $0. If an annuity is used, then the “total payout” is reported.
  • Field 38 – MSA Period: If the MSA amount is greater than $0, you need to enter the number of years the MSA is expected to cover the beneficiary.
  • Field 39 – Lump Sum or Structured/Annuity Payout Indicator: If the MSA amount is greater than $0, you will enter “L” for a lump-sum MSA or “S” for a structured/annuity MSA.
  • Field 40 – Initial Deposit Amount: If an annuity, then the MSA seed amount is reported.
  • Field 41 – Anniversary Deposit Amount: If an annuity, then the amount of the annual payments.
  • Field 42 – Case Control Number (CCN): If an MSA is submitted to CMS for review or is otherwise submitted to CMS post-settlement, it will be assigned a CCN. The CCN is entered in this field, although this is optional.
  • Field 43 – Professional Administrator EIN: Enter the Employer Identification Number of the professional administrator here if there is one. If this EIN is not provided, the “case administrator” defaults to the beneficiary. If the EIN does not match a registered administrator account in the Workers Compensation Medicare Set-Aside Portal (WCMSAP), then “case administrator” will also default to the beneficiary.

CMS provided a table of error codes for errors identified in the above-reported information.

Responsible Reporting Entities (RREs) can start testing these new fields on October 7, 2024. For further details, see the Tower article, CMS Sets Date for Start of Section 111 WCMSA Reporting.

CMS also incorporated the following notice into the NGHP User Guide:

As of January 1, 2024, the threshold for physical trauma-based liability insurance settlements will remain at $750. CMS will maintain the $750 threshold for no-fault insurance and workers’ compensation settlements, where the no-fault insurer or workers’ compensation entity does not otherwise have ongoing responsibility for medicals (Section 6.4).

The $750 reporting threshold has been in place for several years.

CMS included minor updates to the WCMSA Reference Guide, version 4.0

Specifically, CMS added:

Instruction specific to beneficiaries has been added to encourage them to use their Medicare.gov access to the portal for the most efficient method of submitting attestations (Sections 11.1.1 and 17.5).

For further information on electronic reporting of attestations, see the above-referenced sections in the guide or the Tower article, CMS Adds Electronic Submission Option for MSA Attestations.

CMS also amended the link in Section 10.3 to reflect the most recent CDC Life Table link. The life tables are used to determine life expectancy for calculation of the MSA.

CMS Sets April 16 for Webinar on Section 111 Reporting of WCMSAs

March 27, 2024

Webinar on Section 111 Reporting of WCMSAs

Prepare for Change: CMS Webinar on Expanding Section 111 NGHP TPOC Reporting to Include WCMSA Information

The Centers for Medicare and Medicaid Services has scheduled a webinar for April 16, 2024, at 2 PM ET to provide updates on the implementation of Section 111 reporting of Workers Compensation Medicare Set-Asides (WCMSAs).  Per the March 25, 2024 announcement:

CMS will be hosting a second webinar regarding the expansion of Section 111 Non-Group Health Plan (NGHP) Total Payment Obligation to Claimant (TPOC) reporting to include Workers’ Compensation Medicare Set-Aside (WCMSA) information. After the first webinar in November, CMS received additional questions and feedback from the industry. The intent of this webinar is to ensure that RREs will be prepared for the change once implemented. With that in mind, this webinar will include a background recap, summary of technical details, updated timelines and CMP impacts. The presentation will be followed by a question and answer session. Because this expansion impacts reporting of WCMSAs, it is strongly recommended that Responsible Reporting Entities (RREs) that report Workers’ Compensation settlements attend.

There is no pre-registration for the webinar.  Full details can be found here.

As of April 4, 2025, TPOC reporting must include Workers’ Compensation Medicare Set-Aside Arrangements (WCMSAs). (See CMS Sets Date for Start of Section 111 WCMSA Reporting).

The WCMSA reporting requirement applies to both CMS-approved and non-approved MSAs.  This information must be reported if the insurance type is workers’ compensation and the TPOC amount is greater than $0. The rule will be prospective only, meaning it applies to TPOC dates of April 4, 2025 and later.

To collect this data, CMS is adding new fields to the Section 111 Claim Input File.

Tower will provide a post-webinar summary.  If you have any questions, please contact Dan Anders at daniel.anders@towermsa.com or 888.331.4941.

 

Special Webinar: Your Need-to-Know Guide on Section 111 Reporting Penalties

October 16, 2023

Pctures with details regarding the October 18th Webinar on Section 111 Penalties

CMS recently published its final rule on the imposition of Section 111 Mandatory Insurer Reporting penalties.  While we addressed the specifics of the rule in our article, CMS Section 111 Penalties Rule Focuses on Untimely Reporting, we know that many questions remain.

In a special webinar on October 18 at 2 p.m. ET, Tower’s Chief Compliance Officer, Dan Anders, and Chief Technology Officer, Jesse Shade, will provide your need-to-know guide to these penalties.  Topics will include:

  • Complete analysis of the rule, including criteria, penalty amounts and appeals
  • Examples of reporting situations which will and will not run afoul of the rule
  • Safe harbors from penalties
  • Best practices to mitigate and eliminate the potential for penalties
  • Resources available to Tower Section 111 reporting clients to ensure proper reporting

A Q&A session will follow the presentation, and we encourage you to submit questions when you register. Please click the link below and register today!

Please note there is no CEU credit offered for this webinar.

Register Here

 

 

CMS Changes Rules for ORM and NOINJ Reporting in the Latest Update of its Section 111 Reporting User Guide

June 9, 2023

CMS User Guides for Section 111 Reporting. open book with colored page markers

The Centers for Medicare and Medicaid Services (CMS) recently released Version 7.2 of its MMSEA Section 111 User Guide. The guide contains some notable updates for Ongoing Responsibility for Medicals (ORM) reporting, determination of the ORM termination date with a physician letter, and use of the NOINJ code in certain liability settlements.

Revised Trigger for ORM Reporting

CMS revised Section 6.3 (Policy Guidance) on the trigger for reporting Ongoing Responsibility for Medicals (ORM):

The trigger for reporting ORM is the assumption of ORM by the RRE, which is when the RRE has made a determination to assume responsibility for ORM and when the beneficiary receives medical treatment related to the injury or illness. Medical payments do not actually have to be paid, nor does a claim need to be submitted, for ORM reporting to be required. The effective date for ORM is the DOI, regardless of when the beneficiary receives the first medical treatment or when ORM is reported.

We surmise that CMS added the additional requirement (bolded) for reporting ORM so that allow no-fault plans do not have to report ORM on minor claims that have no evidence of medical treatment.  Workers’ compensation plans already have an exclusion for reporting ORM on minor medical-only WC claims where medical payments do not exceed $750, along with other requirements (See Section 6.3.1 of the guide).

The change raises an interesting question: What obligation does the no-fault plan have to determine if treatment has occurred?  In other words, does the no-fault plan have to actively inquire about treatment? Or can it be passive and wait to report ORM after treatment is occurring? There isn’t an answer from CMS’s ORM definition.

Determining ORM Termination Date Based on Physician Statement

CMS previously added a provision to Section 6.3.2 (Policy Guidance) which allows ORM termination based on a physician statement finding that no additional medical items and/or services associated with the claimed injuries will be required.  Apparently, a question arose about what ORM termination date to enter if such a physician letter is obtained.  Per CMS:

Where an RRE is relying upon a physician’s statement to terminate ORM, the ORM termination

date to be submitted should be determined as follows:

  • Where the physician’s statement specifies a date as to when no further treatment was

required, that date should be the reported ORM termination date;

  •  Where the physician’s statement does not specify a date when no further treatment was

required, the date of the statement should be the reported ORM termination date;

  •  Where the physician’s statement does not specify a date when no further treatment was

required, nor is the statement dated, the last date of the related treatment should be used as the ORM termination date.

The above should clarify the appropriate ORM termination date to use when a physician statement is obtained.

Reporting of NOINJ is Now Optional

Since the early days of Section 111 reporting CMS has required liability claims where medicals are released in settlement but where the type of claim typically has no associated or alleged medical care to be reported.  Because there were no diagnosis codes to report, these claims were reported with a “NOINJ” code.  Examples of such claims were loss of consortium, an errors or omissions liability insurance claim, a directors and officers liability insurance claim, or a claim resulting from a wrongful action related to employment status action.

CMS has now revised its policy in Section 6.2.5.2 of the User Guide (Technical Information) on the reporting of such claims to state:

Note: In cases where the reporting of a liability record only meets the criteria for reporting a ‘NOINJ’ diagnosis code in Field 18, the reporting of the record is no longer required. However, it is optional for the RRE to report the record with the ‘NOINJ’ diagnosis code following the previously existing rules in the User Guide as follows:

This update is great news for carriers who have had to report these types of claims for more than a decade now.

If you have any questions on these updates, please contact Tower’s Chief Compliance Officer, Dan Anders, at (888) 331.4941 or daniel.anders@towermsa.com

CMS: Lead Insurer is RRE for Subscription Insurance Policy Section 111 Reporting

April 26, 2023

CMS User Guides for Section 111 Reporting. open book with colored page markers

In an update to its Section 111 MSP Mandatory Reporting User Guide (Version 7.1 Chapter III Policy Guidance) CMS made clear that in a subscription insurance policy arrangement, the lead insurer is solely responsible for Section 111 mandatory reporting requirements.

The new section of the guide, Section 6.1.13 states:

In a subscription insurance policy arrangement, two or more insurers enter into an agreement whereby the risk of the insurance policy is spread among the various insurance entities in some agreed-upon ratio. In such arrangements, a lead insurer is designated for various administrative and business purposes. While there may be many co-insurers on a subscription insurance policy, there is only one lead insurer, and that lead insurer remains so throughout the policy life cycle.

 Due to the nature of the subscription insurance market and the way such policies are structured, it is appropriate for the lead insurer to act as the sole RRE as it relates to Section 111 mandatory reporting requirements. The ability for the lead insurer to act as the sole RRE is predicated on the assumption that the lead insurer will avail themselves of all rights, requirements, and responsibilities codified in statute and further set out in regulation and within this and any other sub-regulatory guidance provided by CMS, as is from time to time amended. In any such lead reporting situation, as it relates to subscription insurance policies, CMS will assume that the lead insurer, as the sole RRE, will be responsible for all applicable reporting, recovery, and benefits coordination requirements that presently exist, regardless of the existence of any other co-insurer that may enter into a subscription arrangement or similar contract with the lead insurer.

Practical Implications

With subscription insurance policies, risk is divided among two or more policies. It can be an equal split, or one company assumes more risk than another as long as the combined coverage equals 100% of the required limits.  In these arrangements, one insurer takes the lead as administrator.

Based on this policy announcement, only the lead insurer is required to complete Section 111 reporting as the sole RRE.  Other insurers are released from reporting responsibilities.

Please get in touch with Dan Anders, Chief Compliance Officer, at daniel.anders@towermsa.com or 888.331.4941 with any questions.