Electronic Health Records

Policy & Regulation News

CMS Clarifies Flexibilities After ICD-10 Compliance Deadline

By Kyle Murphy, PhD

- The Centers for Medicare & Medicaid Services (CMS) has provided clarification concerning its joint announcement with the American Medical Association (AMA) on flexibilities following the October 1 ICD-10 compliance deadline.

CMS clarifies the flexibilities it will provide following the ICD-10 compliance deadline

On Monday, the federal agency released answers to numerous frequently asked questions in response to feedback from members of the healthcare industry.

First and foremost, CMS reiterates in the FAQs that the July 6 announcement in no way signifies another ICD-10 delay.

"Medicare claims with a date of service on or after October 1, 2015, will be rejected if they do not contain a valid ICD-10 code," the federal agency states. "The Medicare claims processing systems do not have the capability to accept ICD-9 codes for dates of service after September 30, 2015 or accept claims that contain both ICD-9 and ICD-10 codes for any dates of service. Submitters should follow existing procedures for correcting and resubmitting rejected claims."

  • Quebec rolls out province-wide health information exchange
  • mHealth nuances: Mobile security and training
  • 7 Time-Saving EHR Use Tips to Boost Physician Productivity
  • Putting Epic EHR Data to Work for Quality Improvement
  • EHR implementation checklist for hospitals
  • EHR as starting point for accountable care, not just ACOs
  • Indian Health Service seeks to modernize EHR by 2014
  • Are clinicians ready for ICD-10 documentation requirements?
  • Health Information Exchange Sees Growth at eHealth Exchange
  • How Meaningful Use Requirements Impact Health IT Standards
  • Kaiser Permanente joins DreamIT Baltimore accelerator
  • Senate Requests Return of $729.4M in Overpaid EHR Incentives
  • Blue Button Aids in Health Data Exchange with Patients
  • Cerner Seeks EHR Contracts with More Government Agencies
  • How a culture of collaboration, HIT can lead to quality care
  • Mercy Health System Recognized as Top Epic EHR User
  • Study shows EMRs savings determined by complementary factors
  • In-Person Consults at Center of State Telehealth Debates
  • OIG Considers EHR Adoption, Meaningful Use Audits in 2015
  • Do EHR Technology Challenges Outweigh the Benefits?
  • Lakeland, FL hospitals use EHR to monitor quality of graduate education
  • mHealth startups, EHR solutions secure big grants, VC funding
  • How does health IT ensure the success of reporting programs?
  • New SGR repeal estimates place costs at $121 billion
  • 10 Biggest Cerner EHR Implementations in United States
  • How Do Different Health Industry Experts View Data Blocking?
  • AHRQ Studies “Wrong Patient” EHR Errors to Improve Safety
  • Bill Foresees VA EHR Replacement as Interoperability Threat
  • Google takes another stab at healthcare with Calico
  • Accountable Care Task Force Outlines Rules for Value-Based Care
  • HHS Interoperability Pledge Gains Major Support at HIMSS 2016
  • EHR Use Nearly Universal in Hospital Outpatient Practices
  • Former EHR exec gets caught stealing $60,000 from company
  • AMA Begins Two Initiatives to Support Healthcare Innovation
  • HIMSS, AMDIS Suggest Ways CMS Can Reduce Administrative Burden
  • How can EHR adoption move providers beyond meaningful use?
  • Everything’s bigger in Texas, including newly expanded HIE
  • The HIT Group wants input into FDA regulation of health IT
  • VistA scheduling system contributes to scheduling woes at VA
  • CHIME $1M Challenge Pushes for National Patient Identifier
  • Developing Quality Measures to Succeed in Value-Based Care
  • ONC Chief Talks Health IT Standards, Information Sharing
  • Final Health IT Certification Rule Supports HIT Transparency
  • IBM partners with Epic for highly coveted DoD HIM contract
  • 74% of patients comfortable with online physician communications
  • VA Spent Over $1.1B on Homegrown EHR Modernization Efforts
  • Task Force Grapples with HIT Product Comparison Framework
  • ‘Action First’ Vital in Health Information Exchange
  • CMS Extends Hospital 2014 Meaningful Use Reporting Deadline
  • How Most Office-Based Physicians Utilize Health Data Exchange
  • CMS provides updates on ICD-10 delay, dual coding, testing
  • Exercise lowers 30-day readmissions by 34% for COPD patients
  • Meridian Health Plan joins MiHIN data exchange network
  • MEDITECH Offers Users EHR-Integrated PDMP Link through Expanse
  • IOM: Healthcare must work smarter to support physicians
  • Is $2.35 per Patient a Fair Price for EHR Interoperability?
  • Mobile EHR and the mobile practice
  • CIOs to Benefit from CHIME’s KLAS, HIT Research Partnerships
  • ICD-10 transition and your practice
  • Where Did This Latest Meaningful Use Extension Come From?
  • Allscripts Guilty of Deception in EHR Certification, Sales Fight
  • Greenway, eHealth Exchange Lead HIE Project in Oregon
  • AHA, AMA support proposed changes to 2014 meaningful use
  • Has ONC Assumed Too Much about Interoperability for MACRA?
  • ICD-10 Preparation Lacks Testing, Revenue Impact Analysis
  • Pathway for SGR Reform Act provides 3-month Medicare fix
  • CHIME Awards Innovation Prize for Interoperability, FHIR Work
  • Slow and steady likelier to win the race for EHR adoption
  • Horizon BCBS of New Jersey, LHS Health Network create ACO
  • ONC Report Highlights Need for Health IT Interoperability Push
  • Tackling claims processing, payment management bottlenecks
  • Funding to Fuel Tech Adoption at Georgia HIE Intermediaries
  • Telehealth for chronic disease patients improves satisfaction
  • HIMSS Analytics includes ambulatory EHR use in new model
  • Potential VA Secretary Nom May Finish Cerner EHR Contract Talks
  • Industry Experts Provide Meaningful Use Summaries, Analysis
  • NCHS reports physician EHR adoption numbers
  • CMS Seeks Public Comment to Reduce Stark Law Regulatory Burden
  • DirectTrust Backs ONC Focus on EHR Usability, Interoperability
  • CMS Seeks Comments on Reporting Clinical Quality Measures
  • Medical scribe certification may ease EHR data entry burdens
  • Practice Fusion makes EHR big data public with new tool
  • New York HIEs Merge, Bring State Closer to Interoperability
  • USDA Awards $8.6 Million in Telehealth Grants for Rural Health
  • Early Look at the ONC Nationwide Interoperability Roadmap
  • How Physician EHR Use Can Lead Patients to New Therapies
  • Vets Call for VA EHR Optimization, Interoperability Advances
  • Self-Service Models Missing from Patient Engagement
  • Cambridge Health Alliance agrees with BIDMC to join ACO
  • Do Health IT Systems Need Greater Interoperability?
  • VA Epic Scheduling System Implementation May Be Under Budget
  • Meaningful patient engagement through EHR, social media
  • EHRs, meaningful use improve patient safety, medical errors
  • Understanding Interoperability, Value of Health IT Standards
  • Rocky Cerner EHR Implementation Spurs Conflict, Billing Problems
  • ONC Promotes Health IT Interoperability with New Tech Lab
  • Program brings mHealth, medical reference apps to Gulf Coast
  • Small Practices Express Concern over Effects of EHR Adoption
  • CMS Confirms Readiness to Assist During ICD-10 Transition
  • DoD and VA plan to speed up EHR adoption schedule
  • Of particular importance to healthcare organizations and providers is what constitutes a valid ICD-10. CMS has furnished them with an answer:

    ICD-10-CM is composed of codes with 3, 4, 5, 6 or 7 characters. Codes with three characters are included in ICD-10-CM as the heading of a category of codes that may be further subdivided by the use of fourth, fifth, sixth or seventh characters to provide greater specificity. A three-character code is to be used only if it is not further subdivided. To be valid, a code must be coded to the full number of characters required for that code, including the 7th character, if applicable. Many people use the term billable codes to mean valid codes. For example, E10 (Type 1 diabetes mellitus), is a category title that includes a number of specific ICD-10-CM codes for type 1 diabetes. Examples of valid codes within category E10 include E10.21 (Type 1 diabetes mellitus with diabetic nephropathy) which contains five characters and code E10.9 (Type 1 diabetes mellitus without complications) which contains four characters.

    A complete list of the 2016 ICD-10-CM valid codes and code titles is posted on the CMS website at http://www.cms.gov/Medicare/Coding/ICD10/2016-ICD-10-CM-and-GEMs.html. The codes are listed in tabular order (the order found in the ICD-10-CM code book). This list should assist providers who are unsure as to whether additional characters are needed, such as the addition of a 7th character in order to arrive at a valid code.

    According to the FAQs, CMS will specify whether a claim is rejected for an invalid code versus a lack of specificity required for Local Coverage Determinations (LCD) or National Coverage Determinations (NCD). CMS has warned that the guidance will not result in changes to current automated claim processing edits, meaning that certain ICD-10 codes would be rejected if "not consistent with an applicable policy."

    Regarding Medicaid, CMS notes that added ICD-10  flexibility only applies to Medicare fee-for-service claims. However, the Medicaid programs in each state will be "required to process submitted claims that include ICD-10 codes for services furnished on or after October 1 in a timely manner."

    Additionally, CMS makes clear that 12-month one-year period of claims payment review leniency in no way guarantee that commercial payers will follow suit.

    Read all the FAQs here.



    Sign up to continue reading and gain Free Access to all our resources.

    Sign up for our free newsletter and join 1000,000 of
    your peers to stay up to date with tips and advice on:

    EHR Optimization
    EHR Interoperability

    White Papers, Webcasts, Featured Articles and Exclusive Interviews

    Our privacy policy

    no, thanks

    Continue to site...