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

Using Modems for Medicare Connectivity

MEDTranDirect provides connectivity between healthcare providers and all the Medicare contractors (MACs).  Through this connection, providers can have access to the Direct Data Entry (DDE) or FISS system, the ability to send claim files and receive response files like the 835 and 277CA, and connection to the Medicare eligibility system (HETS).

The first two services have been available for almost thirty years.  When they were introduced, access to these systems was achieved through a modem, phone line, and a remote terminal to the IBM mainframe computers running these services.  Now, decades later, this technology is still prevalent among providers who are still using the same methods to access this information and conduct these transactions.  Although many users have replaced the remote terminal with an emulator that can run under Windows on an existing PC, the technology connecting this emulator to the MAC systems still exists and is still supported by many MACs today.

modem blog

Continue reading

Improving the Processing of NOEs and NOTRs for Hospices

As a vendor of eligibility processing services and a NSV (Network Service Vendor) for the Medicare HETS eligibility system, we have a vested interest in the capability of these systems to provide current and valid information. Through the HIPAA transaction for eligibility data (ANSI 270/271), we send requests to these systems for eligibility data for specific patients. Through a real time response, we can provide detailed information about the current status of this patient with the selected payer. This process involves converting the data returned by the payer into a report or entering it into a database.  In this process, we are the “messenger”. The content we provide is completely dependent on the quality of the payer response.

In some cases, these responses can be incomplete or inaccurate.  When this happens, we often get support incidents where providers complain that we are providing incorrect data. Most of the time, they are technically correct, but the issues they present as problems are beyond the ability of these payer systems to accommodate given the way this data is collected.

NOES and NOTRS Continue reading

The Impact of CMS Flexibility on ICD10 Implementation

CMS announced a joint statement with the AMA in early July regarding a compromise on how claims with 10 codes would be processed after 10/1/15.  They published FAQs and responses for this announcement on 7/27.

This announcement was advertised to be a settlement between these organizations regarding the efforts of the AMA to delay the implementation of ICD10 and the insistence of CMS that this deadline was final.

Initially, I was concerned about how this announcement might affect the adjudication of all Medicare claims and the potential modifications to Medicare contractor systems we had already tested with our applications over the last several months.  As it turns out, these changes to CMS policy are largely cosmetic and will have no impact on the processing of most claims.  Additionally, although this policy is promoted as a relaxation of the implementation, it provides little relief to healthcare providers and their staff that are unprepared for the transition.

Flexibility
Flexibility

Continue reading

Opposition to ICD10 – A Perspective of Self Interest

Last week I read several articles about the current efforts to delay the implementation of ICD10 by the AMA and some of our congressmen, possibly influenced by this organization.  Their extremely weak arguments against implementation focus on their own lack of preparedness for the implementation.  Anyone with any knowledge of what has already been done to prepare for this new code set would realize that the negative impact of another delay would far outweigh any benefits of allowing these procrastinators additional time to prepare.

ICD10 Coding
Opposition to ICD10

Continue reading

ICD10 and Medi-Cal Processing – Preparing for Chaos

As the ICD10 deadline approaches, providers and health plans (and their vendors) prepare for the transition with varying levels of effort, efficiency and success.  Although it is true that the organizations that plan, train and test for this event will be more prepared for the transition from ICD9 to ICD10 than their competitors, no organization will avoid the consequences of an industry that seems to struggle with change.

What will happen when Medicare requires the ICD10 codes and other health plans are unable to accept them?  From the provider perspective, the bottom line is receiving reimbursement for your services.  Regardless of the “rules”, providers have always had to comply with reality to get their money.

prepare for chaos
ICD10 Chaos on the horizon.

Continue reading

CMS End-To-End ICD10 Testing – April Results

CMS conducted the second round of end-to-end testing of claims with ICD10 data during the third week of April. MEDTranDirect, and one of our customers, Kimble Hospital of Junction, TX, were selected by Novitas for this round of testing.

As part of the testing process, 30 claims were sent for processing through our 837Direct product in a single batch. Most contained ICD10 codes and future dates, some contained ICD9 and current dates. All the submitted claims processed properly and the corresponding 999s and 277CA records were received.

In addition, CMS provided test 835 electronic remittance files that contained payment and adjustment data for the test claims reflecting how they will be paid in October.

ICD10 Testing
ICD10 Testing

Continue reading

ICD10 Implementation – Possible Delays Pending

With just a few months to go until ICD10 implementation, there is still some chance that implementation might be delayed yet again.

On 4/30/15, Representative Ted Poe of Texas introduced a bill to ban the use of ICD10.

The bill is called the “Cutting Costly Codes Act of 2015”. It prohibits the federal government from requiring the use of ICD10 instead of ICD9. Poe claims that the implementation of the new code set will put unnecessary strain on the medical community.

Possible Delays Pending
Caution

Continue reading

Medicare Eligibility through HETS and the Hospice Notice of Election (NOE)

Medicare maintains a computer system dedicated to the processing of eligibility requests through the HIPAA ANSI 270/271 transactions designed for this purpose. The system is called HETS which stands for HIPAA Eligibility Transaction System. You can obtain more information about this system from their site:
http://cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Technology/HETSHelp/HowtoGetConnectedHETS270271.html

This system is updated daily with information from the Common Working File (CWF) and other CMS systems to include current eligibility data and billing history for all current Medicare patients. This system is supported by the MCARE help desk. As one of the National Service Vendors for this system, we work closely with this organization to monitor reported issues and suggest enhancements. So far, they have done a very good job in dealing with the issues reported and correcting them.

Continue reading

Medicare dial-up connectivity is being eliminated for 717 area code.

EDI trading partners still connecting to Novitas via the former 717 area code modem telephone number will no longer be able to connect for claim submission and report retrieval as of 12:01 AM Eastern Time (ET) on Friday, August 29, 2014.:

novitas

The majority of our trading partners have already made these changes,

Inability to connect for claim submission, remittance and/or report retrieval. and we appreciate your assistance with this effort.  Currently, customers still connecting through the 717 area code telephone number may already be experiencing:

  • Decreased connection quality.
  • Frequent connection time-outs.
  • If your modem is more than four years old, you may need to purchase a new dial-up modem in order to connect.

Customers who have not changed to the new connections should speak to their software vendor immediately to resolve any connection issues you are experiencing.   Additionally, trading partners who are located in the 717 area code will need a long distance phone service in order to connect.

MEDTranDirect is an Approved Network Service Provider for Novitas. MEDTranDirect can provide you with a solution! MEDTranDirect provides secure high-speed Internet connectivity to online inquiry services and the Common Working File (CWF).

MEDTranDirect provides a simple and easy to use product “PayerLink” that provides access to: DDE, PPTN, VIPS, HETS, and Claims file transfer.

 

By Aaron Brandwein – Vice President of Sales and Marketing, MEDTranDirect