Category and SNOMED domains out of sync

XMLWordPrintable

    • Type: Annual Update
    • Resolution: Answered
    • Priority: Minor
    • Component/s: ValueSet
    • Intelligent Medical Objects
    • Hide
      The issue identifies an important analysis of value set content that reveals some inconsistencies in the content of the value sets. The comments are correct for this category - value sets created using SNOMED CT for the QDM "Diagnosis" category should be focused on Disorder, Finding, Situation, and Event. The (very helpful) file provided that lists concepts that fall outside that scope are indeed unlikely to be of value for the measure and will be re-considered with the next annual update.

      In the future, with value sets created using the VSAC, these restrictions will be easier to implement.

      It should be noted that while the QDM categories associated with measure "data types" usually provide good guidance on the types of concepts that should be selected for inclusion, on occasion the categories are a bit too broad to enforce definitive scope restrictions.
      Show
      The issue identifies an important analysis of value set content that reveals some inconsistencies in the content of the value sets. The comments are correct for this category - value sets created using SNOMED CT for the QDM "Diagnosis" category should be focused on Disorder, Finding, Situation, and Event. The (very helpful) file provided that lists concepts that fall outside that scope are indeed unlikely to be of value for the measure and will be re-considered with the next annual update. In the future, with value sets created using the VSAC, these restrictions will be easier to implement. It should be noted that while the QDM categories associated with measure "data types" usually provide good guidance on the types of concepts that should be selected for inclusion, on occasion the categories are a bit too broad to enforce definitive scope restrictions.

      Value Sets with a Category of "Diagnosis" and Quality Data Element of "Diagnosis, Active.." contain SNOMED codes outside of that scope. These outside scope SNOMED domains that are currently being used would be:
      -observable entity
      -regime/therapy
      -procedure
      -organism
      -body structure
      -morphologic abnormality
      -qualifier value
      -navigational concept

      To stay within the bounds of "Diagnosis," the relevant SNOMED domains are:
      -disorder
      -finding
      -situation
      -event

      The intent of the Value Sets using the former list of domains should be able to be captured within these latter four. Has it been considered to restrict the allowable domains of Categories? The inverse issue applies to the Procedure category and others likely have similar issues.

      Attached is the list of what would be affected in the Diagnosis category.

        1. mu2_invalid_diagnosis_june.xlsx
          32 kB

            Assignee:
            Rob McClure
            Reporter:
            Greg Aldin (Inactive)
            Emir Khatipov (Inactive), Kevin Larsen (Inactive), Maria Michaels (Inactive), Maureen Madden (Inactive), Minet Javellana (Inactive), Rabia Khan (Inactive), Steve Emrick (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: