MEDTranDirect Takes on Late NOEs with the New NOE Tracker

Since October of 2014, timely filing of NOE/NOTRs (Notice of Election/Notice of Termination-Revocation) has been a leading issue for the hospice industry.  As a software company that works on Medicare electronic transaction processing, when these regulations were announced, they caught our attention as a possible opportunity for a new product that might resolve some of the issues that CMS and the hospice industry dealt with regarding the efficiency of these transactions.

Notice of Election Tracker

One of the most difficult tasks you deal with regarding developing new software solutions is understanding the actual issues involved with a process and what the problems really are for the entities involved.  When these regulations were announced, it was clear that CMS felt that it was important to get these transactions submitted within five days.  This told us two things.   First, they were not being processed within this window a substantial portion of the time and second, that this delay presented problems for CMS and the industry.

Continue reading

The “Sticky” NOE Problem

MEDTranDirect is a vendor of Medicare connectivity services, including access to the CMS HETS system (HIPAA Eligibility Transaction System) that provides real time eligibility data for healthcare organizations.  The data processed through this system is intended to provide a complete picture of all beneficiary data necessary to determine if payment will be received when healthcare services are provided to Medicare patients.

Late last year, we found a problem in the HETS data where the hospice NOE (Notice of Election) data was only present part of the time when it was processed in the CWF (Common Working File).  We documented this issue and reported it to HETS support.  Their initial response was that this was not a claim and that is why it was not showing up.  This did not make much sense since it did show up at least half of the time.  We resubmitted the problem again in February of this year, their response at that time was that it did not show up because the data was not in the CWF and the problem was with the MACs processing the NOEs and not the HETS system.  This conclusion was also not supported by the data we provided since we gave them screenshots of NOEs entered and accepted in DDE (Direct Data Entry), but were not present in HETS several days later.

Continue reading