1 / 85

5010 in 2012: Not The End of The World

5010 in 2012: Not The End of The World.

adara
Download Presentation

5010 in 2012: Not The End of The World

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 5010 in 2012: Not The End of The World

  2. Len Stusek – Senior Manager, Partner, has been in healthcare IT/EDI since 1988. The last ten years he has served to lead both EDI Sales and Customer Service teams with Quadax as the Division achieved unprecedented growth and nearly 100% client retention. Pat Blech – Product Manager, is responsible for development, implementation and training of the company’s Denial Management suite of applications. Patrick is well- seasoned in client relations and a veteran at speaking on such topics as 5010 and Denial Management.

  3. While some are predicting the end of the world in the year 2012, rest assured that it will not be as a result of the transition to 5010. 5010

  4. 5010. . .What worked, what didn't work and the residual fall-out of the 5010 transition. Many providers faced increased rejections. Where did they come from and recommendations for identifying and working those claims effectively.

  5. What is 5010? • “When you arrive at a fork in the road, take • it.”Yogi Berra

  6. 5010 Transactions • Healthcare Claims - 837 – Institutional and Professional • Remittance Advice – 835 • Eligibility Inquiry/Response – 270/271 • Claim Status Inquiry/Response – 276/277 • Claims File Functional Acknowledgement - 999 • Claims Acknowledgement– 277CA

  7. Intended Purpose of 5010 • Provide the infrastructure on ICD-10 Diagnosis Codes and Present on Admission Indicators • Reduce redundancy and provide uniformity in transaction structure and usage of data content • Reduce dependency on trading partner companion guides which many entities were forced to rely on with 4010A1

  8. 270 & 271 Transactions • Primary and Secondary insurance will now be identified • 5010 version allows for a search by Member ID, last name only or date of birth

  9. 276 & 277 Transactions • Claim Status can be reported – Provider Level, Claim Level and Service Line Level • Addition of Account Number field, receive “cleaner” responses.

  10. 999 File Acknowledgement Previously each Medicare Administrative Contractor produces custom error reports that varied by jurisdiction The Functional Acknowledgement 997 is being replaced by the 999 transaction The TA1 and 999 reflect technical problems that must be addressed by the software preparing the EDI transmission The 999 is output from the Translator indicating either R (Rejected), E (Accepted with Errors), A (Accepted) Clearing houses and software vendors can use these transactions to produce reports tailored to their customers.

  11. 277CA Transaction Proprietary error reporting (277U, 277R ) will be replaced with the 277CA Claims Acknowledgement transaction Claim by claim reporting, accepted claims and returns claim number and rejected claims with the error codes indicated in one file. The 277CA reflects a data problem that must be addressed by resources in the Billing area; Billing staff will likely need reports (or work queues) to be produced using the 277CA transaction in order to identify claim corrections before resubmission.

  12. 5010/ICD-10 Timelines

  13. 5010 and the MACs • MACs and CEDI will support the submission of 4010A1 and 5010 837 claim transactions in production starting April 5, 2011 through December 31, 2011 March 31, 2012. • CMS grants HIPAA 5010 compliance leeway, MGMA asks for more (additional 90 days)

  14. Clearinghouse/Submitter role • 4010 to 5010 for noncompliant providers • 5010 to 5010 standardization? • 5010 to 4010 for noncompliant payers

  15. 5010 – The Aftermath • 837 issues/updates • How do I navigate thru the “stuff”? • 835 issues updates • Tips for post 5010 Denial Management • Final Thoughts • Questions?

  16. From: MedicareEmailList@cgsadmin.com [mailto:MedicareEmailList@cgsadmin.com] Sent: Monday, March 05, 2012 3:17 PMTo: Len StusekSubject: Kentucky Part B News from CGS Kentucky Part B News from CGS Version 5010 – Where Are We Now? Centers for Medicare & Medicaid Services Webinar – Central Event Invitation: Please join the Centers for Medicare and Medicaid Services Regional Offices for an informative webinar on Version 5010 for healthcare providers, clearing houses, vendors and others. Read More...http://www.cgsmedicare.com/kyb/pubs/news/2012/0312/Cope18248.html From: event_registration@intercall.com [mailto:event_registration@intercall.com] Sent: Monday, March 05, 2012 3:36 PMTo: Len StusekSubject: Registration Confirmation You have registered for the following event: EVENT INFORMATION ----------------- Company: CMS Event Title: Version 5010 - Where Are We Now? - Eastern Webinar Event Date: Mar 6, 2012 Event Time: 10:00 AM ET You are not registered for the webinar. Webinar and phone line capacity have been reached. Check with the CMS website (www.cms.gov ) for future opportunities and information. Thank you!

  17. 5010 Early implementation • During the week of December 5-9, 2011, National Government Services experienced processing issues with the new Part A Common Edit Module (CEM) which has resulted in a backlog of claims to be processed through the CEM.                             • Some payers cut-over early without notice resulting in file rejects. • Inbound sent in 5010 format but Outbound sent in 4010 format, due to mapping issue as per 5010 specs in Loop 2010AA Billing provider name, Ref Segment, Data Element 1H - CHAMPUS Identification Numberis not required but it is essential in 4010 which cause this error “BILLING PROVIDER 2ND-ID IS INVALID”

  18. Top Problematic Payers • Caresource - 5010 to 4010 back to 5010 • OH Medicaid - MITS transition ahead of 5010 • MI Medicaid • MI Blue Cross • Aetna • Healthplus (MI) • Note – list does not include a WV specific payer! “If the world was perfect, it wouldn't be.” Yogi Berra

  19. Compliance Statistics • Vendor Compliance • Dec. 2011 50% • April 2012 Projection – 75% • Payer Compliance • Dec. 2011 30% rep. 15% volume • Feb. 2012 80% rep. 67% volume • April 2012 Projection - 94% rep. 75% volume

  20. 5010 issues - General • Claims not making it to payers • No visibility into claim status • Increased rejections • Delayed/missing remits • Vague rejections • Degradation of support • Some entities were reporting 10x production issues & 8x volume increase in call center activity

  21. 5010 Issues post 1/1/2012 • Edits have been updated to accept LOB indicator of "FI" on 5010 FEP claims. • Some payers had dark days where their system was down and did not provide notice. No files could be sent (837’s) or received (835’s) • P55819_496 Submitter not approved for electronic claim submissions on behalf of this entity • Claims containing Occ Code 50 will reject. This is a known issue and there is no established fix date (resolved 1/23/2012)

  22. WV Medicare B - has distributed both ANSI 835 files with "T" for Test and "P" for Production in the same file. Caused remit delay. • Other varied and sporadic ERA (835) delays. • Some providers were “unlinked” to established Clearinghouse with remits going to another. • Rejection of secondary claims that contain negative dollar amounts - CMS has not issued a statement as to how to report claims paid by the primary payer with negative values, something that was acceptable under the 40.10 guidelines.

  23. Invalid rejection of claims for NPIs not being registered with the submitter. The NPI issue was resolved by the various Medicares, affected files had to be resubmit, which resulted in payment delays due to the “ceiling” being reset. • The FISS system added new DRG codes with the January release, however these were not included in the CEM reference file. FISS is aware of this issue and will be correcting under PAR ZFSZ6613. There is no scheduled release date for this issue at this time. • *P56617 – National drug code or universal product number : Invalid for Payer.

  24. Crossover Claim Issues Important Information Concerning Medicare Outreach Efforts to Supplemental Payers Directing Their Payments to Incorrect Addresses •  Over the past several weeks, many physician/practitioner billing offices have notified their servicing A/B Medicare Administrative Contractor or Part B Carrier and the Centers for Medicare & Medicaid Services (CMS) that various supplemental payers have directed payment, arising from Medicare crossover claims, to incorrect payment addresses. The problem appears to have escalated as the supplemental payers have transitioned from receipt of crossover claims in version 4010 professional claims format to the version 5010A1  professional claims format. CMS believes it understands the full dimension of the problem and wishes to pass along those details to affected physician/practitioner billing offices through this article. • http://www.cms.gov/MLNMattersArticles/Downloads/SE1212.pdf

  25. CMS is not receiving similar complaints from institutional providers as tied to Pay-to Address information reported on HIPAA 5010 837 institutional production COB/crossover claims.

  26. Possible Cause #1: • For HIPAA ANSI X12-N 837 version 4010A1 professional claims, Medicare's Part B claims processing system (Multi-Carrier System or MCS) usually only created the 2010AA loop, including the N3 and N4 segments. Since the HIPAA 4010A1 837 Professional Claims Implementation Guide had no prohibition against reporting Pay-to Address-related information—such as Lock-Box or P. O. Box address information, as retained within PECOS and the internal physician/practitioner files as the physician/practitioner’s “check or remittance address”—in the 2010AA N3 and N4 segments, the Part B claims system created 4010A1 837 professional outbound crossovers that only contained 2010AA loop address information. • Under HIPAA 5010 requirements, Medicare must now create a 2010AB loop, with N3 and N4 segments, if the Pay-to Provider Address differs from the Bill-to Provider Address. This means that the address that most often used to be reflected in the 2010AA loop N3 and N4 address segments (which in reality was the Pay-to Address) now has to be reflected in the 2010AB N3 and N4 segments. Now, under HIPAA 5010, the address that Medicare reflects in the 2010AA N3 and N4 loops is truly the Bill-to Provider Address (or “master” and/or “physical address,” as captured within PECOS and the internal Medicare files).

  27. Conclusion tied to Possible Cause #1: Supplemental payers with Coordination of Benefits Agreements (COBA) may systematically still be reading the 2010AA N3 and N4 loops as the basis for determining where to direct their supplemental payments.

  28. Possible Cause #2: • The physician/practitioner’s “check or remittance address,” as maintained by Medicare is no longer valid. As previously mentioned, the “check or remittance address” becomes the 2010AB N3 and N4 segments on outbound version 5010A1 837 professional crossover claims. Remedy for Possible Cause #2: • If the address reflected in the 2010AB N3 and N4 segments is incorrect, the physician or practitioner will need to contact its servicing A/B MAC or carrier to have this information updated through appropriately established procedures.

  29. Possible Cause #3: • There may be instances where the supplemental payer uses the address information that it maintains within its internal files as the basis for directing supplemental payments to a given physician or practitioner, and that information is out of date. Remedy for Possible Cause #3: • The physician/practitioner’s billing office will need to address this matter with the supplemental payer directly for resolution.

  30. Crossover Claim Issues • The COBC activates the following edits once COBA trading partners move into HIPAA 5010 or NCPDP D.0 production: • N22226—“4010A1 production claim received, but the COBA trading partner is not accepting 4010A1 production claims.” • N22230—“NCPDP 5.1 production claim received, but the COBA trading partner is not accepting NCPDP 5.1 production claims.” • *To review the entire CR6658, visit http://www.cms.gov/transmittals/downloads/R1844CP.pdf on the CMS website. • *To review the entire CR6664, visit http://www.cms.gov/transmittals/downloads/R1841CP.pdf on the CMS website.

  31. Crossover Claim Issues • Breaking News – Friday, March 16th • Our Part A claims processing system (FISS) maintainer has identified a situation whereby taxonomy codes reported on incoming version 5010A2 claims are not reliably mapping to outbound version 5010A2 COB/crossover claims. This issue is precipitating numerous problems for State Medicaid Agencies as well as a small number of commercial payers.

  32. Navigating the “stuff” • If you have missing claims • Claim not showing up as accepted from a 277ca • Contact Clearinghouse partner • Claim showing as sent to payer but no payer reporting back • Contact payer – if the payer has no information • Contact Clearinghouse partner

  33. Navigating the “stuff” • Check your provider enrollment and NPI information for correct reporting of Billing and Servicing provider information with each of your payers. •  Actively monitor CMS, payers and clearinghouse partner websites for news. • ‘In theory there is no difference between theory and practice. In practice there is.’ Yogi Berra

  34. Available Resources

  35. J11 Part A Issues

  36. Medicaid Workshops • The WV Bureau for Medical Services (BMS) and Molina Medicaid Solutions will be conducting seven (7) Provider Workshops throughout the state from March 26 – April 9, 2012. We are offering the workshops at various locations to accommodate as many providers as possible. All sessions are identical and include either a continental breakfast or an afternoon snack. Subjects will be discussed that affect a wide variety of provider types. Please join us at this year’s Provider Workshops so you and your staff are aware of new developments that may impact you.Below are the scheduled events. • Martinsburg at Comfort Inn: March 26, 2012 9:00 am – 1:00 pm • Morgantown at Lakeview Resort: March 27, 2012 9:00 am – 1:00 pm • Wheeling at Oglebay Park, Pine Room: March 28, 2012 9:00 am – 1:00 pm • Huntington at Big Sandy Arena: March 29, 2012 12:00 pm – 4:00 pm • Charleston at Charleston Civic Center: April 3, 2012 9:00 am – 1:00 pm • Flatwoods at Days Inn Hotel: April 5, 2012 9:00 am – 1:00 pm • Beckley at Tamarack: April 9, 2012 12:00 pm – 4:00 pm

  37. Medicaid Contacts

  38. Clearinghouse Partners

  39. Top VW Medicaid Errors – February 2012

  40. Reporting Impact • Claim Status Category changes remove all “Not Advised” codes which includes pended claims. Removing the Pend/Suspend category codes on the 835 means that Plans/Payers will now have to report pended claims on the 277CA instead of the 835. • New 5010 standards be implemented/delivered uniquely by HIS/PMS, clearinghouse and individual payers. The potential (reality) is increase is upfront edits at clearinghouse, increase in front end rejections based on tighter edits and reporting on 277ca and increase in 835 denials do rule changes, system changes and unintended consequences.

  41. Impact of 5010 Conversion on Claim Processing

  42. HIS/PMS Ability to Support 5010 • Does your host system have the ability to produce a 5010 formatted file?

  43. HIS/PMS Ability to Support 5010 New 837- 5010 Fields

  44. HIS/PMS Ability to Support 5010 • 4010 or print image may require staff manually populate 5010 required data

  45. HIS/PMS Ability to Support 5010 • 4010 or print image may require staff manually populate 5010 required data • Billed information may deviate from information stored in Host System • Time consuming labor cost

  46. HIS/PMS Ability to Support 5010 • Inability to produce 5010 source file may ultimately result in clearing house payer rejection • May result in future processing issues as well • No support for ICD10

  47. Clearing House/Vendors Ability to Support 5010 • Does your clearinghouse have the ability to accept a 5010 formatted file?

  48. Clearing House/Vendors Ability to Support 5010 • Will your vendor actively track which payers do/do not accept 5010 and transmit required format? • 5010 enforcement period begins July 01, 2012 for most health plans • 5010 enforcement period begins January 01, 2013 for all “Small” health plans

  49. Clearing House/Vendors Ability to Support 5010 • Failure to transmit required ANSI 837 version may result in entire FILE REJECTIONS

  50. Clearing House/Vendors Ability to Support 5010 • Clearing House/Vendors should remain current on all payer specific guidelines to minimize rejections • See CMS MLN Matters® Number: SE1137

More Related