Similar to flare the filter of a same type of an AttributeGroup should be split into multiple queries.
This significantly improves performance and ensures that single requests do not get too large when a criterion with many children gets expanded.
It is important to only break up parameters which are combined using OR.
In the current case this only affects CODE filter.
Further be aware that other filter have to be added
so that all filter and their combinations are expanded.
Similar to flare the filter of a same type of an AttributeGroup should be split into multiple queries.
This significantly improves performance and ensures that single requests do not get too large when a criterion with many children gets expanded.
It is important to only break up parameters which are combined using OR. In the current case this only affects CODE filter. Further be aware that other filter have to be added so that all filter and their combinations are expanded.
=> ?patient=1,2&code=1,2,3&date=gt2025 expands to
?patient=1,2&code=1&date=gt2025 ?patient=1,2&code=2&date=gt2025 ?patient=1,2&code=3&date=gt2025
=>
a CRTDL with a filter
leads to the following query:
instead torch should break the query up into: