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 evaluate-measure is run in hapi-fhir-jpastarter we are noticing that the call for all subjects is cutting off on the paging limit of the server and not getting all subjects avaialble
this is the code that it is hitting in R4RepositorySubjectProvider:
BundleMappingIterable<>(repository, bundle, x -> x.getResource() .getIdElement() .toUnqualifiedVersionless() .getValue()) .toStream();
This creates a scenario where users are limited to the population sizes that can be queried
Steps to reproduce:
Run $evaluate-measure with subject parameter empty for all subjects where population is > paging limit of returned search bundle. Our use case was quering >50 subjects
Observed results:
evaluate-measure subject population is 50
Expected results:
evaluate-measure subject population > 50
The text was updated successfully, but these errors were encountered:
When evaluate-measure is run in hapi-fhir-jpastarter we are noticing that the call for all subjects is cutting off on the paging limit of the server and not getting all subjects avaialble
this is the code that it is hitting in R4RepositorySubjectProvider:
BundleMappingIterable<>(repository, bundle, x -> x.getResource() .getIdElement() .toUnqualifiedVersionless() .getValue()) .toStream();
This creates a scenario where users are limited to the population sizes that can be queried
Steps to reproduce:
Observed results:
evaluate-measure subject population is 50
Expected results:
evaluate-measure subject population > 50
The text was updated successfully, but these errors were encountered: