BN - Medicare Data Match Process (Demand Letters)

GENERAL DESCRIPTION:

This provides guidance on what steps an institution should follow if they receive a Medicare Demand letter.

Background - Centers for Medicare and Medicaid Services (CMS), Benefit Coordination & Recovery Center (BCRC) is the organization that oversees the Medicare Coordination of Benefits.
The first step in the process is the Coordination of Benefits (COB) in which the BCRC works with Employee Trust Funds (ETF) for coordination of benefits to verify if Medicare is the primary or secondary payer.

  • IRS-SSA-CMS Data Match questionnaire is sent to ETF to complete coordinating coverage month data.
  • ETF responds through a Voluntary Data Sharing Agreement (VDSA) using the Electronic Media process to reply to the questionnaire.

If BCRC determines after reviewing the data from the questionnaire that Medicare should have been the secondary payer, it will forward the claim for collection. A Demand Letter will be sent to the employer (UW Service Center) and the health insurance carrier. We are allowed 60 days to resolve this issue. If the situation is not resolved, a second notice will be sent from the BCRC.


PROCEDURE STEPS:


1.  If a Medicare Demand letter is received at the institutional level, please forward to the UW Service Center Benefits Team (Tier 3).  The UW Service Center will complete the processing. If contacted directly by a health insurance carrier regarding a Demand Letter, please refer them to the UW Service Center Benefits Team.

2. The UW Service Center will complete all remaining tasks related to a Medicare Demand Letter.

If you have any questions regarding this, please contact your AG Group.  The contact information is located on the left side of your page.



Keywords:Medicare Data Match Demand Letters CMS Benefit Coordination & Recovery Center BCRC Coordination of Benefits COB   Doc ID:52203
Owner:Samantha Q.Group:Human Resource System (HRS)
Created:2015-06-10 13:06 CSTUpdated:2017-06-08 08:35 CST
Sites:Human Resource System (HRS)
Feedback:  0   0