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
The following CQL results in an Ambiguous call to operator 'isCommunity(org.hl7.fhir.r4.model.MedicationRequest)' error at runtime:
define fluent function isCommunity(medicationRequest MedicationRequest):
exists (medicationRequest.category C
where C ~ Community
)
define fluent function isCommunity(medicationRequest MedicationNotRequested):
exists (medicationRequest.category C
where C ~ Community
)
This code worked in v3.15.0. The following update appears to have introduced this issue.
I’ve already tried setting the signature level to Overloads using: evaluationSettings.getCqlOptions().getCqlCompilerOptions().setSignatureLevel(LibraryBuilder.SignatureLevel.Overloads);
but this didn’t resolve the issue.
The apparent challenge here is that these are legitimately different signatures in CQL, but not in ELM. The ELM shows the same resultType for the medicationRequest operand, being {http://hl7.org/fhir}MedicationRequest.
The text was updated successfully, but these errors were encountered:
The following CQL results in an
Ambiguous call to operator 'isCommunity(org.hl7.fhir.r4.model.MedicationRequest)'
error at runtime:This code worked in v3.15.0. The following update appears to have introduced this issue.
I’ve already tried setting the signature level to Overloads using:
evaluationSettings.getCqlOptions().getCqlCompilerOptions().setSignatureLevel(LibraryBuilder.SignatureLevel.Overloads);
but this didn’t resolve the issue.
The apparent challenge here is that these are legitimately different signatures in CQL, but not in ELM. The ELM shows the same
resultType
for themedicationRequest
operand, being{http://hl7.org/fhir}MedicationRequest
.The text was updated successfully, but these errors were encountered: