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

Identical value set Oid, Value Set Version and Expansion Id with different codes

XMLWordPrintable

    • Hide
      The file ep_eh_unique_vs_20130401.xlsx the user is referring to was removed from the VSAC Download page shortly after posting, because the April release contained updated value sets only for EH value sets, whereas the EP value sets were not updated until 2 months later, in June. We had this announced through the NLM VSAC Updates email list on June 28, 2013.
      So, the user should download the EH file for the 20130401 release and the EH file for the 20121221 release and compare those to the file ep_eh_unique_vs_20130615.xlsx, and, if any discrepancies found, report those to us for review.
      The duplicates that the user sees are due to the bug in the script that was used to generate the file ep_eh_unique_vs_20130401.xlsx, which was another reason that file was removed.
      As always, we recommend VSAC users to subscribe to our VSAC Updates email list at https://list.nih.gov/cgi-bin/wa.exe?A0=NLM_VSAC_UPDATES .
      Show
      The file ep_eh_unique_vs_20130401.xlsx the user is referring to was removed from the VSAC Download page shortly after posting, because the April release contained updated value sets only for EH value sets, whereas the EP value sets were not updated until 2 months later, in June. We had this announced through the NLM VSAC Updates email list on June 28, 2013. So, the user should download the EH file for the 20130401 release and the EH file for the 20121221 release and compare those to the file ep_eh_unique_vs_20130615.xlsx, and, if any discrepancies found, report those to us for review. The duplicates that the user sees are due to the bug in the script that was used to generate the file ep_eh_unique_vs_20130401.xlsx, which was another reason that file was removed. As always, we recommend VSAC users to subscribe to our VSAC Updates email list at https://list.nih.gov/cgi-bin/wa.exe?A0=NLM_VSAC_UPDATES .

      In comparing the ep_eh_unique_vs_20130401.xlsx and ep_eh_unique_vs_20130614.xlsx downloadable files from VSAC for April 1, 2013 and June 14, 2013, I found 246 Value Sets that have the Same OID and Value Set Version in the two files, but there are different codes within those value sets between the two files. I would expect the value set version Id/definition Id or expansion Id to change if there are changes to codes within the value set.

      For example, the April and June files contain the Value Set "Anticoagulant Therapy" with OID 2.16.840.1.113883.3.117.1.7.1.200. The Value Set has the same Version ID, Definition Id, and Expansion ID (20130401) in both files. However, in April’s file, there are 11 distinct RXNORM codes that did not appear in the June file. If 11 distinct codes were removed from this Value Set between April and June, why are the definition and expansion Ids in June's file the same as the version Id in April's file? (see also JIRA # regarding definition Ids and Expansion Ids).

      It appears that 209 of those 246 value sets simply had duplicate codes removed (same code from different versions of the same code set), however 37 value set had distinct codes added or removed

            rob.mcclure Rob McClure (Inactive)
            khmmm Kristen Humpherys (Inactive)
            Duc Nguyen (Inactive), Julia Skapik (Inactive), Maureen Madden (Inactive), Philip Chuang (Inactive), Pishing Chiang (Inactive), Steve Emrick (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: