CMS will not initiate enforcement action against HIPAA-covered entities for an 
additional three months, through Sat June 30, 2012, for the updated HIPAA 
transaction standards (ASC X12 Version 5010, NCPDP Versions D.0 and 3.0).  CMS 
is aware that there are still challenges and issues affecting an industry wide 
upgrade.  To help HIPAA-covered entities with the upgrade, CMS continues to 
update and improve their Version 5010 resources.

Updated FAQ System
CMS has updated the FAQ system and the way it is organized.  There are now 
three ways to more easily find Version 5010 FAQs by going to the CMS FAQs 
Page<https://questions.cms.gov/> and:

 *   Click on the Topic HIPAA Administrative Simplification on the left side of 
the page

    *   Click on the Subtopic Versions 5010 and D.0 that will appear as a 
dropdown under the topic (FAQs on Version 5010 and D.0 will be listed on the 
right side of the page)

 *   Click on the Topic Coding on the left side of the page

    *   Click on the Subtopic ICD-10 that will appear as a dropdown under the 
topic (FAQs on Version 5010 will be listed out on the right side of the page)

 *   Entering the search term "Version 5010" in the Search box on the upper 
left side of the page

CMS' Version 5010 and D.0 FAQs can also be found on the Version 5010 
page<http://www.cms.gov/Medicare/Coding/ICD10/Version_5010.html> of the ICD-10 
website, on the FAQs: Versions 5010 and D.0 Transition Basics fact 
sheet<http://www.cms.gov/Medicare/Coding/ICD10/Downloads/Versions5010D0FAQs.pdf>.
  The newest FAQ recently added by CMS is:

Question:  Is my Version 5010 837 claim compliant if it includes situational 
data that the TR3 Report does not prohibit, and is not needed or used by a 
specific health plan?

Answer:  Yes.  If a submitter sends claim information to a primary payer that 
may not be needed by that payer, but is needed by a secondary or tertiary 
payer, the primary payer should disregard the unneeded information and accept 
the compliant claim. For example:

 *   A data element in the TR3 Report has situational usage and language that 
says "If not required by this implementation guide, do not send."
 *   The submitter submits that data element because it is needed for 
processing by a particular payer that may be secondary or tertiary to the 
primary payer.
 *   A payer that does not need or use that data element cannot reject a claim 
because it contains a data element or information that it does not need or use, 
provided usage of the data element is compliant with the TR3 Report.

Version 5010 Testing Readiness Fact Sheet
CMS also has a Version 5010 Testing Readiness Fact 
Sheet<http://www.cms.gov/ICD10/Downloads/Versions5010TestingReadinessFactSheet.pdf>,
 which explains the Version 5010 upgrade and necessary Phase I Internal and 
Phase II External testing.  This fact sheet can help providers to determine 
steps to successfully complete testing phases for Version 5010.

Keep Up to Date on Version 5010 and ICD-10
Please visit the ICD-10 website<http://www.cms.gov/ICD10> for the latest news 
and resources to help you prepare, and to download and share the implementation 
widget<http://www.browserspring.com/widgets/cms2/iframe.html> today!

________________________________
Note:  If you have problems accessing any hyperlink in this message, please 
copy and paste the URL into your Internet browser.

If you know someone who would like to subscribe to a Medicare Fee-For-Service 
(FFS) provider listserv, go to 
(http://www.cms.gov/prospmedicarefeesvcpmtgen/downloads/Provider_Listservs.pdf).



If you would like to unsubscribe from a specific provider listserv, please go 
to (https://list.nih.gov/cgi-bin/wa.exe?INDEX) to unsubscribe or to leave the 
appropriate listserv.



Please DO NOT respond to this email. This email is a service of CMS and routed 
through an electronic mail server to communicate Medicare policy and 
operational changes and/or updates. Responses to this email are not routed to 
CMS personnel. Inquiries may be sent by going to 
(http://www.cms.gov/ContactCMS).   Thank you.


Reply via email to