Confirming code system version of direct reference codes (DRC)

XMLWordPrintable

    • Type: Question
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • MADiE
    • QDM and QI-Core
    • Not Applicable
    • Measure developers are unable to confirm the code system version of direct reference codes used in logic.
    • Yes

      In MAT, for each annual update, users had to manually update the code system version for DRCs to ensure the correct code descriptor for a target code system version was displayed in the human readable, as code descriptors can change from year to year.

      We are seeking guidance on where the location of the code system version of direct reference codes should be entered in MADiE and how to confirm that the correct version, after the code is added to the CQL editor and is applied to the measure and human readable. No code system version is displayed in the human readable or in the CQL editor to confirm that a specific version of the code is being pulled into the measure.

      Below, please find questions regarding DRCs:

      1. For both QDM and FHIR, is there a way for a MADiE user to identify what version of the code system is assigned to a DRC?
      2. For both QDM and FHIR, if a code is inactive, is MADiE able to identify this and would it result in a "CQL error"?
      3. For both QDM and FHIR, if the code descriptor of a code has changed is MADiE able to identify this and would it result in a "CQL error"?
      4. For both QDM and FHIR, if you would like to include a specific code system version of a DRC in a measure, how would a user do this in MADiE?

      We are seeking overall guidance on DRC management in MADiE as it relates to application of a specific code system version of a code and code descriptor for both QDM and QI-Core measures.

       

            Assignee:
            Chandra Bartleman (Inactive)
            Reporter:
            Shardae Sims
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: