Uploaded image for project: 'CYPRESS Issue Tracker'
  1. CYPRESS Issue Tracker
  2. CYPRESS-244

Problem status OID causes error in Cypress

    Details

    • Type: Implementation Problem
    • Status: Closed
    • Priority: Minor
    • Resolution: Delivered
    • Labels:
      None
    • Solution:
      A bug was discovered in the code system validation wrt whitelisting where it did not properly look up the oids in the whitelist table. This will be resolved in a future release.

      Description

      We are getting the following Cypress errors with Cypress 2.4:

      The valueset 2.16.840.1.113883.3.88.12.80.68 declared in the document cannot be found.

      We are also getting this error for STK3 which has to do with “Problem Type”.

      The valueset 2.16.840.1.113883.3.88.12.3221.7.2 declared in the document cannot be found.

      However, per the QRDA I specification

      Problem Status:
      1. SHALL contain exactly one [1..1] value with @xsi:type="CD", where the @code SHALL be selected from ValueSet HITSPProblemStatus 2.16.840.1.113883.3.88.12.80.68 DYNAMIC (CONF:7365).

      Problem Observation:
      1. SHALL contain exactly one [1..1] code, which SHOULD be selected from ValueSet Problem Type 2.16.840.1.113883.3.88.12.3221.7.2 STATIC 2008-12-18 (CONF:9045).

      CMS has not released any other valuesets to supercede these – I believe these errors are incorrect.

      I did receive the following from Robert Dingwell on this issue:

      I'll take a look. We have a white list of QRDA defined value sets that are supposed to short circuit some of the testing process for various data elements. It may be that those oids did not get added.

      I'm putting this ticket in so that this issue is documented during the shutdown.

        Attachments

          Activity

            People

            • Assignee:
              renee.rookwood Renee Rookwood
              Reporter:
              jkratz Jason Kratz
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Comment Posted On: