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

Discrepancy between Technical Release Notes and eCQM Value Sets Addendum posted at VSAC.

XMLWordPrintable

    • Icon: Annual Update Annual Update
    • Resolution: Done
    • Icon: Moderate Moderate
    • ValueSet
    • None
    • Hide
      Thank you for your question. The VSAC contains the correct codes for the value set release, and there is an error in the Technical Release Notes. In the 2017 Q4 Addendum, the Antithrombotic Ingredient Specific Value set (2.16.840.1.113762.1.4.1021.8) deleted the following codes:

      235473 heparin, porcine

      237057 lepirudin

      The following code was added:

      5224 heparin

      Updated Technical Release Notes will be published shortly.
      Show
      Thank you for your question. The VSAC contains the correct codes for the value set release, and there is an error in the Technical Release Notes. In the 2017 Q4 Addendum, the Antithrombotic Ingredient Specific Value set (2.16.840.1.113762.1.4.1021.8) deleted the following codes: 235473 heparin, porcine 237057 lepirudin The following code was added: 5224 heparin Updated Technical Release Notes will be published shortly.
    • Need guidance ASAP as this is for Q4 2017 eCQM submissions

      In the Technical Release Notes (Q4 2017 code system updates only) Addendum PDF document and associated spreadsheets it says the following:

      Value set Antithrombotic ingredient specific (2.16.840.1.113762.1.4.1021.8): Added 12 RXNORM codes and deleted 2 RXNORM codes (235473, 237057).

      The eCQM Value Sets Addendum posted at VSAC contains only 1 added RXNORM code for the Antithrombotic ingredient specific value set not 12. It does have the 2 deletes matching that part of the release notes.

      Which is correct? The value set posted on the VSAC or the release notes? If it's the release notes can we get a corrected value set ASAP?

            JLeflore Joelencia Leflore
            pyamaura Patrick Yamaura (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: