Closed kylejbrk closed 4 years ago
Sure, I think it's a bug. Thank you for pointing this out, @kylejbrk . We'll fix it soon
I tried digging for the page parameter in the docs, but I couldn't find it. It doesn't look like my client supports it at all, hence why it's getting stuck in the loop.
So perhaps the page parameter is not part of the FHIR standard?
Yep, of course. As far as I know now (according to this https://www.hl7.org/fhir/http.html#paging), FHIR standard doesn't specify which parameters should be used for paging. Client just have to use a link provided in "next" relation from a response (if exists).
Done.
Not sure if this problem is specific to the FHIR Server I am pulling from, but supplying a page number will always return a bundle with resources. The current fetch_all() code uses this:
Since my server always returns something regardless of the page number, it gets stuck in the loop above. The way I've gotten around this in the past is to refer to the next link in the Bundle .
I suppose a quick and dirty solution would be something like the following: