-
Bug/Issue
-
Resolution: Resolved
-
Moderate
-
None
-
CMS155v9/NQFna
-
v6.1.2
I just updated Cypress form 6.0.1 to 6.1.2 and CMS155 has changed.
Previously (I presume correctly) the PopulationSet 2 and PopulationSet 3 NUMER had 0 values, but now they have 5 and 2 respectively.
However, the NUMER in both cases requires relevantDatetime to be set:
define "Numerator 2":
exists ["Intervention, Performed": "Counseling for Nutrition"] NutritionCounseling
where NutritionCounseling.relevantDatetime during "Measurement Period"define "Numerator 3":
exists ["Intervention, Performed": "Counseling for Physical Activity"] ActivityCounseling
where ActivityCounseling.relevantDatetime during "Measurement Period"
I think the relevantDatetime is only set in two instances of intervention performed (one nutrition counseling and one physical activity counseling, and the rest of the cases have both high and low like this:
<effectiveTime><low value='20210501163000'/><high value='20210501164500'/></effectiveTime>
It appears to me the expected numer should be 1 in both of these cases.
- relates to
-
CYPRESS-2222 Cypress6.1.2: Using RelevantPeriod instead of RelevantDateTime for CMS155v9 and CMS69v9
- Closed
-
CYPRESS-2224 Patients Mixing Up relevantPeriod and relevantDatetime in Bundle 2020.0.5
- Closed
-
QKI-2 Guidance for reporting eCQMs with QDM data types allowing either relevantDatetime or relevantPeriod attributes for the 2021 reporting/performance period
- Done