Uncertainty Produced for Duration Operation Involving Days Granularity

[JSRankins]

Summary

Good afternoon. We wanted to keep you in the loop about this issue. The MADiE team received a ticket related to uncertainty surfacing in a Measure Observation when a duration operation is invoked: MADIE-2024. It appears to occur when no milliseconds are provided by user during certain circumstances. To simplify things, I have created a small measure, test data sets and ran them through fqm-execution CLI 1.5.0. We have submitted an issue to cql-execution: Issue 325.

External Tracking Ticket

MADIE-2024
cql-execution issue 325

Expected Behavior

Integer results for duration when appropriate data provided.

Version or Commit

1.5.0

Inputs (e.g. Measure Bundle, Patient Bundle, CQL Library)

Data is in cql-execution issue 325 but provided here for ease of use:

• Measure Bundle: DMT-v0.0.000-FHIR.json
• File with ms producing no issue: DurationIssueMS.json
• File with no ms producing issue: DurationIssueNoMS.json

cql-to-elm Version Used for Measure Logic Translation (if known)

3.3.2

[JSRankins]

After discussion with MITRE about cql-execution Issue 325, The belief is that execution is acting correctly in terms of requiring milliseconds under circumstances where the duration calculation cannot determine a whole unit for the specified datetime inputs. Waiting for feedback from Bryn and Peter.

[JSRankins]

Further feedback has been given by Bryn and Peter. Based on further information, belief now is that cql-execution needs to be updated. Refer to comment from Bryn at cqframework/cql-execution#325 (comment).

[JSRankins]

Based on comment in cqframework/cql-execution#325 (comment), cql-execution is waiting for update to CQL to clarify that the rules used for comparison regarding seconds and milliseconds apply for duration calculations.