Uploaded image for project: 'eCQM Issue Tracker'
  1. eCQM Issue Tracker
  2. CQM-710

SNOMED vs. ICD codes: The eSpecs include both. Do we need to include both in our EHR mapping, or pick one or the other?

XMLWordPrintable

    • Tanna Jackson
    • 972-890-7725
    • Hide
      In some places the clinical quality measures allow multiple methods of capturing data elements to provide additional flexibility and usability for different EHR vendors. Over time, it is expected that diagnostic codes will trend towards SNOMED but where it is reasonable, measure developers and stewards have tried to make accommodations for multiple diagnostic codes. It is not expected that both codes are captured for any one measure; furthermore, it is reasonable to map from one code system to the other for the purpose of correctly identifying patients in the eCQMs.
      Show
      In some places the clinical quality measures allow multiple methods of capturing data elements to provide additional flexibility and usability for different EHR vendors. Over time, it is expected that diagnostic codes will trend towards SNOMED but where it is reasonable, measure developers and stewards have tried to make accommodations for multiple diagnostic codes. It is not expected that both codes are captured for any one measure; furthermore, it is reasonable to map from one code system to the other for the purpose of correctly identifying patients in the eCQMs.
    • High Impact to Measure build

      The eSpecs include SNOMED codes and also ICD codes in the specifications. Is it the expectation that we use both ways to capture the diagnosis codes? It seems redundant, and we would capture the information with one or the other. I want to make sure that I configure our CQM reporting as we should.

            julia.skapik Julia Skapik (Inactive)
            dalakt Tanna Jackson (Inactive)
            Kevin Larsen (Inactive), Maria Michaels (Inactive), Rob McClure (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: