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

Measure Validation engine incorrectly calculates times

XMLWordPrintable

    • Hide
      On QRDA import, Cypress shifts all times to UTC±00:00.

      If calculation errors due to timezone shifting during a certification, have your ATL reach out to the Cypress team for guidance.

      Alternatively, changing the system time of the software instance being tested set to UTC±00:00 will mitigate this issue.
      Show
      On QRDA import, Cypress shifts all times to UTC±00:00. If calculation errors due to timezone shifting during a certification, have your ATL reach out to the Cypress team for guidance. Alternatively, changing the system time of the software instance being tested set to UTC±00:00 will mitigate this issue.
    • CMS108v8/NQFna, CMS190v8/NQFna

      In Cypress 4.0.2, the measure validation engine is incorrectly calculating statuses for uploaded QRDA I documents. An uploaded QRDA I for Shirley Blair (19 N VTE) is inappropriately calculated in DENEX.

      241201_Z7167_E5310.xml is being calculated by Cypress in DENEX because the measure validation engine incorrectly calculates Location.locationPeriod starts during VTEICU."CalendarDayOfOrDayAfter"(start of QualifyingEncounter.relevantPeriod)

      What is being sent in 241201_Z7167_E5310.xml is as follows. It is clear that Date 1 should not count as during CalendarDayOfOrDayAfter Date 2.
      Date 1 representing start of QualityEncounter.relevantPeriod: 2019-04-21 20:00:00 (-05:00)
      Date 2 representing Location.locationPeriod start: 2019-04-23 08:00:00 (-05:00)

      We believe the Cypress measure validation engine is not performing a normalization calculation based on the received data, but rather is converting the timestamps of Date 1 and Date 2 to the following. This is where we believe the Cypress measure engine incorrectly Date 1 as during CalendarDayOfOrDayAfter Date 2.
      Altered Date 1: 2019-04-22 01:00:00 (+00:00)
      Altered Date 2: 2019-04-23 13:00:00 (+00:00)

      Regardless of whether the imported document should contain time zone offsets, a receiving system should be able to perform difference calculations with normalization of datetimes. This is expected of all vendors, The Joint Commission, and CMS. If Cypress intends to continue calculating measure statuses at a time zone of (+00:00), all timestamps in documents available to import need to include the +00:00 offset.

      Attached is the Cypress generated document (56_Shirley_Blair.xml) and our exported document (241201_Z7167_E5310.xml).

            laurend Lauren DiCristofaro (Inactive)
            Alex Liu Alex Liu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: