You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This code is still looking specifically at the information in the modelinfo header.
The "simple" fix seems like it would be to call getContextInfo() and retrieve the birthDateElement from one of the contexts returned. That would require it to be context aware to work properly, i think. Which is not information that i see readily available to the class right now.
For patient contexts, Patient Birth Date information must be supplied as well to allow the CQL-to-ELM translator to render references to patient-age-related functions (AgeInYears, AgeInYearsAt, etc.) into the non-patient-aware age-related functions in ELM (CalculateAgeInYears, CalculateAgeInYearsAt, etc.). This information is not required, but if it is not present, references to patient-age-related functions will be passed directly through to ELM as FunctionRefs.
I'm fairly green to the project, i fully admit i could be missing something, but i couldnt find any reference to this elsewhere so im logging this for at least a discussion/explanation of it.
The text was updated successfully, but these errors were encountered:
Some time ago, 7b8f435 marked
patientBirthDatePropertyName
as deprecated within the modelinfo schema.As such, i would expect to be able to omit it from the model info header if i define the patient context in my model info:
Compiled against cql like this:
I would expect success.
However i get this instead
The problem seems to lie in this snippet here:
clinical_quality_language/Src/java/cql-to-elm/src/main/java/org/cqframework/cql/cql2elm/SystemFunctionResolver.java
Lines 414 to 415 in dfafdb9
This code is still looking specifically at the information in the modelinfo header.
The "simple" fix seems like it would be to call getContextInfo() and retrieve the birthDateElement from one of the contexts returned. That would require it to be context aware to work properly, i think. Which is not information that i see readily available to the class right now.
Looking at the cql spec here: https://cql.hl7.org/07-physicalrepresentation.html
i do see a clause that seems to describe an alternate behavior to what is happening here, under "Context Information":
I'm fairly green to the project, i fully admit i could be missing something, but i couldnt find any reference to this elsewhere so im logging this for at least a discussion/explanation of it.
The text was updated successfully, but these errors were encountered: