Expected behavior
When the cohort definition editor opens, the only requests made to WebAPI are the ones necessary to set up the editor
Actual behavior
When loading a cohort definition, there is a call to the WebAPI/conceptset/ endpoint which loads the full list of concept sets in the WebAPI database for each concept set present in the cohort definition.
Steps to reproduce behavior
Load a cohort definition with > 0 concept sets. Observe the network trace via Google Chrome developer tools:
The screenshot above shows 5 calls to WebAPI/conceptset/ which is the number of concept sets in my cohort definition entry event section. If you open an inclusion rule with > 0 concept sets, WebAPI/conceptset/ is once again called for each concept set present in the inclusion rule.
Expected behavior
When the cohort definition editor opens, the only requests made to WebAPI are the ones necessary to set up the editor
Actual behavior
When loading a cohort definition, there is a call to the
WebAPI/conceptset/endpoint which loads the full list of concept sets in the WebAPI database for each concept set present in the cohort definition.Steps to reproduce behavior
Load a cohort definition with > 0 concept sets. Observe the network trace via Google Chrome developer tools:
The screenshot above shows 5 calls to
WebAPI/conceptset/which is the number of concept sets in my cohort definition entry event section. If you open an inclusion rule with > 0 concept sets,WebAPI/conceptset/is once again called for each concept set present in the inclusion rule.