-
Question
-
Resolution: Referred to External Party for Resolution
-
Blocker
-
None
-
BONNIE
-
Bonnie QDM
-
Antithrombotic Therapy By End of Hospital Day 2
-
CMS72
-
QDM/CQL
-
DENEXCEPPass MedAdmMedReason_eq1dayduringEncIP DENEXCEPFail INR2DaysAftEnc_NoEDNoObsBFEnc2DayAft
-
Measure: Antithrombotic Therapy By End of Hospital Day 2
Account: hmdmtjc
Test cases:
DENEXCEPPass MedAdmMedReason_eq1dayduringEncIP
DENEXCEPFail INR2DaysAftEnc_NoEDNoObsBFEnc2DayAft
We are changing our function, TJC."CalendarDayOfOrDayAfter" to no longer use Global."ToDate" (because it was retired for 2022AU).
Here is what we had before:
TJC.CalendarDayOfOrDayAfter(StartValue DateTime)
Interval[Global."ToDate" ( StartValue ), Global."ToDate" ( StartValue + 2 days ) )
and
Global.ToDate(Value DateTime)
DateTime(year from Value, month from Value, day from Value, 0, 0, 0, 0, timezoneoffset from Value)
We have tried the following replacements for Global."ToDate" and it makes many of our test cases angry.
1. define function "CalendarDayOfOrDayAfter" ( StartValue DateTime ):
Interval[date from ( StartValue ), date from ( Start Value + 1 day) ]
breaks 21 test cases including DENEXCEPPass MedAdmMedReason_eq1dayduringEncIP
2. define function "CalendarDayOfOrDayAfter" ( StartValue DateTime ):
Interval[date from ( StartValue ), date from ( Start Value + 2 days) )
breaks 7 test cases including DENEXCEPFail INR2DaysAftEnc_NoEDNoObsBFEnc2DayAft
Global."ToDate" explicitly zeroed the time field. We tried re-entering the test case date and time in the hopes of clearing seconds and milliseconds, in case that was the problem.
Please see attached for the comparison of the behavior of these two test cases for Bonnie Prior and this 2022 AU change. Any advice and guidance would be appreciated.