FHIR icon indicating copy to clipboard operation
FHIR copied to clipboard

Add support for the CQL Long datatype

Open csandersdev opened this issue 3 years ago • 1 comments

Is your feature request related to a problem? Please describe. In the CQL 1.5.2 release, a new Long data type was added to the CQL typesystem. We need to make some changes to our CQL backend to support the new data type. FHIR R5 will add an integer64 datatype that will correspond to the CQL Long type, so this can probably wait until we start working on that support.

Describe the solution you'd like CQL that uses the Long data type is supported

Describe alternatives you've considered We can continue as we are today without problem as long as none of the CQL being executed relies on the Long datatype.

Acceptance Criteria

  1. GIVEN a CQL with a define that returns a System.Long value of MAX_INTEGER + 1 WHEN the /Library/$evaluate operation is executed against the CQL library THEN the CQL is successfully executed AND the output parameters object contains a FHIR integer64 parameter AND the value is correctly represented as MAX_INTEGER + 1
  2. GIVEN a CQL with an input parameter of System.Long defined... WHEN the /Library/$evaluate operation is executed with a FHIR integer64 parameter THEN the parameter value is passed to the CQL Engine as System.Long

Additional context The test cases above are the most obvious places where support needs to be added. There are other operations such as Library/$data-requirements and Measure/$data-requirements that should be investigated for further impact.

csandersdev avatar Jan 13 '22 15:01 csandersdev

maybe with #4090

lmsurpre avatar Nov 28 '22 14:11 lmsurpre