Happy December everyone. Below are a few things that have crossed my desk recently that I found particularly interesting so I wanted to share. If you’ve run across any interesting articles lately, feel free to share them in the comments.
UHC to Open Medicare Centers in Walgreens
Humana to Layoff 800 employees by the end of 2019
UHC Faces CMS Sanctions on Medicare Advantage Plan
Priority Health and Total Healthcare to Merge
Anthem Suing Federal government for $100 Million in ACA payments
North Carolina Suspends 2/1/2020 Managed Medicaid Implementation
Good morning and happy November. As 2019 draws to a close, CMS as finally given a date for starting to get of HIQA, HIQH, ELGA and ELGH. They sent out the announcement below on 11/1. It sounds like they’re starting with clearinghouses first and will trickle down to everyone else later. I’ll pass on information on this as it becomes available.
” CMS will begin revoking access to Common Working File (CWF) eligibility transactions HIQA, HIQH, ELGA and ELGH effective February 1, 2020. Submitters that aggregate transactions for otherwise disparate providers (e.g., clearinghouses, billing services, software vendors, etc.) and have both HETS and CWF based eligibility access should use HETS exclusively.
CMS will remove HIQA/HIQH/ELGA/ELGH access for these submitters by revoking role-based access for specific CMS RACF IDs. CMS will revoke access starting with high-volume aggregators. Aggregators that use both HETS and CWF based eligibility should assume they must use HETS only no later than February 1, 2020.”
As we wrap up Q3, I’m seeing an increase in questions about the MBI and using it on Medicare eligibility questions. I suspect this is because the transition period for using the HICN or the MBI is coming to an end. Beginning January 1st, 2020 you will no longer be able to use the HICN for eligibility or claims (with a few exceptions).
One of the complaints I’ve seen is that HETS is returning errors in some cases when eligibility is searched using the MBI that’s on the card. I’ve heard that it’s possible the beneficiary’s MBI may change from the one that was originally issued. I’m validating this with CMS and will get back to you on what I find out. The majority of the problems I’ve seen with the MBI have been user keying errors so please make sure you’re keying exactly what’s on the card. If you still haven’t gotten access to the Medicare MBI lookup tool, I highly suggest that you sign up before the end of the year. If you’ve been using it, please leave me a comment and let me know what your experience has been.
Below is a list of exceptions that CMS has published for still using the HICN. I wasn’t aware of most of these so I thought I would pass them along.
This morning Aetna sent out the announcement below regarding some issues they’re having with their EDI transactions for precert and notifications. If you get a rejection with one of the codes listed below, please call the precert number on the members ID card to complete your precert request.
We’d like to let you know we’re rejecting some Precertification Add and Notification transactions, but we’re not returning all the rejection reasons.
We’re currently rejecting some Precertification Add and Notification transactions, but we’re not returning all the rejection reasons. Certain transactions are rejecting with the following two codes:
Our systems aren’t returning additional rejection reasons, so we’re unable to determine the exact reason for the rejected transactions. For some rejected transactions, we’ve determined there are duplicate requests.
We’re researching this issue at a high priority, but we don’t have a resolution date yet. We’ll send an update once we have additional information.
Below is a list of outstanding issues that CMS is on working for the HETS eligibility response. If you’re using eligibility from a vendor (Experian, Change Healthcare, Availity, etc) this is the response you’re receiving. This is also the connection everyone will be required to use once CMS sunsets the CWF eligibility functions.
|Table 1. Open HETS Data Issues Current Data Issues||Percentage of Impacted Medicare Beneficiaries||Date that a Fix is Planned||Detailed Description of the Issue|
|HETS may be returning incorrect Hospice episode information or occurrence counts when the Medicare Beneficiary has a new Notice of Election (NOE) and had billed Hospice episodes four or more years ago.||1%||October 2019||HETS’ data source for Hospice information is the Common Working File (CWF). CMS has identified an issue where CWF is sending an incorrect Hospice information to other systems (including HETS) when the Medicare Beneficiary has a new Notice of Election (NOE) and previously billed hospice periods. CWF updates the file and corrects the Hospice history once a Hospice claim is processed for the new billing period. CWF will update their database and processes to resolve these discrepancies and prevent future occurrences.|
|After the Medicare Beneficiary received the first Pneumococcal Vaccine (PPV), CWF is not sending the eligibility information for the second PPV vaccine to HETS.||33%||Q1 2020||HETS’ data source for prior PPV usage is the Common Working File (CWF). HETS returns PPV vaccination data using CWF records for HCPCS 90670 and 90732. HETS correctly returns the PPV vaccination next eligible dates for both HCPCS if the Medicare Beneficiary has never been vaccinated. When the HETS 271 returns no next eligible date available for PPV, the Medicare Beneficiary may have actually only received one of the PPV vaccines and may still be eligible for the second vaccine after a year between deliveries. CMS encourages Providers to discuss the Pneumococcal vaccine and any previous receipt of that vaccine with your patients.|
|CMS has identified a more accurate source of data for End Stage Renal Disease (ESRD) Dialysis Start Date and ESRD Dialysis End Date.||1%||August 2019||HETS currently returns ESRD information on the 271 response when Service Type Code ‘CQ’ or ‘RN’ are included in the 270 request. CMS has identified an issue with the data source used for the End Stage Renal Disease (ESRD) Dialysis Start Date and ESRD Dialysis End Date. CMS is working to correct this issue quickly. In the interim, CMS encourages dialysis clinics to co-ordinate with each other to get correct Dialysis Start Dates for the coordination of the Medicare Beneficiary’s dialysis training. CMS will modify its data source to utilize the improved data. The format of the ESRD data in the 271 response will be exactly the same as is currently in use.|