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."

  • AAFP: Health IT Industry Should be Closer to EHR Interoperability
  • Minimal EHR Data Transferred to DoD MHS Genesis at Fairchild
  • 6 Areas to Watch in Health Information Exchange
  • Blue Button Aids in Health Data Exchange with Patients
  • FDA Expands EHR Data Analytics with Active Surveillance System
  • ONC Sets Up ‘Proving Ground’ for Health IT Interoperability
  • Halamka Offers Guidance for Health IT Implementation, Policies
  • Mass. General Implements Epic EHR to Boost Interoperability
  • How far-reaching an effect will ICD-10 have on 2014, beyond?
  • Cloud, Registry Added to Health Data Exchange Accreditations
  • Do providers have the EHRs for Stage 2 Meaningful Use?
  • HELP Committee Works to Support 21st Century Cures Act
  • Congress expected to vote on potential ICD-10 delay
  • Epic Named Best EDIS Enterprise Vendor in Overall Satisfaction
  • Study: HIE can reduce unnecessarily repeated tests
  • Smartphones feature in pilot study on patient engagement
  • EHR implementation preparation and planning: CIO series
  • E-prescribing on Surescripts using EHRs increases eight-fold
  • Main Characteristics of Successful EHR Vendors, Technologies
  • mHealth groups: Put patient generated data in Stage 3 MU
  • The EHR cost-control debate continues
  • Why Providers Seek EHR Flexibility Standards From CMS
  • HIMSS, EHRA add to the chorus of Stage 3 Meaningful Use comments
  • 3 Hospitals Sign onto Mercy SaaS for Epic EHR Implementation
  • Pushing through the gaps in health information exchange
  • HIE patient privacy, data security tips for providers: Q&A
  • MiHIN pilots PHI network for meaningful use patient engagement
  • New EHR Technology to Spur EHR Replacement, Other Predictions
  • EverGreen Health partners with Microsoft HealthVault
  • Ensuring Your EHR System Meets MACRA Requirements in 2017
  • Champion of Patient-Centered Care Judy Murphy to Leave ONC
  • How DirectTrust Can Aid Providers with FHIR, Health Data Exchange
  • Preparing for the next phases of health information exchange
  • Epic Systems Ranked Most Innovative EHR Vendor by C-Suite Execs
  • CMS is Prepared for ICD-10 Implementation, GAO Report Says
  • Regenstrief Confirms Commitment to Health Data Standardization
  • EHR Data Interoperability Should Meet Five Use Cases
  • New Grant Program Advances Health Information Exchange
  • Legacy Data Management Strategies Key to EHR Replacement
  • CMS Offers $30M for Quality Payment Program Measures Development
  • AHA backs bill to streamline merger, acquisition reviews
  • Solo Doctor Forfeits Medical License Over Paper Records
  • Providers look to Canada for lessons in ICD-10 implementation
  • Is the EMR market in the US heading for the cliff?
  • What EHR systems can gain from cloud computing?
  • 68% of New Doctors Prefer to be Employed Physicians
  • Collaboration Critical for Improving CDI Across Healthcare
  • Slow EHR, health IT adoption rates may endanger CAHs
  • Pros and cons of Health Information Exchange cloud computing
  • $180M EHR Implementation Project Approved at UW Medicine
  • EHR patient notes: What’s wrong with cloning, anyway?
  • Extending patient care through meaningful use of EHR, HIE
  • Peter O’Rourke to Replace Robert Wilkie as Acting VA Secretary
  • Guide: Meaningful Use Stage 2 clinical quality measures for EPs
  • GAO Calls for VA to Adopt Commercial EHR, VA Likely to Do So
  • Impact of eHealth Exchange on Nationwide Interoperability
  • Meaningful use attestation tools
  • Kansas HIE now state’s responsibility
  • SAMHSA offers guidance for ICD-10 transition
  • Patient engagement should produce smart data, smarter docs
  • Carequality, AMA Singly Advance Health IT Interoperability
  • How to Improve Patient Engagement in the Provider Community
  • As Adoption Slows, the Market Must Embrace EHR Interoperability
  • Group Seeks 90-day Meaningful Use Reporting Period in 2016
  • CMS seeks volunteers for end-to-end ICD-10 testing in 2015
  • Outpatient EHR Adoption Reaches 92%, Nears Market Saturation
  • NFL converts to EHR amid concern over head trauma, lasting injuries
  • Congress Urges CMS to Lower MIPS Exclusion Thresholds
  • HIE Use Cuts Costs, Increases Productivity in STI Treatment
  • 2014 EHR certification churns along as ONC list tops 1000
  • Bayonne Medical Center receives Stage 6 EMRAM recognition
  • EHR implementation timeline for hospitals
  • Physician Feedback Key to EHR Usability Improvements
  • BCBS of Michigan continues push for patient-centered care
  • NextGen Healthcare, Allscripts Expand Health IT Capabilities
  • Health IT Integration Challenges for Genomic Medicine
  • CHIME Outlines Top Health IT Innovation Priorities for HHS
  • Will free HL7 standards stifle interoperability issues?
  • Mercy Hospital St. Louis Achieves HIMSS Stage 7 with Epic EHR
  • Funding to Fuel Tech Adoption at Georgia HIE Intermediaries
  • ICD-10 updates: Providers must use new 1500 form by April 1
  • Is meaningful use too much of a hassle for radiologists?
  • EHR Quality Reporting Rewarded through $36.3M in HHS Funding
  • ONC, ANSI name 5 permanent certification bodies
  • $1.9M AHRQ Grant to Develop Clinical Decision Support Network
  • System-wide Epic EHR Downtime Affects 24 Sutter Health Hospitals
  • Top 5 ICD-10 considerations for small practices
  • Aprima continues quest to lure away Allscripts EHR users
  • Mercy SaaS Service Drives Accelerated Epic EHR Implementation
  • Mayo Clinic Adds Clinical Decision Support Tools to Labs
  • Will the SGR Bill Lead to an ICD-10 Implementation Delay?
  • Why EHR Copy-and-Paste Functionality Risks Patient Care
  • GE Healthcare EHR Earns 2015 Edition ONC Health IT Certification
  • When transitioning to EHRs, planning is key
  • CAQH Seeks Stakeholder Feedback on Provider Data Roadmap
  • 12 EHR Vendors Reach Agreement on Interoperability Standards
  • State Strongholds for EHR Vendors Among MU Hospitals
  • Virtual assistant aids patient engagement, accountable care
  • Interoperable EHRs Coming to More Care Facilities, CMS Says
  • Will Minnesota’s 2015 EHR Interoperability Mandate Work?
  • 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 60,000 of
    your peers to stay up to date with tips and advice on:

    EHR Optimization
    EHR Interoperability
    EHR Replacement

    White Papers, Webcasts, Featured Articles and Exclusive Interviews

    Our privacy policy

    no, thanks

    Continue to site...