Electronic Health Records

Policy & Regulation News

Perils of Using GEMs as Crosswalks for ICD-10 Transition

CMS advised that GEMs should not be used to code patient encounters due to numerous documented shortcomings, assumptions, exceptions and deficiencies as a coding translation tool for coding.

By John Pitsikoulis of Berkeley Research Group

- During the ICD-10 preparation phase, many vendors, clinicians, and IT administrators converted their current I-9 environment with an approach that included using the general equivalence mappings (or a version of the GEMs) as the key mechanism for preparing their ICD-10 coding and billing tools. One of the challenges with the conversion to the ICD-10 code set was the initiative to duplicate the ICD-9 code set in the EHR system with the new expanded ICD-10 code set.

ICD-9 to ICD-10 crosswalks could prove dangerous

Since there was no standard approach for preparing the industry for the new ICD-10 environment, healthcare entities adopted various approaches and methodologies to accomplish this goal.

The GEMs have become the gold standard approach for many payers, providers, and software vendors for the transitions from ICD-9 to ICD-10. It is understandable how one would use the GEMs — if they wanted general equivalence code translations. However for functions such as coding and billing, this is not a logical solution as the GEMs intent was to generally match an I-9 code to the ICD-10 code.

Since the development of the GEMs, the Centers for Medicare & Medicaid Services (CMS) has stood firm in their advisement that GEMs are not crosswalks, rather reference mappings to help the user navigate the complexity of translating meaning from one code set to others. CMS advised that GEMs should not be used to code patient encounters due to numerous documented shortcomings, assumptions, exceptions and deficiencies as a coding translation tool for coding.  

  • EHR-Based Reminders Quickly Improve Medication Adherence
  • What HIPAA compliance means in the cloud
  • ONC shows path to Stage 2 Meaningful Use via Blue Button
  • EHR Patient Data from Rochester RHIO Fueled HPV Vaccine Study
  • $178M Cerner EHR System Under Review After Persistent Problems
  • EHR Interoperability, Integration Focus of HIT Replacement
  • Is Meaningful Use Responsible for Limited EHR Usability?
  • HIMSS: Only half of hospitals have data archiving strategies
  • Current Solutions to EHR Interoperability Issues
  • Why communication is essential for health IT consulting
  • athenahealth Not Engaging With Elliott Acquisition Offers
  • NC health system signs on with Mercy to implement Epic EHR
  • CCHIT no longer to certify EHR systems for meaningful use
  • What’s so important about connecting EHRs and genomics?
  • EHR program calls asthma patients when it’s time for a refill
  • Why CMS chose 2015 as the deadline for ICD-10 compliance
  • EHR Interoperability Issues Challenge Primary Care Teams
  • Ensuring Patient Concerns Don’t Limit Health Data Exchange
  • NYeC, Healtheway develop HIE interoperability certification
  • Cumberland Center for Healthcare Innovation, Cigna form ACO
  • AHA Issues Updated MACRA Resources Following QPP Proposed Rule
  • Leidos DoD EHR Modernization Team Adds EHR Training Group
  • KPMG report indicates unease in EHR implementation
  • Certified EHR: Breaking down the ONC fact sheet
  • Mostashari: Beacons show health information exchange’s value
  • NC HIE latest to add direct messaging
  • AHRQ announces EHR format guidelines for pediatric care
  • Why A Great ICD-10 Steering Committee Is So Important
  • How is accountability affecting rate of readmissions?
  • How Do Different Health Industry Experts View Data Blocking?
  • Epic Named Best EDIS Enterprise Vendor in Overall Satisfaction
  • ONC provides 2014 CQM resources for Stage 2 Meaningful Use
  • Debating effect of Stage 2 Meaningful Use on EHR adoption
  • Primary Care Doctors Spending 6 Hours Daily on EHR Data Entry
  • Healthcare Foursquare? Geomedicine tracks disease triggers
  • AHA Suggests CMMI Promote Health Data Exchange, Regulatory Relief
  • What’s next after Mostashari’s last day at the ONC?
  • Healthcare fraud leads to enrollment moratoria in hot spots
  • How are iPads, tablets influencing mobile EHR designs?
  • Delaware REC helps 1000 providers reach Stage 1 Meaningful Use
  • Final Federal HIT Strategy Plan for Learning Health System
  • Meaningful Use Requirements Impact Adoption of EHR Functions
  • Are HISPs a help or hurdle for health information exchange?
  • Will EHR adoption encourage information exchange?
  • UPMC study to focus on patient-centered mental health IT
  • Is ad-supported software the solution to EHR replacement woes?
  • NWU Project for Patient-Reported Outcomes, EHR Integration
  • Kansas EHR incentives quickly reach $25 million
  • Gauging success of ONC HIE grant recipients
  • Meaningful Use Rule Not Final, But Attestation System Closed
  • Edward Marx receives CHIME-HIMSS 2013 CIO of the year award
  • CDI produces financial, clinical benefits apart from ICD-10
  • Halamka Offers Guidance for Health IT Implementation, Policies
  • Common Clinical Quality Measures Providers Need to Report
  • CMS Prepares Providers for 2016 Meaningful Use Attestation
  • HITSC Workgroup suggests changes to EHR module security certification
  • Will MACRA Implementation Unfairly Affect Small Practices?
  • Start ICD-10 success with the data you already have now
  • Has CMS Failed to Demonstrate Value of Meaningful Use?
  • GAO Calls for VA to Adopt Commercial EHR, VA Likely to Do So
  • Allscripts Launches EHR-Integrated Lyft Transportation Service
  • Care coordinators, guides help navigate complex “continuum”
  • AMA inaugurates Dr. Robert Wah as new president
  • 5 Strategies Driving SHIN-NY Roadmap for Health Data Exchange
  • Why real-time data matters to successful practice management
  • Provider Use of HIE Yields Savings in Reduced Repeat Imaging
  • Surescripts, Epic team up for clinical interoperability
  • Beth Israel announces eMAR roll-out for Stage 2 Meaningful Use
  • EHR adoption increases 133% at community health centers
  • Additional physicians exempt from eRx penalties due to EHR incentives
  • AHA Explains Industry Challenges for EHR Interoperability
  • AAFP Calls for a Less Burdensome ONC Interoperability Plan
  • ONCHIT programs that assess HIT individual competence
  • VT Health Information Exchange Makes Key External Connection
  • What can studies of EHR learn from eRx?
  • Georgia HIE grows with addition of Grady, Emory Health
  • AAFP Requests Simplified Quality Payment Program Requirements
  • Don’t panic! Unspecified ICD-10 codes are still okay to payers
  • Surescripts CEO Harry Totonis to step down in March
  • New Policy Should Accomodate Physician EHR Documentation Demands
  • AHIMA: Half of providers plan to go ahead with ICD-10 anyway
  • Epic Systems Taking TCS to Court over Theft of Trade Secrets
  • ONC Grants $1M for Community Health Information Exchange
  • 3 Programs Supporting Health IT Standard FHIR Development
  • Why ICD-10 Transition Hinges on Clinical Documentation
  • CDC Sees Increase in Emergency Care, Ambulatory EHR Adoption
  • Ohio Healthcare IT Day 2014 to focus on telehealth
  • Aetna, Cigna Continue Push for Accountable Care
  • MA Digital Health Council to Spark State Health IT Growth
  • CHIME, HL7 Embrace JASON Task Force Interoperability Plans
  • GAO, ACHCI highlight shortcomings of CMS Medicare oversight
  • Bulk of wasted DOD, VA iEHR money went to support contracts
  • Value in Leveraging EHR Use Across the Care Continuum
  • Survey: 75% of providers haven’t started ICD-10 testing
  • What physicians make of incentives for care reform
  • ICD-10 transition to impact specialists more negatively
  • HELP Committee Again Seeks Delay of Stage 3 Meaningful Use
  • AMA supports SGR repeal, merit-based incentive system
  • Finalization of Stage 3 Meaningful Use May Need Postponement
  • VA seeks new scheduling unit to work with VistA EHR
  • Unfortunately, many practice managers and hospital administrators will be in for a rude awakening with ICD-10 outcomes. As a result of the very small percentage of one-to-one code matches between ICD-9-CM and ICD-10, EHRs, code search tools, and data conversions tools that relied on the GEMs as a crosswalk made the grave mistake of vastly underestimating the complexities of ICD-10 coding.

    EHR technology and coding tools intended to assist the physicians with code selections are many times configured in a manner that facilitates the selection of an incorrect code. The physician EHR user may only be accessing a subset of codes converted with the GEMs, thereby resulting in the assignment of unspecified or other coders converted as a GEMs default selection. Remember, the GEMs “crosswalk” only contains a very small percentage of one to one code equivalents; resulting in a system configuration that is in many instances less accurate than your ICD-9 system.

    As we all know, ICD-10 transition is not just a coding change; it is also a clinical documentation specificity issue. Many organizations provided clinical documentation specificity education, which was a necessity for preparing for ICD-10 compliance. However, physicians are not coders with many having received only minimal training on the new coding tools and less likely education on ICD-10 coding guidelines and conventions.

    An EHR system with an incorrectly configured coding workflow combined with the clinical documentation requirements significantly increases the revenue and compliance risk that the code selected by the physician is not supported by the clinical documentation in the EHR system.

    As with any major regulatory changes, opportunities to improve performance, mitigate risks and compliance with the regulatory changes become apparent through a detailed analysis. Knowing the risks associated with the misuse of the GEMs, starting with EHR coding tools and structure configuration is an optimal approach for providing the physicians with improved workflow.

    More importantly, enhancements to the EHR coding and billing functions, regardless of the EHR platform, will provide the physicians who perform their own coding an accurate and compliant process. Physician billing process workflow simplification and compliance must be a priority to provide the physician with a decreased administrative burden so that they can dedicate time to their top priority, the patient.

    John Pitsikoulis is a Managing Director at Berkeley Research Group with more than 30 years of consulting experience. He has provided advisory services to clients related to complex business problems including EMR optimization, operational process improvement, coding and clinical documentation.



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