-
Bug/Issue
-
Resolution: Resolved
-
Critical
-
None
-
BONNIE
-
Bonnie QDM
-
CMS72v10
-
ANTITHROMBOTIC THERAPY BY END OF HOSPITAL DAY 2
-
QDM/CQL
-
NUMERPass MedAntithromboticStart_eq0dayB4EdStart and 7 more
-
This will affect AU2022 for STK-5, VTE-1 and VTE-2 and prevent progress to Round 2.
Global.”ToDate” function was eliminated for AU2022. We were urged to not just repeat it in our TJCOverall library and leave it in our code but rather to use ‘date from’ rather than Global.”ToDate” and when the left side of the comparision is a datetime, to use the operation modifier of ‘day of’. It was thought that this would cause the left side to be treated as a date without application of timezone offset. But it appears that in Bonnie, that the timezone offset is applied to the left datetime before doing a date comparison to a date interval. ‘day of’ operation modifier does not appear to prevent application of timezone offset to the leftside in Bonnie. This will affect AU2022 for STK-5, VTE-1 and VTE-2.
Please see the attached document.
Below are the testcase and how it worked before and after the change:
Testcase: NUMERPass MedAntithromboticStart_eq0dayB4EdStart
*Before: *Bonnie 4.3.0 CMS72v10
Account: hmdmtjc
define function "CalendarDayOfOrDayAfter"(StartValue DateTime ): Interval[Global."ToDate" ( StartValue ), Global."ToDate" ( StartValue + 2 days ) )
Testcase: NUMERPass MedAntithromboticStart_eq0dayB4EdStart
After: Bonnie 5.1.0 CMS72v10
Account: hmdmtjc
define function "CalendarDayOfOrDayAfter"(StartValue DateTime ): Interval[date from ( StartValue ), date from ( StartValue ) + 1 day]
- relates to
-
MADIE-990 Discrepancies between "Date from()" and "day of"
- Closed