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
When overloading a fluent function, using the same function name but different arguments, it seems that the order in which the functions appear in the CQL library matters.
Below is an example showing how you get different results when ordering the fluent functions:
When overloading a fluent function, using the same function name but different arguments, it seems that the order in which the functions appear in the CQL library matters.
Below is an example showing how you get different results when ordering the fluent functions:
`library IssueFluentFunctions
using FHIR version '4.0.1'
context Patient
define "EobFluentFunctionError": ([ExplanationOfBenefit]).ffoverload()
define fluent function ffoverload(eob List):
eob.item.serviced.value
define fluent function ffoverload(obs List):
obs.effective.value
////////////////////////////////////////////////////////////////////////////////////
define "EobFluentFunctionError2": ([ExplanationOfBenefit]).ffoverload2()
define fluent function ffoverload2(obs List):
obs.effective.value
define fluent function ffoverload2(eob List):
eob.item.serviced.value`
The results are as follows:
Patient=Patient(id=SamplePatient1)
EobFluentFunctionError=[]
EobFluentFunctionError2=[2023-03-31]
Not sure what the expected behavior is but the expected result is that the date should be returned for both.
IssueFluentFunctions.zip
The text was updated successfully, but these errors were encountered: