Copyright

(c) 2010-2025 Jon L Gelman, All Rights Reserved.

Saturday, March 21, 2009

CMS Publishes a User Manual for MSP Reporting

The Centers for Medicare and Medicaid Services (CMS) has now published a User Manual. The manual details the federal procedures that will be utilized to implement Section 111 of the Medicare, Medicaid, and SCHIP Extension Act of 2007 (MMSEA Section 111).

July 1, 2009 is the implementation date for mandatory reporting in workers' compensation claims. Section 111 adds reporting requirements and does not eliminate any existing statutory provisions or regulations. CMS' existing processes, including for example, CMS’ process for self-identifying pending liability insurance (including self-insurance), no-fault insurance, or workers’ compensation claims to CMS’ Coordination of Benefits Contractor (the COBC) or the processes followed by CMS’ Medicare Secondary Payer Recovery Contractor (the MSPRC) for MSP recoveries, remain undisturbed. The Act does impose penalties for noncompliance.

CMS has announced that it will offer a "query function" to required reporting entities to ascertain whether or not the claimant is a Medicare beneficiary. The query will be based upon identifying data including: HICN or SSN; first initial of the last name; first 6 characters of the last name; date of birth and gender.

Yet to be determined are a host of reporting issues including:

  • Interim dollar reporting threshold for "Total Payment Obligation to the Claimant" (TPOC) amounts -- CMS’s decision on this issue will be released separately in the near future.
  • Interim dollar reporting threshold for "Ongoing Responsibility for Medicals" (ORM) -- CMS has this issue under consideration.
  • Further information regarding reporting for mass torts – This issue is still under discussion.
  • ICD9 Codes – CMS is reviewing the codes to determine if there are certain codes which Responsible Reporting Entities (RREs) will be prohibited from submitting.
  • Examples regarding "Who is the RRE" -- CMS is reviewing additional examples submitted by the industry for possible inclusion in the User Guide.

No comments: